1. SysML/AP233 Mapping Status Report to SE DSIG David Price Allison Feeney June 2009

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

3. Workshop 1 : Structures First SysML/AP233 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

4. Workshop 2 : Activity SysML/AP233 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

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

6. Progress Since March OMG Requirements mapping –Created simple example –Produced basic mapping Value Property mapping –Basic mapping – identified AP233 issue –Awaiting Units from SysML 1.2 RTF Produced proof-of-concept converter –Text Requirements, Allocations, Trace, –Blocks, Composition, Satisfy

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

8. Example 5 Flow Ports

9. Example 5 : Flow

10. Blocks Mapping SysMLAP233 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

11. Example 5 AP233 Flow Computer SVD,SV,S p Plug SVD,SV,S NAU CULI ICO powerIn ICO HIC Domain SVD,SV,S c NAU ICO in:CAout:CA House SVD,SV,S h NAU r Receptacle SVD,SV,S NAU CULI outlet ICO HIC ICO Power SVD,SV,S housePower NAU Reference:CA Interface Connection Interface Connection ??

12. SysML Block as AP233

13. Activity Example

14. Activity Mapping SysMLAP233 ActivityTask Step Action, Call Behavior ActionTask Step, Task Step Hierarchy Object NodesTask IO Control NodesMultidecision element, Concurrent element Object FlowsTask IO Relationships Control FlowsStructured Task Element subtypes Activity ParameterTask IO Activity PartitionGroup

15. Requirements Example

16. Requirements Mapping SysMLAP233 Requirement 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 → Representation → String Representation Item

17. Resulting AP233 File

18. Value Property Mapping SysMLAP233 Property not an association end, with type, owned by Block 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

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

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

21. V1V2V3 Engineering Change Systems Structure and BehaviorRequirements AP233 SysML

22. Systems (OWL DL) SysML User Requirements (AP233) Company Systems Repository S-satisfies-R (AP233) S-subClass-R (OWL DL) DL Reasoner Requirements (OWL DL) Example Use Case

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

24. 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 SysML/AP233 mapping can be completed given current project resources/timescales

25. Communications INCOSE Webinar last week (72 people) wiki.omg.org  SysML Portal SysML-AP233 Mapping area  sysml-ap233@omg.org Email list sysml-ap233@omg.org OMG Model Interchange team supporting NIST SE Plug-Fest TIIWG Connect site has lots of AP233-related information (e.g. usage scenarios)‏ www.ap233.org