Meta-modeling technique: Difference between revisions

Revision as of 07:21, 22 April 2006

Revision as of 07:21, 22 April 2006

Line 3:

The following discussion can be viewed as a detailed application of [[Meta-modeling|metamodeling]] techniques, related to [[Model Driven Engineering]]. In software engineering, data engineering and software engineering, the use of [[Model|models]] is more and more recommended. this should be contrasted with the classical code-based development techniques. A [[Model|model]] always conform to a unique [[Meta-model|metamodel]]. One of the currently most active branch of [[Model Driven Engineering]] is the approach named [[Model Driven Architecture]] proposed by [[OMG]].

OneA '''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 this meta-modeling 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 ==