Testing Early in the Life Cycle
Reviewing Requirements and Design Adequacy

21 Ways to Test that Business Requirements Are Accurate and Complete
15 Ways to Test that System Designs Are Accurate and Complete


2 Day Intensive Seminar Workshop


Most developers do not know how to test that requirements and design are accurate and complete. At best, they use one or two weak methods which are insufficient to help prevent costly rework and up to two-thirds of the errors which traditionally plague finished systems. This unique seminar workshop shows numerous ways to test up-front, where payoffs are greatest. Applying the techniques successively to a real case, participants discover that each technique reveals additional, otherwise-overlooked defects. Participants realize how this testing also improves meaningful customer involvement and communication.


Participants will learn:


  * More than 21 ways to test business requirements and 15 ways to test designs.
  * Finding previously overlooked problems when they are easiest and least expensive to fix.
  * Evaluating the levels of quality embodied within the requirements and design.
  * Testing techniques that enhance customers' involvement and communication with management.
  * Preventing future difficulties related to producibility, maintainability, and usability.
  * 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 system requirements and/or system designs.


 

VALUE OF TESTING UP-FRONT

  • Error sources; economics of quality
  • Proactive Testing™ Life Cycle Model
  • Survey on improving requirements quality
  • Keys to effective testing
  • Why up-front testing usually is so weak
  • CAT-Scan Approach? secret to quality
 

TESTING REQUIREMENTS FORMATS

  • Hidden weaknesses of traditional methods
  • Adding strength to subjective evaluations
  • Making sure they are requirements
  • Assessing reviewability
  • Determining deliverability
  • Testing structural completeness and clarity
 

FINDING OVERLOOKED REQUIREMENTS

  • Identifying all the stakeholders
  • Detecting all three Quality Dimensions
  • Addressing relevant quality factors
  • Commonly overlooked sources
 

ASSURING ACCURACY/COMPLETENESS

  • Finding Engineered Deliverable Quality?
  • Checking importance and criticality
  • Ascertaining trade-off balances
  • Matching to independent definitions
  • Defining acceptance criteria
  • Working out implications in action
  • Simulation and prototyping
  • Standards, guidelines, and conventions
  • Independent/expert validation
 

TESTING PROJECT FINANCES

  • Feasibility vs. justification
  • Testing reliability of cost/benefit estimates
  • Assessing project financial viability
  • Relation to requirements/design adequacy
 

REVIEWING DESIGN SUITABILITY

  • Calculating internal design quality metrics
  • Structured English, Cause-Effect Graphing
  • Checklists/guidelines for judgments
  • Conformance to engineering standards
  • Web and O-O considerations
  • Enlisting meaningful customer cooperation
  • Evaluating designs competitively
 

ACTIVELY TESTING DESIGN ACCURACY

  • Tracing to requirements
  • Tracking data backwards and forwards
  • Walking through logic
  • Prototyping and simulation techniques
  • Exercising user/operations instructions
  • Challenging designs by test planning
  • Measuring the "proof of the pudding"
 

MANAGING THE TESTING PROCESS

  • Selectively allocating resources
  • Tracing to subsequent artifacts
  • Tying back to actual time/cost/problems
  • Managing changes
  • Measuring effectiveness meaningfully
  • Continuously improving the process



Seminars
Articles
Upcoming Events
About Go Pro
Contact Us