Anton, A.I., 1996. Goal-based Requirements Analysis. In: International Conference on Requirements Engineering (ICRE#96). IEEE, Colorado Springs, CO, USA.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....in narrowing the semantic gap between requirements analysis and system design. On one hand, requirements analysis techniques have been recognizing the modeling of the social and intentional context, within which a system will eventually operate, as an important part of the analysis process (e.g. [Ant96, Bub93, Dar93, Yu95]) On the other hand, software design techniques have traditionally been inspired and driven by the programming paradigm of the day (e.g. Boo99, Wir90] This impedance mismatch between analysis and design is one of the main factors for the poor quality of system development projects. One way ....

A. I. Anton, "Goal-Based Requirements Analysis", In Proceedings of the Second International Conference On Requirements Analysis (ICRE'96), pp.136-144, 1996.

....patterns using desirable qualities such as coordinability and predictability. 1. Introduction Modeling the organizational and intentional context within which a software system will eventually operate has been recognized as an important element of the requirements engineering process (e.g. [Ant96, Bub93, Dar93, Yu93]) Such models are founded on primitive concepts such as those of actor and goal. This paper focuses on the definition of a set of organizational patterns that can be used as building blocks for constructing such models. Our proposal is based on concepts adopted from organization theory and ....

A. I. Anton, "Goal-Based Requirements Analysis", Proceedings of the 2 t Int. Conf. On Requirements Analysis, ICRE '96, 1996, pp.136-144.

....revisited in terms of social and intentional primitives. This research has been conducted within the context of the Tropos project [Cas02, Per01] Tropos adopts ideas from MAS technologies and requirements engineering, where agents actors and intentions are used for early requirements analysis [Ant96, Dar93, Yu95]. Tropos is intended as a seamless methodology tailored to describe both the organizational environment of a system and the system itself in terms of the same concepts. In particular, Tropos is founded on the i modeling framework which offers actors (agents, roles, or positions) goals, and actor ....

A. I. Anton, "Goal-Based Requirements Analysis", In Proceedings of the 2 a International Conference on Requirements Analysis, ICRE'96, 1996.

....revisited in terms of social and intentional primitives. This research has been conducted within the context of the Tropos project [Cas02, Per01] Tropos adopts ideas from MAS technologies and requirements engineering, where agents actors and intentions are used for early requirements analysis [Ant96, Dar93, Yu95]. Tropos is intended as a seamless methodology tailored to describe both the organizational environment of a system and the system itself in terms of the same concepts. In particular, Tropos is founded on the i modeling framework which offers actors (agents, roles, or positions) goals, and actor ....

A. I. Anton, "Goal-Based Requirements Analysis", In Proceedings of the 2 na International Conference on Requirements Analysis, ICRE'96, 1996.

....interactions with the users; a misunderstanding at this point may lead to expensive errors during later development stages. Not surprisingly, several approaches have been researched in recent years on suitable concepts, languages and analysis techniques specifically tailored for this phase (e.g. [8, 13, 1]) Formal Methods have a great potential as powerful means for the specification, early debugging and certification of software. They have been successfully applied in several industrial applications, and, in certain fields, they are even becoming integral components of standards [2] However, ....

A. Anton. Goal based requirements analysis. In Proc. 2nd Int. Conf. on Requirements Engineering ICRE'96, 1996.

....thus, demonstrates how dependencies among agents, in conjunction with the goal graph in figure 3, serve as criteria for searching and evaluating further alternative architectural designs. 5. Discussion The requirements engineering research community has recognized the importance of goal modeling [11, 12, 13, 15,16,17]. However, goals are typically used to guide the establishing of requirements or designing of business processes, and serve as criteria for requirements completeness. The approach expounded in this paper recognizes the need to utilize goals during analysis and during the design process. This aids ....

A. I. Anton, "Goal-based Requirements Analysis." Proc.2nd IEEE Int. Conf. Requirements Eng. April 1996.

....interactions with the users; a misunderstanding at this point may lead to expensive errors during later development stages. Not surprisingly, several approaches have been researched in recent years on suitable concepts, languages and analysis techniques specifically tailored for this phase (e.g. [8, 13, 1]) Formal Methods have a great potential as powerful means for the specification, early debugging and certification of software. They have been successfully applied in several industrial applications, and, in certain fields, they are even becoming integral components of standards [2] However, ....

A. Anton. Goal based requirements analysis. In Proc. 2nd Int. Conf. on Requirements Engineering ICRE'96, 1996.

....within the context of a comprehensive software development methodology called Tropos. 1. Introduction Modeling the organizational and intentional context within which a software system will eventually operate has been recognized as an important part of the requirements engineering process (e.g. [Ant96, Bub93, Dar93, Yu93]) Such models are founded on primitive concepts such as those of actor (agent, position or role) and goal. In this paper we focus on the problem of defining a set of organizational patterns which can be used as building blocks for constructing such models. Our proposal is based on concepts ....

A. I. Anton, " Goal-Based Requirements Analysis", Proc. 2 nd Int. Conf. On Requirements Analysis (ICRE'96), 1996, pp.136-144.

....examples of system usages can represent different incarnations of one task fulfilling one specific goal. We therefore elicit and relate goals to the examples (and parts of the examples) because goal models focus on a more abstract level why certain system properties are constructed rather than how [1]. When the whys behind the existing system are understood one can go on modelling critical or problematic details using more concrete modelling languages (e.g. UML Static Structure Diagrams [23] Message Sequence Charts [14] etc. Existing System R Real W World S Scenes Observations of System ....

Annie I. Antn. Goal-based requirements analysis. In Proceedings of International Conference on Requirements Engineering (ICRE'96), pages 136- 144. IEEE, 1996.

....requirements[Mylopoulos92] referred to as soft goals ) Chung96] Similarly emphasis on agents and their relationships is underlying the Albert language aiming at formally specifying requirements [Dubois94] in order to ease their validation through scenario generation. The GBRAM method [Anton 96] that is built over the Inquiry Cycle [Potts94] draws our attention on the nature of the elicitation process that is viewed as a deliberation process among the various stakeholders involved with requirements engineering. Although goal modelling has proved to be useful for specifying purposeful ....

....practical experience tends to show that there are still a number of difficulties. First, even it is often assumed that systems are constructed with some goals in mind [Davies93] in reality [Anton96] Elektra98] goals are not given and therefore the question as to where they originate from [Anton 96] acquires importance. In addition, enterprise goals which initiate the goal discovery process do not reflect the actual situation but an idealised environmental one. Therefore, proceeding from this may lead to ineffective requirements. Eliminating uninteresting and spurious goals is necessary and ....

: A.I. Anton, Goal based requirements analysis. Proceedings of the 2 nd International Conference on Requirements Engineering ICRE'96, pp. 136-144, 1996.

.... 1 Introduction Several proposals coupling goals and scenarios have been recently made to overcome some of the deficiencies and limitations of goal based and scenario based requirements elicitation approaches used in isolation [Framework] CREWSRep97 10] Holbrook 90] Potts 94] Cockburn 95] Anton 96] Leite 97] Haumer 98] Van Lamsweerede 98] Rolland 98] Within this family of approaches, the CREWS L Ecritoire approach [Rolland 98] proposes to exploit a bi directional coupling between goals and scenarios to support requirement elicitation. On the one hand, when a goal is discovered, the ....

A. I. Anton, Goal based requirements analysis. Proceedings of the 2 nd International Conference on Requirements Engineering ICRE'96, pp. 136-144, 1996. 19

.... drawbacks of using each technique in isolation [Pot,97] By combining goals and scenarios the approach aims at : a) facilitating the work of the domain expert by getting over the problem of the fuzzy nature of goals, b) contributing to the important question where the goal originates from [Ant, 96] by helping discover goals, c) overcoming the difficulties encountered in concrete experiences of goal modelling ( Ant, 96] Bub, 94] Rol, 97] by aiding in the task of goal reduction, In order to fulfil these objectives we propose to support the RE process by enactable guidelines rules ....

A. I. Anton, Goal based requirements analysis. Proceedings of the 2 nd International Conference on Requirements Engineering ICRE'96, pp. 136-144, 1996.

....tool set development. Our experience is that it is difficult for domain experts to deal with the fuzzy concept of a goal. Yet, domain experts need to discover the goals of real systems. It is often assumed that systems are constructed with some goals in mind [8] However, practical experience [2, 9] shows that goals are not given and therefore the question as to where they originate from [2] acquires importance. In addition, enterprise goals which initiate the goal process do not reflect the actual situation but an idealised environmental one. Therefore, proceeding from this may lead to ....

....the fuzzy concept of a goal. Yet, domain experts need to discover the goals of real systems. It is often assumed that systems are constructed with some goals in mind [8] However, practical experience [2, 9] shows that goals are not given and therefore the question as to where they originate from [2] acquires importance. In addition, enterprise goals which initiate the goal process do not reflect the actual situation but an idealised environmental one. Therefore, proceeding from this may lead to ineffective requirements. Thus, goal discovery is rarely an easy task. Additionally, it has been ....

[Article contains additional citation context not shown here]

A.I. Anton, Goal based requirements analysis. Proceedings of the 2 nd International Conference on Requirements Engineering ICRE'96, pp. 136-144, 1996.

No context found.

Anton, A.I., 1996. Goal-based Requirements Analysis. In: International Conference on Requirements Engineering (ICRE#96). IEEE, Colorado Springs, CO, USA.

No context found.

A. I. Anton. Goal-based requirements analysis. In Proceedings of the IEEE International Conference on Requirements Engineering (ICRE '96), Colorado Springs, USA, Apr. 1996.

No context found.

A. I. Anton. Goal based requirements analysis. In Proceedings of the 2nd International Conference on Requirements Engineering ICRE'96, pages 136--144, 1996.

No context found.

A. I. Anton. Goal-based requirements analysis. In Proceedings of the IEEE International Conference on Requirements Engineering (ICRE '96), Colorado Springs, USA, Apr. 1996.

No context found.

Anton, A. (1996). Goal-Based Requirements Analysis. In 2nd IEEE Conferenec on Requirements Engineering, pages 136--144, Colorado Springs, Colorado.

No context found.

A.I. Anton, Goal based requirements analysis. Proceedings of the 2 nd International Conference on Requirements Engineering ICRE'96, pp. 136-144, 1996.

No context found.

A.I. Anton. Goal-Based Requirements Analysis. In Proc. of the IEEE International Conference on Requirements Engineering (ICRE), April 1996.

No context found.

A. I. Anton. Goal-based requirements analysis. In Proceedings of the IEEE International Conference on Requirements Engineering (ICRE '96), Colorado Springs, USA, Apr. 1996.

No context found.

A. I. Anton. Goal based requirements analysis. In Proceedings of the 2nd International Conference on Requirements Engineering ICRE'96, pages 136--144, 1996.

No context found.

A.I. Anton, "Goal Based Requirements Analysis," in Proc. Second Int. Conference on Requirements Engineering., ICRE '96, pp. 136--144, 1996.

No context found.

A. I. Anton, "Goal-Based Requirements Analysis", In Proceedings of the Second International Conference On Requirements Analysis (ICRE'96), pp. 136-144, 1996.

No context found.

A.I. Anton, "Goal-based Requirements Analysis," Proc. 2nd IEEE Int'l Conf. Requirements Engineering, CS Press, Los Alamitos, Calif., Apr. 1996, pp. XX-XX.

First 50 documents

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