The use of goals to surface requirements for evolving systems

This paper addresses the use of goals to surface requirements for the redesign of existing or legacy systems. Goals are widely recognized as important precursors to system requirements, but the process of identifying and abstracting them has not been researched thoroughly. We present a summary of a goal-based method (GBRAM) for uncovering hidden issues, goals, and requirements and illustrate its application to a commercial system, an Intranet-based electronic commerce application, evaluating the method in the process. The core techniques comprising GBRAM are the systematic application of heuristics and inquiry questions for the analysis of goals, scenarios and obstacles. We conclude by discussing the lessons learned through applying goal refinement in the field and the implications for future research.

[1]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

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

[3]  Douglas Schuler,et al.  Participatory Design: Principles and Practices , 1993 .

[4]  Martin S. Feather,et al.  Language support for the specification and development of composite systems , 1987, TOPL.

[5]  Michael Jackson,et al.  Problems, methods and specialization , 1994, IEEE Software.

[6]  Colin Potts,et al.  Using schematic scenarios to understand user needs , 1995, Symposium on Designing Interactive Systems.

[7]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[8]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[9]  Gregory D. Abowd,et al.  MORALE. Mission ORiented Architectural Legacy Evolution , 1997, 1997 Proceedings International Conference on Software Maintenance.

[10]  Michael Jackson,et al.  Problems, methods and specialisation , 1994, Softw. Eng. J..

[11]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[12]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[13]  Anthony Finkelstein,et al.  ViewPoint Oriented Software Development , 1990 .

[14]  Leonard J. Bass,et al.  Scenario-based evaluation of software architectures: a case study on internet information systems , 1995 .

[15]  Steve M. Easterbrook,et al.  Domain modelling with hierarchies of alternative viewpoints , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[16]  Eric S. K. Yu,et al.  Using non-functional requirements to systematically support change , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[17]  Stephen Fickas,et al.  Goal-directed concept acquisition in requirements elicitation , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

[18]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[19]  Ana I. Anton,et al.  Goal identification and refinement in the specification of software-based information systems , 1997 .

[20]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[21]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[22]  Kenji Takahashi,et al.  An active hypertext model for system requirements , 1993, Proceedings of 1993 IEEE 7th International Workshop on Software Specification and Design.

[23]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

[24]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[25]  Meir M. Lehman,et al.  Program evolution: processes of software change , 1985 .

[26]  Annie I. Antón,et al.  Managing Use Cases During Goal-Driven Requirements Engineering: Challenges Encountered and Lessons Learned , 1999 .

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

[28]  Annie I. Antón,et al.  A Web-based requirements analysis tool , 1996, Proceedings of WET ICE '96. IEEE 5th Workshop on Enabling Technologies; Infrastucture for Collaborative Enterprises.

[29]  Luqi.  Software evolution through rapid prototyping , 1989, Computer.

[30]  John S. Anderson,et al.  Using scenarios in deficiency-driven requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.