Avoiding any possible

changes

Ignoring possible

changes until they occur

Reacting to changes

once they occur

Implementing

activities that can predict possible changes to minimize rework

Dismissing new

requirements

Waiting for the

change to occur

System prototyping

Ignoring customer feedback

They are still two

separate processes

They should be

considered as a continuum

Maintenance is no

longer necessary

Development is now

seen as uninteresting

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

Systems with

well-defined requirements from the beginning

Systems with static

requirements

Systems that do not

require user feedback

Systems with

requirements likely to change during the development process

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

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

System and software

design

Implementation and

unit testing

Integration and system testing

Requirements analysis

and definition