1 / 24

SysML/AP233 Mapping Status

SysML/AP233 Mapping Status. INCOSE IW 2010-02 MSDS Report Phil Spiby and Allison Feeney. Ontology. Classes and Individuals. AP233 is a data exchange standard. Any SE Tool. Request. Database. Database. Response. References for added semantics. AP233 Data File. AP233 Scope.

jfetzer
Download Presentation

SysML/AP233 Mapping Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SysML/AP233 Mapping Status INCOSE IW 2010-02 MSDS Report Phil Spiby and Allison Feeney

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

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

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

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

  6. 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

  7. 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

  8. 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

  9. 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”

  10. 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

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

  12. Structure Test Case

  13. 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

  14. Blocks in PLCS Tool

  15. Structure in PLCS Tool

  16. Requirements Test Case

  17. 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

  18. Requirements in PLCS Tool

  19. Requirement Name, Id and Text in PLCS Tool

  20. Stereotypes in PLM Tool (1)

  21. SubRequirements in PLCS Tool

  22. Requirement Tracing in PLCS Tool

  23. 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 2010

  24. Communications • wiki.omg.org • SysML Portal • SysML-AP233 Mapping area • sysml-ap233@omg.org Email list • 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

More Related