Engineering Strategies and Practice

ESP Assignment Guide Winter 2016

Image from S. McCahan et al. Designing Engineers: An Introductory Text. Hobboken, NJ: Wiley, 2015.
Page 355

Engineering Strategies and Practice

Table of Contents
Introduction ..................................................................................................................... 3
Learning objectives for the documents and presentations .............................................. 3
Detailed instructions for sections of the reports............................................................... 4
Basic components ....................................................................................................... 4
The Conceptual Design Specification (CDS) adds the following sections ................... 5
In ESP I, the following section is added: ...................................................................... 5
In ESP II, the following sections are added: ................................................................ 5
The Final Design Specification (FDS) does not include Alternative Designs but goes
into more detail on the Proposed Conceptual Design. ................................................. 5
Basic Components .......................................................................................................... 5
Cover Page (template posted) ........................................................................................ 6
Executive Summary ........................................................................................................ 6
1.0

Project Requirements ............................................................................................ 6

1.1

Problem Statement ............................................................................................ 7

1.2

Identification of Stakeholders ............................................................................. 7

1.3

Functions ........................................................................................................... 7

Note on Functional Basis ............................................................................................. 8

1.4

Objectives .......................................................................................................... 8

1.5

Constraints ......................................................................................................... 8

Measurability of Requirements - a special note ........................................................... 9

1.6

Service Environment .......................................................................................... 9

1.7

Client Ethics and Values (ESP II) ..................................................................... 10

2.0 Project Management Plan (ESP II).......................................................................... 10

3.0 Conclusion .............................................................................................................. 11
4.0 Reference List ......................................................................................................... 11
Appendices ................................................................................................................... 12
The Conceptual Design Specification (CDS) adds the following sections ..................... 12
2.0 Alternative Designs .............................................................................................. 12
2.1 2.5
3.0
1

Alternative Designs <insert name of individual design> ...................... 13

Proposed Conceptual Design ....................................................................... 13

Engineering Strategies and Practice

3.1
Proposed Conceptual Design - Name of Design <insert name of the
recommended design>........................................................................................... 13
3.2

Metrics (ESP I) .......................................................................................... 14

3.2

Plan for Detailed Design (ESP II) .................................................................. 14

3.3 Outstanding Decisions (ESP II) ........................................................................ 14

3.4 Preliminary Implementation Requirements (ESP II) ......................................... 14
3.5 Preliminary Environmental Impact (ESP II) ...................................................... 15
3.6 Preliminary Human Factors (ESP II) ................................................................ 15
3.7 Preliminary Social Impact (ESP II) ................................................................... 15
3.8 Preliminary Economics (ESP II) ....................................................................... 15
3.9 Preliminary Test Plan (ESP II).......................................................................... 15
The Final Design Specification (FDS) (ESP II) .............................................................. 16
Disclaimer .................................................................................................................. 16
2.0 Detailed Design ................................................................................................... 16
2.1 Regulations, Standards, and Intellectual Property ........................................... 17
2.2 Testing ............................................................................................................. 17
2.3 Implementation Requirements ......................................................................... 17
2.4 Life Cycle and Environmental Impact ............................................................... 18
2.5 Human Factors................................................................................................. 18
2.6 Social Impact.................................................................................................... 18
2.7 Economics........................................................................................................ 18
Lessons Learned and Strategy (LLS) ............................................................................ 19
Oral Presentations......................................................................................................... 20
Seminar presentation (ESP I)........................................................................................ 20
Design Review Gateway (DRG) (ESP II) ...................................................................... 21
Outline form ........................................................................................................... 21
Final Presentation (ESP II) ............................................................................................ 22

Engineering Strategies and Practice

Introduction
This guide refers to the following cycle of graded assignments in ESP:
Team Documents (to be submitted to client):
Project Requirements (ESP I)
Project Requirements & Project Management Plan (ESP II)
Conceptual Design Specification (ESP I & II)
Final Design Specification (ESP II)
Individual assignment:
Lessons Learned & Strategy (ESP II)
Oral Presentations:
Seminar Presentation (ESP I)
Design Review Gateway in-tutorial presentation (ESP II)
Final presentation (ESP II - client is invited)

Learning objectives for the documents and presentations

Learning objectives evaluated in your documents and presentations represent design,
team work, project management and communication. The last is the key to
demonstrating your ability with the other learning objectives. Your reports and
presentations provide the evidence that you have understood and can apply the tools
and methods discussed in the textbook and in lecture.
Over your four year (five with PEY) undergraduate program, you are expected to
develop the following five engineering communication abilities. At graduation, you
should be able to demonstrate a superior ability to:
1.
2.
3.
4.
5.

Structure a logical argument in an engineering context

Organize communication for an intended audience
Develop clear, correct, and cohesive sentence and paragraph structures
Deliver oral communication effectively to an intended audience
Create clear and appropriate visuals to represent engineering ideas

Specifically, by the end of ESP, you should be able to:

Identify and represent multiple perspectives in an engineering design problem

Identify bias in both information sources and your own communication
Generate a number of equally valid solutions to a design problem
Generate criteria to evaluate your solutions to a design problem
Gather, evaluate and appropriately utilize information from a variety of sources
Apply an audience analysis so that your communication is appropriate for the
intended audience
Communicate key information to a client through a short report that is well
organized and professional in tone
Work with a group to create a unified document resulting from synergistic team
interactions

Engineering Strategies and Practice

Support statements with explanations and evidence that makes use of

