System Analysis Concepts

System Architecture Concepts Series

By Mazen Salah El Dien Mahmoud

Supervised by Dr. Maher

I.1 The Architecture of System

1 System Construct

2 System Elements

3 System Elements Entity Relationships

I.1 The Architecture of System Cont.

System Construct
I.1 The Architecture of System Cont.
System Construct
I.1 The Architecture of System Cont.

SystemElements SystemElements

- The SYSTEM OF INTEREST (SOI)- - The OPERATING ENVIRONMENT-which

which apply to MISSION SYSTEM apply to HIGHER ORDER SYSTEMS and
role and SUPPORT SYSTEM role. PHYSICAL ENVIRONMENT.
I.1 The Architecture of System Cont.
System Elements Entity Relationships

To identify the relationship exists Between Two System Entities, we

have two steps:
- The first step is Identify Logical Association.
- The second step is Identify Logical Entities and their Interactions.
Example:
Room Lighting—Logical Architecture Entity Relationships The top
portion of the Figure3 depicts a simple ROOM LIGHTING SYSTEM
consisting of a PERSON (entity) desiring to control a room
LIGHT SOURCE (entity). As a logical representation, we draw a
line between the PERSON (entity) and the LIGHT SOURCE (entity)
to acknowledge the relationship. Thus, we state that the PERSON
(entity) has a logical association or entity relationship with the
LIGHT SOURCE.
I.1 The Architecture of System Cont.
Logical-Physical Representations
I.2 System Levels of Abstraction and Semantics

1 WHAT IS ABSTRUCTION?

2 SYSTEM LEVELS OF ABSTRACTION

3 System Decomposition and Integration Design

Guidelines
I.2 System Levels of Abstraction and Semantics Cont.

Tailoring Levels of Abstraction for Your

4 System’s Application
I.2 System Levels of Abstraction and Semantics Cont.

What is Abstraction

Product Structure The hierarchical structure of a physical system that represents decomposition
relationships of physical entities. A top assembly drawing, specification tree, and a bill of materials
(BOM) are primary documents for describing a SYSTEM’s product structure.

SYSTEM LEVELS OF ABSTRACTION

When we address the deliverable system context, we need a standard way of communicating the embedded
levels of abstraction. Since all systems are hierarchical, the User’s system may be a supporting element of
HIGHER ORDER SYSTEM. Given the large number of direct and indirect Users of the system,

System Decomposition and Integration Design Guidelines

System structures are viewed from two SE perspectives:

1. Analytically, as a top-down, hierarchical decomposition or expansion.
2. Physically, as bottom-up, vertically integrated se
I.2 System Levels of Abstraction and Semantics Cont.
I.3 The System of Interest Architecture

1 What is an SOI?

2 The System Element Architecture Construct

3 System Element Interactions

I.3 The System of Interest Architecture Cont.

What is an SOI? THE SYSTEM ELEMENT ARCHITECTURE CONSTRUCT

The central focal point for the
development of any system is the
SYSTEM OF INTEREST (SOI) consisting
of the MISSION SYSTEM(s) and its
SUPPORT SYSTEM(s).
• PERSONNEL Element
• EQUIPMENT Element
• MISSION RESOURCES Element
• PROCEDURAL DATA Element
Sytem • SYSTEM RESPONSES Element
Analysis • FACILITIES Element

The System Element Interaction

When you define your system and identify
physical instances of each system
element, the next step is to characterize
the levels of interactions that occur
between each interface.
I.4 The Operating Environment Architecture

1 What is operating Environment

2 Operating Environment Overview

Physical Environment Domain System

3 Elements
I.4 The Operating Environment Architecture
What is operating Environment
The OPERATING ENVIRONMENT represents the totality of natural and human-made entities that a
system must be prepare to cope with during missions and throughout its lifetime. As one of a
system’s key life expectancy dependencies, the system’s ability to: 1) prepare for, 2) conduct, and
3) complete missions successfully is influenced by its OPERATING ENVIRONMENT.

The success of any system is ultimately determined by its ability to:

1. Conduct its planned missions and achieve performance mission objectives.
2. Cope with threats—namely, vulnerability and survivability—within its prescribed OPERATING
ENVIRONMENT.

