Rolland, C., Achour, C.B., Cauvet, C., Ralyt, J., Sutcliffe, A., Maiden, N.A.M., Jarke, M., Haumer, P., Pohl, K., Dubois, E. & Heymans, P. (1996). A proposal for a scenario classification framework. CREWS Report 96-01.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....term Universe of Discourse with the same meaning given by Michael Jackson [3] to Application Domain. Loucopoulos [4] also uses both terms as synonyms. literature shows some degree of dispersion and contradiction in the use of scenarios. Recent work of the CREWS project confirms this observation [10,11]. This lack of precision of when and how scenarios should be used has spread to the engineers who are using these techniques in the field. Thus, most developers see scenario creation more as a craft than as an engineering task. Recent studies concerning the use of scenarios in industrial projects ....

....that scenarios must rely on natural language as a means of communication among stakeholders, in particular among clients users and requirements engineers. The strategy also relies on the idea of scenario evolution [14] starting from what Rolland et al. classified as organisational context [10], which aims at the broad picture of how the work gets done [10, p. 30] and what Jarke et al. 50] called environmental scenarios. Our scenarios are neither specifications nor requirements, they are auxiliary descriptions for the process of requirements definition. They provide a knowledge ....

[Article contains additional citation context not shown here]

Rolland C, Ben Achour C, Cauvet C, Ralyte J, Sutcliffe A, Maiden M, Jarke M, Haumer P, Pohl K, Dubois E, Heymans P. A proposal for a scenario classification framework. Requirements Eng 1998;3(1):23--47

....from RE can be combined with different areas of V V. Scenarios and use cases 1 (see e.g. 1, 2, 3, 4, 5] are gaining increased attention in RE, as means for eliciting, documenting and validating requirements. The exact definition of a scenario may vary depending on purpose, contents and form [6], but most definitions include the notion of a partial description of system usage as seen by its users. 1. The terms scenario and use case are sometimes used as synonyms and sometimes they are distinguished by defining a scenario to be a specific realisation of a use case. 2 Accepted at ....

Rolland, C., et. al. "A Proposal for a Scenario Classification Framework", Report of ESPRIT Project CREWS, no. 96-01, 1996. Available via e-mail: crewsrep@informatik.rwt-aachen.de.

....consistent prose, or formal content. Plurality is either 1 or multiple, similar to our multiplicity. Structure can be unstructured, semiformal, or formal. This dimension shares some common characteristics with our representation criterion. Rolland et al. suggest yet another set of criteria in [66], but without a real emphasis on specific needs of telecommunication systems. The next section does not attempt to provide a single scenario definition. Instead, it presents and compares different notations according to the selected criteria. 2.3 Selected Notations There are dozens of scenario ....

..... CREWS L Ecritoire. CREWS, the European ESPRIT project on Cooperative Requirements Engineering With Scenarios, proposes structured narrative text for capturing requirements scenarios, together with a set of style and content guidelines [14] This notation is supported by a tool called L Ecritoire [66] and, to some extent, by the SAVRE tool [58] In a way similar to Jacobson s use cases, the textual scenarios are divided into two main categories: normal scenarios and extension scenarios. The latter can be either normal (alternatives) or exceptional, depending on whether they allow to reach the ....

Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A.G., Maiden, N.A.M., Jarke, M., Haumer, P., Pohl, K., Dubois, E., and Heymas, P. (1998) "A proposal for a Scenario Classification Framework". Requirements Engineering Journal, 3(1), 23-47.

....in industrial practice, but comprehensive and expressive studies on the practical relevance of the techniques proposed by Page14 research are still rare. A good survey on scenario usage in system development is reported in [Widen98] and a framework for scenario classification is proposed in [Rolland98]. 2.1.1 The use of scenarios in existing software design methods Use of scenarios is gaining momentum among software methodologists and designers for supporting a number of different design methods. Some of these methods are summarized below: Object Modeling Technique (OMT) OMT [Rumbaugh91] ....

C. Rolland et al., "A proposal for scenario classification framework", Requirements Engineering Journal, Vol. 3, No. 1, Springer Verlag, 1998.