appropriate scientific principles or published research
Document research appropriately
Iterate by revising content from previous document(s) as applicable
Utilize an engineering notebook usefully
Organize paragraphs logically
Organize sentences logically
Proof-read and correct your writing for major errors in spelling, grammar, syntax
and usage
Produce and use a work breakdown structure, several forms of activity network
diagram and a Gantt chart for project management
Work with common graphical and program-based methods of displaying,
planning and controlling a project
Carry out an oral presentation that is professional in tone and substance
Identify the design decisions and strategies as presented in the course that went
into the project

Detailed instructions for sections of the reports

All reports begin with some basic elements. These are first presented in the Project
Requirements (ESP I)/Project Requirements & Project Management Plan (ESP II) and
are subsequently revised in the Conceptual Design Specification (CDS) (ESP I & II) and
Final Design Specification (FDS) (ESP II). The revisions incorporate new information
from the client as well as instructions and suggestions from the TA, PM (ESP II) and CI.

Basic components
Cover Page (posted template)
Executive Summary
1.0 Project Requirements
1.1. Problem Statement
1.2. Stakeholders
1.3. Functions
1.4. Objectives
1.5. Constraints
1.6. Service Environment
1.7. Client Ethics and Values (ESP II)
2.0 Project Management Plan
3.0 Conclusion/Recommendation
4.0 Reference List (IEEE format)
Appendices
Attribution Table: In addition to the required content for the CDS, a hard copy of the
attribution table must be completed and signed by ALL team members. This attribution
table must be submitted to the Teaching Assistant (TA) in the tutorial of the assignment
deadline. It does not have to be included in Google Docs.

Engineering Strategies and Practice

The Conceptual Design Specification (CDS) adds the following

sections
2.0 Alternative Designs, (including the one to be presented as Proposed Conceptual Design)
2.1. <Insert Name of Design 1>
2.2. <Insert Name of Design 2>
2.3. <Insert Name of Design 3>
2.4. <Insert Name of Design 4>
2.5. <Insert Name of Design 5>
3.0 Proposed Conceptual Design
3.1. Proposed Design - <Insert Name of Proposed Conceptual Design>

In ESP I, the following section is added:

3.2 Metrics

In ESP II, the following sections are added:

3.2. Plan for Detailed Design
3.3. Outstanding Decisions
3.4. Preliminary Implementation Requirements
3.5. Preliminary Life Cycle and Environmental Impact
3.6. Preliminary Human Factors
3.7. Preliminary Social Impact
3.8. Preliminary Economics
3.9. Preliminary Test Plan

The Final Design Specification (FDS) does not include Alternative

Designs but goes into more detail on the Proposed Conceptual
Design.
2.0 Detailed Design
2.1. Regulations, Standards, and Intellectual Property
2.2. Testing
2.3. Implementation Requirements
2.4. Life Cycle and Environmental Impact
2.5. Human Factors
2.6. Social Impact
2.7. Economics
2.7.1. Market Issues (optional)

Basic Components
The following basic components are required in most documents. However, these
requirements vary slightly from course to course, term to term. When in doubt check the
actual Assignment Instructions, posted on the course website. They will provide the
most authoritative and up-to-date requirements for sections of the document for which
you will be responsible.

Engineering Strategies and Practice

Cover Page (template posted)

All fields MUST be filled in: project number, project title, date, client information, design
team names in full and student numbers. Ensure that all names are spelled correctly,
including Client organization, Client contact person, Project Manager, TA and
Communication Instructor. Use the cover page template provided.
Note: It is not possible in Google Docs to remove a specific page from the automatic
page number tool. Therefore you will not be penalized for having a page number on
your Cover Page. To submit the document to your client, you should export it to Word or
another word processing program and then correct all formatting. Remove page number
from the Cover Page before the document goes to the client.

Executive Summary
An Executive Summary is a short, detailed synopsis of your report. The final version
should not exceed one page. The purpose of the Executive Summary is to condense
the entire report such that a reader should finish it knowing the basic information about
the project. Only an interested reader needs to read more.
Important decisions about your project may be made based on the Executive Summary
alone. Therefore, it must be complete, clearly and precisely written, and cover the most
important points made in the most relevant sections of your report. Write the Executive
Summary after you have finished the rest of the report.
Executive Summaries are generally written in paragraph form, but may contain bullet
and/or numbered lists. The opening, however, should be in paragraph form. An
Executive Summary is an independent document attached to a report; therefore, it
should not have a page number or a header number or internal citations [numbers in
square brackets].
Note: It is not possible in Google Docs to remove a specific page from the automatic
page number tool. Therefore you will not be penalized for having a page number on
your Executive Summary. To submit the document to your client, you should export it to
Word or another word processing program and then correct all formatting. Remove
page number from the Executive Summary before the document goes to the client.

1.0 Project Requirements

Between a heading and a subheading, you should have a brief paragraph introducing
the section. Between 1.0 Project Requirements and 1.1 Problem Statement, you can
introduce the project, the client and any high level information that is not specifically part
of the problem. Project Requirements serve as a contract between you and your client
and gives a complete solution-independent engineering definition of the project for
which you are designing a solution.
Requirements are covered in Part 2 of Designing Engineers Design Process
(Chapters 2 8 in WileyPLUS)
6

Engineering Strategies and Practice

1.1

Problem Statement

