0% found this document useful (0 votes)
44 views4 pages

Guidelines For Preparing Project Report

The document provides guidelines for preparing project reports, including formatting requirements for paper, layout, chapters, numbering, font sizes, figures, tables, and equations. It specifies that reports include three copies - one for the department, guide(s), and candidate. Approval from the guide(s) is required before final printing. The last chapter should summarize work carried out, contributions, and scope for future work. Hardware and software projects have additional requirements for documentation. Reports will be evaluated based on various criteria and marks will be allotted at seminars and by the guide.

Uploaded by

Annappa K Arya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views4 pages

Guidelines For Preparing Project Report

The document provides guidelines for preparing project reports, including formatting requirements for paper, layout, chapters, numbering, font sizes, figures, tables, and equations. It specifies that reports include three copies - one for the department, guide(s), and candidate. Approval from the guide(s) is required before final printing. The last chapter should summarize work carried out, contributions, and scope for future work. Hardware and software projects have additional requirements for documentation. Reports will be evaluated based on various criteria and marks will be allotted at seminars and by the guide.

Uploaded by

Annappa K Arya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

GUIDELINES FOR PREPARING PROJECT REPORT

Paper and layout:


 Project reports should be typed neatly only on one side of the paper With 1.5 line spacing
 On a A4 size bond paper (210 x 297 mm).
 The margins should be: Left - 1.25", Right - 1", Top and Bottom - 0.75".
 The reports submitted to the department/guide(s) must be hard bounded, with a plastic
covering.
 Separator sheets, used if any, between chapters, should be of thin paper

The total numbers of reports to be prepared are:


 One copy to the department
 One copy to the concerned guide(s)
 One copy to the candidate.

Approval:
 Before taking the final printout, the approval of the concerned guide(s) is mandatory and
suggested corrections, if any, must be incorporated.
 For making copies dry tone Xerox is suggested

Chapters (to be numbered in Arabic) containing Introduction- which usually specifies the
scope of work and its importance and relation to previous work and the present
developments

Main body of the report divided appropriately into Chapters, Sections and Subsections.

The chapters, sections and subsections may be numbered in the decimal form
 For e.g. Chapter 2, Sections as 2.1, 2.2 etc., and Subsections as 2.2.3, 2.5.1 etc.

Font size (Times New Roman only):


 The chapter must be left or right justified (font size 16).
 Followed by the title of chapter centered (font size 18),
 Section/subsection numbers along with their headings must be left justified with section
number and its heading in font size 16 and
 Subsection and its heading in font size 14.
 The body or the text of the report should have font size 12.

The figures and tables must be numbered chapter wise


 For e.g.: Fig. 2.1 Block diagram of a serial binary adder, Table 3.1 Primitive flow table, etc.

Only SI units are to be used in the report.

Important equations must be numbered in decimal form


 For e.g. V = IZ .......... (3.2)
 All equation numbers should be right justified.

The last chapter should contain the summary of the work carried, contributions if any, their utility
along with the scope for further work.
Reference OR Bibliography:
 The references should be numbered serially in the order of their occurrence in the text and
their numbers should be indicated within square brackets for e.g. [3].
 The section on references should list them in serial order in the following format.

For textbooks –
[1] A.V. Oppenheim and R.W. Schafer, “Digital Signal Processing”,Englewood,
N.J., Prentice Hall, 3 Edition, 1975.

For papers –
[2] Devid, “Insulation design to combat pollution problem”, Proc of IEEE, PAS, Vol
71, Aug 1981, pp 1901-1907.

For websites –
[3] Ram Ganeshan and Terry P. Harrison, “An Introduction to Supply Chain
Management”[Courtesy: http:// lcm.csa.iisc.ernet.in/scm/supply_chain_intro.html]

Important:
 The project report should be brief and include descriptions of work carried out by others only
to the minimum extent necessary.
 Verbatim reproduction of material available elsewhere should be strictly avoided.
 Where short excerpts from published work are desired to be included, they should be within
quotation marks appropriately referenced.
 Proper attention is to be paid not only to the technical contents but also to the organization of
the report and clarity of the expression.
 Due care should be taken to avoid spelling and typing errors.
 The student should note that report-write-up forms the important component in the overall
evaluation of the project.

Hardware projects must include:


 The component layout, complete circuit with the component list containing the name of the
component, numbers used, etc. and the main component data sheets as Appendix.
 At the time of report submissions, the students must hand over a copy of these details to the
project coordinator and see that they are entered in proper registers maintained in the
department.

Software projects:
 Must include a virus free disc, containing the software developed by them along with the read
me file.
 Read me file should contain the details of the variables used, salient features of the software
and procedure of using them: compiling procedure, details of the computer
hardware/software requirements to run the same, etc.
 If the developed software uses any public domain software downloaded from some site, then
the address of the site along with the module name etc. must be included on a separate sheet.
It must be properly acknowledged in the acknowledgments.
 Distribution of Marks for B.E. / B.Tech. Dissertation Evaluation

Sl No Particulars Max. marks


1 Relevance of the subject in the present context 10
2 Literature Survey 10
3 Problem formulation 10
4 Experimental observation / theoretical modeling 10
5 Results – Presentation & Discussion 10
6 Conclusions and scope for future work 10
7 Overall presentation of the Thesis/Oral presentation 40
 Total Marks 100

Additional Guidelines

Project Dairy:

 Each batch has to maintain a Project Dairy which has be carried by the team every time
while meeting the guide. The team has to enter the suggestions given by the guide into the
dairy and take the signature of the guide. The dairy is an important document to allot final
marks by the guide.

Seminar Results:

 After every seminar, result will be announced as – satisfactory / unsatisfactory. If the result
is found unsatisfactory 5 marks will be deducted from individual marks and the team has to
repeat the seminar for satisfactory.

Allotment of Marks:

 First Seminar - 10
 Second Seminar - 20
 Third Seminar - 30
 Paper Presentation - 10
 Balance Marks - 30 exclusively by the Guide
 Total - 100

(Seminar marks will be allotted by 3 members’ committee - Guide, Expert & HOD)

Certificate
 Certificate should consist of individual name on the individual copy while the department
and guide copy consist of all four (team) names.

 Last page of the Project report should consist of brief bio-data of team members with
individual identity size photo

Project Coordinator Head of the Department


Prof. Harish H .M Prof. Rajashekar. U

You might also like