Systems Engineering Course Lecture 3

College of Science and Engineering
ENGR9742 ONC-TON-S2 2022 Systems Engineering

ENGR9742 ONL-FLN-S2 2022 Systems Engineering
Lecturer: Richard Bowyer
richard.bowyer@flinders.edu.au
Lecture 3:
Stakeholder and system requirements definition.
Cognitive work analysis of workplace.
ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S.
Richard S.Bowyer,
Bowyer 2022
2022
Lecture Outline
• Where are we on the V-diagram?
• Who or what is a stakeholder?
• Stakeholder requirements definition.
• What are Stakeholder requirements? (You would be surprised how
often they do not know what they want)
• Consultative process
• System requirements definition.
• What is the difference between stakeholder and system
requirements?
• Cognitive work analysis of systems and the workplace.
• How does CWA assist us to work out what we need to design?
• Examples of CWA
ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

What you will learn
• A systematic approach to perform requirements
analysis
• An appreciation for succinct formal language protocols
that make for good requirements specifications.
• The importance of a ‘sound’ relationship with your
stakeholder(s) and/or customer(s).
• You will appreciate the necessity to listen to your
stakeholder(s) and codify their wants and requirements
into a list of verifiably correct statements that capture
the definition of the end product.
What you will learn
We shall focus on;
• Understanding what drives requirements.
• The consultation process
• Derivation of requirements from needs-analysis
• The application of strict rules of English grammar
• Cognitive work analysis of the stakeholder product
environment.
• Closing the loop with your stakeholder to verify the
accuracy of the requirements document.
In the last lecture, we considered ethics in the conduct of
the systems engineer and also the ethics that guide
development of a product.
We also looked at standards, and how they set the

parameters on engineering a safe, effective, and fit-for-
purpose system.
Ethics stay with the systems engineer at every moment

and must not become invisible nor secondary at any time.
Why is Requirements Analysis Important?
• The process of determining the requirements for a
project, asking what the stakeholder wants, is the
fundamental starting point of an engineering project.
• A new system, is defined by the requirements analysis.
• This is one of the most critical phases in the systems

engineering, and when done well, minimizes design
changes through the development process.
(Blanchard & Fabrycky, 1990).
Where do Requirements Come From?
• The first stage of the process is direct communication with
the stakeholder.
• Requirements are derived from the NEEDS of the
stakeholder(s).
• You must communicate effectively with your stakeholders.
• You must record the stakeholder’s comments accurately
• If there is any ambiguity in a statement, then clarify
immediately.
• Check the requirements for any inconsistencies or logical
contradictions.
What is a need?
• A need is, among other things, a new business or
operational opportunity in the market-place.
• A need arises from existing business processes that
have reached a limit and ‘need’ expansion to improve
on a business outcome, or a brand-new opportunity.
• Needs are not simply wish statements, although they
may form an important part of generational planning
for improvement of the business ‘bottom-line’.

Characteristics of a ‘Need’
“Before considering the characteristics of well-formed need
statements and requirement statements and the supporting
rules for writing needs and requirements, we define several
fundamental terms, based on the definitions provided in Ryan,
Wheatcraft, Dick, and Zinni (2014).
Many people may want to define needs and requirements for
a service or system, but that need or requirement is not valid
until it is formally agreed-to, baselined, and placed under
configuration management.”
Source: Systems Engineering Principles and Practice, Third Edition. Alexander Kossiakoff,
Samuel J. Seymour, David A. Flanigan, and Steven M. Biemer.
© 2020 John Wiley & Sons, Inc. Published 2020 by John Wiley & Sons, Inc.

Where are we on our journey along the V-diagram?
We have a It takes time treq to gather all the
Project information from the stakeholders that will
Manager in
place at the
define their requirements.
beginning of
out journey. Time invested at this stage, to understand
the stakeholder’s needs, flowing into their
requirements, improves the likelihood of a
successful outcome and reduces re-work in
later system development stages.
treq
There will also be some ‘back and forth’
and feedback of ideas, or suggested
time
changes, with the stakeholder as the
requirements are developed. Richard S. Bowyer, 2022
ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering
Where are we on the NASA System Engine?
You are here

From Stakeholder Needs to System Realisation
Getting To here
from here

Who or what is a stakeholder?
Stakeholders are those individuals or groups who would be
directly or indirectly affected by the proposed project.
Stakeholders may include;
The prime customer with whom the systems engineer interacts

to define the product to be delivered.
Contracted services associated with the stakeholder who are

involved with operational matters with the existing legacy
systems to which the new system is to be an addition.
Who or what is a stakeholder?
These could be, for example, those who will provide life-cycle
support services, operations managers, or component
suppliers.
Whatever the form of the stakeholder, the system engineer

must develop a professional, working relationship that enables
truthful, accurate, and a complete record of the requirements
for the task.

Who are the stakeholders?
Component
Government Suppliers
Economist
Marketing Accountants
who set prices
Stakeholders
Investors Technical
Customers who Managers who

Purchase/use supervise
the product distribution
Community

How do we write system requirements?
The language used to discern the stakeholders requirements
must be clear, unambiguous, technically rich, grammatically
correct, and logically sound.
Why?
If the requirements can be interpreted in more than on way,

then confusion will abound and costs will inevitably soar, while
reputations will diminish.

Interactions with the Stakeholder
How do we keep organised when interacting with

the stakeholder(s)?
Stakeholder expectations must be documented,

and if necessary, managed and modified to achieve
a workable solution.
The expertise of the systems engineer, and the

project manager, are central to a positive outcome.

An Example
The Brief from your stakeholder (customer)
An important part of life is the ability to think clearly in the
morning. For many folks, a hot cup of coffee is a necessary part
of starting their day, to put a spring in their step and to focus their
attention on the tasks of the day. However, the quality of the cup
of coffee has shown to be key in deriving the essential benefits
from the wonderful brew. To this end, the stakeholder has
commissioned your company, the Best-Ever Machine Company,
to design, develop to protype stage, test, and deliver the final
product, the Best-Ever Coffee Machine.
An Example
The Brief from your stakeholder (customer)
Best Ever Coffee Machine

INPUTS OUTPUT
Figure 1: The top-level block (system) diagram based on the ‘brief’.

An example
The requirements analysis is the most important part of this
system development project to produce the best-ever coffee
machine.
Table 1 shows a summary of the stakeholder requirements that
were composed after multiple meetings and conversations
between the stakeholder and team from the best ever ideas
company.
The team comprised a systems engineer, a graphics artist, a
mechanical engineer and a representative of the contracts
department.

An example
Table 1: Requirements for the best-ever coffee machine
Requirement Name of Priority Description /Reason
Number Requirement (Desirability)
Low, Medium,
High
1 Makes best coffee High Coffee is the best ever.
2 Accepts all coffee High All brands of coffee can be processed
beans
3 Portable Med Can move with two people
4 Easy to clean High Essential for hygiene
5 Must be stylish High Must look great in the coffee shop
6 Should be silent Med Not noisy
7 Must be recyclable High Green credentials
8 Energy efficient High Low running cost
9 Should be compact Med Easy to locate in the coffee shop
10 Must be cheap, but High Value for money. Must be able to recoup the
not cheap looking investment in a reasonable time.

An example
Notice that the stakeholder requirements are not particularly
technical, nor are they filled with specifications to guide the
design and development of the product.
It is the job of the systems engineer to translate and

transform the requirements into something useful for
engineering purposes.
The next step then, is to perform a further analysis to

determine the System Requirements.
ANALYSIS OF REQUIREMENTS
The requirements in Table 1 reveal some common ‘needs’ of the
stakeholder.
From this table, a list of system requirements are derived, which
are implied by the top-level requirements and not at all obvious to
the stakeholder. These are shown in Table 2.
For example, requirement 4 implies that all internal parts of the
machine must be accessible.
This was deemed to require access panels on each side of the
machine.
Likewise, requirement 6, though only of medium priority, demands
that any mechanisms function smoothly and with as little noise as
possible. ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022
ANALYSIS OF REQUIREMENTS
It is at this point in the systems analysis, that the engineer
should consult with the stakeholder, to explain the
implications of their ‘wish-list’ and arrive at any mutually
agreeable compromises, if necessary, before further design
work proceeds.
Once the System Requirements are determined, then the

