Content deleted Content added
repair |
m ISBNs (Build KE) |
||
Line 1:
[[
Meta-process modeling supports the effort of creating flexible [[process model]]s. The purpose of process models is to document and communicate processes and to enhance the reuse of processes. Thus, processes can be better taught and executed. Results of using meta-process models are an increased productivity of process engineers and an improved quality of the models they produce.<ref name="Rolland 1998" />
Line 5:
== Overview ==
Meta-process modeling focuses on and supports the process of constructing [[process model]]s. Its main concern is to improve process models and to make them evolve, which in turn, will support the development of systems.<ref name="Rolland 1998">{{cite book | chapter=A Comprehensive View of Process Engineering | title=Proceedings of the 10th International Conference on Advanced Information Systems Engineering table of contents | pages =1–24 | year= 1998 |isbn=3-540-64556-X | author= Colette Rolland
|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=
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" />
Line 21:
The assembly technique is based on the idea of a process repository from which process components can be selected. Rolland 1998 <ref name="Rolland 1998" /> lists two selection strategies:
#Promoting a ''global'' analysis of the project on hand based on contingency criteria (Example Van Slooten 1996<ref name="Van Slooten 1996">{{cite book |author=K. Van Slooten, B. Hodes|chapter= Characterising IS development project |title=[[IFIP WG 8.1]] Conf. on Method Engineering|publisher= Chapman and Hall |pages= 29–44|year= 1996 | ___location=London | isbn=0-412-79750-X }}</ref>)
#Using the notion of descriptors <ref name="Antonellis 1991">V. De Antonellis, B. Pernici, P. Samarati. F-ORM METHOD: A methodology for reusing specifications. In Object Oriented Approach in Information Systems. Van Assche F., Moulin B., [[C Rolland]] (eds), North Holland, 1991</ref> as a means to describe process chunks. This eases the retrieval of components meeting the requirements of the user / matching with the situation at hand.<ref name="Rolland 1996b">{{
chapter = A proposal for context-specific method engineering | title = Proceedings of the IFIP TC8, WG8.1/8.2 working conference on method engineering on Method engineering : principles of method construction and tool support | year = 1996 |isbn = 0-412-79750-X |pages = 191–208 | publisher = Chapman & Hall | ___location = London }}</ref>
(Example Plihon 1995<ref name="Plihon 1995">{{cite journal | author=V. Plihon, [[C. Rolland]] |title= Modelling Ways-of-Working |journal= Proc 7th Int. Conf. on Advanced Information Systems Engineering (CAISE) |publisher= Springer Verlag |year= 1995 |doi=10.1007/3-540-59498-1 | pages=126–139 | url= http://www.springerlink.com/content/f62651046x8q0j24/ }}</ref> in NATURE (<ref name="NATURE" />) and repository of scenario based approaches accessible on Internet in the CREWS project <ref name="CREWS">[http://sunsite.informatik.rwth-aachen.de/CREWS CREWS project homepage (Cooperative Requirements Engineering With Scenarios)]</ref><ref name="Rolland 1998b">{{cite journal| author=[[C. Rolland]], C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans | title= A proposal for a scenario classification framework | journal=Requirements Engineering Journal| volume= 3 | issue=1| pages=23 | year= 1998 | doi=10.1007/BF02802919 |url=http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.30.5360&rep=rep1&type=pdf}}</ref>)
Line 45:
* [[Petri nets]] in EPOS <ref name="Jacherri 1992" /> and SPADE <ref name="Bandinelli 1993">{{cite journal | chapter = Process Modeling in-the-large with SLANG (1993) | author= S. Bandinelli, A. Fugetta, S. Grigoli | title= Proc. of the 2nd Int. Conf. on Software Process | ___location= Berlin |year= 1993 |pages=75–93 | url = http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.31.9650 }}</ref>
* Rule based paradigm in MERLIN <ref name="Emmerich 1991">W. Emmerich, G. Junkermann, W Schafer, MERLIN : knowledge-based process modeling, Proc. of the First European Workshop on Software Process Modeling, Milan, Italy, 1991.</ref>
* ALF <ref name="Benali 1989">{{
* Marvel <ref name="Kaiser 1988">{{cite journal | author=G. E. Kaiser, et al. |year=1988 | title=Database Support for Knowledge-Based Engineering Environments | journal=IEEE Expert | volume=3 |issue=2 | pages=18–32 | doi=10.1109/64.2102}}</ref>
* EPOS <ref name="Jacherri 1992" />
Line 65:
Besides the CREWS-L’Ecritoire approach, the multi-model view has served as a basis for representing <ref name="Rolland 1999" />:
:(a) the three other requirements engineering approaches developed within the CREWS project, Real World Scenes approach,<ref name="Haumer 1998">{{cite journal | doi=10.1109/32.738338 | title=Requirements elicitation and validation with real world scenes | year=1998 | last1=Haumer | first1=P. | last2=Pohl | first2=K. | last3=Weidenhaupt | first3=K. | journal=IEEE Transactions on Software Engineering | volume=24 | pages=1036 | issue=12}})</ref> SAVRE approach for scenario exceptions discovery,<ref name="Sutcliffe 1998">{{cite journal | doi=10.1109/32.738340 | title=Supporting scenario-based requirements engineering | year=1998 | last1=Sutcliffe | first1=A.G. | last2=Maiden | first2=N.A.M. | last3=Minocha | first3=S. | last4=Manuel | first4=D. | journal=IEEE Transactions on Software Engineering | volume=24 | pages=1072 | issue=12}}</ref> and the scenario animation approach <ref name="Dubois 1998">{{
:(b) for integrating approaches<ref name="Ralyté 1999">{{cite book |author=J. Ralyté, C. Rolland, V. Plihon |chapter= Method enhancement by scenario based techniques | title=Proceedings of the 11th conference on advanced information systems engineering, Heidelberg, Germany |date=June 1999 |isbn=3-540-66157-3 |pages=103–118 |publisher=Springer-Verlag |___location=London |url=http://portal.acm.org/citation.cfm?id=646087.679900#}}</ref> one with the other and with the OOSE approach <ref name="Jacobson 1992">{{cite book|isbn=
Furthermore, the CREWS-L’Ecritoire utilizes [[Process Model]]s and [[Meta-Process Model]]s in order to achieve flexibility for the situation at hand. The approach is based on the notion of a labelled graph of intentions and strategies called a ''map'' as well as its associated ''guidelines''.<ref name="Rolland 1999" /> Together, map (process model) and the guidelines form the method.
Line 76:
The map of the CREWS-L’Ecritoire method looks as follow:
[[
The map consists of goals / ''intentions'' (marked with ovals) which are connected by ''strategies'' (symbolized through arrows). An ''intention'' is a goal, an objective that the application engineer has in mind at a given point of time. A ''strategy'' is an approach, a manner to achieve an intention. The connection of two goals with a strategy is also called ''section''.<ref name="Rolland 1999" />
Line 89:
* ''Intention Achievement Guidelines (IAG)'' aim at supporting the application engineer in the achievement of an intention according to a strategy, are concerned with the tactics to implement these strategies, might offer several tactics, and thus may contain alternative operational ways to fulfil the intention.
[[
[[
[[
In our case, the following guidelines – which correspond with the map displayed above – need to be defined:
Line 125:
In the multi-model view as presented in the paper of C. Rolland, the meta-process (the instance of the meta-process model) is “a process for the generation of a path from the map and its instantaneous enactment for the application at hand.” <ref name="Rolland 1999" /> While the meta-process model can be represented in many different ways, a map was chosen again as a means to do so. It is not to be mixed up with the map for the process model as presented above.
[[
[[Colette Rolland]] describes the meta-model as follow <ref name="Rolland 1999" />:
| |||