SC 207 - Term Paper

Related Work
 

Home

1.  Introduction
1.1  About Topic
1.2  Relation to SC207
1.3  New Contributions
1.4  Elaboration

2.  Related Work
2.1  Table

3.  Comments
3.1  Uses
3.2  Improvement
3.3  Notations / Diagrams
3.4  Results
3.5  Future

4.  References
4.1  Materials

 

 

Table

Some of the relevant material specified in the article are unable to be found both online and in the library database.

 

Author(s) Year Article Some Description Relation to Article
W.S. Humphrey T.R. Snyder R.R. Willis July 1991 Software process improvement at Hughes Aircraft After initial assessment found the Software Engineering Division (SED) to be a level two organization, strengths and weaknesses of the SED were indentified and recommendations were made for process improvement. After establishing and implementing an action plan, the SED grew from level 2 to a level 3 in just 2 years. This paper shows clearly the differences between initial and final assessment for the growth one process maturity level. 
R. Dion July 1993 Process Improvement and Corporate Balance Sheet By attempting process improvement based on a 3-phase cycle of stabilization, control and change, the maximum benefits attainable were calculated.    It is shown that a cut down on rework costs due process-improvement  has increased productivity. Thus proving the thesis of the article.
J. Herbsleb 1994 Benefits of CMM-Based Software Process Improvement : Initial Results Data from 13 organizations were collected and analyzed to obtain information on the results of CMM-based software process improvement efforts Different case studies proved the thesis that that software process improvement can pay off.
H.Wohlwend  S.Rosenbaum Nov 1994 Schlumberger's software improvement program

A software process improvement effort was started of by a small group. As productive changes occurred across the company, improvements in many development areas, including project planning and requirements management, were observed.

This paper shows how  process maturity was taught and calculated in a major company.
M.C.Paulk 1995

Capability Maturity Model, The: Guidelines for Improving the Software Process

 
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  immature process to a mature, disciplined process, in a path laid out in five levels Article uses the SW-CMM model described. It has also refined SW-CMM model to break up CMM Level 1 to CMM-Level 1 Lower half and CMM-Level 1 Upper half.
Judith G. Brodman  Donna L. Johnson 1996 Return on Investment(ROI) from Software Process
Improvement as Measured by U.S. Industry
This report describes the research results, which include a profile of metric usage according to software maturity level (Levels 1 through 5) and the organizational factors that contribute to higher and lower process maturity. This research uses similar methods as article to collect data but uses a mapping technique to derive the relationship between process improvement trends and organization
B.K. Clark 1997 The Effects of Software Process Maturity on Software Development Effort This research examines the effects of Software Process Maturity, using a SW-CMM, on development effort, where effort is the primary determinant of software development cost and schedule. The article is just an extension of this report. This report explains clearly the equations derived for the article.
Thomas McGibbon
 
1999 A Business Case for Software Process Improvement Revised The benefits of improved software management has been demonstrated from a business, profit and loss, and senior management perspective using software process improvement techniques. The intent is to generalize and model the cost benefits one can achieve from software process improvement. This report examines the Software Process Improvement (SPI)  and shows the cost benefits attainable through SPI. Cocomo Model is used to create a  spreadsheet. 
B.Boehm 2000 Software Cost Estimation with COCOMO II Defines COCOMO II which is a classic rework of the COCOMO model to address modern software processes and construction techniques along with representative examples of applying the models to key software decision situations. It also introduces emerging COCOMO II extensions for cost and schedule estimation of COTS integration and rapid development. Article uses the CocomoII Model based on this paper to derive the equation to carry out the study.
Hosted by www.Geocities.ws

1