
References
*Andriole, Stephen J. (1996) Managing Systems Requirements : Methods, Tools, and
Cases, McGraw-Hill.
Basili V., and D. Weiss (1981) Evaluation of a Software Requirements Document by
Analysis of Change Data, Fifth International Conference on Software Engineering,
Computer Society Press of the IEEE.
Bellin, David and Susan S. Simone (1997), The CRC Card Book, Addison-Wesley.
Boehm, Barry W. (1988) “Understanding and Controlling Software Costs”, IEEE
Transactions on Software Engineering, Vol.14, No. 10, October.
Boehm, Barry W. (1996) “Anchoring the Software Process”, IEEE Software, July, pp. 7382.
*Boehm, Barry W. (1998) “A Spiral Model of Software Development and
Enhancement”, IEEE Computer, May, pp. 61-72.
Booch, Grady (1994) Object-Oriented Analysis and Design with Applications, AddisonWesley.
Booch, Grady (1996) Object Solutions : Managing the Object-Oriented Project,
Addison-Wesley.
Booch, Grady and Ed Eykholt (Editor). (1996) The Best of Booch : Designing Strategies
for Object Technology, SIGS Books and Multimedia.
Booch, Grady, Jim Rumbaugh and Ivar Jacobson (1998) The Unified Modeling
Language, Documentation Set, version 1.3, Rational Software.
*Booch, Grady, Jim Rumbaugh and Ivar Jacobson (1999) The Unified Modeling
Language User Guide, Addison-Wesley.
Brooks, Frederick P. Jr. (1995) The Mythical Man-Month : Essays on Software
Engineering (Anniversary Edition), Addison-Wesley.
Buschmann, Frank, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal
(1996) Pattern Oriented Software Architecture: A System of Patterns, John Wiley &
Sons.
*Cockburn, Alistair (1997) “Structuring Use Cases with Goals”, Journal of ObjectOriented Programming, (Part I) Sep-Oct, (Part II) Nov-Dec (also available on his
web page at http://members.aol.com/acockburn/).
Cockburn, Alistair (1998) Surviving Object-Oriented Projects: A Manager's Guide,
Addison-Wesley.
Crosby, Philip B.(1979) Quality is Free: The Art of Making Quality Certain, Mentor
(Penguin).
Cusumano, Michael A. and Richard W. Selby (1995) Microsoft Secrets: How the World’s
* Recommended Reading
R-1
Requirements Management with Use Cases
Most Powerful Software Company Creates Technology, Shapes Markets, and
Manages People, The Free Press.
Davis, Alan M. (1993) Software Requirements: Objects, Functions, and States, Prentice
Hall.
Davis, Alan M. (1995) 201 Principles of Software Development, McGraw Hill.
Davis, Alan M. (1995) “Software Prototyping”, Advances in Computers, Vol. 40.
Demarco, Tom (1995) Why Does Software Cost So Much? : And Other Puzzles of the
Information Age, Dorset House Publishing.
Dion, Raymond (1993) “Process Improvement and the Corporate Balance Sheet,” IEEE
Software, 10, 4, July.
Dorfman, M. and Richard H. Thayer (Editors). (1997) Software Engineering, IEEE
Computer Society Press.
Douglass, Bruce P. (1998) Real-Time UML: Developing Efficient Objects for Embedded
Systems, Addison-Wesley.
Eeles, Peter and Oliver Sims (1998) Building Business Objects, John Wiley & Sons.
Eriksson, Hans-Erik and Magnus Penker (1998) UML Toolkit, John Wiley & Sons.
Fenton, Norman E. and Shari L. Pfleeger (1997) Software Metrics: A Rigorous and
Practical Approach, PWS Publishing Company.
Firesmith, Donald G. and Edward M. Eykholt (1995) Dictionary of Object Technology,
SIGS Books.
*Fisher, Roger, William Ury and Bruce Patton (Editor). (1991) Getting to Yes:
Negotiating Agreement Without Giving in (Second Edition), Penguin Books.
Fowler, Martin (1997) Analysis Patterns: Reusable Object Models, Addison-Wesley.
**Fowler, Martin (1999) UML Distilled, Second Edition: Applying the Standard Object
Modeling Language, Addison-Wesley.
Gamma, Erich, Richard Helm, Ralph Johnson, and John Vlissides (1995) Design
Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley.
Gause, Donald C. and Gerald M. Weinberg (1990) Are Your Lights On?: How to Figure
Out What the Problem REALLY Is, Dorset House Publishing.
**Gause, Donald C. and Gerald M. Weinberg (1989) Exploring Requirements: Quality
Before Design, Dorset House Publishing.
Goldberg, Adele, and Kenneth S. Rubin (1995) Succeeding With Objects: Decision
Frameworks for Project Management, Addison-Wesley.
*Grady, Robert B. (1992) Practical Software Metrics for Project Management and
Process Improvement, Prentice Hall.
Graham, Ian (1995) Migrating to Object Technology (Book and Disk), Addison-Wesley.
Harmon, Paul and Mark Watson (1998) Understanding UML: The Developer's Guide:
With a Web-Based Application In Java, Morgan Kaufmann.
R-2
Reading
* Recommended
References
Heinckiens, Peter M. (1998) Building Scalable Database Applications: Object-Oriented
Design, Architectures, and Implementations, Addison- Wesley.
Hohmann, Luke (1997) Journey of the Software Professional: The Sociology of Software
Development, Prentice Hall.
*Humphrey, Watts S. (1989) Managing the Software Process, Addison-Wesley.
Humphrey, Watts S., et al. (1991) “Software Process Improvement at Hughes Aircraft,”
IEEE Software, July.
Humphrey, Watts S. (1997) Introduction to the Personal Software Process, AddisonWesley.
*IEEE 830-1994, “Recommended Practice for Software Requirements Specifications”,
Software Engineering Standards Committee of the IEEE Computer Society.
IEEE 829-1983, “Standard for Software Test Documentation”, Software Engineering
Standards Committee of the IEEE Computer Society.
ISO 9000-3 (1991) “Guidelines for the Application of ISO 9001 to the Development,
Supply, and Maintenance of Software”, International Organization for
Standardization, Geneva.
Jackson, Michael (1995) Software Requirements & Specifications: a lexicon of practice,
principles and prejudices, Addison-Wesley.
*Jacobson, Ivar, et al (1992) Object-Oriented Software Engineering: A Use Case Driven
Approach, Addison-Wesley.
*Jacobson, Ivar, M. Ericsson and A. Jacobson (1994) The Object Advantage : Business
Process Reengineering With Object Technology, Addison-Wesley.
Jacobson, Ivar, et al. (1997) Software Reuse: Architecture Process and Organization for
Business Success, ACM Press and Addison-Wesley.
*Jacobson, Ivar, Grady Booch and Jim Rumbaugh (1999) The Unified Software
Development Process, Addison-Wesley.
Katzenbach, Jon R. and Douglas K. Smith (1993) The Wisdom of Teams: Creating the
High-Performance Organization, HarperCollins.
Kelly, John C., Joseph S. Sherif and Jonathan Hops (1992) "Analysis of Defect Densities
Found During Software Inspections," Journal of Systems Software, 17.
**Kruchten, Philippe (1998), The Rational Unified Process: An Introduction, AddisonWesley.
Larman, Craig (1998) Applying UML and Patterns: An Introduction to Object-Oriented
Analysis and Design, Prentice Hall.
Larson, Carl E. and Frank M. Lafasto (1989) Teamwork: What Must Go Right, What Can
Go Wrong, Sage Publications.
**Leffingwell, Dean and Don Widrig (1999) Managing Software Requirements: A
Unified Approach, Addison-Wesley.
Liberty, Jesse (1998) Beginning Object-Oriented Analysis and Design: With C++, Wrox
* Recommended Reading
R-3
Requirements Management with Use Cases
Press Ltd.
Lorenz, Mark and Jeff Kidd (1994) Object-Oriented Software Metrics: A Practical Guide,
Prentice Hall.
Lutz, Robyn (1993) "Analyzing Software Requirements Errors in Safety-Critical
Embedded Systems," IEEE International Symposium on Requirements Engineering,
January.
Martin, James and James J. Odell (1995) Object-Oriented Methods: A Foundation,
Prentice Hall.
*McCarthy, Jim (1995) Dynamics of Software Development, Microsoft Press.
McConnell, Steve (1993) Code Complete: A Practical Handbook of Software
Construction, Microsoft Press.
*McConnell, Steve (1996) Rapid Development: Taming Wild Software Schedules,
Microsoft Press.
*Moore, Geoffrey A. (1991) Crossing the Chasm: Marketing and Selling High-Tech
Products to Mainstream Customers, HarperCollins.
Muller, Pierre-Alain (1997) Instant UML, Wrox Press Ltd.
Odell, James J. (1998) Advanced Object-Oriented Analysis and Design Using UML, SIGS
Books.
Paulk, M., Curtis B., et al. “Capability Maturity Model for Software, Version 1.1”,
Software Engineering Institute, Pittsburgh, PA SEI-93-TR-024
Paulk, M., et al. “Key Practices of the Capability Maturity Model, Version 1.1,” Software
Engineering Institute, Pittsburgh, PA, SEI-93-TR-025
Paulk, Mark C., et al. (1993) “Capability Maturity Model , Version 1.1”, IEEE Software,
July.
*Paulk, Mark C., et al. (1994) The Capability Maturity Model: Guidelines for Improving
the Software Process, Addison-Wesley.
Putnam, L. (1994) “The Economic Value of Moving Up the SEI Scale”, Managing System
Development, July.
Quatrani, Terry (1998) Visual Modeling With Rational Rose and UML, Addison-Wesley.
Rational Software Corporation (1999) “Rational Unified Process v. 5.5”, Rational
Software Corporation.
Ries, Al and Jack Trout (1993) The 22 Immutable Laws of Marketing: Violate Them at
Your Own Risk, HarperCollins.
*Rosenberg, Doug (1999) Use Case Driven Object Modeling With UML : A Practical
Approach, Addison-Wesley.
*Royce, Walker (1998) Software Project Management: A Unified Framework, AddisonWesley.
R-4
Reading
* Recommended
References
Rumbaugh, James, et al. (1991) Object-Oriented Modeling and Design, Prentice Hall.
Rumbaugh, James, Ivar Jacobson, and Grady Booch (1999) The Unified Modeling
Language Reference Manual, Addison-Wesley.
*Schneider, Geri, Jason P. Winters and Ivar Jacobson (1998) Applying Use Cases: A
Practical Guide, Addison-Wesley.
Shaw, Mary, and David Garlan (1996) Software Architecture : Perspectives on an
Emerging Discipline, Prentice Hall.
Sheldon, Frederick T., Krishna M. Kavi, Robert C. Tausworthe, James T. Yu, Ralph
Brettschneider and William W. Everett (1992) "Reliability Measurement: From
Theory to Practice," IEEE Software, July.
Shlaer, Sally, and Stephen J. Mellor (1992) Object Lifecycles: Modeling the World in
States, Prentice Hall.
Shurtleff, Mark (1994) “Storyboarding and the Human Interface”, Software
Development, July.
*Sommerville, Ian and Pete Sawyer (1997) Requirements Engineering: A Good Practice
Guide, John Wiley & Sons.
Taylor, David A. (1995) Business Engineering With Object Technology, John Wiley &
Sons.
Taylor, David A., (1998) Object Technology: A Manager's Guide (Second Edition),
Addison-Wesley.
Texel, Putnam P. and Charles B. Williams (1997) Use Cases Combined With
Booch/OMT/UML: Process and Products, Prentice Hall.
*Thayer, Richard H., and Merlin Dorfman (Editors). (1997) Software Requirements
Engineering (Second Edition), IEEE Computer Society Press.
*The Standish Group (1995) “Chaos Report” (available on their web site at
www.standishgroup.com).
Weinberg, Gerald M. (1986) Secrets of Consulting : A Guide to Giving and Getting
Advice Successfully, Dorset House Publishing.
Weinberg, Gerald M. (1998) The Psychology of Computer Programming: Silver
Anniversary Edition, Dorset House Publishing.
Weinberg, Gerald M. (1997) Quality Software Management : Anticipating Change (Vol
4), Dorset House Publishing.
*Weinberg, Gerald (1995) “Just Say No! Improving the Requirements Process”,
American Programmer, October.
Wirfs-Brock, Rebecca, et al. (1990) Designing Object-Oriented Software, Prentice Hall.
Wright, Peter (1998) Beginning Objects With Visual Basic 5, Wrox Press Ltd.
Yourdon, Edward (1992) Decline & Fall of the American Programmer, Prentice Hall.
* Recommended Reading
R-5
Requirements Management with Use Cases
R-6
Reading
* Recommended
References
* Recommended Reading
R-7