van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE International Symposium on Requirements Engineering (2001) 249-63 Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Towards Improved Requirements Practices in Agile Software.. - Srikanth, Antón (2002) (Correct)
....between goals and scenarios are documented in the literature [AP98, DvLF93] and employed by the ADaPT. It is easy to overlook and difficult to uncover requirements using traditional RE techniques [PTA94] Goals (the targets of achievement) and scenarios (behavioral descriptions of a system) [AP98, DvLF93, Lam01, RSB98, vLDM95, WPJ98] have proven to ensure the early identification of typically overlooked requirements [PTA94, AP98] The GBRAM (Goal Based Requirements Analysis Method) employs a goal hierarchy to structure and organize requirements information (i.e. scenarios, constraints and auxiliary notes, such as rationale) ....
A van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour, IEEE 5th Int'l Symp. on Requirements Engineering (RE'01), Toronto, Canada, pp. 249-261, 27-31 August 2001.
Goal-Mining to Examine Health Care Privacy Policies - Anton, Earp, Reese (2002) (Correct)
....electronic commerce systems [AP98] as we now discuss. 2.3.1 Goals Goals are the objectives and targets of achievement for a system. In requirements engineering, goal driven approaches focus on why systems are constructed, expressing the rationale and justification for the proposed system [Lam01]. Since goals are evolutionary, they provide a common language for analysts and stakeholders. Focusing on goals, instead of specific requirements, allows analysts to communicate with stakeholders using a language based on concepts with which they are both comfortable and familiar. Furthermore, ....
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour, IEEE 5th International Symposium on Requirements Engineering (RE'01), Toronto, Canada, pp. 249-261, 27-31 August 2001.
Developing Safety-Critical Systems with UML - Jürjens (2003) (Correct)
....GROOM UML workshop 98, OOPSLA 98, PSMT 98, ECOOP 00 workshop reader, AMCIS 00, and other conferences) Furthermore, there are techniques for requirements elicitation that can be used fruitfully with the current approach. An example is the approach of goal oriented requirements engineering [vL01] which is specifically useful for non functional requirements and which is related to UML in [SC02] Outline In Sect. 2 we explain the foundation for checking the constraints associated with the stereotypes suggested for safety critical systems development which are presented in Sect. 3, ....
Axel van Lamsweerde. Goal-oriented requirements engineering: A guided tour. In RE'01 - 5th IEEE International Symposium on Requirements Engineering, pages 249--263, Toronto, August 2001. Invited Paper.
The Context-Based Constraint Language Ccl For Components - Bubl (2002) (1 citation) (Correct)
....established that require Requirements Engineering ments management needs to be done throughout a system s lifetime. Moreover, there has been a large body of work published (e.g. 28] on the traceability of requirements. Furthermore, goal oriented requirements engineering is well established ([58]) The new approach presented here does not aim to replace these existing concepts. Instead, it is an addition to them. This work was supported by the German Federal Ministry of Education and Research as part of the research project KONTENG (Kontinuierliches Engineering fur evolutionare ....
Axel van Lamsweerde. Goal-oriented requirements engineering: A guided tour. In 5 IEEE International Symposium on Requirements Engineering, Toronto, pages 249--263. ACM Press, August 2001.
Designing for Privacy and Other Competing Requirements - Yu, Cysneiros (2002) (6 citations) (Correct)
....interpretations to be accommodated during the early stages of requirements and design. Recent advances in requirements engineering offer systematic approaches for addressing this type of requirements and model the different alternatives that might arise during tradeoffs [Potts 94] Chung 00] VanLamsweerde 01] However, they do not provide constructs to model and reason about the social dimension. In today s networked world, we need to move towards an agent oriented approach to modeling and analysis where agents can be humans, hardware and software interacting in complex ways to achieve shared or ....
....at innovative solutions that address individual as well as organizational goals. Research in goal oriented requirements engineering has provided some of the groundwork in this regard, by offering systematic techniques for discovering, refining, and addressing goals. GBRAM [Potts 94] and KAOS [VanLamsweerde 01] address goals and NFRs but do not deal with social relationships. The NFR framework [Chung 00] deals only with NFRs. How NFRs are related and impact on functional requirements is only superficially covered. i incorporates NFRs as softgoals. NFRs are eventually converted into functional ....
VanLamsweerde, A. "Goal-Oriented Requirements Engineering: A Guided Tour" Proc of the 5 IEEE Int. Symp. on Requirements Engineering, pp:249262, 2001.
A Framework for Modeling Privacy Requirements in Role Engineering - He, Anton (Correct)
....[Kay02] A complete overview of goal driven RE techniques is beyond the scope of this paper. Herein we only discuss goal scenario combination approaches. A more complete overview of goal driven RE approaches can be found in [Lam0 t, Kay02] Goals and scenarios have complementary characteristics [Lam01]. Goals are usually abstract and declarative. They are high level objectives of the business, organization 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 ....
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour, Proc. of the 5 tn International Symposium on Requirements Engineering (RE'OO, pp. 249262, IEEE, 2001.
Relating Software Requirements and Architectures.. - Hall, Jackson.. (2002) (5 citations) (Correct)
....controlled variables, and shares much in common with the problem frames approach. Its main focus, however, is on event based (control) systems, and its tabular notation has not been used to incorporate architectural considerations. A number of goal based requirements approaches, most notably KAOS [17] and the NFR framework [5] have proposed the explicit use of the notion of goals to structure requirements and, consequently, the problem domain. KAOS in particular, allows domain properties, assumptions and constraints to be represented as part of its goal based specifications. More recent ....
....the problem domain. KAOS in particular, allows domain properties, assumptions and constraints to be represented as part of its goal based specifications. More recent work by Letier and van Lamsweerde addresses the identification of agents (e.g. components) and their assignment to goals [18, 17]. The KAOS approach remains essentially goal driven and it is not clear how existing architectural artifacts can influence the problem structuring process. Similarly, the NFR framework uses high level goals to initiate a process of identification of associated design components. A very common ....
A. van Lamsweerde, "Goal-Oriented requirements Engineering: A Guided Tour", Proceedings of the 5th International Symposium on Requirements Engineering (RE'01), pp.249-261, IEEE CS Press, 2001.
From System Goals to Intruder Anti-Goals: Attack.. - van Lamsweerde.. (2003) Self-citation (Van lamsweerde) (Correct)
No context found.
A. van Lamsweerde , "Goal-Oriented Requirements Engineering: A Guided Tour", Invited Minitutorial, Proc. RE'01 - 5 Intl. Symp. Requirements Engineering, Toronto, August 2001, pp. 249-263.
Deriving Tabular Event-Based Specifications from.. - De Landtsheer.. (2003) (1 citation) Self-citation (Van lamsweerde) (Correct)
No context found.
A. van Lamsweerde , "Goal-Oriented Requirements Engineering: A Guided Tour", Invited Minitutorial, Proc. RE'01 - 5 Intl. Symp. Requirements Engineering , Toronto, August 2001, pp. 249-263.
Deriving Operational Software Specifications from System Goals - Letier, van Lamsweerde (2002) (1 citation) Self-citation (Van lamsweerde) (Correct)
.... general requires complex models to be elaborated, structured, interrelated and negotiated [29] Goal oriented requirements engineering refers to the use of goals for requirements elicitation, elaboration, organization, specification, analysis, negotiation, assignment, documentation and evolution [31]. Goals are objectives the system under consideration must achieve. The word system here refers to the software to be together with its environment [11] Goals are formulated in terms of optative statements [41] which may refer to functional or nonfunctional properties [5] and range from ....
.... properties [5] and range from high level concerns (such as safe transportation for a flight control system) to lower level ones (such as reverse thrust enabled when wheels pulse on ) There are multiple reasons why goals must be made explicit in the requirements engineering process [31]. Goals drive the elaboration of requirements to support them; they provide a criterion for requirements completeness and pertinence; they induce rich specification structuring mechanisms such as AND decomposition composition for refinement abstraction and OR decomposition for reasoning about ....
[Article contains additional citation context not shown here]
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour". Invited minitutorial, Proc. RE'01 - International Joint Conference on Requirements Engineering, Toronto, IEEE, August 2001, pp.249-263.
Agent-Based Tactics for Goal-Oriented Requirements Elaboration - Letier, van Lamsweerde (2002) (2 citations) Self-citation (Van lamsweerde) (Correct)
.... and the assignment of responsibilities for the resulting requirements to agents such as humans, devices and software [Lam00c] Goal oriented RE refers to the use of goals for requirements elicitation, elaboration, organization, specification, analysis, negotiation, documentation and evolution [Lam01]. Goals are objectives to be achieved by the system under consideration. The word system here refers to the software to be together with its environment [Fic92] Goals are formulated in terms of optative statements [Zav97] which may refer to functional or non functional properties and range ....
.... may refer to functional or non functional properties and range from high level concerns (such as safe transportation for a flight control system) to lower level ones (such as FlightPathAngle mode engaged until aircraft near desired altitude ) Goals play a prominent role in the RE process [Lam01]. They drive the elaboration of requirements to support them [Rub92, Dar93, Ant98, Kai00] They provide a criterion for requirements completeness and pertinence [Yue87] They induce rich specification structuring mechanisms such as goal AND decomposition composition for specification ....
[Article contains additional citation context not shown here]
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour". Invited minitutorial, Proc. RE'01 - International Joint Conference on Requirements Engineering, Toronto, IEEE, August 2001, pp.249-263.
RE Approach for e-Business Advantage - Steven Bleistein Karl (2004) (Correct)
No context found.
van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE International Symposium on Requirements Engineering (2001) 249-63
Validating strategic alignment of organizational IT.. - Bleistein, Cox, Verner (2006) (Correct)
No context found.
van Lamsweerde, A., 2001. Goal-oriented Requirements Engineering: A Guided Tour. In: Proceedings of the 5th IEEE International Symposium on Requirements Engineering. IEEE, Toronto.
Problem Frames Approach for e-Business Systems - Bleistein, Cox, Verner (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
Process Modeling in e-Business Systems Requirements Analysis - Steven Bleistein Computer (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
Modeling Business Strategy in E-Business Systems.. - Bleistein, Cox, Verner (2004) (Correct)
No context found.
van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE International Symposium on Requirements Engineering (2001) 249-63
Requirements Engineering for e-Business Systems.. - Problem Diagrams With (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
B-SCP: A requirements analysis framework for.. - Bleistein, Cox.. (2006) (Correct)
No context found.
A. van Lamsweerde, Goal-oriented requirements engineering: a guided tour, Presented at Fifth IEEE International Symposium on Requirements Engineering, Toronto, 2001.
Strategy-Oriented Alignment in Requirements Engineering.. - Bleistein, al. (2004) (Correct)
No context found.
VAN LAMSWEERDE, A. (2001): Goal-oriented requirements engineering: A guided tour. 5th IEEE International Symposium on Requirements Engineering. Toronto, IEEE.
Embedding Policy Rules for Software-Based Systems in a.. - Strembeck (2005) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
An Integrated Approach to Engineer and Enforce Context.. - Strembeck, Neumann (2004) (Correct)
No context found.
VAN LAMSWEERDE,A. 2001. Goal-oriented requirements engineering: A guided tour. In Proceedings of the 5th IEEE International Symposium on Requirements Engineering (RE).
A Role Engineering Tool for Role-Based Access Control - Strembeck (2005) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
Strategy-Oriented Alignment in Requirements Engineering.. - Bleistein, al. (2004) (Correct)
No context found.
VAN LAMSWEERDE, A. (2001): Goal-oriented requirements engineering: A guided tour. 5th IEEE International Symposium on Requirements Engineering. Toronto, IEEE.
Requirements Engineering for e-Business Advantage - Bleistein, Cox, Verner, Phalp (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
Modeling Business Strategy in E-Business Systems.. - Bleistein, Cox, Verner (2004) (Correct)
No context found.
van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE International Symposium on Requirements Engineering (2001) 249-63
Process Modeling in e-Business Systems Requirements Analysis - Steven Bleistein Computer (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
Problem Frames Approach for e-Business Systems - Bleistein, Cox, Verner (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour," presented at 5th IEEE International Symposium on Requirements Engineering, Toronto, 2001.
RE Approach for e-Business Advantage - Bleistein, Cox, Verner (2004) (Correct)
No context found.
van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: Proc. 5th IEEE International Symposium on Requirements Engineering (2001) 249-63
Using Runtime Introspectible Metadata to Integrate.. - Neumann, Strembeck, Zdun (2002) (1 citation) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
An agent-based requirements engineering framework for . . . - Bresciani (2003) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour, IEEE 5th Int l Symp. on Requirements Engineering, pp. 249-261, August 2001.
Bounded Model Checking for Past LTL - Benedetti, Cimatti (2003) (11 citations) (Correct)
No context found.
A. van Lamsweerde. Goal-oriented requirements engineering: A guided tour. In Proc. 5th IEEE International Symposium on Requirements Engineering, pages 249--263, 2001.
REF: a Practical Agent-Based Requirement Engineering Framework - Bresciani, Donzelli (Correct)
No context found.
A. van Lamsweerde. Goal-oriented requirements engineering: A guided tour. In Proceedings of RE'01 - International Joint Conference on Requirements Engineering, pages 249--263, Toronto, aug 2001. IEEE.
Domain ontology analysis in agent-oriented requirement engineering - Donzelli (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour, IEEE 5th Int l Symp. on Requirements Engineering, pp. 249-261, August 2001.
Composing Requirements Using Problem Frames - Robin Laney Leonor (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", Proceedings of the 5 th International Symposium on Requirements Engineering (RE'01), pp249-261, IEEE CS Press, 2001.
Developing Safety-Critical Systems with UML - Jürjens (2003) (Correct)
No context found.
Axel van Lamsweerde. Goal-oriented requirements engineering: A guided tour. In RE'01 - 5th IEEE International Symposium on Requirements Engineering, pages 249--263, Toronto, August 2001. Invited Paper.
Requirements, Architectures and Risks - James Kiper Dept (Correct)
No context found.
van Lamsweerde, A., 2001, "Goal-Oriented Requirements Engineering: A Guided Tour", Proceedings 5th IEEE International Symposium on Requirements Engineering, Toronto, Canada, August, pp. 249-2
Architecture-driven Problem Decomposition - Rapanotti, Hall, Jackson, Nuseibeh (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented requirements Engineering: A Guided Tour", Proceedings of the 5th International Symposium on Requirements Engineering (RE'01), pp.249-261, IEEE CS Press, 2001.
Using Runtime Introspectible Metadata to Integrate.. - Neumann, Strembeck, Zdun (2002) (1 citation) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
An Approach to Engineer and Enforce Context Constraints in.. - Neumann, Strembeck (2003) (5 citations) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
Problem Frames: - Coordination (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", in Proceedings of the 5 th International Symposium on Requirements Engineering (RE'01), IEEE Computer Society Press 2001, 249-261. -- 16 --
A Scenario-driven Role Engineering Process for Functional.. - Neumann, Strembeck (2002) (6 citations) (Correct)
No context found.
A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proc. of the 5th IEEE International Symposium on Requirements Engineering (RE), August 2001.
Composing Requirements Using Problem Frames - Robin Laney Leonor (2004) (Correct)
No context found.
A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", Proceedings of the 5 th International Symposium on Requirements Engineering (RE'01), pp249-261, IEEE CS Press, 2001.
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