 |
From Essential Use Cases to Objects |
|
|
| |
Robert Biddle, James Noble, Ewan Tempero |
| |
 Reprint
[#123]: 2003 | Adobe .PDF File: about 1.2M. |
| |
Abstract: 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. |
| |
Keywords: essential use cases,
object-oriented design, object-oriented programming, responsibility-driven
design, software engineering, process, concurrent engineering |
| |
Reprint of chapter from L. Constantine
(ed), forUSE 2002 Proceedings of the First International Conference on
Usage-Centered, Task-Centered, and Performance-Centered Design.
Rowley, MA: Ampersand Press, 2002. For more details and to order,
click here. |
| |
Reprint
[#123]: 2003 | Adobe .PDF File: about 1.2M. |
| |
Related Documents:
Use Cases and Responsibility [#113],
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. |
