|
Establishing a SEI Capability Maturity Model Level 3 Metrics Program--And Living to Tell About It Metrics are foundational to CMM Levels 3, 4, and 5. However, introducing all of the metrics required by CMM Level 3 into your organization can seem like an insurmountable task. Examine a case study of the development and deployment of a successful CMM Level 3 metrics program. Learn about each major Level 3 metrics requirement and obtain examples on how they can be addressed.
|
Greg Parent, EDS
|
|
Using Software Measurement to Effect Change Using a real-life case study, Jeanette Horan presents how the search for product quality improvement at Lotus led to the realization that the software measurement process needed to be changed to drive organizational priorities. Learn how a cross-functional team provided recommendations for a new process, standardized on core metrics, and implemented a new self-service application. Discover how the use of innovative technology and active participation by the stakeholders resulted in a consistently streamlined process that allows fact-based decision making resulting in improved product quality and customer satisfaction.
|
Jeanette Horan, Lotus Development Corporation
|
|
Interpreting Graphical Defect Trend Data Evaluation of graphical defect trend data can dramatically increase your ability to predict current project quality, schedule milestone compliance, and provide historical data for proper test and development scheduling of later revisions. Jim Olsen will explore some of the complexities in analyzing graphic defect trending in this presentation (winner of the Best Presentation award for ASM'99). Learn ways to determine how much time establishes a trend, when the appropriate time to start taking data occurs, what type of data to track, and how to estimate the amplitude of defect oscillations at the end of the product cycle.
|
Jim Olsen, Novell, Inc.
|
|
Testing Your Software's Requirements Many testing organizations focus primarily on software executable code, but that's not the only thing you can test. For instance, did you ever consider testing your software requirements? When you test only code, you face some big disadvantages, not to mention that design defects often aren't even fixable because they demand too much effort, too late in the release cycle. In fact, it's difficult to even report some requirements defects since the developers have already committed to the design strategy. But if you test your requirements early in the game, you can discover defects before they're cast into designs and code, consequently saving your organization potentially huge rework costs.
|
Brian Lawrence, Coyote Valley Software
|
|
Going Beyond QA: Total Product Readiness The successful release of software requires more than just testing to ensure the product functions properly; success is also defined by how prepared the product is for advertisement, delivery, installation, training, support, etc. In this paper, we’ll discuss how testing can be expanded to cover all aspects of Total Product Readiness (TPR).
|
Douglas Thacker, Liberty Mutual Insurance Group
|
|
High Maturity Benefits and Blarney With more and more organizations claiming to be Capability Maturity Model (CMM) Level four or five, is high maturity all it's cracked up to be? This talk clarifies what attributes should be present in a true high maturity organization, and presents case studies where organizations benefited substantially from achieving these high maturity capabilities. It also addresses practices that, while they technically quality as high maturity, add absolutely no business value to development and its customers.
|
Bill Curtis, TeraQuest
|
|
Sorting Out Six Sigma and the CMM While the Capability Maturity Model has become widely accepted as an approach to software process improvement, Six Sigma is becoming increasingly popular in manufacturing and service organizations. This has resulted in some confusion over methods and conflicts for resources. However, the two approaches are actually synergistic.
|
David Card, Software Productivity Consortium
|
|
Solid Software: Is it Rocket Science? While we can't guarantee that our software will never fail, we can take serious steps to reduce the risk. The toughest kind of system to build involves safety-critical software where the reliability requirements are extremely strict-and whose failure puts lives in jeopardy. Shari Lawrence Pfleeger looks at what "solid software" means, and explores ways we can achieve it. She examines solid software within the context of the proposed National Missile Defense System.
|
Shari Lawrence Pfleeger, Systems/Software, Inc.
|
|
Understanding Variation and Stability: The Key to Managing Your Software Process The control chart is a form of instrumentation that acts like a pressure gauge in the world of software development. It provides critical data to help guide the decisions made by software engineers and managers. This presentation shares the results of studies using statistical process control analysis to monitor and adjust software process improvement activities. It also highlights the correlation between the use of control charts and improved processes.
|
Anita Carleton and William Florac, Software Engineering Institute
|
|
Measurement and the CMM: How Measurement Practices Evolve People who use the Capability Maturity Model (CMM) for software often struggle with the apparent paradigm shift as they move from level to level, particularly when they reach Level four in the CMM one to five level scheme. This presentation illustrates the characteristics of a measurement program at the different CMM maturity levels. It particularly seeks to demystify the Level four concepts of process capability and process performance baselines, and how these concepts are applicable to all CMM levels. The presenter uses real-world examples from a variety of mid- to high-maturity organizations to show participants how to make the transitions across CMM levels without losing momentum.
|
Charlie Weber and Beth Layman, TeraQuest Metrics
|