Professional Documents
Culture Documents
Document Approval
Document Control
Table of Contents
1 Introduction...................................................................................................................................4
1.1 Purpose.....................................................................................................................................4
1.2 Scope.........................................................................................................................................4
1.3 Definitions.................................................................................................................................4
1.4 Responsibility...........................................................................................................................4
1.5 References.................................................................................................................................5
2 Design Qualification Process.....................................................................................................6
2.1 Business Requirements Review...............................................................................................6
2.2 Functional Design Review.......................................................................................................6
2.3 Technical Design.......................................................................................................................7
2.4 Source Code Control................................................................................................................7
2.5 Coding Standards....................................................................................................................7
2.6 Code Reviews...........................................................................................................................7
2.7 Unit (Component) Testing.......................................................................................................7
2.8 Validation Change Control Process........................................................................................7
3 Design Qualification - Phase Entry/Exit......................................................................................8
3.1 Phase Entry..............................................................................................................................8
3.2 Phase Exit.................................................................................................................................8
4 Design Qualification Protocol - Preparation................................................................................9
4.1 Protocol Title............................................................................................................................9
4.2 Pre-approval.............................................................................................................................9
4.3 Introduction............................................................................................................................10
4.4 Regulatory Requirements......................................................................................................10
4.5 Methodologies........................................................................................................................10
4.6 Documents to be reviewed.....................................................................................................10
4.7 Acceptance Criteria...............................................................................................................10
5 Design Qualification Report........................................................................................................12
5.1 Report on the design evaluation process..............................................................................12
5.2 Summary and Conclusions....................................................................................................12
5.3 Protocol Results Acceptance..................................................................................................12
Title Design Qualification SOP
Version Status Date Page
1.0 Commercial in Confidence 16-Aug-2006 4 of 13
1 Introduction
1.1 Purpose
The Design Qualification process ensures that a computer system
requiring validation to is designed to meet the regulatory
requirements of the pharmaceuticals industry.
1.2 Scope
Department/Section: Client, IT and Validation groups.
This SOP will apply to the design of all computer systems that
require validation to meet pharmaceutical industry regulatory
requirements. For information on computer systems that require
validation see SOP SOP_0200 Validation Determination.
1.3 Definitions
Project Team the team formed by the business to implement a
new computer system. This team will typical comprise of: a project
manager, users, software engineers, IT support staff, trainers, and
IT quality assurance staff.
Client the business system owner is typically the line manager
responsible for the business process where the computer system
will be used.
Validation Group the group responsible for ensuring that
computer systems are implemented and maintained in a validated
state.
IT Group the group responsible for development, operation, and
maintenance of computer systems.
1.4 Responsibility
The overall responsibility to ensure that the DQ is carried out in
accordance with this SOP lies with the Business System Owner.
The Project Team are responsible for ensuring that they follow the
process described in this document is followed.
The Validation group is responsible for the production of the Design
Qualification Protocol document and Design Qualification Report.
Title Design Qualification SOP
Version Status Date Page
1.0 Commercial in Confidence 16-Aug-2006 5 of 13
1.5 References
Document ID Title
SOP_0102 Document Standards
SOP_0401 Code Review SOP
SOP_0402 Unit Testing SOP
SOP_0900 Validation Change Control SOP
Title Design Qualification SOP
Version Status Date Page
1.0 Commercial in Confidence 16-Aug-2006 6 of 13
Audit trails;
Backup and recovery;
Resilience and data integrity, and;
Disaster recovery.
4.2 Pre-approval
At the beginning of the DQ Protocol a pre-approval section is
required. This section will contain a table for signatures. The table
of signatures must provide for the following information to be
captured:
1. The department or function of the signatory;
2. The name of the signatory;
3. A space to record the signature, and;
4. A space to record the date of the signature.
The section must contain a statement informing the reviewer that
signing this document infers that they have read, understood and
agree with the contents of the protocol.
Normally this information is collected on the approval page of the
DQ Protocol.
Title Design Qualification SOP
Version Status Date Page
1.0 Commercial in Confidence 16-Aug-2006 10 of 13
4.3 Introduction
The introduction section of the DQ protocol must contain
subsections providing information on:
1. The objectives of the DQ protocol;
2. The scope of the DQ protocol stating the phase of the
implementation lifecycle the IQ protocol applies too;
3. A list of documents referenced in the DQ protocol;
4. A description of the system being designed which identifies
the intended use of the system.
4.5 Methodologies
This section of the DQ protocol must identify any Software
Development Lifecycle or development methodology to be used in
the design and development of the system. This section must
describe any issues identified with this methodology and the
controls that have been put in place to address these issues.
Examples:
o Unacceptable AC: The Technical Design Specification
will contain appropriate definitions of code modules.
Title Design Qualification SOP
Version Status Date Page
1.0 Commercial in Confidence 16-Aug-2006 11 of 13