The problem statement describes your clients need in engineering terms and includes
any relevant background information that you have discovered through research. This is
NOT merely a rewording or paraphrasing of the statement the client gives you; this is
the problem in the design engineers own words. It indicates the scope of the problem
and describes the gap in the world that your client is seeking to fulfill with the solution.
It is vital that you figure out the client need BEFORE you begin writing the problem
statement. This is actually the most important part of the assignment. Consider, as you
create the problem statement, the functional basis of the design. To be successful in
this assignment you must be solution independent, NOT solution driven (offering or
implying a solution before fully defining the problem). To be successful in this
assignment you must have references other than the client statement.

1.2

Identification of Stakeholders

Stakeholders are people or organizations that have a stake or interest that will be
affected by the design you are creating. A stakeholder interest is stakeholders
connection to the design: it is an aspect of their business, holdings or existence that will
be affected, positively or negatively, by the design. An interest implies that there may be
benefit or loss. (A stakeholder may be hostile to the whole idea of the design and want
to prevent it.) The interest should be stated independent of the design. Any claim
about the stakeholder interest should be supported by research.
A table is best for this section. It should show the Stakeholder, Interest and impact
which defines the connection between the stakeholder interest and an aspect of the
design (function, objective or constraint). You may create a kind of shorthand to save on
words e.g. C1 to refer to Constraint 1.
This section should include all stakeholders, and their respective interests. However,
although the client, user and design team are the most obvious stakeholders, as a
matter of convention they are NOT included in this list. Rather, the list should show all
other relevant individuals or organizations.

1.3

Functions

What the design should do, including:

Primary functions the design is to perform (required)
Secondary functions that enable or result from the primary functions (if
appropriate)
Unintended functions/uses (if appropriate)

Functions are normally verbs i.e. the design will store energy. Other word forms such
as nouns or adjectives are not acceptable. Do not write the design will be for the
storage of energy. (Note, using the appropriate word form for functions reduces the
word count by almost 50%.)
7

Engineering Strategies and Practice

Note on Functional Basis

The Project Requirements must contain a statement defining the Functional Basis of the
design. Basically, it identifies the way the design will control mass, energy or
information. As such, it is almost a formula: The functional basis of this design is to
(verb from the following verb list) (mass, energy or information).
Example: The functional basis of this design is to parse information.
Verb list for statement of functional basis
Choose 1 of the following verbs specifying control:

Sense, detect, indicate, identify

Support, maintain, secure, steady, hold constant
Combine, connect, join, mix, merge, bond
Separate, split, detach, parse
Store, deposit, place
Extract, remove, mine, retrieve, recover
Transport, transmit, convey, move, channel, rotate
Transform, convert, alter, modify, adapt

1.4

Objectives

What the design should be, including:

Physical, financial, environmental, social and performance objectives for

the design
Goals and metrics for these objectives

An objective is identified by should be coupled with an adjective or descriptive phrase.

For example: The product should be less than 5 kg. for portability. (This is a case in
which less than 5 kg. is not a constraint, but rather a goal set for the objective.)

1.5

Constraints

What the design must be, including:

Strict requirements for the design

May be functional, physical, financial, environmental, social or
other as would be relevant to the project

A constraint will be identified by shall coupled with a definitive and testable limit.

For example: The product shall weigh less than 10 kg.

Constraint statements identify mandatory requirements that the design must meet and
commit the designer to meeting the specification. If the constraint is not met, the system
may have to be re-designed at the expense of the designer to meet the tolerance.

Engineering Strategies and Practice

Measurability of Requirements - a special note

For a design to be considered at all, it must meet the functional requirement. It must
"do" the function. This determination is generally done at a high level and often
qualitatively.
Objectives and constraints on the other hand are used to rank better and worse
designs. Therefore, each should have a clear measure of success a metric. For some
metrics, simple measurement is all that is required, such as a physical size constraint or
a weight constraint. Other metrics are more complicated and require calculations or
testing for example, minimum structural load or a durability requirement. Only
objectives and constraints that have sound metrics associated with them are
acceptable. If you are unable to figure out a metric for your objective, then rewrite the
objective to be more specific. Should be Green does not have a reasonable metric, but
Should be entirely manufactured of recycled materials does have a reasonable metric.
For more information on metrics, please read Designing Engineers: An Introductory
Text Investigating Ideas: Using Metrics, pp. 177-179 (Chapter 7, section 7.1 in
WileyPLUS).

1.6

Service Environment

The service environment describes the location where the design will operate. A
location is more than just a latitude and longitude on earth or a point in space. The
description of a location includes a description of all elements that might typically be
present in that location. For example the amount of rain, the typical temperature range,
the presence or absence of cell phone coverage, the types of animals and insects
native to the environment, the noise level range, and the people. If the technology you
are designing will be mobile, or will be installed in a number of different locations, then
you need to describe the range of conditions typical for these different locations. If it will
only operate outside, then you need to describe the outside conditions. And if it will only
operate inside, then you need to describe the indoor conditions.
Document the total environment that the design must operate in. Service environment
should not be written from the point of view of the device or design. That is, it is not how
the device will be designed to operate within an environment, but what the
environmental concerns are in the first place. In other words, NOT The design must be
water-proof but Temperatures can be expected to range from -32C to +40C.
Average rainfall is 709 mm and snow is 138 mm [1]. However, you may choose to
show the connection between the Service Environment and FOCs already defined in
your document as you did in the Stakeholders Section a kind of shorthand to save on
words e.g. C1 to refer to Constraint 1.