....expected benefits: 1. Modelling effort is reduced, as the same information is used for many purposes. 2. Traceability from requirements to test is promoted, which can be assumed to lead to less expensive maintenance. Both RE and V V have a variety of approaches proposed for usage modelling. In (Rolland et al. 1998) a survey of existing literature on scenarios and use cases in RE shows a great span of available methods. In (Jarke, et al. 1998) a survey of industrial practise revealed a great diversity in the ways that scenarios and use cases are applied. In (Graham, 1994) a number of different black box ....

Rolland, C., Ben Achour, C., Cauvet, C., Ralyt, J., Sutcliffe, A., Maiden, N., Jarke, M., Haumer, P., Pohl, K., Dubois, E., Heymans, P., "A Proposal for a Scenario Classification Framework", Requirements Engineering Journal, 3:1, 1998.

.... held at Dagstuhl Castle in early 1998, a general framework for integrating scenario based techniques in model based processes of continuous change management has been established [Jarke et al. 1998] Section 3: A comprehensive survey of the state of the art in research has been conducted [Rolland et al. 1998] and contrasted with the analysis of about 25 industrial projects in which use cases, scenarios, and scenes were used with varying degrees of success [Arnold et al. 1998, Weidenhaupt et al. 1998] Section 4: Two prototypical requirements engineering environments addressing key problems ....

....intermediate artefacts as the system itself. Scenarios are a particular kind of design artefact in the development world, intended to facilitate shared understanding of the target system, its interaction with users and subject domain, and its larger context. A review of the scenario literature [Rolland et al. 1998] showed that this framework also provides a good starting point for classifying scenario based approaches. Looking at the work activity as the subject domain and scenarios as one kind of development system artefact, we obtain four views (figure 4) CREWS 7 . What part of the work activity is ....

[Article contains additional citation context not shown here]

Rolland, C. et al. 1998. A proposal for a scenario classification framework.

....have agreed on. Requirements engineering process is a cooperative process in which stakeholders and requirement engineers have to understand each other when eliciting and understanding requirements and reconciling differences at technical and social level. This is explored in the CREWS project [24] which will develop, evaluate and demonstrate the applicability of methods and tools for cooperative scenario based requirements elicitation and validation [21] 23] Our purpose is to provide a single set of the main concepts for analysing cooperative work processes. In order to take into ....

ROLLAND, C., BEN ACHOUR, C., et.al., A proposal for a scenario classification framework, in: ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable I1: Initial integration workpackage (1997).

....approaches emphasise some description of the real world. Within the long term research ESPRIT project CREWS, we have proposed a framework for classifying scenarios as a way to explore the issues underlying scenario based approaches in RE. Applying the framework on several scenario approaches [Rolland 97] proved the existence of the large variety of products and practices of scenarios. This work shows also that one has little understanding about how scenarios should be retrieved, constructed, and appended to different methods. 1 This work is partly funded by the Basic Research Action CREWS ....

....Indeed, this additional information is the most relevant to discriminate between scenario approaches, and we find necessary to define carefully and precisely these internal properties. The internal part of the descriptors is inspired by the framework for 6 scenario classification proposed in [Rolland 97] This framework allows to identify the relevant properties of scenarios and to discriminate between scenario chunks. Three views of the framework, namely the form, content, lifecycle of scenarios are used to identify the internal properties of the scenario chunk descriptors. Each of them is ....

[Article contains additional citation context not shown here]

C. Rolland, A. Sutcliffe, M. Jarke, E Dubois, et al. "A Proposal for a Scenario Classification Framework". ESPRIT 4 th Framework Programme CREWS 21.903, Deliverable D1-I1.1, 1997.

....of industrial projects using scenarios [44] the use of scenarios, in addition to conceptual models, improves the quality of the requirements engineering process. A comprehensive comparison of existing scenario based techniques has been developed in the ESPRIT Reactive Research Project CREWS 1 [40]. The most popular form of scenarios are use cases as proposed by Jacobson s OOSE [21] and their various extensions, e.g. by Regnell [38] 39] or Cockburn [8] Complementary experiences in e.g. participatory design (e.g. 3] 5] 43] indicate that better stakeholder involvement can be achieved ....

C. Rolland et al., "A Proposal for a Scenario Classification Framework", Requirements Engineering Journal, Vol. 3, No. 1, 1998, pp. 23-47.

