CH 8: The Architecture of Systems

8.1 INTRODUCING THE SYSTEM ARCHITECTURE CONSTRUCT

CH 8: The Architecture of Systems

 CH 8: The Architecture of Systems

8.2 INTRODUCTION OF THE SYSTEM ELEMENTS

8.3 UNDERSTANDING SYSTEM ELEMENT ENTITY
RELATIONSHIPS

CH 8: The Architecture of Systems

Logical Entity
Relationships
•The first step in identifying logical entity
relationships is to simply recognize and
acknowledge that some form of association
exists through deductive reasoning. You may
not know the physical details of the
relationship—that is, how they linkup—but
you know a relationship does or will exist.
Graphically, we depict these relationships as
simply a line between the two entities.

•The second step is to characterize the

logical relationship in terms of logical
functions—that is, what interaction occurs
between them must be provided to enable
the two entities to associate with one
another.

CH 8: The Architecture of Systems

Physical
Entity
Relationships
•The physical implementation of system
element interfaces requires more in-depth
analysis and decision making. Why?
Typically, cost, schedule, technology,
support, and risk become key drivers that
must be “in balance” for the actual
implementation. Since there should be a
number of viable candidate options available
for implementing an interaction, trade
studies may be required to select the best
selection and configuration of physical
components. Graphically, we refer to the
physical implementation of an interface as a
physical representation. As we select
components (copper wire, light switches,
lighting fixtures, etc.),

CH 8: The Architecture of Systems

CH 9:System Levels of Abstraction and Semantics
9.1 ESTABLISHING A SEMANTICS FRAME OF REFERENCE

One of your first tasks as a system analyst or SE is to establish a semantics frame of reference for your SYSTEM OF
INTEREST (SOI). When most people refer to systems, they communicate about a system from their own observer’s frame
of reference of everyday work tasks. When you listen to communications between Users, the Acquirer, and System
Developers, you soon discover that one person’s SYSTEM equates to another person’s SUBSYSTEM, and so forth

CH 9:System Levels of Abstraction and Semantics

9.2
UNDERSTANDING
SYSTEM LEVELS
OF ABSTRACTION

•We identify several groupings of items:

•1. Entity 10 consists of Entities A and E.

•2. Entity 20 consists of Entities C, F, and I.

•3. Entity 30 consists of Entities D, J, H,

and M.

•4. Entity 40 consists of Entities B, K, L, N,

and O.

CH 9:System Levels of Abstraction and Semantics

9.3 Tailoring Levels of Abstraction for Your System’s
Application

CH 9:System Levels of Abstraction and Semantics

9.4 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 sets of entities.

•System composition entity relationships

(ERs) enable us to analytically decompose
hierarchical systems into manageable design
levels of complexity. Figure 9.4 provides a
framework for the rules stated in Table 9.2.

CH 9:System Levels of Abstraction and Semantics

CH 10: The System of Interest Architecture
THE SYSTEM ELEMENT ARCHITECTURE
CONSTRUCT

Every human-made system consists of a generalized framework we refer to as the System Element Architecture
(SEA). The SEA represents a logical arrangement of system elements that serve as generalized construct or template
for systems design and analysis. Figure 10.1 provides a graphical representation of the SEA. To promote readability
and simplicity in the figure, the OPERATING

ENVIRONMENT is abstracted as a single entity. Every system performs MISSION SYSTEM and SUPPORT
SYSTEM roles as part of its tasking from HIGHER ORDER SYSTEMS. Regardless of the system role, each system
consists of combinations of system elements with specific system and mission objectives.

CH 10: The System of Interest Architecture

Mission System and •Each MISSION SYSTEM and SUPPORT SYSTEM consists of a unique set of integrated
Support System system elements that enable the system to accomplish its mission and objectives. The
mission/support system elements are PERSONNEL, EQUIPMENT, SOFTWARE, MISSION
Compositional RESOURCES, PROCEDURAL DATA, and SYSTEM RESPONSES. Table 10.1 relates each of
these elements to the MISSION SYSTEM and SUPPORT SYSTEM roles.
Elements

CH 10: The System of Interest Architecture

CH 10: The System of Interest Architecture
CH 11: The Operating Environment Architecture
CH 11: The Operating Environment Architecture
 CH 11: The Operating Environment Architecture

11.1 OPERATING
ENVIRONMENT
OVERVIEW
•Analytically, the OPERATING
ENVIRONMENT that influences and
impacts a system’s missions can be
abstracted several different ways.
For discussion purposes the
OPERATING ENVIRONMENT can be
considered as consisting of two high-
level domains: 1) HIGHER ORDER
SYSTEMS and 2) the PHYSICAL
ENVIRONMENT as shown in Figure
11.1. Let’s define each of these
system elements.
CH 11: The Operating Environment Architecture
CH 11: The Operating Environment Architecture
CH 11: The Operating Environment Architecture
CH 12 : System Interfaces
CH 12 : System Interfaces
CH 12 : System Interfaces
CH 12 : System Interfaces
CH 12 : System Interfaces
CH 12 : System Interfaces
CH 12 : System Interfaces