Physical environment
Considerations may include range of temperature, pressure range, wind velocity, rain
and salt spray, humidity, dirt and dust, corrosive environments, shock loading, vibration,
and noise level. When writing this sub-section:
9

Engineering Strategies and Practice

As a general rule, you do not need to choose the most extreme extremes:
e.g. the record low temperature or high temperature. Engineers typically use
ranges that are based on statistical percentages. For example ASHRAE
tables (American Society of Heating, Refrigeration, and Air-conditioning
Engineers) and other environmental statistics will report the 99% low
temperature or 1% high temperature for an environment which means that
99% of the time the temperature is above this low and 1% of the time the
temperature is above this high.
You may also acknowledge other elements that may be active in the users
environment, including (but not limited to) appliances or machinery.

Living things
This subsection identifies organisms that may interact with the design or need to be
considered when developing the design. To think about when writing this sub-section:

These may be animals, microbes or plants.

If you are considering humans, you may identify factors such as culture, age,
language, physical attributes, and education.
You may also include malevolent beings in the service environment - you
need to identify these in addition to users, other people, and other living
beings, which have a positive or neutral interaction with your design.

Virtual environment
This subsection identifies any virtual systems that may exist within the physical
environment. These may include the presence of WiFi or a cellular network, the
operating system for the computer, or version of the software.

1.7

Client Ethics and Values (ESP II)

This section demonstrates that you understand your clients perspective. The client may
have specific ethical policies that will impact cost or implementation. Additionally, the
client may have values that will influence a design choice; these values may relate to
labour practices, aesthetics, cultural perception, or be environmental, social, or political.
Your client will be reading this section. Be professional and diplomatic.

2.0 Project Management Plan (ESP II)

In the body of your report, concisely describe the project plan. Identify project
milestones and due dates, that are of concern to your client, especially those that
require a client action. This information is updated in each document. Do not include
internal milestones or due dates that do not directly concern your client. This additional
level of detail is expected in a Gantt chart which is a separate document submitted to
the Project Manager.

10

Engineering Strategies and Practice

3.0 Conclusion
Summarize the key points and bring the document to a close in a way that fully defines
what the reader may expect, at this point, from the project. The reader should therefore
have reaffirmed any action they are being asked to take as well as those you are taking.
This is not a word-for-word repetition of earlier material, but rather a way of bringing the
document together and consolidating its main message(s). It may include
recommendations and/or next steps.

4.0 Reference List

It is an academic offence to represent the ideas of others as your own, that is, to commit
plagiarism. Students who are caught plagiarising the work of others, will be required to
attend a meeting with a representative of the First Year Chair and will be subject to
sanctions that may include a zero on the assignment or worse.
In order to ensure that you are properly identifying your sources, you must follow
BOTH of the following two steps.
1) In the body of your report, wherever you have used information in any form
(including graphics) from anyone other than yourself, or ideas that are not your
own, you must identify the source with an in-text citation, which is a number in a
square bracket, e.g. [5].
2) At the end of your document, list all cited sources in a Reference list using IEEE
referencing standards. The IEEE referencing standard can be found at:
http://www.ieee.org/documents/ieeecitationref.pdf. Only IEEE referencing is
permitted in this course and it must be followed exactly.
Warning: If you have taken someones idea, AND their exact words, you must indicate
that these are not your words. This can be done with quotation marks (-) if the text is
short or by indenting and italicizing (block quote) if the text is longer. Examples:

The entrance average in engineering at Vitruvius University has increased by 7%

over the last five years [1]. (idea only, citation and reference required)
The 7% increase in entrance averages over the last five years is a clear
indication of the outstanding quality of our entering students Vitruvius University
President Leonardo Da Vinci has announced [1]. (idea AND words, citation,
reference AND QUOTATION MARKS required)

A full explanation of how to cite a source can be found in Document Style

Requirements in the Communication in ESP Guide posted in Course Information on
Blackboard. If you do not document your sources properly, you will face a charge of
academic misconduct. If you are unsure how to properly cite a reference ask your CI or
another member of the ESP teaching team.

11

Engineering Strategies and Practice

