SAIP (Chapter 6): Air Traffic Control

This case study reveals how various tactics are used to provide architectural solutions that address the various quality attributes of a very demanding and complicated system that holds a ton of stakeholders and is highly fault intollerant.

A case study of this nature always comes in handy as a practical way of illustrating a proposed process to software architecture. It helps to put things in perspective, and let's the reader know the timing of each step in the process and which tactics can be used. Even though, the author clearly states that this project never went live, which sort of takes away from the project's credibility, it still allows us to get a better understanding of the process as discussed in previous chapters.

The questions that creep into my mind as I read through the chapters were more in the area of:
What kind of architect is required for a project like this? Can any architect come in and learn enough about avaition before scoping this out?
It almost sounds like an architect must be a jack of many trades to be able to determine what network topologies are availabe, what sort of hardware redundancy options are available, what kinds of security layers, etc.