NMSG-085 Status Report - SISO Discussion Forums

Download Report

Transcript NMSG-085 Status Report - SISO Discussion Forums

MSG-085 2RS Common Interest Group
SINEX OVERVIEW
April 11th 2013
MSG-085 2RS CIG
Slide 1
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.
MSG-085 2RS CIG
Slide 2
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.
MSG-085 2RS CIG
Slide 3
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.
MSG-085 2RS CIG
Slide 4
SINEX Approach
SINEX
Requirements
C-BML
Phase 1
MSDL V1
C2LG
Specification
SINEX MODEL
SINEX XML
Schemas
MSG-085 2RS CIG
Doc Gen
JSON X-Form
SINEX
HLA-FOM
XSD X-Form
HLA X-Form
OWL X-Form
SINEX OWL
Ontology
Modules
SINEX
Documentation
Slide 5
Who are the SINEX Stakeholders ?
There are two basic groups of SINEX Stakeholders:
1. End-user / Client
• Procurement Agencies
• Operational Users
2. 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.
MSG-085 2RS CIG
Slide 6
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.
MSG-085 2RS CIG
Slide 7
Defining the SINEX Model Using UML
MSG-085 2RS CIG
Slide 8
MIM Production Chain
MODEL REVISIONS
TOOLS
REQUIREMENTS & CHANGE PROPOSALS
MSG-085 2RS CIG
Slide 9
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
CP Editor can view an existing
model and construct sets of
“Change Proposals” or CPs.
MIP Change
Proposal
Editor
(CP Editor)
Requirements
MIM V1.1
Change
Proposal
MIM V1.2
Change
Proposal
MSG-085 2RS CIG
MIM V1.3
Change
Proposal
Slide 10
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIM
V1.1
MIP Change
CP Processor applies
CP to
Proposal
existing model and
generates
Editor
Editor)
revised UML(CPmodel.
Requirements
MIP Change
Proposal
Processor
(CP Processor)
MIM V1.1
Change
Proposal
MSG-085 2RS CIG
MIM V1.2
Change
Proposal
MIM V1.3
Change
Proposal
Slide 11
MIM Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
MIM V1.1
XML
Schemas
MIM
V1.1
MIP Change
MIP Change
Proposalgenerate
TransformProposal
Tools automatically
Editor
Processor
other required
model
representations,
(CP Editor)
(CP Processor)
such as XML Schema Description (XSD)
documents
Requirements
MIP
UML → XML
Transform Tool
MIM V1.2
Change
Proposal
MIM V1.1
Change
Proposal
MSG-085 2RS CIG
MIM V1.3
Change
Proposal
Slide 12
MIM Production Chain
C2IEDM
JC3IEDM
MIP Change
Proposal
Editor
(CP Editor)
Requirements
MIM
V1.0
MIM V1.1
XML
Schemas
MIM
V1.1
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML
Transform Tool
MIM V1.2
Change
Proposal
MIM V1.1
Change
Proposal
MSG-085 2RS CIG
MIM V1.3
Change
Proposal
Slide 13
MIM-based SINEX Production Chain
C2IEDM
JC3IEDM
MIM
V1.0
SINEX V1.0
XML
Schemas
SINEX
V1.0
MIP Change
MIP Change
MIM Tools have
been modified to MIP
Proposal
Proposal
UML → XML
support
SINEX
Editor
Processor developmentTransform Tool
(CP Editor)
(CP
Processor)
requirements
SINEX
Requirements
SINEX V1.1
Change
Proposal
SINEX V1.0
Model
Definition
MSG-085 2RS CIG
SINEX V1.2
Change
Proposal
Slide 14
MIM-based SINEX Production Chain
C2IEDM
JC3IEDM
MIP Change
Proposal
Editor
(CP Editor)
SINEX
Requirements
MIM
V1.0
SINEX V1.0
XML
Schemas
SINEX
V1.0
MIP Change
Proposal
Processor
(CP Processor)
MIP
UML → XML
Transform Tool
SINEX V1.1
Change
Proposal
SINEX V1.0
Change
Proposal
MSG-085 2RS CIG
SINEX V1.2
Change
Proposal
Slide 15
Current SINEX Capability
SINEX
Requirements
C-BML
Phase 1
MSDL V1
C2LG
Specification
SINEX MODEL
SINEX XML
Schemas
MSG-085 2RS CIG
Doc Gen
JSON X-Form
SINEX
HLA-FOM
XSD X-Form
HLA X-Form
OWL X-Form
SINEX OWL
Ontology
Modules
SINEX
Documentation
Slide 16
SINEX/MIM Tools Screenshots (1/2)
1
1.
2
2.
3.
3
4
4.
Start with MIM foundation classes
Delete / Add / Modify as Required
Use an automated, repeatable process [to generate model]
Maintain a model, but generate schemas
3
2
SINEX
Model
Definition
V1.0
SINEX
Model
V1.0
MSG-085 2RS CIG
Slide 17
1
1.
2.2
3.3
4.4
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
4
3
SINEX V1.0
XML
Schemas
SINEX
Model
V1.0
MSG-085 2RS CIG
Slide 18
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
SISO Phase 1
and CIG Inputs
CONSTITUENTS (5Ws)
ADDITIONAL VOCABULARY & METADATA
CIEM
BASE TYPES
MIP Information Model (MIM)
MSG-085 2RS CIG
Slide 19
SINEX Requirements Traceability
SINEX
MSG-085 2RS CIG
Requirements
???
Slide 20
SINEX Requirements Traceability
• Collect and refine requirements
• Build model in layers
• Maintain links between model elements & requirements
Requirements
MSG-085 2RS CIG
Slide 21
A DSEEP Overlay for C2-Simulation Federations
MSG-085 2RS CIG
Slide 22
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 C2Simulation 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.
MSG-085 2RS CIG
Slide 23
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.
MSG-085 2RS CIG
Slide 24
DSEEP as an Iterative Vee-Model
The SISO DSEEP Process can be expressed as an Iterative Vee-Model
MSG-085 2RS CIG
Slide 25
A C2-Simulation DSEEP Overlay
A similar Vee-Model can be outlined for a:
DSEEP C2-Simulation Federation Overlay
MSG-085 2RS CIG
Slide 26
A C2-Simulation DSEEP Overlay
SINEX
Documentation
SINEX
XML Schema
MSG-085 2RS CIG
Slide 27
A C2-Simulation DSEEP Overlay
SINEX
Documentation
SINEX
XML Schema
XML Schema
Extensions
?
C2SIM
Federation
Requirements
Extensions
required
As per C2SIM Federation Requirements, SINEX Model
Extensions are created using the SINEX approach, if needed.
MSG-085 2RS CIG
Slide 28
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.
MSG-085 2RS CIG
Slide 29
Questions ???
MSG-085 2RS CIG
Slide 30