Jaypee University of Engineering & Technology, Guna

Final Year Project (B. Tech.), Sem. VIII, (10B19EC791) Year 2011-12
Date: 20, April, 2012

NOTICE
Guidelines for Submission of Final Year Projects Report
1. Final year project report must be submitted to the concerned committee coordinator on or before 10 May, 2012. 2. The number of pages in the project report should not be more than 60-80 (approx). 3. Each project group is instructed to prepare (3 + Number of students in their batch) number of copies of final project report. Among the three copies, one copy will be submitted to institute library, another one to the departmental library and the last copy will be submitted to the respective supervisor (In case any project group has more then one supervisor, they have to submit the extra number of copies so that each supervisor must get one copy of project report individually.) 4. Each group has to take the approval of their respective supervisor/s about the contents of project report prior to printing.

Rajesh Kumar Vishwakarma (Project Coordinator)

Jaypee University of Engineering & Technology, Guna

Final Year Project (B. Tech.), Sem. VIII, (10B19EC791) Year 2011-12

Date: 20t, April, 2012

NOTICE
Guidelines for preparing the chapters of Final Year Project Report Chapter X
(Font size-14, Bold, running, Top Left)

NAME OF CHAPTER
(Font size-14, Bold, Capital letters, center alignment) 2: TITLE (Example: INTRODUCTION) (Font size-12, Bold, all capital letters) 2.1: Sub-Title (Example: Discrete Fourier Transform) (Font size-12, Bold, Each word start with a capital letter) 2.1.1 Sub-sub-title (Example: Classification of communication link) (Font size-12, Bold, Only first letter of title is in capital letter) Rest of the matter should be in running letter with Font size-11 and line spacing 1.5 lines in Times New Roman format. For Table: For Figure: Table 1 Title of table (on the top of the table) Fig. 1. Caption of figure (at the bottom of the figure)

Mathematical equations: Numbered in small parentheses ( ) showing chapter information also, like (3.1) References: Numbered in large parentheses like [ ] and must follow the IEEE format. Note: List of figures, list of tables, certificate, acknowledgement, abstract, front cover, inner cover, table of contents and personal detail must be referred from previous year project reports which are available in the library. Rajesh Kumar Vishwakarma (Project Coordinator)

Jaypee University of Engineering & Technology, Guna

Final Year Project (B. Tech.), Sem. VIII, (10B19EC791) Year 2011-12

Date: 20, April, 2012

NOTICE
Guidelines for Organization of Final Year Project Report
1. Each project report must contain five chapters. (**) 2. Chapter 1: Introduction (Brief history of the area, present status in India and abroad), Statement of problem or problem formulation, Organization of project report). 3. Chapter 2: Mathematical or analytical background of the subject area, conceptualization of problem, in-depth treatment of various models available in subject area, conclusion of studies made in the chapter. 4. Chapter 3: The detail study of the approach/model undertaken for the proposed project, description of the design, complexity analysis, performance study hardware/simulation description of the project undertaken. 5. Chapter 4: Simulation of model, overview of the coding style, comparison of simulation results and usefulness of the project along with applications. 6. Chapter 5: Conclusion, project findings and scope for future extension. 7. References: Details of the of the books, articles, published documents, project reports,
thesis and websites.

8. Appendix: If any (Source code, extra derivation or related theory). 9. A CD containing soft copy of project report in the pdf format and source code must be attached in all the project reports. Above given is only a guide line. Depending upon the title or nature of project, the content of chapter may vary but following points must be covered. Introduction Literature survey Design and Modeling of proposed work Simulated results and applications Conclusion References Appendix: If any

Rajesh Kumar Vishwakarma (Project Coordinator)