Upload
varun-pra
View
73
Download
3
Tags:
Embed Size (px)
Citation preview
INTRODUCTION TOAVIONIC SYSTEMS DEVELOPMENT
WORKSHOP
This Workshop provides a comprehensive overview to the process, methods, techniques and tools for the Avionic Systems design, development and integration. Main topics include:
A preliminary overview of the systems engineering concepts
A detailed analysis of the avionic system development process, including the designapproach and the activities to be performed during the entire system development cycle,from the feasibility studies to the operational clearance
A detailed description of the methods and tools that are currently used for the avionicsdevelopment and integration. Particular consideration is given to the modern modeling andsimulation methods, techniques and tools which can be used for the system development,including the system architectural design. The basic concurrent engineering concepts arealso addressed.
Quality and safety aspects.
The Workshop is designed for beginning systems engineers, but will also serve to introduce avionics fundamentals to practicing engineers of small and medium enterprises involved in the design, development and operation of avionic systems, subsystems and components.
WORKSHOP OVERVIEW
CONTENT1. INTRODUCTION TO SYSTEMS ENGINEERING
1.1. The Current Environment1.2. Definition of a System1.3. Definition of Systems Engineering1.4. The System Life Cycle
2. THE AVIONIC SYSTEM DEVELOPMENT CYCLE
2.1. Design Approach
Top Down Design ApproachBottom Up Design ApproachLife Cycle Design ApproachThe System Development ModelModel Based System Development
2.2. Development Phases
Development Cycle OverviewFeasibility StudyOperational RequirementsPreliminary System DesignDetailed System Design
CONTENT (cont d)
Equipment DevelopmentOperational Software DevelopmentDevelopment of Integration and Testing FacilitiesSystem Integration and TestingGround TestsFlight Tests
3. AVIONIC SYSTEM DEVELOPMENT METHODS AND TOOLS
3.1. Concurrent Engineering
GeneralThe System Development ProcessImproving the System Development ProcessDistributed Systems Engineering
3.2. Operational Software Development Facilities
Software Design, Coding and TestingSoftware Verification
3.3. System Integration and Testing Facilities
Integration RigsAntenna Testing
CONTENT (cont d)
Electromagnetic Compatibility TestingHIRF Testing
3.4. Modeling and Simulation Tools
Modeling and Simulation Tools for the System Architectural DesignReconfigurable SimulatorsMission SimulatorsSoftware Modeling and Automatic Code GenerationDistributed Interactive Simulation
3.5. Rapid Prototyping Tools for the HMI Design
4. QUALITY AND SAFETY ASPECTS
4.1. Quality Engineering
Total Quality ManagementQuality Systems, Standards and SpecificationsProduct and Process Quality Assurance
CONTENT (cont d)
4.2. System Configuration Management
GeneralConfiguration Change ControlSoftware Configuration
4.3. Development of Safety Critical Elements
Safety and Mission Critical FunctionsSafety EngineeringFault Tolerance Concept
1. INTRODUCTION TO SYSTEMS ENGINEERING
1.1. The Current Environment1.2. Definition of a System1.3. Definition of Systems Engineering1.4. The System Life Cycle
THECURRENT
ENVIRONMENT
SYSTEM ENGINEERING CONCEPTS, PRINCIPLES AND METHODS
CONSTANTLY CHANGINGREQUIREMENTS
CHANGINGTECHNOLOGY
LONGERACQUISITION TIMES
GREATERINTERNATIONAL COMPETITION
HIGHEROVERALL COSTS
EXTENDED SYSTEMLIFE CYCLES
MULTIPLEPRIME/SUPPLIER TEAMS
INCREASINGSYSTEM COMPLEXITY
1.1. The Current Environment
A SYSTEM CONSTITUTES A SET OF INTEGRATED COMPONENTS WORKING TOGETHER WITH THE COMMON OBJECTIVE OF FULFILLING SOME DESIGNATED USER NEED
CONSTRAINTS
- Technology- Economic- Social- Political- Environmental
RESOURCEREQUIREMENTS
- Human- Equipment- Software- Facilities- Data- Maintenance
Support
SYSTEM
INPUT
UserRequirements
(Need)
OUTPUT
A System thatwill respond to a User need in an
effective and efficient manner
1.2. Definition of a System
THE MAJOR ELEMENTS OF A SYSTEM
OperatingPersonnel
PrimeOperatingEquipment
OperatingSoftware
Data
Test andSupport
Equipment
MaintenanceElements
THE SYSTEM
1.2. Definition of a System
EXAMPLE MODERN COMBAT AICRAFT
1.2. Definition of a System
EXAMPLE ATTACK HELICOPTER
1.2. Definition of a System
THE SYSTEM ENGINEERING IS THE EFFECTIVE APPLICATION OF SCIENTIFIC AND ENGINEERING EFFORTS TO TRANSFORM AN OPERATIONAL NEED INTO A DEFINED SYSTEM CONFIGURATION THROUGH THE TOP DOWN ITERATIVE PROCESS OF REQUIREMENT ANALYSIS, FUNCTIONAL ANALYSIS AND ALLOCATION, SYNTHESIS, DESIGN OPTIMIZATION, TEST AND EVALUATION AND VALIDATION
The Department of Defense (DOD) defines Systems Engineering as the Process that:
- transforms operational needs and requirements into an integrated system design solution throughconcurrent consideration of all Life Cycle needs
- ensures that system definition and design reflect the requirements for all system elements
- ensures the compatibility, interoperability and integration of all functional and physical interfaces
- characterizes and manages technical risk
1.3. Definition of Systems Engineering
SYSTEMS ENGINEERING AREAS OF EMPHASIS
A Top Down approach is required, viewing the system as a whole.An overview and an understanding of how the system components fittogether are essential.
A Life Cycle orientation is required, addressing all phases to include system design and development, production, operation, maintenace, support and retirement.
A complete effort is required relative to the initial identification of system requirements, in order to ensure the effectiveness of early decision making in the design process.
Interdisciplinary effort and team approach are required throughoutthe system design and development process.
1.3. Definition of Systems Engineering
EXAMPLE OF SYSTEM LIFE CYCLE
1.4. The System Life Cycle
SYSTEM ENGINEERING WITHIN THE SYSTEM LIFE CYCLE
THE SYSTEM ENGINEERING PROCESS IS CONTINUOUS, ITERATIVE AND INCORPORATES THE NECESSARY FEEDBACK PROVISIONS AT EACH STEP OF THE SYSTEM LIFE CYCLE
1.4. The System Life Cycle
2. THE AVIONIC SYSTEM DEVELOPMENT CYCLE
2.1. Design Approach
2.1.1. Top Down Design Approach2.1.2. Bottom Up Design Approach2.1.3. Life Cycle Design Approach2.1.4. The System Development Model2.1.5. Model Based System Development
2.2. Development Phases
2.2.1. Development Cycle Overview2.2.2. Feasibility Study2.2.3. Operational Requirements2.2.4. Preliminary System Design2.2.5. Detailed System Design
2.2.6. Equipment Development2.2.7. Operational Software Development2.2.8. Development of Integration and Testing Facilities2.2.9. System Integration and Testing2.2.10. Ground Tests2.2.11. Flight Tests
TOP DOWN DESIGN APPROACH
OPERATIONALREQUIREMENTS
SYSTEMDESIGN
COMPONENTSDEVELOPMENT
INTEGRATION
- DRIVEN BY OPERATIONAL REQUIREMENTS
- PERFORMANCE ORIENTED
- IMPLIES SIGNIFICANT DEVELOPMENT WORK AT BOTH SYSTEMAND COMPONENTS LEVELS
- PLATFORM SPECIFIC
- USED FOR SYSTEMS DEVELOPMENT AT THE UPPERTECHNOLOGY EDGE
- TYPICAL OF NEW MILITARY PROGRAMS WITH VERYDEMANDING REQUIREMENTS
2.1. Design Approach
BOTTOM UP DESIGN APPROACH
EXISTINGCOMPONENTS
ADAPTATION
INTEGRATION
PERFORMANCEASSESSMENT
- BASED ON REUSE OF EXISTING COMPONENTS, ACCORDING TOTHE OFF THE SHELF CONCEPT
- COST ORIENTED
- REDUCES DEVELOPMENT EFFORT, TECHNICAL RISKAND PROGRAM TIMESCHEDULE
- CAN BE EASILY ADAPTED TO DIFFERENT PLATFORMS
- CONFLICTS WITH THE NEED FOR TECHNOLOGYGROWTH
- TYPICAL OF MILITARY UPGRADE PROGRAMSWITH LIMITED BUDGETS AND SHORTTIMESCHEDULES
2.1. Design Approach
FUNCTIONAL DECOMPOSITION
Hierarchy Level 0(Context-Diagram)
External Data Sink
External Data Source
Bottom-Up
Top-Down
Hierarchy Level 1
Hierarchy Level 2
2.1. Design Approach
2.1. Design Approach
GENERATORSHIGH LEVEL CONTROLS
STATUS
MISSION AVIONICS
SENSOR(S) SENSORSCONTROL
SENSORSINTERFACE
HORIZONTALENGINE
CONTROLHORIZONTAL
ENGINE
NGIRI
DIRECTION
STATUS
VERTICALENGINE
CONTROLVERTICALENGINE
NGIRI
STATUSPROVISION
BASICAVIONICS
VROT
VOICE
MISSION DATA
VOICE
TO AIRTRAFFIC CONTROL
ELECTRICAL POWER GENERATIONAND DISTRIBUTION SYSTEM
EPGDS CONTROL
HIGH LEVEL CONTROLS
STATUS
PNEUMATIC SYSTEM
ACTUATORS PS CONTROL
HIGH LEVEL CONTROLS
STATUS
UNDERCARRIAGE SYSTEM
ACTUATORS US CONTROL
VIDEO
DATA
GROUNDSTATION
NAUTILUS ETF AVIONICS FUNCTIONAL ARCHITECTURE LEVEL ZERO
2.1. Design Approach
NAUTILUS ETF AVIONICS FUNCTIONAL ARCHITECTURE LEVEL ONE
BASIC AVIONICS
HORIZONTALENGINES
VERTICALENGINES
NGIRI
DIRECTION
STATUS
NGIRI
STATUS
VROT
GROUNDSTATION
VOICE
DATA
AIR TRAFFICCONTROL
HIGH LEVELCONTROLS
STATUS
EPGDS
PROVISION
MISSIONAVIONICS
HIGH LEVELCONTROLS
STATUS
HIGH LEVELCONTROLS
STATUS
PS
USVOICE
VIDEO
COMMUNICATIONSSUBSYSTEM
UTILITIESCONTROL
SUBSYSTEM
FLIGHTCONTROLS
SUBSYSTEM
NAVIGATIONSUBSYSTEM
FLIGHT MANAGEMENTSUBSYSTEM
AUTOPILOT
MONITORING ANDRECORDINGSUBSYSTEM
VISIONSUBSYSTEM
VIDEO
DATA
MISSION DATA
TO COMMUNICATIONSSUBSYSTEM
FROM NAVIGATIONSUBSYSTEM
FROM ALL SUBSYSTEMS
LIFE CYCLE DESIGN APPROACH
THE SYSTEM ENGINEERING PROCESS MUST ENSURE THAT THE USER REQUIREMENTS ARE MET IN AN EFFECTIVE AND EFFICIENT MANNER ACROSS THE ENTIRE SYSTEM LIFE CYCLE, INCLUDING DEVELOPMENT, PRODUCTION AND OPERATIONAL USE.
SYSTEM DESIGN REQUIREMENTS
- FUNCTIONS
- PERFORMANCE
- MAN/MACHINE INTERFACE
- COST/EFFECTIVENESS
- ENVIRONMENTAL REQUIREMENTS
- RELIABILITY
- MAINTAINABILITY
- TESTABILITY
- SAFETY
- SURVIVABILITY
- VULNERABILITY
- RECONFIGURABILITY
- HUMAN FACTORS
- PRODUCUBILITY
- SERVICEABILITY
- LIFE CYCLE COST
2.1. Design Approach
THE V SYSTEM DEVELOPMENT MODEL
HW / SW Design
SystemAcceptance
System Integration & Test
Module Integration & Test
Requirements Analysis
System Modification
SystemsAnalysis &
Design
Test Scenarios
Test Scenarios
Test Scenarios
HW / SWImplementation
& Unit Test
2.1. Design Approach
DEVELOPMENT CYCLE OVERVIEW
OperationalRequirements
SystemPreliminary
DesignReview
SystemFinal
DesignReview
SystemTest
ReadinessReview
Installationon Aircraft
FlightRelease
OperationalClearance
PreliminaryDesign
DetailedDesign
Equipment Development
Software Development
Development of Integrationand Testing Facilities
GroundTests
Flight Tests
System Integration and Testing
2.2. Development Phases
FEASIBILITY STUDYINPUT
- OPERATIONAL REQUIREMENTS
ACTIVITIES
- IDENTIFICATION OF RISK AREAS
OBJECTIVE
- RISK REDUCTION
- IDENTIFICATION OF THE VARIOUS POSSIBLETECHNOLOGICAL AND DESIGN APPROACHES
- EVALUATION OF THE CANDIDATES IN TERMS OF PERFORMANCE,EFFECTIVENESS, LOGISTIC REQUIREMENTS AND LIFE CYCLE ECONOMIC CRITERIA
- INITIATION OF RESEARCH ACTIVITIES, IF REQUIRED, WITH THE OBJECTIVE OFDEVELOPING NEW METHODS/TECHNIQUES FOR SPECIFIC APPLICATIONS
- SELECTION OF AN OVERALL TECHNICAL APPROACH ANDRECOMMENDATION TO THE CUSTOMER
OUTPUT
- FINALIZED OPERATIONALREQUIREMENTS
- AGREED OVERALL TECHNICALAPPROACH
2.2. Development Phases
OPERATIONAL REQUIREMENTS
THE OPERATIONAL REQUIREMENTS REFLECT THE NEEDS OF THE USER RELATIVE TO SYSTEM UTILIZATION AND THE ACCOMPLISHMENT OF A MISSION.
TYPICAL OPERATIONAL REQUIREMENTS FOR MILITARY AIRCRAFT
- OPERATIONAL DEPLOYMENT: NUMBER OF SITES, GEOGRAPHICAL DISTRIBUTION, QUANTITY
- MISSION TYPES: AIR SUPPORT, INTERDICTION, INTERCEPTION, AIR DEFENSE, ETC.
- MISSION PROFILE: FLIGHT PATH, RANGE, ALTITUDE
- MISSION SCENARIO: TERRAIN, TARGETS, THREATS, ETC.
- OPERATIONAL FUNCTIONS: NAVIGATION, WEAPON AIMING, MAN/MACHINE INTERFACE, STORE MANAGEMENT, ETC.
- UTILIZATION REQUIREMENTS: OPERATING HOURS, DUTY CYCLE, OPERATIONAL LIFE, ETC.
- EFFECTIVENESS REQUIREMENTS: RELIABILITY, MAINTAINABILITY, TESTABILITY, VULNERABILITY, ETC.
- ENVIRONMENT: TEMPERATURE, VIBRATION, ELECTROMAGNETIC COMPATIBILITY, ETC.
- PERFORMANCE: NAVIGATION ACCURACY, WEAPON DELIVERY ACCURACY, REACTION TIME, WEIGHT, ETC.
2.2. Development Phases
PRELIMINARY SYSTEM DESIGN
OPERATIONALREQUIREMENTS
REQUIREMENTSANALYSIS
SYSTEMFUNCTIONAL
DESIGN
SUBSYSTEMFUNCTIONAL
DESIGN
SUBSYSTEMDESIGN
SYSTEMREQUIREMENTS
DOCUMENTS
SUBSYSTEMREQUIREMENTS
DOCUMENTS
HARDWARE/SOFTWARECOMPONENTS
DEFINITION
ITERATIONS
ITERATIONS
ITERATIONS
OBJECTIVES OF THE PRELIMINARY SYSTEM DESIGN PHASE
- CONVERSION OF THE OPERATIONAL REQUIREMENTSINTO AN INTEGRATED SYSTEM DESIGN SOLUTION
- DEFINITION OF THE SYSTEM FUNCTIONAL ARCHITECTURE,HARDWARE/SOFTWARE PARTITIONING AND SYSTEMPHYSICAL ARCHITECTURE
2.2. Development Phases
AVIONIC SYSTEM SPECIFICATION
SCOPE
APPLICABLE DOCUMENTS
OPERATIONAL REQUIREMENTS
Mission Types
Mission Profiles
Mission Scenario
Utilization Requirements
General
System Functional Architecture
FUNCTIONAL AND PERFORMANCEREQUIREMENTS
GeneralSystem Moding
Subsystems Definition
Flight Management SubsystemAutopilotCommunications SubsystemVision SubsystemUtilities Control SubsystemMonitoring and Recording Subsystem
2.2. Development Phases
Functional Interface
External InterfaceInternal Interface
Navigation SubsystemFlight Controls Subsystem
System Performance RequirementsNavigation AccuracyCommunications Subsystem PerformanceVision Subsystem PerformanceSystem Readiness for Operations
PHYSICAL REQUIREMENTS
Hardware ConfigurationHardware Preliminary ArchitectureEquipment FunctionsSystem Intercommunication
2.2. Development Phases
Physical Characteristics
System WeightSystem VolumeInstallation Requirements
Electrical Power Supply Requirements
Electrical Power Supply CharacteristicsPower Consumption
Cooling Requirements
Cooling Air CharacteristicsAir Mass Flow
SAFETY AND MISSION CRITICALITYDESIGN REQUIREMENTS
Basic Definitions
Safety/Flight Critical FunctionsMission Critical Functions
Basic Design Requirements
Safety/Flight Critical Failure Rate
Software Development Environment
Software Development ToolsHost SystemSoftware Integration and Verification Facilities
Software Design/Architecture
Software Design MethodologiesSoftware ArchitectureSoftware Development PhasingVerification of Software
DESIGN AND CONSTRUCTION Environmental Conditions
Temperature/Altitude
OPERATIONAL SOFTWARE DESIGNREQUIREMENTS
Mission Critical Failure RateFailure Tolerance RequirementsRedundancy and Reconfiguration Concept
AVIONIC SYSTEM SPECIFICATION (cont d)
UmidityVibrationsShockSalt FogOthers
2.2. Development Phases
AVIONIC SYSTEM SPECIFICATION (cont d)
Electromagnetic Compatibility
Radiated and Conducted EmissionsSusceptibility to Radiated and ConductedEmissions
Lightning Protection
LOGISTIC SUPPORT REQUIREMENTS
Reliability
SYSTEM TESTING, QUALIFICATION ANDCERTIFICATION REQUIREMENTS
System Testing and Qualification
Avionics System Test ConceptEquipment Testing and QualificationSoftware VerificationSystem Integration and TestingOn Aircraft Ground TestingFlight Testing
System Certification
Maintainability
Testability
PRELIMINARY SYSTEM DESIGN
EXAMPLE INTEGRATED NAVIGATION SUBSYSTEM
ALTITUDEDATA
GENERATION
INERTIALDATA
GENERATION
GPSDATA
GENERATION
TERRAINREFERENCENAVIGATION
KALMANFILTER
NAVIGATION COMPUTING
TERRAIN DATA
AIRCRAFT POSITION
FUNCTIONAL ARCHITECTURE
RADARALTIMETER TRN
NAVIGATIONCOMPUTER
PHYSICAL ARCHITECTURE ALTERNATIVE 1
AVIONIC BUS
RADARALTIMETER INS GPS TRN
AVIONIC BUS
PHYSICAL ARCHITECTURE ALTERNATIVE 2
INS/GPS(INCLUDING
KALMAN FILTER)
NAVIGATION COMPUTER(INCLUDING
KALMAN FILTER)
2.2. Development Phases
DETAILED SYSTEM DESIGN
OBJECTIVES- PRODUCE DETAILED DEVELOPMENTSPECIFICATIONS AND ASSOCIATED DOCUMENTSIN ORDER TO START PARALLEL DEVELOPMENT OF THESYSTEM COMPONENTS AND OF THE INTEGRATION ANDTESTING FACILITIES
- SELECT EQUIPMENT SUPPLIERS
INPUT- RESULTS OF THE PRELIMINARYSYSTEM DESIGN
ACTIVITIES
- SELECTION OF EQUIPMENT SUPPLIERS
- DETAILED DEFINITION OF EQUIPMENT CHARACTERISTICS, INCLUDING FUNCTIONS, PERFORMANCE,FUNCTIONAL, ELECTRICAL AND MECHANICAL INTERFACES, CONTROLS AND DISPLAYS, PHYSICALREQUIREMENTS, ENVIRONMENTAL REQUIREMENTS, PRODUCT REQUIREMENTS, ETC.
- PREPARATION OF EQUIPMENT DEVELOPMENT SPECIFICATIONS AND ASSOCIATED DOCUMENTS
- DETAILED DEFINITION OF THE SOFTWARE REQUIREMENTS FOR THE OPERATIONAL FLIGHT SOFTWARE OF THEMISSION COMPUTER/COMPUTERS. PREPARATION OF THE SOFTWARE REQUIREMENTS SPECIFICATIONS AND OFTHE ASSOCIATED DOCUMENTS
- DETAILED DEFINITION OF THE DESIGN REQUIREMENTS FOR THE SYSTEM INTEGRATION ANDTESTING FACILITIES. PREPARATION OF THE RELEVANT SPECIFICATIONS AND ASSOCIATEDDOCUMENTS
OUTPUT- EQUIPMENT DEVELOPMENT SPECIFICATIONS ANDASSOCIATED DOCUMENTS
- SOFTWARE FUNCTIONAL REQUIREMENTS ANDASSOCIATED DOCUMENTS
- SYSTEM INTEGRATION AND TESTING FACILITIESSPECIFICATIONS AND ASSOCIATED DOCUMENTS
2.2. Development Phases
EQUIPMENT DEVELOPMENT
DEVELOPMENT AND PRODUCTION OF AVIONIC EQUIPMENT ARE USUALLY SUBCONTRACTED TO SELECTED SUPPLIERS
DESIGN REALIZATION OFA MODELSREALIZATION OF
B MODELSREALIZATION OF
C MODELSPRELIMINARY
QUALIFICATION
EQUIPMENTDEVELOPMENTSPECIFICATION
DESIGNDOCUMENTATION
ENGINEERING MODELSRETAINED BY THE SUPPLIER
FOR DEVELOPMENT ACTIVITIES
REPRESENTATIVE MODELSDELIVERED FOR SYSTEM
INTEGRATION AND TESTING
FLYABLE MODELSFOR INSTALLATIONON THE AIRCRAFT
PRELIMINARY DECLARATIONOF DESIGN AND PERFORMANCE
FOR FIRST FLIGHT
FINALQUALIFICATION
FINAL DECLARATIONOF DESIGN ANDPERFORMANCE
SUPPLIERS ACTIVITIES
ALL B AND C EQUIPMENT MODELS ARE SUBJECT TO ACCEPTANCE TESTING BEFORE DELIVERY
2.2. Development Phases
EQUIPMENT DEVELOPMENT
THE DEVELOPMENT ACTIVITIES PERFORMED BY THE EQUIPMENT SUPPLIERS ARE TECHNICALLY MONITORED BY EQUIPMENT ENGINEERS
EQUIPMENT ENGINEERS MAIN ACTIVITIES
- PREPARATION AND UPDATING OF THE EQUIPMENT SPECIFICATIONS
- TECHNICAL MONITORING OF THE EQUIPMENT DEVELOPMENT IN ORDER TO ENSURE COMPLIANCE WITH THE SPECIFIEDREQUIREMENTS
- IDENTIFICATION AND EVALUATION OF IMPACTS ON THE AVIONIC SYSTEM RESULTING FROM POSSIBLE DEVIATIONSFROM THE EQUIPMENT SPECIFICATIONS
- APPROVAL OF ALL DEVIATIONS FROM THE SPECIFICATIONS AND/OR MODIFICATIONS TO THE EQUIPMENT
- ANALYSIS AND APPROVAL OF ALL TECHNICAL DOCUMENTS PRODUCED BY THE SUPPLIERS
- TECHNICAL LIASON WITH THE SUPPLIERS
- SUPPORT TO SYSTEMS AND SOFTWARE ENGINEERS
2.2. Development Phases
OPERATIONAL FLIGHT SOFTWARE DEVELOPMENT
EXAMPLE OPERATIONAL FLIGHT SOFTWARE ARCHITECTURE
BASIC SOFTWARE
EQUIPMENTMANAGEMENT
NAVIGATIONSENSORS
DISPLAYS ANDCONTROLS
WEAPONS
OTHERS
DATA BASE
MISSION DATA
WEAPONS DATA
EQUIPMENTDATA
HUD HANDLER
HUD MODING
HUD FORMATS
MFD HANDLER
MFD MODING
MFD FORMATS
DATA HANDLER
NAVIGATIONCOMPUTATIONS
WEAPONAIMING
COMPUTATIONS
STORESMANAGER
MODECONTROLLER SCHEDULER
THE OPERATIONAL FLIGHT SOFTWARE IS THE APPLICATION SOFTWARE RESIDENT IN THE AIRCRAFT MISSION COMPUTERS PERFORMING THE AVIONIC FUNCTIONS REQUIRED IN ORDER TO FULFILL THE MISSION REQUIREMENTS
2.2. Development Phases
OPERATIONAL FLIGHT SOFTWARE DEVELOPMENT
SOFTWAREFUNCTIONAL
REQUIREMENTS
SOFTWAREREQUIREMENTS
ANALYSISSOFTWARE
PRELIMINARYDESIGN
SOFTWAREDETAILED
DESIGN CODING ANDUNIT TESTING UNIT
INTEGRATIONAND TESTING
CSCIQUALIFICATION
TESTINGSOFTWAREREQUIREMENTS
ANALYSISSOFTWARE
PRELIMINARYDESIGN
SOFTWAREDETAILED
DESIGN CODING ANDUNIT TESTING UNIT
INTEGRATIONAND TESTING
CSCIQUALIFICATION
TESTING
CSCI/HWCIINTEGRATIONAND TESTING
SYSTEMFINAL
DESIGNREVIEW
SOFTWARESPECIFICATION
REVIEW
PRELIMINARYDESIGNREVIEW
CRITICALDESIGNREVIEW
SOFTWARETEST
READINESSREVIEW
SYSTEMTEST
READINESSREVIEW
SOFTWAREREQUIREMENTSSPECIFICATION
INTERFACEREQUIREMENTSSPECIFICATION
SOFTWAREARCHITECTURE
SOFTWAREDESIGN
DESCRIPTION
INTERFACEDESIGN
DESCRIPTION
DATA BASEDESIGN
DESCRIPTION
SYSTEMQUALIFICATION
TESTING
SOFTWARETEST
DESCRIPTION
SOFTWARETEST
REPORT
SOFTWARETEST
DESCRIPTION
SOFTWARETEST
REPORT
CSCI = COMPUTER SOFTWARE CONFIGURATION ITEM
HWCI = HARDWARE CONFIGURATION ITEM
2.2. Development Phases
DEVELOPMENT OF INTEGRATION AND TESTING FACILITIES
THE INTEGRATION AND TESTING ACTIVITIES AT SYSTEM/SUBSYSTEM LEVELS REQUIRE COMPLEX FACILITIES, CAPABLE OF SUPPORTING THE SYSTEM INTEGRATION AND TESTING ACCORDING TO THE HARDWARE IN THE LOOP METHODOLOGY WITH PILOT INTERACTION IN A REPRESENTATIVE ENVIRONMENT
THE TECHNICAL CHARACTERISTICS OF THE INTEGRATION AND TESTING FACILITIES ARE STRONGLYRELATED TO:
A) THE SPECIFIC AIRCRAFT CHARACTERISTICSB) THE SPECIFIC AVIONIC SYSTEM ARCHITECTURE AND CONFIGURATIONC) THE SPECIFIC EQUIPMENT HARDWARE
THE REALIZATION OF THE INTEGRATION AND TESTING FACILITIES REQUIRES SPECIFIC DESIGN AND DEVELOPMENT
2.2. Development Phases
SYSTEM INTEGRATION AND TESTING
THE SCOPE OF THE INTEGRATION AND TESTING ACTIVITIES IS TO VERIFY THAT THE FUNCTIONS AND PERFORMANCE OF THE INTEGRATED AVIONIC SYSTEM COMPLY WITH THE REQUIREMENTS OF THE AVIONIC SYSTEM SPECIFICATION
STATIC TESTS
- ELECTRICAL INTEGRATION
- STATIC STIMULATION OF EQUIPMENT, IN ORDER TO VERIFY CORRECT STATIC OPERATION
- MODIFICATION OF SELECTED PARAMETERS
- INJECTION OF ERROR CONDITIONS
- VERIFICATION OF DIGITAL, DISCRETE AND ANALOG EQUIPMENT INTERFACES
2.2. Development Phases
SYSTEM INTEGRATION AND TESTING
DYNAMIC TESTS
THE DYNAMIC TESTS ALLOW THE VERIFICATION OF THE GLOBAL SYSTEM FUNCTIONS AND PERFORMANCES, OPERATING IN DYNAMIC CONDITIONS IN A REPRESENTATIVE ENVIRONMENT
OPEN LOOP DYNAMIC SIMULATIONTHE INTEGRATED SYSTEM IS STIMULATED BY COMPUTER GENERATED SIGNALS, ACCORDING TO PREDEFINED MATHEMATICAL MODELS
CLOSED LOOP DYNAMIC SIMULATION
THE INTEGRATED SYSTEM IS STIMULATED BY AN AIRCRAFT SIX DEGREES OF FREEDOM MATHEMATICAL MODEL,CONTROLLED BY PILOT COMMANDS.
THE CLOSED LOOP SIMULATION RUNS ACCORDING TO THE FOLLOWING OPERATIONAL MODES:
A) CLOSED LOOP SIMULATION WITH PILOT IN THE LOOP
THE LOOP IS CLOSED BY THE ACION OF THE PILOT/OPERATOR WITHIN THE MANEUVERS LIMITATIONSIMPOSED BY THE AIRCRAFT OPERATIONAL FLIGHT ENVELOPE
B) CLOSED LOOP SIMULATION WITH SIMULATED PILOT (DETERMINISTIC TESTS)
A MATHEMATICAL MODEL GENERATES A PREDEFINED FLIGHT PATH. THIS MODE ALLOWS TESTS REPEATABILITY.
2.2. Development Phases
GROUND TESTS
THE SCOPE OF THE GROUND TESTING ACTIVITIES IS TO VERIFY THE CORRECT INTEGRATION OF THEAVIONIC SYSTEM ON THE AIRCRAFT IN TERMS OF:
A) MECHANICAL, ELECTRICAL AND FUNCTIONAL INTERFACESB) COMPATIBILITY WITH OTHERS AIRCRAFT SYSTEMS.
POST INSTALLATION TESTING
- VERIFICATION OF THE AVIONIC SYSTEM FUNCTIONALITY WHEN INSTALLED ON THE AIRCRAFT
- VERIFICATION OF AVIONIC SYSTEM INTERFACES WITH OTHERS AIRCRAFT SYSTEMS
- USUALLY PERFORMED BY USING SPECIFIC TEST SOFTWARE PACKAGES
- PERFORMED ON ALL AIRCRAFTS
2.2. Development Phases
GROUND TESTS
ANTENNA TESTING
- VERIFICATION OF CORRECT OPERATION OF TRANSMITTING AND RECEIVING ANTENNAS ASSOCIATED TO AVIONIC EQUIPMENT
- ANTENNAS RADIATION PATTERNS ARE MEASURED WITH EXTENSIVE LABORATORY TESTING ON SCALED MODELS INANECHOIC CHAMBERS. ADDITIONAL TESTS ON PROTOTYPES AIRCRAFTS.
HAZARD FROM ELECTROMAGNETIC RADIATION TO ORDNANCE (HERO) TESTING
- VERIFICATION OF IMPACTS ON AIRCRAFT SYSTEMS RESULTING FROM EXTERNAL ELECTROMAGNETIC EMISSIONS
ELECTROMAGNETIC COMPATIBILITY TESTING
- VERIFICATION OF MUTUAL COMPATIBILITY OF AVIONIC EQUIPMENT AMONG THEMSELVES FOR ELECTROMAGNETICRADIATED AND CONDUCTED EMISSIONS
- VERIFICATION OF COMPATIBILITY OF AVIONIC EQUIPMENT WITH OTHERS AIRCRAFT SYSTEMS FOR ELECTROMAGNETICRADIATED AND CONDUCTED EMISSIONS
- BASICALLY PERFORMED ON PROTOTYPES AIRCRAFTS
2.2. Development Phases
FLIGHT TESTS
THE SCOPES OF THE FLIGHT TESTING ACTIVITIES ARE:
A) PERFORM THE FINAL INTEGRATION OF THE AVIONIC SYSTEM ON THE AIRCRAFT IN THE ACTUAL OPERATING CONDITIONS
B) DEMONSTRATE THAT THE AVIONIC SYSTEM COMPLIES WITH THE OPERATIONAL REQUIREMENTS
THE FINAL INTEGRATION OF THE AVIONIC SYSTEM ON THE AIRCRAFT REQUIRES EXTENSIVE FLIGHT CHAMPAINS ON PROTOTYPESAIRCRAFTS, IN ORDER TO COVER THE FOLLOWING MAIN ASPECTS:
A) ENVIRONMENT: VIBRATION, TEMPERATURE, ALTITUDE, HUMIDITY, ETC.B) COOLING: AIR FLOW, AIR TEMPERATURE AND PRESSURE, ETC.C) POWER SUPPLY: AIRCRAFT POWER SUPPLY CHARACTERISTICS, NORMAL AND ABNORMAL CONDITIONS, TRANSIENTS, ETC.D) ELECTROMAGNETIC COMPATIBILITY: RADIATED AND CONDUCTED EMISSIONS, COMPATIBILITY BETWEEN TRANSMITTING
AND RECEIVING EQUIPMENT, ETC.E) FUNCTIONALITY: FINAL VERIFICATION OF THE AVIONIC SYSTEM FUNCTIONALITY.
ACTUAL AIRCRAFT OPERATING CONDITIONS
2.2. Development Phases
FLIGHT TESTS
OPERATIONAL FUNCTIONS AND PERFORMANCE
DEMONSTRATION OF THE COMPLIANCE TO THE OPERATIONAL REQUIREMENTS FOR:
A) OPERATIONAL FUNCTIONS: NAVIGATION, WEAPON AIMING, COMMUNICATIONS, STORES MANAGEMENT, SELF PROTECTION, ETC.
B) OPERATIONAL PERFORMANCE: NAVIGATION ACCURACY, TARGET DETECTION RANGE AND ACCURACY, WEAPON AIMING ACCURACY, WEAPON DELIVERY ACCURACY, COMMUNICATIONS RANGE AND COVERAGE, THREAT DETECTION RANGE AND COVERAGE, ETC.
MAN/MACHINE INTERFACE
DEMONSTRATION OF THE COMPLIANCE TO THE OPERATIONAL REQUIREMENTS FOR:
A) OPERATIONAL PROCEDURES: SYSTEM MODING, SUBSYSTEM MODING, EQUIPMENT OPERATION AND CONTROL, ETC.
B) DISPLAYS FORMATS AND SYMBOLOGY: HEAD UP DISPLAY, HEAD DOWN MULTIFUNCTION DISPLAYS, CONTROL AND DISPLAY UNITS, DEDICATED PANELS, ETC.
C) ALL ERGONOMIC ASPECTS
2.2. Development Phases
FLIGHT TESTS
FLIGHT TEST INSTRUMENTATION
FLIGHT TEST INSTRUMENTATION (FTI) IS INSTALLED ON BOARD OF PROTOTYPES AIRCRAFTS FOR DATA COLLECTION, COMPRESSION AND RECORDING FOR POST FLIGHT ANALYSIS AND EVALUATION.
RECORDED DATA INCLUDE:
A) FLIGHT AND NAVIGATION DATA: AIRCRAFT ATTITUDE, ALTITUDE, SPEED, POSITION, ETC.B) ENVIRONMENTAL DATA: VIBRATION, TEMPERATURE, ETC.C) EQUIPMENT INPUT/OUTPUT DATA: DIGITAL, DISCRETES, ANALOGS, ETC..
FLIGHT BACK UP ACTIVITIES
THE FLIGHT TESTS ARE SUPPORTED BY PARALLEL FLIGHT BACK UP ACTIVITIES PERFORMED ON THE INTEGRATION ANDTESTING FACILITIES.
THIS ALLOWS TO:
A) REPRODUCE RECORDED SITUATIONS, IN ORDER TO ANALYZE AND EVALUATE THE MALFUNCTIONS DETECTED DURING THE FLIGHTS
B) IDENTIFICATION AND TEST OF CORRECTIVE ACTIONS FOR THE MALFUNCTIONS DETECTED DURING THE FLIGHTS.
2.2. Development Phases
3. AVIONIC SYSTEM DEVELOPMENT METHODS AND TOOLS
3.1. Concurrent Engineering
3.1.1. Definition3.1.2. System Design and Analysis3.1.3. Interactive Simulation3.1.4. System Verification
3.2. Operational Software Development Facilities
3.2.1. Software Design, Coding and Testing3.2.2. Software Verification
3.3. System Integration and Testing Facilities
3.3.1. Integration Rigs3.3.2. Antenna Testing3.3.3. Electromagnetic Compatibility Testing3.3.4. HERO Testing
3.4. Modeling and Simulation Tools
3.4.1. Modeling and Simulation Tools for the System Architectural Design3.4.2. Reconfigurable Simulators3.4.3. Mission Simulators3.4.4. Software Modeling and Automatic Code Generation3.4.5. Distributed Interactive Simulation
3.5. Rapid Prototyping Tools for the HMI Design
GENERAL
COMPUTERIZED DESIGN AIDS
- SIMULATION METHODS
- MATHEMATICAL PROGRAMMING METHODS
- STATISTICAL TOOLS
- DATA BASE MANAGEMENT MODELS
- SPECIALIZED ENGINEERING TOOLS
- PROJECT MANAGEMENT AIDS
3.1. Concurrent Engineering
3.1. Concurrent Engineering
TimeRequirements-Analysis
SystemsAnalysis &
Design
HW/SWDesign
HW/SWImplementation
ModuleIntegration & Test
SystemIntegration & Test
System Acceptance
System Engineers
Test Engineers
Mechanical Engineers
Software Engineers
Electrical Engineers
THE SYSTEM DEVELOPMENT PROCESS
3.1. Concurrent Engineering
Time
System Engineers
Test Engineers
Electrical Engineers
Software Engineers
Mechanical Engineers
Requirements-Analysis
SystemsDesign & Analysis
HW/SWDesign
HW/SWImplementation
ModuleIntegration & Test
SystemIntegration & Test
System Acceptance
System Engineers
Test Engineers
Mechanical Engineers
Software Engineers
Electrical Engineers
Time
IMPROVING THE SYSTEM DEVELOPMENT PROCESS
DISTRIBUTED SYSTEMS ENGINEERING
DISTRIBUTEDSYSTEMS
ENGINEERING
SYSTEMDESIGN
PROJECTREVIEWS
ENGINEERINGANALYSIS
TESTPREPARATION
AND EXECUTION
SIMULATIONS
DISTRIBUTED SYSTEM DESIGN AND ANALYSISDISTRIBUTION AND COLLABORATIVE EVALUATION OF ANALYSIS AND SIMULATION RESULTS
DISTRIBUTED DESIGN REVIEWS
CONSOLIDATION OF THE SYSTEM DESIGN IN A DISTRIBUTED REVIEW TEAM
DISTRIBUTED SYSTEM VERIFICATIONSUPPORT TO PREPARATION, EXECUTION AND EVALUATION OF SYSTEM TESTS
3.1. Concurrent Engineering
OPERATIONAL FLIGHT SOFTWARE DEVELOPMENT FACILITY
- INCLUDES A SET OF SOFTWARE TOOLS COVERING ALL PHASES OF THE DEVELOPMENT PROCESS
- INCLUDES A HOST SYSTEM WITH A SUFFICIENT NUMBER OF WORK PLACES TO SUPPORT THE DEVELOPMENT EFFORT
- SUPPORTS THE ENTIRE SOFTWARE LIFE CYCLE IN ACCORDANCE WITH THE APPLICABLE MILITARY STANDARDS(MIL STD 498 MILITARY STANDARD SOFTWARE DEVELOPMENT AND DOCUMENTATION)
GRAPHIC SOFTWARE DEVELOPMENT FACILITY
- DEFINES, DEVELOPS AND MAINTAINS THE FORMATS AND SYMBOLOGY OF THE HEAD UP DISPLAY AND OF THE HEAD DOWNMULTIFUNCTION DISPLAYS
- ALLOWS RAPID PROROTYPING OF DISPLAYS FORMATS AND SYMBOLOGY ON HOST COMPUTER
- ALLOWS AUTOMATIC CODE GENERATION FOR TARGET COMPUTER
SOFTWARE VERIFICATION STATION
- SUPPORTS THE HARDWARE/SOFTWARE INTEGRATION OF THE OPERATIONAL FLIGHT SOFTWARE IN A REPRESENTATIVEENVIRONMENT
- ALLOWS THE VERIFICATION OF THE OPERATIONAL FLIGHT SOFTWARE FUNCTIONALITY IN A SIMULATED DYNAMICENVIRONMENT, INCLUDING AIRCRAFT AND AVIONIC EQUIPMENT SIMULATORS
3.2. Operational Software Development Facilities
- ALLOWS TO TEST AND EVALUATE THE INTEGRATED AVIONIC SYSTEM FUNCTIONS, PERFORMANCE ANDINTEGRATION ASPECTS
- SUPPORTS THE VALIDATION OF THE OPERATIONAL FLIGHT SOFTWARE BEFORE FLIGHT
- SUPPORTS THE FINAL TESTING OF THE INTEGRATED SYSTEM BEFORE FLIGHT AND THE PREPARATIONOF THE FLIGHT RELEASE DOCUMENTS
- SUPPORTS THE AVIONIC SYSTEM INTEGRATION AND TESTING ACTIVITIES ON GROUND ACCORDINGTO THE HARDWARE IN THE LOOP AND PILOT IN THE LOOP CONCEPTS
- PROVIDES AN EFFECTIVE MEAN OF TRAINING PILOTS ON THE USE OF THE AVIONICS AND ON THERELATED FLIGHT AND ATTACK PROCEDURES
FUNCTIONS OF AN AVIONICS INTEGRATION RIG
AN AVIONICS INTEGRATION RIG CAN BE EXPANDED TO PROVIDE AN OVERALL MISSION SIMULATION CAPABILITY IN A COMPLEX TACTICAL SCENARIO
3.3. System Integration and Testing Facilities
COCKPIT MOCK UP
EQUIPMENT BENCH
OPERATIONAL ENVIRONMENTSIMULATOR
AIRCRAFT SIMULATOR
DATA ACQUISITION ANDSTIMULATION SYSTEM
IMAGE GENERATOR
TERRAIN DATA BASETACTICAL SCENARIO SIMULATOR
GRAPHICS CONTROL
STRUCTURE SIMULATION SYSTEM
PROJECTION SYSTEM
SCREEN
STRUCTUREWIRING
POWER SUPPLYPROJECTOR
STRUCTUREWIRING
POWER SUPPLY
STRUCTUREWIRING
POWER SUPPLY
AVIONICEQUIPMENT
NON AVIONICEQUIPMENT
DYNAMICS/BASIC SENSORSAVIONIC EQUIPMENT SIMULATORS
INTERFACE WITH REAL EQUIPMENTDATA ACQUISITION AND STIMULATION
SOFTWARE SERVICES
NON AVIONIC EQUIPMENT SIMULATORS
DISCRETES
ANALOGS
DISCRETES
ANALOGS
LAN
LAN
DIGITAL
DISCRETES ANALOGS
REAL DISPLAYSAND INDICATORS
REAL CONTROLS
AVIONICS INTEGRATION RIG CONFIGURATION
3.3. System Integration and Testing Facilities
3.3. System Integration and Testing Facilities
ANTENNA TESTING
The design of airborne antennas and their location on the aircraft are essential for the overall system performance. The radiation patterns of the antennas can be significantlyaffected by the aircraft structure. Interference problems can also occur from couplingfrom an onboard transmitting antenna to a receiving antenna. Extensive testing activitiesmust therefore be carried out to ensure the desired installed performance.
Computational antenna modelling on structures
Measurements on subscale models of the airframe
Full scale ground measurementsOperational flight testing to verify properinstallation, functional performance and electromagnetic compatibility with the aircraft systems
OVERVIEW
HW / SW Design
SystemAcceptance
System Integration & Test
Module Integration & Test
Requirements Analysis
SystemsAnalysis &
Design
Test Scenarios
Test Scenarios
Test Scenarios
HW / SWImplementation
& Unit Test
MODELING AND SIMULATIONTOOLS FOR
SYSTEM DESIGN
SOFTWARE MODELINGAUTOMATIC CODE GENERATORS
INTEGRATION RIGSMISSION SIMULATORS
RECONFIGURABLE SIMULATORSMISSION SIMULATORS
3.4. Modeling and Simulation Tools
3.4. Modeling and Simulation Tools
SYSTEM DEVELOPMENT PROBLEMS
- Systems today are becoming more and more complex.
- Static documentation is insufficient for describing dynamic behavior.
- Functional groups have a lack of communication.- System requirements can be misinterpreted.
- Individuals interpret requirements differently.- Missing requirements.- Ambiguous requirements.- Conflicting requirements.
System Development Time
Cost
($$) of
Err
ors
3.4. Modeling and Simulation Tools
SystemAcceptance
System Integration & Test
Module Integration & Test
Requirements Analysis
Requirements Models(Use Cases)
System Modification
System - / Performance - Model
TEST/PARAMETER-DATABASE
Test Scenarios Test Scenarios
HW / SWImplementation
& Unit Test
HW / SW Design
SystemsAnalysis &
Design
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
SystemFunctional
Design
RequirementsDocument
System Requirements
Document
Subsystem Design *HW/SW Requirements
SpecificationDocument
* Concurrent Engineering Task
SubsystemFunctionalDesign *
HW Design & Build SW Design & Implementation
Subsystem Requirements
Document
Links providing Traceabilityto original Requirements
Test Scenarios /Test Vectors
Test/ParameterDatabase
Executable Use Case Models
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
- Requirements Model
- Analyze each requirement and derive new system requirements.- Develop use-case models of the requirements.
- Functional Model
- Build and validate a functional description of the entire system.- Concerned with functional decomposition of a system, building a complete definition of the
system interfaces, and behavioral descriptions of the functions.- Functional decomposition is modeled independent of the physical architecture.
- Executable specification to describe dynamic behaviour.
- System validation performed early in the design process.
- Early detection of design errors.
- Model based design.
- removes ambiguous requirements.- resolves conflicting requirements.
- Communication channels are opened.
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
TEST DATABASE
- Tests need to be defined at each stage of the development cycle.
- At every level of the systems hierarchy, before progressing to thenext level, the model should be tested to validate the systemrequirements.
- Stimuli and responses should be recorded and applied during eachphase of development.
- Tests recorded on the virtual system can be applied to the physicalsystem.
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
MODELING AND SIMULATION CONCEPT FOR SYSTEM DESIGN
GRAPHICAL MODELING AND
DESIGN
SIMULATION AND ANALYSIS
GENERATE CODE
VALIDATE AND DEBUG DESIGN
EXECUTABLE SPECIFICATIONS
PROTOTYPES
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
PI_Controller
Vehicle_Dynamics
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
User Interface View
Panel
TargetPilot
Use Case 1
UC_1_1_3 Select Weapon
UC_1_1_4 Perform prerelease calcsUC1_1_1 Process
and store TGT position data
UC1_1 TGT Acquisition
UC1_1_12 Groundstab LDP
to TGT
Use Case 1
Use Case View
Use
Cas
e D
iagr
am
Use Case Scenario View
Sequ
ence
Dia
gram
Time-continuous Behavioral View
Time-
cont
inuou
s Diag
ram
State-based Behavioral View
Statec
hart
Statemate
Functional / Architectural View
Activity Char
t
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
- System Design Automation Tool.
- Allows the user to:
- Graphically model a design.
- Uses a graphical modeling language.
- Perform system analysis.
- Allows early validation of the systems behavior and functionality.
- Create a rapid prototype of the system.
- C/Ada and VHDL/Verilog Code can be generated for a design.- Panels can be created as a user interface to your simulation.
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
FROM USE CASES TO SYSTEM DESIGN
Identify Use Cases (done in RQ Analysis)
Identify Subsystems
Assign Requirements (Use Cases) to Subsystems
Define Subsystem Interfaces
Synthesize High Level Architecture- Functional System Design- System-Level COTS Analysis
Refine Subsystems- HW / SW Partitioning
Hierarchy Level 0(Context-Diagram)
ExternalData Sink
External Data Source
Hierarchy Level 1 Top-Down
Hierarchy Level 2
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
ENCAPSULATION OF ACTIVITIES
Statechart
Activity Chart
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
Hierarchy Level -1
Hierarchy Level 0 and 1
Hierarchy Level 2
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
Mini-Spec Continuous Diagrams( VisSim )
Truthtables
C-Code:User written or
SE-Tool generated( Matrix_x, Simulink, )
Statemachines(Statechart)
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
Interactive SimulationGenerating Events and/or changing Conditions and Data manually via a Monitor Window or a Graphic User Interface
- Animation of Statecharts and Activity Charts - Play-back File (Simulation Control Language (SCL-) Format)- Trace-File (Output: Spread Sheet, Waveform Display)
SIMULATION MODES
Batch SimulationUsers may write their own Simulation Control Program (SCP) on the Basis of a recorded Playback File
Testbench Simulation
By defining a Statechart to be a Testbench this Chart will beinterpreted as a Concurrent State Machine to the entire System.
- Stimulation and Monitoring of the System via the Broadcasting Mechanism- Application: Test Program Generation, FMEA, linear Plant Models
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
3.4. Modeling and Simulation Tools
Aerospace Typical Applications
Avionics
Flight SurfacesPassenger
CabinSystems
Hybrid
DiscreteLogical
Behavior
Time/ContinuousControl Law
Behavior
MATRIXX/BetterState
Simulink/StateFlowStatemate MAGNUM/VisSim
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
Example Hybrid Systems
Discrete LogicSystems
Exterior Car LightingDigital Displays
Time-Continuous / Control Law Systems
Engine ControllerFlight Surfaces
Physical Systems
Hybrid SystemsAutopilot
TransmissionHVAC
3.4. Modeling and Simulation Tools
The essential concept behind model checking is to (mathematically) prove whether a given model (a set of system requirements or a simulation model) satisfies a certain specification property.
Define a formal model of the system that issubject to verification by creating a model of the system in a language that fits the model checker's input language.
MODELING AND SIMULATION TOOLS FOR THE SYSTEM ARCHITECTURAL DESIGN
Provide a particular system property thatshould be proved. In other words, a question aboutthe system's behavior is formulated that should beanswered by the model checker.
Invoke the model checking tool and receive a notification whether the given system property wasfulfilled or not. In case the system property couldnot be verified, a counterexample is generated tofinger-point to the source of error in the simulationmodel.
MODEL CHECKING
3.4. Modeling and Simulation Tools
RECONFIGURABLE SIMULATORS FOR THE SYSTEM DESIGN
RECONFIGURABLE SIMULATORS CAN BE USED IN THE SYSTEM DESIGN PHASE FOR EARLY PRELIMINARY ANALYSIS AND EVALUATION OF POSSIBLE DESIGN ALTERNATIVES IN A REPRESENTATIVE ENVIRONMENT
- FRONT PANEL GENERAL LAYOUT
- DISPLAYS FORMATS AND SYMBOLOGY
- SYSTEM/SUBSYSTEMS MODING
- AVIONICS CONTROL PROCEDURES
- FLIGHT AND MISSION PROCEDURES
- MAN/MACHINE INTERFACE PROCEDURAL ASPECTS
3.4. Modeling and Simulation Tools
MISSION SIMULATORS FOR THE SYSTEM DESIGN
3.4. Modeling and Simulation Tools
MISSION SIMULATORS FOR THE SYSTEM DESIGN
MISSION SIMULATORS CAN STRONGLY SUPPORT THE SYSTEM DESIGN BY PROVIDING AN EFFECTIVE MEAN FOR ANALYZING AND EVALUATING THE AVIONIC SYSTEM BEHAVIOUR IN AN EARLY STAGE OF THE DEVELOPMENT
MAIN AREAS OF UTILIZATION
- EARLY VERIFICATION OF THE AVIONIC SYSTEM FUNCTIONALITY AND PERFORMANCE
- EARLY VERIFICATION OF COMPLIANCE TO THE OPERATIONAL REQUIREMENTS IN A HIGHLYREPRESENTATIVE ENVIRONMENT
- EVALUATION OF THE MAN/MACHINE INTERFACE CHARACTERISTICS IN A HIGHLY REPRESENTATIVEENVIRONMENT
- DEFINITION AND EVALUATION OF FLIGHT AND MISSION PROCEDURES IN A HIGHLYREPRESENTATIVE TACTICAL SCENARIO
- EARLY VERIFICATION OF COMPLIANCE TO THE OPERATIONAL REQUIREMENTS WITH THE FINAL USER
3.4. Modeling and Simulation Tools
MISSION SIMULATOR FUNCTIONAL BLOCK DIAGRAM
TACTICALSCENARIO
SIMULATOR
VISUALSIMULATOR
AIRCRAFTSIMULATOR
PILOTINTERFACE
SENSORSSIMULATORS
AVIONICEQUIPMENT
SIMULATORS
REALAVIONIC
EQUIPMENTSOFTWARESERVICES
OPERATIONAL ENVIRONMENTSIMULATOR
AVIONIC SYSTEM
SCENARIO DATA
STATUS STATUS
COMMANDS
PROJECTIONSYSTEM
GRAPHICS
PLATFORMDATA
STATUS
COMMANDSAND CONTROLS
3.4. Modeling and Simulation Tools
MISSION SIMULATOR PHYSICAL CONFIGURATION
COCKPIT MOCK UP
OPERATIONAL ENVIRONMENTSIMULATOR
AIRCRAFT SIMULATOR
DATA ACQUISITION ANDSTIMULATION SYSTEM
IMAGE GENERATOR
TERRAIN DATA BASETACTICAL SCENARIO SIMULATOR
GRAPHICS CONTROL
STRUCTURE
SIMULATION SYSTEM
PROJECTION SYSTEM
SCREEN
STRUCTUREWIRING
POWER SUPPLYPROJECTOR
STRUCTUREWIRING
POWER SUPPLY
DYNAMICS/BASIC SENSORSAVIONIC EQUIPMENT SIMULATORS
DATA ACQUISITION AND STIMULATION
SOFTWARE SERVICES
NON AVIONIC EQUIPMENT SIMULATORS
DISCRETES
ANALOGS
LAN
LAN
DIGITAL
DISPLAYSINDICATORS
CONTROLS
3.4. Modeling and Simulation Tools
AIRCRAFT SIMULATOR
THE AIRCRAFT SIMULATOR IS A HIGH FIDELITY SIX DEGREES OF FREEDOM AERODYNAMIC MODEL SIMULATING IN REAL TIME THE FLIGHT CHARACTERISTICS AND HANDLING OF THE AIRCRAFT. IT ALSO SIMULATES SOME AIRCRAFT SYSTEMS AND EQUIPMENT.
3.4. Modeling and Simulation Tools
AIRCRAFT SIMULATOR MAIN SIMULATION MODELS
- AERODYNAMIC SYSTEM
- FLIGHT CONTROLS SYSTEM
- FLIGHT MANAGEMENT SYSTEM
- AUTOPILOT SYSTEM
- NAVIGATION SYSTEM
- AIR DATA SYSTEM
- AMBIENT SYSTEM
- WINDS SYSTEM
- ELECTRICAL SYSTEM
- HYDRAULIC SYSTEM
- ENGINE SYSTEM
- AUTOTHROTTLE SYSTEM
3.4. Modeling and Simulation Tools
THE TACTICAL SCENARIO SIMULATOR ALLOWS THE DEFINITION OF INTERACTIVE TACTICAL SCENARIOS WITHIN USER DEFINED SYNTHETIC ENVIRONMENTS. ONCE THE SCENARIOS ARE GENERATED, THE SIMULATOR RUNS THEM IN REAL TIME, ENABLING FREE PLAY PARTICIPATION MIXED IN WITH THE PREDEFINED ENTITY BEHAVIOR RULES.
TACTICAL SCENARIO SIMULATOR
3.4. Modeling and Simulation Tools
TERRAIN DATA BASE
3.4. Modeling and Simulation Tools
IMAGE GENERATOR
3.4. Modeling and Simulation Tools
DATA ACQUISITION AND STIMULATION SYSTEM
3.4. Modeling and Simulation Tools
ImplementationTesting
MechanisticDesign
DetailedDesign
CodingUnit
TestingIntegration
Testing
ValidationTesting
IterativePrototypes
DesignObject-oriented SW Engineering
System Modification
Kno
wle
dge
Bas
e
HW/SW RequirementsSpecification
Test Scenarios
RequirementsSpecification
Function drivenSystems Engineering
RequirementsCapture & Analysis
A-D-I-T Cycles
SystemsAnalysis & Design
A-D-I-T Cycles
SystemAcceptance
Test Scenarios
SOFTWARE MODELING AND AUTOMATIC CODE GENERATION
3.4. Modeling and Simulation Tools
+TypePP_DATA PP_DATA
+setPP_DATA(TypePP_DATA iPP_DATA)
CALC_AVG_SIGMA
+ACQ_DATA : OMBoolean
+setACQ_DATA(OMBoolean iACQ_DATA)+RESTART_ACQ()
DATA_ACQUISITION
+PB_ON_OFF : OMBoolean+PB_DISP : int
+setPB_ON_OFF(OMBoolean iPB_ON_OFF)+setPB_DISP(int iPB_DISP)
SIGNAL_GENERATOR
+A_DAT : double
+setA_DAT(double iA_DAT)+SEND_PP_DATA()
PRE_PROCESSING
+DISP_REQUEST : OMString+AV_VAL : double+SIGMA : double
+setDISP_REQUEST(OMString iDISP_REQUEST)+setAV_VAL(double iAV_VAL)+setSIGMA(double iSIGMA)
DATA_EVALUATION
DISPLAY
1
1
1 1
1
1
1
1
1
1
1
EXAMPLE OF SOFTWARE MODELING OBJECT MODEL DIAGRAM
3.4. Modeling and Simulation Tools
Transition labels = Notes
EXAMPLE OF SOFTWARE MODELING STATECHARTS
3.4. Modeling and Simulation Tools
CODE GENERATION AND DEBUGGING
3.4. Modeling and Simulation Tools
DISTRIBUTED INTERACTIVE SIMULATION
DISTRIBUTED INTERACTIVE SIMULATION FACILITIES SUPPORT INTERACTION AND COLLABORATIVE WORKING BETWEEN GEOGRAPHICALLY DISTRIBUTED FACILITIES FOR NUMERICAL SIMULATION AND REAL TIME SIMULATION, INCLUDING HARDAWARE IN THE LOOP AND/OR MAN IN THE LOOP
NETWORK
COMMUNICATIONS
SIMULATION ANDVIRTUAL REALITY
MIDDLEWARE
SUPERVISOR GROUPWARE
HARDWARE INTHE LOOP
MAN INTHE LOOP
NUMERICALMODELS
SUPERVISIONAND CONTROL
VIDEOCONFERENCE ANDCOLLABORATIVE WORKING
3.4. Modeling and Simulation Tools
DISTRIBUTED INTERACTIVE SIMULATION
ENGINEERING: COLLABORATIVE WORK BETWEEN DISTANT ENGINEERING TEAMS
SYSTEM VALIDATION: VALIDATION OF COMPLEX SYSTEMS WITH DISTRIBUTED TEST FACILITIES
TRAINING: TRAINING AND MISSION REHEARSAL USING REMOTE RESOURCES
RTIHLA-RTI
RTI RTI RTI
UserInteraction
DSI
Logger
DSI
RTI RTI
DSI
DSI
Tank Simulator
DSI
DSI
Aircraft Simulator
THE RAPID PROTOTYPING IN THE MAN/MACHINE INTERFACE DESIGN
ADVANCED TACTICAL FIGHTER COCKPIT LAYOUT TYPICAL HEAD DOWN DISPLAY FORMAT
3.5. Rapid Prototyping Tools for the HMI Design
THE RAPID PROTOTYPING IN THE MAN/MACHINE INTERFACE DESIGN
THE RAPID PROTOTYPING TOOLS ARE USED IN THE AEROSPACE INDUSTRY FOR DESIGNING, RAPID PROTOTYPING, TESTING AND DEPLOYING MAN/MACHINE INTERFACES. THEY ENABLE THE DEVELOPMENT OF DYNAMIC, INTERACTIVE, REAL TIME GRAPHICAL MAN/MACHINE INTERFACES FOR COMPLEX APPLICATIONS SUCH AS THE COCKPIT LAYOUTS AND THE DISPLAYS AND CONTROLS FORMATS AND SYMBOLOGY
RAPID DESIGN, GENERATION, TESTING AND DOCUMENTATION OF VIRTUAL MAN/MACHINE INTERFACE OBJECTS FOR MISSION CRITICAL, SAFETY CRITICAL AND SIMULATION APPLICATIONS
AUTOMATIC CODE GENERATION FOR THE DEVELOPMENT ENVIRONMENT
AUTOMATIC CODE GENERATION FOR REAL TIME EMBEDDED TARGET
AUTOMATIC GENERATION OF QUALIFIABLE SOURCE CODE WHICH IS COMPILED FOR THE DEVELOPMENT ENVIRONMENT AND FOR REAL TIME EMBEDDED TARGETS
3.5. Rapid Prototyping Tools for the HMI Design
4. QUALITY AND SAFETY ASPECTS
4.1. Quality Engineering
4.1.1. Total Quality Management4.1.2. Quality Systems, Standards and Specifications4.1.3. Product and Process Quality Assurance
4.2. System Configuration Control
4.2.1. Configuration Identification4.2.2. Configuration Change Control4.2.3. Software Configuration4.2.4. Configuration Audits
4.3. Development of Safety Critical Elements
4.3.1. Safety and Mission Critical Functions4.3.2. Safety Engineering4.3.3. Fault Tolerance Concept
TOTAL QUALITY MANAGEMENT: THE TOTAL INTEGRATED MANAGEMENT APPROACH THAT ADDRESSES SYSTEM/PRODUCT QUALITY DURING ALL PHASES OF THE LIFE CYCLE AND AT EACH LEVEL IN THE OVERALL SYSTEM HIERARCHY
- TOTAL CUSTOMER SATISFACTION
- CONTINUOUS IMPROVEMENT ON A DAY TO DAY BASIS APPLIED TO ENGINEERING, PRODUCTIONAND SUPPORT PROCESSES AND FUNCTIONS
- INDIVIDUAL UNDERSTANDING OF PROCESSES, EFFECTS OV VARIATION AND PROCESS CONTROL METHODS.INDIVIDUAL EMPLOYEES MUST BE KNOWLEDGEABLE OF VARIOUS PROCESSES AND THEIR INHERENTCHARACTERISTICS
- TOTAL ORGANIZATIONAL APPROACH, INVOLVING EVERY GROUP IN THE ORGANIZATION. INDIVIDUALEMPLOYEES MUST BE MOTIVATED AND SHOULD BE RECOGNIZED AS BEING KEY CONTRIBUTORS TOMEETING QUALITY OBJECTIVES
QUALITY ENGINEERING IS A PART OF THE SYSTEM ENGINEERING PROCESS
- QUALITY PLANNING: THE DEVELOPMENT OF A TOTAL QUALITY MANAGEMENT PLAN MUST BE ACCOMPLISHEDDURING CONCEPTUAL DESIGN AND UPDATED AS REQUIRED
- QUALITY IN DESIGN: SIMPLICITY, FLEXIBILITY, STANDARDIZATION, ROBUSTNESS
4.1. Quality Engineering
TOTAL QUALITY MANAGEMENT
4.1. Quality Engineering
A Quality System is an organizational structure with responsibilities, procedures, processes, and resources that implements a management function to determine and enforce quality principles. A Quality System encompasses Quality Assurance and Quality Control.
Quality Assurance
Quality Control
A management system for programming and coordinating the quality maintenanceand improvement efforts of the various groups in a design and/or manufacturing organization, so as to permit design and/or production in compliance withregulatory and customer requirements.
Conduct and direct supervision of the quality tasks (inspection of product) toensure that the quality requirements of the product are achieved.
QUALITY SYSTEMS, STANDARDS AND SPECIFICATIONS
4.1. Quality Engineering
QUALITY SYSTEMS, STANDARDS AND SPECIFICATIONS
Quality and reliability are critical values for the aerospace industry. In an environmentwhere the mistakes or failure of products or services can be fatal, the effectiveoperation of a quality management system plays an essential role in helping to reduce risks and provide a reliable framework for organizations to provide a product or service.
Quality management systems have been used in the aerospace industry for many years. Efforts by members of the aerospace industry to establish a single common qualitymanagement system resulted in AS9100, 9110, 9120. They are used and supported by the world's leading aerospace companies and also throughout their supply chain partnerships.
AS9100 - Quality Management System Requirements for Design and/or Manufacture of Aerospace Products
AS9110 - Quality Management System Requirements for MaintenanceOrganizations
AS9120 - Quality Management System Requirements for StockistDistributors
4.1. Quality Engineering
QUALITY SYSTEMS, STANDARDS AND SPECIFICATIONS
AS 9100 has been endorsed by all major Aerospace regulators, including:
Federal Aviation Administration (FAA) U.S. Department of Defense (DoD) National Aeronautics and Space
Administration (NASA).
The AS9100 is the quality management standard specifically written for the aerospace industry. Itprovides organizations with a comprehensive quality management system focused on areas direclyimpacting product safety and reliability.
Configuration managementRequires that management discipline be applied over the life cycle of a product to provide visibility and control of its functional and physical characteristics
DesignEnsures that design responsible organizations have a robust design process to meet safety and reliability requirements demanded by the Aerospace industry
PurchasingRequires effective controls over the organizations entire supply chain
Product RealizationEnsures that each phase of product realization, fromplanning procuring and manufacturing to shipment iscontrolled for delivery of product conforming to customerrequirements
Product Monitoring/MeasurementDefines requirements for product validation prior toshipment.
4.2. System Configuration Management
GENERAL
ONCE A CONFIGURATION BASELINE HAS BEEN ESTABLISHED, IT IS ESSENTIAL THAT ANY VARIATIONS OR CHANGES WITH RESPECT TO THAT BASELINE BE TIGHTLY CONTROLLED. THE PROCESS OF CONFIGURATION IDENTIFICATION, THE CONTROL OF CHANGES AND MAINTAINING THE INTEGRITY AND CONTINUITY OF DESIGN ARE ACOMPLISHED THROUGH THE CONFIGURATION MANAGEMENT
PRELIMINARYDESIGN
DETAILEDDESIGN
DEVELOPMENT PRODUCTION OPERATIONALUSE
FUNCTIONALBASELINE
ALLOCATEDBASELINE
PRODUCTBASELINE
UPDATED PRODUCTBASELINE
CLASS 1 CHANGESDESIGN CHANGES AFFECTING FORM AND/OR FIT AND/OR FUNCTION AND/OR ANY OTHER SYSTEM SPECIFICATION REQUIREMENT
CLASS 2 CHANGESDESIGN CHANGES RELATIVELY MINOR IN NATURE AND NOT AFFECTING THE SYSTEM SPECIFICATION REQUIREMENTS
CONFIGURATION CHANGE CONTROL
4.2. System Configuration Management
SOFTWARE CONFIGURATION
4.2. System Configuration Management
The Software Configuration Management (SCM) process identifies the functional and physicalattributes of software at various points in time, and performs systematic control of changes to the identified attributes for the purpose of maintaining software integrity and traceability throughout the software development life cycle.
It identifies four procedures that must be defined for each software project to ensure that a sound SCM process is implemented.
Configuration identification is the process of identifying the attributes that define every aspect of a configuration item. These attributes are recorded in configuration documentation and baselined. Baselining an attribute forces formal configuration change control processes to be effected in the eventthat these attributes are changed.
Configuration change control is a set of processes and approval stages required to change a configuration item's attributes and to re-baseline them.
Configuration status accounting is the ability to record and report on the configuration baselinesassociated with each configuration item at any moment of time.
Configuration audits are broken into functional and physical configuration audits. They occur eitherat delivery or at the moment of effecting the change. A functional configuration audit ensures thatfunctional and performance attributes of a configuration item are achieved, while a physicalconfiguration audit ensures that a configuration item is installed in accordance with the requirementsof its detailed design documentation.
- FLIGHT CONTROL SENSORS, PROCESSING AND DISPLAYS
- TERRAIN FOLLOWING/TERRAIN AVOIDANCE SENSORS ANDCONTROL
- STORES MANAGEMENT CRITICAL FUNCTIONS
EXAMPLE TACTICAL AIRCRAFTTYPICAL SAFETY/FLIGHT CRITICAL FUNCTIONS
EXAMPLE TACTICAL AIRCRAFTTYPICAL MISSION CRITICAL FUNCTIONS
- NAVIGATION SENSORS, PROCESSING AND DISPLAYS
- ATTACK SENSORS, PROCESSING AND DISPLAYS
- COMMUNICATIONS
- STORES MANAGEMENT NON CRITICAL FUNCTIONS
- TACTICAL SITUATION MANAGER
- ELECTRONIC WARFARE
SAFETY/FLIGHT CRITICAL FUNCTIONSFUNCTIONS WHICH ARE ESSENTIAL TO SAFE OPERATION OF THE AIRCRAFT. FAILURES TO THESE FUNCTIONS MIGHT LEAD TO A HAZARD FOR THE PILOT OR FOR THE AIRCRAFT.
SAFETY/FLIGHT CRITICAL FUNCTIONS MUST BE SUBJECT TO RIGOROUS FAULT TOLERANT AND INTEGRITY DESIGN PHILOSOPHIES.
MISSION CRITICAL FUNCTIONSFUNCTIONS WHICH RELATE DIRECTLY TO THE MISSION OF THE AIRCRAFT. FAILURES TO THESE FUNCTIONS MIGHT LEAD TO THE MISSION ABORT.A LOWER DEGREE OF FAULT TOLERANCE AND INTEGRITY CAN BE ACCEPTED FOR THE MISSION CRITICAL FUNCTIONS.
4.3. Development of Safety Critical Elements
SAFETY AND MISSION CRITICAL FUNCTIONS
SAFETY IS A SYSTEM DESIGN CHARACTERISTIC. IT IS ESSENTIAL THAT THE SAFETY REQUIREMENTS BE APPROPRIATELY INTEGRATED INTO THE OVERALL SYSTEM ENGINEERING PROCESS
SAFETY PROGRAM TASKS
- PROGRAM MANAGEMENT TASKS
- SYSTEM SAFETY PROGRAM PLAN
- REVIEW AND CONTROL OF SUPPLIERS/SUBCONTRACTORS
- SYSTEM SAFETY PROGRAM REVIEWS
- DESIGN AND ANALYSIS TASKS
- FAULT TREE ANALYSIS
- HAZARD ANALYSIS
- RISK ANALYSIS
- DATA COLLECTION, ANALYSIS, FEEDBACK AND CORRECTIVE ACTIONS
- TEST AND EVALUATION TASKS
- SAFETY TRAINING PROGRAM
- SAFETY TEST AND EVALUATION
4.3. Development of Safety Critical Elements
SAFETY ENGINEERING
THE CRITICAL SYSTEMS MUST BE DEVELOPED ACCORDING TO THE FAULT TOLERANCE CONCEPT. THE FAULT TOLERANCE IS THE ABILITY OF A SYSTEM TO PROVIDE ITS FUNCTION AND TO CONTINUE OPERATION AFTER ONE OR MORE FAULTS HAVE OCCURRED.
FAULT TOLERANCE TECHNIQUES
- FAULTS MUST BE DETECTED, IDENTIFIED AND ISOLATED- REDUNDANT SYSTEM RESOURCES MUST BE AVAILABLE AND BE RECONFIGURED
TO PROVIDE CONTINUING OPERATION- MONITORS, VOTERS AND SWITCHING MECHANISMS ARE REQUIRED TO RECOGNIZE
FAULTS AND TO PROVIDE RECONFIGURATION PATHS
- THE RECOVERY MECHANISMS MUST BE AUTONOMOUS, ALLOWING GRACEFULDEGRADATION
- ALL FAILURES THAT MIGHT LEAD TO A HAZARD MUST BE DETECTED
4.3. Development of Safety Critical Elements
FAULT TOLERANCE CONCEPT