 |
Essential Use Cases and
Responsibility in Object-Oriented Development |
|
|
| |
Robert Biddle, James Noble, Ewan Tempero |
| |
 Report
[#113]: 2001 | Adobe .PDF File: about 276K. |
| |
Abstract: 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. |
| |
Keywords: essential use cases,
object-oriented design, object-oriented programming, responsibility-driven
design, software engineering, process, concurrent engineering |
| |
Unpublished paper, Victoria University of
Wellington, New Zealand (September 2001). |
| |
Report
[#113]: 2001 | Adobe .PDF File: about 276K. |
| |
Related Documents:
Use Cases to Objects [#123],
Handling Exceptions [#127],
Structure and Style [#106],
Process Agility [#110], Newsletter:
Implementing Designs |
|
|
| |
Note: Links are encouraged; please link to this
page, not to the .PDF file. |
