Академический Документы
Профессиональный Документы
Культура Документы
March 2013
Project Details
1. 2. 3. Project Title Area of Work Student Details Student 1 Name Reg No: _________, Roll No: ___ Room No: ____, __th Block, MIT Hostels, Manipal Ph: __________ Email: __________ 4. Organization where the project is being carried out with postal address : Student 2 Name Reg No: _________, Roll No: ___ Room No: ____, __th Block, MIT Hostels, Manipal Ph: __________ Email: __________ : Times New Roman Bold, Font Size 14, Normal Style, Justified : Times New Roman, Font Size 12, Normal Style, Justified
Dept of Electrical & Electronics, MIT Manipal, Manipal 576 104 Karnataka Guide Name, Guide Designation, Dept of Electrical & Electronics, Manipal Institute of Technology, Manipal - 576 104 Ph: 0820 2925121, __________ (M) Email: __________ 16 weeks
5.
Guide Details
6. 7. 8. 9.
: : : :
1.1 Introduction
Explain the motivation for your project. Does your project have a social theme? What inspired you to do this project? Did you extend an existing project? What was goal of your project, such as optimizing the cost/performance/power?
2. Objective
2.1 Proposed Solution
Explain a top-level block diagram of the project, explaining the inputs and outputs of your system. Explain where your project fits into the overall solution. Explain what you have attempted to do differently, compared to known publications. Provide the system-level block diagram of your solution and identify the main hardware and software components. Explain your assumptions on the inputs and outputs of the system. For example, what is the assumption on the input data format, output data format, etc. What are the constraints that you had to factor into your design, such as cost/weight/form-factor, etc.
3. Implementation
3.1 Hardware Implementation
Explain your hardware design, using suitable schematic diagram that shows the integrated circuits you have used. Explain why you selected the different ICs. You may include an explanation of the challenges you faced in realizing the hardware. Do not show details of PCB design in this section & Bill in APPENDIX A & C ( only for final report). Include a photo of the finished product.
Explain your software implementation using flow charts or algorithm. Do not include any code in this section; please show the code in APPENDIX B
4. Results Analysis
Include the results of your hardware and software testing. Include simulation results, screen grabs, graphs, bode plots, etc. Write down your observations. Feel free to include tables/figures/graphs. If you have worked with a hospital or other organization and have performed field trials, include the details of these trials.
Results in graphical plots (with axes quantity & its units of measurement) or tabular form (with
notation & its units of measurement)
5. Conclusions
Explain what was achieved in the project as compared to the goal of the project. Explain the strengths and limitations of the project. Explain the future scope of the project.
References
List references in IEEE format. Ensure that you provide all details for each reference, such as the names of the authors, title of the paper/report, source of the publication, year of publication, etc. Journal / Conference Papers [1] Name 1 and Name 2, Paper Title, Full Journal Name, volume no, publication year, page numbers [2] Name 1 and Name 2, Paper Title, Proceedings of the International / National Conference on ___, Institution, Country, Date, page numbers Midterm project report March 2013, Dept. of E&E, MIT, Manipal
Reference / Hand Books [1] Name 1, Book Title, Publication Name, Edition, ISBN number Web [1] Topic 1, website name (do not include long URLs)
Appendix (A, B & C): To be given only for the final report.
Appendix A
If you wish to provide any details of a PCB design that you have carried out, include them here.
APPENDIX B
Include the software code with comments.
Figure captions below Figure with continuous numbering Tables captions above Table with continuous numbering
A hard copy (Spiral binding ) of synopsis to be submitted to the coordinator at least 1 day before presentation.