Flight Simulation: A Case Study in an Architecture for Integrability.

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 3
Advertisements

PROVING FLIGHTS.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Chapter 15: Packaged Software and Enterprise Resource Planning
Object-Oriented Software Development CS 3331 Fall 2009.
Information Flow: Tactical Network Design and Bandwidth Management University XXI Texas A&M University University of Texas United States Army.
Target Markets: Segmentation and Evaluation
1 S ystems Analysis Laboratory Helsinki University of Technology A Simulation Model for Aircraft Maintenance in an Uncertain Operational Environment Ville.
Sense & Avoid for UAV Systems
- 1 - Component Based Development R&D SDM Theo Schouten.
Database Administration
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Simulation Exercises Overview Activities designed to assess, enhance and evaluate preparedness.
Software Engineering Tools and Methods Presented by: Mohammad Enamur Rashid( ) Mohammad Rashim Uddin( ) Masud Ur Rahman( )
Basic Challenges of Organizational Design
Development Processes and Organizations
Slide 1 Flight Simulation – Ch 8 A Case Study in an Architecture for “Integrability” Boeing 747 flight simulator in action – from
3- System modelling An architectural model presents an abstract view of the sub-systems making up a system May include major information flows between.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Target Markets: Segmentation and Evaluation
Chapter 1: Introduction to Systems Analysis and Design
Chapter 3 Network and System Design. Objectives After reading the chapter and reviewing the materials presented the students will be able to: Understand.
Slide 1Lesson 14: Fundamentals of the CAP Flying Safety Program Fundamentals of the CAP Flying Safety Program.
A haptic presentation of 3D objects in virtual reality for the visually disabled MSc Marcin Morański Professor Andrzej Materka Institute of Electronics,
Air Force Doctrine Document 2-1: Air Warfare
TEACHING WITH CONTRIVED EXPERIENCES
A haptic presentation of 3D objects in virtual reality for the visually disabled MSc Marcin Morański Professor Andrzej Materka Institute of Electronics,
Chapter 10 Information Systems Analysis and Design
ANTs PI Meeting, Nov. 29, 2000W. Zhang, Washington University1 Flexible Methods for Multi-agent distributed resource Allocation by Exploiting Phase Transitions.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
1 S ystems Analysis Laboratory Helsinki University of Technology A Simulation Model for Aircraft Maintenance in an Uncertain Operational Environment Ville.
Slide 1 CS 310 Software Engineering Professor C. Shilepsky Spring Chapter 1 u define software engineering.
* Motivation * The direction and intensity of effort * Direction of effort * Refers to whether an individual seeks out, approaches, or is attracted to.
Parallel and Distributed Simulation Introduction and Motivation.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Aerospace Engineering™ Overview. What is Project Lead the Way? Focus on learning through Rigor Relevance Retention Integration Motivation.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 1-1 Organizational Theory, Design, and Change Sixth Edition Gareth R. Jones Chapter.
4/25/2017 Reliability Chapter Ten Reliability Reliability.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Java Software Solutions Lewis and Loftus Chapter 15 Copyright 1997 by John Lewis and William Loftus. All rights reserved. 1 Software Development Process.
1 #*#* Transitioning Your Organization to an Object-Oriented Methodology.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Chapter 2: Development process and organizations
New Product Development Page 1 Teddy Concurrent Engineering by Teddy Sjafrizal.
Using Game to Transfer Knowledge CISSE 2009 Mazeyanti, Nazleeni, Mohd Izad1 Using Computer Game to Share Knowledge 1 Mazeyanti M Ariffin, 2 Nazleeni Samiha.
Software Engineering INTRODUCTION TO SOFTWARE DEVELOPMENT.
Chapter 1: Introduction Omar Meqdadi SE 3860 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Communications between Flight Deck and Line Maintenance The Critical Interface.
Week 7 Lecture Part 2 Introduction to Database Administration Samuel S. ConnSamuel S. Conn, Asst Professor.
Understand Systems Integration Chao-Hsien Chu, Ph.D. School of Information Sciences and Technology The Pennsylvania State University How Hierarchy Why.
Learning of Coordination of a Quad-Rotors Team for the Construction of Multiple Structures. Sérgio Ronaldo Barros dos Santos. Supervisor: Cairo Lúcio Nascimento.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
1 Alternative Designs for a Joint C4I Capability Certification Management (JC3M) System A Student Project Gregory A. Miller Naval Postgraduate School Monterey,
Introduction to Electronics Part 1 Stewart Watkiss.
Air Force Institute of Technology
Information Systems Development
2016 Student Astronaut Challenge Coach Training
CASE Tools and Joint and Rapid Application Development
Unit Commanders' Course
Embry-Riddle Aeronautical University
Organizational Effectiveness
Organizational Effectiveness
Chapter 2: Building a System
Presentation transcript:

Flight Simulation: A Case Study in an Architecture for Integrability

Chapter 8: Flight Simulation: Relationship to the Architecture Business Cycle8.1 Relationship to the Architecture Business Cycle 8.2 Requirements and Qualities8.2 Requirements and Qualities 8.3 Architectural Solution8.3 Architectural Solution 8.4 Summary8.4 Summary 8.5 For Further Reading8.5 For Further Reading 8.6 Discussion Questions8.6 Discussion Questions

Flight Simulation Cont.: The segment of the Architecture Business Cycle (ABC) that connects desired qualities to architecture is the focus of this case study. Figure 8.1 shows the ABC for Structural-Model-based flight simulators.Figure 8.1 The simulators discussed in this chapter are acquired by the U.S. Air Force. Their end users are pilots and crews for the particular aircraft being simulated. 3

Flight Simulation Cont. Flight simulators are used for pilot training in the operation of the aircraft, for crew training in the operation of the various weapons systems on board, and for mission training for particular missions for the aircraft. Some simulators are intended for standalone use, but more and more are intended to train multiple crews simultaneously for cooperative missions. 4

Initial stages of the ABC for the flight simulator 5

Flight Simulation Cont. The flight simulators are constructed by contractors selected as a result of a competitive bidding process. The simulator systems are large (some as large as 1.5 million lines of code), have long lifetimes (the aircraft being simulated often have lifetimes of 40 years or longer), and have stringent real- time and fidelity requirements (the simulated aircraft must behave exactly like the real aircraft in situations such as normal flight, emergency maneuvers, and equipment failures). 6

Flight Simulation Cont. The beginning of the Structural Model pattern dates from 1987 when the Air Force began to investigate the application of object-oriented design techniques. Electronic flight simulators had been in existence since the 1960s, and so this investigation was motivated by problems associated with the existing designs. 7

Flight Simulation Cont. These included construction problems (the integration phase of development was increasing exponentially with the size and complexity of the systems) and life-cycle problems (the cost of some modifications was exceeding the cost of the original system). 8

Flight Simulation Cont. The Structural Model pattern was able to overcome these problems, as we will see. It has been used in the development of the B-2 Weapons System Trainer, the C-17 Aircrew Training System, and the Special Operations Forces family of trainers, among others. 9