Challenges in software project cost estimation a comparative case study

Estimating the cost, effort, and size to complete a software project is one of the most difficult and confusing tasks confronted by software project managers. Though, an early estimate is very crucial when bidding for contracts or determining whether the project viable, it’s accuracy cannot be guara...

Täydet tiedot

Bibliografiset tiedot
Päätekijä: Fashina, Alfred
Muut tekijät: Informaatioteknologian tiedekunta, Faculty of Information Technology, Informaatioteknologia, Information Technology, Jyväskylän yliopisto, University of Jyväskylä
Aineistotyyppi: Pro gradu
Kieli:eng
Julkaistu: 2021
Aiheet:
Linkit: https://jyx.jyu.fi/handle/123456789/75671
_version_ 1826225741915750400
author Fashina, Alfred
author2 Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_facet Fashina, Alfred Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä Fashina, Alfred Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_sort Fashina, Alfred
datasource_str_mv jyx
description Estimating the cost, effort, and size to complete a software project is one of the most difficult and confusing tasks confronted by software project managers. Though, an early estimate is very crucial when bidding for contracts or determining whether the project viable, it’s accuracy cannot be guaranteed because of factors like incomplete requirements, inadequate information from past projects and the experience of the estimator. Accurate software cost estimate can help the developer make more logical decisions in planning, scheduling, allocating resource, and monitoring the project progress. Considering all the estimation models developed by various researchers, it is inevitable to say that there has not been a perfect estimation method that solves all estimation problem. The first part of this thesis provides a general overview of software estimation and some models, which are classified as algorithm and non-algorithm models. The second part is a comparative case study research, which emphasizes on two non-algorithm model, Top-down and Bottom-Up method in comparison with the estimate gotten from a software development project. The main result of this study is that it is almost impossible to evaluate an accurate and error-free estimate at the beginning of a software project. Combining two or more estimation models at the beginning of the project and enhancing the estimate as the project progresses could give the better estimate, but other factors like risk assessment, resetting expectation, unexpected unknowns and exploring the use of automation should also be considered.
first_indexed 2021-05-17T13:40:46Z
format Pro gradu
free_online_boolean 1
fullrecord [{"key": "dc.contributor.advisor", "value": "Abrahamsson, Pekka", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Fashina, Alfred", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2021-05-17T08:15:25Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2021-05-17T08:15:25Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2021", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/75671", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Estimating the cost, effort, and size to complete a software project is one of the most difficult and confusing tasks confronted by software project managers. Though, an early estimate is very crucial when bidding for contracts or determining whether the project viable, it\u2019s accuracy cannot be guaranteed because of factors like incomplete requirements, inadequate information from past projects and the experience of the estimator.\nAccurate software cost estimate can help the developer make more logical decisions in planning, scheduling, allocating resource, and monitoring the project progress. Considering all the estimation models developed by various researchers, it is inevitable to say that there has not been a perfect estimation method that solves all estimation problem. \nThe first part of this thesis provides a general overview of software estimation and some models, which are classified as algorithm and non-algorithm models. The second part is a comparative case study research, which emphasizes on two non-algorithm model, Top-down and Bottom-Up method in comparison with the estimate gotten from a software development project.\nThe main result of this study is that it is almost impossible to evaluate an accurate and error-free estimate at the beginning of a software project. Combining two or more estimation models at the beginning of the project and enhancing the estimate as the project progresses could give the better estimate, but other factors like risk assessment, resetting expectation, unexpected unknowns and exploring the use of automation should also be considered.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2021-05-17T08:15:25Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2021-05-17T08:15:25Z (GMT). No. of bitstreams: 0\n Previous issue date: 2021", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "59", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.format.mimetype", "value": "application/pdf", "language": null, "element": "format", "qualifier": "mimetype", "schema": "dc"}, {"key": "dc.language.iso", "value": "eng", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "software cost estimation", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "top-down method", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "bottom-up method", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "incomplete requirements", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "cost overrun", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "unexpected events", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Challenges in software project cost estimation : a comparative case study", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "master thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202105172945", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "yvv.contractresearch.funding", "value": "0", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_bdcc", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "openAccess", "language": null, "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "masterThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.subject.oppiainekoodi", "value": "601", "language": "", "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ohjelmistokehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "projektit", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "estimointi", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "kustannusarviot", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "projektinhallinta", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "software development", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "projects", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "estimating", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "cost estimates", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "project management", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.format.content", "value": "fulltext", "language": null, "element": "format", "qualifier": "content", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}, {"key": "dc.type.okm", "value": "G2", "language": null, "element": "type", "qualifier": "okm", "schema": "dc"}]
id jyx.123456789_75671
language eng
last_indexed 2025-02-18T10:55:48Z
main_date 2021-01-01T00:00:00Z
main_date_str 2021
online_boolean 1
online_urls_str_mv {"url":"https:\/\/jyx.jyu.fi\/bitstreams\/3995b472-d8a9-44cc-8bbd-a6779b36a719\/download","text":"URN:NBN:fi:jyu-202105172945.pdf","source":"jyx","mediaType":"application\/pdf"}
publishDate 2021
record_format qdc
source_str_mv jyx
spellingShingle Fashina, Alfred Challenges in software project cost estimation : a comparative case study software cost estimation top-down method bottom-up method incomplete requirements cost overrun unexpected events Tietojärjestelmätiede Information Systems Science 601 ohjelmistokehitys projektit estimointi kustannusarviot projektinhallinta software development projects estimating cost estimates project management
title Challenges in software project cost estimation : a comparative case study
title_full Challenges in software project cost estimation : a comparative case study
title_fullStr Challenges in software project cost estimation : a comparative case study Challenges in software project cost estimation : a comparative case study
title_full_unstemmed Challenges in software project cost estimation : a comparative case study Challenges in software project cost estimation : a comparative case study
title_short Challenges in software project cost estimation
title_sort challenges in software project cost estimation a comparative case study
title_sub a comparative case study
title_txtP Challenges in software project cost estimation : a comparative case study
topic software cost estimation top-down method bottom-up method incomplete requirements cost overrun unexpected events Tietojärjestelmätiede Information Systems Science 601 ohjelmistokehitys projektit estimointi kustannusarviot projektinhallinta software development projects estimating cost estimates project management
topic_facet 601 Information Systems Science Tietojärjestelmätiede bottom-up method cost estimates cost overrun estimating estimointi incomplete requirements kustannusarviot ohjelmistokehitys project management projects projektinhallinta projektit software cost estimation software development top-down method unexpected events
url https://jyx.jyu.fi/handle/123456789/75671 http://www.urn.fi/URN:NBN:fi:jyu-202105172945
work_keys_str_mv AT fashinaalfred challengesinsoftwareprojectcostestimationacomparativecasestudy