Bibliography
Topics
Models and Tools 
| BOO98 |
G. Booch, J.
Rumbaugh, and I. Jacobson, 1998. UML User
Guide. Addison-Wesley Longman. |
|
|
Published at the same time as Unified Process
for EDUcation 5.1, this book is an excellent user's guide on UML by
its main authors. |
| CONA99 |
Jim Conallen, 1999.
Building Web Applications with UML.
Addison-Wesley Longman. |
|
|
A
good introduction to the basics of web application development in
the context of the UPEDU. This book also shows how to use the UML to
model web applications and introduces a Web Application Extension to
the UML. |
| DOUG98 |
Bruce Powel Douglass
1998. Real-Time UML. Addison Wesley
Longman. |
|
|
Using UML as the notation, this book offers
good advice on the application of object-oriented technology for
real-time systems. |
| ERI97 |
Hans-Erik Eriksson
and Magnus Penker 1997. UML Toolkit. New
York: John Wiley & Sons. |
|
|
A
more comprehensive book on UML as seen from Sweden by another pair
of Rational friends. |
| FOW97 |
Martin Fowler 1997.
UML Distilled—Applying the standard object
modeling language. Addison-Wesley Longman. |
|
|
A
very nice little introduction to UML if you're in a hurry. |
| LAR01 |
Craig Larman 2001.
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process
Prentice Hall PTR. |
|
|
Provides you with a language in which to think about software design. More details at http://www.amazon.com/exec/obidos/ASIN/0130925691/ |
| MUL98 |
Pierre-Alain Muller
1998. Instant UML. Wrox Inc. |
|
|
Another short introduction to UML by a former
colleague. |
| QUA98 |
Terry Quatrani 1998.
Visual Modeling with Rational Rose and
UML. Addison Wesley Longman. |
|
|
Provides step-by-step guidance on how to build
UML models. At the same time, it follows the UPEDU, in effect
providing a small scale example. |
| RUM98 |
J. Rumbaugh, I.
Jacobson, and G. Booch, 1998. UML Reference
Manual. Addison Wesley Longman. |
|
|
Certainly more digestible that the OMG
standard, UML fully exposed by its main authors. |
| UML99 |
OMG Unified Modeling Language Specification,
Version 1.3. Rational Software Corporation, 18880
Homestead Road, Cupertino, CA 95014, and Object Management Group,
Inc., 492 Old Connecticut Path, Framingham, MA 01701. |
|
|
The latest specification of the UML. Available
online at http://www.rational.com/uml. |
| UML96 |
G. Booch, J.
Rumbaugh, and I. Jacobson 1996. The Unified
Modeling Language for Object-Oriented Development. Documentation
set, version 0.9 Addendum, Rational Software Corporation. |
| UML95 |
G. Booch and J.
Rumbaugh 1995. Unified Method for
Object-Oriented Development. Documentation set, version 0.8,
Rational Software Corporation. |
Software Process 
| AMB99 |
Scott W. Ambler 1999.
More Process Patterns: Delivering
Large-Scale Systems Using Object Technology. New York, NY: SIGS
Books/Cambridge University Press. |
|
|
The companion to [AMB98]. |
| AMB98 |
Scott W. Ambler 1998.
Process Patterns: Building Large-Scale
Systems Using Object Technology. New York, NY: SIGS
Books/Cambridge University Press. |
|
|
A
good resource on process tailoring and applying object-oriented
techniques to software engineering projects. |
| BOE96 |
Barry W. Boehm 1996,
"Anchoring the Software Process," IEEE
Software, July 1996, pp.73-82. |
|
|
This article defines the four phases and the
corresponding milestones. |
| BOE88 |
Barry W. Boehm 1988,
"A Spiral Model of Software Development and Enhancement," Computer, May 1988, IEEE, pp.61-72. |
|
|
This seminal article defines the principles and
motivations of iterative development. |
| DOD94 |
Software Development and Documentation,
MIL-STD-498, U.S. Department of Defense, December 1994. |
|
|
|
| FER01 |
Xavier Ferre et al.
2001, "Usability Basics for Software Developers," IEEE Software, January 2001, pp.
22-29. |
| HIG00 |
James A. Highsmith
2000. Adaptive Software Development: A
Collaborative Approach to Managing Complex Systems. Dorset
House. |
|
|
|
| HUM89 |
Watts S.
Humphrey1989. Managing the Software
Process. Reading, MA: Addison Wesley Longman. |
|
|
A
classic book on software process and the capability maturity model
developed at the Software Engineering Institute. |
| ISO95 |
ISO/IEC 12207 Information Technology— Software Life-cycle
Processes. ISO, Geneva, 1995, 57p. |
|
|
|
| ISO91 |
ISO 9000-3 Guidelines for the Application of ISO 9001 to
the Development, Supply, and Maintenance of Software. ISO,
Geneva 1991. |
|
|
Two key standards for software process
definition and assessment. |
| JAC98 |
Ivar Jacobson, Grady
Booch, and James Rumbaugh 1998. The Unified
Software Development Process. Addison Wesley Longman. |
|
|
This recent textbook is a more thorough
description of the Unified Process and is a useful companion to the
UPEDU. Also provides examples of UML modeling. |
| JAC97 |
Ivar Jacobson, Martin
Griss, and Patrik Jonsson 1997. Software
Reuse—Architecture, Process and Organization for Business
Success. Addison Wesley Longman. |
|
|
This textbook on software reuse is great
complement to the UPEDU. It features also some great chapters on
architecture. |
| JEF01 |
Ron Jeffries, Ann
Anderson, and Chet Hendrickson 2001. Extreme
Programming Installed. Addison-Wesley. |
|
|
This book describes practical Extreme
Programming techniques. |
| KRU96 |
Philippe Kruchten
1996. "A Rational Development Process", CrossTalk, 9
(7), July 1996, p.11-16. |
|
|
Developed with Walker Royce, Sue Mickel, and a
score of Rational consultants, this article describes the iterative
lifecycle of the Rational Process. |
| KRU91 |
Philippe Kruchten
1991. "Un processus de dévelopment de logiciel itératif et centré
sur l’architecture", Proceedings of the 4th
International Conference on Software Engineering, December 1991,
Toulouse, France, EC2. |
|
|
The Rational iterative process in French. |
| KRU00 |
Philippe Kruchten
2000. The Rational Unified Process, An
Introduction, Second Edition. Addison Wesley
Longman. |
|
|
A
must buy—this second edition quickly introduces you to the concepts,
structure, content, and motivation of the UPEDU. |
| MCF96 |
Robert McFeeley 1996.
IDEAL: A User's Guide for Software Process
Improvement. Software Engineering Institute, Pittsburgh, PA,
CMU/SEI-96-HB-001. |
|
|
Describes a software process improvement
program model called IDEAL, a generic description of a sequence of
recommended steps for initiating and managing a process
implementation project. |
| PAR86 |
David L. Parnas and
Paul C. Clements, "A Rational Design Process: How and Why to Fake
It", IEEE Trans. Software Eng., Feb.
1986, pp.251-257. |
|
|
|
| PAU93 |
Mark Paulk, et al.
1993. Capability Maturity Model for
Software, Version 1.1. Software Engineering Institute,
Pittsburgh, PA SEI-93-TR-024. |
|
|
The original reference for the capability
maturity model. |
| ROY90 |
Walker E. Royce,
"TRW’s Ada Process Model for Incremental Development of Large
Software Systems", Proceedings ICSE 12,
March 26-30, 1990, Nice, France, IEEE, pp.2-11. |
|
|
|
|
ROY70 |
Winston W. Royce,
"Managing the Development of Large Software Systems: Concepts and
Techniques", Proceedings, WESCON, August
1970. |
|
|
|
Requirements 
| AND96 |
Stephen J. Andriole
1996. Managing Systems Requirements:
Methods, Tools, and Cases. McGraw Hill. |
|
|
|
| BEY98 |
Hugh Beyer and Karen
Holtzblatt 1998. Contextual Design. San
Francisco, CA: Morgan Kaufmann Publishers. |
|
|
|
| CON99 |
Larry Constantine and
Lucy A.D. Lockwood 1999. Software for Use. Reading, MA: Addison
Wesley Longman. |
|
|
An
excellent book on user-centric design, focusing on techniques and
practical guidelines for developing software that is usable. |
| COO99 |
Alan Cooper1999. The Inmates are Running the Asylum.
Indianapolis, IN: SAMS. |
|
|
|
| DAV93 |
Alan Davis 1993. Software Requirements—Objects, Functions and
States. Englewood Cliffs, NJ: Prentice Hall. |
|
|
|
| FIS91 |
Roger Fisher and
William Ury 1991. Getting to Yes—Negotiating
Agreement Without Giving In, 2nd Edition. Penguin Books
USA. |
|
|
|
| GAU89 |
Donald Gause and
Gerald Weinberg 1989. Exploring
Requirements—Quality Before Design. New York, NY: Dorset
House. |
|
|
|
| GOU88 |
John D. Gould 1988.
"How to Design Usable Systems", in Helander, Martin, ed. Handbook of Computer Interaction, pp.
757-789, North-Holland, Amsterdam, The Netherlands. |
|
|
|
| GOU87 |
John D. Gould,
Stephen J. Boies, Stephen Levy, John T. Richards and Jim Schoonard
1987. "The 1984 Olympic Message System: a test of behavioral
principles of system design", in Communications of the ACM, Vol. 30, No. 9,
pp. 758-769. |
|
|
|
| GRA92 |
Robert Grady 1992. Practical Software Metrics for Project
Management and Process Improvement. Prentice-Hall. |
|
|
|
| HOL96 |
Holtzblatt,
K., and H. Beyer 1996. "Contextual Design: Principles and Practice,"
Field Methods for Software and Systems
Design. D. Wixon and J. Ramey (Eds.), NY, NY: John Wiley &
Sons, Inc. |
| IEEE93 |
IEEE Std 830-1993. Recommended Practice for Software Requirements
Specifications. Software Engineering Standards Committee of the
IEEE Computer Society: New York, NY, 1993. |
|
|
|
| ISO13407 |
ISO/TC159 1999. Human-centred design processes for interactive
systems. Report ISO 13407:1999, International Organization for
Standardization, Geneva, Switzerland. |
|
|
|
| KOV99 |
Benjamin L. Kovitz
1999. Practical Software Requirements—A
Manual of Content & Style. Manning Publications. |
|
|
|
| LEF99 |
Dean Leffingwell and
Don Widrig 1999. Effective Requirements
Management. Addison Wesley Longman. |
|
|
|
| MAY99 |
Deborah J.
Mayhew1999. The Usability Engineering
Lifecycle. Morgan Kaufmann Publishers. |
|
|
|
| SCH98 |
Geri Schneider and
Jason P. Winters 1998. Applying Use Cases—A
Practical Guide. Addison Wesley Longman. |
|
|
|
| SOM97 |
Ian Sommerville and
Pete Sawyer 1997. Requirements Engineering—A
Good Practice Guide. New York, NY: John Wiley & Sons,
Inc. |
|
|
|
| THA97 |
Richard H. Thayer and
Merlin Dorfman 1997. Software Requirements
Engineering, 2nd Edition. IEEE Computer Society Press. |
|
|
|
| WEI95 |
Gerald Weinberg,
1995. "Just Say No! Improving the Requirements Process", American Programmer, October 1995. |
|
|
|
Analysis & Design 
| BAS98 |
Len Bass, Paul
Clements, and Rick Kazman 1998. Software
Architecture in Practice. Addison Wesley Longman. |
|
|
A
handbook of software architecture, with numerous case studies. |
| BUS96 |
Frank Buschmann,
Régine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stahl
1996. Pattern-Oriented Software
Architecture— A System of Patterns, New York, NY: John Wiley and
Sons, Inc. |
|
|
Following the model of the "gang of four" book
(Gamma, et al, see above) this book makes an inventory of a wide
range of design patterns at the level of the architecture. |
| FOW97a |
Martin Fowler 1997.
Analysis Patterns: Reusable Object
Models. Addison Wesley Longman. |
|
|
|
| GAM94 |
Erich Gamma, Richard
Helm, Ralph Johnson and John Vlissides 1994. Design Patterns—Elements of Reusable
Object-Oriented Software. Addison Wesley Longman. |
|
|
One of the earlier works on
patterns, this book deals with patterns "in the small". |
| GAR93 |
David Garlan and Mary
Shaw. An Introduction to Software
Architecture. SEI Technical Report CMU/SEI-94-TR-21. |
|
|
|
| HOF98 |
Christine Hofmeister,
Robert Nord, and Dilip Soni 1999. Applied
Software Architecture. Addison Wesley Longman. |
|
|
The architectural design approach they
recommend is very similar to that of the UPEDU, based on multiple
coordinated views. |
|
|
This proposed standard recommends architectural
description based on the concept of multiple views. |
| JAC97 |
Ivar Jacobson, Martin
Griss and Patrik Jonsson, 1997. Software
Reuse—Architecture, Process and Organization for Business
Success. Addison Wesley Longman. |
|
|
A
great companion book to the UPEDU, this book offers insights on the
design of components and systems of interconnected system, and lays
out a strategy for institutionalizing a practice of systematic reuse
at the corporate level. |
| KRU95 |
Philippe Kruchten
1995, "The 4+1 view model of architecture," IEEE Software. 12(6), November 1995. |
|
|
The origin of the 4+1 views used for
architectural description in the UPEDU. |
| LMFS96 |
Lockheed Martin
Federal STARS (Software Technology for Adaptable, Reliable Systems)
Program. Domain Engineering Guidebook. |
|
|
This Guidebook provides a high-level
description of the Domain Engineering process in the context
of a real organization—the U.S. Air Force's Space and Warning
Systems Center. |
| PW92 |
Dewayne E. Perry and
Alexander L. Wolf. Foundations for the Study
of Software Architecture. ACM SIGSOFT Software Engineering
Notes, 17(4):40-52, October 1992. |
|
|
|
| REC97 |
Eberhardt Rechtin and
Mark Maier1997. The Art of System
Architecting. Boca Ration, FL: CRC Press. |
|
|
Although not specifically directed to software
engineers, these two books are extremely valuable for software
architects: in particular, they introduce an invaluable set of
heuristics and many examples of architecture. |
| REC91 |
Eberhardt Rechtin
1991. Systems Architecting: creating and
building complex systems. Englewood Cliffs NJ:
Prentice-Hall. |
|
|
|
| ROY91 |
Walker E. Royce and
Winston Royce, "Software Architecture: Integrating Process and
Technology," Quest, 14 (1), 1991,
Redondo Beach, CA: TRW, pp.2-15. |
|
|
|
| SHA96 |
Mary Shaw and David
Garlan 1996. Software
Architecture—Perspectives on an Emerging Discipline. Upper
Saddle River, NJ: Prentice-Hall. |
|
|
A
good introduction to the concepts and problems of software
architecture. |
| WIT94 |
Bernard I. Witt, F.
Terry Baker, and Everett W. Merritt 1994. Software Architecture and Design—Principles,
Models, and Methods. New York, NY: Van Nostrand Reinhold. |
|
|
One of the first comprehensive book written on
software architecture. |
Object-Oriented Technology 
| BOO93 |
Grady Booch 1993. Object-Oriented Analysis and Design with
Applications, 2nd edition. Redwood City, CA: The
Benjamin/Cummings Publishing Company. |
| BUH96 |
R. J. A. Buhr and R.
S. Casselman 1996. Use Case Maps for
Object-Oriented Systems. Upper Saddle River, NJ:
Prentice-Hall. |
|
|
This book develops some other views on use
cases. |
| JAC92 |
Ivar Jacobson, et al.
1992. Object-Oriented Software Engineering—A
Use Case-Driven Approach, Wokingham, England: Addison Wesley
Longman. |
| RUM91 |
James Rumbaugh, et
al. 1991. Object-Oriented Modeling and
Design. Upper Saddle River, NJ: Prentice-Hall. |
|
|
The three books above are the original roots to
the object-oriented analysis and design discipline from "the three
amigos", just before the advent of the UML and the UPEDU. Despite
the use of their original notations, they are still the key
references for OO designers. |
| RUM96 |
James Rumbaugh 1996.
OMT Insights. New York: SIGS
Books. |
|
|
A
complement to the original OMT book, diving into special
topics: inheritance, use cases, and so on. |
| SEL94 |
Bran Selic, Garth
Gullekson, and Paul Ward 1994. Real-time
Object-Oriented Modeling. New York, NY: John Wiley & Sons,
Inc. |
|
|
The reference work on using object technology
for the design of reactive systems by the people who have brought us
ObjecTime Developer. |
| WIR90 |
Rebecca Wirfs-Brock,
Brian Wilkerson, and Lauren Wiener 1990. Designing Object-Oriented Software. Upper
Saddle River, NJ: Prentice-Hall. |
|
|
This book describes the Class, Responsibility,
Collaboration (CRC) approach to object-oriented software
development. |
Test 
| BAC01a |
James Bach 2001. What Is Exploratory Testing? (And How It
Differs from Scripted Testing). Software Testing and Quality
Engineering Magazine, Jan 29, 2001. |
|
|
|
| |
|
This article is available
online at: http://www.stickyminds.com. |
| BAS87 |
BAS87 Victor R.
Basili and H. Dieter Rombach 1987. Tailoring
the Software Process to Project Goals and Environments.
Proceedings of the 9th International Conference on Software
Engineering Software, IEEE Press. |
|
|
|
| BEI95 |
Boris Beizer 1995. Black Box Testing. New York, NY: John Wiley
& Sons, Inc. |
|
|
A
treasure of strategies to develop test cases for the functional
testing of software. Dr. Beizer’s writing style and wit make this
book easy and fun to read, with excellent, understandable
examples. |
| BLA99 |
Rex Black 1999. Managing the Testing Process. Microsoft
Press. |
| |
|
This book is a good source of
information about managing system testing efforts. |
|
|
|
| GLA81 |
Robert L. Glass 1981.
Persistent Software Errors. IEEE
Transactions on Software Engineering, March 1981. |
|
|
|
|
|
|
| IEEE83 |
IEEE 829-1983 Standard for Software Test Documentation.
Software Engineering Standards Committee of the IEEE Computer
Society, New York. |
|
|
|
| KAN01 |
Cem Kaner, James Bach
and Bret Pettichord 2001. Lessons Learned in
Software Testing. John Wiley & Sons, Inc. |
| |
|
A wealth of tips and tricks
that help to address a wide variety of issues faced in the testing
of computer software. Good coverage of management, psychological as
well as the technical aspects of software testing. |
| KAN99 |
Cem Kaner, Jack Falk
and Hung Quoc Nguyen 1999. Testing Computer
Software, 2nd Edition. John Wiley & Sons, Inc. |
| |
|
Billed as "The bestselling
software testing book of all time", this book offers a broad
coverage of various aspects of software testing. |
| MAR00 |
Brian Marick 2000. Faults of Omission. Software Testing and
Quality Engineering Magazine, March-April 2000. |
|
|
|
| |
|
This article is available
online at: http://www.testing.com/writings/omissions.pdf. |
| OST84 |
Thomas J. Ostrand and
Elaine J. Weyuker 1984. Collecting and
Categorizing Software Error Data in an Industrial Environment.
Journal of Systems and Software, Vol. 4, 1984. |
| |
|
|
|
|
|
Configuration & Change Management 
| BER92 |
H. Berlack 1992. Software Configuration Management. New
York, NY: John Wiley & Sons, Inc. |
|
|
|
| BUC93 |
J. Buckley 1993. Implementing Configuration Management,
Hardware, Software and Firmware. Los Alamitos, CA: IEEE
Computer Science Press. |
|
|
|
| WHI91 |
David Whitgift 1991.
Methods and Tools for Software Configuration
Management. New York, NY: John Wiley & Sons,
Inc. |
|
|
|
Project
Management 
| AMI95 |
K. Pulford, A.
Kuntzmann-Combelles, and S. Shirlaw 1995. A
Quantitative Approach to Software Management—The AMI Handbook.
Addison Wesley Longman. |
| BOE00 |
Barry W. Boehm et al,
2000. Software Cost Estimation with COCOMO II. Upper Saddle River,
NJ: Prentice-Hall. |
|
|
The successor to the original classic
work. |
| BOE81 |
Barry W. Boehm 1981.
Software Engineering Economics. Upper
Saddle River, NJ: Prentice-Hall. |
|
|
A
classic work on software effort estimation that describes the
original COCOMO estimation model. |
| BOE91 |
Barry W. Boehm 1991.
Software Risk Management: Principles and
Practices, IEEE Software, Jan. 1991,
IEEE, pp.32-41. |
|
|
Still the best little introduction to risk
management. |
| BOO95 |
Grady Booch 1995. Object Solutions—Managing the Object-Oriented
Project. Addison Wesley Longman. |
|
|
A
pragmatic book for managers of object-oriented projects; one of the
sources on the underlying philosophy of the UPEDU. |
| CAR93 |
Marvin J. Carr, et
al. 1993. Taxonomy-Based Risk
Identification, Technical Report CMU/SEI-93-TR-6, Pittsburgh,
PA, SEI, June 1993, 24p. |
|
|
Provides a source of inspiration to get started
on your own list of risks. |
| CHA89 |
Robert Charette
1989. Software Engineering Risk Analysis and
Management. New York, NY: McGraw-Hill. |
|
|
Practical perspective on risk management. |
| CHID94 |
Chidamber and Kemerer
1994. A metrics suite for object-oriented
design, IEEE Transactions on Software Engineering, 20(6),
1994. |
|
|
One of the original contributions to the field
of OO software metrics. |
| CLE96 |
Robert T. Clemen
1996. Making Hard Decisions: An Introduction
to Decision Analysis. Duxbury Press. |
|
|
Thorough yet accessible treatment of the
fundamentals of decision analysis. |
| DEV95 |
Michael T. Devlin and
Walker E. Royce. Improving Software
Economics in the Aerospace and Defense Industry, Technical Paper
TP-46, Santa Clara, CA, Rational Software Corporation, 1995. |
| EVA98 |
James R. Evans and
David L. Olson 1998. Introduction to
Simulation and Risk Analysis. Upper Saddle River, NJ:
Prentice-Hall. |
|
|
Good introduction to the use of simulation for
business modeling. |
| FAI94 |
Richard Fairley 1994.
"Risk Management for Software Project," IEEE
Software, 11 (3), May 1994, pp.57-67 |
|
|
Straightforward strategy for risk management if
you have never done this before. |
| GIL88 |
Tom Gilb 1988. Principles of Software Engineering
Management. Harlow, England: Addison Wesley Longman. |
|
|
A
great book by a pioneer of iterative development, it's full of
pragmatic advice for the project manager. |
| HEND96 |
Brian
Henderson-Sellers 1996. Object-Oriented
Metrics, Measures of Complexity. Prentice Hall PTR. |
|
|
Good, detailed coverage of OO-specific
metrics. |
| JON94 |
Capers Jones 1994. Assessment and Control of Software Risks.
Yourdon Press. |
|
|
An
indispensable source of risks to check your list against to make
sure it's is complete. |
| KAR96 |
Dale Karolak 1996. Software Engineering Risk Management. Los
Alamitos, CA: IEEE Computer Society Press. |
|
|
Offers more sophisticated advice and techniques
for risk management. |
| MCO96 |
Steve McConnell 1996.
Rapid Development. Redmond, WA:
Microsoft Press. |
|
|
Excellent coverage of good practice for rapid
software development |
| MSP97 |
User's Guide for
Microsoft Project 98, Microsoft Corporation, 1997. |
|
|
|
| OCO94 |
Fergus O'Connell
1994. How to Run Successful Projects.
New York, NY: Prentice-Hall International. |
|
|
A
real gem! Everything you really need to know to manage your first
project, in 170 pages. |
| PMI96 |
A Guide to the Project Management Body of
Knowledge. The Project Management Institute: Newton Square, PA,
19073-3299, USA. 1996. |
|
|
|
| PUT92 |
Lawrence Putnam &
Ware Myers 1992. Measures for Excellence:
Reliable Software On Time, Within Budget. Yourdon Press. |
|
|
|
| ROY98 |
Walker Royce 1998. Software Project Management: A Unified
Framework. Addison Wesley Longman. |
|
|
An
indispensable companion to the UPEDU, this book describes the spirit
of the Rational Process and its underlying software economics. Full
of great advice for the project manager. |
| VOS96 |
David Vose 1996. Quantitative Risk Analysis: A Guide to Monte
Carlo Simulation Modeling. John Wiley & Sons. |
|
|
A
good guide to the modeling of uncertainty using Monte Carlo
techniques. |
| WHIT97 |
Scott Whitmire 1997.
Object-Oriented Design Measurement. John
Wiley & Sons, Inc. |
|
|
A
good, if mathematically challenging, treatment of the theoretical
basis of software measurement. |
Miscellaneous 
| BOU94 |
Serge Bouchy
1994. L'ingénierie des systèmes
informatiques évolutifs, Paris, France: Eyrolles, 330p. |
|
|
|
| BRO95 |
Frederick P. Brooks,
Jr. 1995. The Mythical Man-Month—Essays on
Software Engineering 2nd ed. Reading, MA, Addison Wesley
Longman. |
|
|
A
classic that should be read and re-read by everyone involved in
software development. We recommend this 20-year anniversary edition
rather than the original 1975 edition. |
| CON92 |
D. Conner 1992. Managing at the Speed of Change. New York,
NY: Random House, Inc. |
|
|
|
| DAT99 |
C.J. Date 1999. An Introduction to Database Systems.
7th ed. New York, NY: Addison-Wesley Publishing Company,
Inc. |
|
|
Excellent introduction, reference, and source
of background information on Database Systems. |
| DAV95 |
Alan Davis 1995. 201 Principles of Software
Development. New York, NY: McGraw-Hill. |
|
|
Full of good advice for every team member on a
project. |
| DEG90 |
Peter DeGrace and
Leslie Stahl 1990. Wicked Problems, Righteous Solutions: A Catalog
of Modern Software Engineering Practices. Englewood Cliffs, NJ:
Yourdon Press. |
|
|
An
insightful book on various process lifecycles and their origins,
flaws, and strengths; useful for understanding the importance of
process. |
| DEI84 |
Harvey M. Deitel
1984. An Introduction to Operating
Systems. Addison Wesley Longman. |
|
|
|
| FIS96 |
Charles Fishman 1996.
Johnson Space
Center Shuttle Software Group, “They Write the Right Stuff”. Fastcompany, Issue 6, p. 95, December,
1996. |
|
|
|
| GRA97 |
Ian Graham, et al.
1997. The OPEN Process Specification.
Harlow, England: Addison Wesley Longman. |
|
|
Another process model, coming from down under
that shares some principles with the Rational Unified Process
(UPEDU). |
| HAC97 |
JoAnn T. Hackos and
Dawn M. Stevens 1997. Standards for Online
Communication. John Wiley and Sons, Inc. |
|
|
For the
modern technical writer, this book has become "the bible". It
defines a process for developing user manuals, specifically focusing
on how you produce online help systems. |
| IBM2000 |
IBM System Integrated Method. International
Business Machines Corporation 1998, 1999, 2000. |
|
|
|
| IBM99a |
An Approach to Designing e-business
Solutions. International Business Machines Corporation
1999. |
|
|
http://www.redbooks.ibm.com/abstracts/sg245949.html |
| IBM99b |
Design Considerations: From Client Server
Applications to e-business Applications. International Business
Machines Corporation 1999. |
|
|
http://www.redbooks.ibm.com/abstracts/sg245503.html |
| IBM99c |
The Front of IBM WebSphere—Building e-business
User Interfaces. International Business Machines Corporation
1999. |
|
|
http://www.redbooks.ibm.com/abstracts/sg245488.html |
| IBM98a |
Architecture Description Standard:
Overview. International Business Machines Corporation
1998. |
| IBM98b |
Architecture Description Standard: Semantic
Specification. International Business Machines Corporation
1998. |
|
|
Other relevant Web sites for the preceding IBM
references are: http://www.redbooks.ibm.com http://www-306.ibm.com/e-business/ondemand/us/index.html http://www-306.ibm.com/software/ http://www-136.ibm.com/developerworks// http://www-1.ibm.com/services/us/index.wss/home |
| IBM97 |
IBM 1997. Developing Object-Oriented Software—An Experienced-
based Approach. Upper Saddle River, NJ: Prentice-Hall. |
|
|
Like the UPEDU, an iterative, incremental,
object-oriented, scenario-driven, risk-aware process developed by
the IBM Object Technology Center. |
| IEEE90 |
IEEE Std 610.12-1990.
IEEE Standard Glossary of Software
Engineering Terminology. The Institute of Electrical and
Electronics Engineers, Inc.: New York, NY, 10017-2394, USA.
1990. |
|
|
|
| JEL93 |
J. Jellison 1993. Overcoming Resistance: A Practical Guide to
Producing Change in the Workplace. New York, NY: Simon
& Schuster, Inc. |
|
|
|
| KAT93 |
Jon R. Katzenbach and
Douglas K. Smith 1993. The Wisdom of
Teams. New York, NY: Harper Business. |
|
|
The secret of effective teams. |
| KET98 |
Nasser Kettani, et
al. 1998. De Merise à UML. Paris,
France: Editions Eyrolles. |
|
|
Merise is a very popular software development
methodology in France, which has been upgraded to use UML. It has
some similitude with the UPEDU. |
| LEA97 |
Doug Lea 1999.
Concurrent Programming in Java. Addison
Wesley Longman. |
|
|
|
| MCA95 |
Jim McCarthy
1995. Dynamics of Software
Development. Redmond, WA: Microsoft Press. |
|
|
Fifty-three rules of thumb by a Microsoft
development manager. |
| MCO97 |
Steve McConnell
1997. Software Project Survival
Guide. Redmond, WA: Microsoft Press. |
|
|
A
collection of practical experience on how to deliver successful
software projects. |
| MCO93 |
Steve McConnell 1993.
Code Complete—A Practical
Handbook of Software Construction. Redmond, WA: Microsoft
Press. |
|
|
A
great book for the implementers and for testers looking at the
implementation, integration, and test aspects of the development
process. |
| MOS98 |
Microsoft 1998. The
Microsoft Manual of Style for Technical
Publications. Redmond, WA: Microsoft Press. |
|
|
|
| STA97 |
Jennifer Stapleton
1997. The Dynamic System Development
Method. Addison Wesley Longman. |
|
|
At
15,000 feet, the DSDM approach could be seen as an introduction to
the UPEDU. Although they use a different terminology, the two
processes are very close to each other, and you can see the UPEDU as
an instance or an implementation of DSDM. |
| TAN86 |
Andrew S. Tannenbaum
1986. Operating Systems: Design and
Implementation. Upper Saddle River, NJ: Prentice
Hall. |
|
|
|
| WID00 |
R. Max Wideman and
PMForum, February, 1999 and January, 2000. Wideman Comparative Glossary of Project
Management Terms v2.0. www.pmforum.org |
|
|
This great collection of various software
engineering terms and their many definitions is available online at
http://www.pmforum.org/library/glossary/. |
| YOU97 |
Edward Yourdon 1997.
Death March: Managing "Mission Impossible"
Projects. Upper Saddle River, NJ: Prentice Hall. |
|
|
An
interesting view on project
troubles. |
Copyright:
© 1987 - 2004 Rational Software Corporation
© 2004 École Polytechnique de Montréal
|