| Black box testing - | (Software Engineering) testing that does not focus on the internal details of the program but uses external requirements |
| Boundary value analysis - | (Software Engineering) a black box testing method that designs test cases that exercise data boundaries |
| Bounding - | (Software Engineering) removing ambiguity from specification |
| Business risks - | (Software Engineering) the set of potential business problems or occurrences that may cause the project to fail |
| CASE - | (Software Engineering) Computer-aided software engineering, see also, Tools |
| Cause-effect graphing - | (Software Engineering) a black-box testing method |
| 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 - |
| Change request - | (Software Engineering) provides detail on the type of change that is requested |