Scribd
Upload
591 views4 pages

Physical Configuration Audit Checklist

This checklist is used to conduct a software Physical Configuration Audit (PCA) for ISD mission software projects. The PCA verifies that the software configuration item matches the technical documentation. It is performed before formal delivery and the Functional Configuration Audit. The checklist includes questions to verify baseline documentation, that walkthroughs/inspections of the design and code were conducted, and that the delivered software matches the release documentation. The auditor indicates if the results satisfy requirements or list deficiencies.

Uploaded by

Petrr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
591 views4 pages

Physical Configuration Audit Checklist

This checklist is used to conduct a software Physical Configuration Audit (PCA) for ISD mission software projects. The PCA verifies that the software configuration item matches the technical documentation. It is performed before formal delivery and the Functional Configuration Audit. The checklist includes questions to verify baseline documentation, that walkthroughs/inspections of the design and code were conducted, and that the delivered software matches the release documentation. The auditor indicates if the results satisfy requirements or list deficiencies.

Uploaded by

Petrr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

ISD Physical Configuration Audit

Checklist

Number: 580-CK-036-01 Approved By: (signature)


Effective Date: August 10, 2005 Name: Joe Hennessy
Expiration Date: August 10, 2009 Title: Chief, ISD

Responsible Office: 580/Information Systems Division (ISD) Asset Type: Checklist


Title: ISD Physical Configuration Audit Checklist PAL Number: 3.1.1.4

Purpose This checklist is to be used when conducting a software Physical


Configuration Audit (PCA). A PCA verifies that a configuration item as built
conforms to the technical documentation that defines it. This audit is
generally performed prior to formal delivery of a product, and also prior to the
Functional Configuration Audit (FCA).

Scope This checklist is to be used for all ISD mission software projects, including
software projects that involve firmware.

Roles and Product Development Lead (PDL):


Responsibilities Responsible for ensuring that the PCA audit is conducted properly. Also
responsible for ensuring that all action items from this audit are tracked to
closure.

Independent Auditor:
Responsible for conducting the PCA.

NOTE: It is important that someone independent of the software system


being audited conduct the PCA. Software Quality personnel can either
lead the audit (as an external auditor) or participate in the audit with
representatives from Software Configuration Management (CM) and
Software Engineering.

Change History Version Date Description of Improvements


1.0 8/10/05 Initial version approved by CCB

ISD Physical Configuration Audit Checklist Page 1 July 26, 2005


Version: 1.0

Check the Process Asset Library at http://software.gsfc.nasa.gov/process.cfm to obtain the latest version.
NOTE: Words shown in blue underlined contain links to additional information.
Date(s) of Audit: ___________________________ Project: ____________________________
Independent Auditor(s): __________________________________________________________
Name and number of CI/Release examined: __________________________________________

Yes,
Findings and
Item # Audit Question No, Comments
Observations
N/A

PCA Baseline Documentation


Has the organization responsible for the
1 CI/CSCI provided the following prerequisite
data for the Product Baseline:
Software product specification for each
1a
CI/CSCI?
Software Release Letter and/or Version
1b
Description Document (VDD)?
1c Updated software design documentation?
1d Software Requirements Specification(s)?
1e Interface Requirements Specification(s)?
A listing of approved and outstanding
1f
changes against the CI/CSCI?
A list delineating any deviations/waivers
1g
against the configuration item?
Software Operations and/or Maintenance
1h
manuals?
Software User’s Manuals and/or User’s
1i
Guide?
For firmware items (if applicable),
identification of items to be accepted (by
1j nomenclature, Specification Id number, CI Id,
serial number, drawing & part number, code
id number)?

Baseline Audit Checklist


Has a walkthrough/inspection been
2
conducted on the design of each CSCI?
Has a walkthrough/inspection been
3
conducted on the code of each CSCI?
Have the action items resulting from
4
walkthroughs/ inspections been closed out?
ISD Physical Configuration Audit Checklist Page 2 July 26, 2005
Version: 1.0

Check the Process Asset Library at http://software.gsfc.nasa.gov/process.cfm to obtain the latest version.
NOTE: Words shown in blue underlined contain links to additional information.
Yes,
Findings and
Item # Audit Question No, Comments
Observations
N/A
Does the CI/CSCI delivery media conform to
5 the packaging/labeling requirements as
defined in the SMP/PP?
For firmware, are engineering change control
6
numbers unique?
For firmware, have the CIs been built in
7
accordance with the approved specifications?
Has the actual CI/CSCI delivery been
examined to ensure that every item specified
8
in the Release Letter and the VDD is
physically included in the delivery?
Is the Product Baseline of the deliverable
9 software system defined and complete?

Check one:
o Results reviewed satisfy the requirements and are accepted (see
attached comments).
o Results reviewed do not satisfy requirements (see attached
comments and list of deficiencies).
Approved by: Date:
_________________________________________________ ____________

ISD Physical Configuration Audit Checklist Page 3 July 26, 2005


Version: 1.0

Check the Process Asset Library at http://software.gsfc.nasa.gov/process.cfm to obtain the latest version.
NOTE: Words shown in blue underlined contain links to additional information.
Date(s) of Audit: __________________ Project: _____________________________________
Independent Auditor(s): __________________________________________________________
Name and number of CI/Release examined: __________________________________________

# Additional Comments from PCA audit

ISD Physical Configuration Audit Checklist Page 4 July 26, 2005


Version: 1.0

Check the Process Asset Library at http://software.gsfc.nasa.gov/process.cfm to obtain the latest version.
NOTE: Words shown in blue underlined contain links to additional information.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy