Combining Goals and Functional Requirements in a Scenario-based Design Process

While promising approaches to early system design using scenarios have been proposed, no design process is available that guides scenario-based development. We present a model that combines scenarios both with functions and goals. Functions are required to make the desired behaviour of some scenario happen in order to achieve one or more goals. Using this model, we propose a systematic and concrete design process that is both model-driven and data-driven. Our design process supports the transition from the current to a new system and guides the design of a new system. In addition, this process makes it possible to detect redundancy and to improve both completeness and understandability of the resulting design. We have applied our approach in real-world projects, and our experience suggests the utility of this approach.

[1]  Hermann Kaindl,et al.  An integration of scenarios with their purposes in task modeling , 1995, Symposium on Designing Interactive Systems.

[2]  Hermann Kaindl Using Hypertext for semiformal representation in requirements engineering practice , 1996, New Rev. Hypermedia Multim..

[3]  Ashok K. Goel,et al.  Functional representation as design rationale , 1993, Computer.

[4]  Mary Beth Rosson,et al.  Binding objects to scenarios of use , 1994, Int. J. Hum. Comput. Stud..

[5]  L. Suchman Plans and situated actions , 1987 .

[6]  Hermann Kaindl,et al.  A case study of decomposing functional requirements using scenarios , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[7]  Peter Johnson,et al.  Rapid prototyping of user interfaces driven by task models , 1995 .

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

[9]  Hermann Kaindl,et al.  A practical approach to combining requirements definition and object‐oriented analysis , 1997, Ann. Softw. Eng..

[10]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .

[11]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[12]  Hermann Kaindl,et al.  How to identify binary relations for domain models , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[13]  Roger C. Schank,et al.  SCRIPTS, PLANS, GOALS, AND UNDERSTANDING , 1988 .

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

[15]  Leis J.M,et al.  Proceedings of the Symposium , 1997 .

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

[17]  Allan MacLean,et al.  Design space analysis and use representations , 1995 .

[18]  Larry L. Constantine,et al.  Essential modeling: use cases for user interfaces , 1995, INTR.

[19]  Robert L. Mack Discussion: scenarios as engines of design , 1995 .

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