1 / 8

Some Explanations on JP-02 of CD2 MFI 10

Some Explanations on JP-02 of CD2 MFI 10. Masao OKABE Expert Contribution 2013/5/24 2013/5/28 r1. JP02 on CD2 MFI 10. Note Model <-contained_by-----contains-> Model_Element can be superseded by Model <-used_by-----uses-> Model_Element,

nelson
Download Presentation

Some Explanations on JP-02 of CD2 MFI 10

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. Some Explanations on JP-02 of CD2 MFI 10 Masao OKABE Expert Contribution 2013/5/24 2013/5/28 r1 Masao OKABE

  2. JP02 on CD2 MFI 10 Note • Model <-contained_by-----contains-> Model_Element can be superseded by Model <-used_by-----uses-> Model_Element, where the attribute “uses” of Model is inherited from Model_Element. used_by Modelling_Language Model_Element described_by uses describes should be Model Model contained_by describes contains described_by Model_Element Modelling_Language Masao OKABE

  3. Rationale of used_by Model_Element uses • It is a common characteristic to almost anything (including even an atom, except quaks?) that a thing can be decomposed to other things. • This is not a characteristic specific to a process. • So, an Model_Element that identifies an model element that represents somethings should be also able to be decomposed to other Model_Elements. Masao OKABE

  4. Rationale of • Given a universe of discourse (in a general sense, and not in a Common Logic sense), usually, there is one model that represents some aspect of the UoD. But, suppose that there is a model M1 for a UoD U1 and a model M2 for a UoD U2. Then, we can think about a consolidated UoD U3 := U1∪U2. We can treat M3:= M1∪M2 as one model for the UoD U3. • So, it is just a modeler's choice (or intention) what a model is. A more general (or fundamental) one is a model element, which represents somethings in the UoD. A model is just a model element that is chosen as a model based on a modeler’s intention. Model_Element Model Masao OKABE

  5. How it works • The point is that a Model can also be an aggregation of Model_Elements (or can use Model_Elements), by the reference “uses” inherited from Model_Element. used_by uses Model_Element (uses) (used_by) Model describes described_by Modelling_Language Masao OKABE

  6. Relation to MFI5 1 of 2 • Then, the metamodel of process model registration can be very naturally introduced as a specialization of this metamodel as follows; (used_by) used_by (uses) uses Process_Model_Element Model_Element (uses) (uses) (used_by) (used_by) Model Process_Model describes (describes) described_by (described_by) Modelling_Language Process_Modelling_Language Masao OKABE

  7. Relation to MFI5 2 of 2 • MFI5 does not need to introduce any structure between Process_ Model and Process_Element (i.e (1)) nor between Process and Process_Element (i.e.(2)). (1) can (and should) be superseded by (3). (2) can (and should) be superseded by (4). • Other parts may not need (3) or (4), then they need not use them, since their cardinalities can be zero. (4) < A part of CD5 MFI5> (used_by) 0..1 < A part of the proposal> 0..* (uses) Process_Model_Element Process_Model 0..* (uses) (1) (used_by) 0..1 (3) (2) Process_Model Process_ Element Process Masao OKABE

  8. Relation to MFI5Another Point • MFI5 provides the association between Process_Model and Process (i.e. (4) ) so that it can register the situation that a process (as a model element) is further decomposed (modeled) by another process model. • For example, say, a top level process model M consists of a process (as a process model element) P1 about manufacturing a product, and a process P2 about distributing the product. A mid level process model M1 further decomposes (models) a process P1. • But, MFI5 need not provide that capability (i.e. (4) is not necessary.), because in the proposed MFI 10, mapping is not between models but between model elements. < A part of CD5 MFI5> Process_Model (1) • So, a semantically equivalent mapping between a model element and a necessary), because in the proposed MFI10, mapping is not between models but model (as a specialization of a model element) can supersede the association (4). • That is, there should be a semantically equivalent mapping between the process P1 and the process model M1. (2) Process_ Element Process (4) Masao OKABE

More Related