[bib01entry01] W. S., Adolph, 1996. “Cash Cow in the Tarpit: The Reengineering of a Legacy System.” IEEE Software, May.

[bib01entry02] ———. 2000. “Lost in Chaos: A Chronology of a Failure.” Software Development Magazine, January.

[bib01entry03] Christopher Alexander,. <year>1979</year>. The Timeless Way of Building. New York: Oxford University Press.

[bib01entry04] ———. <year>1977</year>. A Pattern Language. New York: Oxford University Press.

[bib01entry05] Edward V. Berard, <year>1998</year>. Be Careful with Use Cases.

[bib01entry06] Barry W. Boehm, <year>1981</year>. Software Engineering Economics. Englewood Cliffs, N.J.: Prentice-Hall.

[bib01entry07] Frederick P., Brooks,, Jr. <year>1995</year>. The Mythical Man Month Anniversary Edition: Essays on Software Engineering. Reading, Mass: Addison-Wesley.

[bib01entry08] ———. 1987. “No Silver Bullet: Essence and Accidents of Software Engineering.” IEEE Computer, Vol. 20, No. 4, April.

[bib01entry09] W. J., Brown, et al. <year>1998</year>. Anti-Patterns, Refactoring Software, Architectures, and Projects in Crisis. New York: John Wiley & Sons.

[bib01entry10] Alistair Cockburn,. <year>1998</year>. Surviving Object-Oriented Projects. Reading: Addison-Wesley.

[bib01entry11] ———. <year>2001</year>. Writing Effective Use Cases. Boston: Addison-Wesley.

[bib01entry12] ———. <year>2002</year>. Agile Software Development. Boston: Addison-Wesley.

[bib01entry13] Constantine, Larry, and Lucy Lockwood. <year>1999</year>. Software for Use. Reading: Addison-Wesley.

[bib01entry14] Jim Coplien,. <year>1996</year>. “Software Patterns.” SIGS Management Briefings, p. 7.

[bib01entry15] ———. 1998. Lecture to the Phoenix Patterns Group, Phoenix, Ariz.

[bib01entry16] Martin Fowler,. <year>1999</year>. Refactoring. Reading, Mass.: Addison-Wesley.

[bib01entry17] Richard Gabriel,. <year>1996</year>. Patterns of Software. New York: Oxford University Press, p. 56.

[bib01entry18] E., Gamma, et al. <year>1995</year>. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, Mass.: Addison-Wesley.

[bib01entry19] Ian Graham,. 1997. Remarks at Andy Pol's OOPSLA Workshop. Atlanta.

[bib01entry20] I., Jacobson, et al. <year>1992</year>. Object-Oriented Software Engineering: A Use Case Driven Approach. Reading, Mass.: Addison-Wesley.

[bib01entry21] ———. <year>1995</year>. The Object Advantage: Business Process Reengineering with Object Technology. ACM Press.

[bib01entry22] Andy Kraus,. 1996. “Use Case Blue.” Object Magazine, May, pp. 63–65.

[bib01entry23] C. Larman, <year>2002</year>. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, 2nd Edition. Prentice-Hall.

[bib01entry24] Susan Lilly,. 1999. “Use Case Pitfalls: Top 10 Problems from Real Projects Using Use Cases.” Proceedings of the TOOLS USA '99, IEEE Computer Society.

[bib01entry25] Arthur Marx,. <year>1972</year>. Son of Groucho. New York: McKay.

[bib01entry26] A. J. Riel, <year>1996</year>. Object-Oriented Design Heuristics. Reading, Mass.: Addison-Wesley.

[bib01entry27] Linda Rising,. <year>1998</year>. The Patterns Handbook: Techniques, Strategies and Applications. Cambridge: Cambridge University Press.

[bib01entry28] ———. <year>2000</year>. The Pattern Almanac. Boston, Mass.: Addison-Wesley.