Project 13: Embraer Cockpit Instrumentation For FAA

Project 13: Embraer Cockpit Project 13: Embraer Cockpit Instrumentation For FAAInstrumentation For FAA

Team MembersTeam Members

Project SummaryProject Summary

► The client is developing the The client is developing the flight dynamics for the flight dynamics for the Embraer 170/175 aircraft Embraer 170/175 aircraft using the open source Flight using the open source Flight Gear simulator. Gear simulator.

► They need graphics They need graphics software to simulate the software to simulate the functionality of the actual functionality of the actual cockpit by simulating the cockpit by simulating the gauges in the primary flight gauges in the primary flight display (PFD), navigation display (PFD), navigation display (NavDisplay), engine display (NavDisplay), engine instruments (EICAS) display. instruments (EICAS) display.

Sample Embraer PFD

Architecture – LogicalArchitecture – Logical► When our software When our software

executes, a user settings executes, a user settings file will be loaded into the file will be loaded into the system. The file contains system. The file contains font path, Flight Gear NAV font path, Flight Gear NAV Data path, and display Data path, and display settings.settings.

► Our software will use the Our software will use the setting to initialize the setting to initialize the graphics engine (window graphics engine (window size and NAV database) and size and NAV database) and launch the graphics loop.launch the graphics loop.

► The three displays will be The three displays will be rendered. All displays are rendered. All displays are rendered based on the user rendered based on the user settings and NAV Data. The settings and NAV Data. The NAV Data is updated every NAV Data is updated every 1/24 of a second.1/24 of a second.

Architecture - ProcessArchitecture - Process

► Our project involves two Our project involves two major processes: Main major processes: Main Embraer Display process Embraer Display process and Flight Gear Simulator and Flight Gear Simulator process.process.

► The Main Embraer Display The Main Embraer Display Process includes tasks such Process includes tasks such as rendering and parsing as rendering and parsing user setting and NAV data.user setting and NAV data.

► The Flight Gear Simulator The Flight Gear Simulator Process is used for user Process is used for user input (E.g. takeoff, landing, input (E.g. takeoff, landing, 360 degree spin, etc) so 360 degree spin, etc) so that the NAV data can be that the NAV data can be updated.updated.

Architecture - DevelopmentArchitecture - Development

► From the development From the development standpoint, our project standpoint, our project consists of three major consists of three major layers. layers.

► Layer 1 handles object Layer 1 handles object initializations, parsing initializations, parsing user setting file and user setting file and retrieve NAV Data.retrieve NAV Data.

► Layer 2 prepares Layer 2 prepares graphics settings and graphics settings and render window.render window.

► Layer 3 renders the Layer 3 renders the three displays.three displays.

Architecture - PhysicalArchitecture - Physical

► Our system can be run Our system can be run on two nodes.on two nodes.

► One node will be used One node will be used for our Embraer for our Embraer Instrumentation Instrumentation Process.Process.

► The Flight Gear The Flight Gear Simulator Process will Simulator Process will be run on a separate be run on a separate node since it’s an node since it’s an graphically intensive graphically intensive OpenGL application.OpenGL application.

Architecture – Sample Use Case Architecture – Sample Use Case ScenarioScenario

► John configured our John configured our application to run on 1024 x application to run on 1024 x 768 and set the Flight Gear 768 and set the Flight Gear NAV Data path.NAV Data path.

► John started up our application John started up our application and saw the three displays and saw the three displays rendered. However, the NAV rendered. However, the NAV data stayed the same.data stayed the same.

► John starts up Flight Gear John starts up Flight Gear Flight Simulator. He took off, Flight Simulator. He took off, set speed at 350 MPH, and set speed at 350 MPH, and turn left 90 degrees.turn left 90 degrees.

► The application receives the The application receives the updated NAV data and render updated NAV data and render the displays to reflect the the displays to reflect the updated speed and heading.updated speed and heading.Actual Embraer Cockpit

PrototypePrototype

Reuse of Critical ComponentsReuse of Critical Components

► In order of importanceIn order of importance PFD (Critical Component)PFD (Critical Component)

► Reusing examples from the OpenGC artificial horizon Reusing examples from the OpenGC artificial horizon exampleexample

► Reusing part of the OpenGC Nav. display as our Reusing part of the OpenGC Nav. display as our “compass” sub section in our PFD“compass” sub section in our PFD

Nav. DisplayNav. Display► Unfortunately will have to be done almost from scratch.Unfortunately will have to be done almost from scratch.

Engine DisplayEngine Display► Parts of the engine display can be reused from existing Parts of the engine display can be reused from existing

OpenGC engine display, but are cosmetically different.OpenGC engine display, but are cosmetically different.

PerformancePerformance

►Compiled under Visual Studio .NET 2003Compiled under Visual Studio .NET 2003►PFD display took 0.3 seconds to render PFD display took 0.3 seconds to render

on an Intel Pentium 4 processor 2.8 on an Intel Pentium 4 processor 2.8 MHZ with 512 MB of ram.MHZ with 512 MB of ram.

►Reused 60% of gauge components Reused 60% of gauge components within the original OpenGC project. within the original OpenGC project.

►Stable releases of external library Stable releases of external library components are in use.components are in use.

Design for SimplicityDesign for Simplicity

►Fonts manager, RenderWindow, Fonts manager, RenderWindow, AppObject, and parts of gauge AppObject, and parts of gauge components from OpenGC are reused or components from OpenGC are reused or slightly modified.slightly modified.

►Gauges use communicational cohesion, Gauges use communicational cohesion, which operate from the same data source.which operate from the same data source.

►Gauges also use data coupling, which is Gauges also use data coupling, which is only simple data being passed between only simple data being passed between modulesmodules

Design for MaintainabilityDesign for Maintainability

►Well-documented codeWell-documented code►External libraries are upgradeable External libraries are upgradeable

within he project environmentwithin he project environment►Low coupling between the PFD, NAV Low coupling between the PFD, NAV

display, and Engine display gaugesdisplay, and Engine display gauges► Informative error messages showing Informative error messages showing

which method fails.which method fails.

Design for TestabilityDesign for Testability

► Our system has convenient interfaces to drive the Our system has convenient interfaces to drive the execution and verification tests.execution and verification tests.

► Our system has been decomposed into components Our system has been decomposed into components for processing of successive refinements. for processing of successive refinements.

► We’ve considered a high-level conceptual model in We’ve considered a high-level conceptual model in terms components and their interaction for terms components and their interaction for developing a number of scenarios of anticipated developing a number of scenarios of anticipated changes and assessing the degree to which the changes and assessing the degree to which the architecture supports these changes, quality architecture supports these changes, quality aspects like maintainability and flexibility may be aspects like maintainability and flexibility may be tested at any early stage.tested at any early stage.

Design for ReliabilityDesign for Reliability

► Ideally we need to design to operate failure Ideally we need to design to operate failure free. To do so we need to make sure:free. To do so we need to make sure: We have accurate data input.We have accurate data input. Transform the data properly.Transform the data properly.

By examining the expected usage pattern of our By examining the expected usage pattern of our system, we can identify which areas of system, we can identify which areas of concentration are needed for debugging.concentration are needed for debugging.

We expect the mean time between failures to be We expect the mean time between failures to be less than 100 hours.less than 100 hours.

Complexity ChartComplexity Chart

Problem Problem Domain Domain

Architecture Architecture ComplexityComplexity

Logic Logic Design –Design –DataData

Logic Logic Design –Design –CodeCode

ComplexitComplexity (Total / y (Total / 18 ) * 18 ) * ( Type ( Type Factor )Factor )

Our Our ProjectProject

4 – Some 4 – Some calculations calculations are difficultare difficult

2 – Architecture 2 – Architecture follows an follows an existing existing pattern. pattern. Process design Process design is is straightforward. straightforward. No HW/SW No HW/SW interfaces. interfaces.

2 – Several 2 – Several data element data element types have types have straightforwastraightforward rd relationships. relationships. No object No object classes have classes have inheritance inheritance greater than greater than 3.3.

3 – Well-3 – Well-structured structured small small modules with modules with low coupling. low coupling. Object Object classes classes methods well methods well focused and focused and generalized. generalized.

( 11 / 18 ) * ( ( 11 / 18 ) * ( 10 ) = 6.110 ) = 6.1

Estimated SLOC ModelsEstimated SLOC Models

Using the COCOMO II method developed at Using the COCOMO II method developed at University of Southern California: Center for University of Southern California: Center for Computer Software Engineering Computer Software Engineering

► Top Down ApproachTop Down Approach► Function PointFunction Point► Internet PointInternet Point► Feature PointFeature Point► Capability RequirementCapability Requirement

Labor Rates UsedLabor Rates Used

► Strategist: $23.97Strategist: $23.97► Analyst: $17.05Analyst: $17.05► Designer: $14.38Designer: $14.38► Programmer: Programmer:

