Chapter 1.

1
Introduction to Systems Engineering

• Introduction
• What is Systems Engineering?
• History of Systems Engineering and
INCOSE
• Is Systems Engineering a Separate
Engineering Discipline?
• Future Steps
International Council On Systems Engineering 8/29/20 1
19
 Briefing to the
Texas Board of Professional Engineers

What is
Systems Engineering?

International Council On Systems Engineering 8/29/20 2

19
 What is a System?

• Definition of a System
(NASA Systems Engineering Handbook)
– A system is a set of interrelated components which
interact with one another in an organized fashion
toward a common purpose.

• System components may be quite diverse

– Persons and Organizations
– Software and Data
– Equipment and Hardware
– Facilities and Materials
– Services and Techniques

International Council On Systems Engineering 8/29/20 3

19
 Systems Engineering &
Component Engineering

• Science
Determines what Is

• Component Engineering
Determines what Can Be

• Systems Engineering
Determines what Should Be

International Council On Systems Engineering 8/29/20 4

19
 Systems Engineering
• Definition of Systems Engineering
(NASA SE Handbook)
– Systems Engineering is a robust approach to
the design, creation, and operation of systems.

• Systems Engineering consists of

– Identification and quantification of system goals
– Creation of alternative system design concepts
– Performance of design trades
– Selection and implementation of the best design
(balanced and robust)
– Verification that the design is actually built and properly
integrated in accordance with specifications
– Assessment of how well the system meets the goals
International Council On Systems Engineering 8/29/20 5
19
 • What needs are we trying to fill?
• Focus of Systems Need • What is wrong with the current situation?
• Is the need clearly articulated?
Engineering
• Who are the intended users?
– From Original Need Operations Concept • How will they use our products?
– To Final Product • How is this different from the present?

• The Whole • What specific capability will we provide?

Functional Requirements • To what level of detail?
System
• Are element interfaces well defined?
• The Full System
Life Cycle • What is the overall plan of attack?
System Architecture • What elements make up the overall approach?
• Are these complete, logical, and consistent?

• Which elements address which requirements?

Allocated Requirements • Is the allocation appropriate?
• Are there any unnecessary requirements?

• Are the details correct?

• Focus of Component Detailed Design • Do they meet the requirements?
Engineering • Are the interfaces satisfied?

• On Detailed Design • Will the solution be satisfactory in terms

Implementation
• And Implementation of cost and schedule?
• Can we reuse existing pieces?

• What is our evidence of success?

Test & Verification • Will the customer be happy?
• Will the users’ needs be met?
 The “Vee” Model of
System Development
User Requirements System
& Concept of Demonstration &
Operations Validation Systems
Engineering
Domain
System
System Integration
Requirements &
& Test
Architecture

Component
Component Design
Integration & Test

Component
Engineering
Procure, Fabricate, Domain
& Assemble Parts

International Council On Systems Engineering 8/29/20 7

19
 Systems Engineering
Contributions
• Systems engineering brings two elements to a
project that are not usually present
– A disciplined focus on the
• end product,
• its enabling products, and
• its internal and external operational environment
(i.e., a System View)
– A consistent vision of stakeholders’ expectations
independent of daily project demands
(i.e., the System’s Purpose)

International Council On Systems Engineering 8/29/20 8

19
 Role of Systems Engineering in
Product Development
• Integrates Technical Effort Across Systems Engineering
the Development Project

Chem Engrg
Mech Engrg

Civil Engrg
Elec Engrg
– Functional Disciplines

SW Engrg
– Technology Domains
– Specialty Concerns

Systems Engineering Systems Engineering

Communications
Maintainability
Environment

Producibility

Computers
Reliability

Structures

Processes
Avionics
Safety

International Council On Systems Engineering 8/29/20 9

19
 Building Blocks of
Systems Engineering
• Math & Physical Sciences
– Qualitative modeling
– Quantitative modeling
– Physical modeling
– Theory of Constraints
– Physical Laws
• Management Sciences
– Economics
– Organizational Design
– Business Decision Analysis
– Operations Research
• Social Sciences
– Multi-disciplinary Teamwork
– Organizational Behavior
– Leadership
Unique to Systems Engineering
International Council On Systems Engineering
• Body of Knowledge
– Problem definition
• Concept of operations
• System boundaries
• Objectives hierarchy
• Originating requirements
– Concurrent engineering
• System life cycle phases
• Integration/Qualification
– Architectures
• Functional/Logical
• Physical/Operational
• Interface
– Trades
• Concept-level
• Risk management
• Key performance parameters
8/29/20 10
19
 Ethical Considerations

• Achieving balance between • System Optimization

inherent conflicts – Subsystems often suboptimal to
achieve best balance at system level
– System Functionality and
Performance – Ultimate system purpose must prevail
against conflicting considerations
– Development Cost and
– Long-term considerations (e.g.,
Recurring Cost
disposal) may drive technical decisions
– Development Schedule • Customer Interface
(Time to Market)
– Often must act as “honest broker”
– Development Risk – Carries burden of educating
(Probability of Success) customer on hard choices
– Business Viability and – Must think ahead to the next
Success customer and next application
– Must “challenge” all requirements

International Council On Systems Engineering 8/29/20 11

19
 Summary

• Systems Engineering
– Has Unique Focus
• End product and system purpose
• Stakeholder needs and expectations
• Full system life cycle
(Conception through Retirement)
– Has Unique Approach
• Integrates disciplines and technologies
• Balances conflicting considerations
– Has Unique Methods, Tools & Models for
• System analysis and simulation
• Assessment of performance and risk
• Organization and management of
information and requirements
• Verification and validation

