Usability

Performance

Security

Functionality

Estimating software development effort and cost

Planning software testing activities

Managing software risks

Predicting software defects

A prototype helps in development of accurate project schedule.

 A working prototype helps the customer to provide meaningful feedback about the requirements.

A prototype is iteratively enhanced into a working software and is finally deployed at the client site.

A prototype is deployed at the client site as an operational software till the full version is developed

Approximately 260 person-months

Approximately 180 person-months

Approximately 200 person-months

Approximately 230 person-months

Requirements Inception 

Requirements management

Requirements validation

All of these

 Ignore it as it's too vague.

Accept it as a valid non-functional requirement.

Ask the librarian to provide specific, measurable criteria for "fast" (e.g., response time).

Implement the system and hope it's fast enough.

The Complexity Adjustment Factor (CAF).

The Unadjusted Function Point count (UFP).

Both CAF and TDI

Total Degree of Influence (TDI)

The WBS should be high-level and decomposed into smaller chunks as the project progresses, reflecting the iterative nature of Agile.

The WBS is not relevant in Agile projects.

The WBS should be very detailed and fixed at the beginning of the project.

The WBS should only include user stories.

The team is not skilled enough.

The team is using the wrong development methodology.

The project manager is not effective.

There is a lack of proper requirements management and change control.

Design

Project Management

Testing

Coding