defined requirements cause up to two-thirds of software errors, yet
few organizations know effective methods to assure requirements are
accurate and complete. At most, they use one or two weak methods and
don’t recognize the weakness. This interactive session introduces
21 methods with increasing power. Following the CAT-Scan Approach™,
participants apply the techniques successively to a real case and
discover how each different method reveals additional, otherwise-overlooked
defects when they are easiest and least expensive to fix. Participants
learn ways to find previously overlooked requirements, increase meaningful
customer/user involvement, enhance communications and understanding,
and truly test the adequacy of requirements definitions.
This course shows ways to test requirements after they have been collected.
It is not intended to teach how to collect requirements, although
the testing methods suggest collection methods which would be helpful.
Our companion course, Defining and Managing User Requirements, does
concentrate on teaching how to collect, analyze, and document requirements.
* 21 ways to test that business/user requirements
are accurate and complete.
* Finding previously overlooked problems when they
are easiest and least expensive to fix.
* Recognizing, communicating, and gaining committment
to the importance of adequate requirements.
* Evaluating the levels of quality embodied within
* Testing techniques that enhance customers' involvement
and communication with management.
* Allocating testing resources economically.
WHO SHOULD ATTEND: This course has been designed
for systems and business managers, project leaders, analysts, programmer
analysts, quality/testing professionals, and auditors responsible
for assuring the accuracy and completeness of business/customer