1. MSG-085 2RS Common Interest Group SINEX OVERVIEW
April 11th 2013

2. MSG-085 2RS Common Interest Group
The NATO MSG-085 CIG has formed a Common Interest Group with the objective of proposing a set of recommendations for a structured approach and prototype production chain for the construction of a unified MSDL/C-BML Logical Data Model and derived XML schemas, OWL ontologies, HLA-FOM etc... One of the main objectives of this activity is to develop the means to automatically generate the derived standard products, such as XML Schemata, OWL Ontology Modules, HLA-FOM modules. Another main objective is to establish the means to capture, validate and track a set of stakeholder/operational requirements and derived technical requirements.

3. What is SINEX ? SINEX = Scenario INitialization and EXecution
SINEX is a requirements-based, operations-driven UML Model from which XSD schemas are generated.
SINEX is based on the Multilateral Interoperability Programme (MIP) products, including :
Block 4 MIP Information Model (MIM), provided as an UML model for foundation;
The MIP Change Proposal Process; and
The MIP Change Proposal Toolset.
The SINEX approach unifies the C-BML, MSDL standards.

4. Why do we need the SINEX Approach ?
It is important to define and manage the scope of the C-BML/MSDL standards in a traceable manner and one that is consistent with operational requirements.
It is critical that the C-BML/MSDL standards evolve in a timely fashion when faced with changing and emerging requirements.
The SINEX approach intends generates the derived products that constitute the standard in semi-automated or fully automated manner:
Requirements specifications, Documentation, XML Schemata, HLA FOM Modules, OWL Ontology modules, etc…
The SINEX approach is being proposed as a way forward for the SISO C-BML Phase 2 Drafting Activity.

5. SINEX OWL Ontology Modules
SINEX Approach
SINEX
Requirements
MSDL V1
C-BML
Phase 1
C2LG
Specification
SINEX MODEL
OWL X-Form
HLA X-Form
XSD X-Form
JSON X-Form
Doc Gen
SINEX OWL Ontology Modules
SINEX
HLA-FOM
SINEX XML Schemas
SINEX
Documentation

6. Who are the SINEX Stakeholders ?
There are two basic groups of SINEX Stakeholders:
End-user / Client
Procurement Agencies
Operational Users
Solution Provider
Program Manager
Software Developer
C2-Simulation Federation Architect
The first group will provide the operational/stakeholder requirements.
However, the C-BML/MSDL standard products that are the outputs of the SINEX approach are technical products intended for use by the second group of stakeholders.
Therefore, the validation of the SINEX products must include both groups.

7. Defining the SINEX Model*
(See 13S-SIW-002)
Provides a structured approach based on Systems Engineering Principles and Best Practices, and provides for:
Defining scope and managing requirements;
Verifying that technical specifications have been followed; and
Validating that the derived products meets stakeholder expectations.

8. Defining the SINEX Model Using UML

9. REQUIREMENTS & CHANGE PROPOSALS
MIM Production Chain
REQUIREMENTS & CHANGE PROPOSALS
TOOLS
MODEL REVISIONS

10. MIP Change Proposal Editor
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIP Change Proposal Editor
(CP Editor)
CP Editor can view an existing model and construct sets of “Change Proposals” or CPs.
MIM V1.1 Change Proposal
MIM V1.2 Change Proposal
MIM V1.3 Change Proposal
Requirements

11. MIP Change Proposal Editor
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIM
V1.1
CP Processor applies CP to existing model and generates revised UML model.
MIP Change Proposal Editor
(CP Editor)
MIP Change
Proposal
Processor
(CP Processor)
MIM V1.1 Change Proposal
MIM V1.2 Change Proposal
MIM V1.3 Change Proposal
Requirements

12. MIP Change Proposal Editor
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIM
V1.1
MIM V1.1
XML Schemas
MIP Change Proposal Editor
(CP Editor)
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML Transform Tool
Transform Tools automatically generate other required model representations, such as XML Schema Description (XSD) documents
MIM V1.1 Change Proposal
MIM V1.2 Change Proposal
MIM V1.3 Change Proposal
Requirements

13. MIP Change Proposal Editor
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIM
V1.1
MIM V1.1
XML Schemas
MIP Change Proposal Editor
(CP Editor)
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML Transform Tool
MIM V1.1 Change Proposal
MIM V1.2 Change Proposal
MIM V1.3 Change Proposal
Requirements

14. MIM-based SINEX Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
SINEX
V1.0
SINEX V1.0
XML Schemas
MIP Change Proposal Editor
(CP Editor)
MIM Tools have been modified to support SINEX development requirements
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML Transform Tool
SINEX V1.0 Model Definition
SINEX V1.1 Change Proposal
SINEX V1.2 Change Proposal
SINEX
Requirements

15. MIM-based SINEX Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
SINEX
V1.0
SINEX V1.0
XML Schemas
MIP Change Proposal Editor
(CP Editor)
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML Transform Tool
SINEX V1.0 Change Proposal
SINEX V1.1 Change Proposal
SINEX V1.2 Change Proposal
SINEX
Requirements

