Software Capability Evaluation (SCE) offers a means to evaluate an organization's software process capability - that is, how well an organization manages the process it used to create software. SCE provides a way to compare an offeror's software capability against a predefined standard. This document is an implementation guide: it is intended as a set of practical information which program managers can use to guide them through the process of using SCE in an acquisition. Capability Maturity Model (CMM), Software capability evaluation, Software process.
This report describes Version 1.5 of the Software Capability Evaluation (SCE) method, as taught at the Software Engineering Institute (SEI) from January 1992 to June 1993. This version of the SCE method is based on the process maturity framework defined in Characterizing the Software Process: Maturity Framework (CMU/SEI-87-TR-11, ADA197671), which predates Version 1.0 of the Capability Maturity Model (CMM) described in Capability Maturity Model for Software (CMU/SEl-91-TR 24, ADA240603). The document includes a background overview of the SCE method and its evolution, a detailed description of the activities performed during an SCE, and a discussion of the characteristics of the method and their implications for the use of the method. This as built description provides a baseline for future evolution of the SCE method. Capability maturity model, Software capability evaluation, Software process.
"The increasing rate of technological change we are experiencing in our lifetime yields competitive advantage to organizations and individuals who are willing to embrace risk and the opportunities it presents. Those who choose to minimize or avoid risk, as opposed to managing it, set a course for obsolescence. Hall has captured the essence of risk management and given us a practical guide for the application of useful principles in software-intensive product development. This is must reading for public and private sector managers who want to succeed as we begin the next century." - Daniel P. Czelusniak, Director, Acquisition Program Integration Office of the Under Secretary of Defense (Acquisition and Technology) The Pentagon "Since it is more than just common sense, the newcomer to risk management needs an intelligent guide. It is in this role that Elaine Hall's book excels. This book provides a set of practical and well-delineated processes for implementation of the discipline." - Tom DeMarco, from the Foreword Risk is inherent in the development of any large software system. A common approach to risk in software development is to ignore it and hope that no serious problems occur. Leading software companies use quantitative risk management methods as a more useful approach to achieve success. Written for busy professionals charged with delivering high-quality products on time and within budget, Managing Risk is a comprehensive guide that describes a success formula for managing software risk. The book is divided into five parts that describe a risk management road map designed to take you from crisis to control of your software project. Highlights include: Six disciplines for managing product development. Steps to predictable risk-management process results. How to establish the infrastructure for a risk-aware culture. Methods for the implementation of a risk management plan. Case studies of people in crisis and in control.
Principal Contributors and Editors: Mark C. Paulk, Charles V. Weber, Bill Curtis, Mary Beth Chrissis "In every sense, the CMM represents the best thinking in the field today... this book is targeted at anyone involved in improving the software process, including members of assessment or evaluation teams, members of software engineering process groups, software managers, and software practitioners..." From the Foreword by Watts Humphrey The Capability Maturity Model for Software (CMM) is a framework that demonstrates the key elements of an effective software process. The CMM describes an evolutionary improvement path for software development from an ad hoc, immature process to a mature, disciplined process, in a path laid out in five levels. When using the CMM, software professionals in government and industry can develop and improve their ability to identify, adopt, and use sound management and technical practices for delivering quality software on schedule and at a reasonable cost. This book provides a description and technical overview of the CMM, along with guidelines for improving software process management overall. It is a sequel to Watts Humphrey's important work, Managing the Software Process, in that it structures the maturity framework presented in that book more formally. Features: Compares the CMM with ISO 9001 Provides an overview of ISO's SPICE project, which is developing international standards for software process improvement and capability determination Presents a case study of IBM Houston's Space Shuttle project, which is frequently referred to as being at Level 5 0201546647B04062001
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 0201180952B04062001
In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).
