This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
CMMI, Six Sigma, and Agile: What to Use and When for Embedded Software Development
Technical Paper
2007-01-4183
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
This paper discusses the leading approaches to developing high-quality embedded software: Capability Maturity Model Integration® (CMMI), Six Sigma processes, and Agile software development methods. Organizations often struggle with deciding which approach they should use. Their decisions can have strategic consequences in terms of talent acquisition, organizational structure, resource allocation, and project management. Real life examples of embedded software development projects will be used to illustrate how, depending on the circumstances of the project, CMMI, Six Sigma, and Agile approaches each have a role to play in achieving embedded software excellence. CMMI is ideal for a well defined project, similar to the process an orchestra might use to prepare for a concert when given the sheet music. Six Sigma fits an existing project with running changes or a smaller project that needs to minimize risk in its development, similar to making a specific improvement to one section (e.g. trombones) in the orchestra. Agile is ideal for an unstructured, unknown requirements environment where requirements are discovered throughout development, similar to an improvisational jazz performance. Recommendations are provided that help guide the reader on how to make the process fit the project versus having the project fit the process.
Recommended Content
| Journal Article | Challenges in Validating Safety-Critical Embedded Systems |
| Technical Paper | Rapid Application Development for Embedded Systems Using CAN Calibration Protocol |
Authors
Citation
Stevens, R. and Lenz, J., "CMMI, Six Sigma, and Agile: What to Use and When for Embedded Software Development," SAE Technical Paper 2007-01-4183, 2007, https://doi.org/10.4271/2007-01-4183.Also In
References
- Beck, Kent, et. al. “Manifesto for Agile Software Development” Agile Alliance http://agilemanifesto.org/ 2001
- Boehm, Barry W. “A Spiral Model of Software Development and Enhancement,” ACM SIGSOFT Software Engineering Notes 11 4 August 1986
- Brooks, Frederick P., Jr. The Mythical Man-Month: Essays on Software Engineering Anniversary 1995
- Chrissis, Mary Beth Konrad Mike Shrum Sandy CMMI: Guidelines for Process Integration and Product Improvement Addison-Wesley 2nd 2007
- Dichter, Carl “Is It Designed Right?” Unix Review 51 58 June 1993
- Fornari, Arthur “Lean Six Sigma Leads Xerox” Six Sigma Forum Magazine 11 16 August 2004
- O'Boyle, Thomas F. “Chilling Tale: GE Refrigerator Woes Illustrate the Hazards in Changing a Product,” The Wall Street Journal A1 May 7 1990
- Phillips, Mike “CMMI Version 1.2 and Beyond,” SEPG 2007 Conference March 26 2007
- Rae, Jeneanne “Viewpoint: Have It Both Ways - ‘Ambidexterous’ Companies Can Handle Incremental Change and Bold Initiatives,” Business Week 4038 16 June 11 2007
- Repenning, Nelson P. Sterman John D. “Nobody Ever Gets Credit for Fixing Problems that Never Happened: Creating and Sustaining Process Improvement,” California Management Review 43 4 Summer 2001
- Richardson, Karen “The ‘Six Sigma’ Factor for Home Depot - Departure of CEO Nardelli Brings Into Focus a Management Technique He Championed,” The Wall Street Journal C3 January 4 2007
- Siviy, Jeannine Hallowell Dave “Bridging the Gap between CMMI and Six Sigma Training” Software Engineering Institute, Carnegie Mellon University http://www.sei.cmu.edu/sema/presentations.html 2005