A-7E Avionics System Case Study

1. A-7E Avionics System Case Study

2. Utilizing Architectural Structures • An object-oriented program’s structure often bears little resemblance to its code structure. • The code structure is frozen at compile-time; it consists of classes in fixed inheritance relationships. • A program’s runtime structure consists of rapidly changing networks of communicating objects. • The structures are largely independent and nearly impossible to understand one from the other.

3. Requirements of the A-7E Avionics System • The system is responsible for reading sensors and updating cockpit displays that help the pilot drop weapons on a target. • It does not fly the aircraft.

4. Architecture for the A-7E Avionics System • The architecture is centered around three structures: • Decomposition, a structure of modules • Uses, a structure of modules • Process, a structure of components and connectors • The module decomposition is based on information hiding

5. How the Module Decomposition Achieves its Goals

6. A-7E Module Decomposition Structure • Hardware-Hiding Module • Extended Computer Module • Device Interface Module • Behavior-Hiding Module • Function Driving Module • Shared Services Module • Software Decision Module • Application Data Type Module • Data Banker Module • Filter Behavior Module • Physical Models Module • Software Utility Module • System Generation Module

7. How the Uses Structure Achieves its Goals

8. How the Process Structure Achieves its Goals