Goal sketching with activity diagrams

Download

[thumbnail of ICSEA_2008_paper_228_Boness_And_Harrison.pdf]

Preview

Text
- Accepted Version

Advice

Please see our End User Agreement.

It is advisable to refer to the publisher's version if you intend to cite from this work. See Guidance on citing.

Tools

Lists

Boness, K. D. and Harrison, R. (2008) Goal sketching with activity diagrams. In: Third International Conference on Software Engineering Advances (ICSEA 2008), 26-31 Oct 2008, Sliema, Malta, pp. 277-283.

Abstract/Summary

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.

Item Type	Conference or Workshop Item (Paper)
URI	https://reading-clone.eprints-hosting.org/id/eprint/6060
Refereed	Yes
Divisions	Science > School of Mathematical, Physical and Computational Sciences > Department of Computer Science
Uncontrolled Keywords	Activity Diagram, Agile, Goal, GORE, Requirements
Download/View statistics	View download statistics for this item

Download Statistics

Downloads

Downloads per month over past year

Deposit Details

Date Deposited:	03 Sep 2010 09:08	Date item deposited into CentAUR
Last Modified:	17 Dec 2023 13:49	Date item last modified

References

[i] Dardenne, A., Lamsweerde A., van, and Fikas, S., “Goal- Directed Requirements Acquisition”, Science of Computer Programming Vol. 20, pp. 3-50, North Holland., 1993, pp. 3-50. [ii] Boness, K., Harrison, R., Finkelstein, A., “A lightweight technique for assessing risk in requirements analysis”, Software, IET, 2008, Volume: 2, Issue: 1 pp. 46-57. [iii] Nevo, D., and Wade, M., “How to avoid disappointment by design”, Communications of the ACM, 2007, Vol 50, No.4 . [iv] Boness, K., and Harrison, R, “Goal Sketching: Towards Agile Requirements Engineering”, Proceedings of the International Conference on Software Engineering Advances, ICSEA 2007, pp. 71-76 [v] Cockburn, A., Writing Effective Use Cases, Addison- Wesley, Boston, 2001. [vi] Jackson, M., Requirements Specifications – A lexicon of practice, principles and prejudices, Addison-Wesley, Harlow. 1995. [vii] Guidelines for writing system requirements specifications, IEEE Std 1223-1998. [viii] Jackson, M., Problem Frames, Michael Jackson, Addison Wesley, Harlow. 2001 [ix] Alexander, I., Maiden, N., Scenarios, Stories and Use Cases, John Wiley & Sons, Chichester. 2004. [x] Rajlich, V., “Changing the paradigm of software engineering”, Comm. of the ACM, Vol 49, No.8, 2006. [xi] Ambler, S., The Object Primer, Cambridge University Press, 2004. [xii] Alexander, I, and Stevens, R., Writing Better Requirements, Addison-Wesley, Harlow, 2002. [xiii ] Robinson, W., and Elofson, N., “Goal Directed Analysis with Use Cases”, Journal of Object Technology, vol 3, no. 5, pp. 125-14. 22004, [xiv] Lamsweerde, A., van, and Willemet, L. “Inferring declarative Requirements from Operational Scenarios”, IEEE Trans on Software Engineering, Special Edition on Scenario Management. 1998. [xv] Rolland, C., and Souveyet, C., et. al., “Guiding Modelling using Scenarios”, IEEE Transactions on Software Engineering 24(12), pp.1055-1219. 1998. [xvi] Heaven, W., and Finkelstein, A., “UML profile to support requirements engineering with KAOS”, IEE Proceedings -Volume 151, Issue 1, 9, pp. 10 – 27. 2004. [xvii] Sommerville, I., and Sawyer, P., Requirements Engineering – a good practice guide, Wiley, Chichester. 1997. [xviii] Adolph , S, and Bramble, P., Patterns for effective Use Cases, Addison-Wesley, 2003

University Staff: Request a correction | Centaur Editors: Update this record

Search Google Scholar