Testing and Acceptance Criteria

All programming work goes through a three-tier testing process. First, a software QA test of each new or modified program unit is performed by a PIMS developer other than the author. These tests are based on unit test plans that are documented for use on future releases. When all enhancements for a given release are completed, system integration testing is performed to exercise interfaces between all programs and to verify the integrity of overall database designs. Finally, user testing based on predefined functional test plans is completed to ensure functional and regressional integrity. Before any version is released to production, it is installed on a separate Tandem test pathway (i.e., a nonproduction mirrored system partition) for verification in a realistic environment. Metrics on testing are collected throughout the system and user testing tasks. Bug-detection rates help determine testing progression and provide insight into how clean the releases are (Exhibit 3).

Exhibit 3. System Test Metrics (Cumulative Test Hours versus Bugs

Reported and Fixed)

Exhibit 3. System Test Metrics (Cumulative Test Hours versus Bugs

Reported and Fixed)

Key:

♦ Cumulative hours B- Cumulative major/medium bugs

-0--Cumulative bugs -□- Cumulative major/medium fixed

--A--Cumulative fixed

Key:

♦ Cumulative hours B- Cumulative major/medium bugs

-0--Cumulative bugs -□- Cumulative major/medium fixed

--A--Cumulative fixed

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment