Software engineering test 1 - extra notes
constructive cost model
(COCOMO) approach, which originated in the work of Barry Boehm. Boehm has
modified and extended his original COCOMO to COCOMO II (Boehm et al. 2000).
Conceptual level
Establish a goal. For instance,
“Improve the time to locate a
software code problem.
”
Operational level
Develop a list of questions related to the goal. For example,
“How does the program complexity influence software debugging time?”
Quantitative level
Develop metrics. These could include the number of control
loops in the program for control complexity and the number of person-minutes
spent on debugging efforts.
The Adjusting Phase of Project Management
Resources
Schedule
Project content
Some Project Management Techniques
(1) project effort estimation, (2) work breakdown structure, (3) project status
tracking with earned value, and (4) developing measurements and metrics.
The original
COCOMO includes three levels of models
a macro, an intermediate, and a micro.
These fifteen cost-drivers may
be categorized into four main groups
Product attributes, Computer attributes, Personnel attributes and Project attributes
COCOMO II does still ask for an estimate of the size, which can now take on one
of the three metrics
KLOC, Function point, Object point
Five components of software are considered in the function point estimation
process
1. External inputs
2. External outputs
3. External inquiries
4. Internal logical files
5. External interface files
Five components of software Each component is assigned a weight, based on three possible descriptions of the
project:
1. Simple
2. Average
3. Complex
Program requirements
Statements that define and qualify what the program needs to do.
Design constraints
Statements that constrain the ways in which the software can be designed and implemented.
functional requirements
what the
program does
nonfunctional requirements
—the manner in which the
program must behave
Functional requirements
What a program needs to do.
Nonfunctional requirements
The manner in which the functional requirements need to be achieved.
Nonfunctional Requirements
Performance requirements
Real-time requirements
Modifiability requirements
Security requirements
Usability requirements