Project QuickLook
Manage and Trace Requirements
- Is there a systems engineering process to lower the risk
of high-risk software requirements allocated to software components
in the system design? If so, provide a copy of the written description
of this process.
- Provide a copy of your most detailed description, if any,
of your process for defining system requirements.
- Identify the operational organizations that have provided
people to participate in systems requirements definition.
- If this is an information system, are business rules and
high-volume transactions included in the system requirements?
If so, how many business rules have been defined and how many
high-volume transactions have been defined?
- Are operational scenarios included in the system requirements?
If so, how many operational scenarios are specified?
- What is your approach to ensuring requirements are complete
and consistent?
- Are you following an incremental development life cycle model
in which new requirements will be defined for later incremental
releases based on user experience with earlier releases? If so,
- What will be the first release when the system architecture is complete?
- What will be the first release when system security requirements are complete?
- What will be the first release when system safety requirements
are complete?
- What percentage of the total source lines of code in the first two incremental releases do you expect to be included in the final incremental release?
