Least important

functionality

Most urgently

required functionality

Only minor

functionalities

Randomly picked

functionality

Maintenance is no

longer necessary

Development is now

seen as uninteresting

They should be

considered as a continuum

They are still two

separate processes

System prototyping

Dismissing new

requirements

Waiting for the

change to occur

Ignoring customer feedback

Designing the

software to easily accommodate changes

Making abrupt changes

without considering their impacts

Making changes

difficult to implement

Rejecting any changes

to the initial plan

Systems with

requirements likely to change during the development process

Systems with static

requirements

Systems that do not

require user feedback

Systems with

well-defined requirements from the beginning

The process

activities are spontaneously decided upon

None of the answer choices are correct

The planning is

incremental and easily changes to accommodate customer requirements

All process

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

They are completed

separately

They are not

important

They are outsourced

They are combined and

no formal design documents are produced

Requirements

Gathering

Maintenance

Testing

Implementation

It enforces premature

commitment to full system requirements

It increases the

overall cost of software development

It allows changes to

be incorporated into later increments at a lower cost

It reduces the need

for customer feedback

In the final software

product

On whiteboards and

programmers' notebooks

In formal design

documents

In customer feedback