Meta-process modeling: Difference between revisions

Revision as of 15:56, 5 January 2011

Revision as of 06:38, 5 April 2011

Line 35:

#It forces to look for and introduce, in the process meta-model, generic solutions to problems and this makes the derived process models inherit the solution characteristics.

“The instantiation technique has been used, for example, in NATURE,<ref name="NATURE">[http://www-i5.informatik.rwth-aachen.de/PROJEKTE/NATURE/nature.html NATURE project homepage (Novel Approaches to Theories Underlying Requirements Engineering)]</ref> Rolland 1993,<ref name="Rolland 1993" /> Rolland 1994,<ref name="Rolland 1994">{{cite journal|author=[[C. Rolland]] |title= A Contextual Approach to modeling the Requirements Engineering Process |journal=6th Intl. Conf. on Software Engineering and Knowledge Engineering |___location= Jurmala, Latvia |date= June, 1994 | url = http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.52.9389 }}</ref> and Rolland 1996.<ref name="Rolland 1996">{{cite journal | doi = 10.1109/ICRE.1996.491442 | title = Using generic method chunks to generate process models fragments | year = 1996 | last1 = Rolland | first1 = C. | last2 = Plihon | first2 = V. | pages = 173 | journal=Second International Conference on Requirements Engineering (ICRE'96)}}</ref>. The process engineer must define the instances of contexts and relationships that comprise the process model of interest.”<ref name="Rolland 1998" />

=== Language ===

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}}</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 48:

* 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" />

* Triggers in ADELE <ref name="Belkhatir 1994">{{cite journal | author=N. Belkhatir, W. L. Melo |year=1994 | title=Supporting Software Development Processes in Adele2 |journal=Computer Journal |volume= 37 |issue=7 | pages=621–628 | doi=10.1093/comjnl/37.7.621}}</ref> and MVP-L <ref name="Finkelstein 1994" />).

Languages are typically related to process programs whereas instantiation techniques have been used to construct process scripts.<ref name="Rolland 1998" />

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 }}</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}})</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}}</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>

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.

The main source of this explanation is the elaboration of [[Colette Rolland]] in .<ref name="Rolland 1999" />.

===Process model / Map===

Line 80:

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" />

A map “allows the application engineer to determine a path from Start intention to Stop intention. The map contains a finite number of paths, each of them prescribing a way to develop the product, i.e. each of them is a process model. Therefore the map is a multi-model. It embodies several process models, providing a multi-model view for modeling a class of processes. None of the finite set of models included in the map is recommended ‘a priori’. Instead the approach suggests a dynamic construction of the actual path by navigating in the map. In this sense the approach is sensitive to the specific situations as they arise in the process. The next intention and strategy to achieve it are selected dynamically by the application engineer among the several possible ones offered by the map. Furthermore, the approach is meant to allow the dynamic adjunction of a path in the map, i.e. adding a new strategy or a new section in the actual course of the process. In such a case guidelines that make available all choices open to handle a given situation are of great convenience. The map is associated to such guidelines” .<ref name="Rolland 1999" />.

=== 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 }}</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}}</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).

Line 284:

* [[Code generation]]

* [[Data mapping]]

* [[Data transformation]]

* [[Domain Specific Language]] (DSL)

* [[Domain-specific modeling]] (DSM)

* [[Eclipse (software)]]

* [[Generative programming]] (GP)

* [[Glossary of Unified Modeling Language terms]]

Line 303:

* [[Model Driven Engineering]] (MDE)

* [[Model Transformation Language]] (MTL)

* [[Model-based testing]] (MBT)

* [[Model-driven architecture]] (MDA)

* [[Modeling language]]

Line 309:

{{multicol-break}}

* [[Object Constraint Language]] (OCL)

* [[Object-oriented analysis and design]] (OOAD)

* [[QVT|MOF Queries/Views/Transformations]] (QVT)

* [[Semantic spectrum]]

* [[Semantic translation]]

* [[Software factory]]

* [[Transformation language]] (TL)

Line 325:

{{reflist}}

{{DEFAULTSORT:Meta-Process Modeling}}

[[Category:Systems engineering]]

[[Category:Unified Modeling Language]]