AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 1 of 9

AQS 200 001

AQS DESIGN & DEVELOPMENT CONTROL PROCESS
Purpose
This procedure is intended to describe the design and development control process activities for the AQS-200 office information technology projects and programs

Scope:
All Quality, Integration & Executive Services (AQS)-200 system development projects and AQS-200 non-system development projects reported to the Aviation Safety (AVS) dashboard level.

Approval(s):
Approver: <signed by JoAnn Carroll> Manager, Information Technology Division

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 2 of 9

REVISION HISTORY Rev 0 1 Original Changed the process number from 010 to 009 Added Authorized Signature on File to the footer Updated process flow to match AQS standard Changed process to reflect reorganization Changed entire process scope Changed the process to meet the scope Updated the process flow Rewrote the entire process.
Implemented P-06-324

Description of Change

Effective Date 03/25/05 01/30/06

05/31/06

3 4 5 6

Revised process flow diagram per PAR P-06-439 Added reference to AQS 200-001 WI4, PMP Development & Maintenance Updated metrics to reflect input from the AQS-200 management team Referenced data collection form in Section 9.2, updated template to accommodate branding

10/27/06 2/5/07 5/31/07 3/10/08

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 3 of 9

PROCESS FLOW MAP

START PROJECT

3.0 Input Activities

2.0 Planning Activities

4.0 Output Activities

1.0 Control Activities

PMP & SDLC Phases

5.0 Review Activities

9.0 Project Documentation / Records 7.0 Validation Activities

6.0 Verification Activities

8.0 Change Control Activities

END PROJECT

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 4 of 9

1.0

Control Activities
1.1

AQS-200 offices that are involved in information technology design and development activities shall use the AQS-200 System Development Lifecycle (SDLC) Work Instruction (WI) developed to control automation project design and development activities, in conjunction with AQS-200 Program/Project Management Plan (PMP) Development and Maintenance Work Instruction (WI4). AQS-200 offices shall use control activities identified by phase and lifecycle type within the AQS-200 SDLC WI. Specific activities shall be designated in the PMP.
1.2.1

1.2

The AQS-200 manager responsible for the program must approve Lifecycle types not defined within the AQS-200 SDLC WI if determined necessary to accomplish the design and development of the product.

1.3

Modification to the design and development planning activities shall follow the AQS200 PMP Development and Maintenance Work Instruction (WI4).

Planning Activities
1.4

The responsible AQS-200 office shall manage, as directed by the AQS-200 PMP Development and Maintenance Work Instruction (WI4) and theAQS200 SDLC WI, both internal and external interfaces if applicable. Examples of project documents that may contain how these interfaces are to be managed by the project are: 1.4.1 1.4.2 1.4.3
1.4.4 1.4.5

Interface Control Documents Project Management Plan Communication Plan Design Specifications. Configuration Management Plan

1.5

Modification to the design and development planning activities shall follow the AQS200 PMP Development and Maintenance Work Instruction (WI4). These activities may be handled by the following methods defined in the SDLC: 1.5.1 1.5.2 1.5.3 Reviews Audits Meetings

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control 1.6

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 5 of 9

Control and modification of these activities may be found in the following types of project documentation: 1.6.1 1.6.2 1.6.3 Project Management Plan Test Plans Implementation Plan

1.7

To the extent planning is dependent upon the scope of the design effort, the AQS-200 office responsible for the project may use the AQS-200 SDLC WI and the specified criteria within Section 13 of the SDLC to determine the scope of the effort.

Input Activities 3.1 The responsible AQS-200 office is expected to identify input activities in relation to the project. The inputs are to be defined in the project documentation as specified within the AQS-200 SDLC WI. These activities may encompass the entire project SDLC and shall be addressed within the documentation. The controlling document for project inputs is the program/project management plan created under the AQS-200 PMP Development and Maintenance Work Instruction (WI4). Types of documents used to identify inputs for a specified project are: 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 1.7.6 1.8 Project Scope Document Requirement Specifications Design Specifications Traceability Matrices Planning Documentation Testing Documentation

Project external and internal input requirements should address the functional, performance, regulatory and legal requirements for the project. Furthermore, the project input documentation should include past project specific design methodology if applicable or any requirements that were determined by both the business and information technology personnel involved in the project. The AQS-200 SDLC WI provides guidance to the AQS-200 office on the documentation and phases in which input requirements are addressed. Examples of project documentation that may contain this information are: 1.8.1 1.8.2 1.8.3 Statement of Work Project Management Plans Reviews

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 6 of 9

1.8.4 1.8.5 1.8.6 1.8.7 1.8.8 1.8.9

1.9

Concept of Operations Orders Policy Standards Requirements Specifications Design Specifications

Project related input activities shall be reviewed for adequacy as identified in the AQS200 SDLC WI. Examples of adequacy review activities for the project SDLC may include but are not limited: 1.9.1 1.9.2 1.9.3 1.9.4 Audit reports Meeting minutes Status reports Briefings

1.10