next stage commences, that of mapping system
requirements to the functional requirements for the system.

Mapping Stakeholder Requirements into
System Requirements
Mapping Process
Stakeholder Systems
conducted by the
Requirements Requirements
Systems Engineer

Derived System Requirements for the best-ever
coffee machine
Requirement Name of Derived Priority Description
Low, Medium,
High
1 Correct temp. Filtered High To make the best coffee, every parameter must
water, correct time, be controlled accurately. Operating parameters
correct grinding are defined for use in validation process,
2 Adaptable to state of High Must adapt grinding technique, temperature of
coffee beans water, duration of filtering
3 Use of alloys and Med Materials must be strong, heat resistant
plastic
4 Removable panels High Panels on machine must be removable to allow
for cleaning implements to access all parts.
5 Consult industrial High An industrial designer will create a ‘look’ that
designer satisfies the stylish requirement. Operator
interface is bright and intuitive to use.

Derived System Requirements for the best-ever
coffee machine
Requirement Name of Derived Priority Description
Low, Medium,
High
6 Smooth operation Med Low friction components. Quiet motor and
grinding mechanism.
7 Material used must comply High Materials marked with recycling codes. Design is
with recycling standards convenient to disassemble.
8 Thermal insulation to retain High Energy efficiency demands excellent thermal

heat. Efficient water engineering and electrical control of the heating
heating element. Accurate element
temperature control. Safe,
stand-by mode.
9 Compact footprint Med Compact mechanisms.
10 Industrial designer High Ensure design looks high-class whilst keeping
required within budget.
Requirements Validation
System requirements must be validated. This may be
accomplished by;
1) using an independent organization to apply various

validation methods against various scenarios to ensure the
requirements capture the stakeholder’s needs and objectives.
2) Perform informal validation process involving the

stakeholders to ensure the requirements capture the
stakeholder’s needs and objectives.

Mapping Systems Requirements into
Functional Requirements
Mapping Process
System Functional
conducted by the
Requirements Requirements
Systems Engineer

FUNCTIONAL ANALYSIS
The functional requirements are specified and informed by the
derived system requirements for the machine.
Each system requirement maps to a particular function, such

as, heating the water, crushing the coffee beans, filtering the
coffee, monitoring the temperature, controlling the water
temperature, interfacing with the operator and so on.
The functions define the behaviour of the next stage of

development, instantiation of those functions into hardware,
software, or a combination.
FUNCTIONAL ANALYSIS AND DEFINITION
Consider system requirement 1;
This requires a function that can:
Function(Control water temperature )
a) this requires a closed loop control system with a means of
setting a desired temperature
b) a process is required to control the flow of current through the
heating element
c) A process is required to control the duty cycle of the current
flowing through the heating element
d) A process is required to eliminate or reduce electromagnetic
interference emanating from the machine

FUNCTIONAL ANALYSIS AND DEFINITION
Function(Control the grinding process)
a) A motor control system is required to control the speed
characteristics of the grinder.
b) The state of the grinding mechanism must be observed and
alert the user if maintenance is required.
Function(Interface with the user)
a) A touch display and screen is required to enable various
modes of operation to be selected
Function(Control the filtration process)
a) A quality of water sensing function is required to alert the
user when the water filter needs replacement.
b) A monitor of the filtration efficiency is required
To Summarise
The transformation of Stakeholder requirements into the

functions necessary to fulfill those requirements can be
summarised in a data-flow diagram.

DATA FLOW DIAGRAM OF TRANSFORMATION OF
REQUIREMENTS INTO SYSTEM PROCESS DESIGNS
Stakeholder Stakeholder Stakeholder
Answers Requirements Requirements Requirements
Stakeholders
Interview Requirements
Process Analysis Process
Questions
Function Definition System

System
Process Requirements
Sub-system Functions
Definition Process
System
Functions System
Process System
Designs System Requirements
Requirements
Functions
Process
Designs

Stakeholder Expectations Definition Process
INPUTS TO YOUR OUTPUTS TO
DELIBERATIONS YOUR DESIGN
This is an Include this

