SysML/AP233 Mapping Status INCOSE IW MSDS Report Phil Spiby and Allison Feeney 1

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

AP233 Scope 3 requirements text-based property-based breakdowns static structure PDM analysis trade study behaviour product structure system sub-system functional breakdown WBS verification & validation function-based issue config control security risk program management person & org state-based

SysML/AP233 Data Overlaps 4 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

Extensibility Enables Life Cycle Processes 5 Database Request Response Database AP233 Data File References for added semantics Taxonomy PLCS DOD classes

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 6

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 7

Workshop 3 : Requirements & Constraint Blocks SysML/AP233 mapping workshop held June 22, 2009 under OMG SE DSIG “Constraint Blocks” was a topic “Requirements” was a topic Produced basic mapping, issues 8

Progress since last INCOSE Final AP233 Draft International Standard released in ISO for ballot Previously produced “proof-of-concept SysML to AP233 converter” –But that's just one hand clapping Produced first demo : Scenario is “SysML Release to a Life Cycle Support Tool” 9

Demo : Release to PLSC Scenario is “SysML Release to a Life Cycle Support Tool” Steps are –SysML → AP233 –AP233 → PLCS format –Import PLCS into Share-A-space Life Cycle Support Tool 10

Demo : Example Usage 11 AP233-based Data Bus Failure Assessment relating Failures to Systems using System Data originating in SysML

Structure Test Case 12

SysML Block -> PLM Implemented Block -> Item classified as System and Block –Block name -> Item Id concatenation of all owners of Block Block structure -> Item instance in assembly Instance Id concatenation of all owners of Property 13

Blocks in PLCS Tool 14

Structure in PLCS Tool 15

Requirements Test Case 16

SysML Requirement -> PLM Implemented Requirement -> Requirement classified if stereotyped –Requirement name -> PLM name –Requirement Id -> PLM id –Requirement Text -> Requirement description Tracing Relationships – Traces From/To SubRequirement -> Requirement Relationship 17

Requirements in PLCS Tool 18

Requirement Name, Id and Text in PLCS Tool 19

Stereotypes in PLM Tool (1) 20

SubRequirements in PLCS Tool 21

Requirement Tracing in PLCS Tool 22

Conclusions Mappings –Structures, Requirements, Constraint Blocks map well Project is “proof-of-concept” –Not all of SysML/AP233 mapping can be completed given current project resources/timescales Potential for larger-scale demo at OMG March

Communications wiki.omg.org –SysML Portal –SysML-AP233 Mapping area list –OMG Model Interchange team supporting NIST SE Plug-Fest TIIWG Connect site has lots of AP233- related information (e.g. usage scenarios)‏ 24