Show simple item record

dc.contributor.authorHussain, Wen_NZ
dc.contributor.authorZowghi, Den_NZ
dc.contributor.authorClear, Ten_NZ
dc.contributor.authorMacDonell, SGen_NZ
dc.contributor.authorBlincoe, Ken_NZ
dc.date.accessioned2017-03-17T03:08:03Z
dc.date.available2017-03-17T03:08:03Z
dc.date.copyright2016-09-12en_NZ
dc.identifier.citation2016 IEEE 24th International Requirements Engineering Conference (RE), Beijing, 2016, pp. 126-135. doi: 10.1109/RE.2016.64
dc.identifier.urihttp://hdl.handle.net/10292/10383
dc.description.abstractSoftware has always been considered as malleable. Changes to software requirements are inevitable during the development process. Despite many software engineering advances over several decades, requirements changes are a source of project risk, particularly when businesses and technologies are evolving rapidly. Although effectively managing requirements changes is a critical aspect of software engineering, conceptions of requirements change in the literature and approaches to their management in practice still seem rudimentary. The overall goal of this study is to better understand the process of requirements change management. We present findings from an exploratory case study of requirements change management in a globally distributed setting. In this context we noted a contrast with the traditional models of requirements change. In theory, change control policies and formal processes are considered as a natural strategy to deal with requirements changes. Yet we observed that "informal requirements changes" (InfRc) were pervasive and unavoidable. Our results reveal an equally 'natural' informal change management process that is required to handle InfRc in parallel. We present a novel model of requirements change which, we argue, better represents the phenomenon and more realistically incorporates both the informal and formal types of change.
dc.publisherIEEEen_NZ
dc.relation.urihttp://ieeexplore.ieee.org/abstract/document/7765518/
dc.rightsCopyright © 2016 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.
dc.subjectInformal requirements change; Scope creep; Requirements management; Requirements change management
dc.titleManaging Requirements Change the Informal Way! When Saying 'No' Is Not an Optionen_NZ
dc.typeConference Contribution
dc.rights.accessrightsOpenAccessen_NZ
dc.identifier.doi10.1109/RE.2016.64en_NZ
aut.relation.endpage135
aut.relation.startpage126
pubs.elements-id217631
aut.relation.conferenceIEEE 24th International Requirements Engineering Conference (RE'16)en_NZ


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record