Москва, 29-30 октября 2012 г.

Международная конференция

Organization-technical methods for development of

on-board equipment based on IMAKoverninskiy Igor V., Kan Anna V.

FGUP GosNIIAS

Introduction

On-board equipment development on the base of IMA with open architecture, which consists of unified, full functions set of hardware and software, developed by Russian-European cooperation activity

This development is aimed for detail work out and automation of processes, that provide forces coordination for the creation of certifiable on-board treatment

2

System processes

The designing of on-board equipment demands providing of the following processes:

• End-to-end planning

• Managing process by modification implementation during the whole life-cycle of on-board equipment

• Strict configuration control providing process during the whole life-cycle of on-board equipment

• Requirements hierarchy system creation process starting from the top-level requirements for the on-board equipment and ending with requirements for separate components

3

Systems Development based on IMA

GUIDELINES AND METHODS FOR

CONDUCTING THE SAFETY

ASSESSMENT

PROCESS ON CIVIL AIRBORNE

SYSTEMS AND EQUIPMENT

Р4761 (ARP 4761)

System development process

Р4754ARP 4754A /ED-79)

“Guidelines for development of civil

aircraft and systems ”

Electronic HW Development

Process

КТ-254

(DO-254/ED-80)

Software Development

Process

КТ-178(DO-178B/ED-12B)

Design tradeoffs

КТ-178B

Inputs & Outputs

КТ-254

Inputs & Outputs

DO-297Integrated Modular Avionics(IMA) Development

Guidance and Certification Considerations

4

Key Concepts of ARP 4754A: General

Tenets of Industry Best Practice

Planning and documentation

• Define what you are going to do, do it, and gather evidence along the way

Requirements management

• Requirements must be captured, validated, implemented, verified, and traced

Safety Analyses as part of development process

• Functional Hazard Assessment and architecture drives Development Assurance Levels(DALs) thus process rigor

• Derive safety-related system requirements

Structure and control throughout the process

• Configuration management to control documents/data/tools, process assurance to monitorprocess, certification interface to find compliance

Thorough verification

• Reviews/simulation/analysis/test as appropriate at each stage5

6

7

Guidelines for on-board equipment

development SAE ARP4754a – GUIDELINES FOR

DEVELOPMENT OF CIVIL AIRCRAFT AND

SYSTEMS

1. SCOPE

1.1. Purpose

1.2 Document Background

2. REFERENCES

2.1 Applicable Documents

2.2 Definitions

2.3 Abbreviations and Acronyms

3. DEVELOPMENT PLANNING

3.1 Planning Process

3.2 Transition Criteria

4. AIRCRAFT AND SYSTEM DEVELOPMENT

PROCESS

4.1 Conceptual Aircraft/System Development Process

4.2 Aircraft Function Development

4.3 Allocation of Aircraft Functions to Systems

4.4 Development of System Architecture

4.5 Allocation of System Requirements to Items

4.6 System Implementation

5. INTEGRAL PROCESSES

5.1 Safety Assessment

5.2 Development Assurance Level Assignment

5.3 Requirements Capture

5.4 Requirements Validation

5.5 Implementation Verification

5.6 Configuration Management

5.7 Process Assurance

5.8 Certification and Regulatory Authority Coordination

GUIDELINES FOR DEVELOPMENT OF

ON-BOARD EQUIPMENT

INTEGRAL PROCESSES

ON-BOARD EQUIPMENT TECHNICAL DOCUMENTATION

VOLUME 5.1

Technical

Documentation

ON-BOARD EQUIPMENT DEVELOPMENT

VOLUME 3.2

Functions and

Technical

Requirements

for

On-board

Equipment

VOLUME 3.1

On-board

Equipment

Development

Life Cycle VOLUME 3.3

Design and

Architecture

Development

VOLUME 4.5

Quality

Assurance

Process

VOLUME 4.3

Verification

Process

VOLUME 4.2

Validation

Process

VOLUME 4.1

Safety

Assessment

&

Human

FactorsVOLUME 4.4

Configuration

Management

Process

GENERAL PROVISIONSVOLUME 1.1

General

Provisions

ON-BOARD EQUIPMENT DEVELOPMENT PLANNING

VOLUME 2.1

On-board

Equipment

Development

Planning

VOLUME 2.2

Suppliers

VOLUME 3.4

Systems,

HW and SW

Development

VOLUME 4.6

Certification

Process

VOLUME 3.5

Design of

Onboard

Maintenance

Means

8

Analysis of existing tools

There are a number of both commercial and free tools, that are partially perform required functions. Although all instruments have got disadvantages:

• There is no such tool at the market, which could fully meet the requirements of КТ-178В (DO-178B) in part of life-cycle’s support and at the same time could allow convenient interaction with SW requirements. The end-user has to compile the integration from several tools, and the final set may not provide the required level of convenience and ergonomics

• Tools, which are proposed at the market, initially are not oriented on compliance with КТ-178В (DO-178B) , and additional settings are required, still some aspects of compliance couldn’t be achieved in the boundaries of the tool or are being achieved by artificial way

