References
Topics
BRO95 |
Frederick P. Brooks Jr. 1995. The Mythical Man-Month -
Essays on Software Engineering 2nd ed. Reading, MA, Addison-Wesley |
|
|
A classic that should be read and re-read by
everyone involved in software development. I recommend the 20-year anniversary edition
rather than the original 1975 edition. |
DAV95 |
Alan Davis 1995. 201 Principles of Software Development,
New York: McGraw-Hill. |
|
|
Full of good advice for every worker. |
KAT93 |
Jon R. Katzenbach, and Douglas K. Smith 1993. The Wisdom of
Teams, New York: Harper Business. |
|
|
The secret of effective teams. |
YOU97 |
Edward Yourdon 1997. Death March: Managing "Mission
Impossible" Projects, Upper Saddle River, NJ: Prentice Hall. |
|
|
An interesting view on project troubles. |
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. |
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. |
DOD94 |
Software Development and Documentation, MIL-STD-498,
U.S. Department of Defense, December 1994. |
|
|
|
HUM89 |
Watts S. Humphrey1989, Managing the Software Process,
Reading, MA: Addison Wesley. |
|
|
A classic book on software process, and the
capability maturity model developed at the Software Engineering Institute. |
JAC97 |
Ivar Jacobson, Martin Griss, and Patrik Jonsson 1997. Software
reuseArchitecture, process and Organization for Business Success, Addison Wesley
Longman. |
|
|
This textbook on software reuse is great
complement to the Rational Unified Process. It features also some great chapters on
architecture. |
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 Rational Unified
Process. Provides also examples of UML modeling. |
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 larchitecture," Proceedings of the 4th
International Conference on Software Engineering, December 1991, Toulouse, France,
EC2. |
|
|
The Rational iterative process, but in
French. |
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. |
MCF96 |
Robert McFeeley 1996. IDEAL: A User's Guide for Software
Process Improvement, Software Engineering Institute, Pittsburgh, PA, CMU/SEI-96-HB-001 |
|
|
It describes a software process improvement
program model: IDEAL, a generic description of a sequence of recommended steps, for
initiating and managing a process implementation project. |
ISO95 |
ISO/IEC 12207 Information technology - Software life-cycle
processes, ISO, Geneva, 1995, 57p. |
|
|
|
ROY70 |
Winston W. Royce, "Managing the Development of Large
Software Systems: Concepts and Techniques," Proceedings, WESCON, August 1970 |
|
|
|
ROY90 |
Walker E. Royce, "TRWs Ada Process Model for
Incremental Development of Large Software Systems," Proceedings ICSE 12, March
26-30, 1990, Nice, France, IEEE, pp.2-11 |
|
|
|
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. |
BOO93 |
Grady Booch 1993. Object-Oriented Analysis and Design with
Applications, 2nd edition. Redwood City CA: The Benjamin/Cummings Pub. Co. |
|
|
|
JAC92 |
Ivar Jacobson, et al. 1992. Object-Oriented Software
Engineering a Use Case-Driven Approach, Wokingham, Engl.: Addison-Wesley. |
|
|
|
RUM91 |
James Rumbaugh, et al. 1991. Object-Oriented Modeling and
Design, Englewood Cliffs, NJ: Prentice-Hall. |
|
|
The three books above are the original roots
to the object-oriented analysis and design workflow, from "the three amigos,"
just before the advent of the UML, and the Rational Unified Process. Despite the use of
their original notations, they are still the key reference for the OO designer. |
RUM96 |
James Rumbaugh 1996. OMT Insights. New York: SIGS
Books. |
|
|
A complement to the original OMT book, diving
into special topics: inheritance, use cases etc. |
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. |
SEL94 |
Bran Selic, Garth Gullekson, Paul Ward 1994. Real-time
Object Oriented Modeling. New York: John Wiley & Sons. |
|
|
The reference work on using object technology
for the design of reactive systems by the people who have brought us ObjecTime Developer. |
UML95 |
G. Booch, and J. Rumbaugh, Unified Method for
Object-Oriented Development, Documentation set, ver. 0.8, Rational Software Corp.,
1995 |
|
|
|
UML96 |
G. Booch, J. Rumbaugh and I. Jacobson, The Unified Modeling
Language for Object-Oriented Development, Documentation set, ver. 0.9 Addendum,
Rational Software Corp., 1996. |
|
|
|
UML98 |
G. Booch, J. Rumbaugh and I. Jacobson 1998. The Unified
Modeling Language. Documentation set, version 1.2, Cupertino, CA: Rational Software. |
|
|
The latest OMG standard on UML, at the time I
write this annex. Available online at http://www.rational.com/uml |
BOO98 |
Grady Booch, et al. 1998. UML Users Guide. Addison
Wesley Longman. |
|
|
Published at the same time at the Rational
Unified Process 5.1, this book is an excellent user's guide on UML by its main authors. |
RUM98 |
Jim Rumbaugh, et al. 1998. UML Reference Manual.
Addison Wesley Longman. |
|
|
Certainly more digestible that the OMG
standard, UML fully exposed by its main authors. |
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, and at the same time following the Rational Unified Process for which
this book provides in effect a small scale example. |
FOW97 |
Martin Fowler 1997. UML DistilledApplying the
standard object modeling language. Addison Wesley Longman. |
|
|
A very nice little introduction to UML, if
you are in a hurry. |
MUL98 |
Pierre-Alain Muller 1998. Instant UML, Wrox Inc. |
|
|
Another short introduction to UML by a former
colleague. |
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. |
AMI95 |
K. Pulford, A. Kuntzmann-Combelles, and S. Shirlaw, A
quantitative approach to Software management-The ami handbook, Addison-Wesley, 1995 |
|
|
|
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. |
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. |
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 Corp., 1995 |
|
|
|
GIL88 |
Tom Gilb 1988. Principles of Software Engineering
Management, Harlow, Engl.: Addison-Wesley. |
|
|
A great book by a pioneer of iterative
development, full of pragmatic advice for the project manager. |
BOO95 |
Grady Booch 1995. Object SolutionsManaging the Object
oriented project, Addison-Wesley. |
|
|
A pragmatic book for managers of
object-oriented project; one of the sources of the Rational Unified Process underlying
philosophy. |
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. |
JON94 |
Capers Jones 1994. Assessment and Control of Software
Risks, Yourdon Press. |
|
|
An indispensable source of risks to check to
make sure your list 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. |
ROY98 |
Walker Royce 1998. Software Project Management: a Unified
Framework. Addison-Wesley-Longman. |
|
|
An indispensable companion to the Rational
Unified, this book describes the spirit of the Rational Process, the underlying software
economics, and is full of great advice for the project manager. |
OCO94 |
Fergus O'Connell 1994. How to run successful projects.
New York: Prentice-Hall International. |
|
|
A real gem. Everything you really need to
know to manage your first project, in 170 pages. |
DAV93 |
Alan Davis 1993. Software Requirements Objects,
Functions and States. Englewood Cliffs, NJ: Prentice Hall. |
|
|
|
GAU89 |
Donald Gause & Gerald Weinberg 1989. Exploring
Requirements Quality Before Design. Dorset House. |
|
|
|
WEI95 |
Gerald Weinberg, 1995. "Just Say No! Improving the
Requirements Process", American Programmer, October 1995. |
|
|
|
IEEE93 |
IEEE Std 830-1993, Recommended Practice for Software
Requirements Specifications, Software Engineering Standards Committee of the IEEE
Computer Society, New York, 1993. |
|
|
|
BER92 |
H. Berlack, 1992. Software Configuration Management,
New York: John Wiley & Sons. |
|
|
|
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: John Wiley & Sons. |
|
|
|
BEI95 |
Boris Beizer1995, Black Box Testing. New York: John
Wiley & Sons. |
|
|
A treasure of strategies to develop test
cases for the functional testing of software. Dr. Beizers writing style (and wit)
makes this book easy and fun to read, with excellent, understandable examples. |
GOG93 |
Patricia Goglia 1993. Testing Client/Server Applications.
QED Press. |
|
|
This was the first book available focused on
testing client / server applications. |
HET88 |
Bill Hetzel 1988. The Complete Guide to Software Testing
2nd Edition. QED Press. |
|
|
|
PER |
Willam E Perry, Effective Methods for Software Testing.
New York: J. Wiley/QED Press. |
|
|
|
SCH94 |
Charles H. Schmauch 1994. ISO 9000 for Software
Developers, Milwaukee WI: ASQC Quality Press. |
|
|
|
IEEE83 |
IEEE 829-1983 Standard for Software Test Documentation,
Software Engineering Standards Committee of the IEEE Computer Society, New York. |
|
|
|
BUS96 |
Frank Buschmann, Régine Meunier, Hans Rohnert, Peter
Sommerlad, and Michael Stahl 1996. Pattern-Oriented Software Architecture - A System of
Patterns, New York: John Wiley and Sons. |
|
|
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. |
WIT94 |
Bernard I. Witt, F. Terry Baker, and Everett W. Merritt 1994. Software
Architecture and DesignPrinciples, Models, and Methods, New York: Van Nostrand
Reinhold. |
|
|
One of the first comprehensive book written
on software architecture. |
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 Rational Unified Process. |
SHA96 |
Mary Shaw, and David Garlan 1996. Software
ArchitecturePerspectives on an Emerging Discipline, Upper Saddle River, NJ:
Prentice-Hall. |
|
|
A good introduction to the concepts and
problems of software architecture. |
BAS98 |
Len Bass, Paul Clements & Rick Kazman 1998. Software
Architecture in practice, Addison-Wesley. |
|
|
A handbook of software architecture, with
numerous case studies. |
HOF98 |
Christine Hofmeister, Robert Nord, Dilip Soni. Applied
Software Architecture. Addison Wesley Longman (to be published in 1998) |
|
|
The architectural design approach they
recommend is very similar to that of the Rational Unified Process, based on multiple
coordinated views. |
REC91 |
Eberhardt Rechtin 1991. Systems Architecting: creating and
building complex systems. Englewood Cliffs NJ: Prentice-Hall. |
|
|
|
REC97 |
Eberhard 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: they
introduce in particular invaluable set of heuristics, and many examples of architecture. |
JAC97 |
Ivar Jacobson, Martin Griss, and Patrik Jonsson, 1997. Software
reuseArchitecture, process and Organization for Business Success. Addison Wesley
Longman. |
|
|
A great companion book to the Rational
Unified Process, this book offers insights on the design of components, of systems of
interconnected system, and lays out a strategy for institutionalizing a practice of
systematic reuse at the corporate level. |
IEEE98 |
IEEE Recommended Practice for Architectural Description,
Draft 3.0 of IEEE P1471, May 1998 (http://www.pithecanthropus.com/~awg/ |
|
|
This proposed standard will recommend
architectural description based on the concept of multiple views. |
ROY91 |
Walker E. Royce, and Winston Royce, "Software
Architecture: Integrating Process and Technology," Quest, 14 (1), 1991,
Redondo Beach CA, TRW, pp.2-15 |
|
|
|
JAC94 |
Ivar Jacobson, Maria Ericsson, and Agneta Jacobson 1994.
The Object Advantage - Business process reengineering with object technology.
Addison-Wesley |
|
|
The basis of the Business modeling workflow,
this is the very first book that applied object technology to the field of business
engineering. |
HAM93 |
Michael Hammer and James Champy1993. Reengineering the
corporationA Manifesto for Business revolution. New York: HarperBusiness. |
|
|
The book that popularized the movement of
business (re-)engineering. An excellent complement to the book above. |
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
lifecycle, their origins their flaws, and their strengths; useful to understand the
importance of process. |
STA97 |
Jennifer Stapleton 1997. The Dynamic System Development
Method. Addison-Wesley. |
|
|
At 15,000 feet, the DSDM approach could be
seen as an introduction to the Rational Unified Process. Although they use a different
terminology, the two processes are very close to each other, and you can see the Rational
Unified Process as an instance or an implementation of DSDM. |
IBM97 |
IBM 1997. Developing object-oriented softwareAn
experienced based approach. Prentice-Hall. |
|
|
Like the Rational Unified Process, iterative,
incremental, object-oriented, scenario-driven, risk-aware process developed by the IBM
Object Technology Center. |
GRA97 |
Ian Graham, et al. 1997. The OPEN Process Specification.
Harlow, Engl.: Addison Wesley. |
|
|
Another process model, coming from down
under, which shares some principles with the Rational Unified Process. |
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
Rational Unified Process. |
MCO93 |
Steve McConnell 1993. Code CompleteA Practical
Handbook of Software Construction. Redmond, WA: Microsoft® Press. |
|
|
A great book for the implementer and test
workers, looking at the implementation, integration and test aspects of the development
process. |
MCA95 |
Jim McCarthy 1995. Dynamics of Software Development.
Redmond, WA: Microsoft® Press. |
|
|
Fifty-three rules of thumbs by a Microsoft®
development manager. |
BOU94 |
Serge Bouchy, L'ingénierie des systèmes informatiques
évolutifs, Paris, Eyrolles, 1994, 330p. |
|
|
|
CON92 |
Conner, D. 1992. Managing at the Speed of Change, New
York, NY: Random House, Inc. |
|
|
|
JEL93 |
Jellison, J. 1993. Overcoming Resistance: A Practical
Guide to Producing Change in the Workplace, New York, NY: Simon & Schuster, Inc. |
|
|
|
| |

|