dc.contributor.advisor | Abrahamsson, Pekka | |
dc.contributor.author | Fashina, Alfred | |
dc.date.accessioned | 2021-05-17T08:15:25Z | |
dc.date.available | 2021-05-17T08:15:25Z | |
dc.date.issued | 2021 | |
dc.identifier.uri | https://jyx.jyu.fi/handle/123456789/75671 | |
dc.description.abstract | 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. | en |
dc.format.extent | 59 | |
dc.format.mimetype | application/pdf | |
dc.language.iso | en | |
dc.subject.other | software cost estimation | |
dc.subject.other | top-down method | |
dc.subject.other | bottom-up method | |
dc.subject.other | incomplete requirements | |
dc.subject.other | cost overrun | |
dc.subject.other | unexpected events | |
dc.title | Challenges in software project cost estimation : a comparative case study | |
dc.identifier.urn | URN:NBN:fi:jyu-202105172945 | |
dc.type.ontasot | Pro gradu -tutkielma | fi |
dc.type.ontasot | Master’s thesis | en |
dc.contributor.tiedekunta | Informaatioteknologian tiedekunta | fi |
dc.contributor.tiedekunta | Faculty of Information Technology | en |
dc.contributor.laitos | Informaatioteknologia | fi |
dc.contributor.laitos | Information Technology | en |
dc.contributor.yliopisto | Jyväskylän yliopisto | fi |
dc.contributor.yliopisto | University of Jyväskylä | en |
dc.contributor.oppiaine | Tietojärjestelmätiede | fi |
dc.contributor.oppiaine | Information Systems Science | en |
dc.rights.copyright | Julkaisu on tekijänoikeussäännösten alainen. Teosta voi lukea ja tulostaa henkilökohtaista käyttöä varten. Käyttö kaupallisiin tarkoituksiin on kielletty. | fi |
dc.rights.copyright | This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited. | en |
dc.type.publication | masterThesis | |
dc.contributor.oppiainekoodi | 601 | |
dc.subject.yso | ohjelmistokehitys | |
dc.subject.yso | projektit | |
dc.subject.yso | estimointi | |
dc.subject.yso | kustannusarviot | |
dc.subject.yso | projektinhallinta | |
dc.subject.yso | software development | |
dc.subject.yso | projects | |
dc.subject.yso | estimating | |
dc.subject.yso | cost estimates | |
dc.subject.yso | project management | |
dc.format.content | fulltext | |
dc.type.okm | G2 | |