Software Processes Flashcards
1
Q
Specification
A
- Defining what the system should do
2
Q
Design and implementation
A
- Defining the organization of the system and implementing the system
3
Q
Validation
A
- Checking that the system does what the customer wants
4
Q
Evolution
A
- Changing the system in response to changing customer needs
5
Q
Stages of testing
A
- Component/development testing
- System/release testing
- Customer/user testing
6
Q
Software prototype
A
- A prototype is an initial version of a system used to demonstrate concepts and try out design options.
7
Q
Process metric
A
- Used to measure the efficiency and effectiveness of various processes
8
Q
Design activities
A
- Architectural design
- Database design
- Interface design
- Component selection and design
9
Q
Reducing the costs of rework
A
- Change anticipation
- Change tolerance
10
Q
Benefits of prototyping
A
- Improved system usability
- A closer match to users’ real needs
- Improved design quality
- Improved maintainability
- Reduced development effort
11
Q
Throw-away prototypes
A
- It may be impossible to tune the system to meet non-functional requirements.
- Prototypes are normally undocumented.
- The prototype structure is usually degraded through rapid change.
- The prototype probably will not meet normal organizational quality standards.
12
Q
Incremental delivery
A
- The development and delivery are broken down into increments, with each increment delivering part of the required functionality.
- User requirements are prioritized, and the highest priority requirements are included in early increments.
13
Q
Process improvement
A
- Way to enhance quality of software
- Process maturity approach
- Agile approach
14
Q
Process improvement activities
A
- Measure
- Analysis
- Change