International Council On Systems Engineering 8/29/20 12

19
 Briefing to the
Texas Board of Professional Engineers

History
of
Systems Engineering
and the

The International Council On

Systems Engineering (INCOSE)

International Council On Systems Engineering 8/29/20 13

19
 Systems Engineering Heritage

• Water Distribution Systems in Mesopotamia 4000 BC

• Irrigation Systems in Egypt 3300 BC

• Urban Systems such as Athens, Greece 400 BC

• Roman Highway Systems 300 BC

• Water Transportation Systems like Erie Canal 1800s

• Telephone Systems 1877

• Electrical Power Distribution Systems 1880

International Council On Systems Engineering 8/29/20 14

19
 Modern Origins
of the Systems Approach
• British Multi-disciplined Team Formed (1937) to
Analyze Air Defense System

• Bell Labs Supported Nike Development (1939-1945)

• SAGE Air Defense System Defined and Managed by

MIT (1951-1980)

• ATLAS Intercontinental Ballistic Missile Program

Managed by Systems Contractor, Ramo-Wooldridge
Corp (1954-1964)

International Council On Systems Engineering 8/29/20 15

19
 Spread of the Systems Approach1

• Early Proponents
– Research and Development Corporation (RAND)
– Robert McNamara (Secretary of Defense)
– Jay Forrester (Modeling Urban Systems at MIT)
• Growth in Systems Engineering Citations
(Engineering Index)
– Nil in 1964
– One Page in 1966
– Eight Pages in 1969
• Nine Universities Offered Systems Engineering
Programs in 1964
1) Hughes, Thomas P., Rescuing Prometheus, Chapter 4, pps. 141-195, Pantheon Books, New York, 1998.

International Council On Systems Engineering 8/29/20 16

19
 Government Publications Codified
Systems Engineering Discipline
• USAF Systems Engineering Handbook 375-5 [1966]

• MIL-STD-499 (USAF), Systems Engineering

Management [1969]

• U.S. Army Field Manual 770-78, Systems

Engineering [1979]

• Defense Systems Management College, Systems

Engineering Management Guides [1983, 1990]

• NASA Systems Engineering Handbook [1995]

International Council On Systems Engineering 8/29/20 17

19
 Discipline Maturation

• “Explosive Growth in Computing Power is

Profoundly Changing the Systems, Themselves,
and, Consequently, Systems Engineering as
Practiced Over the Last Half Century.”
--- Eberhardt Rechtin, July 1993

• Steady Growth in Commercial Computer Tools

that Automate and Improve Execution of Systems
Engineering Process

• Increasing World Wide Reports of Systems

Engineering Applications

International Council On Systems Engineering 8/29/20 18

19
 Expanding Horizons

• Collaboration with Other Technical Societies

• Development of Systems Engineering Standards
(National & International)
• Encouraging International Membership
(Now 27% Outside United States)
• Nurturing Emerging SE Applications
– Commercial
– Environmental

• Fostering SE Education and Research

International Council On Systems Engineering 8/29/20 19

19
 Why Systems Engineering
Is
a Separate Engineering
Discipline!

International Council On Systems Engineering 8/29/20 20

19
 Two Perspectives on SE
• SE is a way of thinking
– Practiced by senior
engineers with OJT
– Is unique to the
product/industry of the
engineering firm
– Should be taught within other
engineering disciplines
– Scientific foundations and
body of knowledge have
commonality across
product/industry but are not
unique to SE
– SE team has engineers of all
disciplines
International Council On Systems Engineering
• SE is a discipline of
engineering
– Has scientific foundations
that cross many other
engineering disciplines
– Has body of knowledge
separate from other
disciplines
– Can be taught separately
from other disciplines in an
engineering school
– Separate roles exist on the SE
team for a specific product
time
8/29/20 21
19
 SE as an Engineering Discipline
• Scientific Foundations
– Qualitative modeling
• Data modeling
• Process modeling
– Quantitative modeling
• Behavioral modeling
• Feedback and control
• “ility” modeling
• Trade-off modeling
– Physical modeling
• Prototypes for requirements
• Usability testing
• Prototypes for interface
resolution
• Integration/qualification
International Council On Systems Engineering
• Body of Knowledge
– Problem definition
• Concept of operations
• System boundaries
• Objectives hierarchy
• Originating requirements
– Concurrent engineering
• System life cycle phases
• Integration/Qualification
– Architectures
• Functional/Logical
• Physical/Operational
• Interface
– Trades
• Concept-level
• Risk management
• Key performance parameters
8/29/20 22
19
 Summary
• Systems Engineering – an Engineering Discipline
– Skills and Problems Not Unique
– But Unique Mixture of Skills and Problems
• Growing SE Academic Community
– Houston, SMU, Texas Tech
– MIT, Rochester Inst. Of Tech., Stevens Inst. Of Tech.
• Growing Body of Knowledge
– Books
– SE Journal and Conferences
– Standards
• Students Pursue Degrees in SE
• Engineers Pursue Job Titles in SE
• Engineering Firms Pursue Engineers that Think
at the System Level

International Council On Systems Engineering 8/29/20 23

19
 Recommendations

• Recognize Systems Engineering as a distinct

engineering discipline
• Follow a process similar to Software Engineering
to define the discipline of Systems Engineering
– Body of Knowledge
– Code of Ethics
– Professional Practice
– Education Criteria/Collaboration with NCEES
– Examination Standards
• Move out quickly to partner with INCOSE to lead,
facilitate & coordinate further actions
International Council On Systems Engineering 8/29/20 24
19