The Guild Library

Home
About the Guild
Articles
Books
–New Books
–Guild Books
–Guild Library
Consulting
Contact us
Resources
–Requirements
–Software Engineering
–Project Management
–Other
–Cocktails
Requirements Template
Seminars
–Mastering Requirements
–Risk Management
–Requirements Modeling
–Mastering the Requirements Process part II
Services
–Litigation Support
–Project Clinics
–Physical Exam
Volere

 

This is a reading list of our favorite new, and not-so-new, books. A book is listed here if one or more Guildoon considers it interesting enough to pass on to you. Not all the books are professional reading, however we don't guarantee that you will like our taste in leisure reading. We thought that you might like to look into some of these, and will be pleased to hear about your favorite reading. Please send your favorites and worthy additions to the Guild Bookmeister.

The categorization and subject grouping is subjective and quirky. Please let one of us know if you have specific objections, and please let one of us know if you have enjoyed any of our selections.

The books are into broad categories:

Books Useful for Requirements Analysts:

Beyer, Hugh and Karen Holtzblatt. Contextual Design. Defining Customer-Centered Systems. Morgan Kauffmann, San Francisco, 1998.

Bolton, Robert. People Skills. How to Assert Yourself, Listen to Others and Resolve Conflicts. Simon & Schuster, 1979.

Burgess, Anthony. Language Made Plain. Fonatana, London, 1975.

Buzan, Tony with Barry Buzan. The Mind Map Book. BBC Books, London, 1995.

Carroll, John. Scenario-Based Design. John Wiley and Sons. New York, 1995.

Checkland, Peter & J. Scholes. Soft Systems Methodology in Action. John Wiley & Sons, Chichester, 1991.

Checkland, Peter. Systems Thinking, Systems Practice. John Wiley & Sons, Chichester, 1981.

Cockburn, Alistair. Writing Effective Use Cases. Addison-Wesley, 2001.

Constantine, Larry and Lucy Lockwood. Software for Use ­ A Practical Guide to the Models and Methods of Usage-Centered Design. Addison Wesley, New York, 1999.

Cristensen, Clayton. The Innovator's Dilemma. Harvard Business School Press, Boston, Mass. 1997.

Davis, Alan. Software Requirements - Objects, Functions and States. Prentice-Hall, Englewood Cliffs, NJ, 1993.

DeGrace, Peter and Leslie Hulet Stahl. Wicked Problems, Righteous Solutions. Yourdon Press, New Jersey, 1990.

Ellinor, Linda and Glenna Gerard. Dialogue: Rediscovering the Transforming Power of Conversation. John Wiley & Sons, New York, 1998.

Fisher, Roger and William Ury. Getting to Yes. Penguin, New York, 1991.

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

____________________ Are Your Lights On? How to Figure Out What the Problem Really Is. Dorset House, New York, 1990.

Gershenfeld, Neil. When Things Start to Think, Henry Holt & Co. New York, 1999.

Graham, Ian. Requirements Engineering and Rapid Development, an object-oriented approach. Addison-Wesley, 1998.

Hatley, Derek, Peter Hruschka and Imtiaz Pirbhai. Process for System Architecture and Requirements Engineering. Dorset House, New York, 2000

Hauser, John and Don Claussing. The House of Quality. Harvard Business Review. Harvard Business School, Boston, 1988.

Hayakawa, S.I. Language in Thought and Action. George Allen & Unwin, London, 1970

Hooks, Ivy F and Kristin A Farry. Customer-Centered Products: Creating successful products through smart Requirements Management, Amacom, 2001.

This book promises to be different. Hooks is very experienced, with a long career at NASA behind her. Kristin Farry is 'an engineer and pilot and a space shuttle flight controller'. This is not your normal requirements book. As soon as you are inside it you understand that they are addressing managers, and telling them how to ensure that the requirements are written before the product is built. I loved the debunking of the corporate requirement management myths:

    1. Everyone knows what the project is about.
    2. Everyone knows how to write requirements.
    3. We already have a requirements management process in place.
    4. Everyone understands our requirements process.
    5. Nothing can be done about bad requirements.

