Added by Geoff Sauer on Oct 17, 2007.
Average rating: 3.00/5.00 (n=1)
 


Essential use cases are abstract, lightweight, technology-free dialogues of user intentions and system responsibilities that effectively capture requirements for user interface design. Employing essential use cases in typical object-oriented development processes requires designers to translate them into conventional use cases, costing time, imposing rework, and delaying work on the object-oriented development until the user interface design is complete. We describe how essential use cases can drive object-oriented development directly, without any intervening translation, allowing user interface development to proceed in parallel. Working with essential use cases yields some unexpected further benefits: analysts can take advantage of recurring patterns in essential use cases, and the crucial common vocabulary of responsibilities lets designers trace directly from the essential use cases to the objects in their design.
 
  View both works by Biddle, Robert, James Noble and Ewan Tempero  
  View all 15 works published by Constantine and Lockwood  

Please share your rating/opinion of "Essential Use Cases and Responsibility in Object-Oriented Development".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués