Scribd
Upload
88 views

MERE5001-Module 3 - Systems Engineering

Though there is a wide range of systems engineering definitions, we can simply focus on its function which is to guide the engineering of complex systems.

Uploaded by

Cedric Dela Costa
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
88 views

MERE5001-Module 3 - Systems Engineering

Though there is a wide range of systems engineering definitions, we can simply focus on its function which is to guide the engineering of complex systems.

Uploaded by

Cedric Dela Costa
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Module 3

Systems Engineering
 What is Systems Engineering?
 Relevance and Benefits of Systems Engineering
WHAT IS SYSTEMS
ENGINEERING?
The function of systems engineering is to guide the
engineering of complex systems1.
guide – to lead, manage, or direct
engineering - the application of scientific principles to practical ends
systems - set of interrelated components working together toward
some common objective
complex – restricts system in which elements are diverse; have
intricate relationships with one another
1
A. Kossiakoff et. al, “Systems Engineering - Principles and Practices,” 2 nd edition, Wiley Series; 2011
Systems Engineering (SysE) and
Traditional Engineering Disciplines
Systems Engineering
focused on the system as a whole, emphasizing its total
operation; looks at the system from the outside as well
as from the inside
responsible for leading the formative stage (concept
development) of a new system development
bridges the traditional engineering disciplines
Examples of Engineered Complex Systems1
(Signal and Data Systems)

1
A. Kossiakoff et. al, “Systems Engineering - Principles and Practices,” 2 nd edition, Wiley Series; 2011
Examples of Engineered Complex Systems1
(Material and Energy Systems)

1
A. Kossiakoff et. al, “Systems Engineering - Principles and Practices,” 2 nd edition, Wiley Series; 2011
SysE Common Themes
top-down approach vs. bottom-up approach
requirements engineering
life-cycle focus vs. acquisition only
system optimization and balance
integration of specializations and disciplines
management
Top-Down vs Bottom-Up Approach
Top-Down Approach Bottom-Up Approach
starts by looking at the starts by designing and
system as a whole building components
system-level requirements integrate them into next
are developed higher-level element
system is broken down into tested for desired
subsystems; subsystems into properties and design is
assemblies, and then into modified in an iterative
components manner until it meets criteria
Requirements Engineering
Business Needs System Requirements

Logical Design

Physical Architecture
Requirements Traceability
assures the customer that all requirements can
accounted for in the design at any stage and that
no unnecessary requirements are included
forward traceability – design decisions can be
traced from any given system-level requirement
backward traceability – means that any lower-
level requirement is associated with at least one
higher-level requirement
Life-Cycle Focus
requires a focus on the capability system, not
on the product – resulting to a focus on life-
cycle costs (LCC)
SysE maintains a life-cycle focus as decisions
are made
often tempted to focus on acquisition issues in
order to minimize acquisition costs and
schedules
System Optimization and Balance
a collection of optimally-designed subsystems do not
necessarily lead to an optimal system
SysE looks for optimal system-level performance
sometimes must force subsystem and component
designers down sub-optimal paths
SySE also recognizes that system must be designed
with balance in mind
Integration of Specializations/
Disciplines
SysE integrates a diverse range of technical
disciplines and specializations
SysE defines the tasks that can be completed
by these disparate disciplines and provides the
management to integrate their efforts to
produce a system that meets the user’s
requirements
Management
SysE has both technical and management roles
strong link between functions of project
management and systems engineering
SysE products ensure that project management
decisions are informed
RELEVANCE AND BENEFITS OF
SYSTEMS ENGINEERING
“the engineering or the re-engineering of:
a) commercial or non-commercial systems, or part thereof;
b) any system, small or large, simple or complex, software-
intensive or not, precedented or unprecedented;
c) systems containing products made up of hardware,
software, firmware, personnel, facilities, data, materials,
services, techniques, or processes (or combinations
thereof);
d) a new system or a legacy system, or portions thereof 2.”

2
ANSI/EIA-632 Standard: Processes for Engineering a System
Relevance of Systems Engineering
SysE can be applied to all systems but we must
do so in a thoughtful manner
thoughtless application can increase costs,
complexity, and schedule without any reduction
in risk
SySE activities must be tailored so that they add
value and reduce risks
Relevance of Systems Engineering
Customers use SysE to define business and
system requirements and to monitor contractor
progress and risk
Contractors use SysE to develop effective
processes for the design, development and test
of systems
Both parties are looking to produce “quality”
systems while minimizing exposure to risk
Benefits of Systems Engineering
Life-Cycle Costs (LCC) Savings
Reduction in overall acquisition schedule
Reduction in technical risk
A quality system
Life-Cycle Cost Savings
Savings over the entire life cycle are possible due
to systems engineering focus on the entire life
cycle
Early emphasis on SysE can result in significant
cost savings later in the construction and/or
production, operational use and system support,
and retirement phases
Reduction in overall acquisition schedule
Reduction in Technical Risk
SysE forces the consideration of all feasible
alternatives with a view to selecting the best
solution (allowing risk to be considered during the
selection process)
Design decisions and alternatives are linked back
to the original requirements through traceability
Technical Risk is monitored and assessed
continuously ensuring that risk mitigation occurs
in a timely manner
Quality System
Disciplined approach to SysE leads to a
“quality” system into service Business Needs
quality  fitness-for-purpose; or an
ability to serve the intended purpose
SysE ensures that specified System
Requirements
requirements accurately reflect the
business and stakeholder needs; and
the resulting system meets the Resulting
System
specified requirements
END OF MODULE 3

You might also like