| 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 |
| Bounding - | (Software Engineering) removing ambiguity from specification |
| 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 - |
| Change request - | (Software Engineering) provides detail on the type of change that is requested |
| Configuration status reporting (CSR) - | (Software Engineering) an activity that help software developer to understand what changes have been made and why |
| Customer - | (Software Engineering) the person or group that has requested the software and will be paying the bill for its development |
| Data design - | (Software Engineering) an activity that translates the data model developed during analysis into implementable data structures |
| Data warehouse - | (Software Engineering) a large, independent database that has access to databases that serve many different applications that are required by a business |
| Design specification - | (Software Engineering) a document that describes the design |