User Tools

Site Tools


sysml-ap233:mapping_between_sysml_and_ap233

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sysml-ap233:mapping_between_sysml_and_ap233 [2009-07-13 14:22]
afeeney
sysml-ap233:mapping_between_sysml_and_ap233 [2010-07-21 07:58] (current)
pspiby Added Packages and meta data mapping
Line 7: Line 7:
  
 The mappings are being produced in a series of Workshops with SysML and AP233 experts.  ​ The mappings are being produced in a series of Workshops with SysML and AP233 experts.  ​
 +
 +
 +
 +
  
  
Line 37: Line 41:
  
 The results of this workshop (i.e. the overview of the mappings, issues and actions) are documented in this wiki now. The results of this workshop (i.e. the overview of the mappings, issues and actions) are documented in this wiki now.
 +
 +
 +== Mapping review at INCOSE IW 2010 ==
 +A worksop was held on Monday, 8 February 2010 at the INCOSE IW held in Mesa Arizona USA.
 +
 +Project status report 8 February, 2010 to INCOSE MDSD is available in {{sysml-ap233:​incose-sysml-ap233-mapping-2010-02.ppt|this presentation}}.
 +
 +== SysML Model management including Mapping review at INCOSE IS 2010 ==
 +A workshop was held on Sunday, 11 July 2010 at trhe INCOSE IS held in Chicago, USA.
 +
 +A presentation on the use of AP233 to support Configuration/​change management of SysML models as presented at the meeting is available {{sysml-ap233:​ap233_based_cm_for_sysml.pptx|here}}.
 +
 +Files used in the demonstration are available.
 +
 +^ SysML file ^ AP233 file ^ Description ^
 +| {{sysml-ap233:​structuredemo.xmi|structuredemo.xmi}} | {{sysml-ap233:​structuredemo.xml|structuredemo.xml}} | Initial structure file |
 +| {{sysml-ap233:​reqmtdemo.xmi|reqmtdemo.xmi}} | {{sysml-ap233:​reqmtdemo.xml|reqmtdemo.xml}} | Requirement file that has a block in common with structure file |
 +| {{sysml-ap233:​structuredemo-new.xmi|structuredemo-new.xmi}} | {{sysml-ap233:​structuredemo-new.xml|structuredemo-new.xml}} | Updated structure file one block changed |
 +| N/A | TBD | Combined file giving history of structure and linked requirements |
  
 ====== Blocks Mapping ====== ====== Blocks Mapping ======
Line 107: Line 130:
 | Subject | System (Same as block) | | Subject | System (Same as block) |
 | Extension Point | TBD | | Extension Point | TBD |
- 
  
 ====== Requirements Mapping ====== ====== Requirements Mapping ======
Line 118: Line 140:
 | Copy, Derive | Requirement_view_definition_relationship + Classification (‘Copy’,​ ‘Refine'​) | | Copy, Derive | Requirement_view_definition_relationship + Classification (‘Copy’,​ ‘Refine'​) |
 | Trace | View_definition_relationship + Classification ('​Trace'​) | | Trace | View_definition_relationship + Classification ('​Trace'​) |
-| Trace between Requirements| Tracing_relationship ​(don't use this AP233 construct)|+| Trace between Requirements| Tracing_relationship |
 | Text | Requirement View Definition ← Single_property_is_definition → Property_representation → Representation → String_representation_item | | Text | Requirement View Definition ← Single_property_is_definition → Property_representation → Representation → String_representation_item |
 +
 +====== Packages and metadata Mapping ======
 +^ SysML      ^ AP233      ^
 +| Package | Collection_view_definition → Collection_version → Collection + Classification ('​Package'​) |
 +| Containment | Collection_membership |
 +| Model | Collection_view_definition → Collection_version → Collection + Classification ('​Model'​) |
 +| XMI file | Digital_file → Digital_document_definition → Document_version → Document |
 +| Model in file | Collection_assignment between Collection representing model and Digital_document_definition for the file | 
  
 ====== Issue Log ====== ====== Issue Log ======
Line 131: Line 161:
 | 07 | SysML Nested Parts require the use of AP233 Component Upper Level Identification to maintain the complete path/​context. |  |  | | 07 | SysML Nested Parts require the use of AP233 Component Upper Level Identification to maintain the complete path/​context. |  |  |
 | 08 | In STEP in order to have a unit and a property we must give it a value. ​ The link between value and property is value_with_unit which assigns the value. ​ Number is mandatory. |  |  | | 08 | In STEP in order to have a unit and a property we must give it a value. ​ The link between value and property is value_with_unit which assigns the value. ​ Number is mandatory. |  |  |
 +
  
 ====== Actions ====== ====== Actions ======
-^ Timeframe ​ ^ Action ​     ^ Assigned To ^ +^ Timeframe ​ ^ Action ​     ^ Assigned To ^ Status ​
-| 15 July 2009 | Rewrite of SysML 1.1 annex D.4 | | +| 15 July 2009 | Rewrite of SysML 1.1 annex D.4 | ABF | Complete ​
-| 15 July 2009 | Review '​Parsed Text' proposal from Michael Chonoles | | +| 15 July 2009 | Review '​Parsed Text' proposal from Michael Chonoles | DMP Complete ​
-| July 2009 | Develop compelling use case scenario to serve as narrative for INCOSE paper | |  +| San Antonio %%OMG%% 9/09 | SE DSIG/​MIWG/​ManTIS joint session baseline document for review and dry run demo | DMP| Complete ​
-| September 2009 | INCOSE IS paper submission due | +INCOSE IW 02/10MBSE/MDSD Report and Demo | PSComplete ​
-| San Antonio %%OMG%% 9/09 | SE DSIG/​MIWG/​ManTIS joint session baseline document for review and dry run demo | | +| INCOSE ​IS 07/10| MDSD Report and Demo | PS | Complete ​|
-Long Beach %%OMG%% 12/09 MIWG full, public demo    +
-| INCOSE ​IW 02/10| MBSE/MDSD Report and Demo |  |+
sysml-ap233/mapping_between_sysml_and_ap233.1247509332.txt.gz · Last modified: 2009-07-13 14:22 by afeeney