Skip to main content

MSF for CMMI Process Improvement

Go Search
Home
  
MSF for CMMI Process Improvement > Wiki Pages > Activity - Define Safety Requirements  

Activity - Define Safety Requirements

Activity Information

Define Safety Requirements

Description

Safety requirements specify steps taken to protect human life and limb during human/product interaction. They must reflect any industry-specific regulatory requirements. These requirements deal with any hazardous element of a product that is made up of, or controlled by software. If the software is part of a system, these software safety requirements are defined as part of the overall system safety requirements. Grouping these safety requirements stresses their importance and aids in their tracking, design, development, testing, and validation. While it is true that not all software projects have safety issues that need to be addressed, it is recommended to consider safety requirements early in any project.

Attributes

Element Categories[CMMI Level 3] RD SP 3.2, [CMMI Track 2] Planning, [CMMI Level 3] RD SP 2.1
When

After the input requirements are available.

Entry Criteria

User Scenarios Complete:
User scenarios have been created, reviewed, and approved.

Quality of Service Requirements Complete:
The quality of service requirements have been created, reviewed, and approved.

Domain Model Complete:
The domain model has been created, reviewed, and approved.

Exit Criteria

Safety Requirements Baselined:
The safety requirements are reviewed, approved, and baselined.

Is RequiredYes

Steps

  1. Analyze Input Requirements:

    Analyze the scenarios, quality of service requirements, and any industry-specific regulations for input requirements specific to security.
  2. Draft Safety Requirements:

    Create a draft of the safety requirements from initial input.
  3. Review Safety Requirements:

    Review the draft safety requirements. This review should include an assessment of preparedness for any regulatory audits. Update the requirements based on feedback.
  4. Baseline Requirements:

    Baseline the reviewed and approved safety requirements for the project. This baseline is used in change management and revising project estimates during replanning.

Inputs and Outputs

WorkProductInputOutputAllowable States
RequirementNew

Predecessors

TypeNameDependency Type
Define Security RequirementsFinish-Start

Successors

TypeNameDependency Type
Define Operational RequirementsFinish-Start

Last modified at 12/19/2007 10:37 AM  by Administrator