0% found this document useful (0 votes)
68 views17 pages

Livestock Monitoring System Design Guide

This document provides guidance for completing the conceptual design phase of a project. It outlines desired outcomes including having a conceptual design that explores system functions and structure to meet requirements. It suggests activities such as using functional analysis to determine system functions and exploring different architectures. Developers are encouraged to consider TRIZ techniques and develop at least four solution concepts. Selection criteria should be established to select a preferred system option using a method like multi-attribute value analysis. The document includes an example conceptual design for a livestock monitoring system and suggests ways to develop views of the problem from the perspectives of stakeholders, system context, user needs, and functional requirements.

Uploaded by

Little Yuhee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
68 views17 pages

Livestock Monitoring System Design Guide

This document provides guidance for completing the conceptual design phase of a project. It outlines desired outcomes including having a conceptual design that explores system functions and structure to meet requirements. It suggests activities such as using functional analysis to determine system functions and exploring different architectures. Developers are encouraged to consider TRIZ techniques and develop at least four solution concepts. Selection criteria should be established to select a preferred system option using a method like multi-attribute value analysis. The document includes an example conceptual design for a livestock monitoring system and suggests ways to develop views of the problem from the perspectives of stakeholders, system context, user needs, and functional requirements.

Uploaded by

Little Yuhee
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

SEIP –

Workshop Week 08

Cris Birzer, David Harvey, Kim Harvey


and Dorothy Missingham
Desired outcomes
• Conceptual design complete
- Explore system functions to meet the requirements and
system structure to support the functions
- Identify and describe at least four system options
- Use a systematic approach to select a concept to
develop further

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 – 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”
- Develop at least 4 viable solution concept options
5
Suggested activities – Selection
• Select preferred system option
- Develop selection criteria by revisiting problem statement,
looking for key requirements / constraints and thinking
about other important issues such as ergonomics,
aesthetics, ease of manufacture, cost, development risk,
schedule risk, training needed, safe disposal, etc. Develop
at least 5 selection criteria (will need to describe and
justify in your report)
- Use the MVA selection method to determine the most
appropriate option to move forward with

6
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)

7
EXAMPLE…

8
Project – Livestock Monitoring System Design

• Graziers have
asked for a solution
for monitoring
livestock,
the presence of feral
animals and the
status of their
fences

• We have been
tasked to conduct a
conceptual design
for a system that
meets the Graziers’
needs
9
Project – Livestock Monitoring System Design

• Graziers have
asked for a solution
for monitoring
livestock,
the presence of feral
Monitor Livestock animals and the
status of their
fences
Monitor
Fence
• We have been
Monitor the
tasked to conduct a
presence of conceptual design
feral animals for a system that
meets the Graziers’
needs
10
People view – Stakeholder influence map

• Each stakeholder group will have an influence on the other


stakeholders, and by extension, the project. Make sure to get to the “so
what?”, explaining what this means for your project approach / system
design.

11
System view – System context diagram

• Show the external entities that the system will interact with, giving the
first indication of required interfaces and interactions.

12
User view – Scenario-based needs analysis

• Structured way to describe what the user wants to be able to do, and
determine what they need from the system at each step. Make sure to describe
the scenario context.

13
Problem definition – User view

• Use the scenario and other provided information to define the problem
in user / stakeholders terms.

ID Description Source
UN01 The device shall be able to fly Needs Analysis

UN02 The device shall monitor the owners live stock Needs Analysis

UN03 The device shall monitor the presence of feral animals Needs Analysis

UN04 The device shall monitor the status of owner fences Needs Analysis

UN05 The device shall be electric powered Statement of Need

UN06 The device shall recharge from 230v 50 Hz single phased power Statement of Need

UN07 The device shall have a flight time of 1 hour or greater Statement of Need

UN08 The device shall be transported on a trailer no bigger than 2.4 metres long and 1.8 metres wide Statement of Need

UN09 The device shall be ready for flight 15 minutes or less from the commencement of unloading Statement of Need

UN10 The device shall be ready for departure in 15 minutes of less from the commencement of disassembly Statement of Need

UN11 The device shall be operatable by one person for flight preparation, flight, post flight Statement of Need
Problem definition – System view
• Define the problem in systems terms, to which you can actually develop
a design. Ensure that these requirements trace to your problem
definition.
Consider arranging requirements in categories…

– Start with needs


then develop Beware of using traceability of You can also include a
requirements “Derived”. Aim to link each column for criticality
requirement to an element in your (or priority) of each
– Requirements categories problem definition, an external requirement –
(start with reference (such a legislation) or Essential, very
categories, brainstorm some simple calculations (maybe important, important,
requirements) in an annex) desirable
Functional analysis – Generic functions

16
Functional analysis – Functional architecture (hierarchy)

17
Synthesis – Morphological table

• Two candidate designs developed using a morphological


table

18

You might also like