Planned maintenance
A system upgrade is planned for 10/12-2024, at 12:00-13:00. During this time DiVA will be unavailable.
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Evaluation of Software Projects: A Recommendation for Implementation The Iterating Evaluation Model
Blekinge Institute of Technology, Department of Software Engineering and Computer Science.
2002 (English)Independent thesis Advanced level (degree of Master (One Year))Student thesis
Abstract [en]

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. , p. 46
Keywords [en]
Process Improvement, CMM, Evaluation, Software Project Process, Experience Factory
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-2935Local ID: oai:bth.se:arkivex94531E5BD0D74122C1256C7E00546655OAI: oai:DiVA.org:bth-2935DiVA, id: diva2:830230
Uppsok
Technology
Supervisors
Available from: 2015-04-22 Created: 2002-11-27 Last updated: 2018-01-11Bibliographically approved

Open Access in DiVA

fulltext(782 kB)120 downloads
File information
File name FULLTEXT01.pdfFile size 782 kBChecksum SHA-512
ef7bb59f6db72d4f9515d6ce72ba4c13ec0da26dcdd11f91072bc61fd676a07fb12b9aa26cb16b7a7a821616bd6ce76c0b113b1d92c5c3625b311f3c5e64b43f
Type fulltextMimetype application/pdf

By organisation
Department of Software Engineering and Computer Science
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 120 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 163 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf