Controlling the software development process

Large systems can be composed of millions of lines of software code, developed by many companies, where the software works with hardware items being developed by many other companies, plus people, policies, constraints, regulations, and a myriad of other factors—and it all must be integrated, work seamlessly, delivered on time and within the budget.

Reference Source of Information: The guidebook describes what must be or should be done, who should do it, when it needs to be done, and what work products should be produced during each stage of the system development life cycle. Learn more at: 'Amazon Gechman'

Who should read this guidebook? The guidebook is a vital source to software project managers, everyone on the system development team, Information Technology departments, system stakeholders, and especially programmers who are promoted to software project manager positions. For students, this guidebook is likely a first time view of the real world of building large complex software-intensive systems.

Reader Friendly:  The Guidebook was planned to make it interesting, as easy as possible to understand, and easy to find topics of interest.  It is illustrated with over 80 figures and over 130 tables providing a wealth of practical information in a succinct format.  

 Tailoring guidelines are provided to meet the needs of each system. The Guidebook has in-depth descriptions of the incremental buildup of structured step-by-step stages covering the full system development life cycle from system concept to system retirement.