Comment:
Migration of unmigrated content due to installation of a new plugin
Tabsetup
0
1. The Requirement
1
2. Rationale
2
3. Guidance
3
4. Small Projects
4
5. Resources
5
6. Lessons Learned
6
7. Software Assurance
Div
id
tabs-1
1. Requirements
Excerpt
5.1.6 The project manager shall prepare and maintain records of the configuration status of software configuration items.
1.1 Notes
NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.
1.2 History
Expand
title
Click here to view the history of this requirement: SWE-083 History
Include Page
SITE:SWE-083 History
SITE:SWE-083 History
1.3 Applicability Across Classes
Applicable c
a
1
b
1
csc
1
c
1
d
1
dsc
1
e
0
f
1
g
0
h
0
Div
id
tabs-2
2. Rationale
Configuration status accounting (CSA) provides a way for a project to determine the content of configuration items (CIs) throughout the life cycle by capturing the status of submitted products such as data, models, scripts, code, and their associated change requests. It also allows project managers to monitor the developing software and know, based on status accounting reports, the contents of versions and releases of software.
Div
id
tabs-3
3. Guidance
Floatbox
"While the status information can be compiled by hand, it can be a tedious process. Many tools exist that provide an integrated configuration management system for all kinds of documents, including source code, and that can generate the status reports when requested. Some of these tools are free or low-priced." (NASA-GB-8719.13, NASA Software Safety Guidebook
Swerefn
refnum
276
)
Configuration status accounting generates and/or maintains records of the status and contents of the software throughout the life cycle. This function keeps track of the changes and the contents of versions and releases. Both the acquirer and the provider need to have a status accounting system.
When preparing status accounting records, consider the intended audience for those records and prepare them so that the receiver can obtain the information they need quickly and clearly. Consider the following information for CSA records:
Stages of incompleteness, correctness, and obsoleteness for each CI.
Identify each stage (e.g., draft, under review, ready for integration/delivery, operational, superseded).
Status of each CI (version, whether it is checked-out when it was last updated, who made the changes, and what was changed).
Status of change requests/problem reports.
The SMA (Safety and Mission Assurance) Technical Excellence Program (STEP) Level 2 Software Configuration Management and Data Management course
Swerefn
refnum
343
provide a set of questions useful for determining the type of status accounting data that is important to a project. If the answers are important, then the appropriate data needs to be collected and reported as part of CSA. A few of those questions are shown below:
Which versions of which products are installed at which sites?
What are the differences between versions?
What is the version history of each CI in each version of each product?
What documents support each version of each product?
What hardware configuration is required to operate a specific version of each product?
When will the next version of a given CI for a given product be available?
Which versions of which products are affected by a given configuration item revision?
Which revisions of which CIs make up a specific version of a product?
How many errors were reported and/or fixed in each version of each product in a given time period?
Which product versions are affected by a specific problem report?
When establishing status accounting activities, consider coordinating or applying the same concepts as part of data management activities. A basic description of data management is provided in SWE-079.
Projects with limited personnel and access to an automated CM tool that has reporting features may find that those features are helpful in fulfilling this requirement.
Div
id
tabs-5
5. Resources
5.1 References
refstable
Show If
group
confluence-users
Panel
titleColor
red
title
Visible to editors only
Enter the necessary modifications to be made in the table below:
SWEREFs to be added
SWEREFS to be deleted
SWEREFs called out in the text: 276, 343
SWEREFs NOT called out in text but listed as germane: 212, 216, 273
5.2 Tools
Include Page
Tools Table Statement
Tools Table Statement
Div
id
tabs-6
6. Lessons Learned
6.1 NASA Lessons Learned
No Lessons Learned have currently been identified for this requirement.
6.2 Other Lessons Learned
No other Lessons Learned have currently been identified for this requirement.
Div
id
tabs-7
7. Software Assurance
Excerpt Include
SWE-083 - Status Accounting
SWE-083 - Status Accounting
7.1 Tasking for Software Assurance
1. Confirm that the project maintains records of the configuration status of the configuration items.
7.2 Software Assurance Products
None at this time
Note
title
Objective Evidence
Software Problem reporting or defect tracking data
Software configuration management system data
Software assurance audit results of the change management processes.
Software version description document(s).
Expand
title
Definition of objective evidence
Include Page
SITE:Definition of Objective Evidence
SITE:Definition of Objective Evidence
7.3 Metrics
None identified at this time.
7.4 Guidance
The software engineering guidance in SWE-083 (this requirement) provides guidance on the types of configuration records that should be kept. Particularly important are the records of the items and their versions in each baseline, and the records of the configurations that are being delivered and described in the version description documents that accompany a delivery. Confirm that all the configuration management records are being kept and that they are accurate.
