This document provides an introduction to systems engineering. It defines systems engineering as an interdisciplinary approach that focuses on defining customer needs, documenting requirements, and enabling the realization of successful systems through design, validation, and considering the complete problem. Systems engineering integrates all disciplines into a team effort to develop products that meet user needs. The document discusses how systems engineering emerged to manage complexity and reduce risks associated with new systems. It also discusses systems thinking, systems engineering leadership, and professional development.

1. SYSTEM ENGINEERING
INTRODUCTION TO SYSTEM & IE
Sri Susilawati Islam

2.  Systems engineering is a profession, a process, and a perspective as illustrated by the
following three representative definitions. Certain keywords emerge from this
sampling – interdisciplinary, iterative, sociotechnical, and wholeness.
 Systems engineering is an interdisciplinary approach and means to enable the
realization of successful systems. It focuses on defining customer needs and required
functionality early in the development cycle, documenting requirements, and then
proceeding with design synthesis and system validation while considering the
complete problem: operations, cost and schedule, performance, training and support,
test, manufacturing, and disposal. Systems engineering integrates all the disciplines
and specialty groups into a team effort forming a structured development process
that proceeds from concept to production to operation. SE considers both the
business and the technical needs of all customers with the goal of providing a quality
product that meets the user needs. [INCOSE 2004]
“Systems engineering is a methodical, disciplined
approach for the design, realization, technical
management, operations, and retirement of a system”.
2.6 DEFINITION OF SE

3.  SE Purpose:
 “SE emerged as an effective way to manage complexity and change. As both
complexity and change continue to escalate in products, services, and society,
reducing the risk associated with new systems or modifications to complex
systems continues to be a primary goal of the systems engineer”
2.8 USE AND VALUE OF SYSTEMS ENGINEERING
The consequences of
making early decisions
without the benefit of
good information and
analysis. SE extends
the effort performed
in concept exploration
to reduce the risk of
hasty commitments
without adequate
study

4. 2.8.1 SE EFFECTIVENESS
A 2012 study by the National Defense Industrial Association, the
Institute of Electrical and Electronic Engineers (IEEE), and the Software
Engineering Institute of Carnegie Mellon surveyed 148 development
projects and found clear and significant relationships between the
application of SE activities and the performance of those projects

5. The left column represents those projects deploying lower levels of SE expertise
and capability, as measured by the quantity and quality of specific SE work
products. Among these projects, only 15% delivered higher levels of project
performance, as measured by satisfaction of budget, schedule, and technical
requirements, and 52% delivered lower levels of project performance

6. 2.9 SYSTEMS SCIENCE AND SYSTEMS THINKING
Systems science brings together research into all aspects of systems with the
goal of identifying, exploring, and understanding patterns of complexity that
cross disciplinary fields and areas of application. It seeks to develop
interdisciplinary foundations that can form the basis of theories applicable to
all types of systems (e.g., in nature, society, and engineering) independent of
element type or application.
systems science can help to provide a common language and intellectual
foundation for SE and make practical system concepts, principles, patterns,
and tools accessible to practitioners of the “systems approach.”

7. 2.9 SYSTEMS THINKING
“As a systems engineer, it is vital to develop knowledge and skills
that can be utilized in performing a deep analysis of problem or
opportunity situations for which system responses are required. “
The primary purpose of applying Systems Thinking is to create an
understanding and appreciation of multiple views on the same situation /
problem / opportunity at hand, in order to effectively address it.
Peter Senge, a leader in the field, defines systems thinking as a discipline for seeing
wholes and a framework for seeing interrelationships rather than things, for seeing
patterns of change rather than static snapshots (Senge, 1990).
• We prefer to apply “systems thinking” in terms of appreciating the context and
intent of the viewer, in terms of how (s)he views the containing - as well as system of
interest for his/her specific purpose at the time.
• “How does the viewer perceive the identified system and for what purpose?”
• This leads to an appreciation for multiple perspectives or – views.

9. 2.9 SYSTEMS SCIENCE AND SYSTEMS THINKING

10. 2.10 SYSTEMS ENGINEERING LEADERSHIP
Many of the processes in this handbook rightly discuss management (e.g.,
decision management, risk management, portfolio management, knowledge
management), and these are all important aspects of the SE process.
Kotter defines the key differences between leaders and managers as:
• Coping with change versus coping with complexity
• Setting a direction versus planning and budgeting
• Aligning people versus organizing and staffing
• Motivating people versus controlling and problem
solving
1. A quote often attributed to Peter Drucker is: “Managers
do things right. Leaders do the right things.” Compare this
to the informal definitions of the SE verification and
validation processes: “Verification ensures you built the
system right. Validation ensures you built the right system.”

11. 2.10 SYSTEMS ENGINEERING LEADERSHIP
Aspects of leadership that are particularly relevant for systems engineers include:
1. Thinking strategically and looking at the long‐term implications of decisions and actions
to set vision and course
2. Seeing the “big picture”
3. Casting or capturing the vision for the organization and communicating it (the systems
engineer may be working in support of the identified leader, or sometimes, it isn’t the
leader’s prerogative to “cast” the vision)
4. Defining the journey from the “as is” of today to the “to be” of tomorrow
5. Turning ambiguous problem statements into clear, precise solution challenges for the
team
6. Working with the stakeholders (including customers), representing their points of view to
the team and the team’s point of view to them
7. Maximizing customer value by ensuring a direct tie of all engineering effort to the
customer business or mission needs
8. Establishing an environment for harmonious teams while working to leverage the
potential benefits of diversity (including bridging cultural and communication differences
in multidisciplinary teams)
9. Challenging conventional wisdom at all levels
10. Managing conflicts and facilitating healthy conflict around ideas and alternatives
11. Facilitating decision making Demanding and enabling excellence

12. 2.11 SYSTEMS ENGINEERING PROFESSIONAL
DEVELOPMENT
To efficiently and cost‐effectively deliver differentiated products to the market,
an organization needs to know what gaps exist in their overall capability. An
individual needs to know what skills would enable them to be more effective,
to develop those skills, and to have a standard to demonstrate and
communicate their skill levels.

13. 2.11 SYSTEMS ENGINEERING PROFESSIONAL
DEVELOPMENT
To efficiently and cost‐effectively deliver differentiated products to the market,
an organization needs to know what gaps exist in their overall capability. An
individual needs to know what skills would enable them to be more effective,
to develop those skills, and to have a standard to demonstrate and
communicate their skill levels.

14. THANK YOU.
Sampoerna University