A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pages 94-- 104, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....or system. Scenarios are concrete, narrative, and procedural. They describe real situations using examples and illustrations. Hence combining goals and scenarios is an effective way to elicit and validate requirements. Goals are operationalized through scenarios and refined into requirements [AMP94]. Similarly, scenarios can be used to help discover goals [AP98] The GBRAM uses goal hierarchies to organize requirements as scenarios, goal obstacles, and consmints [Ant96] Others also organize scenarios hierarchically according to goals and goal obstacles [Coc97] Rolland et al. proposed a ....

A. I. An6n, W. M. McCracken and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Proc. of the 6 tn International Conference on Advanced Information Systems Engineering (CAiSE"94), Utrecht, The Netherlands, pp. 94-104, 6-10 June 1994.

....A requirement represents one particular way of achieving some specific goal; the requirement is therefore more likely to evolve, towards another way of achieving that same goal, than the goal itself. The higher level a goal is, the more stable it will be. Others have made that same observation [Ant94] It turns out that different system versions often share a common set of high level goals; the current system and the system to be correspond to alternative refinements of common goals in the goal refinement graph, and can therefore be integrated into one single goal model (see Section 3) ....

....to favor those which better ensure some soft tar get property. In a similar vein, Sut93] proposes a classification according to desired system states (e.g. positive, negative, alternative, feedback, or exception repair) and to goal level (e.g. policy level, functional level, domain level) Ant94] makes a distinction beween objective goals, that refer to objects in the system, and adverbial goals, that refer to ways of achieving objective goals. Goal types and taxonomies are used to define heuristics for goal acquisition, goal refinement, requirements derivation, and semi formal ....

[Article contains additional citation context not shown here]

A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering, Proc. CAISE'94, LNCS 811, Springer-Verlag, 1994, 94-104.

....in the context of an organisational role by an actor playing that role. In this respect we have been inspired by the Role Activity diagrams of [23] The process submodel is also closely related with the objectives and goals submodel: processes are operationalisations of organisational goals [1]. 3.1 Primitive and Complex Actions Our process submodel is built around the concepts of situation calculus [20, 27] and the concurrent logic programming language ConGolog [5] The situation calculus is a first order language for representing dynamically evolving domains. A situation is a state ....

.... documents (e.g. mission statement) outlining the strategy of the enterprise to be modelled (and possibly other enterprises in the same industry sector) and so on [2] During this activity the analyst using our methodology must try to uncover not only prescriptive goals, but also descriptive ones [1]. After we have a preliminary statement in natural language of the enterprise objectives and goals, then the process of constructing a corresponding AND OR goal graph by asking why and how questions can begin [4] This process involves reducing goals, identifying conflicts and detecting ....

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pages 94-- 104, 1994.

....requirements derivation. Goals are operationalized and refined into requirements and point to new, previously unconsidered scenarios. Scenarios are descriptions of concrete system behaviors. They may summarize the behavior traces of an existing system. Scenarios also help in the discovery of goals [AMP94, AP98, JBC98, Pot99, RSB98]. Although the merits and benefits of scenario based and goalbased analysis in requirements engineering are well understood, researchers are now faced with the question of how to use scenarios and goals in a complimentary fashion for evolving systems in which risk and impact assessment as well as ....

....refining these goals and scenarios. The GBRAM heuristics and supporting inquiry include references to appropriate construction of scenarios and the process by which they should be discussed and analyzed. We have successfully applied this method to the analysis of systems for various organizations [AMP94, Ant96, Ant97, AP98, ADS00]. The latter two of these systems were electronic commerce applications [AP98, ADS00] Securing sensitive data is essential from the initial design phase of a system and the cost of security controls must be appropriate for the risk environment of the individual system. A risk analysis is needed ....

[Article contains additional citation context not shown here]

