DISCLAIMER — NOT LEGAL ADVICE: This FAQ provides illustrative technical guidance and sample requirements for Model-Based Systems Engineering (MBSE) project deliverables. It does not constitute legal advice or establish an attorney-client relationship. Before incorporating these provisions into a contract, Statement of Work (SOW), or Contract Data Requirements List (CDRL), obtain review from qualified engineering, acquisition, and legal professionals. Tailor all requirements to the project's scope, applicable standards, and contractual order of precedence.
Specify what the project must deliver, which standards each deliverable must satisfy, which editable and human-readable formats must be supplied, and how the customer will verify acceptance. Require an integrated, configuration-controlled System Architecture Model (SAM) as the principal engineering work product, together with model-derived specifications, reusable model libraries, standards-conformance evidence, and quality reports. SysML diagrams alone are not sufficient evidence of a complete architecture model.
The example requirements below are written in CDRL-style language. “Shall” denotes a proposed mandatory obligation; all requirements must be tailored and incorporated into the governing contract before they become binding.
The Contractor shall submit the following configuration-controlled work products for the approved System-of-Interest (SoI). The contract shall identify which conditional deliverables are required and establish the delivery milestone, revision frequency, responsible authority, and acceptance criteria for each CDRL.
| CDRL | Project deliverable | Minimum delivery formats |
|---|---|---|
| A001 | System Architecture Model (SAM) | Native editable model/repository (e.g., Cameo/MagicDraw/CATIA Magic .mdzip/.mdxml; Sparx Enterprise Architect .qea/.qeax, or legacy .eap/.eapx); separately approved standards-based exchange (e.g., applicable SysML v1 XMI) |
| A002 | System Architecture Views and Viewpoint Definitions | PDF, HTML; linked to A001 |
| A003 | Model-Based System Requirements Specification (SRS) | PDF, HTML, DOCX |
| A004 | Model-Based System Design Specification (SDS) | PDF, HTML, DOCX |
| A005 | Model-Based Interface Control Documents (ICDs) | PDF, HTML, DOCX |
| A006 | System Architecture, System Analysis, and Design Pattern Libraries | Native editable model libraries (e.g., Cameo/MagicDraw/CATIA Magic .mdzip/.mdxml; Sparx Enterprise Architect .qea/.qeax or approved repository/package exports); pattern documentation in PDF or HTML; applicable XMI exchange files |
| A007 | Applicable Standards and Conformance Matrix | PDF, CSV or XLSX |
| A008 | Enterprise Architecture Framework (EAF) Conformance Matrix | PDF, CSV or XLSX |
| A009 | Requirements Traceability and Verification Coverage Reports | PDF, CSV or XLSX |
| A010 | Model Validation and Architecture Quality Report | PDF; machine-readable findings where available |
| A011 | Model Configuration and Dependency Manifest | PDF plus CSV, JSON, or equivalent |
| A012 | Model Interoperability Demonstration Report | PDF; exchange test artifacts |
| A013 | Change Impact Analysis Report | PDF, CSV or XLSX |
| A014 | Simulation, Parametric Analysis, and Trade Study Results (when required) | PDF, CSV; native analysis files where applicable |
Deliverable rule: Each document and report shall identify its source model baseline, generation or export date, applicable standards, revision, and unresolved exceptions. Native model and library files shall remain editable and inspectable by authorized customer personnel in the agreed tool environment.
2.1 Standards Baseline. The Contractor shall establish and deliver A007 — Applicable Standards and Conformance Matrix, identifying each contractually applicable standard, exact edition, relevant clauses, affected CDRLs, conformance evidence, approved tailoring, and deviations. A standard is mandatory only to the extent explicitly incorporated into the contract.
2.2 Core Architecture and Systems Engineering Standards. The Contractor shall implement the applicable requirements and practices of:
| Standard or reference | Required deliverable application |
|---|---|
| ISO/IEC/IEEE 42010:2022 | Architecture descriptions, stakeholder concerns, viewpoints, views, and architecture-description consistency in A001–A002 |
| ISO/IEC/IEEE 42020:2019 | Defined architecture processes, governance, and work-product management evidenced in A001 and A007 |
| ISO/IEC/IEEE 42030:2019 | Architecture evaluation criteria, results, rationale, and dispositions reported in A010 |
| ISO/IEC/IEEE 15288 (contract-selected edition) | Applicable system life-cycle processes and work-product traceability across A001–A014 |
| OMG SysML v1.7 or SysML v2.0 (one explicitly selected baseline) | Modeling-language conformance of A001 and A006 |
| OMG UML and XMI, where applicable | SysML v1 metamodel foundation and agreed exchange requirements for A001/A006 |
| OMG KerML and applicable SysML v2 specifications | SysML v2 foundation, model representation, and access/interchange capabilities where applicable |
| INCOSE Systems Engineering Handbook and SEBoK | Documented engineering best practices, when adopted or contractually incorporated |
| Applicable functional-safety, cybersecurity, reliability, and domain standards | Domain-specific system, analysis, interface, and verification deliverables |
2.3 Evidence, Not Assertions. A supplier's use of a modeling tool labeled “SysML-compliant” shall not, by itself, establish conformance. The Contractor shall deliver objective evidence, including validated model elements, standards-to-deliverable mappings, architecture evaluations, review records, and approved exceptions.
2.4 SysML Version. The contract shall explicitly choose SysML v1.7 or SysML v2.0, identify the supported tool/version, and specify exchange and compatibility requirements. SysML v2 shall not be assumed to be a backward-compatible replacement for SysML v1.
3.1 Selected Framework. The Contractor shall conform to the contractually selected EAF—such as DoDAF, OMG UAF, or TOGAF, as applicable to the project. Where no EAF is mandated, the Contractor shall propose an architecture-description framework aligned with ISO/IEC/IEEE 42010 for Customer approval.
3.2 Framework Deliverables. A002 shall provide the required stakeholder-oriented views and documented viewpoints. A008 shall map each applicable EAF obligation to SAM packages, model elements, views, and review or validation evidence.
3.3 Cross-View Consistency. A001, A002, and A008 shall collectively demonstrate consistency among operational, functional, logical, physical, and other contractually required architecture descriptions. The Contractor shall identify and resolve unsupported allocations, contradictory definitions, missing interfaces, and inconsistent relationships.
3.4 Scope of Conformance. Conformance shall be evaluated against the framework's contractually selected viewpoints and information products, not against an arbitrary diagram count or every artifact in the entire framework.
4.1 Primary Engineering Deliverable — A001. The Contractor shall deliver an integrated, editable, configuration-controlled SAM covering the approved SoI and the architecture decomposition necessary for its intended engineering decisions.
4.2 Minimum Model Content. A001 shall contain or maintain controlled references to:
4.3 Model Semantics. For a SysML v1.7 baseline, the Contractor shall apply appropriate BDD, IBD, Activity, Sequence, State Machine, Requirement, and Parametric models. For SysML v2, equivalent requirements shall be implemented using the selected v2 language constructs. Diagram appearance shall not substitute for semantically linked model information.
4.4 Model Authority. A001 shall be authoritative only for the engineering data expressly designated as model-authoritative by the approved configuration management plan. Conflicts with contracts, approved requirements baselines, regulatory obligations, or other controlled records shall be resolved through the designated configuration authority.
5.1 Mandatory Pattern Libraries — A006. The Contractor shall document, maintain, deliver, and demonstrably apply reusable, configuration-controlled libraries in three categories:
5.2 Pattern Documentation. Each pattern shall identify its unique ID, purpose, applicability, governing standards, stakeholder concerns, assumptions, required model elements and relationships, constraints, permitted variations, usage instructions, validation checks, example application, responsible owner, and version.
5.3 Required Application. The Contractor shall apply approved patterns where applicable to A001 and its derived deliverables. Each representative pattern use shall be traceable to the library pattern and version. Nonapplication or modification of a required pattern shall be justified and approved.
5.4 Model Integrity. A006 shall contain reusable model definitions and templates, not merely drawings or descriptive text. The Contractor shall demonstrate that pattern reuse improves repeatability, model consistency, architecture integrity, and cross-view quality through documented checks and representative examples.
6.1 System Requirements Specification — A003. The Contractor shall deliver a human-readable SRS generated from, or maintained in controlled synchronization with, the approved requirements baseline. Each requirement shall have an identifier, statement, source, classification, status, verification method, and relevant relationships. Requirements traceability and coverage shall be documented in A009.
6.2 System Design Specification — A004. The Contractor shall deliver an SDS describing approved system/component decomposition, static structures, functional behavior, dynamic behavior, interfaces, constraints, and required allocations. The SDS shall be consistent with A001 and applicable A006 patterns.
6.3 Interface Control Documents — A005. The Contractor shall deliver ICDs defining controlled interfaces, their connected participants, exchanged items and data, types, units, ranges, protocols, timing, physical characteristics, error handling, and verification criteria, as applicable. Interface definitions shall be linked to corresponding elements in A001.
6.4 Document Generation. A003–A005 shall be generated from or maintained in controlled synchronization with their authoritative model data. The Contractor shall document the generation procedure and any externally maintained authoritative sources; undocumented manual discrepancies shall not be permitted.
7.1 Native Editable Formats. A001 and A006 shall include native editable model projects or repository deliverables, applicable profiles, model libraries, validation rules, resources, and instructions necessary to open, inspect, and maintain the work products in the contractually approved modeling environment. Nonexclusive examples include:
.mdzip and/or .mdxml native project files, as supported by the selected product and version, with required dependencies..qea or .qeax native file-based repositories; .eap or .eapx only where a compatible legacy environment is specifically approved. For server-hosted repositories, an agreed repository backup, migration package, or other restorable editable delivery shall be supplied rather than merely a connection shortcut.The Contractor shall identify the supplied native formats, modeling-tool versions, required licenses or access arrangements, and dependencies. The examples above are illustrative and shall not mandate or favor a particular modeling-tool vendor.
7.2 Standards-Based Exchange. In addition to native editable deliverables, the Contractor shall provide the contractually specified standards-based model exchange representation where applicable:
.xmi or agreed XML extension) conforming to the agreed UML/SysML metamodel and XMI versions, together with required profiles and libraries. Both Cameo/MagicDraw/CATIA Magic and Sparx Enterprise Architect support XMI-based model exchange subject to tool-specific options and interoperability limitations.Vendor-specific exchange formats (including Enterprise Architect Native XML/XEA exports) may be delivered in addition to, but shall not be labeled substitutes for, contractually required standards-based interchange. Neither XMI nor any native-format export shall be assumed to preserve all diagrams, profiles, tool-specific metadata, or repository configuration without an agreed import or round-trip demonstration.
7.3 Interoperability Acceptance — A012. The Contractor shall demonstrate successful exchange or access of a representative model subset, including agreed elements, relationships, properties, types, and libraries. Known losses and unsupported constructs shall be documented. An export file alone shall not establish interoperability.
7.4 Human-Readable and Tabular Formats. A002–A005 shall be delivered in the formats shown in the CDRL matrix. Compliance matrices, coverage reports, and quality reports shall be supplied in the tabular or machine-readable formats indicated, enabling independent review and analysis.
7.5 Consistent Configuration. All delivery representations shall reference the applicable approved baseline, version, and tool dependencies. Divergence among formats shall be documented and resolved under configuration control.
8.1 Acceptance Evidence — A007–A014. The Contractor shall deliver objective evidence appropriate to each contracted work product, including standards-conformance matrices, EAF mappings, model-validation findings, traceability reports, architecture evaluations, pattern-reuse demonstrations, and interoperability test results.
8.2 Model Quality. A010 shall report results of checks for language conformance, referential integrity, structural and behavioral consistency, interface compatibility, cross-view consistency, required pattern use, and model organization. Critical unresolved inconsistencies shall be corrected or formally dispositioned before acceptance.
8.3 Coverage. A009 shall report required requirements satisfaction, allocation, verification, and interface coverage against contractually approved thresholds; omissions and exceptions shall be explicitly identified.
8.4 Independent Inspection. The Customer shall be able to inspect underlying editable model elements, their relationships, pattern libraries, and the associated conformance and validation evidence using the agreed access environment and data rights.
8.5 Acceptance Basis. A deliverable shall be accepted only when its required content, standards conformance, approved EAF coverage, applicable pattern-library use, formats, configuration records, and objective acceptance criteria have been demonstrated. The number or visual quality of SysML diagrams is not a substitute for engineering integrity.
The Customer shall specify the selected SysML version; applicable ISO/IEC/IEEE, OMG, and EAF standards with exact editions; required architecture viewpoints; the scope and acceptance rules of the three reusable pattern libraries; the native and exchange tool environments; required CDRLs and delivery dates; quality thresholds; data rights; review authority; and the contractual order of precedence.
Bottom line: A successful MBSE/SysML procurement specifies deliverable content + standards conformance + reusable patterns + required formats + measurable acceptance evidence. The goal is an inspectable, interoperable, maintainable engineering architecture—not a collection of attractive but disconnected diagrams.
This FAQ is an engineering and procurement-planning example, not legal advice or a complete contractual instrument.

Made in RapidWeaver