Meta-process modeling: Difference between revisions

Revision as of 06:38, 5 April 2011

Revision as of 00:15, 19 May 2011

Line 40:

Rolland 1998 <ref name="Rolland 1998" /> lists numerous languages for expressing process models used by the software engineering community:

* E3 <ref name="Finkelstein 1994" />

* Various Prolog dialects for EPOS,<ref name="Jacherri 1992">{{cite journal| author = Letizia Jaccheri and Jens-otto Larsen and Reidar Conradi | title = Software Process Modeling and Evolution in EPOS |journal = IEEE Transactions on Software Engineering | year = 1992 | volume = 19 | pages = 1145–1156 | url= http://www.idi.ntnu.no/grupper/su/publ/pdf/capri-final.pdf| doi = 10.1109/32.249660| issue = 12}}</ref> Oikos,<ref name="Ambriola 1991">V. Ambriola, M. L. Jaccheri, Definition and Enactment of Oikos software entities, Proc. of the First European Workshop on Software Process Modeling, Milan, Italy, 1991</ref> and PEACE <ref name="Finkelstein 1994" />

* PS-Algol for PWI <ref name="Finkelstein 1994" />)

as well as further computational paradigms:

Line 62:

==Example: “Multi-model view”==

[[Colette Rolland]] (1999)<ref name="Rolland 1999" /> provides an example of a meta-process model which utilizes the instantiation and assembly technique. In the paper the approach is called “Multi-model view” and was applied on the CREWS-L’Ecritoire method. The CREWS-L’Ecritoire method represents a methodical approach for [[Requirements Engineering]], “the part of the IS development that involves investigating problems and requirements of the users community and developing a specification of the future system, the so-called conceptual schema.”.<ref name="Rolland 1993" /><ref name="Hagelstein 1988">{{cite journal | doi=10.1016/0950-7051(88)90031-7 | title=Declarative approach to information systems requirements | year=1988 | last1=Hagelstein | first1=J | journal=Knowledge-Based Systems | volume=1 | pages=211 | issue=4 }}</ref><ref name="Dubois 1989">{{cite journal | author=E. Dubois, J. Hagelstein, A. Rifaut | title= Formal Requirements Engineering with ERAE | journal= Philips Journal Research | volume= 43 | issue= 4 | year = 1989}}</ref>

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">{{ cite journal | author = E. Dubois, P. Heymans | title= Scenario-based techniques for supporting the elaboration and the validation of formal requirements | journal= Requirement Eng J | year= 1998 | volume = 3 | issue = 3–4 | pages=202–218 | doi = 10.1007/s007660050005}}</ref>

:(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=0201544350 | url=http://books.google.com/?id=A6lQAAAAMAAJ | title=Object-oriented software engineering: a use case driven approach | first=Ivar | last=Jacobson | year=1992 | publisher=ACM Press}}</ref>

Line 83:

=== Guidelines ===

A guideline “helps in the operationalisation of the selected intention”;<ref name="Rolland 1999" /> it is “a set of indications on how to proceed to achieve an objective or perform an activity.”<ref name="RobertDict 1995">Le Petit Robert French Dictionary, Dictionnaires Le Robert, France, 1995</ref> The description of the guidelines is based on the NATURE project’s contextual approach <ref name="NATURE" /><ref name="Rolland 1995">{{cite journal | doi=10.1016/0306-4379(95)00018-Y | title=An approach for defining ways-of-working | year=1995 | last1=Rolland | first1=C | journal=Information Systems | volume=20 | pages=337 | issue=4 }}</ref><ref name="Grosz 1997">{{cite journal | author = G. Grosz, [[C. Rolland]], S. Schwer et al.. | title = Modelling and engineering the requirements engineering process: an overview of the NATURE approach | journal = Requirements Eng J | year = 1997 | volume = 2 | pages = 115–131 | doi = 10.1007/BF02802771 | issue = 3}}</ref> and its corresponding enactment mechanism.<ref name="Si-Said 1997"/>

Three types of guidelines can be distinguished:

* ''Intention Selection Guidelines (ISG)'' identify the set of intentions that can be achieved in the next step and selects the corresponding set of either IAGs (only one choice for an intention) or SSGs (several possible intentions).