Goal Sketching with Activity Diagrams

Goal orientation is acknowledged as an important paradigm in requirements engineering. The structure of a goal-responsibility model provides opportunities for appraising the intention of a development. Creating a suitable model under agile constraints (time, incompleteness and catching up after an initial burst of creativity) can be challenging. Here we propose a marriage of UML activity diagrams with goal sketching in order to facilitate the production of goal-responsibility models under these constraints.

[1]  Rachel Harrison,et al.  Goal Sketching: Towards Agile Requirements Engineering , 2007, International Conference on Software Engineering Advances (ICSEA 2007).

[2]  Rachel Harrison,et al.  A lightweight technique for assessing risks in requirements analysis , 2008, IET Softw..

[3]  John B. Shoven,et al.  I , Edinburgh Medical and Surgical Journal.

[4]  J. A. Salvato.  John wiley & sons. , 1994, Environmental science & technology.

[5]  Dorit Nevo,et al.  How to avoid disappointment by design , 2007, CACM.

[6]  Václav Rajlich,et al.  Changing the paradigm of software engineering , 2006, CACM.

[7]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[8]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[9]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[10]  Alistair Cockburn,et al.  Patterns for Effective Use Cases , 2002 .

[11]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[12]  Anthony Finkelstein,et al.  A UML profile to support requirements engineering with KAOS , 2002 .

[13]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[14]  Scott W. Ambler.  The Object Primer , 1995 .

[15]  William N. Robinson,et al.  Goal Directed Analysis with Use Cases , 2004, J. Object Technol..