Requirements change: What's the alternative?

Davis, AM; Nurmuliani, N; Park, S; Zowghi, D

Requirements change: What's the alternative?

Davis, AM Nurmuliani, N Park, S Zowghi, D

Permalink

Publication Type:: Conference Proceeding
Citation:: Proceedings - International Computer Software and Applications Conference, 2008, pp. 635 - 638
Issue Date:: 2008-09-23

Open Access

Copyright Clearance Process

Recently Added
In Progress
Open Access

This item is open access.

Adobe PDF

Download full textAdobe PDF (330.55 kB)

View on publisher's site

View statistics

Full metadata record

Field	Value	Language
dc.contributor.author	Davis, AM	en_US
dc.contributor.author	Nurmuliani, N	en_US
dc.contributor.author	Park, S	en_US
dc.contributor.author	Zowghi, D https://orcid.org/0000-0002-6051-0155	en_US
dc.date.issued	2008-09-23	en_US
dc.identifier.citation	Proceedings - International Computer Software and Applications Conference, 2008, pp. 635 - 638	en_US
dc.identifier.isbn	9780769532622	en_US
dc.identifier.issn	0730-3157	en_US
dc.identifier.uri	http://hdl.handle.net/10453/10742
dc.description.abstract	Numerous studies have shown that a software project's cost, schedule and defect density escalate as the rate of requirements change increases. Yet none of these studies have explored the effects of not making requirements changes in response to changes in user needs. This paper explains why a project incurs just as much, if not more, risk when requirements changes are suppressed. © 2008 IEEE.	en_US
dc.relation.ispartof	Proceedings - International Computer Software and Applications Conference	en_US
dc.relation.isbasedon	10.1109/COMPSAC.2008.216	en_US
dc.title	Requirements change: What's the alternative?	en_US
dc.type	Conference Proceeding
utslib.for	0803 Computer Software	en_US
utslib.for	080309 Software Engineering	en_US
dc.location.activity	Turku, Finland	en_US
pubs.embargo.period	Not known	en_US
pubs.organisational-group	/University of Technology Sydney
pubs.organisational-group	/University of Technology Sydney/DVC (Research)
pubs.organisational-group	/University of Technology Sydney/DVC (Research)/Graduate Research School
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology/School of Systems, Management and Leadership
pubs.organisational-group	/University of Technology Sydney/Strength - HCTD - Human Centred Technology Design
pubs.organisational-group	/University of Technology Sydney/Strength - STEM Education Futures
utslib.copyright.status	open_access
pubs.publication-status	Published	en_US

Abstract:

Numerous studies have shown that a software project's cost, schedule and defect density escalate as the rate of requirements change increases. Yet none of these studies have explored the effects of not making requirements changes in response to changes in user needs. This paper explains why a project incurs just as much, if not more, risk when requirements changes are suppressed. © 2008 IEEE.

Please use this identifier to cite or link to this item:

http://hdl.handle.net/10453/10742