This presentation was prepared by Ishara Amarasekera and Nadeera Meedin based on the paper, Goal-Oriented Requirements Engineering: A Guided Tour by Axel van Lamsweerde. This presentation contains a summary of the content provided in this research paper and was presented as a paper discussion for the course, Requirements Engineering in Computer Science.

1. Goal-Oriented Requirements Engineering :A Guided
Tour by Axel van Lamsweerde
Present By :
Ishara Amarasekera
Nadeera Meedin

2. Introduction

3. Background

4. Background(Cont…)

5. Modeling Goals

6. Specifying Goals

7. • Goal verification
- Verify the requirements entail the goals identified
• Goal validation
- Validate goals generating scenarios
• Goal-based requirements elaboration
- Goal/requirement elicitation by refinement
- Goal/requirement elicitation by abstraction
- Goal Operationalization
- Analogical Reuse
- Obstacle-driven elaboration
• Conflict Management
• Goal-based negotiation
• Evolution management
Describe with a Case
Study
Goal Reasoning

8. – NFR Framework
• Modeling and Analysis of Non-functional requirements
– i*/Tropos
• Agent-oriented, also for BPR, organizational impact analysis and software
process modeling
– KAOS (Used in the research)
• Rich set of formal analysis techniques
– GBRAM
• Identification and abstraction of goals from various sources of information
The Main GORE Approaches

9. Knowledge Acquisition in autOmated
Specification[4]
or
Keep All Objects Satisfied[5]
The KAOS method

10. The KAOS method

11. • Goal identification from the initial document
• Formalizing goals and identifying objects
• Eliciting new goals through WHY questions
• Eliciting new goals through HOW questions
Goal model and object model elaboration

12. • Goal identification
from the initial
document
Uses GRAIL[2]
Clouds – soft goals
Parallelograms –
Formalizable goals
Goal model and object model elaboration

13. • Goal identification from the initial document
• Formalizing goals and identifying objects
• Eliciting new goals through WHY questions
• Eliciting new goals through HOW questions
Goal model and object model elaboration

14. • Formalizing goals and identifying objects
Goal model and object model elaboration

15. • Goal identification from the initial document
• Formalizing goals and identifying objects
• Eliciting new goals through WHY questions
• Eliciting new goals through HOW questions
Goal model and object model elaboration

16. Eliciting new goals
through
WHY questions
Goal model and object model elaboration

17. • Goal identification from the initial document
• Formalizing goals and identifying objects
• Eliciting new goals through WHY questions
• Eliciting new goals through HOW questions
Goal model and object model elaboration

18. Eliciting new goals
through
HOW questions
Goal model and object model elaboration

19. The KAOS method

20. ● Identifying potential responsibility assignments
● Deriving agent interfaces
● Identifying operations
● Identifying operationalizing goals
Elaboration of alternative agent models

21. Identifying potential
responsibility assignments
Elaboration of alternative agent models

22. ● Identifying potential responsibility assignments
● Deriving agent interfaces
● Identifying operations
● Identifying operationalizing goals
Elaboration of alternative agent models

23. Deriving agent interfaces
The agent must be able to evaluate the goal antecedent, and
establish the goal consequent
Elaboration of alternative agent models

24. ● Identifying potential responsibility assignments
● Deriving agent interfaces
● Identifying operations
● Identifying operationalizing goals
Elaboration of alternative agent models

25. Identify the operations relevant to the goals along with their
domain pre and post condition
Identifying operations
Elaboration of alternative agent models

26. ● Identifying potential responsibility assignments
● Deriving agent interfaces
● Identifying operations
● Identifying operationalizing goals
Elaboration of alternative agent models

27. Identifying operationalizing goals
Identify the trigger conditions of the identified operations relevant to
the goals
Elaboration of alternative agent models

28. The KAOS method

29. ● Anticipating obstacles
● Handling conflicts
● Evaluation and selection of alternatives
Evaluation and selection of alternatives

30. Anticipating obstacles
Achieve[CommandMsgIssuedlnTime];
CommandMsgNotlssued,
CommandMsglssuedLate,
CommandMsgSentToWrongTrain
Early generation of high level exceptions
Obstacle mitigation strategies can be used in resolving obstacles
Evaluation and selection of alternatives

31. ● Anticipating obstacles
● Handling conflicts
● Evaluation and selection of alternatives
Evaluation and selection of alternatives

32. ● Handling conflicts
Evaluation and selection of alternatives

33. • Bay Area Rapid Transit(BART) is not a Business Application
• Not to deliver an experience report but to convince to pursue in
GORE research
• Review various research efforts undertaken and the arguments
are in favour of goal orientation
• Deriving Architectural Descriptions from Goal-Oriented
Requirements Models[3]
• OpenME[7] is an Open-Source tool similar to GRAIL
Conclusion

34. [1]“ElaborationOfRequirementsUsingTheKAOSApproach < MethodEngineering < UUCS.” [Online]. Available:
http://www.cs.uu.nl/wiki/MethodEngineering/ElaborationOfRequirementsUsingTheKAOSApproach. [Accessed: 07-Feb-2014].
[2] R. Darimont, E. Delor, P. Massonet, and A. Van Lamsweerde, “GRAIL/KAOS: an environment for goal-driven requirements analysis,
integration and layout,” in , Proceedings of the Third IEEE International Symposium on Requirements Engineering, 1997, 1997, p. 140–.
[3] D. Vanderveken, A. Van Lamsweerde, D. E. Perry, and C. Ponsard, Deriving Architectural Descriptions from Goal-Oriented
Requirements Models. September, 2005.
[4] A. Dardenne, A. van Lamsweerde, and S. Fickas, “Goal-directed Requirements Acquisition,” in Selected Papers of the Sixth
International Workshop on Software Specification and Design, Amsterdam, The Netherlands, The Netherlands, 1993, pp. 3–50.
[5] A. Van Lamsweerde and E. Letier, “From object orientation to goal orientation: A paradigm shift for requirements engineering,” in
Radical Innovations of Software and Systems Engineering in the Future, Springer, 2004, pp. 325–340.
[6] D.T. Ross and K.E. Schoman, “Structured Analysis for Requirements Definition”, IEEE Transactions on Software Engineering,’ Vol. 3,
NO. 1, 1977, 6-15.
[7] “OpenOME, an requirements engineering tool.” [Online]. Available: http://www.cs.toronto.edu/km/openome/. [Accessed: 08-Feb-
2014].
References

35. THANK YOU