Appendices
In the appendices, put material that does not fit in the flow of the document, either
because it is too extensive or because, though only a part of it is relevant, you have
included the whole to give an interested reader a complete, detailed understanding of
your subject. Examples are: manufacturers' data sheets, relevant research documents,
or details of alternate designs.
As far as figures are concerned, determining which should be in the body of the
document and which should be in the appendices will be a matter of judging the
relevance of the figure and the way that it fits into (or disrupts) the flow of the document.
It is vital to include the most relevant drawings, plans or sketches in the body of your
document; additional ones can be included in the appendices.
Any information included in the appendices must be mentioned in the body of the report.
Moreover, all material in the appendices, including published material such as
manufacturers specifications, must have a short explanation written by your team
showing the relevance of this material. Material should be divided appropriately into
individual appendices, each of which should be clearly labeled and titled: eg, Appendix
F: Drawings of Alternate Designs.
Sources for all material included in appendices must be documented in the
Reference List. You do this by putting a number in a square bracket [#] next to the
discussion of the appendix in the body of the report. Then you add to the reference list,
as you would any reference material, the full bibliographic information in correct form, as
explained in the Course Package.

The Conceptual Design Specification (CDS) adds the

following sections
2.0 Alternative Designs
These must include the Proposed Conceptual Design. Just as a Critical Thinker would
look for many different solutions to a problem, a CDS provides multiple, valid designs.
Each design should represent a different approach to the problem, a different trade-off
between objectives. Each solution should therefore provide the reader (supervisor and
client) with unique information about how the problem could be solved. The information
created by the development of multiple designs can be extremely valuable to the client
and may cause the client to change some basic elements or constraints.
Use the introduction of Alternative Designs to explain and justify your idea generation
and selection processes. Present the methods your team used to generate the
alternatives and then evaluate them, specifying and justifying the criteria your team
considered important. That is, do not just identify the method (e.g. Weighted Decision
Matrix); also give details of the discussion the group had, the reasons you made the
decisions you made.
12

Engineering Strategies and Practice

Flag any obstacles you encountered in your idea generation process and how you
overcame them. Direct your reader to appendices for any tables or charts or other
appropriate material. This introduction should be specific to your project. If the same
introduction could put substituted into a report for any of the other projects, then it is not
specific enough to your project.

2.1 2.5

Alternative Designs <insert name of individual design>

There should be five alternatives and all must be feasible. You may not have one
clearly superior design and four clearly inferior designs. Give a unique name for each
design to aid your reader in recalling each design for example, Design 1 Ramp
Meters, Design 2 - Viaduct. Give a short description of each alternative design and then
review its performance in relation to project key requirements functions, objectives
and constraints. A table listing the same requirements (e.g. the same top objectives) for
each alternative helps the reader to compare the alternatives. Use parallel structure
throughout the five alternative design subsections to make it easier for your reader to
understand the comparison.
In each section, provide visual descriptions for all designs (such as sketches, drawings,
schematics, flow charts). Add measurements where appropriate. Make sure all figures
and tables are labelled according to the style requirements of the course.
If you have too many figures to include in the body of the report, you may add extra
figures in the appendices. Refer your reader to these appendices clearly in the body of
the report, identifying each appendix by alphabetical designation and title e.g.
Appendix A: Design Option 1 Details of the Power Supply.

3.0

Proposed Conceptual Design

Identify the alternative design your team is recommending, and provide a rationale
explaining how and why it will solve the clients problem. Whereas the alternative
section showed how each alternative meets the technical requirements (functions,
objectives and constraints) this introduction justifies your design approach and shows
how meeting the functions, objectives and constraints (FOC) will result in the outcome
the client has asked for. In this brief, persuasive discussion, you will explain how the
solution will have the desired result and you will support that explanation with evidence.

3.1 Proposed Conceptual Design - Name of Design <insert name of the

recommended design>
Provide detailed information about your recommended solution to give the client a
reasonable sense of how this design will function and how it will meet the objectives of
the project. You should include graphic material: simple sketches, drawings, or
flowcharts to communicate to the client how you envision the design at this point. Add
measurements if appropriate. This design, if agreed to by the client, would be the one
you develop in the Final Design Specification (FDS). It is not necessary, or expected,
that you will have a fully detailed design at this point.
13

Engineering Strategies and Practice

3.2

Metrics (ESP I)

To persuade your client to proceed with the recommended design, you must
demonstrate that there are actual tests to show that your recommended design will
meet the design objectives. Given the restrictions of the document, the Metrics section
should focus only on the most critical objectives in your project and should rely on
appropriate conventional testing methods that have been documented by credible
sources, such as ISO or CSA or other standards organizations. You are not expected to
perform these tests.
For more information, please see Designing Engineers: An Introductory Text
Investigating Ideas: Using Metrics, pp. 177-179 (Chapter 7, section 7.1 in WileyPLUS).

3.2

Plan for Detailed Design (ESP II)

Determine the scope for the Final Design Specification, the next document you will work
on. What will you deliver to your client? A design, a flowchart, a paper prototype? What
seems feasible at this point? What is your plan for creating a detailed design? What
aspects of the design are you proposing to detail, and to what degree? Give your client
a good idea of what to expect at the end of the term.

3.3 Outstanding Decisions (ESP II)

In this subsection, you show that you know what you dont know: the design details yet
to be worked out. You cannot be expected to have made decisions for every detail of
the design and, in fact, it is probably a good idea not to present too deep a level of detail
to the client before the client approves the design. So, in this section, identify elements
of the design still to be worked out and explain the associated requirements. For
example, if flooring material needs to be chosen, on what basis will that decision be
made?

3.4 Preliminary Implementation Requirements (ESP II)

This section informs the client about the various costs, disruptions or accommodations
that could be expected should the client decide to implement the design:

Does it require your client to purchase new equipment or software?

Will your client need to change their organizational structure?
Will your client need to hire people to install the design?

There may be other questions to consider, depending on your project. It is important to

identify requirements for which you will need to research the costs for the detailed
design.
For more information on Implementation Requirements, please see Designing
Engineers: An Introductory Text Post Conceptual Design, pages 194-217 (Chapter 8
in WileyPLUS).

14

Engineering Strategies and Practice

3.5 Preliminary Environmental Impact (ESP II)

Using a life-cycle analysis, identify the potential environmental impacts of your proposed
design, and explain how the design tries to lessen the negative impacts and increase
the positive ones.
For more information on Design for the Environment, please see Designing Engineers:
An Introductory Text Design for X: The Environment, pages 365-400 (Chapter 15 in
WileyPLUS).

3.6 Preliminary Human Factors (ESP II)

Explain how your proposed design addresses key human factors and the method that
your team used to define these factors. Were aspects of Universal Design considered?
How did you analyse user experience and integrate that analysis into the design?
For more information on Human Factors, please see Designing Engineers: An
Introductory Text Design for X: Human Factors, pages 413-437 (Chapter 17 in
WileyPLUS).

3.7 Preliminary Social Impact (ESP II)

Examine the key social impacts associated with your proposed design, and explain how
your design tries to lessen negative impacts and increase positive ones. Also explain
how your design balances the concerns of the different stakeholders.
It may help to review Designing Engineers: An Introductory Text Requirements:
Describing Stakeholders and Describing Users, Operators and Clients, pages 69-82
(Chapter 2, sections 2.6 and 2.7 in WileyPLUS).

3.8 Preliminary Economics (ESP II)

Identify life-cycle economic costs (but not the actual dollar values) for your proposed
design, including capital, operating, and disposal costs. Also consider external costs
arising from the social impacts.
For more information, please see Designing Engineers: An Introductory Text
Resources: Economics, pages 523-549 (Chapter 25 in WileyPLUS).

3.9 Preliminary Test Plan (ESP II)

As in the Metrics Section of the ESP I CDS, this section supports the credibility of your
recommended design by demonstrating that there are actual tests to show that it will
meet the design objectives. Given the restrictions of the document, the test plan you
propose should test only the most critical objectives in your project and should rely on
appropriate conventional testing methods that have been documented by credible
sources, such as ISO or CSA or other standards organizations. You are not expected to
perform these tests.

15

Engineering Strategies and Practice

For more information, please see Designing Engineers: An Introductory Text
Investigating Ideas: Using Metrics, pp. 177-179 (Chapter 7, section 7.1 in WileyPLUS).

The Final Design Specification (FDS) (ESP II)

The FDS does not include Alternative Designs but goes into more detail on the
Proposed Conceptual Design. It includes a disclaimer on the Cover Page.

Disclaimer
All Final Design Reports must have clearly noted on the Cover Page, the following
disclaimer:
This Final Design Specification (the "Report") has been prepared by first year
engineering students at the University of Toronto (the "Students") and does
not present a Professional Engineering design. A Professional Engineer has
not reviewed the Report for technical accuracy or adequacy. The
recommendations of the Report, and any other oral or written
communications from the Students, may not be implemented in any way
unless reviewed and approved by a licensed Professional Engineer where
such review and approval is required by professional or legal standards, it
being understood that it is the responsibility of the recipient of the Report to
assess whether such a requirement exists.

2.0 Detailed Design

Section 2.0 should clearly describe the final proposed design. Tell the client as much as
you know in as much concrete detail as possible. This description should now include
all specifications (e.g., physical measurements, memory requirements, power
requirements) and provide your client with a clear sense of what the design will look
like, how it will operate, and how it will meet his or her needs. This last point can be a
revision of the discussion you presented in the CDS about how, in meeting the
functions, objectives and constraints (FOC), the design will provide the outcome the
client has asked for. You will support that explanation with evidence. While every project
will be different, the general expectation is that this section will:

16

Describe the design in detail

Explain how the design meets the functions, key objectives, and constraints
identified in the Project Requirements. Note: include any Design for X
factors (e.g., safety, reliability, affordability).
Include at least two diagrams (technical drawing, flow chart, etc.). Note:
drawings, diagrams, etc. may be placed in appendices
May also discuss a model or prototype to be delivered to the client

Engineering Strategies and Practice

2.1 Regulations, Standards, and Intellectual Property

In this sub-section, your team demonstrates due diligence by identifying:

Safety and environmental regulations and standards that apply to your project
Building codes that apply to your project
Any patented technologies or processes that are relevant to this project. It is
not likely that you will be infringing on patents, but you should make the client
aware of the licensing fees for patented or copyrighted material (e.g.,
software packages) if applicable.

For more information on regulations, standards and IP, please see Designing
Engineers: An Introductory Text Constraints, pages 56-60 (Chapter 2, section 2.4 in
WileyPLUS) and Design for X: Intellectual Property. pp. 436-459 (Chapter 18 in
WileyPLUS).

2.2 Testing
Indicate how your proposed design would be tested to ensure that it meets important
design objectives. ESP teams are rarely called upon to perform the actual tests, so
identify and describe three standard tests that would be conducted. These tests should
be feasible and include measurable criteria where appropriate. Good sources for
credible tests are standards organizations such as ISO or CSA. Note: Section 2.1 has
already identified safety and environmental regulations, so do not repeat that
information in this section.
For more information, please see Designing Engineers: An Introductory Text
Investigating Ideas: Using Metrics, pp. 177-179 (Chapter 7, section 7.1 in WileyPLUS).

2.3 Implementation Requirements

Your CDS provided a preliminary discussion of the various costs, disruptions or
accommodations that could be expected should the client decide to implement the
design. In the FDS, you answer the same questions but with far more detail:

Does it require your client to purchase new equipment or software?

Will your client need to change their organizational structure?
Will your client need to hire people to install the design?

There may be other questions to consider, depending on your project. If your client has
approved the recommended design from the CDS, you can build on the Preliminary
Implementation Requirements section from that document, this discussion is expected
to be more detailed and thoroughly researched than the one in the CDS.
For more information on Implementation Requirements, please see Designing
Engineers: An Introductory Text Post Conceptual Design, pages 194-217 (Chapter 8
in WileyPLUS).

17

Engineering Strategies and Practice

2.4 Life Cycle and Environmental Impact

Your CDS provided a preliminary discussion of the possible negative environmental
impacts of your design and how to mitigate them. Now, using a life-cycle analysis,
identify the potential environmental impacts of your proposed design, and explain how
the design tries to lessen the negative impacts and increase the positive ones. If your
client has approved the recommended design from the CDS, you can build on the
Preliminary Life Cycle and Environmental Impact section from that document, this
discussion is expected to be more detailed and thoroughly researched than the one in
the CDS.
For more information on Design for the Environment, please see Designing Engineers:
An Introductory Text Design for X: The Environment, pages 365-400 (Chapter 15 in
WileyPLUS).

2.5 Human Factors

In more detail than was provided in the CDS, explain how your proposed design
addresses key human factors and the method that your team used to define these
factors. Were aspects of Universal Design considered? How did you analyse user
experience and integrate that analysis into the design? If your client has approved the
recommended design from the CDS, you can build on the Preliminary Human Factors
section from that document, but this section is expected to be more detailed and
thoroughly researched than the one in the CDS.
For more information on Human Factors, please see Designing Engineers: An
Introductory Text Design for X: Human Factors, pages 413-437 (Chapter 17 in
WileyPLUS).

2.6 Social Impact

Examine the key social impacts associated with your proposed design, and explain how
your design tries to lessen negative impacts and increase positive ones. Also explain
how your design balances the concerns of the different stakeholders. If your client has
approved the recommended design from the CDS, you can build on the Preliminary
Social Impact section from that document, but this section is expected to be more
detailed and thoroughly researched than the one in the CDS.
It may help to review Designing Engineers: An Introductory Text Requirements:
Describing Stakeholders and Describing Users, Operators and Clients, pages 69-82
(Chapter 2, sections 2.6 and 2.7 in WileyPLUS).

2.7 Economics
This section has a different focus than Implementation Requirements. That section
focused on the costs for materials and installation. This section looks at the design from
a broader perspective. While you should summarize capital expenditures and
installation costs, this is where you identify operating costs including energy, materials,
18

Engineering Strategies and Practice

labour and maintenance, as well as the costs for disposal and decommissioning. Also
identify any external costs (costs to society) arising from the designs life cycle.
For more information, please see Designing Engineers: An Introductory Text
Resources: Economics, pages 523-549 (Chapter 25 in WileyPLUS). You may find the
following section especially helpful Economics: Types of Costs and Revenues, page
540-545 (Chapter 25, section 25.4 in WileyPLUS).

2.7.1 Market Issues (OPTIONAL)

This section is not applicable to all designs, but if your client has asked you to
consider manufacturing and/or distribution, then you should be able to answer the
following questions:

What is the intended market?

What types of existing systems will this design compete against and who
makes them?
How is this design different from existing systems?
What is the estimated retail price, if applicable, and/or return on investment?
What is the time to market? How long will it take to implement this design?

Lessons Learned and Strategy (LLS)

This is an individual assignment that is intended to evaluate your ability to analyse your
teams performance and your performance in a team in a professional setting. The
intended audience may be yourself in the future, a future team or your present team and
supervisor. You should write it with your supervisor in mind as the audience because
that will help you set the appropriate tone.
The situations that you discuss in the LLS must be events in which you took an active
part, not events that you observed. While we do learn things by observing others, we do
not actually find out how we ourselves will behave in similar circumstances until we
actually participate. Therefore, the evidence for your strategies must come from your
own personal experience, as documented in your Engineering Notebook and LLS.
The situations described in the LLS must pre-exist the writing of the document. You
cannot simply sit down, the night before the assignment is due, and write an essay
about team dynamics. This document is not an exercise in that kind of essay writing. It
is intended, on the contrary, to give you an opportunity to organize notes you have
taken during the term and provide a discussion of those notes.
What you should discuss in your LLS are things that went right or things that went
wrong:

19

Milestones or deliverables are key points

What were your expectations?

Were you disappointed? Why?

Engineering Strategies and Practice

Were your expectations exceeded? Why? Can this be repeated?

Other questions a Lessons Learned addresses can be found in Designing

Engineers: An Introductory Text Critical Thinking in Design Documents, pages
300-305; (Chapter 12, section 12.2 in WileyPLUS).

All explanations must be in the body of the document the Lessons Learned and
Strategies section(s) and not in the Appendix of Examples or other Appendices. The
word limit for this document is intentionally kept tight; marks will be deducted for any
attempt to add words either in the appendices or by including wordy additions as jpgs or
any other format that subverts word count processes. Further, labels must NOT be
longer than 200 characters, including spaces.
Evidence is anything that backs up your explanation:

Drafts of sections of documents

Emails or text messages between team members

Quick sketches of ideas

A reference list is only required if you used research in exploring some of the ideas you
discuss in the document. In such a case, all requirements in relation to the use of other
peoples ideas and words will apply to this document.

Oral Presentations
Various forms of oral presentation are performed in Engineering Strategies and Practice
I & II, from informal small group talks, to client interviews to formal presentations.
Person to person interactions are key to developing trust. Interviews and conversations
can do this. Presentations take person-to-person to a higher level person to group or
group to group. They are more structured than conversations but in engineering should
have a sense of spontaneity and ease. That is, the speaker should seem to be simply
talking to the audience, but in a heightened way that is structured and gives the
audience a sense of efficiency. Such a presentation contains no irrelevant details. It
comes to an end appropriately and in good time. (Based on Dieter, Engineering Design:
A Materials and Processing Approach p.768)

Seminar presentation (ESP I)

At some point during the three-week seminar series, each individual student is expected
to perform a brief (2 to 5 minute) informal presentation addressing a key area identified
by the seminar leader. The student may be required to get the seminar leaders
approval on the topic, in advance of the presentation. No visual support component is
normally required for these brief presentations. Time may be allotted, however, for one
or two questions.
Key elements of such an informal presentation are body language and organization.
You are expected to have a professional demeanour and develop a rapport with the
audience. In order that your presentation be organized, you are highly encouraged to
20

Engineering Strategies and Practice

create an outline, even if it is not as detailed as the outline discussed below for the ESP
II presentations. It should consider purpose, main point, the order of the points you are
making, and conclusion. For more information, please read Designing Engineers: An
Introductory Text Communication: Influencers of Communication and Organizing
Presentations, pages 344-353; (Chapter 13, sections 13.6 & 13.7 in WileyPLUS).

Design Review Gateway (DRG) (ESP II)

The Design Review Gateway (DRG) is a reality check on your project. DRGs or similar
are common in industry. Usually the design team is presenting to an Executive Board or
an engineering team not directly involved with the project and therefore objective. The
purpose of the presentation is to get approval to proceed with your project. If you do not
make a persuasive engineering argument in industry your project will be dissolved as
the company does not see value in expending additional resource on the project.
In ESP, the DRG is a 7-minute in-tutorial presentation prepared by your team and
presented by no more than three of its members. It is an overview of the project and its
current progress. The grade for the presentation is a team grade, even for those that do
not speak. Therefore those students are encouraged to contribute to the presentation
through research, completion of the outline form, preparation of visual aids, and
answering of post presentation questions. All team members must be present at the
presentation even the non-speakers. (If you dont attend, you will receive zero grade.)

Outline form
An outline enables you to give a presentation that seems spontaneous but in reality
reflects a high degree of control on your part. A template is provided with the following
required fields:
o
o
o
o
o
o
o

Opening Strategy
Main Statement
Keyword Summary of Sub-statements
Sub-statements with individual explanations and evidence
Conclusion
Take-Away Statement
Question and answer period

For more information, please see Designing Engineers: An Introductory Text

Communication: Organizing Presentations, pages 349-353; (Chapter 13, section 13.7 in
WileyPLUS).
Visual Support: For the in-tutorial presentation, each team is allowed one flipchart
sheet or one page of handout. For most effective use of this limited resource, please
see Designing Engineers: An Introductory Text Communication: Diagrammatic
Elements and Using Pictures and Photographs, pages 330-343; (Chapter 13, sections
13.4 & 13.5 in WileyPLUS).

21

Engineering Strategies and Practice

Question and Answer Period: Your ability to answer questions effectively is often the
real take-away for an audience. Answering difficult questions showcases your
knowledge and creates a sense of trust between you and your audience. If you do not
know the answer to a question, try to answer it as best you can; however, it is far better
to acknowledge that you do not know the answer than to provide a confusing response.
Keep your answers to questions succinct, and plan to have different team members
field questions.
For information relevant to presenting, please see Designing Engineers: An Introductory
Text Communication: Influencers of Communication, pages 349-353; (Chapter 13,
section 13.6 in WileyPLUS).

Final Presentation (ESP II)

This oral presentation will provide an overview of your completed project. The audience
will be ESP faculty members, colleagues and clients. Generally, oral presentations
cannot cover the same amount of detail as written documents; therefore, your
presentation must be a distillation of your report, organized around its most significant
information (key messages). It is recommended that, early in your presentation, you
identify the problem you were addressing and the solution you chose; it is also
recommended that you follow the presentation sequence indicated in these instructions.
Each team, however, will need to decide itself the best way to organize its presentation.
Industry Analogy: This is similar to a Final Client Meeting which is common in
industry. At the conclusion of a design contract you will meet one final time with
your client. You are attempting to persuade your client that your final design meets
their needs and is ready for implementation. Rarely directly stated, but important,
is communicating what value you have added to your clients situation. I.E. Have
you been worth the cost to hire you?
As with the DRG, you are expected to be meticulously organized and practiced, but still
maintain a sense of spontaneity. You are expected to complete an outline form with the
template provided by the course. As well, as with the DRG, there will be a question and
answer period. For more information, please read Designing Engineers: An Introductory
Text Communication: Influencers of Communication and Organizing Presentations,
pages 344-353; (Chapter 13, sections 13.6 & 13.7 in WileyPLUS).
Visual Support: For the final presentation, each team must show slides (i.e.
PowerPoint or Keynote, etc.) The key word here is support. Visuals strengthen your
oral delivery of information. They do not substitute for it. Therefore, it is not advisable to
have long slides which require time to read while the presenter does not speak. On the
other hand, slides should have visual elements that back up the speaker show
graphically what the speaker is describing in words. They also spell out and reinforce
understanding of difficult concepts or even keep clear the spelling of terms and names.
Ultimately, slides should be as visual as possible.

22

Engineering Strategies and Practice

Slides with text should contain:

a clear, concise message

a readable format (no decorative fonts)
high quality figures

For more information on design, please see Designing Engineers: An Introductory Text
Communication: Effective Slides, pages 354-359; (Chapter 13, section 13.8 in
WileyPLUS). Also, visit Michael Alleys website Scientific Presentations The
Assertion-Evidence Approach http://writing.engr.psu.edu/slides.html - this site has great
information, examples and templates.

23