वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No.

13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
वै गु आ निदेनशका
सॉफ़्टवेयर के नलए
स्वतंत्र सत्यापि और नवनधमान्यकरण (भू उपस्कर)
AQA DIRECTIVE
ON
SOFTWARE INDEPENDENT VERIFICATION AND VALIDATION
(GROUND EQUIPMENT)

अंक-1, संशोधि-0, िवम्बर 2023

ISSUE – 1.0, REV -00, NOVEMBER 2023

वैमानिक गुणवत्ता आश्वासि महानिदेशालय

भारत सरकार, रक्षा मंत्रालय
'ए' ब्लॉक, सातवं मंनिल, रक्षा कायालय पनरसर
कस्तूरबा गँधी मागग , िई नदल्ली- 110001

DIRECTORATE GENERAL OF
AERONAUTICAL QUALITY ASSURANCE
GOVERNMENT OF INDIA, MINISTRY OF DEFENCE,

पृष्ठ संख्या Page 1 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023

PREFACE

DGAQA as regulatory authority for Quality Assurance and Final Acceptance of

military aviation stores during design, Development, Production, Manufacture/ Repair/
Overhaul/ up-gradation/ modification/ life extension etc. at various DPSUs/OFs/DRDO
Labs etc. have encountered number of issues related to software quality assurance &
validation.

2. All the systems are now software based as received and felt for having requisite
guidelines on Independent Verification and Validation of software which plays a
predominant role in the design and development of Airborne and related Ground
Equipment. A well-defined procedure for carrying out IV & V will enhance in achieving
defect free software in the equipment it resides and to avoid flight safety ramification.

3. Military aviation production agencies must produce and continually improve safe
and reliable stores that meet customer and regulatory requirements thereby assuring
customer satisfaction.

4. This AQA directive is issued for general guidance during Quality Assurance
activities of software residing in Test Rigs, Tools, Testers, Ground Equipment and
Simulators.

पृष्ठ संख्या Page 2 of 16

वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
LIST OF AMENDMENTS

Sl Amendment Date of
Brief of Amendments Authority
No No Amendment

पृष्ठ संख्या Page 3 of 16

वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Table of Contents

1. Introduction................................................................................................................... 6
2. Scope............................................................................................................................ 6
3. Objective....................................................................................................................... 6
4. Types of Software......................................................................................................... 6
5. Flow of activities in V&V and IV&V Process ................................................................. 7
6. Involvement of DGAQA and other stake holders in IV&V during SDLC Activities........ 8
7. Software Configuration Management ......................................................................... 11
8. Software certification/Clearance Methodology ...........................................................13
9. Software/Product/System Validation...........................................................................13
10. Software Approval Authority ..................................................................................... 14
11. Conclusion............................................................................................................... 15
12. References................................................................................................................ 15

पृष्ठ संख्या Page 4 of 16

वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Acronyms
ATP / R Acceptance Test Procedure / Report
CCB Configuration Control Board
CEMILAC Centre for Military Airworthiness and Certification
CFE Customer Furnished Equipment
COTS Commercial-off-the-shelf
CSCI Computer Software Configurable Item
Design, Development & Production of Military Air systems &
DDPMAS
airborne Stores
D&D Design and Development
DGAQA Directorate General of Aeronautical Quality Assurance
ENTEST Environmental Test
FDA Flight Data Analysis
FTI Flight Test Instrumentation
GOS Ground Operating System
GSQR General Staff Qualitative Requirements
GSS Ground Support System
HATS Hardware Acceptance Test Software
HLD High Level Design
HSI Hardware Software Integration
IV&V Independent Verification and Validation
JSQR Joint Services Qualitative Requirements
LLD Low Level Design
PFMG Pre Flight-Message Generator
PSQR Preliminary Services Qualitative Requirements
QT Qualification Tests
SCI Software Configuration Index
SCMP Software Configuration Management Plan
SCN Software Change Note
SCR Software Change Request
SDD Software Design Description/Document
SDLC Software Development Life Cycle
SDP Software Development Plan
SDS Software Design Standards
SECI Software Life Cycle Environment Configuration Index
SoFT Safety of Flight Tests
SQA Software Quality Assurance
SQAP Software Quality Assurance Plan
SQR Services Qualitative Requirements
SRD Software Requirement Data/Document
SRS Software Requirement Specification
STLC Software Test Life Cycle
STP Software Test Plan
STR Software Test Report
SVP Software Verification Plan
SVR Software Verification Results
SyRD System Requirement Data/Document
TAA Technical Airworthiness Authority
TTGE Test Rigs and Tools, Testers & Ground Equipment
V&V Verification and Validation
VDD Version Description Document

पृष्ठ संख्या Page 5 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
1. Introduction

Verification and Validation (V&V) is a system engineering discipline which helps design &
development organization to build quality into the system/software during the system/software
life cycle. Verification is concerned with checking that the system is well engineered and
Validation is concerned with checking that the system/software meets the user needs.
Independent Verification and Validation (IV&V) is the process of checking that a product,
service or system meets specifications and that it fulfills its intended purpose. IV&V services
must be provided, managed and financed by organizations that are technically, managerially
and financially independent of the design and development organization.
IV&V is a “Process” as well as “Product” oriented activity. It is viewed as performing a
“Technology Audit” by QA regulatory bodies with a focus on safety aspects.

2. Scope

This document gives an outline of IV&V processes and QA activities involved during the
Design and Development of Software/Firmware used in Ground equipment, Rigs, Simulators,
Ground Test equipment of Airborne Stores. This document shall be read in conjunction with
DDPMAS and in case of conflict the later shall take precedence.

3. Objective

This document provides an overview of IV&V activities and the associated role of DGAQA.
The document also briefs the role of DGAQA when the software is developed by following DO-
178C/ DO-278 standards. The primary objective of an IV&V activity is to provide an objective
assessment of products and processes throughout the project life cycle. In addition, IV&V will
facilitate early detection and correction of errors, enhance management insight into risks and
ensure compliance with project performance, schedule and budget requirements.

4. Types of Software

Airborne Embedded Software is customized/ specialized software meant to control the

airborne hardware to carry out specific assigned tasks, for example Mission Computer
Software, Air Data Computer Software, customized Operating System etc. Clearance of such
software including its SDLC documentation and ground system software which controls such
airborne equipment is given by CEMILAC on the basis of IV&V report examined & coordinated
by all stakeholders namely system experts, domain experts, testing experts including DGAQA
rep. (Chapter 21.C.6 of IMTAR-21 Version-2.0)

पृष्ठ संख्या Page 6 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Software Criticality

i. Critical Software: The software whose malfunctioning may affect safety, reliability,
maintainability, interchangeability and operational effectiveness is termed as critical software.
Example: HUMS software, Aircraft simulator software, IFF encryptor software loader, FADEC
etc.

ii. Non-Critical Software: The software which is not classified as critical and if it’s
malfunctioning will not affect the safety of the aircraft/crew or the execution of the mission then
such software is termed as non-critical software Example: Ground tester software, TTGE
software etc.

5. Flow of activities in V&V and IV&V Process

Figure below is a V- model of software development life cycle, which shows verification and
validation activities are part of every stage in the SDLC and STLC process.

SDLC / STLC V-Model

Difference between Verification and Validation

Verification Validation
Verification includes checking Validation includes testing and validating the
documents, design, codes and actual software product.
programs.
Verification is the static testing. Validation is the dynamic testing.
It does not include the execution of It includes the execution of the code.
the code.
Methods used in verification are Methods used in validation are Black Box
reviews, walkthroughs, inspections Testing, White Box Testing and non-functional
and desk-checking. testing.

पृष्ठ संख्या Page 7 of 16

वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
It can find the bugs in the early stage It can only find the bugs that could not be found
of the development. by the verification process.
V&V/ IV&V team does verification and Validation to be done by IV&V/ IV&V team in
DGAQA oversees the task coordination with DGAQA.
Verification comes before Validation. Validation to be carried out after the verification
of each SDLC phase.

6. Involvement of DGAQA and other stake holders in IV&V during SDLC Activities

Sl
SDLC Phase Activity Responsibility Remarks
#
System/User
Requirements
For example,
Document This document is submitted by
GSQR, ASQR,
(SyRD/URD) the User to the Main Contractor.
JSQR etc.
System or DO 178, IEEE 12207,
Approval of STP
1 User DSSD or any other Using SyRD Designer will
(ATP) is by
Requirements process acceptable to prepare SRD and SDP
CEMILAC/
RCMA/ CEMILAC documents and Test Team
DGAQA, as
(21.C6.1.7-b of IMAP) prepares ATP/STP document.
applicable

