<Insert Project Title>
Project Proposal

Document Version: <Insert Version Number>

Authors

This document was prepared by:

<Insert contact information for each author as follows:
Name, Title
Organization
Address
Office phone
email address / Example:
John Doe, Project Manager
Ministry of X
Roundabout A
Office Phone: xxx-xxxx
/ Example:
Jane Doe, IT Coordinator
Ministry of X
Roundabout A
Office Phone: xxx-xxxx

Version History

Date / Document Version / Document Revision History / Document Author/Reviser
Insert version completion date> / <Insert version number> / <Briefly describe work completed to create the version> / <Name author or reviser>
Example:
May 15, 2006 / 1.0 / Initial draft / John Doe
May 28, 2006 / 2.0 / Reviewed with IT Coordinator and revised / John Doe
June 2, 2006 / 3.0 / Reviewed and revised following meeting with Project Sponsor / Jane Doe

Approvals

Date / Document Version / Approver Name and Title / Approver Signature
<Insert approval date> / <Insert version approved> / Provide name and title of approver>
Example:
June 30, 2006 / 3.0 / James Doe, Project Sponsor and Director, IT
June 30,2006 / 3.0 / John Doe, Project Manager

1.Problem background and definition

This section describes the problem or opportunity the project seeks to address using factual information. Read Chapter 3 in Dym.

Please describe your project in narrative form using these questions as a guideline. You may delete the box for your submission.

PROBLEM DEFINITION (Your project should solve a well-defined engineering problem):

●What is the problem that you are addressing?

●Who is the end user, and what is the end user profile?

●What is the target market?

2.Existing Solutions

This section provides some of the existing solutions and discuss the opportunities for improvement>

Please describe existing solutions in narrative form using these questions as a guideline. You may delete the box for your submission.

EXISTING SOLUTIONS

●What are the existing solutions to the problem?

●Who are the manufacturers?

●Do they solve the problems or there are opportunities for improvement?

●Is there a way to solve the problem in a more cost-effective manner than the existing solution?

3.Project Goal

<This section provides a clear, concise statement of the project’s purpose and intended results. The project goal statement should be brief (one sentence). Refer to Chapter 2 in Dym.

4.Proposed Solution

Engineering Solution: Please describe this in a narrative form for the solution to the problem highlighting significant design features and benefits. Specifically, note the requirements, objectives, constraints, and functions. Refer to Chapters 3, 4, and 6.1 in Dym.

PROPOSED SOLUTION (You should have a top-level idea of the solution or how you will solve the problem):

●What is the significance of this project?

●What is the proposed solution or approach?

●What are the advantages of your proposed solution?

●What are the customer requirements, objectives, and functions?

5.Key Stakeholders

<This section provides a description of the people with the strongest interest in or influence over project work and results. If you are doing a project at work, identify the people who are working on the project or have interest in the project and explain what they will be doing and what you will be doing. The role you have is critical to explain at this point.

6.Assumptions and Constraints

<This section identifies and explains the assumptions and constraints of the project. Refer to Chapter 5 in Dym.

6.1 Assumptions

<List assumptions here.>

6.2 Constraints

<List constraints here.>

7.Impact Analysis

IMPACT ANALYSIS (Describe how the following issues impact your problem and its solution):

●Organizational

●Networking standards

●Security

●Ethical

●Social

●Legal

●Economic

●Target market/end user

CAUTION: Students often consider the impact analysis as an afterthought and give little serious thought to this section. However, considering these issues is an integral part of designing a solution or system in the broader context. Designs and their implementations have failed for lack of consideration of such issues.

8.Risks

<This section lists project risks. Risks are something that may or may not happen in the future that could have a negative impact on the project.>

9.Estimated Cost

< Provide an initial estimate of what the project is expected to cost with a top level breakout. If you are doing this at work, what are the projected costs (if any) incurred by you? >

10.Estimated Duration

< Provide an initial estimate of the project duration. Remember that the project must be completed (designed, built in hardware, tested and presented by week 7 of ET450.>

Date:
Approved by:
Approver Signature:
Project Manager Name:
Project Manager Signature:
<Insert Project Name> – Project Proposal / (1)