EN 4660-005:2011

0 Introduction
1 Scope
2 Normative references
3 Terms, definitions and abbreviations
4 System Functions
5 Software Architecture Definition
6 Direct Interfaces Definitions
7 Logical Interfaces Definitions
8 Data Type Definitions
9 Tailoring
Annex A (normative) - AGL

The purpose of this European Standard is to establish uniform requirements for design and development of software architecture for modular avionics systems as defined per ASAAC.1.1Software Architecture OverviewThe ASAAC Software Architecture is based on a three-layer stack as shown by a simplified Figure 2.Each layer is described in terms of it dependency/independency on both the aircraft system and the underlying hardware.1.2Software Architectural ComponentsFigure 3 provides an overview of the software architectural components and software interfaces.1.2.1Functional ApplicationsThe term "Functional Applications" relates to all functions that handle the processing of operational data, e.g.-Radar Applications,-Mission Management,-Stores Management,-Vehicle Management System,-Communication, Navigation and Identification.1.2.2Application Management (AM)AM is responsible for the non-standardised system management, i.e. the AM performs the non-generic system management. As an example, the AM may perform the mission/moding management. The interface between the AM and GSM is the System Management Logical Interface (SMLI) (see 4.1.2).1.2.3Operating System (OS)A Real-Time OS provides the particular part of OSL functionality that controls the real-time behaviour of the Processing Element and its associated resources (see Clause 0).1.2.4Generic System Management (GSM)The GSM is responsible for the management of the core processing (see 4.1.1 and 5.2.1). This functionality is divided into four areas:-Health Monitoring,-Fault Management,-Configuration Management,-Security Management.1.2.5Run-Time Blueprints (RTBP)The RTBP contain the information (e.g. process description, routing information, fault management data) required to configure and manage the core processing on which it is hosted (see 5.3).(...)