Project Report Rules
Project Report Rules
Indents andspacing: The spacing after paragraph must be Opt, and Line spacing must be l.5 lines.
Line Justification: All parts of the report (except the title page) must use full justification.
Headings: All major report headings (see list below) must be formatted to stand out from the body
text and must have a type size of 14-point and bold. All minor headings must be formatted to stand
out from the body text and must have a type size of 12-point, bold and italics.
Page Numbers: All pages are to be numbered consecutively and centered within footer at the
bottom of each page, beginning with page Ion the first page of text after the title page. Youdo not
need to start anew page for cach section. But cach chapter started on new page.
Footer: Footer contained Project name, Student name and academic Year
Tables, Figures, Graphs and Drawings: All tables, figures, graphs and drawings are to be
numbered consecutively using Arabic numerals (1. 2. 3. etc.). Atitle is to appear after the number
and the entire label is to appear under the table, figure, graph or drawing.
Paper: All reports must be printed on good quality white bond paper, measuring 210 by 297 mm
(A4).Only Laser printer and Ink Jet printer outputs are acceptable.
ORGANIZATION OF REPORTS
All design project reports submitted must be organized in the following order:
Title Page: The format of the title page, including spacing and capitalization must be exactly as in
the sample title page shown below.
Abstract: This should be a "reader's digest" version of the project report, emphasizing what was
done and the results achieved in concise summary fashion. The length of the abstract should be
between 200 and 500 words.
Introduction: In this chapter, briefly discuss the general motivation or application area for your
design. Discuss the goals for your design. The use of a Table for your design specifications is
recommended. Discuss your basic approach and related literature. Discuss the specific
contributions you make with this work and why they might be of interest to the reader. The
introduction sets the stage for understanding of your design, what you did, and why it is important
or interesting, as well as puts the work in proper conteXt compared to the state-of-the-art. You are
not expected to fully understand the state-of-the-art in this area or make a novel contribution, but
you should be able to at least point to relevant background literature.
Theory/Discussion of Simulation and Design Methods: In this chapter. discuss the relevant
theory, and the simulation approaches used in arriving at your design. Cite relevant references
where appropriate. Outline the design approach and the areas that required careful attention.
Assume you are writing for another student to be able to perform asimilar design.
Description of Design: In this chapter, provide and discuss block diagram, schematics, diagrams
and/or pictures of your design.
System Design: Hardware section: In this section, discuss your circuit diagram, calculations of a
Component values and list all the components used in your system with prizes in a tabular format.
Firmware section: In this section, discuss software development tool, and firmware/source/driver
code of proposed system along with flowchart.
Appendix A-Datasheet: Inthis chapter:, include important pages of device datasheets used in your
system.
Appendix B- Bibliography: The report should end with a list of references. These should be listed
in an appropriate format, as that used in IEEE publications or other standard research journals.
References should be numbered consecutively and should follow the form shown below:
(References consist of books, web links and research journals)
Example of journal article referencing:
Maiers, J. and Y. S. Sherif, "Application of Fuzzy Set Theory", IEEE Transactions on Systems.
Man, and Cybernetics, Vol. SMC-15, No. 1, pp. 41-48, January 1985.
For the
Partial Fulfillment of
Master Degree of Science (Electronic Science)
Affiliated to
By
Name, Surname
Guide Name