A Simple SQA Plan

Key Points from the Narrative process is ad hoc a lot of code reuse usability is very important accuracy and interoperability are problems testing is not formal at all little or no unit testing of reused modules

Suggestions Schedule time for and set milestones for: FTRs Requirements Detailed Design Peer Reviews new code modules Unit Testing (black box) all code module Gather these procedures in an "SQA Guidelines" document When time and money permit, send off an interested person to FTR training

Suggested format for SQA Guidelines Items to be Reviewed Pass Fail Criteria Responsibilities Schedule of Tests and Reviews

SQA Guidelines I. Items to be Reviewed System Requirements formal technical review consisting of facilitator: in-house requirements guru from different group author : Sue scribe: Zack customer rep (or sample user if customer is not available)

System Design Software Design FTR similar to above FTR need to assign specific people Software Design FTR facilitator: in-house designer from another group author: Zack or The Other Bob scribe: Tim or John member: Tim or John

All Reused Code Modules All New Code Modules code walkthroughs black box testing All Reused Code Modules white box testing for automatic ordering module In the future, perhaps add User Interface Usability Testing

SQA Guidelines II. Pass Fail Criteria System Requirements completeness System Design need a checksheet which includes survey of users' environment Software Design need a checksheet

New Code Modules Reused Modules User Interface need coding guidelines for walkthroughs black box - simple black box testing Reused Modules black box - boundary value analysis User Interface meets all usability criteria described in SRS be sure to use different browsers

SQA Guidelines III. Responsibilities Need to fill in this table Task Person Expected Completion

SQA Guidelines IV. Schedule for Tests and Reviews SRS FTR - end of week 2 System Design FTR - end of week 3 Software Design FTR - end of week 4 Unit Testing - scheduled throughout coding

Summary concentrate effort on problem areas insure completion by requirements design new code insure completion by adding these tasks to the schedule as milestones, and assigning responsibility