For a system to accomplish these objectives, SE’s face several major challenges.
1. Understand WHAT missions the User plans for the system to accomplish.
2. Based on the missions, specifically bound the system’s OPERATING ENVIRONMENT.
3. Understand the OPERATING ENVIRONMENT opportunities and threats related to those
missions.
4. Identify the most likely or probable OPERATING ENVIRONMENT opportunity and threat
scenarios that influence/impact system missions.
I.4 The Operating Environment Architecture Cont.
Operating Environment Overview
I.4 The Operating Environment Architecture Cont.
Operating Environment Overview
I.4 The Operating Environment Architecture Cont.
PHYSICAL ENVIRONMENT DOMAIN SYSTEM ELEMENTS
A system’s PHYSICAL ENVIRONMENT domain consists
of three classes of
system elements: NATURAL, HUMAN-MADE, and
INDUCED. NATURALand HUMAN-MADE
ENVIRONMENTs systems interact; the INDUCED
ENVIRONMENT represents the time dependent
result of that interaction.
EXAMPLE
Let’s assume that we are developing a system such
as a building that has a placement or impact
on a land use area that has HISTORICAL significance.
The building construction may disturb artifacts and
relics from the legacy culture, and this may
influence technical decisions relating to the physical
location of the system. One perspective may be to
provide physical space or a buffer area between the
historical area and our system. Conversely, if our
system is a museum relevant to an
archeological discovery, the location may be an
INTEGRAL element of the building design.
I.5 System Interfaces

1 What is an interface?

2 Interface PURPOSE

3 INTERFACE TYPES
I.5 System Interfaces

4 LOGICAL AND PHYSICAL INTERFACES

5 PHYSICAL INTERFACE TYPES

6 INTERFACE PERFORMANCE AND INTEGRITY

I.5 System Interfaces

What is an interface?

Interfaces occur between combinations of two or more system

elements—such as EQUIPMENT, PERSONNEL, and FACILITIES
—or between entities within system element levels of abstractions .

System engineering efforts often focus on:

1. The composition of the system architecture.
2. How those elements interact with each other and their
OPERATING ENVIRONMENT.
I.5 System Interfaces

Purpose of interface?

The purpose of an interface is to associate or physically connect a

SYSTEM, PRODUCT, SUBSYSTEM, ASSEMBLY, SUBASSEMBLY, or
PART level component to other components within its OPERATING
ENVIRONMENT.
I.5 System Interfaces

Purpose of interface?

Typical interface objectives include the following:

Objective 1: Physically link or bind two or more system elements
or entities.
Objective 2: Adapt one or more incompatible system elements or
entities.
Objective 3: Buffer the effects of incompatible system elements.
Objective 4: Leverage human capabilities.

Objective 5: Restrain system element or its usage.

I.5 System Interfaces Cont.
Interface PURPOSE
I.5 System Interfaces Cont.
INTERFACE TYPES
Interfaces exhibit three types of operation: active, passive, or active/passive.

Active Interfaces
EXAMPLE
Radio stations, as active “on the air” systems, radiate signals at a designated frequency via patterns to
specific
areas for coverage.
Passive Interfaces
EXAMPLE
A car radio, when powered ON and viewed by a radio station system, PASSIVELY receives signals over a
tuned frequency. The radio processes the information and provides an ACTIVE audio interface for the
occupants in the car.
Combination Active/Passive Interfaces
EXAMPLE
A two-way walkie-talkie radio has an ACTIVE interface when the User presses the “Push to Talk” button to
broadcast audio information to others listening on the same frequency within a specified transmission
range and conditions. When the “Push to Talk” button is OFF, the device has a PASSIVE interface that
monitors incoming radio signals for processing and audio amplification as controlled by the User.
I.5 System Interfaces Cont.
LOGICAL AND PHYSICAL INTERFACES

Logical interfaces
Represent a direct or indirect association or relationship between two entities.

Physical interfaces
Represent physical interactions between two interfacing entities .

EXAMPLE
The Internet provides a mechanism for a User with a device such as a computer equipped with the
appropriate hardware and software to communicate with an external Web site. In this context a logical
interface or association exists between the user and the Web site. When the User connects with the Web
site, a physical interface is established.
I.5 System Interfaces Cont.
PHYSICAL INTERFACE TYPES

- Mechanical Interfaces
- Electrical Interfaces
- Optical Interfaces
- Acoustical Interfaces
- Natural Environment Interfaces
- Chemical Interfaces
- Biological Interfaces
I.5 System Interfaces Cont.
INTERFACE PERFORMANCE AND INTEGRITY

Interfaces, as an entry point or portal into a system,

are vulnerable to threats and failures, both
internally and externally. Depending on the extent
of the physical interface interaction and resulting
damage or failure, the interface capability or
performance may be limited or terminated.