How to Read This Book

Software Development is divided into four parts focusing on the background, people, processes, and technology of successful software development projects. While we hope you read this book from cover to cover, a short, one page or less, introduction is provided at the start of each chapter. Anyone seriously interested in software development, from novice programmers to the most experienced architects and managers, should at least read the introduction to each chapter. In addition,Chapter 1, "The Ten Commandments of Successful Software Development", should be read completely as it summarizes what we believe are the ten most important concepts anyone associated with a software development project should be familiar with. These ten commandments will be referred to again and again throughout the rest of the book. Software architects, developers, and managers will then probably read the various chapters more or less thoroughly depending on theirspecific interests. The following provides some additional information to help guide you through the four parts of this book.

Part One consists of Chapters 1 through 4 and provides a general background in software development concepts. Software developers and architects can skim through Chapters 2 through 4 as they will probably be familiar with most of this material. Software development managers and MIS managers, especially those without a strong development background, should read through this material and be certain they understand the concepts as they provide a basis for the topics covered in the remainder of the book. Chapters 5 through 9 make up Part Two of the book, focusing on people issues related to software development. This is perhaps the most important section of the book for software development managers. Part Three, Chapters 10 through 13, focuses on software development processes. This part of the book should be of interest to all readers. While it has been said that software development is still more of an art than a science, projects following mature, "best practice" development processes areconsistently more successful than those that don't. Chapters 14 through 22 comprise Part Four of the book and cover software development technology. These chapters are more likely to be read thoroughly by a software architect or developer, although managers should at least be familiar with the concepts presented therein.