bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Error formatting macro: alias: java.lang.NullPointerException
SWE-053 - Manage Requirements Changes
Unknown macro: {div3}

1. Requirements

3.1.2.1 The project shall collect and manage changes to the software requirements.

1.1 Notes">1.1 Notes

The project analyzes and documents changes to requirements for cost, technical, and schedule impacts.

1.2 Implementation Notes from Appendix D

NPR 7150.2 does not include any notes for this requirement.

1.3 Applicability Across Classes

Class

  A_SC 

A_NSC

  B_SC 

B_NSC

  C_SC 

C_NSC

  D_SC 

D_NSC

  E_SC 

E_NSC

     F      

     G      

     H      

Applicable?

   

   

   

   

   

   

   

    P(C)

   

    P(C)

   

   

   

Key:    A_SC = Class A Software, Safety Critical | A_NSC = Class A Software, Not Safety Critical | ... | - Applicable | - Not Applicable
X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

Unknown macro: {div3}

2. Rationale

$body
"The average project experiences about a twenty-five percent change in requirements after the requirements have been defined for the first system release, which causes at least a twenty-five percent schedule slip [23]. Several studies also have shown that volatility in requirements contribute to the inefficient production of low-quality software [11, 13]. Consequently, requirements should be managed using a defined configuration management process that uses change control boards and automated change control tools that manage each requirement as a separate configuration item [10, 27].1 Using a configuration management tool permits personnel to identify which requirements have been added, removed, or changed since the last baseline, who has made these changes, when they were made, and the reason for making them. In addition, by maintaining requirements in a configuration management tool, they can be traced to the artifacts that realize them."6   
$body

Changes to requirements can be an indicator of software instability or an unclear description of the end product.  Regardless of the reason, requirements changes often mean increased costs, longer schedules, and changes in the technical features of the software.  Changes in requirements can result in rework and can affect software safety.

Collecting, analyzing, and managing requirements changes allow a project to control those changes and measure their impact.  Requirements change management can also provide early insights into the impact of those changes to the overall project's budget and schedule, including the ability to plan how to address changes rather than simply reacting when a change is made.

Unknown macro: {div3}

3. Guidance

 

Per the NASA Software Safety Guidebook, "The actual process of making changes should be a structured, defined process. This process should describe how a proposed change is submitted, evaluated, decided upon, and incorporated into the requirements baseline. Usually a change control board, consisting of people from various disciplines and perspectives, will review potential changes and either approve or reject them. A requirements management tool can help manage the changes made to many individual requirements, maintain revision histories, and communicate changes to those affected by them.

Part of the change management process should be an evaluation of the impact the change will have on the system and other requirements. Traceability information is an important tool in this evaluation." 1

Per the NASA Systems Engineering Handbook, managing changes to requirements is part of an overall requirements management process. "The Requirements Management Process is used to:

  • Manage the product requirements identified, baselined, and used in the definition of the WBS model products during system design;
  • Provide bidirectional traceability back to the top WBS model requirements; and

Manage the changes to established requirement baselines over the life cycle of the system products."2

See SWE-052 for guidance on requirements traceability and SWE-080 for guidance on impact analysis, including cost, technical, and schedule impacts.

For contracted software development, the contract should specify the requirements management activities expected of the contractor (provider), including capturing requirements changes, managing requirements changes, analyzing those changes for cost, technical, and schedule impacts, and documentation of the analysis results.

Keep in mind that managing changes to requirements is an ongoing process that occurs throughout the project lifecycle and should be planned for during project planning activities.

Capture and manage the changes

Consider using configuration management tools, requirements management tools, or change request tools to capture changes to requirements.  Many of these tools will keep version histories and are able to provide reports on the changes. Some of those reports may be useful to management when analyzing the impact of the requirements changes on the project.

Regardless of the capture method, projects should collect a minimum set of data to describe the requested change.  See SWE-113 guidance for more information.

As part of managing requirements changes, the team should keep in mind the effect of "requirements creep" on software development, including its costs and complexity.  Those performing impact analyses or approving/disapproving requirements changes should carefully scrutinize requests to avoid approving enhancements not required to accomplish the project goals and objectives.

Analyze the changes for cost, technical, and schedule impacts

"Effective management of requirements changes requires a process that assesses the impact of the proposed changes prior to approval and implementation of the change. " (NASA Systems Engineering Handbook)2

Once change requests are documented, the team should analyze them for their effect on all parts of the software system as well as their effect on the overall system and project, as applicable to the level of change.  Typically, changes are reviewed by a Configuration Control Board (CCB) or other review board who can request or perform an impact analysis before determining how to disposition the change (see SWE-080).

When performing analysis of changes, look for impacts such as:

  • Impact to other parts of the software system (not just the immediate design or code where the change will occur): architecture, design, interfaces, concept of operations, higher and lower level requirements
  • Impact to other parts of the overall system (e.g., system requirements, interfaces, hardware)
  • Safety, reliability, performance impacts
  • Skills needed (e.g., special expertise, additional developers, consultants)
  • Rework effort (e.g., requirements specification, design, code, test, user manuals)
  • New effort (e.g., code development, documentation, test case development, software assurance)
  • Impact to stakeholders
  • Potential to introduce errors into the software
  • Criticality of affected software

Traceability matrices and tools are useful when determining the impact of a change, but the team should update the traceability information to keep it current as changes to the requirements occur (see SWE-052).  Other relevant items, from the NASA Systems Engineering Handbook, include:

  • Performance margins – "a list of key performance margins for the system and the current status of the margin... the propellant performance margin will provide the necessary propellant available versus the propellant necessary to complete the mission"
  • Configuration management top evaluators list – "appropriate persons [to evaluate] the changes and providing impacts to the change... changes need to be routed to the appropriate individuals to ensure that the change has had all impacts identified."
  • Risk system and threats list – "used to identify risks to the project and the cost, schedule, and technical aspects of the risk...A threats list is normally used to identify the costs associated with all the risks for the project."

The team should use the results of the impact assessment to determine the effect the change has on the project in terms of:

  • Cost including personnel and equipment costs
  • Schedule including new or revised design, development, testing, and documentation effort
  • Technical impacts to the function of the software and overall system

Document analysis results

Document and maintain with the project records the results of the impact analysis and any decisions based on that analysis.  Communicate the results to the appropriate stakeholders, i.e., project personnel who must implement approved changes, must update documentation related to those changes, must test those changes; system level personnel who must coordinate changes in response to this requirements change;  as well as those affected if a requested change is not approved for implementation, including stakeholders outside the development team.

Other tasks

In addition to the activities noted above, managing changes to requirements may also include the following:

  • Ensuring that relevant project plans are updated to reflect approved requirements changes
  • Ensuring change requests are created, assigned, and completed for work products affected by approved requirements changes, e.g., design documents, user manuals, interface specifications
  • Ensuring changed requirements and all related changed work products are verified and validated
  • Ensuring traceability documents are updated to reflect the requirements change

Ensuring that the rest of the project uses only the latest, updated project documents that reflect the requirements change

Consult Center Process Asset Libraries (PALs) for Center-specific guidance and resources related to the management of requirements changes.

Additional guidance related to the management of requirements changes may be found in the following related requirement in this handbook:

SWE-052:

Bidirectional Traceability(software requirements to higher level requirements)

SWE-080

Track & Evaluate Changes



Unknown macro: {div3}

4. Small Projects

add

Unknown macro: {div3}

5. Resources

  1. add
  2. add

5.1 Tools

add

Unknown macro: {div3}

6. Lessons Learned

add

  • No labels