| Architecture - | (Software Engineering) the overall structure of software components, the data and/or content that components manipulate, and the relationships between them |
| Aspect-oriented development - | (Software Engineering) a development approach that emphasizes "concerns" (also called "aspectual requirements" that incorporate features, functions and information content) that cut across multiple system functions |
| Baseline - | (Software Engineering) a point at which some deliverable produced during the software engineering process is put under formal change contro |
| Change control - | (Software Engineering) an umbrella process that enables a project team to accept, evaluate, and act on changes in a systematic manner |
| Change control authority (CCA) - | (Software Engineering) the person(s) who have responsibility for deciding whether a change is to be made |
| Change management - | (Software Engineering) a set of software engineering actions that helps ensure that changes are properly identified, controlled, and reportedChange report - |
| Configuration - | (Software Engineering) the collection of programs, documents and data that must be controlled when changes are to be madeConfiguration audit - |
| Configuration control - | (Software Engineering) the control of changes to programs, documents or data |
| Configuration items - | (Software Engineering) the individual pieces of programs, documents and data that are controlled using SCM |
| Data dictionary - | (Software Engineering) a database that contains definitions of all data items defined during analysis; see also, Requirements dictionary |