Professional Documents
Culture Documents
Chapter 2
Systems Approach and Systems
Engineering
System Definition
1
5/17/2021
Definition of System
A system is an organized or
complex whole; a group of
parts interacting in a
coordinated way.
1. The parts of the system
affect the system and are
affected by it : Holism
2. The group of parts does
something: Exhibits Behavior
3. The group is of particular
interest
2
5/17/2021
3
5/17/2021
4
5/17/2021
A Company as a System
The whole system
Management
Production subsystem
Production
manager
Manufacturing
subsystem Supervisor Elements
Team A Team B
5
5/17/2021
Attributes
◼ Systems, subsystems, and elements each have
distinguishing characteristics called attributes
◼ These describe or express the condition of system,
subsystem, or element in qualitative or quantitative
terms.
◼ In human-made systems, many of the attributes are
designed into the system so that the system
performs as required.
6
5/17/2021
System Structure
◼ Elements and subsystems are linked together
by relationships. The form of the relationships
is referred to as the structure of the system.
◼ Most systems, including projects, can be
conceptualized as hierarchical and network
structures.
7
5/17/2021
Hierarchical structure
A B C
a b c d e f g
Network structure
e c
d b g
a f
Mechanism/Means/Methods
Input-process-output relationship
8
5/17/2021
9
5/17/2021
10
5/17/2021
System Approach
11
5/17/2021
Systems Approach
The systems approach is a methodology for solving
problems and managing systems that accounts for
Technical Council on Lifeline Earthquake Engineering (TCLEE) Lifeline Systems Interdependence Committee: Conceptual model
developed to help understand, model, manage, and exploit the increasingly coupled and complex operations across lifeline systems
12
5/17/2021
System Models
A model is a simplified representation of a system; it
abstracts the essential features of the system under
study.
◼ A physical model is a scaled-down abstraction of the
real system. It includes some aspects of the system
and excludes others.
❑ Example: model airplane.
◼ A conceptual model depicts the elements, structure,
and flows in a system in terms of a schematic
diagram or mathematical formulation.
❑ Example: population dynamics schematic
13
5/17/2021
Deaths
Births
Migration
14
5/17/2021
maturity
death
conception
growth
birth
15
5/17/2021
16
5/17/2021
System Engineering
17
5/17/2021
1. SE is a multifunctional, interdisciplinary,
concurrent effort.
❑ Systems engineers work with the system’s
stakeholders to determine their needs and what
the system must do to fulfill them.
❑ The needs become the basis for defining the
system requirements, which specify what the
system will do
18
5/17/2021
19
5/17/2021
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
20
5/17/2021
Detailed characteristics
of system
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
21
5/17/2021
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
Test
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
22
5/17/2021
EVALUATION
EVALUATION
Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd
ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).
23
5/17/2021
Tasks Evaluation
Stakeholders Schedule
Human
Resources Evaluation
24
5/17/2021
Class Activity
System Concepts and Principles
25
5/17/2021
Class Exercise
26