Rapid Application Development

1) Less Documentation.
2) Faster Delivary Time.

Iterative Builds

1) Phased: Customers uses version 1,2 etc.
2)Prototyping: Customer views version 1.

Iterative Design:

3) Throwaway Prototyping: Design version only.

Prioritising Requirements:

Two Functions:

1) Version release to customer as early as possible.
2) If expectations are high but budgets are low-product must contain the essential elements.

Difficulties:

1) Customers want everything in version 1.
2) For customers to set priorities.
3) Functionality is interlinked and hard to be seperated.

Sample Requirments Scales:

High Priority: Product not acceptable without this function or feature.
mission critical.
required for next release.

Medium Priority: Supports necessary system operations. Required eventually but not immediately.
Would enhance the product.

Low Priority:Nice to have if budget allows.

Steps:

1) List all the features/functions contained in the requirements.
2) Assocaiate each one with a priority category and state a reason why.
3) Sort the list into a descending order of importance.
4) Agree final list with customers.
5)Group features/functions in to versions.