The objectives of the Product Requirements Review Procedure (for Low Control?) are to - Define the process to review Product Requirements (e.g., System Requirements, Software Requirements) and changes to Product Requirements.
- Establish a standard set of Product Requirements quality criteria (documented in the Product Requirements Checklist in Appendix A).
- Ensure that Product Requirements have undergone a thorough review and update using the Product Requirements Checklist.
- Ensure that Product Requirements are complete, consistent, correct, unambiguous, and verifiable.
This procedure applies to the development and review of technical Product Requirements for LaRC Low-Control projects/activities (as opposed to requirements defined in a Statement of Work which are reviewed using the 'Statement of Work (SOW) Review Procedure'). For an extended definition of Control Class, see Appendix D of the 'Product Requirements Development and Management Procedure'.
A project/activity is defined as Low Control if all of the following are true; the project/activity has:- a total potential personnel resource investment of less than 8 FTE (but more than 2 FTE) across all lifecycle phases; depending on the full cost of the FTE, this may be between $0.5M to over $2M,
- a potential for waste of facility resources (e.g., electricity, liquid nitrogen, operational costs) of less than $250K - but greater than $50K if failure occurred; this is only the cost of potential waste of facility resources if failure occurred - not the total cost of the project/activity,
- potential risk to routine operations of at most a facility inconvenience if a failure occurred (e.g., a facility test has to be re-run due to the failure), or
- potential for knowledge of a failure at the Directorate or Branch level if failure occurred.
If the project/activity 1) exceeds any one of the above; or 2) has the potential for safety mishap, i.e., loss of life, serious injury, or damage to equipment greater than $1M; or 3) has the potential for catastrophic or partial mission failure, it should follow the 'Product Requirements Development and Management Procedure'. |