DI-SESS-82513

Software Process Audit

Specifies the format, content, and intended use for a Software Process Audit report documenting the contractor's software maintenance and development process under AS9115.

Approval DateFebruary 25, 2026

AMSC NumberN10618

Preparing ActivityAS

Project NumberSESS-2026-005

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Software Process Audit provides information about the software maintenance/development process as defined by AS9115 and associated documentation. This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract Contractual Engineering Task (CET).

Preparation Instructions

1Reference documentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2FormatContractor's format is acceptable.

3ContentThe following shall be included in the Software Audit Report:

3.1The Software Audit Report shall review/include the following

3.1.1Software PlanningMaintain a documented Software Development Plan (SDP) defining lifecycle processes, roles and responsibilities, risk management, and project deliverables.

3.1.2Requirements ManagementImplement a process for capturing, validating, and maintaining bidirectional traceability of software requirements through design, implementation, and test.

3.1.3Software Design and DevelopmentApply formal design methods and coding standards. Conduct peer reviews and maintain detailed design documentation for traceability and verification.

3.1.4Verification and ValidationDevelop and execute documented test plans and procedures. Ensure full traceability between requirements and verification results.

3.1.5Configuration ManagementEstablish a configuration management system to control software versions, tools, build environments, and baselines. Implement formal change control.

3.1.6Supplier ManagementIf subcontracting software development, flow down AS9115 requirements to suppliers and ensure appropriate oversight and verification.

3.1.7Software Quality AssuranceMaintain an independent software quality assurance function responsible for audits, compliance monitoring, and corrective action verification.

3.1.8Delivery and Post-DeliveryEnsure software deliveries are fully verified and compliant with contractual acceptance criteria. Provide plans for maintenance and support as applicable.

3.1.9Documentation and RecordsMaintain controlled documentation and records demonstrating compliance with AS9115 and project-specific software quality requirements.

3.1.10Integration with AS9100Ensure the software quality system aligns with and supports the Contractor's AS9100-certified quality management system.

3.1.11Include current audit/surveillance results, other relatedaudit/surveillance reports, corrective actions, and the upcoming surveillance audit/surveillance.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer