|Christensen, Mark / Thayer, Richard H.|
The Project Manager's Guide to Software Engineering's Best Practices
Software Engineering Best Practices
2002. 552 Pages, Softcover
ISBN 978-0-7695-1199-3 - John Wiley & Sons
Since the earliest days of the computer industry, managing a software project has been a complex and demanding activity. While the technical content of software products and the technical methods used to build them have changed over time, the fundamental issues that determine the success or failure of software projects have remain fairly constant. That is, the same fundamental management mistakes continue to be made. To cite a few examples; requirements are unclear at the beginning of projects and are not managed during the project, the product is not tested adequately, schedules are misestimated or not tracked in sufficient detail. The contents of this book, together with the underlying IEEE Standards, are dedicated to helping the reader in their work: The continuing quest to produce quality software products in a predictable manner.
This book, containing all original material, is based on the proposition that the IEEE Software Engineering Standards capture many of the fundamental 'best practices' of software project management. It is written to assist the reader in applying those standards to their projects and company. To meet this goal, the authors discuss and elaborate the standards that bear on the three key management areas of: Software systems engineering, Processes for developing software products, Planning and control of software project activities.
The body of the book is correspondingly organized into three parts. Software Systems Engineering, which argues that software development projects are most successful when developed using a systems level viewpoint. Process Management and Control, which describes the key activities needed to define, support, and manage a project's software development processes. Project Planning and Management completes the book, integrating the elements of cost and schedule estimation and control, risk management, and the role metrics play in performing those tasks.
From the contents
I: Software Systems Engineering.
1. Software Systems Engineering.
2. Concept of Operations.
3. Software Requirements Specification.
4. Software User Documentation.
5. Software Verification and Validation.
6. Software Maintenance.
II: Process Management and Control.
7. Software Life Cycle Process Management.
8. Software Process Improvement.
9. Software Configuration Management.
10. Software Quality Assurance.
11. Software Reviews.
III: Project Planning and Management.
12. Software Cost and Schedule.
13. Software Engineering Project Management.
14. Software Risk Management.
15. Software Metrics.
A. The Work Breakdown Structure.
B. Representing Project Schedules.
About the Authors.