DI-SAFT-82493

Software Level of Rigor Safety Report (SLORSR)

Provides a comprehensive accounting of all Level of Rigor (LOR) related work per MIL-STD-882E(C1) paragraph 4.4.

Approval DateJuly 15, 2025

AMSC NumberF10585

Preparing Activity40 (AFMC/SE)

Project NumberSAFT-2025-011

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

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

Supersedes

—

DI-SAFT-80102DI-SAFT-80105

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Software Level of Rigor Safety Report (SLORSR) is a comprehensive accounting of all Level of Rigor (LOR) related work per MIL-STD-882E(C1) paragraph 4.4.

This Data Item Description (DID) contains the content and format preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

a. This DID is related to DI-SAFT-80102, Safety Assessment Report (SAR); and DI-SAFT-80105 System Safety Program Progress Report (SSPPR).

(Copies of these DIDs are available online at https://quicksearch.dla.mil.)

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.

2FormatThe SLORSR shall be in the contractor's format.

3ContentThe SLORSR shall include the following information:

3.1IntroductionState, in narrative form, the purpose of the SLORSR.

3.2OverviewA brief overview of the software architecture and its roles within the system.

3.2.1The program's definition of what a Unit of Software is(e.g. Computer Software Configuration Item (CSCI), Computer Software Component (CSC), Computer Software Unit (CSU); this definition is to be used in all documentation required by this DID).

3.2.2Information needed to properly characterize how software is partitioned into the units of software as documented within the SLORSR.

3.3SwCI/LOR DeterminationThe rationale supporting how the Software Criticality Index (SwCI)/LOR was derived for each Unit of Software.

3.3.1For each unit of software, list the Software Control Category (SCC)per MIL-STD-882E(C1) Table IV with the accompanying supporting rationale applicable to the SCC.

3.3.2For each unit of software, the rationale behind determining the worst potential Severityper MIL-STD-882E(C1) Table I for the unit of software. Several hazards may involve the same unit of software, the most severe Severity; the most severe Severity is used.

3.3.3For each unit of software, list the derived Software Criticality Index (SwCI)per MIL-STD-882E(C1) Table V and the accompanying tier of Level of Rigor (LOR).

3.4LOR Activities

3.4.1Describe each LOR Activity for each LOR Tier(corresponding to SwCI Tier).

3.4.2Provide LOR artifacts correlated to each LOR activity for each Unit of Software.

3.5LOR Activity Status

3.5.1Define the timeline when MIL-STD-882E(C1) Table VI will be queried.Typical program timelines may include prior to Preliminary Design Review (PDR), prior to Critical Design Review (CDR), prior to formal testing, prior to fielding, and periodically during sustainment.

3.5.2For each unit of software, provide status of MIL-STD-882E(C1) Table VI questions for each LOR activity.

3.5.3For each LOR Tier's Activity:

3.5.3.1Annotate what is left to be defined.

3.5.3.2Annotate Government Management (PM) decision to expend additional resources to define LOR activity or to obtain Risk Acceptance Authority's formal acceptance for the unspecified LOR Tier (if any).If unavailable, highlight the need for a decision to be made.

3.5.4Summarize applicable LOR task activities.

3.5.4.1For each unit of software for each LOR task activity, provide or cite the reference to all program artifacts required to show compliance with the LOR task activity.Provide partial artifacts if available.

3.5.4.2Annotate specifically what is incomplete with the LOR criteria.

3.5.4.3Annotate Government PM decision to expend additional resources to define the LOR activity or obtain Risk Acceptance Authority's formal acceptance for the incomplete LOR activity.If unavailable, highlight the need for a decision to be made.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

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