Software
Includes SQA This document is prepared by the
Quality Approved by
2 activities as per the Main contractor / D & D Agency
Assurance DGAQA.
provided template QC/QA team
Plan (SQAP)
This document is generated by
the designer team approved by
Changes in
CEMILAC Design Categorized
software
Includes under DOA (Design Organization
configuration
Configuration Approval) and approved by
shall be
identification, CEMILAC/DGAQA (as
controlled
Software Baselines and applicable).
through SCR and
Configuration traceability, Problem
3 SCN.
Management reporting, change
The VDD
Plan (SCMP) control, Change Main Contractor shall use
Document/SCM
review, Supplier configuration management
tool shall be
control, Archive, tools/applications to manage the
made available
retrieval, and release activities mentioned.
to DGAQA for
verification.
VDD is generated as part of
SCMP by design team.
Software
This document is generated by
Requirements
User Requirements the designer team and reviewed CEMILAC
Specification /
4 are technically by IV&V team approves this
Document
specified in detail. (SRS approval not required for document.
(SRS/SRD/V
COTS and legacy TTGEs)
DD)

पृष्ठ संख्या Page 8 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Sl
SDLC Phase Activity Responsibility Remarks
#
Check if the the
coding of Test
rigs/TTGEs
1) is done in line
with established
Code to be generated by design SRS to be
Code Walk- coding
5 team & reviewed by IV&V team approved by
through standards/practices
in coordination with DGAQA. CEMILAC
2) exactly meets
the specifications laid
down by SRS, SDD,
Interface control
documents etc.
SDD, HLD, LLD
Unit Testing, and testing
Unit Test cases,
Integration documents shall
Integration test cases
and I V&V team prepares and be made
6 and Functional Test
Functional approves this document available to
Cases are developed
Testing DGAQA while
by Test Team
documents witnessing the
tests.
Includes test
environment/test- DGAQA
setup, testing approves this
This document is generated by
method, traceability document, as
the IV&V team for configuration-
Software Test and coverage applicable.
controlled software with a
Plan (STP) analysis as
registered Checksum* and
(Also called applicable. DGAQA
7 Version.
Requirements compares the
Registered checksum should be
Based Testing Verifies that the registered
a part of the STP document and
(RBT)) delivered system checksum of the
is verified before starting the
meets User’s software with the
tests
requirement and generated
system is ready for checksum.
real world use.
Software Test Includes the executed
Report (STR) test cases and STR is generated by the IV&V
respective results. team
Software
8
Quality Prepared by QA team
DGAQA
Assurance to bring out SQAR is generated by main
approves this
Report compliance to the contractor QA team
document.
(SQAR) SQAP.

· Main Contractor shall constitute V&V team for non-critical software and IV&V team for critical
software for the verification and validation of the all types of software. Test Rig and Type-
C TTGE software. IV&V team shall consist of system experts, domain experts, testing
experts from relevant stake holder of D & D organizations (like Design groups of ADA, HAL,
BEL etc.), CEMILAC and DGAQA representatives.
पृष्ठ संख्या Page 9 of 16
 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
· IV&V team shall carry out IV&V planning, carry out independent reviews, analysis verification,
testing reporting activities and participate in Software review meetings, during the various
phases of Software life cycle.
· DGAQA ensures proper IV&V / V&V throughout the SDLC/STLC phases.
· V&V process at various stages of Software Development Life Cycle (SDLC) is carried out in
two-tier configuration - first by in-house V&V team (System experts & Domain experts of
main contractor) and then by IV&V team (System experts, Domain experts of main
contractor, IV&V rep, CEMILAC rep, DGAQA rep etc.) based on the criticality level of the
software.
· The criticality level of the test rig used for a subsystem of an Air System or an Airborne Store
shall be arrived at based on the criticality level of such subsystem/Airborne Store.
· An IV&V plan shall be made specific to the project after identifying the criticality of the
software.
· Designer V&V activities for any phase shall be completed before delivering the products for
IV&V activities. Designer V&V reports shall be provided to IV&V.
· The Test Rig/Simulator/TTGE software shall be developed and tested in accordance with an
established Software Development Life Cycle Process in coordination with DGAQA.
· Modified and incremental versions of the software shall also be reviewed based on regression
testing or change Impact Analysis as applicable by IV & V Team.
· Ensure that Development and Testing Tool Verification/Qualification, Compiler Validation,
Object Code Verification (OCV) are addressed.
· Software shall follow a systematic design, development, testing and certification based on its
criticality and the software should be under configuration control and should have a
checksum.
· Ensure complete dynamic real time testing of the software on a “Certified/Approved Test
Rig”.
· IV&V recommendations will form an essential input to CEMILAC and DGAQA for clearance
of software based on its criticality.
· DGAQA may delegate the Verification & Validation responsibility of software to IV&V/
approved inspector of SQA group of the Main Contractor depending on the criticality of
software under DGAQA-AFQMS approval.

