Software Processes

Question 1

Specification

Answer 1

• Defining what the system should do

Question 2

Design and implementation

Answer 2

• Defining the organization of the system and implementing the system

Question 3

Validation

Answer 3

• Checking that the system does what the customer wants

Question 4

Evolution

Answer 4

• Changing the system in response to changing customer needs

Question 5

Stages of testing

Answer 5

• Component/development testing
• System/release testing
• Customer/user testing

Question 6

Software prototype

Answer 6

• A prototype is an initial version of a system used to demonstrate concepts and try out design options.

Question 7

Process metric

Answer 7

• Used to measure the efficiency and effectiveness of various processes

Question 8

Design activities

Answer 8

• Architectural design
• Database design
• Interface design
• Component selection and design

Question 9

Reducing the costs of rework

Answer 9

• Change anticipation
• Change tolerance

Question 10

Benefits of prototyping

Answer 10

• Improved system usability
• A closer match to users’ real needs
• Improved design quality
• Improved maintainability
• Reduced development effort

Question 11

Throw-away prototypes

Answer 11

• 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.

Question 12

Incremental delivery

Answer 12

• 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.

Question 13

Process improvement

Answer 13

• Way to enhance quality of software
• Process maturity approach
• Agile approach

Question 14

Process improvement activities

Answer 14

• Measure
• Analysis
• Change