Bibliography

The following works are either central to the ideas presented in this book or simply interesting reading for systems analysts.

Abdel-Hamid, Tarek, and Stuart Madnick. Software Project Dynamics: An Integrated Approach. Englewood Cliffs, N.J.: Prentice-Hall, 1991.

The authors have investigated the process of building software, modeled the process, and used the model to predict the implications of managerial policies. An outstanding book.

Alexander, Christopher, Sara Ishikawa, and Murray Silverstein. A Pattern Language. New York: Oxford University Press, 1977.

This fascinating book discusses how to make use of patterns when constructing buildings. By following the patterns, a builder will construct a livable and beautiful house. A similar approach to software construction would undoubtedly lead to more usable and maintainable systems.

Arango, Guillermo, Eric Schoen, and Robert Pettengill. “Design as Evolution and Reuse.” Proceedings of the Second International Workshop on Software Reusability. Luca, Italy: IEEE Computer Society, March 1993.

This paper describes practical experience in the evolution and reuse of product knowledge across wide geographical boundaries.

Boehm, Barry W. Software Engineering Economics. Englewood Cliffs, N.J.: Prentice-Hall, 1981.

This is a monumental work in the field of measuring the software process. The author includes work on the COCOMO estimation and measuring model.

Boehm, Barry W, ed. Software Risk Management. Washington, D.C.: IEEE Computer Society Press, 1989.

In today’s world, the majority of software projects either fail completely, or fall far short of original expectations. Often, this is due to the development team failing to evaluate the risks. Read this collection and lessen your own risks.

Böhm, C., and G. Jacopini. “Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules.” Communications of the ACM, Vol. 9, No. 5 (May 1966), pp. 366-71.

In this landmark paper, the authors proved that any program could be constructed using only selection and repetition as the constructs.

Booch, Grady. Object-Oriented Design with Applications. Redwood City, Calif.: Benjamin/Cummings Publishing Company, 1991.

A very good book on using the object paradigm for design. Booch s notation is somewhat complex, but the sample applications and the discussions of several object-oriented languages make this very worthwhile.

Chen, Peter, ed. Entity-Relationship Approach to Information Modeling and Analysis. Amsterdam: North-Holland Publishing Company, 1983.

Delskov, Lis, and Therese Lange. Strukturet Analyse — Integreret Systemanalyse. Copenhagen: Teknisk Forlag, 1991.

This is in Danish, so it has a somewhat restricted readership. The charming authors present an intelligent integration of event-response and data modeling.

DeMarco, Tom. Structured Analysis and System Specification. Englewood Cliffs, N.J.: Prentice-Hall, 1978.

Although the analysis technique DeMarco describes has evolved since 1978, this book is an entertaining and informative read on basic structured analysis and how it got started.

DeMarco, Tom. Controlling Software Projects. Englewood Cliffs, N.J.: Prentice-Hall, 1982.

Presents a practical method for making estimates based on the analysis model. As the analysis model is a plan for the construction of the system, this method makes a lot of sense.

DeMarco, Tom, and Timothy Lister. Peopleware: Productive Projects and Teams. New York: Dorset House Publishing, 1987.

A series of fascinating anecdotes and lessons that reveal more about project management than almost all conventional books on the subject.

DeMarco, Tom, eds. Software State-of-the-Art: Selected Papers. New York: Dorset House Publishing, 1990.

From the Editors’ Preface: “Do yourself a huge favor: Read these thirty-one papers and throw out all the stacks of unread material dating back as far as 1980. You’ll feel better immediately.”

Dickinson, Brian. Developing Quality Systems, 2nd ed. New York: McGraw-Hill, 1989.

The author uses data flow diagrams to describe his method for doing systems analysis, design, and development.

Dijkstra, Edsger. Selected Writings on Computing: A Personal Perspective. New York: Springer-Verlag, 1982.

This noted pioneer’s writings are more of a memoir than a text. The advice he gives, however, is lovely, some focused on the human side, the rest on the technology.

Flavin, Matt. Fundamental Concepts of Information Modeling. Englewood Cliffs, N.J.: Prentice-Hall, 1981.

The definitive book on information modeling. It pays back the effort necessary to understand its concepts.

Freedman, Daniel P., and Gerald M. Weinberg. Handbook of Walkthroughs, Inspections, and Technical Reviews, 3rd ed. New York: Dorset House Publishing, 1990.

We consider walkthroughs and reviews to be an important part of systems development. This is the most accessible book on the subject.

Gause, Donald C., and Gerald M. Weinberg. Exploring Requirements: Quality Before Design. New York: Dorset House Publishing, 1989.

This book takes a very close look at the importance of systems analysis. Highly recommended reading.

Gilb, Tom. Principles of Software Engineering Management. Reading, Mass.: Addison-Wesley, 1988.

An especially good treatment of how to define measurable project goals.

Hatley, Derek J., and Imtiaz A. Pirbhai. Strategies for Real-Time System Specification. New York: Dorset House Publishing, 1987.

Real-time systems have few differences from commercial systems. However, the differences may be important to you. The Hatley-Pirbhai approach is difficult to understand at first, but worth the effort.

Heckel, Paul. The Elements of Friendly Software Design. New York: Warner Books, 1984.

One of those paperbacks that you can read in two lunchtimes, but Heckel’s thoughts will stay with you much longer.

Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, and Gunnar Overgaard. Object-Oriented Software Engineering: A Use-Case Driven Approach. Wokingham, England: Addison-Wesley, 1992.

