Quality Assurance Section for a Design Specification

[article]

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

Issue Tracking: The process used to document and manage changes to a set of software.

1.2 Project Quality Assurance
This section describes the quality assurance activities used in creating applications. These activities combine to prevent defects from being introduced into the software and to uncover defects in the software.

1.2.1 Verification and Validation Methodology
The V-model of Quality Assurance is the integration of development, test, and quality assurance techniques. These techniques verify the requirements and design of the application and validate the software created from the
requirements and design.

1.2.2 Verification Activities
All work products, from documents to code, undergo technical reviews both internally and with the client to ensure we can answer the question, "Are we building the right system?"

1.2.2.1 Technical Reviews of Documentation
A technical review is a quality assurance technique where a work product, like a requirements document, is reviewed and commented on by a group of team members to identify problems, conflicts, and omissions. Reviews can range from formal meetings to informal peer reviews.

1.2.2.2 Design Walkthroughs (before the client sees it and with the client)
A walkthrough is a quality assurance technique where a work product like the system design is presented to project members. Typically, the system architect or technical lead conducts the walkthrough, presenting the material to those responsible for implementing or validating it. This is usually done in a formal meeting, and all issues are tracked and managed.

1.2.2.3 Code Reviews
As software is implemented, project members perform technical reviews of the code. The goal is to find and remove defects before implementation.

1.2.2.4 Training
Project management assesses the team for any training needs in the development language, development processes, or tools used to create or test the application.

1.2.2.5 Standards and Conventions
To help create high quality code, a set of standards and conventions is established and followed. This practice is not meant to inhibit creativity, ownership, or flexibility. It is used to bring all development staff to the same level.

1.2.3 Validation Activities
There are a number of validation activities that can be used to answer the question; "Did we build the system right?" This section describes the activities that are more typically known as testing.

1.2.3.1 Unit Test Phase
Unit testing executes all logic paths and exercises all data variances, including error handling. The individual developer performs it after the unit has been initially created or after it has undergone extensive modification.

1.2.3.2 Module Test Phase
Module Testing encompasses a logical group of units and exercises the interfaces between the component units, including error handling. The individual developer also performs this type of testing after the functional module has been initially created or after it has undergone extensive modification.

1.2.3.3 Integration Test Phase
Integration Testing encompasses software functionality and exercises the interfaces between software modules, including error handling, and is performed on a software subsystem or completed software build. An independent test team performs it after a software build, comprised of new and modified modules, has been configured into a testable executable. Tests are developed based on information from a design specification and requirements document.

1.2.3.4 System Test Phase
System Testing encompasses all system functionality and verifies that the system requirements have been met. System testing is performed on a completed software system. An independent test team performs it after the completed software system

About the author

Margaret Harris's picture Margaret Harris

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.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Nov 09
Nov 09
Apr 13
May 03