Structure and style in use cases for user interface design

Although widely employed in both object-oriented software engineering and user interface design, use cases are not well-defined. Relatively little attention has been paid to the various styles for writing the narratives that define use cases and their consequences for user interface design and software usability. Common narrative styles are presented with examples and discussions of their relative advantages and disadvantages. Essential use cases, a variant employed within usage -centered design, are contrasted with conventional use cases and scenarios. For the most efficient support of user interface design and particularly for large, complex projects, a highly -structured form of use case has evolved. New narrative elements and relationships among use cases are introduced. These include means for expressing partial or flexible ordering of interaction, relationships with business rules, as well as a clarification of the often misunderstood concept of extension that recognizes two distinct forms: synchronous and asynchronous extensions.

[1]  B. Funderburk,et al.  Mirror, Mirror... , 2004 .

[2]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

[3]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

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

[5]  John M. Carroll,et al.  Scenarios, objects, and points of view in user interface design , 2001 .

[6]  I. A N G R A H A M Task scripts , use cases and scenarios in object oriented analysis , 2022 .

[7]  Larry Constantine,et al.  Constantine on Peopleware , 1995 .

[8]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[9]  Mary Beth Rosson,et al.  Scenario-based design , 2002 .

[10]  Jonathan Lee,et al.  Analyzing User Requirements by Use Cases: A Goal-Driven Approach , 1999, IEEE Softw..

[11]  Michael T. Rock,et al.  Part 1: Framing the Issues , 2000 .

[12]  Glenford J. Myers,et al.  Structured Design , 1999, IBM Syst. J..

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

[14]  Harlan D. Mills Software Development , 1976, IEEE Transactions on Software Engineering.

[15]  Putnam P. Texel,et al.  Use Cases Combined With Booch/Omt/Uml: Process and Products , 1997 .

[16]  Brian Henderson-Sellers,et al.  Black and White Diamonds , 1999, UML.

[17]  Rex Nettleford Mirror Mirror , 1971 .

[18]  Larry L. Constantine,et al.  Software for Use - A Practical Guide to the Models and Methods of Usage-Centered Design , 1999 .

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

[20]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[21]  Kendall Scott,et al.  UML distilled - applying the standard object modeling language , 1997 .

[22]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

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

[24]  Brian Henderson-Sellers OML: Proposals to Enhance UML , 1998, UML.

[25]  Brian Henderson-Sellers,et al.  Comparing OPEN and UML: the two third-generation OO development approaches , 1999, Inf. Softw. Technol..

[26]  Dave Roberts,et al.  Designing for the User with OVID: Bridging the Gap Between Software Engineering and User Interface Design , 1998 .

[27]  Glenford J. Myers,et al.  Structured Design , 1974, IBM Syst. J..

[28]  Nuno Jardim Nunes,et al.  Wisdom—Whitewater interactive system development with object models , 2001 .

[29]  D.R. Chand,et al.  Essential systems analysis , 1986, Proceedings of the IEEE.