Investment in QA activities will
Promote better, more testable, more implementable specifications
Reduce the cost of developing specifications
Increase the quality and interoperability of implementations
Reduce duplication of test-development effort
Even a small investment pays big dividends
We can't do your QA work for you
We don't have the resources nor the domain-specific expertise
We do provide guidelines and tools
We can help avoid duplication of effort
Use our templates, measure against our checkpoints
Tell us what else you need
Roadmap, primer, guide to the other documents
Planning, logistics, operation, and maintenance of WG quality processes
How to write clearer, more implementable, more testable specifications
Technologies, tools, methods for writing test materials
Scope - define the scope, identifying what needs to conform and how
Conformance Clause - specify the conformance policy and requirements
If you must subset - use profiles, modules, functional levels
Extensions - specify whether and how extensions are allowed
Tag for later use - identify testable assertions, discretionary items
Claims - specify how conformance claims and statements are made
Analyze the specification
Declare the structure of the test suite
Document the testing methodology
Provide test automation and results-reporting framework
Plan for test development & conformance testing
Get Started - appoint a QA lead
Integrate - commit to QA goals and scenario
Staff - assess and assign appropriate staffing
Coordinate - synchronize QA and specification deliverables
Plan - for for development, publication, maintenance
How? - use OpsGL's charter template and process template
What do you think of:
Our last-call documents?
Our tools and resources (Library, Matrix, Tools, ...)?
Other feedback?
What would you like us to do next?
Review your processes and specs?
Provide consulting services?
Document existing best practices?
Provide templates, tools, test harnesses?
Other suggestions?
What else?