ECE362 Principles of Design High Level Design - Rose

ECE362
Principles of Design
High Level Design
and
PDS
Session 3
Page 1
1
High Level Design
Stage 1 – Needs,
System Definition, &
PDS or Requirements
Specification
Needs and
Marketing
System
Definition
Requirements
Specifications
Stage 2 – Design
High Level
Design
Conceptual
Design
Detail
Design
Test
Verification
Reporting
Sales
Distribution
Stage 3 – Test,
Verification, & Reporting
Stage 4 –Manufacturing,
Manufacturing
Sales, & Distribution
This process is part of what
we call Systems Engineering
ECE362Lec2_app2_W04.ppt
Session 3
Deliver Product = $$$
Page 2
2
Sample HLD and PDS
Formulate a High Level Design document and a
Product Design Specification for a residence
hall room for a single resident.
ECE360ResidenceHallPDS.pdf
HighLevelRequirements&PDSDormRoomExam
ple.pdf
Session 3
Page 3
3
Features of a PDS
•Basis for all design decisions
•May serve as a contract
•Dynamic rather than static
•Considers all aspects of the product
and it’s interactions
•Good PDS => Good design
•Include all aspects at beginning, even if
at a superficial level
•More details as project progresses
Session 3
Page 4
4
Elements of a PDS
•
•
•
•
•
•
•
•
Performance
Environment
Service Life
Maintenance and repair
Target Product Cost
Competition
Shipping
Packaging
Session 3
Page 5
5
Elements of a PDS
•Quantity
•Manufacturing Facility
•Size
•Weight
•Aesthetics, appearance and finish
•Materials
•Production Life Span
•Standards and specifications
Session 3
Page 6
6
Elements of a PDS
•Ergonomics
•Customer
•Quality/Reliability
•Shelf-Life
•Processes
•Time-scales
•Testing
•Safety
Session 3
Page 7
7
Elements of a PDS
•Company constraints
•Market constraints
•Patents, literature, product data
•Political and social implications
•Legal
•Installation
•Documentation/Training
•Disposal
Session 3
Page 8
8
Guidelines for a PDS
•
PDS represents what you are trying
to achieve, not the achievement
itself.
•
PDS is for you and your colleagues;
it should be written succinctly and
clearly.
Session 3
Page 9
9
Guidelines for a PDS
•
Never write a PDS in essay form; use
short, sharp definitive statement;
leave space for amendments.
•
From the beginning quantify
parameters, even when they are
estimates.
Session 3
Page 10
10
Guidelines for a PDS
•
Always date the PDS and put an
issue number on it.
• Clearly document amendments.
• To gain flexibility, each time start
preparing a PDS starting from a
different specification.
More details on PDS @
PDS_Guidelines.pdf
Session 3
Page 11
11
Assignment – Due Mon, Dec 8
INDIVIDUAL ASSIGNMENT – Quiz on Friday over
system engineering, requirements specifications, and
high level design.
TEAM ASSIGNMENT – Complete an HLD for an ECE
laboratory located in C115 to be used for the following
courses:
–
–
–
ES203
ECE200
ECE250
TEAM ASSIGNMENT – Complete a PDS for the ECE
laboratory on Thursday, Dec 11.
Session 3
Page 12
12