List of references compiled by Axel van Lamsweerde and related to his tutorial on "Goal-Oriented Requirements Engineering" given on 6 Nov 2002 at Imperial College, London Posted on 5 December 2002 A. KAOS-related references: --------------------------- 1. Context, intro, background etc: 2 invited papers supposed to be readable: [Lam00c] A. van Lamsweerde, Requirements Engineering in the Year 00: A Research Perspective. Invited Keynote Paper, Proc. ICSE’2000: 22nd International Conference on Software Engineering, ACM Press, 2000, pp. 5-19. [Lam01] 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. 2. Seminal paper, experience on difficult problem [Dar93] A. Dardenne, A. van Lamsweerde and S. Fickas, Goal-Directed Requirements Acquisition, Science of Computer Programming, Vol. 20, 1993, 3-50. [Lam95] A. van Lamsweerde, R. Darimont, and Ph. Massonet, "Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learnt", Proc. RE’95 - 2nd Intl. IEEE Symp. on Requirements Engineering, March 1995, 194-203 (the language and underlying meta-model have evolved since then, that's why I suggest reading in addition the "Background" summary section of any recent paper, e.g., TSE Oct. 2000 paper on obstacles below) 3. Goal refinement papers: [Dar96] R. Darimont and A. van Lamsweerde, Formal Refinement Patterns for Goal-Driven Requirements Elaboration, Proc. FSE’4 - Fourth ACM SIGSOFT Symp. on the Foundations of Software Engineering, San Francisco, October 1996, 179-190. [Let02a] E. Letier and A. van Lamsweerde, Agent-Based Tactics for Goal-Oriented Requirements Elaboration, Proc. ICSE’02: 24th Intl. Conf. on Software Engineering, Orlando, IEEE Computer Society Press, May 2002 4. Obstacle analysis paper (+ complete goal graph for non-trivial, real system): [Lam00a] A. van Lamsweerde and E. Letier, Handling Obstacles in Goal-Oriented Requirements Engineering, IEEE Transactions on Software Engineering, Special Issue on Exception Handling, Vol. 26, No. 10, October 2000. - On run-time obstacle resolution: [Fea98] M. Feather, S. Fickas, A. van Lamsweerde, and C. Ponsard, Reconciling System Requirements and Runtime Behaviour, Proc. IWSSD’98 - 9th International Workshop on Software Specification and Design, Isobe, IEEE CS Press, April 1998. 5. Selected topics, depending on your taste: - On goal operationalization: [Let02b] E. Letier and A. van Lamsweerde, Deriving Operational Software Specifications from System Goals, Proc. FSE’10: 10th ACM SIGSOFT Symp. on the Foundations of Software Engineering, Charleston, November 2002. - On conflict management: [Lam98b] A. van Lamsweerde, R. Darimont and E. Letier, "Managing Conflicts in Goal-Driven Requirements Engineering", IEEE Trans. on Sofware. Engineering, Special Issue on Inconsistency Management in Software Development, November 1998. - On scenario-based inference of specs: TSE Dec. 98 [Lam98c] A. van Lamsweerde and L. Willemet, "Inferring Declarative Requirements Specifications from Operational Scenarios", IEEE Trans. on Sofware. Engineering, Special Issue on Scenario Management, December 1998, 1089-1114. - (On analogical reuse of goal-oriented specifications:) [Mas97] P. Massonet and A. van Lamsweerde, Analogical Reuse of Requirements Frameworks, Proc. RE-97 - 3rd Int. Symp. on Requirements Engineering, Annapolis, 1997, 26-37. All KAOS papers are downloadable from http://www.info.ucl.ac.be/research/projects/AVL/ReqEng.html 2. Other refs related to goal-oriented RE (cited on my slides): -------------------------------------------------------------- [Ant94] A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering, Proc. CAISE'94, LNCS 811, Springer-Verlag, 1994, 94-104. [Ant98] A.I. Anton and C. Potts, The Use of Goals to Surface Requirements for Evolving Systems, Proc. ICSE-98: 20th Intrnational Conference on Software Enginering, Kyoto, April 1998. [Ant01] A.I. Anton, R. Carter, A. Dagnino, J. Dempster and D.F. Siege, Deriving Goals from a Use-Case Based Requirements Specification, Requirements Engineering Journal, Vol. 6, 2001, 63-73. [Boe95] B. W. Boehm, P. Bose, E. Horowitz, and Ming June Lee, Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach, Proc. ICSE-17 - 17th Intl. Conf. on Software Engineering, Seattle, 1995, pp. 243-253. [Chu00] L. Chung, B. Nixon, E. Yu and J. Mylopoulos, Non-functional requirements in software engineering. Kluwer Academic, Boston, 2000. [Dub98] E. Dubois, E. Yu and M. Petit, "From Early to Late Formal Requirements: A Process-Control Case Study, Proc. IWSSD’98 - 9th International Workshop on Software Specification and Design, Isobe, IEEE CS Press, April 1998, 34-42. [Dwy99] M.B. Dwyer, G.S. Avrunin and J.C. Corbett, Patterns in Property Specifications for Finite-State Verification, Proc. ICSE-99: 21th International Conference on Software Enginering, Los Angeles, 411-420. [Fea87] M. Feather, Language Support for the Specification and Development of Composite Systems, ACM Trans. on Programming Languages and Systems 9(2), Apr. 87, 198-234. [Fic92] S. Fickas and R. Helm, Knowledge Representation and Reasoning in the Design of Composite Systems", IEEE Trans. on Software Engineering, June 1992, 470-482. [Jac95] M. Jackson, Software Requirements & Specifications - A Lexicon of Practice, Principles and Pejudices. ACM Press, Addison-Wesley, 1995. [Myl92] Mylopoulos, J., Chung, L., Nixon, B., Representing and Using Nonfunctional Requirements: A Process-Oriented Approach, IEEE Trans. on Sofware. Engineering, Vol. 18 No. 6, June 1992, pp. 483-497. [Myl99] J. Mylopoulos, L. Chung and E. Yu, "From Object-Oriented to Goal-Oriented Requirements Analysis", Communications of the ACM, Vol. 42 No. 1, January 1999, 31-37. [Nus94] B. Nuseibeh, J. Kramer and A. Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specifications", IEEE Transactions on Software Engineering, Vol. 20 No. 10, October 1994, 760-773. [Par95] D.L. Parnas and J. Madey, Functional Documents for Computer Systems, Science of Computer Programming, Vol. 25, 1995, 41-61. [Rob89] Robinson, W.N., Integrating Multiple Specifications Using Domain Goals, Proc. IWSSD-5 - 5th Intl. Workshop on Software Specification and Design, IEEE, 1989, 219-225. [Rol98] C. Rolland, C. Souveyet and C. Ben Achour, Guiding Goal Modeling Using Scenarios, IEEE Trans. on Sofware. Engineering, Special Issue on Scenario Management, December 1998, 1055-1071. [Ros77] D.T. Ross and K.E. Schoman, "Structured Analysis for Requirements Definition", IEEE Transactions on Software Engineering, Vol. 3, No. 1, 1977, 6-15. [Sut98] A. Sutcliffe, Scenario-Based Requirements Analysis, Requirements Engineering Journal Vol. 3 No. 1, 1998, 48-65. [Yue87] K. Yue, What Does It Mean to Say that a Specification is Complete?, Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987. [Yu93] E.S.K. Yu, "Modelling Organizations for Information Systems Requirements Engineering", Proc. RE'93 - 1st Intl Symp. on Requirements Engineering, IEEE, 1993, 34-41. [Yu97] E. Yu, Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering, Proc. RE-97 - 3rd Int. Symp. on Requirements Engineering, Annapolis, 1997, 226-235. [Zav97a] P. Zave and M. Jackson, "Four Dark Corners of Requirements Engineering", ACM Transactions on Software Engineering and Methodology, 1997, 1-30.