International System/Software Best Practices in Avionics and Defence Software (Preview of popular Avionics & Defence Standards).

1. ESSS 2016 – Avionics & Defense Track
V&V Lessons Learnt
Under Multiple Standards
Pradeep Oak
Oak Systems Pvt Ltd.
1
/ oaksys / Oak-systems / oaksystesting / oaksys

2. Agenda
 About Oak Systems
 International System/Software Best Practices
in Avionics and Defence Software (Preview of
popular Avionics & Defence Standards)
 V&V Best Practices
 Q & A
2

3. About Oak Systems
 Specialist Software V&V Services company
 Established in 1998
 ISO 9001 certified since 2003
 Over 100 Software specialists
 Multiple domain expertise
 Headquartered in Bengaluru; Projects across
several countries
3

4. Our Portfolio 4
Domains
Aerospace &
Defence
Automotive
Embedded
Healthcare
Rail & Space
Services
Software
Verification &
Validation
Test Rig
Development
Software Testing &
Test Automation
Full lifecycle
Documentation
Support
Standards
DO-178B/C
ISO 26262
IEEE 12207
IEC 61508..

5. International Best Practices 5
There are numerous standards, frameworks and guidelines covering
software systems -
 ISO, IEC, IEEE, DO, …
 DOD-STD-2167A
 IEEE/ISO/IEC 12207
 RTCA DO-178
 CMMI / ISO 9001, …
Over the years, all the standards are learning from experience, from
one another & we see a convergence among them
Let us look into some of these ...

6. DOD-STD-2167A
Military Standard for Defense System Software Development
6
 Contains requirements for the development of Mission-Critical
Computer System S/W
 Establishes a uniform software development process which is
applicable throughout the system life cycle
 Defines development activities which result in:
I. generation of different types & levels of software and documentation
II. application of development tools, approaches, and methods
III. project planning and control
 Incorporates practices which have been demonstrated to be cost-
effective from LC perspective, based on information gathered by
the DoD and industry.

7. DOD-STD-2167A 7

8. DOD-STD-2167A
Military Standard for Defense System Software Development
8
 Was intended to be dynamic and responsive to the rapidly evolving
software technology field
 Should be selectively applied and tailored to fit the unique
characteristics of each software acquisition program.
 MIL-STD-498 superseded DOD-STD-2167A; IEEE12207 superseded 498.
 V&V in DOD-STD-2167A is around preliminary & baselined work
products (documents, Code, Exe); There is no clarity on V&V and
IV&V at in-process Activities

9. IEEE/ISO/IEC12207
Systems and software engineering — Software life cycle processes
9
 Provides a common framework for developing and managing
software. The processes in this Standard form a comprehensive set.
 An organization, depending on its purpose, can select an appropriate
subset to fulfill that purpose
 Designed to be tailored for an organisation, project, or application
 Designed to be used when software is a stand-alone entity, or an
embedded or integral part of the total system
 Processes of Acquirer, Developer, Supplier, Assessor, User
 Flexibility in use of chosen SDLC model, including Agile

10. Organisation of IEEE 12207 10

11. DO-178 B/C
Considerations in Airborne Systems and Equipment Certification
11
 Provides Guidance for determining, in a consistent manner and
with an acceptable level of confidence, that the software
aspects of airborne systems and equipment comply with
airworthiness requirements
 Levels – A, B, C, D, E (Based on Safety Assessment of the System)
 Does not prescribe any specific SDLC model
 V & V form a significant subset of objectives
 Verification as a combination of reviews, analyses and testing

12. DO-178B Lifecycle Model 12

13. CMMI
13

14. ISO 9001
14

15. IEEE 1012-2004
IEEE Standard for Software Verification and Validation
15
This standard applies to software being developed, maintained, or
reused [legacy, commercial-off-the-shelf (COTS), non-developmental
items]. The term software also includes firmware, microcode, and
documentation. Software V&V processes include analysis, evaluation,
review, inspection, assessment, and testing of software products

16. IEEE 1012-2004 16
Key concepts
Software integrity levels: Four software integrity levels to describe the
importance of the software, varying from high integrity to low integrity,
to the user
There are minimum V&V tasks required for each of the four software
integrity levels.
Optional V&V tasks defined for tailoring the V&V effort to address
project needs and application specific characteristics

17. IEEE 1012-2004 17
Key concepts
Intensity and rigour applied to V&V tasks vary according to the
software integrity level. Higher software integrity levels require greater
intensity and rigour to the V&V task.
Criteria for V&V tasks for correctness, consistency, completeness,
accuracy, readability, and testability

18. Software Integrity Levels 18
 Software integrity levels determine the V&V tasks to be
performed.
 Integrity levels are assigned to software requirements,
functions, groups of functions, or software components or
subsystems.
 High-integrity software - larger set of V&V processes and
more rigorous V&V tasks.
 Each Integrity level - has minimum V&V tasks and addition
of optional V&V tasks

19. V&V Lessons Learnt 19
 It is important to understand the User Requirements, Domain,
Stds requirements/system context
 No matter what is the standard to be followed, core activities
remain the same
 Interpretation of standard/guideline to your context is
important
 Focus on your programme goals & objectives
 Focus on Defect Prevention

20. In a nutshell .. 20
 All standards & Guidelines talk of the same thing in different
languages/jargon
 V&V activities to be planned keeping in mind the functional &
non-functional requirements, safety requirements and such
other considerations
 It is possible to combine IEEE/DO/ISO/CMMI into one single
quality management process

21. 21
Questions & Answers
You can contact me for any support/queries
pradeep@oaksys.net

22. Thank you!
Oak Systems Pvt. Ltd.
#27, NGEF Lane, Off 100 Feet Road,
Indira Nagar, Bangalore – 560 038, INDIA
Tel : +91-80-41 26 76 81
Email: contact@oaksys.net
URL: www.oaksys.net
22