Project related requirements that are incomplete, ambiguous and conflicting are to be identified and resolved when possible. As the project moves thru the AQS-200 SDLC WI, methods of identifying and resolving issues can be located in the related project documentation. Examples of project documents that may provide methods to resolve the issues are: 1.10.1 1.10.2 1.10.3 1.10.4 1.10.5 1.10.6 Statement of Work Project Management Plans Implementation Plans Audit reports Meeting Minutes Operation Plans

Appropriate project personnel shall maintain record inputs as described in the AQS-200 SDLC WI. Output Activities
1.11

Project outputs related to the selected work pattern per the Project Management Plan shall be verified and approved before release of the product. As a project moves through the phases the outputs shall be verified and approved per the PMP. Approval criteria and methods can be located within project documentation. The AQS-200 SDLC WI can be used to provide information on the criteria and methods to be used. The controlling document for project output activities is the PMP developed under
UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 7 of 9

AQS-200 PMP Development and Maintenance Work Instruction (WI4). Examples of project documentation and activities that would contain the specified approval criteria and methods are: 1.11.1 1.11.2 1.11.3 1.11.4 1.11.5 1.11.6
1.12

Project Management Plan Configuration Management Plan Quality Assurance Plan Test Plans Reviews Contract documentation

Project outputs shall provide the ability of verification against development and design inputs. Appropriate verification information shall be available and provide for acceptance criteria. The information shall also contain the characteristics to ensure safe and proper use of the product delivered. Examples of documentation and activities that may contain the information are: 1.12.1 Requirements Specifications 1.12.2 Verification and Validation Plan 1.12.3 Traceability Matrices 1.12.4 Test Plans 1.12.5 Security Plan 1.12.6 Risk Assessments 1.12.7 Project oversight activities

Review Activities
1.13

The responsible AQS-200 office shall perform project review activities. These activities shall be planned and arranged for as specified in the program/project management plan created under the AQS-200 PMP Development and Maintenance Work Instruction (WI4). The review activities shall evaluate the results of the product design to meet requirements. The review activities shall identify problems and implement actions necessary to resolve those problems. Examples of documents and activities that can be used to identify and evaluate problems and reviews are: 1.13.1 1.13.2 1.13.3 1.13.4 1.13.5 Meetings Design Reviews Oversight Audits Project Management Plan Contract Reviews

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 8 of 9

1.13.6 Testing Activities 1.13.7 Change Request / Discrepancy Reports Appropriate project personnel shall maintain records including any necessary actions as described in the PMP. Verification Activities
1.14

The responsible AQS-200 office shall plan verification activities to ensure the product output meets the input requirements. The project shall maintain records of verification activities and associated follow-up of actions taken. These activities are specified in the AQS-200 SDLC WI and the work pattern selected by the project. The controlling document for verification activities is the program/project management plan created under the AQS-200 PMP Development and Maintenance Work Instruction (WI4). Examples of verification records and documents are: 1.14.1 Verification and Validation Document 1.14.2 Test Scripts/Cases 1.14.3 Change Request / Discrepancy Reports

Validation Activities
1.15

The responsible AQS-200 office shall plan validation activities to ensure the product can meet the project requirements to ensure its intended use. Wherever practicable validation activities shall be completed prior to the release or implementation of the product. The project shall maintain records of validation activities and associated follow-up of actions taken. Examples of validation records and documents are: 1.15.1 Verification and Validation Document 1.15.2 Test Scripts/Cases 1.15.3 Oversight/Audit Reports

Change Control Activities

1.16

The responsible AQS-200 office shall identify and document change control activities. Change control activities shall be reviewed, verified and validated as specified on the selected work pattern for the project. These changes shall include evaluation of the effect of changes to the delivered product if applicable. Examples of documents that can be used to identify how a project would handle this activity are:
UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use

AVS Quality Management System

Title: Design and Development Control

QPM # AQS-200-001

Revision
6

Effective Date: 03/10/08

Page 9 of 9

1.16.1 1.16.2 1.16.3 1.16.4

Project Management Plan Configuration Management Plan Statement of Work Acquisition Plan

Appropriate project personnel shall maintain records required to include necessary actions during product design and after release as described in the PMP. 2.0 Project documentation and records
2.1

Project documentation and records shall be maintained by the appropriate project personnel in an electronic centralized secured AQS-200 site that is accessible by appropriate project personnel. Information for the collection of metrics will be captured in conjunction with the Release Notification process, AQS-200-005, on form AQS200-005-F1. This form is located on the shared G drive, in subfolders under G:\AVS11\AVS11B\AVS11B Project Files\Z-AQS230-Release Notification.

2.2

Process Measure: Percentage of Releases issued on or before their scheduled due date. Product Conformity Measure: Percentage of tests (of software releases) successfully completed. Stakeholder Satisfactions Measure: Did the application/release pass the User Acceptance Test (UAT)?

UNCONTROLLED COPY WHEN DOWNLOADED Check The Master List To Verify That This Is The Correct Revision Before Use