Slide 1 Flight Simulation – Ch 8 A Case Study in an Architecture for “Integrability” Boeing 747 flight simulator in action – from

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 2 4. Achieving Qualities.
Advertisements

Computer Systems & Architecture Lesson 3
Chapter 10 The Traditional Approach to Design
Towards Target-Level Testing and Debugging Tools For Embedded Software Harry Koehnemann, Arizona State University Dr. Timothy Lindquist, Arizona State.
MotoHawk Training Model-Based Design of Embedded Systems.
Technical department - boclair academy Computer Animation & Simulation Pentakis dodecahedron (60 faces)
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
 An object-oriented program’s structure often bears little resemblance to its code structure.  The code structure is frozen at compile-time; it consists.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Software Architecture Design Instructor: Dr. Jerry Gao.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Lecture 13 Revision IMS Systems Analysis and Design.
1 of 14 1/15 Schedulability Analysis and Optimization for the Synthesis of Multi-Cluster Distributed Embedded Systems Paul Pop, Petru Eles, Zebo Peng Embedded.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented design 2.
Ritu Varma Roshanak Roshandel Manu Prasanna
Scheduling with Optimized Communication for Time-Triggered Embedded Systems Slide 1 Scheduling with Optimized Communication for Time-Triggered Embedded.
Establishing the overall structure of a software system
Use Case Analysis – continued
CSC230 Software Design (Engineering)
System Design Decomposing the System. Sequence diagram changes UML 2.x specifications tells that Sequence diagrams now support if-conditions, loops and.
Copyright Arshi Khan1 System Programming Instructor Arshi Khan.
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
Client/Server Software Architectures Yonglei Tao.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Commerce, a.s., Bratislava
Chapter 10 Architectural Design
Flight Simulation: A Case Study in an Architecture for Integrability.
Your Logo 1 TREATMENT OF TIME IN A FLIGHT SIMULATOR In a real-time simulator, the most important resource to manage is time itself. A flight simulator.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 13Slide 1 Architectural Design u Establishing the overall structure of a software system.
Architectural Design portions ©Ian Sommerville 1995 Establishing the overall structure of a software system.
So What? Operations Management EMBA Summer TARGET You are, aspire to be, or need to communicate with an executive that does not have direct responsibility.
Architectural Design To explain the advantages and disadvantages of different distributed systems architectures To discuss client-server and distributed.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Styles.
SOFTWARE DESIGN.
1 Software Design Reference: Software Engineering, by Ian Sommerville, Ch. 12 & 13, 5 th edition and Ch. 10, 6 th edition.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
1 Software Design Overview Reference: Software Engineering, by Ian Sommerville, Ch. 12 & 13.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Software Engineering CSC 342/Dr. Ghazy Assassa Chapter 10, Architectural Design “Sommerville +.. “ Slide 1 CSC 342 Semester II: H ( G)
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
Distributed System Concepts and Architectures 2.3 Services Fall 2011 Student: Fan Bai
Conformance Test Experiments for Distributed Real-Time Systems Rachel Cardell-Oliver Complex Systems Group Department of Computer Science & Software Engineering.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 system architecture 1 after designing to meet functional requirements, design the system.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 13. Review Shared Data Software Architectures – Black board Style architecture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 11 Slide 1 Architectural Design.
Chapter 7: Architectural Design Chapter 11 in textbook 1.
CSC480 Software Engineering Lecture 10 September 25, 2002.
Lecture 18: Object-Oriented Design
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Applied Architectures, Part 2 Software Architecture Lecture.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
School of Aviation Application of Threat and Error Management Paul Kearney.
Introduction to Avionics Mac Mollison. What I Want to Talk About l What do we mean by “avionics”? l What is the focus of this course?
Slide 1 Chapter 8 Architectural Design. Slide 2 Topics covered l System structuring l Control models l Modular decomposition l Domain-specific architectures.
Embedded Real-Time Systems Processing interrupts Lecturer Department University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
Part 3 Design What does design mean in different fields?
Applied Architectures, Part 2
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
软件体系结构 过程调用体系结构 Call/Return Systems
Software Architecture
Half-Sync/Half-Async (HSHA) and Leader/Followers (LF) Patterns
Software testing and configuration : Embedded software testing
Utility-Function based Resource Allocation for Adaptable Applications in Dynamic, Distributed Real-Time Systems Presenter: David Fleeman {
Applied Architectures, Part 2
Design Yaodong Bi.
Use Case Analysis – continued
Presentation transcript:

Slide 1 Flight Simulation – Ch 8 A Case Study in an Architecture for “Integrability” Boeing 747 flight simulator in action – from boeing-747-flight-simulator-in-his-bedroom/. boeing-747-flight-simulator-in-his-bedroom/ Before software - the Wallingford Improved Flight Trainer, From

Slide 2 Coming Up Today… –Term paper - Intro –Ch 08 – Flight Simulation – this  Intro – see for example YouTube vids: qXJWkuY. qXJWkuY Thursday –Present outcomes for Project 2 –Turn in Thurs night (and HW 3 - Yikes!) “How to clean the Gherkin”

Slide 3 Overview Structural Model –Minimize modules N-Square charts Requirements and Qualities –Three roles –Lots of constraints Architectural Solution –Treatment of time (real- time)

Slide 4 Pattern - Structural Model Simplicity and similarity of the system’s substructures Decoupling of data- and control-passing strategies from computation Minimizing module types A small number of system-wide coordination strategies Transparency of design

Slide 5 Structural Model

Slide 6 Roles The Crew –The people being trained The Simulator Instructor –Monitors crew performance –Initiates training situations The Environment –Atmosphere, threats, weapons, other aircraft “Maybe that one’s not one of ours? Modern simulator from the outside.

Slide 7 Requirements and Qualities Real-time performance constraints Continuous development and modification –Maintains “verisimilitude” = realism, as the airplanes changed specs Large size and high complexity Developed in geographically distributed areas

Slide 8 Problems Expensive to debug, test, and modify –Increased cost of integration Unclear mapping between software structure and aircraft structure –Many coupling effects to be considered E.g., pilot moves the rudder and aileron controls, which move the control surfaces, which affects the aerodynamics and causes the aircraft to turn. –Performance “fidelity” is # 1 goal

Slide 9 Architectural Solution Treatment of Time Periodic time management –A fixed time quantum based on frame rate –Non-preemptive cycle scheduling – invokes each process for a fixed time quantum Event-based time management –“Interrupt” based –Adds new events into event queue –Does in order of soonest needed But all messages from a single source must be done in order! Mixed-time systems –The two above systems must interact

Slide 10 Architectural Solution, cntd Structural Model Architectural Pattern Executive –Handles the coordination issues Application –Handles computation of the simulation –Functions are implemented by subsystems

Slide 11 Modules Executive –Timeline Synchronizer –Periodic Sequencer –Event handler –Surrogate Connects air vehicle model to environment model Application –Subsystem controller –Controller children

Slide 12 Allocation of Functionality to controller children Based on OO modeling of the “objects” of the real airplane: Kinetics – the physics Aircraft systems – distribution of energy within the airframe Avionics – ancillary support Environment

Slide 13 Decomposition n-Square Charts –What “Partition 2” communicates with… Partition 1Inputs OutputsPartition 2Outputs Inputs Partition 3

Slide 14 Air Vehicle Model Domain An example… Kinetics GroupLoads Vehicle State Vector Vehicle Position Power Aircraft Systems Group Power Inertial StateLoadsAvionics Group Ownship Emissions Atmosphere, Terrain, and Weather Environment Emitter Data Environment Group

Slide 15 Summary How the architecture achieves… Performance –Executive with time budgets, and –Periodic scheduling strategy Integrability –All data and control pass through a subsystem controller as an intermediary –Each partition was restricted in inputs and outputs Modifiability –Few base module configurations for the designer and maintainer to understand

Slide 16 Questions?