<p><p>The concept of processes is at the heart of software and systems engineering. Software process models integrate software engineering methods and techniques and are the basis for managing large-scale software and IT projects. High product quality routinely results from high process quality.</p>
Managing the Software Process
β Scribed by Watts S. Humphrey
- Publisher
- Publishing Company
- Year
- 1990
- Tongue
- English
- Leaves
- 520
- Series
- The SEI Series in Software Engineering
- Edition
- 1990
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
The author, drawing on years of experience at IBM and the SEI, provides here practical guidance for improving the software development and maintenance process. He focuses on understanding and managing the software process because this is where he feels organizations now encounter the most serious problems, and where he feels there is the best opportunity for significant improvement. Both program managers and practicing programmers, whether working on small programs or large-scale projects, will learn how good their own software process is, how they can make their process better, and where they need to begin.
"This book will help you move beyond the turning point, or crisis, of feeling over-whelmed by the task of managing the software process to understanding what is essential in software management and what you can do about it." - Peter Freeman, from the Foreword
About the Author
Known as βthe father of software quality,β Watts S. Humphrey is the author of numerous influential books on the software-development process and software process improvement. Humphrey is a fellow of the Software Engineering Institute (SEI) at Carnegie Mellon University, where he founded the Software Process Program and provided the vision and early leadership for the original Capability Maturity Model (CMM). He also is the creator of the Personal Software Process (PSP) and Team Software Process (TSP). Recently, he was awarded the National Medal of Technologyβthe highest honor given by the president of the United States to America's leading innovators.
β¦ Table of Contents
1 A Software Maturity Framework
2 The Principles of Software Process Change
3 Software Process Assessment
4 The Initial Process
5 Managing Software Organizations
6 The Project Plan
7 Software Configuration Management--Part 1
8 Software Quality Assurance
9 Software Standards
10 Software Inspections
11 Software Testing
12 Software Configuration Management--(Continued)
13 Defining the Software Process
14 The Software Engineering Process Group
15 Data Gathering and Analysis
16 Managing Software Quality
17 Defect Prevention
18 Automating the Software Process
19 Contracting for Software
20 Conclusion
Appendix A A Software Process Maturity Framework
Appendix B Software Engineering Assessment Agreement
Appendix C Conducting Software Inspections
β¦ Subjects
Nonfiction, Computers, General, Programming, Software Development & Engineering, Business & Productivity Software, Project Management Tools, Software engineering -- Management; 54.52 software engineering; Ontwerpen; Beheer; Software; GeΜnie logiciel; toepassingen; applications; computer software; programmeren; programming; software-ontwikkeling; software engineering; Software, Application Programs
π SIMILAR VOLUMES
Not connecting software project management (SPM) to actual, real-world development processes can lead to a complete divorcing of SPM to software engineering that can undermine any successful software project. By explaining how a layered process architectural model improves operational efficiency, <b
<P>Using actual examples of software process improvement from the private sector and government, this work demonstrates how quality systems, measurement techniques and performance evaluations work. It presents a methodology for analyzing an ongoing software development process and establishing a rat
The examples can be kind of wordy and not always widely relevant, but there's a lot of good common sense and eye opening truth here for developers of all kinds (although probably mostly for leads, managers, execs).
Providing practical insights on how to best manage technical professionals, this text demonstrates that people are important in building software systems and suggests how to identify, motivate and organize innovative people. The work explains how teams can be used to solve difficult problems and und