By Topic

Simulating software development processes

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
G. A. Hansen ; CAPI, West Chester, OH, USA

One of the main factors affecting any product development schedule is rework. In the consumer product market, the risk of rework is often measured against the need to get to market quickly. This frequently happens in the software market as well; products are released with known bugs and then upgraded after user testing. Therefore, software development organizations may choose to limit the iterations of defect correction to meet schedules or control costs. The decision to release software after a certain point is a business decision, and there is little written about business decisions in any software-related literature, including the SEI's Capability Maturity Model. A quick review of software project management literature suggests that rework is implicit in software estimating techniques, but is not explicit. The amount of rework and the manner in which it is treated are very important factors in determining software schedules and cost

Published in:

Computer  (Volume:29 ,  Issue: 1 )