| Black box testing - | (Software Engineering) testing that does not focus on the internal details of the program but uses external requirements |
| Business risks - | (Software Engineering) the set of potential business problems or occurrences that may cause the project to fail |
| Change control - | (Software Engineering) an umbrella process that enables a project team to accept, evaluate, and act on changes in a systematic manner |
| 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 |
| Chief programmer team - | (Software Engineering) one way of organizing project staff |
| Classes - a basic construct in object - | (Software Engineering) oriented methods that categorizes elements of the problem |
| Classic life cycle - | (Software Engineering) a linear, sequential approach to process modeling |
| Clusters - | (Software Engineering) a collection of program components (modules) that is tested as a group |
| Complexity - | (Software Engineering) a quantitative measure of a program's complexity |