....Lift scenario given in Figure 8. 7. RELATED WORK The informal use of scenarios for requirements elicitation, validation and documentation is widely recognized among practitioners [69, 72] and is promoted by many methodologies [68, 67, 34, 58] Proposals for representing scenarios have flourished [63]; they generally consist in extensions or adaptations of existing notations for capturing dynamic behaviors of specific agents. For type level scenarios, these include, e.g. regular expressions [11] statecharts [25] decision trees [32] operational scripts [67] enriched with contextual ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois and P. Heymas, "A Proposal for Scenario Classification Framework". Requirements Engineering Journal, Vol. 3 No. 1, 1998. Also available as CREWS Report Series No. 96-01.

....analysis methods and therefore, that it is worth looking for the integration of such approaches in current methods. This shall lead to an enhancement of the existing methods with scenario based techniques. Moreover, in the CREWS project we have proposed a framework for classifying scenarios [Rolland 98b] as a way to explore the issues underlying scenario based approaches in Requirements Engineering (RE) The application of this framework on several scenario based approaches proven the existence of the variety of products and practices of scenarios. We situate our work in the situational method ....

....required PRODUCT PARTs allowing to apply the chunk. If the type of the required product is scenario based , this product must be characterised by providing values to the classification attributes. These scenario classification attributes are 8 defined in the scenario classification framework [Rolland 98b] They permits to specify what is the required scenario medium (text, table, graphic, image, etc. notation (informal, formal, semiformal) interactivity (None, hypertext like, advanced) animation (True, False) coverage (functional, intentional, non functional) etc. The DESCRIPTOR INTENTION ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyt, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, A proposal for a scenario classification framework. Requirements Engineering Journal Vol 3, No 1, Springer Verlag, pp.23-47, 1998.

....Engineering With Scenarios) n21903. The literature shows that scenarios come in different forms : textual, animated, prototypes etc. However, a number of authors [12, 17, 19, 21, 26, 27, 39, 42] recommends textual ones. A survey of scenario based approaches conducted within the CREWS project [32] has shown that over thirteen approaches eight recommend the use of natural language text descriptions of system use . The widespread use of textual scenarios was also confirmed by visits of industrial sites which showed that, in practice, 90 of scenarios are expressed in either textual form or ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois and P. Heymans, A Proposal for a Scenario Classification Framework, ESPRIT Reactive Long Term Research Project 21.903 CREWS, Deliverable I1: Initial Integration Workpackage (1997).

....2.1 The CREWS surveys on scenario based RE CREWS has undertaken two surveys on scenario based approaches in RE, Human Computer Interface, Software Engineering and Information System Engineering. The first one is a state of the art on scenario based methods and tools developed by research [Rolland 98] and the second is a survey of the practice of scenarios in European industrial organisms [Weidenhaupt 98] These are commented in turn. 2.1.1 State of the art of scenario based methods and tools in research The CREWS state of the art on the scenario based approaches covers over 40 different ....

....in turn. 2.1. 1 State of the art of scenario based methods and tools in research The CREWS state of the art on the scenario based approaches covers over 40 different research approaches out of which 12, selected for their representativeness of the main trends, are studied in the details [Rolland 98] This survey exhibits a great diversity of scenario related methods, models and notations. Indeed, scenarios support the capture of examples, scenes, narrative descriptions of contexts, cases of system use and illustrations of agent behaviours. Moreover, they allow to elicit requirements in ....

[Article contains additional citation context not shown here]

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyt, A. Sutcliffe, N. A.M. Maiden, Matthias Jarke, P. Haumer, K. Pohl, E. Dubois, P. Heymans, A Proposal for a Scenario Classification Framework. RE, Vol.3, N1, pp.23-47, 1998.

....concrete behaviours, they capture real requirements. However, because they deal with examples and illustrations, scenarios are inherently partial and only provide restricted requirements descriptions which need to be generalised to obtain complete requirements. Scenarios have been developed [Rolland98c] for different purposes with different contents, expressed in different levels of abstraction and with different notations. In so far as their purpose is concerned, scenarios can be descriptive, explanatory or exploratory. Descriptive scenarios [Potts94] capture requirements by enabling the ....

: C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyt, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, "A Proposal for a Scenario Classification Framework". Requirements Engineering Journal, Vol; 3, No. 1, pp. 23-47, 1998.