Buy this book for your boss. Buy it from Amazon.com

Jackson, Michael. Software Requirements & Specifications - a lexicon of practice, principles and prejudices. Addison-Wesley, Wokingham, England. 1995. ISBN 0-201-87712-0.

This is a book of ideas. You may not agree with all of them, but all of them will make you think about the subject, and some of them will make you think differently about the subject.

Jackson, Michael. Problem Frames ­ Analysing and structuring software development problems. Addison-Wesley, 2001.

Kelley, Tom. The Art of Innovation. Lessons in creativity from IDEO, America's leading design firm. Doubleday, New York. 2001 Amazon.com

Kilov, Haim, Bernhard Rumpe and Ian Simmonds (editors). Behavioral Specifications of Businesses and Systems. Kluwer Academic Publishing, 1999.

Kotonya, Gerald and Ian Sommerville. Requirements Engineering: Processes and Techniques. John Wiley 1998.

Kovitz, Benjamin. Practical Software Requirements ­ a Manual of Content & Style. Manning, Greenwich CT, 1999.

Lausen, Soren. Software Requirements - Styles and Techniques. Addison-Wesley, London. 2002. Amazon.com

Leffingwell, Dean and Don Widrig. Managing Software Requirements - a Unified Approach. Object Technology Series (Series editors Booch Jacobson Rumbaugh), Addison-Wesley, 2000

Latour, Bruno. ARAMIS or The Love of Technology. Harvard University Press, Massachusetts, 1996.

Lauesen, Søren. Software Requirements - styles and techniques Samfundslitteratur, Copenhagen, 1999

Loucopoulos, Pericles and Vassilios Karakostas. System Requirements Engineering. McGraw-Hill, London, 1995.

Macaulay, Linda. Requirements Engineering. Springer-Verlag, London, 1994.

Maiden N.A.M, C. Ncube & A. Moore Acquiring Requirements for Commercial Off-The ­Shelf Pagage Selection: Some Lessons Learned. City University 1998

McMenamin, Steve & John Palmer. Essential Systems Analysis. Yourdon Press, New York, 1984.

Moore, Geoffrey. Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers. HarperBusiness, 1999.

Norman, Donald. The Design of Everyday Things. Doubleday, New York, 1990.

___________ The Invisible Computer. MIT Press, Cambridge, Mass. 1999.

Pardee, William. To Satisfy & Delight Your Customer. Dorset House, New York, 1996.

Peters, Tom. The Circle of Innovation. Alfred A. Knopf, New York, 1997.

Petrowski, Henry. The Evolution of Useful Things. Pavilion, London, 1993.

Prieto-Diaz, Rubén & Guillermo Arango. Domain Analysis and Software Systems Modeling. IEEE Computer Society Press 1991.

Robertson, James & Suzanne. Complete Systems Analysis - the Workbook, the Textbook, the Answers. Dorset House, New York, 1994.

_______________________ Mastering the Requirements Process. Addison-Wesley, 1999.

Schank, Roger. Tell Me a Story ­ Narrative and Intelligence. Northwestern University Press, Evanston IL. 1990.

Seybold, Patricia Customers.com: How to Create a Profitable Business Strategy for the Internet and Beyond. Times Books, 1998.

Sommerville, Ian and Pete Sawyer. Requirements Engineering ­ a Good Practice guide. John Wiley & Sons, Chichester, England, 1998.

Terninko, John. Step-by-step QFD. Second Edition. St. Lucie Press, Boca Raton FL, 1997.

Weigers, Karl. Software Requirements. Microsoft Press, 1999.

Wieringa, R.J. Requirements Engineering - Frameworks for Understanding. John Wiley, 1996.

Wiley, Bill. Essential System Requirements. Addison-Wesley, 2000.

Young, Ralph. Effective Requirements Practices. Addison-Wesley, 2001.



 

Books About Software Management:

Abdel-Hamid, Tarek and Stuart Madnick, Software Project Dynamics - an Integrated Approach. Prentice-Hall, Englewood Cliffs NJ, 1991.

The authors have investigated the process of building software, modelled the process and used the model to predict the implications of managerial policies. Recommended.

Austin, Robert D. Measuring and Managing Performance in Organizations. New York: Dorset House, 1996.

This book is a must for anyone who ever has to measure anything in a development organization. See foreword by Tim Lister and Tom DeMarco.

Boehm, Barry. Software Risk Management. IEEE Computer Society Press, Los Alamitos, CA. 1989.

Charette, Robert. Software Engineering Risk Analysis and Management. McGraw-Hill, New York, 1989.

Cusumano, Michael and Richard Selby. Microsoft Secrets. Free Press, New York, 1995. ISBN 0-02-874048-3.

Cusamano and Selby were given access to Microsoft, and how they produce their market-dominating software. There is something here for all of us.

DeMarco, Tom. Why Does Software Cost So Much? And Other Puzzles of the Information Age. Dorset House, New York, 1995. ISBN 0-932633-34-X.

A collection of essays adapted from DeMarco's writing over the past decade or so. Each one has something for you. Pay particular attention to essays 2 and 3: Mad About Measurement and Management-Aided Software Engineering. (See Ed Youdon's review of this book, reprinted from American Programmer.)

DeMarco, Tom. The Deadline. Dorset House, New York, 1997.

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

Fenton, Norman and Shari Lawrence Pfleeger. Software Metrics: A Rigorous and Practical Approach International Thomson Computer Press, 1997

Function Point Counting Practices Manual. International Function Point Users Group, Westerville OH.

Garmus, David and David Herron. Measuring the Software Process. Yourdon Press, New Jersey, 1996.

Gilb, Tom with Susannah Finzi. Principles of Software Engineering Management. Addison-Wesley, Wokingham, England, 1988.

Jones, Capers. Applied Software Measurement. McGraw-Hill, 1991

Jones, Capers. Assessment and Control of Software Risks. Yourdon Press, Englewood Cliffs, New Jersey, 1994. ISBN 0-13-741406-4.

Jones takes a masterly look at the 63 software risks, assesses each one for susceptibility, causes, prevention, treatment and so on. This book contains valuable information for anyone starting software projects today.

Jones, Capers. Software Quality - Analysis and Guidelines for Success. International Thomson, Boston, Massachusetts, 1997

Maguire, Steve. Debugging the Development Process. Microsoft Press, Redmond, Washington, 1994.

Schelling, Thomas. The Strategy of Conflict. Harvard University Press, Massachusetts, 1980.

Senge, Peter. The Fifth Discipline. Doubleday, New York, 1990.

Thomsett, Rob. Third Wave Project Management: A Handbook for Managing the Complex Information Management Systems of the 1990's. Prentice-Hall/Yourdon Press, New York, 1993.

van Solingen, Rini and Egon Berghout. The Goal/Question/Metric Method ­ A practical guide for quality improvement of software development. McGraw Hill, 1999.

Weigers, Karl. Creating a Software Engineering Culture. Dorset House, New York, 1996

Weinberg, Jerry. Quality Software Management. Dorset House, New York.

Volume 1 Systems Thinking (1992, ISBN 0-932633-22-6) looks at the problem of thinking about the correct "system" - the system for doing business, and not just the computer system. Volume 2 First-Order Measurement (1993 ISBN 0-932633-24-2) tackles the subject of how measurement is part of any quality movement. Volume 3 Congruent Action (1994, ISBN 0-932633-28-5) solves the problem of acting together to solve problems. Volume 4 Anticipating Change (1997 ISBN 0-932633-32-3) discusses the idea of managing change. Together, these books make a complete and comprehensive guide for the modern software manager.

 

 

Books About Software Development:

Beyer, Hugh and Karen Holtzblatt. Contextual Design. Defining Customer-Centered Systems. Morgan Kauffmann, San Francisco, 1998.

Booch, Grady, James Rumbaugh and Ivar Jacobson. Unified Modeling Language User Guide. Addison Wesley, 1998.

Buschmann, Frank, Regine Meunier, Hans Rohnert, Peter Sommerlad and Michael Stal. Pattern-Oriented Software Architecture - A System of Patterns. John Wiley & Sons, Chichester, England, 1996. ISBN 0-471-95869-7.

Carroll, John. Scenario-Based Design. John Wiley and Sons. New York, 1995.

Checkland, Peter & J. Scholes. Soft Systems Methodology In Action. John Wiley & Sons, Chichester, 1991.

Cook, Steve and John Daniels. Designing Object Systems. Object-oriented Modeling with Syntropy. Prentice-Hall, Hemel Hempstead, England. 1994. ISBN 0-13-203860-9.

Coplien, James and Douglas Schmidt (Eds.) Pattern Languages of Program Design. Addison-Wesley, Reading, Massachusetts, 1995. ISBN 0-201-60734-4.

Davis, Alan. Software Requirements - Objects, Functions and States. Prentice-Hall, Englewood Cliffs, NJ, 1993.

DeGrace, Peter and Leslie Hulet Stahl. Wicked Problems, Righteous Solutions. A Catalogue of Modern Software Engineering Paradigms. Yourdon Press, Englewood Cliffs, NJ, 1990. ISBN 0-13-590126-X.

Dustin, Elfriede et al. Automated Software Testing Published by Addison-Wesley, 1999.

This book is a useful guide for software engineers and software project managers, responsible for software test activities. Likewise, the book also serves as a textbook for the classroom setting, supporting software engineers who wish to develop modern software test skills. The organization of the book is correlated with the phases, tasks and steps of the test lifecycle with a special emphasis on the automated test tool introduction process. Case studies are provided from lessons learned and the experience of many different software test professionals on many different project teams. The book contains a reprint of Suzanne Robertson's article "An Early Start to Testing: How to test Requirements".

Fowler, Martin. UML Distilled: Applying the Standard Object Modeling Language. Addison Wesley, 1997.

Gamma, Eric, Richard Helm, Ralph Johnson and John Vlissides. Design Patterns - Elements of Reusable Object-Oriented Software. Addison-Wesley, Reading Mass. 1995. ISBN 0-201-63361-2. Tom DeMarco's review of this book, reprinted from IEEE Software Magazine

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

____________________ Are Your Lights On? How to Figure Out What the Problem Really Is. Dorset House, New York, 1990.

Gilb, Tom with Susannah Finzi. Principles of Software Engineering Management. Addison-Wesley, Wokingham, England, 1988. ISBN 0-201-19246-2.

Gilb, Tom and Dorothy Graham. Software Inspection. Addison-Wesley, Wokingham, England, 1993. ISBN 0-201-63181-4.

Hay, David C. Data Model Patterns, Conventions of Thought, Dorset House, New York, 1995.

Structures common to many types of business are analyzed in domains like accounting, material requirements planning, contracts and process manufacturing.

Jacobson Ivar, Martin Griss, Patrik Jonsson: Software Reuse: Architecture Process and Organization for Business Success. Addison-Wesley Longman, Wokingham, June 1997.

Jacobson, Ivar, Grady Booch and James Rumbaugh. The Objectory Software Development Process. Addison Wesley, 1998.

Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, Gunnar Övergaard. Object Oriented Software Engineering - a Use case Driven Approach. Addison-Wesley, Wokingham, England, 1992.

Macaulay, Linda. Requirements Engineering. Springer-Verlag, London, 1994.

Maguire, Steve. Debugging the Development Process. Microsoft Press, Redmond, Washington, 1994.

McConnell, Steve. Code Complete. Microsoft Press, Redmond, Washington, 1993. ISBN 1-55615-484-4

This book is about good programming. Period. If you earn you money writing code, buy this book.

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

This is a breakthrough book. It introduces event partitioning as a way of breaking the system into units for study, and discusses how by finding the essential, or logical, system you find a better basis for any new implementation.

Oestereich, Bernd, Peter Hruschka, et.al.. Erfolgreich mit Objektorientierung. Oldenbourg, München, 1999.

Page-Jones, Meilir. What Every Programmer Should Know about Object-Oriented Design. Dorset House, New York, 1995. ISBN 0-932633-31-5.

A very valuable book as it concentrates on the design of object systems, and skips the breathless prose on how wonderful objects are. This is recommended for those about to enter the object world, or those who wonder why they did. This book was awarded a Software Development Magazine Jolt award.

Fundamentals of Object-Oriented Design in UMLPage-Jones, Meilir. Fundamentals of Object-Oriented Design in UML. Foreword by Larry Constantine. Addison-Wesley, 1999. ISBN: 020169946X

This is part of the Addison-Wesley UML series (Booch, Jacobson, Rumbaugh series editors). But this is not yet another book about the UML notation. This book is about design. From the author: "Everyone who writes code also designs code ­ either well or badly, either consciously or unconsciously. My goal in writing this book is to encourage OO professionals to create good object-oriented designs consciously and prior to coding." Buy from Amazon.com

Pardee, William. To Satisfy and Delight Your Customer. Dorset House, New York, 1996. ISBN 0-932633-35-8.

Pfleeger, Charles. Security in Computing. Prentice Hall, New Jersey, 1997.

Pfleeger, Shari Lawrence. Software Engineering ­ Theory and Practice. Prentice Hall, New Jersey, 1998.

Prieto-Diaz, Rubén & Guillermo Arango. Domain Analysis and Software Systems Modeling. IEEE Computer Society Press 1991.

Robertson, James and Suzanne. Complete Systems Analysis: the Workbook, the Textbook, the Answers, Dorset House, New York, 1994.

This book contains a complete project which you can work through as a way of learning analysis techniques. The book is partitioned so that it can be used either as a textbook, for management familiarization or a step by step case study with explanations and worked examples.

Rumbaugh, James, Ivar Jacobson and Grady Booch. Unified Modeling Language Reference Manual. Addison Wesley, 1998.

Shlaer, Sally and Steve Mellor. Object-Oriented Systems Analysis. Yourdon Press, Englewood Cliffs, New Jersey, 1988.

____________________. Object Lifecycles - Modeling the World in States. Yourdon Press, Englewood Cliffs, New Jersey, 1992.

Sommerville, Ian and Pete Sawyer. Requirements Engineering ­ a Good Practice guide. John Wiley & Sons, Chichester, England, 1998.

Stevens, Richard, Peter Brook, Ken Jackson and Stuart Arnold. Systems Engineering ­ Coping with Complexity. Prentice Hall Europe 1998.

 

 

Books on Design Philosophy:

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

This is a fascinating book. It shows how to make use of patterns when constructing buildings to make a more livable and beautiful house. We can borrow this idea for software construction as by reusing successful patterns, it would undoubtedly lead to more usable and maintainable systems.

Latour, Bruno. ARAMIS or The Love of Technology. Harvard University Press, Massachusetts, 1996.

Invisible ComputerDon Norman has published the Invisible Computer. Don't be put off by the subtitle: Why Good Products Can Fail, the Personal Computer Is So Complex and Information Appliances Are the Solution. You may not agree with Norman (I didn't) about the personal computer being complex. Read the book instead for the wealth of knowledge Norman brings to the subject, and the insights you will get about designing for use.

Buy it from Amazon.com

 

Norman, Donald A. The Design of Everyday Things. (Previously published as The Psychology of Everyday Things.) New York: Doubleday/Currency, 1988.

RaskinRaskin, Jef. In The Humane Interface, Jef Raskin, the creator of the Apple Macintosh project, demonstrates that many current interface paradigms are dead ends, and that to make computers significantly easier to use requires new approaches. This is not a book about today's cool widgets and interface gimmicks, but a thoughtful treatise on what we should be thinking about when we build our products and their interfaces. Buy from Amazon.com

 

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

An amazing book full of the best advice on how to present information. If you are about to design an information system, do your users a wonderful service and read Tufte first. The book is also wonderful to read. Highly recommended.

_____________ Envisioning Information, Graphics Press, Cheshire, Connecticut, 1983.

Tufte does it again. His second book will give you new insights in to how data can be meaningfully displayed.

___________Visual Explanations. Graphics Press, Cheshire, Connecticut, 1997.

The first book is about numbers, the second about nouns, and this one is about verbs. Visual Explanations shows how changes to data are represented.

Winograd, Terry and Fernando Flores. Understanding Computers and Cognition. Addison-Wesley, Reading, Massachusetts, 1987. ISBN 0-201-11297-3.

Winograd, Terry. Bringing Design to Software. ACM Press, New York, 1996.

 

 

Books Where You Will Find Useful Insights:

Buzan, Tony with Barry Buzan. The Mind Map Book. BBC Books, London, 1995.

Mind maps are a note-taking, and a brainstorming technique. This book from their inventor teaches you how to use them to enhance your thinking.

Bolton, Robert. People Skills. How to Assert Yourself, Listen to Others and Resolve Conflicts. Simon & Schuster, 1979.

Burgess, Anthony. Language Made Plain. Fonatana, London, 1975.

Christensen, Clayton. The Innovator's Dilemma. Harvard Business School Press, 1997.

Demarco, Tom. Slack ­ Getting past burnout, busywork and the myth of total efficiency. Broadway Books, New York. 2001.

Ellinor, Linda and Glenna Gerard. Dialogue: Rediscovering the Transforming Power of Conversation. John Wiley & Sons, New York, 1998.

Garfinkel, Simson. Database nation ­ the death of privacy in the 21st century. O'Reilly, 2001.

Gleik, James. Faster: the acceleration of just about everyhting. Vintage Books, 2000. ISBN: 067977548X. Faster ells of the acceleration that affects almost everything that we do. Some of this acceleration is due to the technology that we use ­ email instead of "snail mail" ­ and some of it due to the growing impatience (or accelerated expectations) of humans living in modern urban areas ­ the obsession with saving two seconds by pressing the door close button in elevators. James Gleick's commentary is enlightening and interesting. Buy from Amazon.com

 

Johnson, Steven. Interface Culture. How technology transforms the way we create and communicate. Basic Books, 1997

Latour, Bruno. ARAMIS or The Love of Technology. Harvard University Press, Massachusetts, 1996.

Norman, Donald. The Design of Everyday Things. Doubleday, New York, 1990.

Pardee, William. To Satisfy & Delight Your Customer. Dorset House, New York, 1996.

Petrowski, Henry. The Evolution of Useful Things. Pavilion, London, 1993.

Schank, Roger. Tell Me a Story ­ Narrative and Intelligence. Northwestern University Press, Evanston IL. 1990.

Schelling, Thomas. The Strategy of Conflict. Harvard University Press, Massachusetts, 1980.

Senge, Peter. The Fifth Discipline. Doubleday, New York, 1990.

Sobel, Dava. Longitude: The true story of a genius who solved the greatest scientific problem of his time. Penguin Books. London, 1995

Tufte, Edward. Visual Explanations. Graphics Press, Cheshire, Connecticut, 1997.

United States Marine Corps. Warfighting. Currency Doubleday, New York, 1994.

3Journals:

IEEE Software. Published by IEEE Computer Society.

This, in my humble opinion, is the best magazine on software engineering. It has some of the most authoritative writers and editors, and is extremely readable. If you do end up on a desret island, and can get only one journal delivered, make it IEEE Software.

Interactions. Published by the ACM.

This is a different style of magazine and we like it. The subject is human-computer interaction, but at a much higher plane than buttons and widgets. Get a feeling for the magazine at their web site.

Software Development Magazine. Published by Miller Freeman Inc.

I like this magazine, but subscribe, don't buy it from the newsstand. Not every issue has something you want, but fairly often they produce an issue that is crammed with great information. Don't miss that one as it is worth the whole year's subscription.

 

 

 

top of page

home |  about |  articles |  books |  consulting |  litigation support |  resources |  physical exam |  clinics |  template |  seminars |  services