W08_appendix - Appendix A: Project Design Specification...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Appendix A: Project Design Specification Document © 2006 Oregon State University ENGR 202 Manual Page 51 A A PPENDIX A A Project Design Specification Document
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Appendix A: Project Design Specification Document Page 52 ENGR 202 Manual © 2006 Oregon State University DOCUMENT OVERVIEW Modern engineering requires groups of engineers to work together, possibly across large distances, to develop sophisticated systems. In order for all of the parts of a project to work together, a project specification document is vital. Development of a project specification document is always the first step in any project. Unless all engineers working on the project have the same understanding of the project pieces, the final result will not function. Project specification documents come in many a varied format/ outlook. Sometimes they will be formal written documents like those submitted for patent approval. Other times they may be ‘back of the napkin’ sort of documents that give only the briefest explanation, but help an engineer to stay focused. For this course, you will be writing a project specification that is somewhere between the two. You will have a formalized structure to follow, including typographical layout and document length. It is important to realize that in many of the courses you will be taking up in later terms, you will be asked to produce design specifications. The sections and content may vary slightly for each course: so, pay attention to what is asked for, in the requirements. For example, in your Senior Design course, you will be asked to write a very in-depth design specification for your final project. Remembering what you have done in these early courses will dramatically improve your success during the senior design implementation. DEVELOP THE PROJECT SPECIFICATIONS When developing any project specification, a few general steps should be taken. In order to make a complete design, use these basic guidelines: ¾ Conduct a technology review. ¾ Come up with a top-level design. ¾ Outline the testing process. Conduct a technology review The first step in developing the project specifications is to review the ‘state of the art’, which is more commonly called a technology review . This can be achieved thus: ¾ Find projects similar to yours. ¾ Review other similar projects. ¾ Tabulate the results with a comparative analysis. ¾ Make final analytical conclusions from the review.
Background image of page 2
Appendix A: Project Design Specification Document © 2006 Oregon State University ENGR 202 Manual Page 53 Find projects similar to yours This first step involves finding similar projects and digging into them to see how they were accomplished . Often times, this could be combined with a market analysis as well, if the project will result in a product to be sold. When working on a new project, you may find that there is nothing on the lines of what you want to design, in existence yet.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/07/2008 for the course ENGR 202 taught by Professor Jander during the Spring '08 term at Oregon State.

Page1 / 44

W08_appendix - Appendix A: Project Design Specification...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online