....approaches have been proposed until now. For example Kyng proposes to use scenarios to envision the requirements [11] Potts to elicit the requirements [15] Jacobson to analyse the objects of the application domain [9] etc. Scenarios may have different forms, contents, coverage, and purposes [19]. However, our investigations show that in the literature, most of the approaches lie on textual scenarios [19] and that in the practice, in about 80 of scenariobased projects, scenarios are described under the textual form [27] The growing number of practitioners demanding for more ....

....[11] Potts to elicit the requirements [15] Jacobson to analyse the objects of the application domain [9] etc. Scenarios may have different forms, contents, coverage, and purposes [19] However, our investigations show that in the literature, most of the approaches lie on textual scenarios [19], and that in the practice, in about 80 of scenariobased projects, scenarios are described under the textual form [27] The growing number of practitioners demanding for more informality in the requirements engineering process [12] seems to confirm this trend. However, as show our enquiries at ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, A Proposal for a Scenario Classification Framework. Requirements Engineering Journal, 3 :1, 1998.

....assumptions relating these occurrences, possible opportunities and risks, and courses of action. Given the renewed interest in scenarios, recent surveys of scenario research and practice suggest that scenarios management means different things to different people, even within disciplines [5, 9, 22, 58, 73]. Clearly, however, scenarios are not just abstract artifacts but a critical representation of the realities as seen by those who create them. Historically, researchers and practitioners from other disciplines have long used scenarios. The scenario concept came into research via military and ....

.... 8VDJH#:RUOG 6RFLDO DVSHFWV ,QGLYLGXDO## LGHDWLRQDO#DVSHFWV # # ## ## ## ## ## 8VDJH#:RUOG KDQJH# FWLYLW :RUN# FWLYLW 6XEMHFW#:RUOG 6RFLDO DVSHFWV ,QGLYLGXDO## LGHDWLRQDO#DVSHFWV 6 VWHP :RUOG Figure 7: Change management as a meta information system A review of the scenario literature [58] shows that this framework also provides a reasonable starting point for classifying scenario based approaches. Looking at the work activity as the subject domain and scenarios as one kind of development system artifact in the change activity, we obtain four views: What part of the work ....

[Article contains additional citation context not shown here]

Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, M., Jarke, M., Haumer, P., Pohl, K., Dubois, E., Heymans, P. 1998. A proposal for a scenario classification framework. Requirements Engineering Journal 3, 1, 23-47.

....how a process model can be constructed, b) the construction technique facet to understand how it can be engineered, c) the change support facet to see how flexible the process model is etc. Facets have been proposed by [Pri87] for classifying reusable components. They have also been used by [Rol98] in requirements engineering for understanding and classifying scenario based approaches. When used in process engineering, a facet provides a means for classification. For example, the coverage facet of the system world (see section 5 below) helps in classifying process models according to the ....

....of a bank organisation. The second approach [Rol96b] uses the notion of descriptor [DeA91] as a means to describe process chunks. It has been tried out to construct information systems methods [Pli95] in NATURE and repository of scenario based approaches accessible on Internet in the CREWS project [Rol98]. For the assembly technique to be successful, it is necessary that process models are modular. If the assembly technique is combined with the instantiation technique then the meta model must itself be modular. 6.2.4 Ad Hoc Traditional process models are expressions of the experiences of their ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, A proposal for a scenario classification framework. To appear in Requirements Engineering Journal 3 :1, 1998.

....which are complementary to one another. The refinement relationship helps in moving from business goals through different levels of abstraction at the discretion of the requirement chunk author. In section 4, we shall show the manner in which the different levels defined in the CREWS project [29], namely the contextual, system interaction and system internal levels, are realised by the abstraction relationship. Distinguishing between the three kinds of relationships does 2 Manner is a subtype of way (see Fig. 3) 3 The notation of RC indices is the following : given a requirement chunk ....

....action is suggested as a goal for the next step of refinement (step 4) The RCA evaluates and names the selected goals. 4. APPLYING RULES TO THE CREWS L ECRITOIRE GOAL ORIENTED APPROACH This section illustrates the use of the generic rules within the Crews L Ecritoire goal oriented approach. In [29], we have classified scenarios into contextual, system interaction and system internal scenarios. Here, we extend this classification to requirement chunks. The three types of RCs, namely contextual, system interaction and system internal requirement chunks inherit their types from the scenario ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, A proposal for a scenario classification framework. To appear in Requirements Engineering Journal, 1998.

