meeting the challenges of ultra large large meeting the
play

Meeting the Challenges of Ultra- -Large Large- - Meeting the - PowerPoint PPT Presentation

Meeting the Challenges of Ultra- -Large Large- - Meeting the Challenges of Ultra Scale Systems via Model- -Driven Driven Scale Systems via Model Engineering Engineering February 2, 2007 February 2, 2007 Dr. Douglas C. Schmidt


  1. Meeting the Challenges of Ultra- -Large Large- - Meeting the Challenges of Ultra Scale Systems via Model- -Driven Driven Scale Systems via Model Engineering Engineering February 2, 2007 February 2, 2007 Dr. Douglas C. Schmidt d.schmidt@vanderbilt.edu www.dre.vanderbilt.edu/~schmidt Institute for Software Vanderbilt University Integrated Systems Nashville, Tennessee

  2. New Demands on Distributed Real-time & Embedded (DRE) Systems Key challenges in the problem space •Network-centric, dynamic, very large-scale “systems of systems” •Stringent simultaneous quality of service (QoS) demands •Highly diverse, complex, & increasingly integrated/autonomous application domains Key challenges in the solution space • Vast accidental & inherent complexities • Continuous evolution & change • Highly heterogeneous (& legacy constrained) platform, language, & tool environments Mapping & integrating problem artifacts & solution artifacts is hard

  3. Evolution of DRE Systems Development Technology Problems • Legacy DRE systems often tend to be: Air CLI • Stovepiped Frame Nav SM HUD CM • Proprietary AP SS7 FLIR IP • Brittle & non-adaptive GPS RX IFF TX • Expensive • Vulnerable Cyclic RTOS Exec Consequence: Small Mission-critical DRE systems changes to legacy have historically been built software often have directly atop hardware big (negative) impact • Tedious on DRE system QoS • Error-prone & maintenance • Costly over lifecycles

  4. Evolution of DRE Systems Development Technology Problems • Legacy DRE systems often tend to be: DRE DRE • Stovepiped Applications Applications • Proprietary Middleware Middleware Services Services • Brittle & non-adaptive Middleware Middleware • Expensive Operating Sys • Vulnerable Operating Sys & Protocols & Protocols Hardware & Hardware & Networks Networks •Middleware has effectively factored out Mission-critical DRE systems many reusable services from traditional historically have been built DRE application responsibility directly atop hardware • Tedious •Essential for product-line architectures • Error-prone •Middleware is no longer the primary DRE • Costly over lifecycles system performance bottleneck

  5. Overview of Component Middleware “Write Code That Reuses Code” • Components encapsulate application “business” logic •Components interact via ports • Provided interfaces , e.g.,facets … • Required connection points , e.g., receptacles • Event sinks & sources • Attributes … … • Containers provide portable execution … environment for components that Container have common operating requirements Container •Components/containers can also •Communicate via a middleware bus Middleware Bus and Replication Security Persistence Notification •Reuse common middleware services A/V Streaming Scheduling Load Balancing

  6. DOC Middleware for DRE Systems (1/2) Client Propagation & Server Declared Priority Models • CORBA is standard middleware • Real-time CORBA adds QoS to classic CORBA to control: 1. Processor Resources Static Scheduling Standard • Thread pools Service Synchonizers • Priority models Request • Portable priorities Buffering • Standard synchronizers • Static scheduling service Explicit Binding Thread Pools 2. Network Resources • Protocol policies Portable Priorities • Explicit binding 3. Memory Resources •Request buffering Protocol Properties •These capabilities address key DRE application development & QoS-enforcement challenges www.omg.org

  7. DOC Middleware for DRE Systems (2/2) • TAO is an open- source version of Real-time CORBA • >> 1,000,000 SLOC • 100+ person years of effort • Pioneered R&D on DRE middleware design & optimizations • TAO is basis for many middleware R&D efforts • Example of good synergy between researchers & practitioners www.dre.vanderbilt.edu/TAO/

  8. Applying TAO in Mission-Critical DRE Systems Organization Application Domain Boeing Aircraft mission & flight control computers SAIC Distributed interactive simulation (HLA/RTI) ATDesk Automated stock trading Raytheon Aircraft carrier & destroyer computing systems Cisco & Qualcomm Wireless/wireline network management Raytheon & Army Joint Tactical Terminal (JTT) Contact Systems Surface mounted “pick-and-place” systems Turkish Navy Shipboard resource management Krones Process automation & quality control Siemens Hot rolling mill control systems LMCO & Raytheon Dynamic shipboard resource management (DDG) CUSeeMe Monitor H.323 Servers Northrup-Grumman Airborne early warning & control (AWACS) JPL/NASA SOFIA telescope, Cassini space probe BAE Systems Joint Tactical Radio System (JTRS) www.dre.vanderbilt.edu/users.html

  9. Component Middleware for DRE Systems Event Dynamic & Static Multimedia Component Security Notifications Scheduling Streaming Implementation Definition Language Fault Tolerance & Load Balancing Component Deployment & Configuration Time/space Real-time Policies Optimizations & Mechanisms www.dre.vanderbilt.edu/

  10. DRE Systems: The Challenges Ahead •Limit to how much application functionality can be refactored into reusable COTS middleware •Middleware itself has become very Gigabit Gigabit Ethernet Ethernet RT-CORBA J2ME DRTSJ hard to use & provision statically & DRE Applications Apps Apps Apps dynamically Middleware Load Balancer RT-CORBA J2ME DRTSJ Workload & Services FT CORBA Replicas Services Services Services Connections & RT/DP CORBA + DRTSJ priority bands RTOS + RT Java Middleware CPU & memory RT-CORBA J2ME DRTSJ Network latency IntServ + Diffserv & bandwidth Operating System •Component-based DRE systems are & Protocols also very hard to deploy & configure •There are many middleware platform Hardware & Networks technologies to choose from Middleware alone is insufficient to solve key large-scale DRE system challenges!

  11. DRE Systems: The Challenges Ahead Gigabit Gigabit Ethernet Ethernet RT-CORBA J2ME DRTSJ DRE Applications Apps Apps Apps Middleware RT-CORBA J2ME DRTSJ Services Services Services Services Middleware RT-CORBA J2ME DRTSJ Operating System & Protocols Hardware & Networks It’s enough to make you scream!

  12. Technology Evolution (1/4) Programming Languages Model-Driven Engineering (MDE) & Platforms Model Model Model Model Model Model Level of Abstraction Generated Model Model Code Code Code Code Code Code Code Platform Translation • State chart Translation Translation • Data & process flow Large • Petri Nets Semantic Gap C/Fortran Operating Systems Assembly Machine code Hardware

  13. Technology Evolution (2/4) Programming Languages •Newer 3 rd -generation languages & & Platforms platforms have raised abstraction level significantly •“Horizontal” platform reuse alleviates the need to redevelop Level of Abstraction common services Model Model Model Model Model Model Model Application Code Application Code Generated Code Application Code Application Code Generated Code Generated Code Framework Framework Framework Framework Domain Specific Domain Specific Domain Specific Domain Specific Pattern Language Pattern Language Pattern Language Pattern Language Framework Framework Framework Framework Platform Platform Platform Platform Platform Platform Platform Platform Frameworks Frameworks Frameworks Frameworks Components •There are two problems, however: Frameworks •Platform complexity evolved faster C++/Java Class Libraries than 3 rd -generation languages C/Fortran Operating •Much application/platform code still Systems Assembly (unnecessarily) written manually Machine code Hardware

  14. Technology Evolution (3/4) Programming Languages Model-Driven Engineering (MDE) & Platforms Domain-specific modeling languages • ESML • PICML • Mathematica Level of Abstraction • Excel • Metamodels Manual translation Domain-independent Saturation!!!! modeling languages • State Charts Components • Interaction Diagrams Frameworks • Activity Diagrams C++/Java Semi-automated Class Libraries C/Fortran Operating Systems Assembly Machine code Hardware

  15. Technology Evolution (3/4) Programming Languages Model-Driven Engineering (MDE) & Platforms Domain-specific modeling languages • ESML • PICML • Mathematica Level of Abstraction • Excel • Metamodels Manual translation Domain-independent modeling languages • State Charts • Interaction Diagrams • Activity Diagrams Semi-automated • OMG is evaluating MDE via MIC PSIG • mic.omg.org

Recommend


More recommend