In short: A software quality plan describes how a software is to be tested in a planned manner. Typically, the software quality plan is prepared after a user requirements specification has been created and a risk analysis has been carried out for the corresponding software. It checks that the created risk-based user requirements are implemented in the software.
These are the guiding questions when creating a software quality plan:
A software quality plan and a software quality report are written by one person who is only involved in writing the plan or report. Another person will carry out the tests. These two functions must be kept separate. A software quality plan does not only assume that the tests can be positive (“software works as desired“). A possible negative outcome (“software does not work as desired“) must also be considered in the plan.
Caution: The software quality plan is not based on assumptions. Instead, it defines acceptance criteria that will determine whether the software passes or fails the test phase.
The following is an example of what a software quality plan might look like:
The software quality plan begins by describing the objective and purpose of the document. The scope of validation is then defined, i.e. the technical system to which the software quality plan applies.
Example: This software quality plan applies to software A123 with interfaces XYZZ1 at site ABC. Ist purpose is to establish the validation status for the software.
It also briefly describes the responsibilities of the validation team and the achievable dates for the different phases.
|Team for the Preparation of the Software Quality Plan
|Timing/Date: February 20xy
Figure 1 Team Software Quality Plan
|Team for the Software Tests
|Timing/Date: March 20xy
|Tester 1 (carries out the tests)
|Tester 2 (witnesses the tests according to the 4-eyes principle)
|Team Leader Operational Staff
Figure 2 Software Testing Team
|Software Quality Report Team
|Timing/Date: April 20xy
Figure 3 Team Software Quality Report
The tabular form is clear and easy to understand.
Persons involved in software quality testing must be trained for the software quality plan. This must be documented by a training certificate.
The software quality plan shall include a brief description of the following aspects:
Figure 4 Software/Computer System Description
The article is an excerpt from the German knowledge portal for equipment and systems qualification GMP:KnowHow Anlagenqualifizierung.
The GMP Compliance Adviser is the most comprehensive GMP online knowledge portal worldwide, combining theory and practice in a successful way.
It is used by more than 10,000 professionals in over 50 countries.
GMP in Practice: "How-to-do"-interpretations and knowledge of our noted industry specialists and according to international GMP regulations.
GMP Regulations: The most important GMP regulations from Europe, USA, Japan and many more (e.g. PIC/S, ICH, WHO,...).
Updates: All regulatory changes are covered, minor or big. With a high frequency update rate of 6x a year, you are always up to date.