Chapter 3

Need Analysis
Instructor: Dr. PHAN THỊ MAI HÀ

09 / 2021
 NEED ANALYSIS
3.1 Introduction
3.2 Operation analysis
3.3 Functional analysis
3.4 Feasibility analysis
3.5 Need validation
3.6 Stakeholder requirement document

SE – C3: Need analysis 2

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction
Need analysis:
Create conditions for a new system;
Proven feasibility of meeting needs at acceptable costs and
risks
Not follow in a specific structure or time
Answer the questions;
Why do we need a new system?
What capabilities does the new system represent?
How can that capability be guaranteed?

SE – C3: Need analysis 3

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction
The starting point of the need:
For example, the vehicle
Two directions of need: is subject to emission
Demand-driven system; control according to the

technology oriented system new standard

Deficiency in Operation
operation requirement

Need analysis

New
technology New system
opportunities

SE – C3: Need analysis 4

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction
The starting point of the need:
Need analysis phase in system life cycle:

SE – C3: Need analysis 5

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction
Systems engineering method in Need analysis:
Input come from different sources
Same four steps of system engineering method
Operation analysis – requirements analysis
Functional analysis – functional definition
Feasibility definition – physical definition
Needs validation – design validation

SE – C3: Need analysis 6

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

2. Operation analysis
Object: addressed is the existence of a valid need (potential
market) for a new system.
Analyze (1) Operation; (2) Maintenance; (3) support systems
In the commercial sector, market studies are continuously carried
out to assess the performance of existing products and the
potential demand for new products. The strengths and
weaknesses of competing systems and their likely future growth
are analyzed.

SE – C3: Need analysis 7

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

2. Operation analysis
Analyze from:
1. Deficiencies in Current Systems
❖ In virtually all cases, the need addressed by a projected new system
is already being fulfilled, at least in part, by an existing system
✓ detailed identification of the perceived deficiencies in the current
system
✓ continually extrapolate the conditions in which the system operates
and re-evaluate system operational effectiveness in the life
2. Obsolescence:
❖ Reason: operating environment may change, current system become
too expensive to maintain, the parts necessary for repair may be no
longer available, competition may offer a much superior product, or
technology may have advanced to the point where substantial
improvements are available for the same or lower cost
SE – C3: Need analysis 8
Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

2. Operation analysis
Definition of Operational Objectives
balance between operational performance and technical risk, cost,
and other developmental factors
specific, complete, and quantitative as practicable, even though
their initial values may be changed numerous times

SE – C3: Need analysis 9

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

3. Functional analysis
Object: an extension of operational studies, directed to
establishing whether or not there may be a feasible technical
approach to a system that could meet the operational objectives
Translation of Operational Objectives into System Functions
❖ carry out certain actions in response to its environment that would
meet the projected operational objectives
❖ May use operation of current system to image new system
❖ Approach: consider the type of primary media (signals, data,
material, or energy) → physical subsystem as sensor, computer,..
❖ visualize the entire system life cycle, including its non-operational
phases
Allocation of Functions to Subsystems

SE – C3: Need analysis 10

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

4. Feasibility analysis
The feasibility of a system concept based on:
❖ functional design
❖ physical implementation
❖ external constraints and interactions, including compatibility with
other systems
Consider:
❖ Relation to current system or application of advanced technology
❖ Assessment of cost

SE – C3: Need analysis 11

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

5 . Need validation
Operational effectiveness model
To animate the engagements between the system model and the
scenarios, an effectiveness model is designed with the
capability of accepting variable system performance
parameters from the system model.
System performance parameters: values of performance
characteristics that define the system’s response to its
environment → MOE - measures of effectiveness

SE – C3: Need analysis 12

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

5 . Need validation
Validation of Feasibility and Need
The effectiveness analysis described above is mainly directed
to determining whether or not a system concept, derived in the
functional and physical definition process, is (1) feasible and
(2) satisfies the operational objectives required to meet a
projected need.

SE – C3: Need analysis 13

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

6. SRD (Stakeholder Requirement Document)

Result of need analysis
Other name: operational concept document, concept of
operations document, system design document
SRD :
❖ System’s mission and application
❖ System operation function, constraint
❖ Boundary
❖ Support and environment concept
Should be written by users’ language

SE – C3: Need analysis 14

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Stakeholder definition
▪ Stakeholder
▪ Payer
▪ User
▪ Professor
▪ System designer

▪ Recursive approach
▪ Initial stakeholder →
second stakeholder

SE – C3: Need analysis 15

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Some constraint of project

Company constraints:
❖ Organizational policies, procedures, standards, or
guidelines on how to develop the company's system, its
customers
Constraints from the project: Project resources, time
constraints, project reporting regulations
External constraint:
❖ Industry, national, international standards

❖ Laws and conventions

❖ Communicating with other systems

SE – C3: Need analysis 16

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Structure of SRD
Scope: Name – general about system
❖ System scope or project
❖ design constraints
❖ interface with external systems
❖ system boundary
Referenced document
Operations: requirement of stakeholders
Operation need: mission
System overview: interface, boundary, system operation
states
Operation environment and support
SE – C3: Need analysis 17
Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Context diagram

SE – C3: Need analysis 18

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Complete and approved SRD

Complete SRD through: seminars, surveys, interviews, models...Note
that the opinions of all stakeholders should be collected
Approve SRD: Important step to take before moving on to the next
step
Traceability:
❖ Forward traceability: each SRD request will be traced to at least
one system request. For example: top amenities → inflight
entertainment
❖ Backward traceability: each system request will trace back to at
least one stakeholder requirement. Example: accommodates 100
passengers → midsize aircraft
❖ Traceability ensures that the system meets the needs of the
customer as there is no redundant function
SE – C3: Need analysis 19
 Term project – Need analysis
Identify stakeholders involved in the system: multiple groups, specify how to
find these stakeholders.
Planning stakeholder outreach and information collection
Set up questionnaires for each stakeholder
Conduct interviews and analyze data
Convert analysis information into system requirements (logic, compatibility,
etc.)
Determine the constraints of the system as well as the environment
Build system function
Feasibility analysis of these functions in the form of giving a response
Pay attention to the feasibility analysis of response solutions and efficiency
scales
SE – C3: Need analysis 20