Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • 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
Prioritization of Stakeholder Needs in Software Engineering: Understanding and Evaluation
Responsible organisation
2004 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

In everyday life, humans confront situations where different decisions have to be made. Such decisions can be non-trivial even though they often are relatively simple, such as which bus to take or which flavor of a soft drink to buy. When facing decisions of more complex nature, and when more is at stake, they tend to get much harder. It is often possible to deal with such decisions by prioritizing different alternatives to find the most suitable one. In software engineering, decision-makers are often confronted with situations where complex decisions have to be made, and where the concept of prioritization can be utilized. Traditionally in software engineering, discussions about prioritization have focused on the software product. However, when defining or improving software processes, complex decisions also have to be made. In fact, software products and software processes have many characteristics in common which invite thoughts about using prioritization when developing and evolving software processes as well. The results presented in this thesis indicate that it is possible to share results and knowledge regarding prioritization between the two areas. In this thesis, the area of prioritization of software products is investigated in detail and a number of studies where prioritizations are performed in both process and product settings are presented. It is shown that it is possible to use prioritization techniques commonly used in product development also when prioritizing improvement issues in a software company. It is also shown that priorities between stakeholders of a software process sometimes differ, just as they do when developing software products. The thesis also presents an experiment where different prioritization techniques are evaluated with regard to ease of use, time consumption, and accuracy. Finally, an investigation of the suitability of students as subjects when evaluating prioritization techniques is presented.

Place, publisher, year, edition, pages
Karlskrona: Blekinge Institute of Technology , 2004. , 172 p.
Series
Blekinge Institute of Technology Licentiate Dissertation Series, ISSN 1650-2140 ; 12
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-00265Local ID: oai:bth.se:forskinfo0C0A10B9EBB6019EC1256FEF00556599ISBN: 91-7295-052-8 (print)OAI: oai:DiVA.org:bth-00265DiVA: diva2:838405
Available from: 2012-09-18 Created: 2005-04-26 Last updated: 2015-06-30Bibliographically approved

Open Access in DiVA

fulltext(1218 kB)140 downloads
File information
File name FULLTEXT01.pdfFile size 1218 kBChecksum SHA-512
5e17517f8c951a4ca2ad512afda8369837e87546172bbd71cb62578240cf463801e949371b8dcb412d309a8a39bfe50815a58e12a880880456f7f7f73370a223
Type fulltextMimetype application/pdf

Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 140 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

Total: 196 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • 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