Sys ML AP 233 Mapping Status Report to SE

Sys. ML/AP 233 Mapping Status Report to SE DSIG David Price Allison Feeney June 2009

AP 233 is a data exchange standard Any SE Tool Request Database Response References for added semantics AP 233 Data File Ontology Classes and Individual Database

Workshop 1 : Structures • First Sys. ML/AP 233 mapping workshop held Jan 31, 2009 under INCOSE MDSD • “Structures” was the topic • Produced Venn diagram of overlaps to help with scoping (see next) • Produced basic mapping, issues, example diagrams • Identified next steps

Workshop 2 : Activity • Sys. ML/AP 233 mapping workshop held Mar 22, 2009 under OMG SE DSIG • “Activity” was the topic • Produced basic mapping, issues – Decided not to work Sequence Diagrams • Issues with relationship to Activity Diagrams • Used examples from tutorial and spec

Actions from Workshops 1 & 2 Finish examples and create sample AP 233 files based on diagrams Offline mapping activity (i. e. straightforward) Sys. ML Value Property/Units mapping Revisit early State Machine mapping Text Requirements mapping Constraint Blocks/Parametrics (opaque constraints)

Progress Since March OMG • Requirements mapping – Created simple example – Produced basic mapping • Value Property mapping – Basic mapping – identified AP 233 issue – Awaiting Units from Sys. ML 1. 2 RTF • Produced proof-of-concept converter – Text Requirements, Allocations, Trace, – Blocks, Composition, Satisfy

Sys. ML/AP 233 Data Overlaps AP 233 Classification Lifecycle Stages System Structures/Blocks Eng Config Mgmt V&V Organizations Schedule Sys. ML Activities Allocations Text-based Requirements Change Management Function Models Approvals, Security, Status Requirements Management Property-based Requirements Issue Management Risk Management Diagrams Parametrics Views and Viewpoints State Machines Property & Units Model Organization Interfaces/Ports & Flows

Example 5 Flow Ports

Example 5 : Flow

Blocks Mapping Sys. ML AP 233 Block System View Definition → System Version → System Composition Association Assembly Component Relationship relating two System View Definitions Generalization View Definition Relationship + Classification('Generalization') Part/Part Definition View Definition Relationship Nested Part Component Upper Level Identification Multiplicity Next Assembly Usage. quantity Connector Interface Connection Port/Port Definition Interface Connector Delegation Port Hierarchical Interface Connector

Example 5 AP 233 Flow SVD, SV, S Domain NAU Interface Connection c in: CA out: CA ICO power. In SVD, SV, S Computer CULI ? ? house. Power NAU House HIC Interface Connection ICO SVD, SV, S Plug ICO outlet SVD, SV, S CULI r NAU Reference: CA p NAU HIC NAU h Power ICO SVD, SV, S Receptacle SVD, SV, S

Sys. ML Block as AP 233

Activity Example

Activity Mapping Sys. ML AP 233 Activity Task Step Action, Call Behavior Action Task Step, Task Step Hierarchy Object Nodes Task IO Control Nodes Multidecision element, Concurrent element Object Flows Task IO Relationships Control Flows Structured Task Element subtypes Activity Parameter Task IO Activity Partition Group

Requirements Example

Requirements Mapping Sys. ML AP 233 Requirement View Definition → Requirement Version → Requirement Composition Requirement Collection Relationship Allocate View Definition Relationship + Classification(‘Allocate') Satisfy Requirement_satisfied_by Refine, Copy, Derive Requirement_view_definition_relationship + Classification(‘Copy’, ‘Refine’, ‘Derive’) Trace Tracing Relationship Text Requirement View Definition ← Single Property Is Definition → Property Representation → String Representation Item

Resulting AP 233 File

Value Property Mapping Sys. ML AP 233 Property not an association end, with type, owned by Block : Assigned_property → System_view_definition Type of Property Assigned_property ← Property_value_representation → Representation and Representation Item Value specification Any_number_value ← Value_with_unit → Unit

Next Steps • Third Workshop Friday of this week – “Interim Delivery” Review • Sept 2009 OMG Final Delivery – Proposed additional annex content for Sys. ML 1. 3 RTF – Demonstrations • Support Model Interchange/NIST Plug-fest – The next rounds are looking at profiles – AP 233 validation support in-work • Feb 2010 INCOSE 2010 International Workshop – Report and demonstrations

Other Project Threads • AP 233 for Change Management of Sys. ML/UML – Link the PLM capabilities in AP 233 to the Sys. ML Metamodel • AP 233 -based ontology for reasoning over SE data • Systems Engineering Web services as extensions to OMG PLM/OASIS PLCS services

AP 233 Engineering Change V 1 V 2 V 3 Sys. ML Systems Structure and Behavior Requirements

Example Use Case Company Systems Repository Sys. ML User Requirements (AP 233) Requirements (OWL DL) DL Reasoner S-satisfies-R (AP 233) S-sub. Class-R (OWL DL) Systems (OWL DL)

NIST Project Summary • Significant progress – on formal mapping of Sys. ML and AP 233 – in harvesting AP 233 into “OMG MDA environment” • OMG standard for ISO EXPRESS language • Still to do – AP 233 Change Management of Sys. ML – Systems Engineering Services – AP 233 Ontology work

Conclusions • Mappings – Structures and Requirements map well – Activities mapping has issues – Property has one issue when no value and Unit awaiting 1. 2 – Constraint Blocks to be done • Project is “proof-of-concept” – Not all of Sys. ML/AP 233 mapping can be completed given current project resources/timescales

Communications INCOSE Webinar last week (72 people) wiki. omg. org Sys. ML Portal Sys. ML-AP 233 Mapping area sysml-ap 233@omg. org Email list OMG Model Interchange team supporting NIST SE Plug-Fest TIIWG Connect site has lots of AP 233 -related information (e. g. usage scenarios) www. ap 233. org