• Proposed high-quality commercial products are expensive

• Free products could be complex and unreliable in operation, because there are no qualitative documentation and developers’ support

9

Program tools designing requirements

• Program tools set, which are automating and formalizing the execution of mentioned integration processes shall be unified at the max level in the boundaries of enterprises-developers of on-board equipment cooperation

• To provide end-to-end configuration control of modification implementation in the project for enterprises-developers

• To provide the unified procedure of data exchange between the enterprises

• To simplify the certification process

• Its structure shall consist of the existing recognized SW and also specialized web-oriented information systems, which are being mastered in the boundaries of Russian and European scientific activity.

10

The tools, developed in the boundaries of

scientific activity “KBO-integration”

• Е178В – DC BARS Ltd.

• ISUT (requirements management

system) – Interface Ltd.

• MASIW (Modular avionics system

integrator workplace) –ISP RAN

(Institute for System Programming)

11

DC BARS Ltd.: profile

Since 1994

● V&V of airborne SW per DO-178B

● SW development

● Certification support

200+ engineers, 4 engineering facilities

E178B: At least 20 engineers involved

Started on April 2010

http://www.dcbars.net/

12

E178B: architecture, tools

Client Server

PostgreSQL +

Java +

ApacheMQ

System core is based on OSEE

http://www.eclipse.org/osee/13

Started on April 2010

Phase 1 (2010):

– Prototype development

Phase 2 (2011):

– Support of all CM processes and QA audits

– Documentation editor prototype

– Integration with IBM Rational DOORS

– E-mail notifications

– Localization approach

Phase 3 (2012):

– Full-featured documentation editor + document publishing

– Basic PM functions

– Artifact search and compare functions

– Engine for database migration to newer server versions

– Trial operation

– Fully packaged product

E178B: tasks, phases

14

Since 1990

● Sales and marketing services

● Training

● …

120+ engineers, 2 branches, several offices in Russia and

abroad, partners – IBM, Microsoft, Borland, Symantec et

al.

Interface Ltd.: profile

15

ISUT: architecture, tools

Plugins for Doors

Version 1

Version 2

Requirements management and

configurationRequirements change control

Requirements publishing

16

Requirements management and

configuration subsystem

Functions:

• Tracking of changes in the requirements list and sole requirements

• Linking the requirements and tracking the links

• Control of implementation status

• Tracking of test results and requirements coverage

• Creation of documentation and reports

17

Requirements changing management

subsystem

Functions:

• Combining of all information repositories of version control systems and modification management under the control of the one server

• Wide possibilities of reports generation , analysis and visualization of trends

• Convenient and user-friendly interface for creation, tracing and evolution of change requests

• The flexible tuning of the changing management process for maximum adaptation to existing user’s requirements for the project organizing.

18

Requirements publishing management

subsystem

Functions:

• The connection possibility to any XML source

• The support for the number of inputs formats and flexible tuning of the documents’ external view

• Parallel generating of different formats documents based on the one pattern

• The reports creation, which contain data from several sources

• Built-in default patterns, which provide fast implementation

• User-friendly patterns correction graphic environment

19

ISP RAS

• The Institute for System Programming (ISP) of the Russian Academy

of Sciences (RAS) was founded on January 25, 1994, on the base of

the departments of System Programming and Numerical Software of

the Institute for Cybernetics Problems of the RAS.

• ISP RAS belongs to the Division of Mathematical Sciences of the

RAS.

• The activities of the Institute include three main components:

• Fundamental Research;

• Software Development and Applied Research for the benefits of the

Industry;

• Education.

• The Institute employs more than 200 highly qualified researchers

and software engineers, including 12 doctors of science and 45

philosophy doctors. Many employees of the Institute also work as

professors in leading Russian universities.

20

21

MASIW 2012

• modeling of IMA architecture from system-levelspecification downto implementation details ofhardware and software components

• static schedule building for periodic ARINC-653 partitions and specialized middleware tasks

• verification of resource allocation consistency, usage domain rule and project-specificconstraints

• AFDX static analysis and simulation framework;

• generation and import of configuration tablesfor VxWorks-653 RTOS and AFDX networkelements

v

AADLModel Editor

РедакторAADL моделей

REALRule Editor

Редактор правилREAL

Designer

Конструктор

Configurator

Конфигуратор

Cfg Аnalyzer

Анализатор конфигурации

Аnalyzer

Анализатор модели

Cfg Generator

Генераторконфигурационных

файлов

ХранилищеАрхитектурных

моделей

ArchDB

22

Conclusion

• Implantation and providing of developed tools and methodologies trial performance at the aviation industry enterprises

• It’s planned to develop work procedures with requirements for system engineering different processes supporting, and also procedures of management requirements configuration and requirements interaction with all systems designing life-cycle processes (according with GOST 15288 (ISO 15288-2008), ARP 4754 A)

• The creation of system engineering instrumental platform according with aviation standards based on free SW

• The report introduces the following DC BARS, “Interface IT”, ISP RAS lecturers

23

Thank you!

Questions?

24