important stage diagram in your
in systems report to map
engineering. your design
journey.

Consultation is Key in Systems Engineering
It is extremely important to involve stakeholders in all phases

of a project.
Such involvement should be built in as a self-correcting, self

assessment, feedback loop that will significantly enhance the
chances of mission success.
Involving stakeholders in a project builds confidence in the

end product and serves as a validation and acceptance with
the target audience.
Communications with the Stakeholder(s)
A NOTE OF PROCEDURAL CAUTION:
It is extremely important to involve stakeholders in all phases of a
project.
This does not mean you engage in a ‘micro-management’ process
with the stakeholder(s). It means you ‘sign-off’ on important
decisions that will affect the realisation of the final product.
Such involvement should be built-in as a self-correcting feedback
loop that will significantly enhance the chances of mission success.
Involving stakeholders in a project, builds confidence in the end
product and serves as a validation and acceptance od the evolving
product.
The key objective of systems engineering
• The key objective of systems engineering is to develop a system to
the requirements of the stakeholders and ensure that the system
works as agreed.
• Systems of systems, or joint cognitive systems, are complex and
prone to exhibiting emergent behaviour.
• Things do go wrong, even when all the requirements are achieved.
• Budget and available resources have a lot to do with this, but
ultimately, it is the foresight of the systems engineer that will
avert tragedy and a loss of control.
• Therefore, it is necessary to consider, at an early stage of
development, the various paths that could lead to a loss of control
or some other toxic behaviour.
Losing control of a system
Determinants of control
Source: JOINT COGNITIVE SYSTEMS, Foundations of Cognitive Systems Engineering
Erik Hollnagel, David D. Woods, Published in 2005 by CRC Press
Coffee Break - 10 minutes

Part 2 of lecture
Cognitive Work Analysis (CWA)

But first, a few words about
Cognitive Systems Engineering (CSE)

Cognitive Systems Engineering (CSE)
• A cognitive system is a system that has a human component such
as a decision maker, or it could be a system where the cognitive
thought processes of a human are modelled and applied as part
of a decision and control process
• It can modify its behaviour on the basis of experience.
• Cognitive systems engineering is an approach to complex
cognitive, socio-technical systems, analysis and design that
facilitates the inclusion of human and machine decision
processes.
• CSE is concerned with the behaviour that a system exhibits –
what it does and why it does it.
A great textbook on CWA by Vicente.

A method for analysing the workplace and how
work is done

The five phases of cognitive work analysis.
Planning, adaptation, how
Where things happen How things are controlled
controls are applied and when
The links of influence

The skill set and capabilities between systems
of the systems

CWA for the analysis of complex cognitive
systems
• CWA enables the systems engineer to study and analyse a system.
• CWA is particularly suitable for the analysis of complex cognitive,
socio-technical systems, where humans are a component of the
system.
• An example would be the emergency department of a hospital, where
medical staff and patients interact with each other and with machines
of various types.
• An aircraft carrier is another example of a complex cognitive, socio-
technical system. There are thousands of concurrent processes in
such an environment or workplace.

Let us focus on the workplace for a moment
The workplace is where systems live. In a bank, a hospital, an aircraft carrier, a
steel plant, or a satellite in space.
Many systems interact directly with humans, so-called social-technical

systems, such as automatic tellers.
Some systems are hidden away beyond the reach of most convenient access,
such as a satellite in orbit around the earth.
No system is an island, so an analysis of the workplace, where we deploy our

systems, is vital.
It is important to understand where systems, that we build, inhabit and

function.
Cognitive Work Analysis
• Cognitive Work Analysis (CWA) is described as a formative, constraint-
based framework for analyzing complex sociotechnical systems
(Rasmussen, Pejtersen, & Schmidt, 1990).
• There are three categories of work analysis modeling.
• They are normative (deriving from a standard or norm), descriptive, and
formative (having a profound influence) work analysis modeling
techniques (Vicente, 1999).
• Normative models describe what a user should do when interacting
with a system.
• Descriptive models describe what a user actually does when interacting
with a system.

Cognitive Work Analysis
• Finally, formative models describe what a user could do when
interacting with a system.
• The formative approach can assist in generating new ways of doing work
(Vicente, 1995).
• Traditional work analysis models fall into the normative or descriptive

categories of modeling, which focus on specific tasks and procedures.
• However, CWA identifies the constraints of the work environment and

the operator, the purpose of the system, and the tasks the user can
accomplish within the constraints of the work environment (Fidel &
Pejtersen, 2004).
Types of work analysis
A normative work analysis focus on
Normative analysis identifying the single best way to perform
tasks/work.
The goal is to describe how work is actually
Descriptive analysis performed and it disregards how it is
intended to be done.
Focus lie on identifying requirements and
constraints that define a work system rather
Formative analysis than describing how work should be or is
done. Instead the worker should decide the
best way to do the work.
(Based on Vicente [43]).
There are rules to be obeyed and constraints
to work within

Constraints that act concurrently on the behaviour
of a system
Social and
organisational
Control tasks structure
Work Domain
to be
Structure
performed
Domain of the
System
Strategies Worker competencies,

possible skill, and experience
Ethics and
standards
Work Domain Analysis (WDA)
the capabilities of the system
• The work domain analysis phase identifies and describes the
possibilities and constraints on work conducted within the
work system, independent of situations and can therefore be
used as a way to deal with novelty according to Vicente
(1999)
• WDA is the first phase of CWA, and it is also regarded as one

of most important as it defines the structure and constraints
that workers act on.

Unexpected system behaviour
• According to Naikar et al, when something unexpected occurs in the

workplace (system), that is, irregular behavior of the work system, the
workers will know the bounds and constraints of the work system.
Source: Naikar, N. et al. 2005. Work domain analysis: Theoretical concepts and methodology. Defence Science and Technology
Report. (2005), 104.
• It is often the informal routes of communication (grape vine) and

control that exert themselves by the workers when an emergency
situation arises.

Abstraction Hierarchy (AH)
The result of a WDA
is represented in an
AH and it serves the
purpose of showing
five levels of
constraints

Generic functional abstraction framework
diagram
The bottom level of

the hierarchy shows
each of the physical
objects within the
domain.

An Example - A maritime surveillance system
An integrated maritime
surveillance system combines
satellite-based vessel
detection, transponder-based
vessel identification and
coastal radar vessel tracking
with airborne patrols.
P-8A Poseidon maritime surveillance aircraft

Source: https://defencesa.com/projects/poseidon-maritime-patrol-aircraft/

Abstraction hierarchy of the maritime surveillance system
Reason for existence
Guiding
Principles
Functions
Subsystems that
support functions

The CWA Phases and their Products.
Phase Product
Work Domain Analysis Abstraction-Decomposition Framework

and System Decomposition
Control Task Analysis Decision Ladders
Strategies Analysis Course of Action, Information Flow Map
Social Organization and Cooperation Combination of previous
Analysis
Worker Competencies Analysis Skills, Rules, Knowledge Inventory, high-
level function allocations
WDA is a part of CWA and is used to analyze and define the task environment

Activity Analysis - or Control Task Analysis
One pathway
An example
CTA identifies and describes the cognitive

structures (e.g., knowledge-base
organization and representational skills)
and processes (e.g., attention, problem
solving, and decision making) underlying
job expertise, and the knowledge and skills
required for similar job components.
(Seamster, Redding, & Kaempf, 1997, p. 4)
Sample description of the task of cooking orders by short-order cooks (hierarchical diagram format).

A contextual activity diagram for the home
Time Adapted from [1]
• Combinations of work situations and work functions that are likely to occur in the home.
• The work situations are defined by stages of the day and week (horizontal axis) and the rooms of the home
(diamonds). The work functions are shown in the circles.
• The boxes around the circles on the right side of the diagram indicate that work functions are likely to occur at more
stages of the day on weekends compared with weekdays.

Strategies Analysis - how the goals can be achieved
A SWOT analysis is a strategic planning method used to evaluate the
strengths, weaknesses, opportunities, and threats related to a project or
business venture.
Strengths: internal characteristics of the business
that give it an advantage over competitors
Weaknesses: internal characteristics that place
the business at a disadvantage against
competitors
Opportunities: external chances to improve
performance in the overall business environment
Threats: external elements in the environment
that could cause trouble for the business

