Ben Achour, C.: Guiding Scenario Authoring, Proc. of the Eight European-Japanese Conference on Information Modeling and Knowledge Bases, Vamala, Finland, May 25-29, (1998)  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... but that there are concerns about how to structure textual use case descriptions [Jarke et al., 1997, Weidenhaupt et al., 1998] To tackle this lack of structure, CREWS has built on to the work of Cockburn in proposing a set of Style and Content Guidelines to enable better scenario authoring [Achour, 1998]. To test how effective the guidelines are, CREWS conducted an experiment where four groups of subjects wrote a use case description, three of the four groups applying some part of the guidelines. CREWS report that application of the guidelines significantly improved the use case descriptions. The ....

....guidelines are, CREWS conducted an experiment where four groups of subjects wrote a use case description, three of the four groups applying some part of the guidelines. CREWS report that application of the guidelines significantly improved the use case descriptions. The results are described in [Achour et al., 1998] and some of the structure of the experiment is found at [Achour and Maiden, 1999] The rest of the paper is as follows. Section 2 discusses the issue of replication. Section 3 lists the CREWS guidelines. Section 4 describes the experimental hypotheses. Section 5 describes the experimental ....

[Article contains additional citation context not shown here]

C Ben Achour (1998), Guiding Scenario Authoring, Proc. 8 th European-Japanese Conference on Information Modelling and Knowledge Bases, Finland, (ed. H. Jaakola, H. Kangassalo), pp181-200, May 1998.

....Within the CREWS project we assume scenarios to be textual and use authoring rules to provide style and content guidelines as well as linguistic devices for analysis, disambiguation and completion. The linguistic devices are based on case grammar and case patterns. Details can be found in [Ben, 98] The guideline is a plan context suggesting 4 steps to Author a scenario namely: 1. choose the form of guidance desired. Indeed the requirements engineer has the possibility to use style guidelines, contents guidelines, both of them or use free text analysis during scenario authoring. This is ....

C. Ben Achour, Guiding scenario authoring, submitted to the 8 th EuropeanJapanese Conference on Information Modeling and Knowledge Bases, 1998.

.... which the syntax of the language used in scenarios is defined) and the deep level (which deals with the semantics of the scenario clause and sentences) At both levels, the linguistic scenario model is tightly related to the precise semantics defined for scenarios in the conceptual scenario model [BenAchour 98a] BenAchour 99] Free prose scenario writing is guided by informal guidelines which help : limiting the size of the input scenarios, targeting their content, advising on what is expected at this very moment in the process (according to the linguistic scenario model) and providing, if ....

....is needed. The rules guiding the conceptualisation of textual scenarios support their linguistic analysis, correction and their mapping onto formally structured concepts. This permits the approach to take advantage of free text expression while limiting the complexity of their interpretation [BenAchour 98a] Rolland 98b] In addition to the computer supported strategy, a manual strategy is also proposed for conceptualising scenarios. This strategy looses the advantage of automation and requires an in depth knowledge of the scenario models. However, we believe several levels automation should be ....

C. Ben Achour, Guiding Scenario Authoring. Proceedings of the 8 th European-Japanese Conference on Information Modelling and Knowledge Bases, Ellivuori, Finland, pp.181-200, 1998.

.... Report Series 99 19 EVALUATING THE CREWS L ECRITOIRE REQUIREMENTS ELICITATION PROCESS Mustapha Tawbi, Fernando Velez, Carine Souveyet, Camille Ben Achour CRI, Universit de Paris1 Sorbonne, 90, rue de Tolbiac, 75013 Paris Submitted to ICRE2000 Fourth IEEE International Conference on Requirements Engineering, Schaumburg, Illinois, USA, June 2000 1 Evaluating the CREWS L Ecritoire Requirements Elicitation Process 1 Mustapha Tawbi, Fernando Velez, Camille Ben Achour, C. Souveyet ....

C. Ben Achour, Guiding Scenario Authoring, Proceedings of the Eight European - Japanese Conference on Information Modelling and Knowledge Bases. May 25-29, Vamala, Finland.

....provided in the form of enactable guiding rules embodied in a computer software environment called L Ecritoire. As a result, it is possible to guide the requirements elicitation process through interleaved goal modelling and scenario authoring. Whereas rules for scenario authoring can be found in [3, 28], we propose here a basis for guidance in goal modelling. There are three kinds of rules, each for determining one of the three kinds of relationships mentioned above namely, AND, OR, and Refinement. Each rule generates a menu of goals for the Requirement Chunk Author (RCA) to evaluate and select. ....

