A multi-view approach for requirements analysis using goal and scenario

As systems get complex, requirements elicitation and analysis are becoming increasingly difficult and important in software development. Even though various analysis methods have been proposed, including scenario‐based analysis, goal‐based analysis, combining goal with scenario and use case‐driven analysis – each method has its own strengths and weaknesses and do not support requirements elicitation and analysis efficiently. This paper proposes a multi‐view approach to analyze the requirements of complex software systems. The multi‐view approach comprises four views, which incorporate many factors that are part of existing methods. This paper discusses the need for these four views, the activities that are part of each view and how they are carried out. As a proof of concept, we apply the multi‐view approach to an automatic teller machine system development.

[1]  Mikael Lindvall,et al.  Evaluating software architectures , 2004, Adv. Comput..

[2]  Heng-Li Yang,et al.  A three-stage model of requirements elicitation for Web-based information systems , 2003, Ind. Manag. Data Syst..

[3]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[4]  Sooyong Park,et al.  A method and tool support for variant requirements analysis: goal and scenario based approach , 2004, 11th Asia-Pacific Software Engineering Conference.

[5]  John Mylopoulos,et al.  Why Goal-Oriented Requirements Engineering , 1998, Requirements Engineering: Foundation for Software Quality.

[6]  Y. Helio Yang Software quality management and ISO 9000 implementation , 2001, Ind. Manag. Data Syst..

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

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

[9]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[10]  Eric Yu,et al.  From Requirements to Architectural Design –Using Goals and Scenarios , 2001 .

[11]  Julio Cesar Sampaio do Prado Leite,et al.  Requirements Validation Through Viewpoint Resolution , 1991, IEEE Trans. Software Eng..

[12]  David C. Yen,et al.  A manager’s guide to total quality software design , 1998 .

[13]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

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

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

[16]  A. Gupta,et al.  A stakeholder analysis approach for interorganizational systems , 1995 .

[17]  Patrick Heymans,et al.  A reuse-Oriented Approach for the Construction of Scenario Bases Methods , 1997 .

[18]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .