Rochester Chapter of the IEEE Computer Society

IEEE Computer Society Presents
Software Requirements: 10 Traps To Avoid

Date: Wed. Sept. 8, 1999

Time: 6:00-8:00 PM

Location:Microelectronic and Computer Engineering Building (bldg. 17) - Room 2150

at Rochester Institute of Technology (See RIT Campus Map)

Successful software projects are built on a foundation of well-understood requirements. However, many development organizations get caught in traps that prevent them from effectively collecting, documenting, or managing their requirements. This presentation describes ten typical requirements problems that can sabotage your project. Several symptoms that indicate you might be getting caught in each trap are described, along with suggestions for avoiding or escaping from the trap. The requirements traps discussed are:

confusion about what a requirement is

inadequate customer involvement

vague and ambiguous requirements

unprioritized requirements

building functionality no one uses

analysis paralysis

scope creep

inadequate requirements change process

insufficient change impact analysis

inadequate requirements version control

Karl Wiegers, PhD., author of Creating a Software Engineering Culture and Software Requirements: A Pragmatic Approach, is Principal Consultant for Process Impact , which focuses on practical software process improvement. Karl also is a frequent contributor to Software Development magazine.

Computer Society meetings are free and open to all. Refreshments will be served at 6:00 and the talk will begin at 6:30.

divider


If you would like to contact the Rochester Chapter of the IEEE Computer Society Webmaster, email to Webmaster. (Modified:17-Feb-2003)

IEEE Computer Society Presents Software Requirements: 10 Traps To Avoid

IEEE Computer Society Presents
Software Requirements: 10 Traps To Avoid