DocumentCode :
1081131
Title :
Strategies for managing requirements creep
Author :
Jones, Capers
Author_Institution :
Software Productivity Res. Inc., Burlington, MA, USA
Volume :
29
Issue :
6
fYear :
1996
fDate :
6/1/1996 12:00:00 AM
Firstpage :
92
Lastpage :
94
Abstract :
One of the most chronic problems in software development is the fact that application requirements are almost never stable and fixed. Frequent changes in requirements are not always caused by capricious clients (although sometimes they are). The root cause of requirements volatility is that many applications are attempting to automate domains that are only partly understood. As software design and development proceeds, the process of automation begins to expose these ill-defined situations. Therefore, although creeping requirements are troublesome, they are often a technical necessity. Several threads of research and some emerging technologies are aimed at either clarifying requirements earlier in development or minimizing the disruptive effect of changing requirements later
Keywords :
software development management; systems analysis; application requirements changes; automation; disruptive effect; ill-defined situations; management strategies; partly understood domains; requirements clarification; requirements creep; requirements volatility; software design; software development; Application software; Automotive engineering; Creep; Design automation; Embedded software; Hardware; Productivity; Programming; Software design; Yarn;
fLanguage :
English
Journal_Title :
Computer
Publisher :
ieee
ISSN :
0018-9162
Type :
jour
DOI :
10.1109/2.507640
Filename :
507640
Link To Document :
بازگشت