• Strategies have been more formally defined as a “category of

cognitive task procedures that transforms an initial state of
knowledge into a final state of knowledge” (Vicente, 1999, p. 9).

Comparison of two strategies to make safe ice-covered roads in Canada.
Strategy 1 Strategy 2
Source: PROCEEDINGS of the HUMAN FACTORS AND ERGONOMICS SOCIETY 52nd ANNUAL MEETING—2008 p265
Demonstrating CWA Strategies Analysis: A Case Study of Municipal Winter Maintenance
Antony Hilliard, Laura Thompson & Cam Ngo, Mechanical and Industrial Engineering, University of Toronto, Canada

Social Organisation and Cooperation Analysis - how the
work demands of the system can be allocated among human
and machine actors to achieve the task
• The Social Organisation and Cooperation Analysis (SOCA) phase of
CWA examines which system entities currently do a task/action, and
who could possibly do a task/action, given the constraints of the
system (possibilities).
• The important point is that entities can be both humans and non-
humans (e.g. technologies, artefacts).
• SOCA aims to identify how functions are currently allocated and to
determine the possibilities for new and different allocations of
functions to be made is needed.

Worker Competencies Analysis - what skill-based, rule-
based, and knowledge-based competencies are necessary for
workers to meet the relevant work demands effectively
• WCA focuses on the competencies that workers need to deal
effectively with the work requirements of a system [1].
• SOCA focuses on which entity is capable of performing a task
and how the work can be it can be effectively distributed and
coordinated.
• Humans possess certain competencies, and the machines with
which they interact, at some level, also possess competencies,
or more usually called capabilities.
[1] PROCEEDINGS of the HUMAN FACTORS AND ERGONOMICS SOCIETY 50th ANNUAL MEETING—2006 447
AN EXAMINATION OF THE KEY CONCEPTS OF THE FIVE PHASES OF COGNITIVE WORK ANALYSIS WITH EXAMPLES FROM A FAMILIAR SYSTEM
Neelam Naikar, Defence Science and Technology Organisation (DSTO) Melbourne, Australia

Next time, all about;
System architecture and concept generation.
Model-based Systems Engineering.
Modelling techniques and languages

Systems Engineering Course Lecture 3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Systems Engineering Course Lecture 3

Uploaded by

Copyright:

Available Formats

College of Science and Engineering

ENGR9742 ONC-TON-S2 2022 Systems Engineering

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

We also looked at standards, and how they set the

Ethics stay with the systems engineer at every moment

• A new system, is defined by the requirements analysis.

• This is one of the most critical phases in the systems

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Stakeholders may include;

The prime customer with whom the systems engineer interacts

Contracted services associated with the stakeholder who are

Whatever the form of the stakeholder, the system engineer

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Customers who Managers who

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

If the requirements can be interpreted in more than on way,

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

How do we keep organised when interacting with

Stakeholder expectations must be documented,

The expertise of the systems engineer, and the

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Best Ever Coffee Machine

Figure 1: The top-level block (system) diagram based on the ‘brief’.

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

It is the job of the systems engineer to translate and

The next step then, is to perform a further analysis to

Once the System Requirements are determined, then the

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

8 Thermal insulation to retain High Energy efficiency demands excellent thermal

1) using an independent organization to apply various

2) Perform informal validation process involving the

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Each system requirement maps to a particular function, such

The functions define the behaviour of the next stage of

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

The transformation of Stakeholder requirements into the

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Function Definition System

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

This is an Include this

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

It is extremely important to involve stakeholders in all phases

Such involvement should be built in as a self-correcting, self

Involving stakeholders in a project builds confidence in the

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

The links of influence

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022

Many systems interact directly with humans, so-called social-technical

No system is an island, so an analysis of the workplace, where we deploy our

It is important to understand where systems, that we build, inhabit and

ENGR9742 ONC-TON-S2 + ONL-FLN-S2 2022 Systems Engineering Richard S. Bowyer, 2022