A.I. Antn, W.M. McCracken and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information System Engineering: 6th International Conference, CAiSE `94 Proceedings, Utrecht, The Netherlands, 6-10 June 1994, pp. 94-104, 1994.

....for Validation The Scenarios technique has been applied in different research areas and a variety of definitions, ways of use and ways of interaction with the user are given. In particular, scenarios have been used in the area of Software Engineering [13] 14] Business process reengineering [15], User Interface Design [16] Documentation and demonstration of software and many more. In addition the term script used in Artificial Intelligence [17] and in Object behaviour Analysis [18] is very similar to the various definitions of scenarios . Page 5 The idea of using scenarios as a ....

Anton A.I., McCracken W.M. and Potts C., Goal Decomposition and Scenario Analysis in Business Process Reengineering, CAiSE'94, 6th International Conference, Ultrecht, The Netherlands, June 1994

.... a requirement exists because of some underlying goal which provides a base for it [Dar91, Som97] goals represent the roots for detecting conflicts among requirements and for resolving them eventually [Rob89, Lam98b] goals are generally more stable than the requirements to achieve them [Ant94]. In short, requirements implement goals much the same way as programs implement design specifications. Goals are to be achieved by the various agents operating together in the composite system; such agents include software components that exist or are to be developed, external devices, and ....

A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering, Proc. CAISE'94, LNCS 811, Springer-Verlag, 1994, 94-104.

....2 Related Work The terms use cases and scenarios mean different things to different people; we thus discuss these terms in the context of other relevant related work. Scenarios aid analysts and stakeholders in developing an understanding of current or envisaged systems and business processes [AMP94, Jac92, PTA94, WPJ98]. They describe concrete system behaviors by summarizing behavior traces of existing or planned systems. Use cases, introduced by the object oriented community [BRJ99, Fow97, Jac92] describe the possible system interactions that external agents may have with a system. In UML, scenarios are ....

.... specification effort, we employed the GBRAM in which goals are operationalized and refined into requirements and point to new, previously unconsidered scenarios (for a detailed explanation of the GBRAM and its heuristics see: Ant97] Similarly, scenarios also help in the discovery of goals [AMP94, AP98a, JBC98, Pot99, RSB98]. Although the merits and benefits of scenario based and goal based analysis in requirements engineering are well understood, researchers are now faced with the question of how to use scenarios and goals in a complimentary fashion. Several approaches, which we briefly discuss, do show promise ....

[Article contains additional citation context not shown here]

Antn, A.I., W.M. McCracken, and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information Systems Engineering, 6 th International Conference Proceedings (CaiSE'94), Utrecht, The Netherlands, pp. 94-104, 6-10 June 1994.

....analysts to communicate with stakeholders using a language based on concepts with which they are both comfortable and familiar. Goals are operationalized and refined into requirements and point to new, previously unconsidered scenarios. Similarly, scenarios also help in the discovery of goals [AMP94, AP98, JBC98, Pot99, RSB98]. Although the merits and benefits of scenariobased and goal based analysis in requirements engineering are well understood, researchers are now faced with the question of how to use scenarios and goals in a complimentary fashion. Several approaches do show promise [AAB99, MMM98, RSB98] but none ....

....recurring question types. These GBRAM heuristics and supporting inquiry [PTA94] include references to appropriate construction of scenarios and the process by which they should be discussed and analyzed. We have successfully applied this method to the analysis of systems for various organizations [AMP94, Ant96, Ant97, AP98, ADS00]. The latter two of these systems were electronic commerce applications [AP98, ADS00] Students in the project studio will employ the GBRAM to support the early stages of the design process. A.# Scenario Management The state of scenario management in practice was reported in [WPJ98] In this ....

A.I. Antn, W.M. McCracken and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information System Engineering: 6th Intl. Conf., CAiSE 94 Proc., Utrecht, The Netherlands, 6-10 June 1994, pp. 94-104, 1994.

....people; we thus discuss these terms in the context of other relevant related work including the goalbased requirements engineering literature. A. # Scenarios and Use Cases Scenarios aid analysts and stakeholders in developing an understanding of current or envisaged systems and business processes [AMP94, Ant96, Ant97, AP98a, AP98b, BL98, Jac92, Pot95, WPJ98]. They describe concrete system behaviors by summarizing behavior traces of existing or planned systems. Use cases, introduced by the objectoriented community [BRJ99, Fow97, Jac92] describe the possible system interactions that external agents may have with a system. In UML, scenarios are ....

....since goals are typically more stable than requirements [Ant97] they are a beneficial source for requirements derivation. Goals are operationalized and refined into requirements and point to new, previously unconsidered scenarios. Similarly, scenarios also help in the discovery of goals [AMP94, AP98a, JBC98, Pot99, RSB98]. Although the merits and benefits of scenario based and goal based analysis in requirements engineering are well understood, researchers are now faced with the question of how to use scenarios and goals in a complimentary fashion. Several approaches, which we briefly discuss, do show promise ....

[Article contains additional citation context not shown here]

Antn, A.I., W.M. McCracken, and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information Systems Engineering, 6 th International Conference Proceedings (CaiSE'94), Utrecht, The Netherlands, pp. 94-104, 6-10 June 1994.

....context of an organisational role by an actor playing that role. In this respect we have been inspired by the Role Activity diagrams of [Oul95] The process submodel is also closely related with the objectives and goals submodel: processes are operationalisations of organisational goals [Bub94, AMP94] 4.1 Primitive and Complex Actions Our process submodel is built around the concepts of situation calculus [MH69, Rei91] and the concurrent logic programming language ConGolog [DGLL97] The situation calculus is a first order language for representing dynamically evolving domains. A situation ....

.... (e.g. mission statement) outlining the strategy of the enterprise to be modelled (and possibly other enterprises in the same industry sector) and so on [BBS98] During this activity the analyst using our methodology must try to uncover not only prescriptive goals, but also descriptive ones [AMP94] After we have a preliminary statement in natural language of the enterprise objectives and goals, then the process of constructing a corresponding AND OR goal graph by asking why and how questions can begin [DvLF93] This process involves reducing goals, identifying conflicts and detecting ....

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pages 94--104, 1994.

....the current system, and joint creativity towards the future. But the number of possible scenarios is even greater than the number of models for a given system. Therefore, many researchers have begun to recognize the need to make the goal hierarchies driving scenario based processes explicit (e.g. [2, 16, 49]) initial model initial model new model new model existing system existing system new system new system change specification reverse analysis engineering legacy integration change implementation 22 By combining these two extensions, we obtain a basic framework for scenario supported change ....

Anton, A.I., McCracken, W.M., Potts, C. 1994. Goal decomposition and scenario analysis in business process re-engineering. Proc. 6th Intl. Conf. Advanced Information Systems Engineering (CaiSE 94), Utrecht, NL, Springer-LNCS, 94-104.

....to apply goal based requirements methods in isolation and suggests that they should be complemented with scenarios. However, he does not make a specific proposal on how this can be done. Yet other proposals exist which interpret scenarios as containing information on how goals can be achieved [1, 14, 25]. Thus, the goal scenario combination has been used to operationalise goals. Yet others look upon goals as playing a documentation role only. This view is taken in [6, 15, 18, 23] where a goal is considered as a contextual property of a use case (integrated set of scenarios) i.e. it is a property ....

....Relationships The composition and alternative relationships lead to a horizontal AND OR structure between RCs. These are extensions of AND OR relationships between goals identified by a number of researchers, for example in NATURE process theory [13] KAOS [7] F 3 [4] and others (e.g. [1, 11, 34]) AND relationships among RCs (the OMT AND association in Fig. 2) link together those chunks that require each other to define a completely functioning system. The requirement chunks RC1.1 and RC1.2 in Fig. 5 associated with the goals, G1.1 and G1.2 are examples of such chunks. Indeed, in ....

A.I. Anton, W. M. Mc Cracken, C. Potts, Goal decomposition and scenario analysis in business process reengineering. Proceedings of the 6 th International Conference CAiSE'94 on Advanced Information Systems Engineering, Utrecht, the Netherlands, Springer Verlag, pp. 94-104, 1994.

....: if there is a dynamic for achieving it then the goal must be a realistic one. Additionally, the scenario specifies a way of operationalising the goal. In this way the goal scenario coupling mitigates the problem of fuzziness of goals and goal operationalisation as reported in the literature [20, 1]. 3.3.1 Finding Whether Goals are Realistic or Not. The writing of a scenario can lead to discover that the associated goal is not realistic. For instance, let us consider the ELEKTRA goal Connect verb (customer) beneficiary (to PPC Network) result (with a meter installation)manner (within 2 ....

Anton A.I., McCraken W.M., Potts C., Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced information System Engineering, 6 th Int. Conf. CaiSE'94 Proc., Utrecht, The Netherlands, 6-10 June 1994, pp 94-104, 1994.

....for understanding the environment of IS, few methods have emerged that offer a systematic way to model enterprise goals. In most goal oriented approaches requirements are derived by high level goals by a (mostly) top down goal decomposition process Dardenne, Lamsweerde [7] Anton, McCracken [8] . Top down decomposition requires well formed questions (i.e. the goals) and the provision of definite answers (i.e. the operationalisation alternatives) This is not always the case since the task of enterprise goal modelling often necessitates the development and resolution of concerns of ....

....or potentially available to the organisation, as described in the organisational and operational viewpoints of the enterprise model. 2.2.2 Goal operationalisation. Operationalisation is the process of refining goals so that the resulting subgoals have an operational definition Anton, McCracken [8] . The most common approach to goal operationalisation is that of goal reduction. Goal reduction is based on top down decomposition. However, instead of being predominantly top down, the goal operationalisation process is likely to be highly iterative and open ended. In the following sections we ....

Anton, A.I., W.M. McCracken, and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering. in 6th International Conference on Advanced Information Systems Engineering (CAiSE.94). 1994. Utrecht, The Netherlands: SpringerVerlag.

....organisational role by an actor playing that role. In this respect we have been inspired by the RoleActivity diagrams of [ Ould, 1995 ] The process submodel is also closely related with the objectives and goals submodel: processes are operationalisations of organisational goals [ Bubenko, 1994; Anton et al. 1994 ] 4.1 Primitive and Complex Actions Our process submodel is built around the concepts of situation calculus [ McCarthy and Hayes, 1969; Reiter, 1991 ] and the concurrent logic programming language ConGolog [ De Giacomo et al. 1997 ] The situation calculus is a first order language for ....

.... statement) outlining the strategy of the enterprise to be modelled (and possibly other enterprises in the same industry sector) and so on [ Bubenko et al. 1998 ] During this activity the analyst using our methodology must try to uncover not only prescriptive goals, but also descriptive ones [ Anton et al. 1994 ] After we have a preliminary statement in natural language of the enterprise objectives and goals, then the process of constructing a corresponding AND OR goal graph by asking why and how questions can begin [ Dardenne et al. 1993 ] This process involves reducing goals, identifying ....

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pages 94--104, 1994.

....has been considered only rather recently in the literature. Goals are generally modelled by intrinsic features such as their type and attributes, and by their links to other goals and to requirements. Various goal taxonomies have been proposed to type goals [Myl92] Dar93] Nix93] Ant94] For instance, information goals are functional goals concerned with keeping agents informed about object states; accuracy goals are non functional goals concerned with maintaining the consistency between objects in the environment and their software image. Useful attributes for a goal may ....

.... Participant agent and Meeting entity are declared in other sections of the specification, e.g. Agent Participant CapableOf CommunicateConstraints, Has Constraints: Tuple [ExcludedDates: SeqOf [TimeInterval] PreferredDates: SeqOf [TimeInterval] Relationship Invited Links Participants card: 0:N , Meeting card: 1:N DomInvar p: Participant, m: Meeting Invited (p, m) p Requesting[ m] ParticipantsList In the declarations above, Constraints is declared as an attribute of Participant (this attribute was used in the formal definition of ParticipantsConstraintsKnown) Also note that ....

Anton, A. I., McCracken, W. M., Potts, C., "Goal Decomposition and Scenario analysis in Business Process Engineering ", CAiSE'94, LNCS 811, Springer-Verlag, pp. 94-104.

No context found.

Antn, A.I., McCracken, W.M., and Potts, C. Goal Decomposition and Scenario Analysis in Business Process Reengineering in proc. of Advanced Information System Engineering: 6th International Conference, CAiSE '94 (Utrecht, The Netherlands, June 1994) 94-104.

No context found.

A.I. Antn, W.M. McCracken and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information System Engineering: 6th International Conference, CAiSE `94 Proceedings, Utrecht, The Netherlands, 6-10 June 1994, pp. 94-104, 1994.

....of alternative future circumstances. In this last capacity, scenarios are also used to envisage how technical systems may change as the result of sociotechnical changes [AP98] Thus, scenarios may be applied at both strategic and tactical (operational) levels, but as we have observed previously [AMP94] scenario analysis aids in bringing tactical goals into alignment with the organization s strategic goals. Scenarios describe narrative sequences that can be real (as in incident reconstruction) desired (such as illustrating a satisfactory application of a policy) or imagined but undesirable ....

A.I. Antn, W.M. McCracken & C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information System Engineering: 6th International Conference, CAiSE `94 Proceedings, Utrecht, The Netherlands, 6-10 June

....things to different people; we thus discuss these terms in the context of other relevant related work including the goalbased requirements engineering literature. Scenarios aid analysts and stakeholders in developing an understanding of current or envisaged systems and business processes [AMP94, AP98a, AP98b, BL98, Jac92, Pot95, PTA94, WPJ98]. They describe concrete system behaviors by summarizing behavior traces of existing or planned systems. Use cases, introduced by the object oriented community [BRJ99, Fow97, Jac92] describe the possible system interactions that external agents may have with a system. In UML, scenarios are ....

.... effort, we employed the GBRAM in which goals are operationalized and refined into requirements and point to new, previously unconsidered scenarios (for a detailed explanation of the GBRAM and its heuristics see: Ant96, Ant97, AP98a] Similarly, scenarios also help in the discovery of goals [AMP94, AP98a, JBC98, Pot99, RSB98]. Although the merits and benefits of scenario based and goal based analysis in requirements engineering are well understood, researchers are now faced with the question of how to use scenarios and goals in a complimentary fashion. Several approaches, which we briefly discuss, do show promise ....

[Article contains additional citation context not shown here]

Antn, A.I., W.M. McCracken, and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering, Advanced Information Systems Engineering, 6 th International Conference Proceedings (CaiSE'94), Utrecht, The Netherlands, pp. 94-104, 6-10 June 1994.

.... Scenarios are receiving widespread attention in various intellectual communities such as objectoriented development [8, 13, 16, 24, 25] human computer interaction [11] and strategic planning [10] In the requirements engineering community, scenarios have proven effective for discovering [4, 18, 22, 23], elaborating [16, 18] refining [27] and validating [1, 7, 15] requirements. A recent study of scenario usage in industrial projects, 29] highlights the increasing need for scenario management strategies. This paper proposes an integrated strategy for scenario management that formalizes ....

....to new contexts; syntactic comparisons are easier to understand and eliminate the need to build a semantic structure. Goals as an organizing structure for scenarios Goal hierarchies are useful for representing relationships between goals and subgoals and for reasoning about goal relationships [4, 12]. The goal topography in the GBRAM [2] uses a goal hierarchy to structure and orga nize requirements information (i.e. scenarios, goal obstacles, constraints and auxiliary notes) Goal topographies help analysts find information and sort goals into naturally different functional requirements. ....

A. Anton, W. McCracken, and C. Potts. Goal Decomposition and Scenario Analysis in Business Process Reengineering. In Adv. Info. Sys. Eng.: 6th Intl. Conf., pages 94--104, June 1994.

No context found.

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pages 94-- 104, 1994.

No context found.

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94, pp. 94--104 (1994).

No context found.

A.I. Anton, M.W. McCracken, and C. Potts. Goal decomposition and scenario analysis in business process reengineering. In Proceedings of CAISE'94 , pages 94104, 1994.

No context found.

A. I. Anton, W. M. McCracken, C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering", Proc. of the 6th Conference on Advanced Information Systems Engineering pp 94-104, Utrecht, The Netherlands, 1994.

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