Quality Assurance Section for a Design Specification

has been configured. Tests are developed based on information from a requirements document.

1.2.3.5 Beta Test Phase
Beta Testing is the validation performed on the completed system in a controlled, production-like environment or in the actual production environment. The client generally performs it with or without the assistance of the independent test team after the completed software system has passed Integration and System testing. Tests are either taken from the System Test Phase portion of the Test Plan or developed from user scenarios of workflow processes.

1.2.3.6 Test Organization
All the validation activities described are organized into one comprehensive test plan. The Test Plan describes the scope, strategy, assumptions and constraints, test tools, and test environment. It describes all test phases and the test cases for each of those phases.

1.3 Project Quality Control
This section describes how the source code is managed, made into builds and releases, and prepared for validation.

1.3.1 Configuration Management
Configuration Management is the detailed recording and updating of information that describes an enterprise's computer systems and networks, including all hardware and software components. Typically it includes the versions and updates that have been applied to installed software packages and the locations and network addresses of hardware devices.

1.3.2 Software Build/Release
As the development task progresses, a build or release will be ready for creation and validation. This collection of units and modules may be a part of or the entire application, depending on how the work was organized. Once
created, the build or release is placed into the appropriate test environment.

1.3.2.1 Build Identification
Each build is uniquely identified using a project-specific convention for each build in a software release. All problems documented include the build identifier.

1.3.2.2 Build Instructions
The technical lead or designee follows a series of steps to create a build or release. These steps, or build instructions, include gathering the proper source code, database tables, and files from the configuration management tool comprising the application and placing them in test or production environment.

1.3.2.3 Release Notes
When each build or release is created, a set of release notes documenting the changes made to the source is also created. They may include a description of new functionality added to the application, as well as a list of defects corrected in the release.

1.3.3 Issue Tracking
Issue Tracking is the detailed recording, tracking, and managing of defects, action items, and enhancements discovered in work products during the project's verification and validation efforts.

The paragraph included for each subsection is more of a description than the actual text used in a document. Use it to develop the right general concept description for your company. Then create a second paragraph for your project-specific activities. I believe this outline will also work for project plans and requirement documents as well as design specifications. It may not work as well for proposals where the main goal is to sell your company and your solution. But it will give you a starting point even for a proposal. So, the next time you are asked to "write up a few points on QA," you'll be ahead of the game.

Pages

About the author

Ms. Margaret Harris is a Senior Computer Scientist with Computer Sciences Corporation. Ms. Harris has fifteen years of professional software engineering experience, including Integration and System Testing, Quality Assurance, Process Development, Project Management, Requirement Analysis, GUI design, and Software Development in both client-server and Web environments.