Boundary value analysis - |
(Software Engineering) a black box testing method that designs test cases that exercise data boundaries |
Business risks - |
(Software Engineering) the set of potential business problems or occurrences that may cause the project to fail |
Change control authority (CCA) - |
(Software Engineering) the person(s) who have responsibility for deciding whether a change is to be made |
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 |
Cohesion - |
(Software Engineering) an informal measure of the degree to which a software component implements a single, focused function |
Configuration items - |
(Software Engineering) the individual pieces of programs, documents and data that are controlled using SCM |
Constraints - |
(Software Engineering) an restrictions or limitations placed on requirements or design |
CRC (class-responsibility-collaborator) modeling - |
(Software Engineering) an object-oriented modeling method that identifies and organizes classes are are relevant to a system |
Data design - |
(Software Engineering) an activity that translates the data model developed during analysis into implementable data structures |