Software Processes Term Paper

Total Length: 344 words ( 1 double-spaced pages)

Total Sources: 1+

poor requirements for development software vs. The problems that occur from poor requirements management

A good manager will present his or her staff with clearly defined requirements, realistic schedules, ask for a product whose specifications can be subject to adequate testing, present his or her staff with reasonable but firm specifications, and have good communication skills. A poor manager will do just the opposite -- not only will he or she have poor interpersonal skills, but quite often a bad manager will present vague specifications for the developing software that workers cannot easily test, and simply demand too much, too quickly, on too tight a budget or a schedule of the staff.
(Davis, 2004)

Poor management can of course contribute to some of the different kinds of failures in requirements for development software. For example, a rushed schedule can result, on the part of the software developers, with key user requirements being dropped from the product. This can create a faulty, bug-ridden, and confusing system for the customer's employees. (Chin,….....

     Open the full completed essay and source list


OR

     Order a one-of-a-kind custom essay on this topic


sample essay writing service

Cite This Resource:

Latest APA Format (6th edition)

Copy Reference
"Software Processes" (2005, January 13) Retrieved June 15, 2026, from
https://www.aceyourpaper.com/essays/software-processes-60991

Latest MLA Format (8th edition)

Copy Reference
"Software Processes" 13 January 2005. Web.15 June. 2026. <
https://www.aceyourpaper.com/essays/software-processes-60991>

Latest Chicago Format (16th edition)

Copy Reference
"Software Processes", 13 January 2005, Accessed.15 June. 2026,
https://www.aceyourpaper.com/essays/software-processes-60991