....the semi structured textual form to represent the scenarios associated to requirement chunks. As shown in Fig. 5, each action of a scenario is expressed in a separate line as a natural language clause preceded by a reference number. The formal semantics of natural language clauses is detailed in [3, 28]. 2.2 The hierarchy of requirement chunks The three types of relationships among requirement chunks lead to a hierarchical organisation of RCs, as illustrated in Fig. 5. RC1.1 AND AND G1.1:Withdraw cash from ATM in a normal way Sc1.1 G1.1 1 :Withdraw cash from ATM by treating the exception ....

[Article contains additional citation context not shown here]

C. Ben Achour, Guiding scenario authoring. Proceedings of the 8 th European Japanese Conference on Information Modelling and Knowledge Bases, pp 181-200, Ellivuori, Finland, May 26-29, 1998.

....scenario includes one or several actions, but, by definition, the combination of actions in a scenario describes a unique path from an initial to a final state. A requirement chunk (RC) is a pair goal, scenario . The CREWS approach addresses the authoring of scenarios and the discovery of goals [1,15]. Both are guided by rules. Goal discovery is guided by situated rules. Each rule proposes a way to fulfil the stakeholder s discovery intention for a well defined situation. Scenario authoring is composed of two steps, scenario writing and scenario correction. Scenario writing is guided by ....

C. Ben Achour, Guiding scenario authoring. Submitted to the Euro-Japanese conference, 1998.

....interactions between two agents, or actions of internal type. CREWS provides guidelines for writing and refining scenarios, and for integrating different scenarios into a UC [12] Guidelines exist to structure scenarios, make scenarios more complete, precise, and consistent in terminological use [13]. CREWS also provides software assistance to apply the guidelines [8] It analyses narrative text to catch the semantics of the text and map the text contents into instances of the CREWS UC model. According to Schank [14] analysing the semantics of scenarios can be done, at least partially, ....

.... linguistics ( 15] 14] 16] 17] 18] 19] artificial intelligence [20] and previous applications of Case Grammars to requirements analysis [21] The linguistic structure and semantics of scenarios actions is interpreted using case patterns and the corresponding set of surface linguistic structures [13]. 2.2 CREWS guidelines for use case authoring To guide in the authoring of scenarios, CREWS provides general guidelines which divide a UC into three sections : i. normal course scenario, describing the normal sequence of actions in the UC, ii. variations to the normal course scenario, and iii. ....

C. Ben Achour. Guiding Scenario Authoring. Proc. 8 th European- Japanese Conference on Information Modelling and Knowledge Bases, Finland, (ed. H. Jaakola, H. Kangassalo), pp. 181-200. Mai 1998.

....the Else statement in the last sentence. Once raised, this issue is solved by the writing an additional scenario considering the alternative case separately. For the sake of place, the rules and guidelines can not be extensively described here. However, more complete information can be found in [2], and [7] 5. Conclusion Very few approaches say how to author textual scenarios. Based on a formal conceptual model of scenarios, this paper aims at guiding the process of scenario authoring. This guidance emphasises two stages : writing and correcting. To help the scenario author writing ....

C. Ben Achour, Guiding Scenario Authoring. Proceedings of the 8 th European Japanese Conference on Information Modelling and Knowledge Bases, pp. 181-200, Ellivuori, Finland, May 2629, 1998.

No context found.

Ben Achour, C.: Guiding Scenario Authoring, Proc. of the Eight European-Japanese Conference on Information Modeling and Knowledge Bases, Vamala, Finland, May 25-29, (1998)

No context found.

Ben Achour, C., "Guiding Scenario Authoring", pp. 152--171 in Proceedings of the Eighth EuropeanJapanese Conference on Information Modeling and Knowledge Bases, IOS Press, Vamala, Finland (25--29 May 1998).

No context found.

C. Achour, "Guiding scenario authoring", In: 8 EuropeanJapanese Conference on Information Modelling and Knowledge Bases , Vammala, Finland, 26-29 May 1998, pp. 181-200.

No context found.

C. Ben Achour, Guiding scenario authoring, in Information Modelling and Knowledge Bases X, pp. 152#171, IOS Press, 1999.

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