$18.82$18.82

► Test/QA: $18.00Test/QA: $18.00► Copywriter: $15.09Copywriter: $15.09► Art/Media: $17.63Art/Media: $17.63► Management: Management:

$24.00$24.00

From the Educational Development From the Educational Development Department of California Avr. Salary Per Department of California Avr. Salary Per HourHour

(Aprox. for Test/QA and Management)(Aprox. for Test/QA and Management)

Schedule by MethodSchedule by Method

Cost by EstimationCost by Estimation

Given the Avr. Cost ExpectedGiven the Avr. Cost Expected

Labor Category Breakdown by Labor Category Breakdown by PhasePhase

Support CallsSupport Calls

Function PointsFunction Points► Calculation:Calculation:► # input types# input types > 1> 1► # output types# output types > 2> 2► # inquiry types# inquiry types > 1> 1► # logical internal files# logical internal files > 1> 1► # interfaces# interfaces > 2> 2► UFP = 4I + 5O + 4E + 10L + 7FUFP = 4I + 5O + 4E + 10L + 7F►

► = 42= 42 (Originally 49)(Originally 49)► DI = I + O + E + L + FDI = I + O + E + L + F► = 7= 7► TCF = 0.65 + 0.01DITCF = 0.65 + 0.01DI► = 0.72= 0.72► FP = UFP x TCFFP = UFP x TCF► = 30.2 Function Points = 30.2 Function Points (Originally 35)(Originally 35)

COCOMO (1/2)COCOMO (1/2)

►Effort in staff months = b * Effort in staff months = b * KDLOCKDLOCcc

►b = 2.4 and c = 1.05; these are b = 2.4 and c = 1.05; these are constants determined by project size, constants determined by project size, innovation, deadline, and constraintsinnovation, deadline, and constraints

►KDLOC: thousands of lines of delivered KDLOC: thousands of lines of delivered source code (not including comments source code (not including comments or unmodified third party code)or unmodified third party code)

COCOMO (2/2)COCOMO (2/2)SIZE INNOVATION DEADLINE CONSTRAINTS

Organic Small Little Not tight Stable

Semi-detached Medium Medium Medium Medium

Embedded Large Greater Tight Complex hdw/customer interfaces

= 6 and 1/4 student months (based on re-evaluated approximation of 2500 lines)

B c

Organic 2.4 1.05

Semi-detached 3.0 1.12

Embedded 3.6 1.20

QFDQFDGoals/Features Interface with FlightGear

open source simulatorUtilize OpenGC glass

cockpit softwareModel a full 3D

cockpit

Provide an exact and realistic simulation of the physical cockpit

9 10 8 27

Ensure a low response time for instrumentation (representing physical situation of aircraft)

8 9 3 20

Allow for extensibility 9 9 4 23

26 28 15

ICED-TICED-T

► Intuitive: The Embraer designers dealt with the intuitiveness of the cockpit Intuitive: The Embraer designers dealt with the intuitiveness of the cockpit itself, but the virtual implementation must be able to match the intuitiveness itself, but the virtual implementation must be able to match the intuitiveness of the actual thing. of the actual thing.

► Consistent: It is highly important that the virtual cockpit be consistent with the Consistent: It is highly important that the virtual cockpit be consistent with the actual Embraer ERJ cockpit. However, the team was unable to obtain a actual Embraer ERJ cockpit. However, the team was unable to obtain a manual for the Honeywell Epic Display system. As a result, the project will be manual for the Honeywell Epic Display system. As a result, the project will be based on the Regional Jet Display demos at Project Magenta’s website and based on the Regional Jet Display demos at Project Magenta’s website and various pictures found on the internet.various pictures found on the internet.

► Efficient: Flow of information must be constant. Changing modes in displays Efficient: Flow of information must be constant. Changing modes in displays must take < one second.must take < one second.

► Durable: Inherently compromised since part of the total package employs Durable: Inherently compromised since part of the total package employs alpha and beta version software.alpha and beta version software.

► Thoughtful: Project is an implementation of an existing design, rather than an Thoughtful: Project is an implementation of an existing design, rather than an entirely new cockpit created from scratch. entirely new cockpit created from scratch.

Intuitive Consistent Efficient Durable Thoughtful

3 4 4 3 2

Current ScheduleCurrent Schedule

Milestones:

0.1 - PFD0.2 - NAV1.0 - EICAS

Any Questions?Any Questions?