sysml-ap233:mapping_between_sysml_and_ap233
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
sysml-ap233:mapping_between_sysml_and_ap233 [2009-06-26 18:39] afeeney |
sysml-ap233:mapping_between_sysml_and_ap233 [2010-07-21 07:31] pspiby |
||
|---|---|---|---|
| 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. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| ====== Workshops ====== | ====== Workshops ====== | ||
| Line 30: | Line 36: | ||
| == Mapping Review Workshop 06/09 == | == Mapping Review Workshop 06/09 == | ||
| - | A workshop is being held on Friday, June 26, 2009 at the San Jose, Costa Rica %%OMG%% Technical Meeting. | + | A workshop was being held on Friday, June 26, 2009 at the San Jose, Costa Rica %%OMG%% Technical Meeting. |
| Project status report June 23, 2009 to %%OMG%% SE DSIG is available in {{sysml-ap233:sysml-ap233-mapping-status-june-2009-omg.ppt|this presentation}}. | Project status report June 23, 2009 to %%OMG%% SE DSIG is available in {{sysml-ap233:sysml-ap233-mapping-status-june-2009-omg.ppt|this presentation}}. | ||
| + | |||
| + | 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 80: | Line 107: | ||
| ====== Interactions Mapping ====== | ====== Interactions Mapping ====== | ||
| Will be left for a future workshop -- complex will likely take most of a day | Will be left for a future workshop -- complex will likely take most of a day | ||
| - | ^ SysML ^ AP233 ^ | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| - | | | | | ||
| ====== State Machines Mapping ====== | ====== State Machines Mapping ====== | ||
| ^ SysML ^ AP233 ^ | ^ SysML ^ AP233 ^ | ||
| + | | State Machine, Region| Behaviour <- Behaviour_version <- Behaviour_view_definition + Classification ('StateMachine'), Classification ('Region') | | ||
| | State | State_definition (Behaviour) | | | State | State_definition (Behaviour) | | ||
| - | | FinalState, PseudoState | State_definition + Classification ('FinalState') | | + | | FinalState, PseudoState | State_definition + Classification ('FinalState'), Classification ( PseudostateKind value ) | |
| - | | | | | + | | State entry, exit, doActivity | Activity_method or Task <- Activity_method_assignment -> State_definition | |
| - | | | | | + | | State deferrable_trigger | Event <- Event_assignment -> State_definition | |
| - | | | | | + | | Transition | State_transition_definition | |
| - | | | | | + | | Transition trigger | Event <- Event_assignment -> State_transition_definition | |
| - | | | | | + | | Transition guard | Condition <- Condition_assignment -> State_transition_definition | |
| - | | | | | + | | Constraint | Text_expression <- Text_expression_Assignment -> State_transition_definition | |
| - | | | | | + | |
| ====== Use Cases Mapping ====== | ====== Use Cases Mapping ====== | ||
| Line 113: | Line 130: | ||
| | Subject | System (Same as block) | | | Subject | System (Same as block) | | ||
| | Extension Point | TBD | | | Extension Point | TBD | | ||
| + | |||
| Line 124: | Line 142: | ||
| | 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 | | ||
| Line 137: | Line 155: | ||
| | 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/10| MBSE/MDSD Report and Demo | PS| Complete | |
| - | | 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.txt · Last modified: 2010-07-21 07:58 by pspiby
Page Tools