* Checksum is like a digital finger print of a file or code. It’s a calculated value, made of
numbers and letters, and is used to verify the integrity of a file. The registered checksum of a
file or code generated originally is compared with the presently generated checksum before
using the software (code) for testing, to ensure the right version is being used.

पृष्ठ संख्या Page 10 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
7. Software Configuration Management

Main Contractor shall establish and implement a means by which the configuration of the
CSCI/Software artifacts (including documentation, source code, executable code, other
records etc.) is managed over the product life cycle to ensure its continued life support. The
Software which is uniquely identified (name, version and checksum) and archived through a
configuration control process only shall be cleared for integration on Test
Rigs/Simulators/TTGES or delivery to User Services. The configuration management includes
processes by which the configuration is identified, change is managed and configuration status
is accounted and disseminated to all stakeholders. Verification/Audit of configuration status is
conducted by DGAQA.

Software and its associated documents should be under configuration control preferably by
using tools to establish its integrity. If tools are used, version of source code and documents is
done automatically by the tool else the diagram below which is self-explanatory can be the
guidelines for version.

Problem Reporting and Change Tracking: All the problems/failures or changes encountered
during the development and testing phase should be documented, analyzed and resolved to
its closure by following the approved process mentioned in SCMP.
Any change to the source code of software shall be controlled through Software Change
Requests (SCRs) and Software Change Notes (SCNs). For the software bug/problem reported,
SCR will be initiated by the Design team and, if required, CCB may be convened. The SCR
approved by Main Contractor QA will be provided to DGAQA, for the approval of SCN, as
applicable.

पृष्ठ संख्या Page 11 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Artifacts under Software Configuration Management (SCM) Control

Artifacts under SCM

· The software planning process defines and coordinates the activities of the software
development and integral processes.

· The software development processes produce the software products/artifacts.

· The integral processes ensure the correctness, control and confidence of the software
life cycle processes and their outputs.

· These artifacts are as per RTCA DO-178C Standards and may vary depending on the
software standards followed.

Testing activities as per DO-178C Criticality Levels, A to D as shown in table below-

Testing Activities as per RTCA DO-178C Criticality
Levels A - D
Review High and Low
Criticality
·
Requirements
Level D
· Test High Level Requirements
· Same as Level D, Plus
Criticality · Test Low Level requirements
Level C · Statement Coverage
· Verify Data and Control Coupling
· Same as Level C, Plus
Criticality · Target Hardware / Platform
Level B Testing
· Decision Coverage
Same as Level B, Plus
Criticality
·
Modified Condition – Decision
Level A
·
Coverage

पृष्ठ संख्या Page 12 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023

8. Software certification/Clearance Methodology

The main contractor should submit the system/software life cycle artifacts/documents. The
artifacts involve both “Process” and “Product” documentation.

Process Documentation – Verification (Not limited to the following reports/documents)

· Planning Documents (e.g.: SQAP, SCMP, STP etc.) as detailed in Table 3
· Audit reports and Meeting Points, as applicable

Product Documentation – Validation (Not limited to the following reports/documents)

· Software development phase artifacts as detailed in Table 3
· Software testing phase artifacts as detailed in Table 3
o Unit Testing, Integration Testing and System Testing
· User Manuals
· Maintenance/Trouble shooting Manuals
· System/Software Admin manuals

DGAQA after ensuring the above Process and Product compliance requirements shall issue
the clearance certificate, as applicable.

9. Software/Product/System Validation

Software/Product/System validation is concerned with checking the user requirements with

the deliverable. This aspect can be established by tracing the customer requirements to the
test cases (forward traceability) and also by tracing the test cases to the customer requirements
(backward traceability) and record the same. All the test cases must “Pass” without any
unacceptable deviation. This should be addressed in STP/STR document and should be
concurred by DGAQA. Validation of the product i.e., delivery of “Right Product” to the User
is a very important activity of DGAQA.

The entire documentation starting with the Software Requirement, Specification, Software
Design, Software Functionality, Software Integration, Software Testing, Software Maintenance
etc., should be described in respective artifacts and should be formally reviewed before
submitting it for clearance to CEMILAC and DGAQA.

पृष्ठ संख्या Page 13 of 16

वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023

10. Software Approval Authority

The approval agency against each type of software are as shown below-

Sl. Types of Software Approved by

