Rejecting any changes

to the initial plan

Designing the

software to easily accommodate changes

Making changes

difficult to implement

Making abrupt changes

without considering their impacts

They are still two

separate processes

They should be

considered as a continuum

Maintenance is no

longer necessary

Development is now

seen as uninteresting

Dismissing new

requirements

Waiting for the

change to occur

System prototyping

Ignoring customer feedback

They are completed

separately

They are combined and

no formal design documents are produced

They are not

important

They are outsourced

The process

activities are spontaneously decided upon

All process

activities are planned in advance and progress is measured against this plan

None of the answer choices are correct

The planning is

incremental and easily changes to accommodate customer requirements

Requirements

Gathering

Maintenance

Testing

Implementation

System and software

design

Implementation and

unit testing

Integration and system testing

Requirements analysis

and definition

In the final software

product

In formal design

documents

In customer feedback

On whiteboards and

programmers' notebooks

It increases the

overall cost of software development

It enforces premature

commitment to full system requirements

It allows changes to

be incorporated into later increments at a lower cost

It reduces the need

for customer feedback

Correcting errors

from earlier stages and refining system unit implementations

User consultation

Testing of individual

program units

Translation of design

into code