Next: About this document
Up: Essential Use Cases and
Previous: Conclusions
References
- 1
-
Christopher Alexander.
The Timeless Way of Building.
Oxford University Press, 1979.
- 2
-
Frank Armour and Granville Miller.
Advanced Use Case Modeling: Software Systems, Volume 1.
Addison-Wesley, 2001.
- 3
-
Kent Beck.
Embracing change with extreme programming.
IEEE Computer, 32(10):70-77, October 1999.
- 4
-
Kent Beck and Ward Cunningham.
A laboratory for teaching object-oriented thinking.
In Proc. of OOPSLA-89: ACM Conference on Object-Oriented
Programming Systems Languages and Applications, pages 1-6, 1989.
- 5
-
David Bellin and Susan Suchman Simone.
The CRC Card Book.
Addison-Wesley, 1997.
- 6
-
Robert Biddle, James Noble, and Ewan Tempero.
Patterns for essential use cases.
In Proceedings of KoalaPLoP 2001, 2001.
To appear.
- 7
-
Marc Bradac and Becky Fletcher.
A pattern language for developing form style windows.
In Robert Martin, Dirk Riehle, and Frank Buschmann, editors,
Pattern Languages of Program Design, volume 3, pages 347-358.
Addison-Wesley, 1988.
- 8
-
Alistair Cockburn.
Writing effective use cases.
Addison-Wesley, 2001.
- 9
-
Larry L. Constantine and Lucy A. D. Lockwood.
Software for Use: A Practical Guide to the Models and Methods of
Usage Centered Design.
Addison-Wesley, 1999.
- 10
-
Martin Fowler.
Analysis Patterns.
Addison-Wesley, 1997.
- 11
-
Martin Fowler.
Refactoring: Improving the Design of Existing Code.
Addison-Wesley, 1999.
- 12
-
Erich Gamma, Richard Helm, Ralph E. Johnson, and John Vlissides.
Design Patterns.
Addison-Wesley, 1994.
- 13
-
Neil Harrison, Brian Foote, and Hans Rohnert, editors.
Pattern Languages of Program Design, volume 4, chapter Part 7:
Patterns of Human-Computer Interaction, pages 445-593.
Addison-Wesley, 2000.
- 14
-
Brian Henderson-Sellers, Anthony Simons, and Houman Younessi.
The OPEN toolbox of techniques.
Addison-Wesley, 1998.
- 15
-
Ivar Jacobson.
The Object Advantage : Business Process Reengineering With
Object Technology.
Addison-Wesley, 1995.
- 16
-
Ivar Jacobson, Grady Booch, and James Rumbaugh.
The Unified Software Development Process.
Addison-Wesley, 1999.
- 17
-
Ivar Jacobson, Mahnus Christerson, Patrik Jonsson, and Gunnar Overgaard.
Object-Oriented Software Engineering.
Addison-Wesley, 1992.
- 18
-
Dean Leffingwell and Don Widrig.
Managing Software Requirements: A Unified Approach.
Addison-Wesley, 2000.
- 19
-
Mikael Lindvall and Kristian Sandahl.
Practical implications of traceability.
Software--Practice and Experience, 26(10):1161-1180, October
1996.
- 20
-
Pete McBreen.
When are use cases done?
OOTips web site at
http://ootips.org/use-cases-done.html
,
January 1998.
- 21
-
Shari Lawrence Pfleeger.
Software Engineering: Theory and Practice.
Prentice Hall, 1998.
- 22
-
Doug Rosenberg and Kendall Scott.
Use case driven object modeling with UML: A practical
approach.
Addison-Wesley, 1999.
- 23
-
James Rumbaugh, Ivar Jacobson, and Grady Booch.
The Unified Modeling Language Reference Manual.
Addison-Wesley, 1998.
- 24
-
Nancy Wilkinson.
Using CRC Cards - An Informal Approach to OO Development.
Cambridge University Press, 1996.
- 25
-
Rebecca Wirfs-Brock and Brian Wilkerson.
Object-oriented design: A responsibility-driven approach.
In Norman Meyrowitz, editor, Proc. of OOPSLA-89: ACM Conference
on Object-Oriented Programming Systems Languages and Applications, pages
71-75, 1989.
- 26
-
Rebecca Wirfs-Brock, Brian Wilkerson, and Lauren Wiener.
Designing Object Oriented Software.
Prentice Hall, 1990.
- 27
-
Rebecca J. Wirfs-Brock.
Designing scenarios: Making the case for a use case framework.
The Smalltalk Report, 3(3), 1993.
- 28
-
Rebecca J. Wirfs-Brock.
The art of meaningful conversations.
The Smalltalk Report, 4(5), 1994.
Robert Biddle
Sun May 20 12:22:36 NZST 2001