Systems Architectures Operational, Interface and Case Studies

Course on Systems Engineering for Postgraduate Students of DIAT 21st October, 2013 Defence Institute of Advanced Technology, Pune

CASDE, Aero. Dept., IIT Bombay

Interface Design
Interface is a connection for hooking another system (external interface) or for hooking one system component to another (internal interface). Interface can contain both logical and physical elements responsible for carrying items from one component (or system) to another. Systems engineer is required to identify interfaces and allocating items to the defined interfaces. Subsequently, requirements for each interface are to be derived from system level requirements. In general, interfaces are the common points of failure.
CASDE, Aero. Dept., IIT Bombay

Interface Architecture
Development of interface architecture is undertaken in conjunction with the development of allocated physical architecture, as discussed previously. There are three broad options that comprise all the architectures used in interface design. These are; Message Passing Architecture Shared Memory Architecture Network Architecture Usually, standards help in ensuring that an interface will enable the connection of the two components. (e.g. RS 232, USB, RGB etc.)
CASDE, Aero. Dept., IIT Bombay

Interface Architecture
Interface architecture development process is as follows.

CASDE, Aero. Dept., IIT Bombay

Operational Architecture Concept

Operational architecture provides a complete description of system, including functional architecture, allocated physical architecture, derived input/output, technology and other trade-offs, qualification requirements & interfaces. The development process for the operational architecture is the activity during which the entire design comes together. Given below are important steps in this regard. Allocate functions /requirements to physical sub-systems. Define & analyze functional activation/control structure. Conduct performance and risk analysis Document architecture & sub-system specifications.
CASDE, Aero. Dept., IIT Bombay

Operational Architecture Concept

Process to develop operational architecture is as follows.

CASDE, Aero. Dept., IIT Bombay

Typical Operational Architecture

Architecture shows elements, their relations, including data flow.

CASDE, Aero. Dept., IIT Bombay

CS 1: Permanent Moon Base

Given below are detailed mission objectives.

CASDE, Aero. Dept., IIT Bombay

CS 1: Permanent Moon Base

Functional Decomposition at System Level.

CASDE, Aero. Dept., IIT Bombay

CS 1: Permanent Moon Base

Sub-system Functional Decomposition.

CASDE, Aero. Dept., IIT Bombay

CS 1: Permanent Moon Base

Functional Requirements Physical Allocation.

CASDE, Aero. Dept., IIT Bombay

CS 1: Permanent Moon Base

Physical Architecture.

CASDE, Aero. Dept., IIT Bombay

CS 2: Typical Air Warfare Mission

An air warfare control system manages the release of weapons, threat D3 (degrade, disrupt, deny) and weapon store levels. Following is the detailed need statement of the above mission. Before an engagement, the engaging platform must be enabled by the air warfare officer. When the platform is enabled, the weapon system is started, if it is not already on, with the weapon launcher disengaged. When the trigger on the platform is depressed, launcher is engaged and the weapons are released.
CASDE, Aero. Dept., IIT Bombay

CS 2:Typical Air Warfare Mission

There is an interlock that prevents the weapons from being released unless a threat has been detected. Once no threats are detected, the engagement is deemed completed and the platform is de-authorized from further weapon release. Further depression of the release switch must not release any more weapons. Lastly, after a short standby period, the platforms weapon system is to be turned off, unless re-authorized. In addition, a metering device sends a pulse to the system, every time a weapon is released, enabling cost estimates.
CASDE, Aero. Dept., IIT Bombay

CS 2: Typical Air Warfare Mission

With regard to D3 assessment, these are stored until the status of threat is known. It is anticipated that sometimes, the threats escape without damage and air warfare officer is required to annotate D3 assessment, with any available information. At the end of each day, D3 assessments are to be archived and may be used for ad hoc enquiries into engagements. At present, two weapon types are to be released from five platforms in the battle-space. Each platform takes one of the two weapon stores. The weapon store levels must not be allowed to fall below 4% of the store capacity.
CASDE, Aero. Dept., IIT Bombay

