Rework Requirement Changes in Software Maintenance

Chua, B

Rework Requirement Changes in Software Maintenance

Chua, B

Permalink

Publisher:: IEEE
Publication Type:: Conference Proceeding
Citation:: The Fifth IEEE International Conference on Software Engineering Advances, 2010, pp. 252 - 258
Issue Date:: 2010-01

Closed Access

	Filename	Description	Size
	2010001466OK.pdf		349.57 kB	Adobe PDF	View/Open

Copyright Clearance Process

Recently Added
In Progress
Closed Access

This item is closed access and not available.

Full metadata record

Field	Value	Language
dc.contributor.author	Chua, B	en_US
dc.contributor.editor	Dujmovic, PDJ	en_US
dc.date	2010-08-22	en_US
dc.date.issued	2010-01	en_US
dc.identifier.citation	The Fifth IEEE International Conference on Software Engineering Advances, 2010, pp. 252 - 258	en_US
dc.identifier.isbn	9780769541440	en_US
dc.identifier.uri	http://hdl.handle.net/10453/16117
dc.description.abstract	The rework cost of a requirement change is high. Requirements changes, which relate to hidden catastrophic failures, can cost many thousands of dollars to fix. An exploratory study on software maintenance records demonstrates that specific change characteristics in corrective change and functional change are shown to have an effect on rework. In pursuing a deep understanding of the effects, we found that unexpected errors and poor understanding of errors trigger higher rework effort.	en_US
dc.publisher	IEEE	en_US
dc.relation.ispartof	The Fifth IEEE International Conference on Software Engineering Advances	en_US
dc.relation.ispartof	International Conference on Software Engineering Advances	en_US
dc.relation.isbasedon	10.1109/ICSEA.2010.45	en_US
dc.rights	© 2010 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.	en_US
dc.title	Rework Requirement Changes in Software Maintenance	en_US
dc.type	Conference Proceeding
utslib.location	Piscataway, USA	en_US
utslib.location.activity	Nice, France	en_US
utslib.for	0803 Computer Software	en_US
dc.location.activity	Nice, France	en_US
dc.location.activity	ISI:000233292100007
pubs.embargo.period	Not known	en_US
pubs.organisational-group	/University of Technology Sydney
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology
pubs.organisational-group	/University of Technology Sydney/Strength - HCTD - Human Centred Technology Design
pubs.organisational-group	/University of Technology Sydney/Students
utslib.copyright.status	closed_access
pubs.consider-herdc	true	en_US
pubs.place-of-publication	Piscataway, USA	en_US
pubs.start-date	2010-08-22	en_US

Abstract:

The rework cost of a requirement change is high. Requirements changes, which relate to hidden catastrophic failures, can cost many thousands of dollars to fix. An exploratory study on software maintenance records demonstrates that specific change characteristics in corrective change and functional change are shown to have an effect on rework. In pursuing a deep understanding of the effects, we found that unexpected errors and poor understanding of errors trigger higher rework effort.

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

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