1 / 34

GRL Introduction

GRL Introduction. Lin Liu University of Toronto April 2001. Why Goal-Orientation?? van Lamsweerde (ICSE 2000). Systematic derivation of requirements from goals Goals provide rationales for requirements

gianna
Télécharger la présentation

GRL Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GRL Introduction Lin Liu University of Toronto April 2001

  2. Why Goal-Orientation??van Lamsweerde (ICSE 2000) • Systematic derivation of requirements from goals • Goals provide rationales for requirements • Goal refinement structure provides a comprehensible structure for the requirements document • Alternative goal refinements and agent assignments allow alternative system proposals to be explored • Goal formalization allows refinements to be proved correct and complete.

  3. Where Are We?? object-oriented programming GRL KAOS UCM SDL UML Detailed design Architectural design Late requirements Implementation [Mylopoulos AOIS’99]

  4. Development-World modelrefers to and reasons about… Alt-1 Alt-2 To-be As-is Operational-World models

  5. Outline 1. Goal-oriented modeling concepts in GRL 2. An example goal-oriented non-functional requirement analysis process 3. Combined use of goal and scenario from requirement to architectural design 4. Agent-oriented concepts in GRL 5. Related works

  6. Goals and Softgoals in GRL

  7. Tasks in GRL

  8. Goal Refinement: Means-ends Link Task Refinement: Decomposition Link

  9. Softgoal Operationalizations: Contribution Relationship Side-effects to softgoals: Correlation Relationship

  10. Resource in GRL

  11. Non-Intentional Elements in GRL • Acting as parameters in GRL intentional elements, i.e., topics of softgoal, “Object” attributes of goal, task and belief • Referring to entities of an external model, such as responsibilities in UCM, class/objects in UML class diagram,…

  12. Convergence of media reduces cost of ownership Belief in GRL

  13. Outline 1. Goal-oriented modeling concepts in GRL 2. An example goal-oriented requirement analysis process 3. Combined use of goal and scenario from requirement to architecture design 4. Agent-oriented concepts in GRL 5. Related works

  14. Softgoal Operationalization Example

  15. Softgoal Operationalization Example(cont’d)

  16. Example (cont’d)

  17. Example (cont’d)

  18. Outline 1. Goal-oriented modeling concepts in GRL 2. An example goal-oriented requirement analysis process 3. Combined use of goal and scenario from requirement to architecture design 4. Agent-oriented concepts in GRL 5. Related works

  19. Goal model in GRL

  20. An Original unbounded UCM scenario corresponding to Goal “Call Services Be Supported”

  21. Bounded UCM scenarios of Solutions: Reside VoiceCoder in (1) Base Station; or (2) in Switch

  22. Design Alternatives & Their Contributions to NFRs

  23. Outline 1. Goal-oriented modeling concepts in GRL 2. An example goal-oriented requirement analysis process 3. Combined use of goal and scenario from requirement to architecture design 4. Agent-oriented concepts in GRL 5. Related works

  24. Agent-Orientation in GRL • Actors are semi-autonomous, partially knowable • Strategic actors, intentional dependencies • Can be considered as goal-holders “Strategic Dependency” Model Meeting Scheduling Example

  25. Revealing goals, finding alternatives • Asking “Why”, “How”, “How else”

  26. Scheduling meeting …with meeting scheduler Consider • Technology as enabler • Networked systems and organizations • Increased inter-dependency and vulnerability • Limited knowledge and control • Openness and uncertainties • Cooperation • Boundaries, locality, identity

  27. Distributed Goal Model with Meeting Scheduler • SR2

  28. Outline 1. Goal-oriented modeling concepts in GRL 2. An example goal-oriented requirement analysis process 3. Combined use of goal and scenario from requirement to architecture design 4. Agent-oriented concepts in GRL 5. Related works

  29. Goal-Oriented Requirements Engineering (GORE) • GORE is gathering momentum • CSD – Feather 87… • KAOS – van Lamsweerde, … • Inquiry Cycle – Potts, Anton • EKD – Bubenko, Rolland, Loucopoulos • Win-Win – Boehm • NFR – Chung, Mylopoulos, … Hopefully, MOMENTUM >>> • Z.URN proposal to ITU-T (Nov. 2000) • GRL

  30. Goal + scenario in RE and in Architectural Design • Krutchen’s 4+1 model of software architecture • Software Architecture Analysis Method (SAAM) • Van Lamsweerde and Willement • CREWS-L’Ecritoire approach of Collete Rolland et al.

  31. Resources regarding GRL Home of GRL • http://www.cs.toronto.edu/km/GRL/ Tool web site • http://www.cs.toronto.edu/km/OME/ References: • Chung, L., Nixon, B.A., Yu, E.and Mylopoulos, J. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000. • Yu, E. and Mylopoulos, J. Why Goal-Oriented Requirements Engineering. In Proceedings of the 4th International Workshop on Requirements Engineering: Foundations of Software Quality. June 1998, Pisa, Italy. E. Dubois, A.L. Opdahl, K. Pohl, eds. Presses Universitaires de Namur, 1998. pp. 15-22. Also at: http://www.cs.toronto.edu/~eric

More Related