Meta-modeling technique: Difference between revisions

Content deleted Content added
MDE (talk | contribs)
Cleaning and progressive transport Metamodel
MDE (talk | contribs)
applying the merge process of this article to metamodeling
Line 1:
{{mergeto|Meta-model}}
{{mergeto|Meta-modeling}}
 
== Examples of metamodeling approaches==
A '''metamodeling technique''' is an approach used to model activities and artifacts in a development process, using process-data diagrams. Saeki (2003) proposed the use of such a metamodeling technique for the purpose of attaching semantic information to the artifacts and for measuring their quality using this information. The modeling technique is adopted to reveal the relations between activities (the process) and artifacts (the data produced in the process). A process-data diagram consists of two integrated diagrams. The left-hand side of the diagram is based on a UML activity diagram, and the right-hand side of the diagram is based on a UML class diagram.
 
=== MetaProcess modeling ===
 
Metaprocess modeling is done by adapting the UML activity diagram. According to Booch, Rumbaugh and Jacobson (1999), an activity diagram is “a diagram that shows the flow from activity to activity; activity diagrams address the dynamic view of a system”. This diagram consists of activities and transitions. If necessary, activities can be divided into sub-activities. Transitions can be used to show the path from one activity to the next. A simple arrow depicts this. Four types of activities exist: unordered, sequential, concurrent and conditional activities.