16. Current SINEX Capability
Requirements
MSDL V1
C-BML
Phase 1
C2LG
Specification
SINEX MODEL
OWL X-Form
HLA X-Form
XSD X-Form
JSON X-Form
Doc Gen
SINEX OWL Ontology Modules
SINEX
HLA-FOM
SINEX
Documentation
SINEX XML Schemas

17. SINEX/MIM Tools Screenshots (1/2)
Start with MIM foundation classes
Delete / Add / Modify as Required
Use an automated, repeatable process [to generate model]
Maintain a model, but generate schemas 1 2 3 4 2 3
SINEX
Model
V1.0
SINEX
Model Definition V1.0

18. SINEX/MIM Tools Screenshots (2/2)
Start with MIM foundation classes
Delete / Add / Modify as Required
Use an automated, repeatable process [to generate model]
Maintain a model, but generate schemas 1 2 3 4 3 4
SINEX V1.0
XML Schemas
SINEX
Model
V1.0

19. Proposed Model Structure (1/2)
Layered Structure, as per SISO C-BML Phase 1
Re-use MIM types as foundation
MESSAGES
(Common, Air, Land, Maritime)
MIEM
CONSTITUENTS (5Ws)
and CIG Inputs
SISO Phase 1
ADDITIONAL VOCABULARY & METADATA
CIEM
BASE TYPES
MIP Information Model (MIM)

20. SINEX Requirements Traceability
???

21. SINEX Requirements Traceability
Collect and refine requirements
Build model in layers
Maintain links between model elements & requirements
Requirements

22. A DSEEP Overlay for C2-Simulation Federations

23. Why a DSEEP Overlay for C2-SIM Federations ?
The SINEX approach produces the technical products that specify how to communicate information across a C2-Simulation federation. However, it does not specify how to define, develop and test a C2- Simulation Federation. SISO has defined the Distributed Simulation Engineering and Execution Process (DSEEP) for the purpose of developing simulation federations. As part of the SINEX activity, the development of a DSEEP C2-Simulation Federation Overlay could utilize SINEX derived products as inputs for this purpose.

24. DSEEP
The SISO DSEEP Process is based on Systems Engineering Principles.
It is an iterative process that links the various steps of the process and includes verification and validation.

25. DSEEP as an Iterative Vee-Model
The SISO DSEEP Process can be expressed as an Iterative Vee-Model

26. A C2-Simulation DSEEP Overlay
A similar Vee-Model can be outlined for a:
DSEEP C2-Simulation Federation Overlay

27. A C2-Simulation DSEEP Overlay
SINEX
Documentation
SINEX
XML Schema

28. A C2-Simulation DSEEP Overlay Federation Requirements
SINEX
Documentation
SINEX
XML Schema
C2SIM
Federation Requirements
XML Schema Extensions ?
Extensions
required
As per C2SIM Federation Requirements, SINEX Model Extensions are created using the SINEX approach, if needed.

29. Conclusions
MSG-085 has formed a Common Interest Group to develop a structured requirements-driven and operationally relevant approach for developing a unified MSDL/C-BML standard.
This approach leverages the latest MIP products while maintaining agility and freedom to use or change any or all elements from the MIP.
This approach includes the automatic generation of standard products such as XML Schemas, HLA-FOM Modules, OWL ontology modules, etc..
Initial work already has been done that shows the viability of this approach that already can produce quality XSD Schemas based on stakeholder requirements in a very short time.
The SINEX approach also calls for the definition of a DSEEP Overlay for C2-SIM Federations.

30. Questions ???

31. SCENARIO INITIALIZATON AND EXECUTION MODEL DEVELOPMENT PROCESS
Collect and Refine Common C2-SIM Federation Requirements
Validate Usability, Completeness and Correctness
Verify Consistency of Products with Requirements 1 6
Define SINEX Model Specification 2
Generate SINEX Model Derived Products 5
Generate SINEX Model 3 4

32. Distributed Simulation Engineering and Execution Process (DSEEP)
Analyse Data and Evaluate Results
Define Simulation Environment Objectives
Perform Conceptual Analysis
Design Simulation Environment
Develop Simulation Environment
Integrate and Test Simulation Environment
Execute Simulation 1 2 3 4 5 6 7

33. Distributed Simulation Engineering and Execution Process (DSEEP)
(Shown as an Iterative Vee-Model)
Analyse Data and Evaluate Results
Define Simulation Environment Objectives
Perform Conceptual Analysis
Execute Simulation 1 7 2 6
Design Simulation Environment
Integrate and Test Simulation Environment 3
Develop Simulation Environment 5 4

34. C2-SIMULATION FEDERATION DSEEP OVERLAY
Define C2-SIM FEDERATION Environment Objectives
Analyse Data and Evaluate Results
Perform Conceptual Analysis 1
Execute C2-SIM FEDERATION 7 2 6
Integrate and Test C2-SIM FEDERATION Environment
Design C2-SIM FEDERATION Environment 3
Develop C2-SIM FEDERATION Environment 5 4