DI-SESS-82549

Digital System Model Views

Defines the content and format requirements for a Digital Systems Model (DSM), an authoritative, structured, computer-interpretable representation of a system used to support engineering analysis, traceability, and lifecycle management.

Approval DateJuly 7, 2026

AMSC Number10682

Preparing ActivityAVN

Project NumberSESS-2026-028

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-SESS-82364

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This Data Item Description (DID) was adapted from DI-SESS-82364. While the two DIDs appear similar in nature, they differ in a few key areas. The purpose of adaptation was to make a DID that is more flexible and easier to tailor. The focus areas were: removing definition of model structure, removing reference to specific model languages, removing references to specific metamodel concepts, structuring to enable tailoring, removing planning material, and moving the focus from data content to data views.

This (DID) will be used by the Department of Defense to define the content and format of digital engineering artifacts delivered by a contractor in the form of a Digital Systems Model (DSM). A DSM is an authoritative, structured, computer-interpretable representation of a system, its behaviors, constraints, interfaces, requirements, and lifecycle data. It captures system information in a way that enables analysis, simulation, traceability, automation, and configuration management. This DID enables programs to receive authoritative digital models and associated data that support system understanding, decision-making, analysis, and lifecycle management.

This DID applies to any digital systems model, regardless of modeling language or tool. Information to be acquired will include data typically associated with a DSM including: structure (e.g., system architecture, components, allocations), behavior (e.g., sequences, state machines, activities), requirements and traceability, interfaces and data flows, parametrics and constraints, verification and validation relationships, associated properties, and configuration information.

This DID was created to clearly specify data item delivery requirements for system models while not being prescriptive as to modeling tools, modeling language, model organization, and modeling methodology/style. Specific model constructs are not enforced, though they are referenced as examples. This DID contains requirements for all possible DSM data views for any stage in the development lifecycle. Sections or views may be tailored (removed or clarified) for expected levels of detail for the appropriate lifecycle stage. 'View' as used in this document refers to the exposure of model data (e.g. diagrams, tables). Multiple view requirements may be satisfied by a singular view. Also, the format of this document does not dictate the format of the model structure.

This Data Item Description (DID) contains the format and content for the data product resulting from the work task described in the contract Statement of Work/Performance Work Statement.

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.

2Format

2.1The DSM shall be delivered in the fileor server format(s) as specified by contract.

2.2The DSM shall comply with the management andmodeling structure defined by the program in contractual documentation (e.g. Model Management Plans, system modeling templates, style guides, etc.).

3ContentThe DSM shall contain the following views:

3.1IdentificationThis view shall fully identify the system and elements covered by the DSM, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

3.2DSM OverviewThis view shall state the purpose of the system to which this document applies. It shall:

3.2.1Describe the general nature of the system (e.g. CONOPs)

3.2.2Summarize the history of system development, operation, and maintenance

3.2.3Identify the project sponsor, acquirer, user, developer, and support agencies

3.2.4Identify current and planned operating sites

3.2.5List other related documents (e.g. table)

3.3Data Rights and Security OverviewThis view shall summarize the purpose and contents of the DSM and shall describe any security or privacy considerations associated with its use.

3.4Referenced documentsThe DSM shall provide views containing the following as applicable:

3.4.1Document identifier

3.4.2Name

3.4.3Versions

3.4.4Date

3.5Assumptions and DecisionsThe DSM shall provide views containing the following as applicable:

3.5.1Design assumptions and decisions

3.5.2Assumptions and decisions about requirements

3.5.3Assumptions and decisions about verification and validation

3.5.4Assumptions and decisions about architecture

3.5.5Assumptions and decisions about use cases

3.5.6Assumptions and decisions about structural aspects

3.5.7Assumptions and decisions about behavioral aspects

3.5.8Assumptions and decisions about the model infrastructure including tool interfaces and data flows

3.5.9Assumptions and decisions about model integration requirements

3.5.10Assumptions and decisions about baseline deliverables (e.g. functional, allocated, and product baselines)

3.6Model InfrastructureThe DSM shall provide views containing the following as applicable:

