DOC PREVIEW
MSU ECE 4512 - An Audio Visual Information Access System

This preview shows page 1-2-3-4 out of 12 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 12 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1. Problem2. DESIGN REQUIREMENTS2.1. Technical Design Constraints2.2. Practical Design Constraints3. APPROACH3.1. DC Power Supplies3.2. Hardware Design3.2.1. Theory of DC Power Supplies3.2.2. More Interesting Theory3.3. Software Design4. EVALUATION4.1. Test Specification4.2. Test Certification – Simulation4.3. Test Certification – Hardware Subsystems4.4. Test Certification – Software Subsystems4.5. Test Certification – System Test5. SUMMARY AND FUTURE WORK6. ACKNOWLEDGEMENTS7. REFERENCESdesign document forAVGET: An Audio Visual Information Access Systemsubmitted to:Professor Joseph PiconeECE 4512 (or 4522, etc.): Senior Design I (or II)Department of Electrical and Computer Engineering413 Hardy Road, Box 9571Mississippi State UniversityMississippi State, Mississippi 39762August 24, 2003prepared by:J. Doe, J. Smith, M. Smith, and Y. SmithFaculty Advisor: Professor John SmithIndustrial Advisor: James Smith, Corona CorporationDepartment of Electrical and Computer EngineeringMississippi State University413 Hardy Road, Box 9571Mississippi State, Mississippi 39762Tel: 555-555-5555, Fax: 555-555-5556email: {doe, jsmith, msmith, ysmith}@ece.msstate.eduDEPARTMENT OF ELECTRICAL AND COMPUTER ENGINEERINGEXECUTIVE SUMMARYThe executive summary must be exactly one page long – no more no less. It should be composed of fourparagraphs. The first paragraph contains an overview of the problem (not the approach).The second paragraph contains an overview of the design constraints. The goal of this paragraph is tomake sure the reader understands the key technical challenges.The third paragraph contains an overview of the approach you are taking to solve the problem. How doyou plan to meet your key design constraints? The second and third paragraphs are the longest.The last paragraph contains an overview of the novelty of your design. This is a fairly short paragraphthat summarizes innovation in your project. What other things can be done to improve your design; whatwill be the impact of success, etc. This paragraph should be about four sentences.There must beTABLE OF CONTENTS1. PROBLEM ..................................................................................................................................12. DESIGN REQUIREMENTS ......................................................................................................12.1. Technical Design Constraints ...........................................................................................12.2. Practical Design Constraints ............................................................................................13. APPROACH ................................................................................................................................23.1. DC Power Supplies ..........................................................................................................33.2. Hardware Design ..............................................................................................................43.3. Software Design ...............................................................................................................54. EVALUATION ............................................................................................................................54.1. Test Specification .............................................................................................................54.2. Test Certification – Simulation ..........................................................................................54.3. Test Certification – Hardware ...........................................................................................54.4. Test Certification – Software ............................................................................................55. SUMMARY AND FUTURE WORK .........................................................................................66. ACKNOWLEDGEMENTS ........................................................................................................67. REFERENCES ...........................................................................................................................6APPENDIX A: PRODUCT SPECIFICATION ....................................................................................7APPENDIX B: SOME INTERESTING RELEVANT DERIVATION..................................................8AVGET: Information Access Page 1 of 81. PROBLEMIn this section, you will define the problem you are addressing, explain its significance, and discuss theimpact of your solution (not how you are going to solve the problem, but what will happen if you solvethe problem). Start with a general overview, background, etc., and then get progressively more detailed.This section must be at least two pages long.2. DESIGN REQUIREMENTSStart with an introductory paragraph or two. Then you will list your specific design constraints, followedby an explanation. This section should be at least three pages long.2.1. Technical Design ConstraintsOur five technical design constraints are shown in Table 1. Each team must have five technical designconstraints that adequately constrain the circuit and software design of the system. Technical designconstraints typically relate to the performance of the system. Note the format of the table and the use of across-reference in the text above. You will need two or three paragraphs explaining these design constraints. Typically these are explainedin groups since design constraints are often interrelated. Use constraints that relate to well-knownstandards (such as UL or FCC specs), and be sure to explain these specifications.Design constraints must be quantitative and must be testable. The section on evaluation will describe thetests you use to verify your design constraints.[Some filler text here … Some filler text here … Some filler text here … Some filler text here … Somefiller text here … Some filler text here … Some filler text here … Some filler text here … Some filler texthere … Some filler text here … Some filler text here … Some filler text here … Some filler text here …]2.2. Practical Design ConstraintsIn the ABET handbook on accrediting engineering programs, it states: “Students must be prepared for engineering practice through the curriculum culminating in a majordesign experience based on the knowledge and skills acquired


View Full Document

MSU ECE 4512 - An Audio Visual Information Access System

Documents in this Course
Approach

Approach

15 pages

Load more
Download An Audio Visual Information Access System
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view An Audio Visual Information Access System and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view An Audio Visual Information Access System 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?