CS 2: Typical Air Warfare System

Given below is the air warfare system synthesized for the functionality stated in previous slides.

Further, a battle group engages the targets within a battle space under control of an AW officer. Battle group consists of number of platforms, each with sensors (S), processors (P) and weapons (W).
CASDE, Aero. Dept., IIT Bombay

CS 2: Typical Air Warfare Architecting

The architecting process is based on analogy.

CASDE, Aero. Dept., IIT Bombay

CS 3: University Space Mission

System Design Guidelines & Requirements.

CASDE, Aero. Dept., IIT Bombay

CS 3: University Space Mission

Functional Decomposition.

CASDE, Aero. Dept., IIT Bombay

CS 3: University Space Mission

Physical Architecture.

CASDE, Aero. Dept., IIT Bombay

CS 4: Typical Aircraft Mission Architecting

Given below is functional decomposition & allocation for an aircraft mission with greater clarity up to third level.

CASDE, Aero. Dept., IIT Bombay

CS 4: Typical Aircraft Mission Architecting

Given below is the corresponding physical architecture that will achieve the functional requirements.

CASDE, Aero. Dept., IIT Bombay

Good Architecture Attributes

Meets the needs of the stakeholders (especially the users) to their satisfaction. Does not violate established principles of architecting. Takes into account relevant -lities by allowing for maintenance, evolution etc., as the customer requires. Are also elegant (intellectually clean of unnecessary complexities or 'exceptions'). Can direct a builder to cost-effective structures that can be completed within a reasonable time frame. Are conceptually pleasing to stakeholders (esp. user). Provide some special advantage (such as a competitive advantage) or utility to the customer.
CASDE, Aero. Dept., IIT Bombay

How to get Good Architecture?

Plan for Essential Complexity; avoid Gratuitous Complexity. Spend enough time on designing interfaces. Iterate on architecture until a satisfactory solution is reached. Be cognizant of big picture while designing subsystems. Provide robustness to anticipated risks. Go by the customer's opinion in case of a difference. Think holistically to arrive at good architecture. Ensure modularity for easier testing, induction of newer ideas.
CASDE, Aero. Dept., IIT Bombay

How to get Good Architecture?

Understand decompositions/ interactions in system parts . Adhere to basic governing laws of the usage context in which the system operates; elegance comes later Prevent ambiguity from creeping into the system through difficulties in communication. Identify sources for user needs appropriately, and obtain user needs from them. Verify the implementability of an idea stated simply. Include uncertainty of information in the architecture design process. Be aware of possible future things happening, future technologies, future values...
CASDE, Aero. Dept., IIT Bombay

Summary
Functional thinking helps to improve upon the system as technological advances can be included in architecture. If a system is to be evolved from scratch, logical procedure is based on elements that appear to contribute to system. Sometimes, architecting is driven by products that synthesize to form desired system, particularly when a new technology is to be inducted for same functionality. operational architectures provide additional insight into the design solution, including behavioral aspects of the system. Interface architecture is evolved using same philosophy of functional thinking and physical translation.
CASDE, Aero. Dept., IIT Bombay

References
NASA Systems Engineering Handbook INCOSE Systems Engineering Handbook A Primer for Model Based Systems Engineering, VITECH The Engineering Design of Systems, Dennis M. Buede Design Methodologies for Space Transportation Systems, Walter E. Hammond, AIAA Education Series Space Transportation : A Systems Approach to Analysis & Design., Walter Hammond, AIAA Education series. Methodology of Aircraft System Architecture Sizing, 26th International Congress of Aeronautical Sciences Civil Aircraft Advanced Avionics Architectures, NAL Conflicting Heuristics for Low-cost Launch Vehicles Architectures, Karl Gallagher Architecture and Principles of Systems Engineering, CE Dickerson & DN Mavris. Engineering Design, Dieter, Schmidt, 4th Ed. Systems Engineering and Analysis, Blanchard, Fabrycky.

CASDE, Aero. Dept., IIT Bombay