Obsolete Software Requirements
Independent thesis Advanced level (degree of Master (Two Years))Student thesisAlternative title
Obsolete Software Requirements (Swedish)
Context. Requirements changes are unavoidable in any software project. Requirements change over time as software projects progress, and involved stakeholders (mainly customers) and developers gain better understanding of the final product. Additionally, time and budget constraints prevent implementing all candidate requirements and force project management to select a subset of requirements that are prioritized more important than the others so as to be implemented. As a result, some requirements become cancelled and deleted during the elicitation and specification phase while other requirements are considered not important during the prioritization phase. A common scenario in this situation is to leave the excluded requirements for being considered in the next release. The constant leaving of the excluded requirements for the next release may simply render them obsolete.
Place, publisher, year, edition, pages
2011. , 85 p.
requirement engineering, obsolete requirements, requirements management
Computer Science Software Engineering
IdentifiersURN: urn:nbn:se:bth-2148Local ID: oai:bth.se:arkivex07565786E77A4680C125797400817BE0OAI: oai:DiVA.org:bth-2148DiVA: diva2:829416
Gorschek, Prof. Tony