SEIP –

Workshop Week 07

Cris Birzer, David Harvey, Kim Harvey

and Dorothy Missingham
Desired outcomes
• Initial Problem definition complete
• Conceptual design started

3
 Problem
definition When we are doing it – Design process

SEIP Conceptual
project Design
scope
Test & evaluation Problem
planning definition

Detailed Design Conceptual

Design

Manufacture and
assembly Detailed
Design

Test & evaluation For detailed design…

refine each sub-system
(recursive approach)
Deployment &
support

Disposal

For overall system 4

 Suggested activities – Problem
definition
• Complete your problem definition including:
- a stakeholder influence map
- a system context diagram
- scenario-based needs analysis to produce a set of needs
• Distil your problem definition into an initial set of
system requirements

5
 How we plan to do it – Methods
Problem definition
Business or
mission • Problem brief review and analysis
analysis
• Research problem context - explore context and key
Stakeholder system issues
needs and
reqts definition • Stakeholder influence map to consider whole problem
human context
• System context diagram to focus on what your system
interacts with
System
requirements • Scenario-based needs analysis to elicit user/stakeholder
definition requirements

• Systems requirements development

– From user needs (high-level system functions)
– From interfaces with other systems (system context)
– System specification structure / category list and brainstorming

6
 Suggested activities – Conceptual
design
• Conceptual design
- Use functional analysis to determine the system functions (see
“Ideas to reality - Architecture” lecture for details)
• Explore different logical / physical architectures in the
solution space to support this behaviour. Utilise the
techniques outlined in the “Ideas to reality -
Architecture” lecture. Seek out further information on
these techniques to help you apply them.
- Consider use of TRIZ techniques, such as:
• “Size-Time-Cost Operator”
• “Notion of Ideal Result”
• “Fields of MATCEMIB”
- Use a morphological table
- Develop at least 4 viable solution concept options
7
 How we plan to do it – Methods
Conceptual design

Architecture • Functional analysis – Determine system functions

definition – Generic function template
– Consider top-down (brainstorm, previous systems, etc.) and
bottom-up (from requirements set)
– Agree on a hierarchy and behaviour
• Explore the solution space – Concept generation (functional
and high-level physical architecture), avoid evaluating
– Research and reverse engineering
– Brainstorming
– Design heuristics – TRIZ
– Morphological tables
• Complete concept designs
– Functional architecture, logical architecture (structure), physical
architecture (layout)
• Select concept
– Multiattribute Value Analysis (MVA)