Administrator o o o Sr.

Member Karma: +1020/-28 [applaud] [smite] Offline Gender: Posts: 386 Location: Hyderabad

Guidelines About Industry Oriented Mini Project on: January 29, 2010, 07:26:38 PM

Quote

The objective of this document is to present the general guidelines for the writing up of a proper project/seminar report.

Important Points: 1. there is no page limit only thing to be considered is that concept is complete. 2. One must acquire all data and concepts, related to one's project. 3. The Format Guidelines are given by respective Dept heads for report layout. 4. Project should have good industry oriented applications. The below info will give you the complete & detailed description of the mini projects reports. It is essential that you produce a clear and concise report that reflects the 1. literature survey, 2. problem identification, 3. project aims and objectives, 4. the engineering design work carried out,

5. tests performed and 6. discussion of results.

The emphasis/ concentrarion should not be on the length of the report, but rather on the way by which the above aspects are presented. In this context, you should avoid downloading bulk text and images from books or the internet or use unconventional fonts or graphics with a view to impress the reader. You should rather show the reader that you have understood the problem at hand and used an engineering approach to produce a working solution by working as a team with your group members. You should also be able to explain the working principle and design of each stage of the developed system. REPORT FORMAT: With the format given below, the project report should normally not exceed 30-40 pages (excluding the appendix), and should not be shorter than 25 pages. Font and Size: For Chapter Numbers and Titles: Times New Roman Size 18, Bold, Centered, Upper-Case. Sections Numbers and Titles: Times New Roman Size 14, Bold, Left aligned Sub-section Numbers and Titles: Times New Roman Size 12, Bold, Left aligned For the main text: Times New Roman Size 12, Justified. NOTE: Do NOT put the Chapter Number and Title on a separate Page. If there are less than four lines remaining at the bottom of the page, start the new section or subsection on the following page.

Paragraphs and Line Spacing: line spacing is 1.5 throughout the report. Leave a one blank space from one paragraph to another. Margins: Top, Bottom, Right: 25mm; left: 30mm. Headers/ Footers: Times New Roman Size 10. Equations : Should be edited with Microsoft Equation, and should be numbered in ascending order in each chapter: E.g:

is the first Equation in Chapter 2.

Next equation number will be 2.2. Equation in next chapter starts with 3.1, 3.2, 3.3 if it is of chapter 3. Page Numbers: Start with Page 1 at the beginning of Chapter 1. Page numbers should be centered at the bottom of the page. Figures and tables: Position Figures and Tables as close as possible to the text where they are referred. Figures and Tables should be numbered in ascending order for each chapter, using the same sequence as for Equations. The number of the figure, and its caption should be typed immediately below it in Times New Roman Size 12.

 The number of the table and its caption should be typed immediately above it in Times New Roman Size 12. TITLE PAGE: The title page should include the following information: Mini-Project Title Student Names and ID Nos. A statement that the report is submitted in partial fulfillment of the requirements for Practical Training of the B.Eng. (Hones...) in Electrical and Electronic Engineering. Date of submission TABLE OF CONTENTS: The table of contents should list all the chapters, sections and other parts of the report, along with their page numbers. In particular the following should be included:

NOTE: The above page numbers are given as examples only.

ACKNOWLEDGEMENT: Any person, institution, organization, department or lab, whose help or support you want to acknowledge for the project. ABSTRACT: A summary of 300 to 400 words of the practical application, the problem to be solved, the approach used and the main results obtained. LIST OF FIGURES: A list of all Figure Numbers presented in the report, and their title (E.g. Figure 2.1 Circuit diagram of the Traffic Light Controller) along with the page numbers.

LIST OF TABLES: A list of Table Numbers should be presented in the report and their title, along with the page numbers. You can arrange the chapters as follows

Chapter 1: Introduction In this you can explain about aim and objective of the project and scope of the project. In this you need to explain the problem and how you are going to solve the problem. Chapter 2: Literature Survey In this you can explain the different technologies which are competing with your technology on which you are doing. Chapter 3: Technology Explain about the technology you used in the project Chapter 4: Architecture In this, first you identify the number of modules that are in the project and the interconnection of modules (blocks). In this chapter you are going to explain the design architecture of the project with the help of the block diagram. Explain the overall architecture and how it works from one block to another block (module).

Chapter 5: Design and implementation In this you can explain about how you have designed the individual blocks and explain the logic behind to implement each block. Explain individually about each block. Chapter 6: Results and Discussion In this chapter you explain about the results. Results which are nothing but testing the each module individually by means of picture, screen shot... etc which explains the input and output. Chapter 7: conclusion and recommendations In this chapter you explain what are the efforts made in solving the problem and explain the problems you come across while you are doing the project. Chapter 8: future scope Explain about the project if it is extended in future and modifications to be done. Chapter 9: applications

Chapter 10: references Web sites Text books Journals or magazines

Appendices: Appendix A: About vhdl/ matlab/ embedded c with sample codes or examples Appendix B: Integrating code of the project