Can any one out there tell what a Butterfly model is? Thanks in advance.
Re: Butterfly model?
Mr. Ram Chillarege, Sr. Manager, IBM
Paper Title: Orthogonal Defect Classification (4A2)
Methods such as Orthogonal Defect Classification and the Butterfly model have changed the face of what software engineering can do. Defect reduction, cost control and productivity enhancements that stretch the limit of what the industry has witnessed in the past two decades.
A Software Reliability Initiative That Costs Less and Delivers More
Kathryn Bassin (Center of Software Engineering, IBM T.J. Watson Research Center)
Abstract: Is this a typical scenario in your organization? An executive is shown a chart that indicates software quality is not at an acceptable level. The executive calls together the management team, and demands an 'n' percent improvement. The managers bring in their technical leads, and explain that results are needed 'now'. The technical leads, already engaged in trying to meet what they believe to be an impossible schedule, drop everything in order to identify and implement actions, usually based on their 'gut feel' and very little technical decision support. The technical teams and managers close their eyes, and cross their fingers, hoping that at least some of the actions will result in a measurable improvement. The Butterfly Model offers a better, proven approach, that costs less and delivers more as exemplified by this case study. On a regular basis, and at critical checkpoints, defect assessments and analysis were performed at the team level, with ODC attribute information forming an important foundation for the analysis. Complete customer reported defect data for the previous release of the component owned by each technical team, was used to capture and assess customer usage. This enabled a strategy which targeted customer usage as the highest priority in terms of defect prevention and defect removal improvements. By utilizing this approach, the speed and accuracy with which the teams identified meaningful actions were greatly improved, as was the return on investment. In this case study, the resource required to identify, prioritize, and implement actions in the 'top-down' approach for one project was 3.5 times the resource required using the Butterfly Model approach in a subsequent, comparable project. The results, in terms of a reduction in Customer Reported Defects was 4 times better with the Butterfly Model approach than the 'top-down' project. The author will describe the steps of the Butterfly Model approach to software reliability improvement, and will provide a detailed explanation of the benefits to the organization, the project, and the bottom line.
[This message has been edited by vantontl (edited 08-31-2001).]