A design process based on a model combining scenarios with goals and functions

While promising approaches to early system design using scenarios have been proposed, no design process is available that guides scenario-based design. We present a model that combines scenarios both with functions and goals. Functions are required to make the desired behavior 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 a certain kind of 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]  Keith Price,et al.  Review of "Principles of Artificial Intelligence by Nils J. Nilsson", Tioga Publishing Company, Palo Alto, CA, ISBN 0-935382-01-1. , 1980, SGAR.

[2]  Allen Newell,et al.  The psychology of human-computer interaction , 1983 .

[3]  David E. Kieras,et al.  Towards a Practical GOMS Model Methodology for User Interface Design , 1988 .

[4]  Dan Diaper,et al.  Task Analysis for Human-Computer Interaction , 1990 .

[5]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[6]  Dean Allemang,et al.  Using functional models in automatic debugging , 1991, IEEE Expert.

[7]  P. Hsia,et al.  Scenario driven requirements analysis method , 1992, Proceedings of the Second International Conference on Systems Integration.

[8]  Peter Johnson,et al.  Human computer interaction: Psychology, task analysis, and software engineering , 1992 .

[9]  Barry Kirwan,et al.  A Guide To Task Analysis: The Task Analysis Working Group , 1992 .

[10]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

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

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

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

[14]  B. Chandrasekaran,et al.  Functional Representation and Causal Processes , 1994, Adv. Comput..

[15]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

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

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

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

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

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

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

[22]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

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

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

[25]  Alistair G. Sutcliffe,et al.  Requirements rationales: integrating approaches to requirement analysis , 1995, Symposium on Designing Interactive Systems.

[26]  Hermann Kaindl,et al.  Representing Functional Requirements and User-System Interactions , 1996 .

[27]  T.M. Duffy,et al.  Scenario-Based Design: Envisioning Work and Technology in System Development [Book Review] , 1996, IEEE Transactions on Professional Communication.

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

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

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

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

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

[33]  Hermann Kaindl,et al.  Combining Goals and Functional Requirements in a Scenario-based Design Process , 1998, BCS HCI.

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

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

[36]  Klaus Pohl,et al.  Requirements Elicitation and Validation with Real World Scenes , 1998, IEEE Trans. Software Eng..

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

[38]  Nancy G. Leveson.  Intent Specifications: An Approach to Building Human-Centered Specifications , 2000, IEEE Trans. Software Eng..