Introduction to Systems Engineering
1. Overview
The lecture introduces formal definitions of systems engineering from
different organizations.
Discusses the main process of applying systems engineering across a
product’s lifecycle.
Focus on conceptual design as the first phase in system development.
2. Formal Definitions of Systems Engineering
A. International Council on Systems Engineering (INCOSE)
Interdisciplinary approach to enable the realization of successful systems.
Defines customer needs and functionality early in development.
Involves documenting requirements, design synthesis, and system validation
while considering the full problem.
Balances business and technical needs to create a quality product that
meets user requirements.
B. Electronic Industries Alliance (EIA)
Technical effort to integrate people, products, and processes into a balanced
system.
Covers the entire lifecycle:
Development, manufacturing, verification, deployment, operations, support,
disposal, and user training.
Involves system configuration management, work breakdown structure, and
decision-making information.
C. Defense Systems Management College
Scientific and engineering approach to achieve three main goals:
Transform operational needs into system specifications through an iterative
process.
Ensure compatibility of physical, functional, and program interfaces.
Integrate key design considerations (reliability, safety, human factors, etc.).
D. Common Themes Across Definitions
Top-down approach
Lifecycle orientation
Thorough initial definition of requirements
Interdisciplinary/team-based approachIntroduction to Systems Engineering
1. Overview
The lecture introduces formal definitions of systems engineering from
different organizations.
Discusses the main process of applying systems engineering across a
product’s lifecycle.
Focus on conceptual design as the first phase in system development.
2. Formal Definitions of Systems Engineering
A. International Council on Systems Engineering (INCOSE)
Interdisciplinary approach to enable the realization of successful systems.
Defines customer needs and functionality early in development.
Involves documenting requirements, design synthesis, and system validation
while considering the full problem.
Balances business and technical needs to create a quality product that
meets user requirements.
B. Electronic Industries Alliance (EIA)
Technical effort to integrate people, products, and processes into a balanced
system.
Covers the entire lifecycle:
Development, manufacturing, verification, deployment, operations, support,
disposal, and user training.
Involves system configuration management, work breakdown structure, and
decision-making information.
C. Defense Systems Management College
Scientific and engineering approach to achieve three main goals:
Transform operational needs into system specifications through an iterative
process.
Ensure compatibility of physical, functional, and program interfaces.
Integrate key design considerations (reliability, safety, human factors, etc.).
D. Common Themes Across Definitions
Top-down approach
Lifecycle orientation
Thorough initial definition of requirements
Interdisciplinary/team-based approach
3. Key Characteristics of Systems Engineering
1. Top-Down Approach
Starts from high-level requirements and refines into detailed specifications.
Ensures alignment with objectives and user needs.
Prevents missing critical design considerations early in development.
2. Lifecycle Orientation
Covers the entire system lifecycle:
Idea → Design → Development → Deployment → Operation → Maintenance →
Disposal.
Ensures long-term performance and sustainability.
3. Strong Focus on Defining System Requirements Early
Engages stakeholders and end-users early to define needs and functions.
Establishes clear and precise requirements to prevent costly redesigns later.
4. Interdisciplinary Team Approach
Involves experts from different fields working collaboratively.
Ensures all aspects of system development are considered and optimized.
Leverages diverse expertise to create a well-integrated solution.
4. Application Domains of Systems Engineering
Educational systems
Financial services
Transportation systems
Manufacturing and production
Aerospace and marine industry
Urban infrastructure development
Communication and IT systems
Healthcare systems (hospitals, clinics, service industry)
Application Scenarios
Large-scale systems (e.g., space-based systems, urban transport).
Small-scale systems (e.g., custom machines for businesses).
Manufacturing and production systems with complex input-output
relationships.
New product design and advanced technologies.
Modifying existing production using available resources (e.g., transitioning
from outsourcing to in-house production).
Data-intensive and information systems (e.g., inventory tracking, kanban
systems).
Supplier-involved design and development at local or international levels.
Military, commercial, and private sector applications.
Human-modified systems that blend natural and artificial components to
meet human needs.
5. Engineered Systems
Definition
A well-implemented systems engineering approach results in an engineered
system.
Can be human-made or human-modified natural systems with artificial
enhancements.
Characteristics of Engineered Systems
Serve a functional purpose and meet specific user needs.
Exist and operate over a defined lifecycle (from idea to disposal).
Have design momentum – evolve through various phases:
High momentum during design, production, and deployment.
Declining momentum during phase-out, retirement, and disposal.
Optimize design alternatives to achieve end-user requirements efficiently.
6. Summary
Systems engineering is a structured, holistic, and collaborative approach to
designing systems.
It ensures systems are efficient, sustainable, and meet their intended
purpose throughout their lifecycle.
Used in a wide range of industries, from manufacturing to aerospace and IT
systems.
A successful application of systems engineering results in an engineered
system that functions effectively and meets its intended objectives.
3. Key Characteristics of Systems Engineering
1. Top-Down Approach
Starts from high-level requirements and refines into detailed specifications.
Ensures alignment with objectives and user needs.
Prevents missing critical design considerations early in development.
2. Lifecycle Orientation
Covers the entire system lifecycle:
Idea → Design → Development → Deployment → Operation → Maintenance →
Disposal.
Ensures long-term performance and sustainability.
3. Strong Focus on Defining System Requirements Early
Engages stakeholders and end-users early to define needs and functions.
Establishes clear and precise requirements to prevent costly redesigns later.
4. Interdisciplinary Team Approach
Involves experts from different fields working collaboratively.
Ensures all aspects of system development are considered and optimized.
Leverages diverse expertise to create a well-integrated solution.
4. Application Domains of Systems Engineering
Educational systems
Financial services
Transportation systems
Manufacturing and production
Aerospace and marine industry
Urban infrastructure development
Communication and IT systems
Healthcare systems (hospitals, clinics, service industry)
Application Scenarios
Large-scale systems (e.g., space-based systems, urban transport).
Small-scale systems (e.g., custom machines for businesses).
Manufacturing and production systems with complex input-output
relationships.
New product design and advanced technologies.
Modifying existing production using available resources (e.g., transitioning
from outsourcing to in-house production).
Data-intensive and information systems (e.g., inventory tracking, kanban
systems).
Supplier-involved design and development at local or international levels.
Military, commercial, and private sector applications.
Human-modified systems that blend natural and artificial components to
meet human needs.
5. Engineered Systems
Definition
A well-implemented systems engineering approach results in an engineered
system.
Can be human-made or human-modified natural systems with artificial
enhancements.
Characteristics of Engineered Systems
Serve a functional purpose and meet specific user needs.
Exist and operate over a defined lifecycle (from idea to disposal).
Have design momentum – evolve through various phases:
High momentum during design, production, and deployment.
Declining momentum during phase-out, retirement, and disposal.
Optimize design alternatives to achieve end-user requirements efficiently.
6. Summary
Systems engineering is a structured, holistic, and collaborative approach to
designing systems.
It ensures systems are efficient, sustainable, and meet their intended
purpose throughout their lifecycle.
Used in a wide range of industries, from manufacturing to aerospace and IT
systems.
A successful application of systems engineering results in an engineered
system that functions effectively and meets its intended objectives.
Systems Engineering Process Models
1. Waterfall Model
A linear, sequential approach where each phase must be completed before
moving to the next.
Symbolically represented by water flowing from one container to another.
Six Steps of the Waterfall Model:
Requirements Analysis – Gather customer/system requirements, define
project scope, and conduct feasibility studies.
Specifications – Allocate requirements to system components.
Design – Define system architecture, modules, and components.
Implementation – Convert conceptual designs into real code (for software) or
prototypes (for physical systems).
Testing – Validate system performance in real-world scenarios, provide user
training.
Maintenance – Ensure long-term functionality through scheduled updates
and bug fixes.
Example: Capstone project on a Decision Support System (DSS) for analyzing
coffee consumption preferences in Lipa City, following AHP (Analytic
Hierarchy Process).
2. V-Model
A structured, verification-driven approach, emphasizing validation at each
stage.
Commonly used in manufacturing and industrial engineering for high-
precision production.
Divided into two parts:
Decomposition & Definition (Left Side of "V")
Integration & Verification (Right Side of "V")
Each step on the left has a corresponding validation step on the right.
First Step: Define System Requirements
Identify key performance indicators (KPIs), production goals, efficiency levels.
Define technical and functional requirements for the system.
Key Takeaways
Waterfall Model is useful for structured, step-by-step system development.
V-Model integrates validation and verification into each phase.
Both models ensure a well-engineered system by following systematic
approaches.
