Requirements Prototype
A
requirements prototype is a
requirements work
product consisting of prototype used to identify new
requirements and
identify defects in existing ones.
The typical objective of a requirements prototype is to:
- Identify new requirements.
- Identify defects in existing requirements.
The typical benefits of a requirements prototype are:
- Requirements prototypes make it easier for stakeholders
to identify requirements when requirements are unclear.
The typical contents of a requirements prototype are:
- Varies by type of requirements prototype.
The typical stakeholders of a requirements prototype
are:
- Producers:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
-
Requirements Team, which uses the requirements
prototypes to identify new potential requirements and
identify defects in existing requirements.
Requirements prototypes are typically produced during the
following phases:
Requirements prototypes typically can be started if the
following preconditions hold:
The typical inputs to an external card include:
- Work Products:
- Stakeholders:
- Requirements prototypes are typically developed
incrementally, iteratively, and in parallel with other
requirements work products.
- Requirements prototypes may have varying degrees of
fidelity from paper user interfaces to executable
simulations.
Requirements prototypes are typically constrained by the
following conventions:
-
Example Requirements
Prototype