Software processes and methodologies

¶ … 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, 2003) Thus, the managerial, people-related failure of a cramped schedule creates a failure on the software staff to meet specific and reasonable technical requirements of the customer. A lack of clear and testable managerial requirements can also lead to interpersonal conflicts amongst software staff regarding product methodology of design, creating an overly confusing architecture. Conversely, systems may be overly simplified to accommodate a tight schedule, resulting in a susceptibility to viruses and worms. (Chin, 2003)