Evaluation of Software Projects: A Recommendation for Implementation The Iterating Evaluation Model
Independent thesis Advanced level (degree of Master (One Year))Student thesis
Software process improvement (SPI) is generally associated with large organizations. Large organizations have the possibilities to fund software process improvement programs as large scale activities. Often these improvement programs do not show progress until some time has elapsed. The Capability Maturity Model can take one year to implement and not until then can measures be made to see how much quality increased. Small organizations do not have the same funding opportunities but are still in need of software process improvement programs. Generally it is better to initiate a software process improvement program as early as possible, no matter what size of organization. Although the funding capabilities for small organizations are less compared to large organizations, the total required funding will still be smaller than in large organizations. The small organization will grow and overtime become a midsized or large organization, so by starting an improvement program at an early stage the funding overall should be minimized. This becomes more visible when the organization has grown large. This master thesis presents the idea of implementing a software process improvement program, or at least parts of it, by evaluating the software project. By evaluating a project the specific needs that are most critical are implemented in the next project. This process is iterated for each concluded project. The master thesis introduces the Iterating Evaluation Model based on an interview survey. This model is compared to an already existing model, the Experience Factory.
Place, publisher, year, edition, pages
2002. , 46 p.
Process Improvement, CMM, Evaluation, Software Project Process, Experience Factory
IdentifiersURN: urn:nbn:se:bth-2935Local ID: oai:bth.se:arkivex94531E5BD0D74122C1256C7E00546655OAI: oai:DiVA.org:bth-2935DiVA: diva2:830230