EE Dept, IIT Bombay

EE712Embedded System Design / Spring 2012-2013

Instructions for Project Report Preparation

1. Submission

The hardcopy of the report should be on A4 sheets (single/double sided), simply stapled on the upper left corner. Do not use a separate cover page, binding, or plastic covers. Submit 1 copy. In addition, a soft copy should be submitted in "PDF" format, by mailing to <..in>, with filename of "ee712_13s_n.pdf", with "n" being the roll number of the first author.

2. Font size

Font size: 11 or 12 for the report text. Project title should be in font 14 and bold. All the headings should be in bold.

3. Information Content

The report should provide the following information
1) Problem statement.
2) Literature review, leading to the block diagram, ckt, components, etc.

3) Investigations: any investigations carried out by you to develop a part of the design, verification of ideas, or other investigations.

4) Final block diagram and circuits

5) Test procedure : to show how that the implementation achieves the requirement of the problem.

6) Test results with plots and tables (appendices, if necessary).
7) Discussion of the results

8) Conclusion and suggestions for further improvement.
9) References.
You may partition the report in appropriately named sections (not necessarily as above).

4. Organization

The report should start with abstract, of about 10 lines. This should emphasize the main problem, approach taken, and the final achievement/status.This should be followed with numbered sections, starting with "1. Introduction". Last section should be conclusion, which should summarize the achievement and include suggestions for any future work.

All equations should be numbered, by putting equation number within "( )", with right alignment.

Follow the practice of proper mathematical notation in the text as well as in equations. Each scalar variable should be single character (with subscript if necessary) and in non-bold italic. Do not use italics for numbers, standard functions, acronyms, labels, and units. Array variable (vector, matrix) should be in bold non-italic.

Leave a space between the number and the associated unit. Use SI units. If other units have to be used in accordance with prevailing practice, corresponding SI value should be given in parentheses.

All figures and tables should be numbered and titled. Figure titles should be below the figure, while the table title should be above the table. The text in the figures and tables should be approximately of the same size as in the text. In any case it must be clearly readable.

Block diagrams and signal flow diagrams : Sizes of blocks in a block diagram should be either similar or should be related to the importance of the block, and not adjusted to enclose the text. Do not mix block diagrams and circuit schematics.

In graphs, the axes should be labeled and units given. The scale and labels should be appropriately selected.

Reference information must be complete (you can check an IEEE paper for this). In case of web references, giving URL is not enough. Find the author, organization, and date (often it is possible to get this information by going backwards in the URL). In case you are really unable to get the year when the web document was prepared, at least give "Last accessed on dd.mm.yyyy".

You should use single column format for preparing the report. All the figures and tables may be given at the end.

5. Format

EE712Embedded System Design Course Project Report, EE Dept, IIT Bombay, April 2013

(Course Instructors: Prof. P. C. Pandey & Prof. D.K. Sharma)

PROJECT TITLE

Author (Roll No) <E-mail>

Author (Roll No) <E-mail>

Author (Roll No) <E-mail>

Abstract

1. Introduction

N. Conclusion

References

(Appendix)