3.6.1Modeling language(s) and version(s)

3.6.2External dependencies (e.g. used projects)

3.6.3Data integration and digital thread with externaltools, data flows, data dictionaries, databases, and other repositories to maintain data consistency.

3.6.4Interfaces (internally or externally) with external softwaresuch as Requirements Management Tools; Product Lifecycle Management tools; reliability, availability, maintainability, and testability tools and databases; risk, issue, and opportunity tools and databases; Model Based Simulation & Analysis (MBS&A) tools.

3.6.5Description of model navigation and views thatdepict model organization.

3.6.6Dashboards or visualizations to navigate or visualizethe model.

3.6.7Metamodels, profiles, and process diagrams supporting thedevelopment and connection of DSM content.

3.7RequirementsViews of Requirements shall be provided and contain the following information:

3.7.1Requirements DocumentationApplicable descriptions and rationale for requirements.

3.7.2Requirements ObjectsIdentification of requirements objects that include all applicable properties and types.

3.7.3Requirements RelationshipsRelationships between requirements and between requirements and other elements (e.g. refine, derive, copy) as defined by the program metamodel.

3.7.4Requirements ReferencesRelationships to reference architectures and external libraries.

3.8Use CasesViews of Use Cases shall be provided and contain the following information:

3.8.1Use Case DocumentationApplicable descriptions and rationale for use cases.

3.8.2Use Case ObjectsIdentification of use cases, their properties, and relationships between use cases (e.g. Include, Generalize) as defined by the program metamodel.

3.8.3Use Case RelationshipsRelationships between use cases and other model elements (e.g. between use cases and requirements) as defined by the program metamodel.

3.8.4Use Case ActorsIdentification and tracing of actors, including inanimate systems, to other model elements.

3.8.5Use Case BehaviorsIdentification of behavioral views which further expand on each use case (e.g. relations to sequence diagrams).

3.9Structural ViewsThe following views shall be provided:

3.9.1InterfacesViews of interfaces shall contain the following information:

3.9.1.1Interface DocumentationApplicable descriptions, purpose, and rationale for interfaces.

3.9.1.2Interface ObjectsIdentification of interfaces, as well as their types and properties, as defined by the program metamodel.

3.9.1.3Interface RelationshipsRelationships between interfaces (e.g. Connectors) and relations to other model elements (e.g. Dependency) as defined by the program metamodel. This includes relations to any parts of reference architecture or a library of standardized elements.

3.9.1.4Interface OwnerInterfaces provided by the System, Subsystem, Component, or Subcomponent.

3.9.1.5Interface ConsumersInterfaces used by the System, Subsystem, Component, or Subcomponent but provided by an external entity.

3.9.1.6Interface InformationDescription of all applicable parameters (e.g. information, energy, or material) being exchanged through the interface.

3.9.1.7Interface BehaviorsDescription of any methods or behaviors being invoked through the interface.

3.9.2Systems, Subsystems, Components, or Subcomponent RepresentationsViews of Systems, Subsystems, Components, or Subcomponent Representations shall contain the following:

3.9.2.1Systems, Subsystems, Components, or Subcomponent Representations DocumentationApplicable descriptions, purpose, and rationale.

3.9.2.2Systems, Subsystems, Components, or Subcomponent Representations ObjectsIdentification of applicable Systems, Subsystems, Components, or Subcomponents, as well as the description of all properties and types.

3.9.2.3Structural RepresentationStructural diagram showing compositional or aggregational relationships to other systems, subsystems, etc.

3.9.2.4Systems, Subsystems, Components, or Subcomponent RelationshipsRelations to other applicable model elements (e.g. Dependency, Allocate) as defined by the program metamodel. This includes relations to any parts of reference architecture or a library of standardized elements.

3.9.2.5Owned InterfacesInterfaces provided by the System, Subsystem, Component, or Subcomponent.

3.9.2.6Required InterfacesInterfaces used by the System, Subsystem, Component, or Subcomponent but provided by an external entity.

3.9.3Data Model ContentViews of Data Model Content shall contain the following:

