AINSI - An Inductive Software Process Improvement Method: Concrete Steps and Guidelines
| dc.contributor.author | Briand, Lionel | en_US |
| dc.contributor.author | Eman, Kaled El | en_US |
| dc.contributor.author | Melo, Walcelio L. | en_US |
| dc.date.accessioned | 2004-05-31T22:33:39Z | |
| dc.date.available | 2004-05-31T22:33:39Z | |
| dc.date.created | 1995-07 | en_US |
| dc.date.issued | 1998-10-15 | en_US |
| dc.description.abstract | Top-down approaches to process improvement based on generic "best practice" models (e.g., CMM, TRILLIUM, BOOTSTRAP, SPICE) have become popular. Despite the idiosyncrasies of each of these approaches, they share some common characteristics: all of them are based on numerous assumptions about what are best practices, and about the business goals of organizations and the problems they face. Other organizations, like the Software Engineering Laboratory of the NASA Goddard Space Flight Center, HP and CRIM in Canada, have adopted the Quality Improvement Paradigm (QIP). The QIP stipulates a more bottom-up and inductive approach to process improvement. The focus of this paradigm is to first understand what processes exist in the organization and to determine what causes the most significant problems. Based on this, opportunities for improvement are devised, and empirical studies are conducted to evaluate potential solutions. In this paper, we present a method, named AINSI (An INductive Software process Improvment method), which defines general but concrete steps and guidelines for putting in place the QIP. This method is the result of the collective experiences of the authors and integrates many lessons learned from process improvement efforts in different environments. It also integrates many complementary techniques such as qualitative analysis, methods for data collection (e.g., the Goal/Question/Metric paradigm), and quantitative evaluation. (Also cross-referenced as UMIACS-TR-95-77) | en_US |
| dc.format.extent | 87197 bytes | |
| dc.format.mimetype | application/postscript | |
| dc.identifier.uri | http://hdl.handle.net/1903/744 | |
| dc.language.iso | en_US | |
| dc.relation.isAvailableAt | Digital Repository at the University of Maryland | en_US |
| dc.relation.isAvailableAt | University of Maryland (College Park, Md.) | en_US |
| dc.relation.isAvailableAt | Tech Reports in Computer Science and Engineering | en_US |
| dc.relation.isAvailableAt | UMIACS Technical Reports | en_US |
| dc.relation.ispartofseries | UM Computer Science Department; CS-TR-3498 | en_US |
| dc.relation.ispartofseries | UMIACS; UMIACS-TR-95-77 | en_US |
| dc.title | AINSI - An Inductive Software Process Improvement Method: Concrete Steps and Guidelines | en_US |
| dc.type | Technical Report | en_US |