Systems Engineering

and Design 3B

Module: 1
The Systems Engineering Introduction

The Design Process

Course strategy.
It is impossible to fully cover and explain every detail of all the different
systems analysis and design tools, techniques, principles, and
methodologies in a single course.
We will rely on Paretos 80 : 20 rule.
For most the knowledge of a relatively small subset (20%) of the
underlying concepts and terminology is sufficient to understand the lions
share (80%) of the topics functionality.
The objective is to explain that crucial 20%.
"Education helps one cease being intimidated
by strange situations."
Maya Angelou

The Design Process

Course strategy.
"Imagination is more important than knowledge.
Knowledge is limited. Imagination encircles the world."
Albert Einstein
Your value as an Engineer is measured by the size of the problems you
are willing to undertake.
- Dr John Tibane motivational speaker

The Design Process

What is the difference between:
High performance super
Car engineering

Prostitution

The Design Process

Let us look at the common points:
High performance super
Car engineering

vs

Prostitution

Produce pleasure
May become additive
Marketed by advertising of high performance features
Additional safety devices required for safe operation
Can be lethal
Create a sense of false empowerment to user
Can destroy moral values (entices to break commitments)

The Design Process

Unless the engineer is practicing his

trade for the benefit and uplift mend of
society his trade is not much different to
prostitution.

The Design Process

Finding the optimal peg for the right hole.

The Solution

The Problem

Unless we know what the hole looks like we

will not recognise when the peg fits

The Design Process

The Basic Design Process

The Design Process

Systems Engineering is the method for

applying the Design Process to
engineering projects.

The Engineering Domains

The Problem
Domain

The Solution
Domain

The Management
Domain

The Implementation
Domain

10

The Problem Domain

The Problem
Domain

A statement of What is to be done

Define the hole

In the problem domain the user/client expresses a specific need or

want.
The problem domain contains the user needs/wants and the
environment of the potential solutions.
What must the solution be capable of doing to be considered as a
solution?
What must the solution not be capable of doing to be considered
as a solution?
What are the interfaces of the solution?
What must the solution attributes be to be considered as a
solution?

11

The Solution Domain

The Solution
Domain

An statement of How it is to be done

Define the peg

In the problem domain the user/client expresses a specific need or

want.
The problem domain contains the user needs/wants and the
environment of the potential solutions.
How will the solution function?
How will the solution not function? Constraints, Limitations
How will the solution domain interface to the problem domain?

12

The Implementation Domain

The Implementation
Domain

The manufacturing of the solution

TBD

13

The Management Domain

The Management
Domain

The managing the solution

Project Management
Technical Management

14

The Problem Domain

Input
Users needs/wants
Users Constraints
Budgetary
Financial
Time
Technology
Others

User Goals Document

All stakeholders
requirements
Legal requirements
Regulatory
requirements
Environmental
requirements

Process

Agreement
Processes

Output

User Goals
Document
What is to be done

Requirements
Engineering
Processes
Design
Process

User
Requirement
Specification
User
Acceptance
Procedure
User
Operational
Description
What is to be done
15

The Solution Domain

Input

User Requirement
Specification

Process

Requirements
Engineering
Processes
Design
Process

What is to be done

Output
System
Development
Specification
System
Architecture
Diagram
System
Interface
Control
Document
System
Acceptance
Procedure
System
Operational
Description
How it is to be done
16

The Implementation Domain

Input

System Development
Specification
System Architecture
Diagram
System Interface
Control Document
System Acceptance
Procedure
System Operational
Description

What is to be done

Process

Requirements
Engineering
Processes
Design
Process

Output

SubSystem /
Component
Development
Specification
Sub-System /
Component
Interface
Control
Document
Sub-System /
Component
Acceptance
Procedure

How it is to be done
17

The Management Domain

Input

Process

Contract

Engineering
Processes

What is to be done

Output

Systems
Engineering
Management Plan
Verification and
Validation Plan
Configuration
Management Plan
Risk Management
Plan
Qualification and
Certification
Management Plan

How it is to be done
18

The SE Process

19