3.9.3.1Data Model Entities (external data model elements)

3.9.3.1.1Data Entities DocumentationApplicable descriptions and rationale for entities.

3.9.3.1.2Data Entities ObjectsIdentification of entities, as well as their types and properties, as defined by the program metamodel.

3.9.3.1.3Data Entities RelationshipsRelationships between entities (e.g. Generalization) and relations to other model elements (e.g. Dependency) as defined by the program metamodel. This includes relations to any parts of reference architecture or a library of standardized elements.

3.9.3.2Data Model Associations (defined relationships between two external data model elements)

3.9.3.2.1Data Associations DocumentationApplicable descriptions and rationale for associations.

3.9.3.2.2Data Associations ObjectsIdentification of associations, as well as their types and properties, as defined by the program metamodel.

3.9.3.2.3Data Associations RelationshipsRelationships between associations (e.g. Generalization) and relations to other model elements (e.g. Dependency) as defined by the program metamodel. This includes relations to any parts of reference architecture or a library of standardized elements.

3.9.3.2.4Data Associations ParticipantsIdentification of all entities that participate in the association.

3.9.3.2.5Data Model RelationsRelations of data model content back to program specified data models (e.g. FACE SDM, a DSDM, or similar).

3.9.3.2.6Data Model Supporting ContentIdentification of all supporting data model content such as modeled measurement, axis, enumerations, etc.

3.9.4Data Model ViewsViews of Data Model Views shall contain the following:

3.9.4.1Data View DescriptionDescription of the data view (e.g. textual description of FACE query specification).

3.9.4.2Data View SpecificationSpecification of the data view to include selection of data and joining of data model entities and associations to expose the selected data.

3.9.4.3Data View RelationshipsRelationships to other data model views.

3.10Behavioral ContentViews of Behavioral Content shall contain the following information:

3.10.1Behavior DocumentationApplicable descriptions, purpose, and rationale for behaviors. Includes pre-conditions, post-conditions, alternatives, and error conditions.

3.10.2Behavior ObjectsIdentification of behaviors, as well as their types and properties, as defined by the program metamodel.

3.10.3Behavior StructureRelations between functions to show hierarchy (e.g. functional decomposition).

3.10.4Behavior RelationshipsRelationships between behaviors (e.g. Dependency) and relations to other model elements (e.g. Allocate) as defined by the program metamodel. This includes relations to any parts of reference architecture or a library of standardized elements.

3.10.5Behavior InteractionsDescription of interactions at each applicable level of the system hierarchy. Interactions include within the system and inputs/outputs to the system including external interfaces and human interactions.

3.10.6Behavior AlternativesDescription of interactions involved in error conditions and alternative paths in scenarios. Interactions include within the system and inputs/outputs to the system such as external interfaces and human interactions.

3.10.7Behavior StatesIdentification of state-based behavior for structural elements (e.g. control classes) including transitions between states.

3.10.8Behavior MessagesIdentification of message flows and the data, data type, format, and communication type (e.g. synchronous, asynchronous) for each message.

3.10.9Behavior ParticipantsMapping of structures to participants (e.g. Lifelines, Allocations, Swimlanes).

3.11Analysis ModelingViews of Analysis Modeling shall contain the following information:

3.11.1Analysis Modeling ParametersIdentification of all necessary parameters and data, including environmental factors, to accomplish analyses and calculations (e.g. response time, capacity, and schedulability) at any architectural level.

3.11.2Analysis Modeling RelationsRelations between all analysis parameters, to include outputs, and any elements within the model (e.g. relations from parameters to elements representing external analyses) as defined by the program metamodel.

3.12All ViewsAll Views (Diagrams, Tables, Matrices, etc.) shall contain the following information:

3.12.1View DocumentationName, purpose, view relationships to other elements, and any other applicable information for each view.

3.12.2View Data Rights and SecurityDescription of the data protection and access control requirements for the diagram.

3.12.3View Deviations and WaiversDescription of how view or view elements deviate from requirements, as well as rationale for noncompliance including waivers.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

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