Content deleted Content added
Citation bot (talk | contribs) m [344]+: issue. |
Disambiguated: meta model → Metamodeling, Code generation → Automatic programming |
||
Line 7:
|publisher=Springer-Verlag |___location= London }}</ref> This is important due to the fact that “[[Process (engineering)|processes]] change with time and so do the [[Process Model]]s underlying them. Thus, new processes and models may have to be built and existing ones improved”.<ref name="Rolland 1998" /> “The focus has been to increase the level of formality of process models in order to make possible their enactment in process-centred software environments”.<ref name="Rolland 1999">{{cite journal | doi=10.1007/s007660050018 | title=A Multi-Model View of Process Modelling | year=1999 | last1=Rolland | first1=C. | last2=Prakash | first2=N. | last3=Benjamen | first3=A. | journal=Requirements Engineering | volume=4 |issue=4| page=169}}</ref> referring to:<ref name="Finkelstein 1994">{{cite book | editor=A. Finkelstein, J. Kramer, B. Nuseibeh |title=Software process modelling and technology. |publisher=Wiley |___location=New York | year=1994 | isbn=0471952060}}</ref>
A process meta-model is a [[Metamodeling|meta model]], “a description at the type level of a process model. A process model is, thus, an instantiation of a process meta-model. [..] A meta-model can be instantiated several times in order to define various process models. A process meta-model is at the meta-type level with respect to a process.” <ref name="Rolland 1998" />
<br style="clear:both" /> There exist standards for several domains:
* [[Software Engineering]]
Line 281:
== See also ==
{{multicol}}
* [[Automatic programming]]
* [[Class-Responsibility-Collaboration card]] (CRC)
* [[Data mapping]]
* [[Data transformation]]
|