Software project management

About: Software project management is a research topic. Over the lifetime, 10691 publications have been published within this topic receiving 196569 citations.

Managing the development of large software systems

Abstract: INTRODUCTION l am going to describe my pe,-.~onal views about managing large software developments. I have had various assignments during the past nit,.: years, mostly concerned with the development of software packages for spacecraft mission planning, commanding and post-flight analysis. In these assignments I have experienced different degrees of successwith respect to arriving at an operational state, on-time, and wi th in costs. I have become prejudiced by my experiences and I am going to relate some of these prejudices in this presentation.

Software risk management: principles and practices

Abstract: The emerging discipline of software risk management is described. It is defined as an attempt to formalize the risk-oriented correlates of success into a readily applicable set of principles and practices. Its objectives are to identify, address, and eliminate risk items before they become either threats to successful software operation or major sources of software rework. The basic concepts are set forth, and the major steps and techniques involved in software risk management are explained. Suggestions for implementing risk management are provided. >

Software Reliability: Measurement, Prediction, Application

Abstract: Revised and updated for professional software engineers, systems analysts and project managers, this highly acclaimed book provides key concepts of software reliability and practical solutions for measuring reliability.

The Capability Maturity Model: Guidelines for Improving the Software Process

Abstract: I. THE CAPABILITY MATURITY MODEL FOR SOFTWARE: BACKGROUND, CONCEPTS, STRUCTURES AND USAGE. 1. Introducing Software Process Maturity. The Evolution of the CMM. Immature versus Mature Software Organizations. Fundamental Concepts Underlying Process Maturity. Total Quality Management and the CMM. Customer Satisfaction. Benefits and Risks of Model-Based Improvement. 2. The Software Process Maturity Framework. Behavioral Characterization of the Maturity Levels. Skipping Maturity Levels. Visibility into the Software Process. Prediction of Performance. 3. The Structure of the Capability Maturity Model. Internal Structure of the Maturity Levels . Maturity Levels. Key Process Areas. Key Practices. Common Features. 4. Interpreting the CMM. Interpreting the Key Practices. The Key Process Area Template. Interpreting the Common Features. Organizational Structure and Roles. Understanding Software Process Definition. The Evolution of Processes. Applying Professional Judgment. 5. Using the CMM. A CMM-Based Appraisal Method. Process Assessments and Capability Evaluation. Software Process Improvement. Using the CMM in Context. 6. A High-Maturity Example: Space Shuttle Onboard Software. Introduction. Background. Approaches to Process Improvement. Overall Lessons. II. THE KEY PRACTICES OF THE CAPABILITY MATURITY MODEL FOR SOFTWARE. 7. The Key Areas for Level 2: Repeatable. Requirements Management. Software Project Planning. Software Project Tracking and Oversight. Software Subcontract Management. Software Quality Assurance. Software Configuration Management. 8. The Key Process Areas for Level 3: Defined. Organization Process Focus. Organization Process Definition. Training Program. Integrated Software Management. Software Product Engineering. Intergroup Coordination. Peer Reviews. 9. The Key Process Areas for Level 4: Managed. Quantitative Process Management. Software Quality Management. 10. The Key Process Areas for Level 5:Optimizing. Defect Prevention. Technology Change Management. Process Change Management. Appendix A: References. Appendix B: Acronyms. Appendix C: Glossary. Appendix D: Abridged Version of the Key Practices. Appendix E: Mapping the Key Practices to Goals. Appendix F: Comparing ISO 9001 and the CMM. Appendix G: An Overview of ISO's SPICE Project. Appendix H: Change History of the CMM. Appendix I: Change Request Form. Index. 0201546647T04062001

The TAME project: towards improvement-oriented software environments

Abstract: Experience from a dozen years of analyzing software engineering processes and products is summarized as a set of software engineering and measurement principles that argue for software engineering process models that integrate sound planning and analysis into the construction process. In the TAME (Tailoring A Measurement Environment) project at the University of Maryland, such an improvement-oriented software engineering process model was developed that uses the goal/question/metric paradigm to integrate the constructive and analytic aspects of software development. The model provides a mechanism for formalizing the characterization and planning tasks, controlling and improving projects based on quantitative analysis, learning in a deeper and more systematic way about the software process and product, and feeding the appropriate experience back into the current and future projects. The TAME system is an instantiation of the TAME software engineering process model as an ISEE (integrated software engineering environment). The first in a series of TAME system prototypes has been developed. An assessment of experience with this first limited prototype is presented including a reassessment of its initial architecture. >