.... following the example of the three dimensions framework of RE developed in the pre cursor NATURE project [13] a scenario classification framework was developed based on a comprehensive survey of scenario literature in requirements engineering, human computer interaction, and other fields [14]. The framework was applied to classify eleven prominent approaches. To complement this research framework, the state of applying scenarios in industrial projects was investigated through site visits with scenario user projects. Given the lack of theory in the field, this study had to be ....

....for each site visit the project background, the scenario characteristics, the way in which scenarios were produced and used, the benefits and problems needs stated by the interview partners and our main lessons learned from the site visit. 2.1. Preparation The CREWS classification framework [14] was used to derive a catalogue of questions for scenario characterization in the site visits. This framework originally was gained from a comprehensive literature survey and applied to classify eleven scenario approaches. It views scenarios from four different angles, concerning the form, ....

[Article contains additional citation context not shown here]

C. Rolland, C. B. Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, and P. Heymanns, "A Proposal for a Scenario Classification Framework," tech. rep., CREWS Report Series No. 96--01, 1996.

....propose three kinds of relationships : AND, OR and Refine. Despite these relationships have been defined within the CREWS project [15] we believe that they are generic and can be used to organise collections of scenarios of different kinds : textual, graphical, animated, functional or not, etc. [14]. The AND OR Refine relationships are semantic relationships which relate scenarios according to the nature of their contents. The solution proposed has been applied on examples [13, 15] and on real case studies [10] 1 This work is partly funded by the Basic Research Action CREWS (ESPRIT ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, P. Heymans, A Proposal for a Scenario Classification Framework. Requirements Engineering Journal, 3 :1, 1998.

....scenario models. 1. Introduction Scenarios have recently gained attention in the field of Requirements Engineering (RE) Scenarios may have different forms, contents, coverage, and purposes. However, our investigations show that in the literature, most of the approaches lie on textual scenarios [6], and that in the practice, in about 80 of scenario based projects, scenarios are described under the textual form [4] The growing number of practitioners demanding for more informality in the requirements engineering process seems to confirm this trend [1] However, as show our enquiries at ....

C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyté, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, A Proposal for a Scenario Classification Framework. Requirements Engineering Journal, 3 :1, 1998.

....components of the system and its environment. This behaviour will be progressively created by interacting with a tool (called animator) which will check if the behaviour respects the constraints of the specification. In other terms, our approach really comes down to test if a given scenario [Rol96], proposed by one or several stakeholders, is compatible with the requirements specification. The main challenges we want adress in our animation tool are the following : to provide a distributed tool which allows different stakeholders to cooperatively animate a specification, each of them ....

Rolland, C., Ben Achour, C., Cauvet, C., Ralyté, J., Sutcliffe, A., Maiden, N.A.M., Jarke, M., Haumer, P., Pohl K., Dubois, E., Heymans, P., A Proposal for a Scenario Classification Framework (CREWS Report 9601) . Available at http://SunSite.Informatik.RWTH-Aachen.DE/CREWS/reports.html

No context found.

Rolland, C., Achour, C.B., Cauvet, C., Ralyt, J., Sutcliffe, A., Maiden, N.A.M., Jarke, M., Haumer, P., Pohl, K., Dubois, E. & Heymans, P. (1996). A proposal for a scenario classification framework. CREWS Report 96-01.

No context found.

: C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyt, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, Dubois, P. Heymans, "A Proposal for a Scenario Classification Framework". Requirements Engineering Journal, Vol; 3, No. 1, pp. 23-47, 1998.

No context found.

Rolland C, Ben Achour C, Cauvet C, Ralyt J, Sutcliffe A, Maiden M, Jarke M, Haumer P, Pohl K, Dubois E, Heymans P (1998) A proposal for a scenario classification framework. Req Eng J 3 (1):23--47

No context found.

C. Rolland et al., A proposal for a Scenario Classification Framework, Journal of Requirements Engineering, Vol. 3 No. 1, 1998, Springer Verlag, pp. 23--47.

No context found.

Rolland and Al, Deliverable D1-I1.1 CREWS, A proposal for a Scenario Classification Framework, 1997

No context found.

C. Rolland, C.Ben Achour, et al, A Proposal for a Scenario Classification Framework, CREWS Report 96-01, City University, London, 1996

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC