Essential Use Cases and Responsibility in Object-Oriented Development  

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.

Biddle, Robert, James Noble and Ewan Tempero. Constantine and Lockwood (2001). Articles>User Interface>Methods

From Essential Use Cases to Objects  

One of the main motivations for essential use cases was the context of user interface design. We, however, have been exploring the application of essential use cases in general object-oriented system development. Our experience has been very positive, and we found advantages to essential use cases that assist in both analysis and in design. This paper outlines two techniques involving essential use cases: use of role-play in requirements analysis, and distribution of system requirements from essential use cases to objects.

Biddle, Robert, James Noble and Ewan Tempero. Constantine and Lockwood (2003). Articles>User Interface>Methods