Consider the following software design problem: Airplane Monitoring: In an airplane, there are many sensors: speed, altitude, cabin pressure, fuel level, etc. The monitoring system will collect the sensor data, preprocess the data, and perform different checks on the sensor data. If a problem is noticed, the system either shows a warning to the pilot (e.g. low on fuel), or in a dangerous situation may react automatically (e.g. by dropping oxygen masks). The system will run on a multi-core machine and should do the checks in near real-time when new sensor data comes in.

As the KWIC case study, draw a system architecture diagram that describes your design on airplane monitoring, for each of the four architectural styles, i.e., shared data, abstract data type, pipe and filter, and implicit invocation. For each style, quickly explain in words how the system works, and state the most important advantages and disadvantages of using this architecture for solving this particular problem