Applying empirical models for estimation

Using simple decomposition techniques for estimation

Basing estimates on previously completed similar projects

The ability to convert size estimates into effort, time, and cost

Focus solely on risk identification

None 

To assess project progress and identify potential risks

Monitor only the current project status

Applying empirical models for estimation

Using simple decomposition techniques for estimation

Basing estimates on previously completed similar projects

The ability to convert size estimates into effort, time, and cost

Process improvement

Coding standards only

Product delivery

Hardware testing

Behavioural elements

Flow-oriented elements

Scenario-based elements

Class-based elements

To write source code

To test the final product

To gather and define user needs

To design system architecture

Verification checks functionality; Validation checks code

Verification is static; Validation is dynamic

Validation is done before Verification

Both are same

Number of developers

Time taken to fix bugs

Cost of testing

Number of defects per size of software

Grey-box testing

Black-box testing

White-box testing

All Mentioned

Guessing inputs

Skipping invalid cases

Boundary Value Analysis

Random testing