Clearance of Airborne Software: (21.C6.3.1-b of IMTR Ver 2.0)
Hardware Acceptance Test Software (HATS) Software: This resides
in the airborne equipment only during the Qualification/ Acceptance
1 tests to validate all hardware resources and works in tandem with CEMILAC
the test rig software. This software will be disabled / erased, as
applicable, before providing the LRU to User Services.

Clearance of Test Rig Software (for Airborne items)/ HSI Software/

Simulation Software (21.C6.3.2 (g) & 21.T2.5 of IMTR Ver 2.0) and CEMILAC
2
GCS software of UAVs

Approved
Type A and Type B
Designer QC.
(21.T2.9 of IMTR Ver 2.0)
(Acceptance
E.g., Licensed procurement of the shelf etc.
based on CoC)
Software residing
Type C
in TTGEs:
(21.C6.3.5 & 6 Maintenance and Pilot Crew
(21.T2.3 of IMTR
Training Software clearance by DGAQA)
3 Ver 2.0:
Indigenous design development of the software
Categorization of Designer QC/
for the ground system.
TTGEs) DGAQA
E.g., GOS(Secondary) and GSS, Mother Fill
Gun and Child Fill Gun for Cripto unit of IFF
etc. #

# Ground data loading and data retrieval

software (Only SRS Approval by CEMILAC) DGAQA

पृष्ठ संख्या Page 14 of 16

 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023
Flow chart on role of TAA during SDLC/STLC

USER/System/Certification Requirements

CEMILAC TAA DGAQA

Respective processes of IMTAR/DDPMAS to be followed

· Airborne Embedded Software. · Ground data loading and data retrieval

· Ground Based Software controlling airborne software
systems. · Calibration and Onboard Instrumentation
· Mission Planning and Analysis Software. · Pilot/Crew Training and Maintenance
· Test Rig Software (HATS/ENTEST Software) software
· Test Rigs used only during development phase
· Type C TTGEs including GOS(Secondary), SRS/SRD approved by CEMILAC, as applicable
GSS
· Software changes post clearance
CFE Software / Bought out Software
Software Clearance by CEMILAC
·

Software Development Plan (SDP) approved by Main Contractor QA

SQAP approval and SCMP compliance by DGAQA

Unit Testing, Integration Testing, Functional Testing and V&V documents

approved by Main Contractor QA.
IV&V conducted by an independent entity

STP, STR, SQAR approved by DGAQA

applicable
Software Clearance by DGAQA

11. Conclusion

This directive gives a general guidance on software QA activities to be followed during software
Quality Assurance activities with special emphasis on IV&V that may be uniformly followed.
Suggestions / Improvements, if any, may please be forwarded to Director (IT) HQ DGAQA.

12. References

· Framework and Procedure for Design, Development and Production of Military Air Systems
& Airborne Stores, Version 1.0
· Indian Military Technical Airworthiness Requirements IMTAR, IMAP
· Software Considerations in Airborne Systems and Equipment Certification – DO178C
· Guidelines for Qualification Test Procedure & Acceptance Test Procedure of ground
Equipment/Test equipment (jigs) for Airborne items (electrical & electronic)- AQA directive
issued on January 2015
· Open literature available on the subject in public domain.
· JSG: 0811
पृष्ठ संख्या Page 15 of 16
 वै गु आ महा निदेशालय संख्या. 13 / 2023 AQA Directive No. 13 / 2023
अंक-1, संशोधि-0, िवम्बर 2023 Issue I, Rev-0, Nov 2023

िोट: िवीितम अद्यति मािकं, प्रौद्योनगकी आनद के साथ दस्तावेि को बेहतर बिािे के नलए सुझाव, यनद कोई हो। इसे अग्रेनित
नकया जा सकता है:

Note: Suggestion, if any, to improve the document with latest updated standards,
technology etc. may be forwarded to:

निदेशक (सूचिा प्रौद्योनगकी), Director (IT),

वैमानिक गुणवत्ता आश्वासि महानिदेशालय Directorate General of Aeronautical Quality
Assurance,
रक्षा मंत्रालय, सातवं मंनजल,
"ए" ब्लॉक, रक्षा कायालय पनरसर, Ministry of Defence, 7th Floor,`A' Block,

कस्तूरबा गंधी मागग, िई नदल्ली -110001 Defence offices Complex, K G Marg,

ईमेल आई.डी: [email protected] New Delhi-110 001
Email ID: [email protected]

पृष्ठ संख्या Page 16 of 16