Project Statement .

What is a Project Statement? A project usually begins with a vague need expressed by a sponsor (internal or external). The purpose of a project statement is to define the problem to be solved so that work can begin on the project. Once the project is completed, the sponsor will be satisfied with the result.

Stages of Building a Project Statement Contact key individuals in the sponsoring organization (or the internal division). Arrange to meet with sponsor Background research – before visit Ask questions Listen Take good notes in your design notebook –write stuff down!! At conclusion of meeting, summarize and restate what you heard

Doing Background Research What do I need to find out? Where and how can I get the information? How reliable is the information? When do I have enough information? How will the information be used?

Elements of a Project Statement Statement of Need Preliminary Requirements Basic Limitations Other Data Questions

Statement of Need A couple of paragraphs Include brief overview of sponsor Discusses the problem/need Concise –but detailed enough so you can talk to it Does NOT include a solution

Preliminary Requirements Describes the requirements broadly Level of detail for initial sponsor meeting Does not require a detailed spec list

Basic Limitations Describes known constraints Notes applicable codes/restrictions Discusses undesirable features May include simple sketches

Other Data Includes relevant information that does not fit in other sections such as that about: equipment, facilities and/or policies of sponsoring organization software*****

Questions Includes questions that have been raised in meetings/discussions but which cannot be answered until later in the design process.

Format for the Project Statement Cover Page (described later) Body: Project Statement with all the necessary elements (as described before) clearly labeled. Additional Information: Identify key technical areas/skills used in the project.

Cover Page A. Course Number (ME4972) and term B. Title of the Project (descriptive) C. Team NUMBER & members D. Sponsoring Organization (contact information) E. UCONN & Sponsor Logos

Body of Statement Statement of Need Requirements Basic Limitations -Introduction/Background Requirements -What is the project goal(s)? Basic Limitations -Metrics/Specifications/other data Verification Approach -What are you going to do? Schedule

Specifications (defined) List the requirements that project must meet. There are different types of specifications, including those for hardware and software.

Specifications (explained) A key concept underlying the specifications is that any competent engineering team should be able to design a device that performs the function that is desired. Specifications determine what is to be built, but do NOT provide any information about how to build the device.

Specifications (warnings) In general, you should NOT specify any components. However, if modifying an existing device [hardware or software], describe the current device in as must detail as possible.

Technical Specifications Contains in a tabular form all of the facts & figures needed to undertake the design project.

Specifications Format (example) Mechanical Parameters (sample) Button: Size 5” x 5’’ (min.) Actuation Force 0.001 N (max.) Weight: 5000 lbs. (max.) Durability: Should survive 10-ft. drops. Electrical Parameters Battery Life 6 months (continuous use) Display: Number of Characters 30 (minimum) Size 2’ min. height x 1.75’ min. width Illumination Visible in strong sunlight

Specifications Format (cont.) Environmental Location Basement (6’ underground) Temp. Range -40 to +700 F Storage temp. -273 to 1000 F Moisture?, Corrosive liquids?, Vibrations? Software Execution time 34.5 seconds (max.) Termination/Reset 1 button Interrupts Standard ^C Memory 4.5 MB Platform Windows PC

A Final warning: Be Specific!

Final Thoughts Plan ahead What do you have to learn to do project: software, technologies, sources of data, references,… Develop a plan, schedule etc. How will the team operate together Regular meeting times, wo/w advisors File development, maintenance, etc. Shared / divided responsibilities Reliability, commitment of team members