Linking soft systems and use-case modelling through scenarios

Abstract Scenarios are fundamental to the description and comprehension of systems of any type. They can therefore provide a common base when attempting to combine different modelling approaches. This paper considers their particular role in linking Soft Systems Methodology (SSM) and Use-case modelling. It does so in the context of examining the potential gain from using these techniques in combination. SSM supports strategic planning for business design or improvement. This involves the development of system models to identify the activities that an organisation must perform to meet its goals. Use-case modelling is a requirements engineering technique that similarly leads to the identification of system activities, but is driven more by the needs of the system's ‘users’ than those of the system itself. These different but complementary perspectives suggest that either technique can be used to help validate the other's models. This seems particularly valuable in the development of information systems. More significantly, however, SSM emerges as a way of enhancing Use-case development and UML in general.

[1]  Desmond Greer.  SERUM - Software Engineering Risk: Understanding and Management , 1997 .

[2]  John Mingers,et al.  The Use of Soft Systems Methodology in Practice , 1992 .

[3]  C. A. R. Hoare,et al.  Communicating sequential processes , 1978, CACM.

[4]  John Mingers.  Using Soft Systems Methodology in the Design of Information Systems , 1995 .

[5]  Alistair Cockburn,et al.  Goals and Use Cases , 1997, J. Object Oriented Program..

[6]  Alistair Cockburn,et al.  Using Goal-Based Use Cases , 1997, J. Object Oriented Program..

[7]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[8]  Gerald M. Weinberg,et al.  Reviews, Walkthroughs, and Inspections , 1984, IEEE Transactions on Software Engineering.

[9]  Ivar Jacobson,et al.  The object advantage - business process reengineering with object technology , 1994 .

[10]  Des Greer,et al.  Prioritisation of system changes using cost-benefit and risk assessments , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[11]  Peter Checkland,et al.  Soft Systems Methodology in Action , 1990 .

[12]  Brian Wilson,et al.  Systems: Concepts, Methodologies, and Applications , 1990 .

[13]  David W. Bustard,et al.  Models to promote effective system change , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[14]  David W. Bustard,et al.  A framework for the revolutionary planning and evolutionary implementation of a business process and its computing support , 1998 .

[15]  David W. Bustard,et al.  Integrating soft systems and object-oriented analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[16]  P J Lewis.  Information-Systems Development: Systems Thinking in the Field of Information-Systems , 1993 .

[17]  John M. Carroll,et al.  Five reasons for scenario-based design , 2000, Interact. Comput..

[18]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[19]  J.M. Carrol,et al.  Five reasons for scenario-based design , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[20]  David W. Bustard,et al.  Enhancing soft systems analysis with formal modelling , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).