1 / 15

SysML/AP233 Mapping Status Report to SE DSIG

SysML/AP233 Mapping Status Report to SE DSIG. David Price Allison Feeney March 2009. Classes and Individual. Ontology. AP233 is a data exchange standard. Any SE Tool. Request. Database. Database. Response. AP233 Data File. References for added semantics. Workshop 1 : Structures.

dlederman
Download Presentation

SysML/AP233 Mapping Status Report to SE DSIG

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 Report to SE DSIG David Price Allison Feeney March 2009

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

  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. 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. Mapping so far

  6. Example 5 Flow Ports

  7. Example 5 : Flow

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

  9. Workshop 1 Next Actions • 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)‏ • Next Workshop: Sunday at March OMG • Functional Model, Activities, Sequence Diagrams

  10. SysML Block as AP233

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

  12. Mapping so far

  13. Workshop 2 Next Actions • Complete workshop 1 actions • AP233 resources applied to UK MOD AP239/PLCS project, Mar 31 deadline but improving AP233 • Planning • June 2009 interim results workshop (OMG or INCOSE or NIST) • Sept 2009 final deliverables at OMG • Support Model Interchange/NIST Plug-fest

  14. Conclusions • Mappings • Structures mapped well • Activities mapping has some issues • Expect no major issues for Requirements and Properties • Project is “proof-of-concept” • Not all of SysML/AP233 mapping can be completed given current project resources/timescales

  15. Communications • http://www.omgwiki.org/OMGSysML/doku.php • SysML Portal • SysML-AP233 Mapping area • sysml-ap233@omg.org Email list

More Related