An object-oriented approach that builds on established concepts.

Kidder, Tracy. The Soul of a New Machine. Boston: Little, Brown and Company, 1981.

This Pulitzer Prize-winning book brilliantly follows the development of a new computer. Powerful reading.

McMenamin, Stephen M., and John F. Palmer. Essential Systems Analysis. Englewood Cliffs, N.J.: Prentice-Hall, 1984.

This outstanding book introduces event partitioning. We are indebted to McMenamin and Palmer for this work, and it is definitely recommended reading.

Meyer, Bertrand. Object-Oriented Software Construction. Hemel Hempstead, England: Prentice-Hall, 1988.

Meyer’s book is a good explanation of the object paradigm. One must fault his (understandable) bias towards his own Eiffel language and (incorrect) attacks on structured design.

Miller, George A. “The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information.” The Psychological Review, Vol. 63, No. 2 (March 1956), pp. 81-97.

An oft-quoted paper dealing with conceptual limits.

Myers, Glenford J. Composite/Structured Design. New York: Van Nostrand Reinhold, 1978.

Myers is one of the originators of structured design, and his books on the subject are readable and informative.

Page-Jones, Meilir. The Practical Guide to Structured Systems Design, 2nd ed. Englewood Cliffs, N.J.: Prentice-Hall, 1988.

The most readable book on the subject of software design. Page-Jones links his subject to event-partitioned systems analysis.

Robertson, Suzanne, and Kenneth Strunch. “Reusing the Products of Analysis.” Proceedings of the Second International Conference on Software Reusability. Luca, Italy: IEEE Computer Society, March 1993.

An account of how project teams built and reused analysis models.

Rock-Evans, Rosemary. Analysis Within the Systems Life Cycle, Vols. 1-4. Maidenhead, England: Pergamon Infotech, 1987.

An exhaustive treatment of systems from the data analysis viewpoint.

Ross, Ronald G. Entity Modeling: Techniques and Application. Boston, Mass.: Database Research Group, 1988.

Entity-relationship modeling is important, and not always easy to understand. We think that different authors throw different lights on the subject, and that one of those lights might be the one that illuminates it for you.

Rumbaugh, James, Michael Blaha, William Premerlani, Frederick Eddy, and William Lorensen. Object-Oriented Modeling and Design. Englewood Cliffs, N.J.: Prentice-Hall, 1991.

This book connects the ideas of structured analysis and essential systems analysis to the development of object-oriented systems.

Russell, Peter. The Brain Book. London: Routledge and Kegan Paul, Ltd., 1980.

Describes mind maps, a useful tool for taking notes and capturing ideas.

Shlaer, Sally, and Stephen J. Mellor. Object-Oriented Systems Analysis. Englewood Cliffs, N.J.: Prentice-Hall, 1988.

Shlaer, Sally, and Stephen J. Mellor. Object Lifecycles: Modeling the World in States. Englewood Cliffs, N.J.: Prentice-Hall, 1992.

These two books by Shlaer and Mellor provide excellent coverage of data modeling. The first introduces the topic in a highly readable way, and the second continues the good work by showing how to model the states of an entity’s life history.

Stevens, Wayne P. Using Structured Design. New York: John Wiley & Sons, 1981.

A good, practical book on structured design.

Tsichritzis, Dionysios C., and Frederick H. Lochovsky. Data Models. Englewood Cliffs, N.J.: Prentice-Hall, 1982.

A complete reference work covering different types of data models.

Tufte, Edward. Envisioning Information. Cheshire, Conn.: Graphics Press, 1983.

This and the next book will give you new insights into how data can be meaningfully displayed.

Tufte, Edward. The Visual Display of Quantitative Information. Cheshire, Conn.: Graphics Press, 1983.

This is a wonderful book. Tufte explains how to avoid the junky graphs and charts that are being endlessly churned out of desktop publishing systems. He further explains his concept of “data-ink”: how to get the most out of your graphics. It was the best book we read that year. Buy a copy and give it to yourself for your next birthday.

Ward, Paul T. Systems Development Without Pain: A User’s Guide to Modeling Organizational Patterns. Englewood Cliffs, N.J.: Prentice-Hall, 1984.

A good introduction to structured analysis for users and junior team members alike.

Ward, Paul T, and Stephen J. Mellor. Structured Development for Real-Time Systems, Vols. 1-3. Englewood Cliffs, N.J.: Prentice-Hall, 1986.

Presents a method for specifying real-time systems.

Weinberg, Gerald M. Quality Software Management, Vol. 1: Systems Thinking. New York: Dorset House Publishing, 1992.

Weinberg, Gerald M. Quality Software Management, Vol. 2: First-Order Measurement. New York: Dorset House Publishing, 1993.

In these two books of a multi-volume set, Weinberg discusses management of projects with the emphasis on the two most important issues: people and honesty.

Weinberg, Gerald M. Rethinking Systems Analysis & Design. New York: Dorset House Publishing, 1988.

Weinberg has the ability to see things that nobody else can. His different approach here is worthwhile reading.

Yourdon, Edward, ed. Classics in Software Engineering. Englewood Cliffs, N.J.: Prentice-Hall, 1979.

Yourdon, Edward, ed. Writings of the Revolution. Englewood Cliffs, N.J.: Prentice-Hall, 1982.

The collections of papers in these two books trace the history of software engineering.