Essential Use Cases and Responsibility in Object-Oriented Development

Essential use cases are abstract, lightweight, technology-free dialogues of user intention and system responsibility that effectively capture requirements for user interface design. We describe how essential use cases can also drive object-oriented development directly, without any intervening translation, and allowing user interface development and object-oriented development to proceed in parallel. Working with essential use cases yields some unexpected further benefits: the crucial common vocabulary of responsibilities lets designers trace directly from the essential use cases to the objects in their design.

[1]  Mikael Lindvall,et al.  Practical implications of traceability , 1996 .

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

[3]  Martin Fowler,et al.  Refactoring - Improving the Design of Existing Code , 1999, Addison Wesley object technology series.

[4]  Doug Rosenberg,et al.  Use case driven object modeling with UML: a practical approach , 1999 .

[5]  Frank Armour,et al.  Advanced Use Case Modeling: Software Systems , 2000 .

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

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

[8]  Ian M. Graham,et al.  Task scripts, use cases and scenarios in object oriented analysis , 1996, Object Oriented Syst..

[9]  Rebecca Wirfs-Brock,et al.  Designing object-oriented software , 1990 .

[10]  Nancy M. Wilkinson.  Using CRC cards: an informal approach to object-oriented development , 1995 .

[11]  Brian Henderson-Sellers,et al.  The OPEN toolbox of techniques , 1998 .

[12]  Kent Beck,et al.  A laboratory for teaching object oriented thinking , 1989, OOPSLA 1989.

[13]  David Bellin,et al.  The CRC card book , 1997 .

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

[15]  Rebecca Wirfs-Brock,et al.  Object-oriented design: a responsibility-driven approach , 1989, OOPSLA 1989.

[16]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[17]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[18]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[19]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[20]  Ewan D. Tempero,et al.  Supporting Reusable Use Cases , 2002, ICSR.

[21]  James Noble,et al.  Sokoban: a system object case study , 2002 .