SYSTEMS ENGINEERING
FUNCTIONAL ANALYSIS & SYSTEM ARCHITECTURE
IGAL BEILIN, SYSTEMS ENGINEERING EXPERT
WHAT IS FUNCTIONAL ANALYSIS?
Definition of the System from the point of view of its functionality -
originating from User Needs, Use Cases and Operational Concept.
Vs. the outdated and flawed “Physical decomposition first”
approach.
The Functional Analysis approach makes sure we build the system
with exactly what users need, and get it right on first try
(or at least much faster)
MAIN STEPS IN FUNCTIONAL ANALYSIS
Define the System’s main functions first
Define the System’s States and Modes (of operation)
Allocate functions to specific States & Modes
Create an Enhanced Function Flow Block Diagram
(EFFBD)
FUNCTIONAL ANALYSIS DIAGRAM
Breakdown to main modes of operation and functions
System Functionality
Main Function /
Objective
Mode 1 Mode 2 Mode 3
Function 1, Function 2 Function 3, Function 4 Function 5
Sub state 2.1 Sub state 2.2
Function 2.1.1 Function 2.2.1
ENHANCED FUNCTION FLOW BLOCK DIAGRAM - EFFBD
Function 1 Function 2
Mode 1 entry / Trigger 1; Dataset 1 entry / Output 1; Dataset 2
do / Perform Function 1 do / Perform Function 2
exit / Output 1 exit / Output 2
Feedback/ Iterative process loop
Function 3 Function 4
Ref. In Ref. Out
OR Mode 2 IT entry / Trigger 2
do / Perform Function 3
entry / Output 3
do / Perform Function 4
IT OR
exit / Output 3 exit / Output 4
Function 5
Mode 3 entry / Dataset 3
do / Perform Function 5
exit / Output 5
• Functional flow • Input/Output
• Trigger events ✓Full functional definition
SYSTEM ARCHITECTURE
• Physical decomposition of the system into modules &
components
• Internal & external interface definition: connecting the
system components with flow of data/matter/energy/etc.
SYSTEM ARCHITECTURE - DECOMPOSITION
System
Main System operation
Module 1 Subsystem 1 Module 2
-Attribute 1: Type -Attribute 1: Type -Attribute 1: Type
-Attribute 2: Type -Attribute 2: Type -Attribute 2: Type
-Attribute 3: Type -Attribute 3: Type -Attribute 3: Type
+ Operation 1 () + Operation 1 () + Operation 1 ()
+ Operation 2 () + Operation 2 () + Operation 2 ()
Module 1.1 Module 1.2
-Attribute 1: Type -Attribute 1: Type
-Attribute 2: Type -Attribute 2: Type
-Attribute 3: Type -Attribute 3: Type
+ Operation 1 () + Operation 1 ()
+ Operation 2 () + Operation 2 ()
SYSTEM ARCHITECTURE – INTERNAL BLOCK DIAGRAM
IBD
System Boundary
Module 1 Module 2
-Attribute 1: Type -Attribute 1: Type
[Link] 1 -Attribute 2: Type [Link] M1-M2 {Power: Voltage} -Attribute 2: Type
-Attribute 3: Type -Attribute 3: Type
+ Function 1 () + Function 2 ()
[Link] M1-S1 {Power: Voltage}
[Link] M2-M1.1 {Comm. Data}
Subsystem 1
-Attribute 1: Type
-Attribute 2: Type Composed off
-Attribute 3: Type
+ Function 4 () Composed off
Module 1.1 Module 1.2
-Attribute 1: Type -Attribute 1: Type
[Link] 1.1 -Attribute 2: Type -Attribute 2: Type
-Attribute 3: Type -Attribute 3: Type
+ Function 5 () + Function 7 ()
+ Function 6 ()
SUMMARY
Functions definition comes first.
Functional Analysis and Architecture definition complement
each other to create a full, comprehensive system model.
Complete Architecture definition, accompanied by quality
requirements, are the foundation for successful System
development.
When we connect the pieces right, the whole is so much more
than the sum of its pieces.
INTERESTED & WANT TO LEARN MORE?
Follow + and for more content like this.
Igal Beilin – Systems Engineering enthusiast