General Guidelines - First Review for B.Tech Mechanical VIII Sem
3 likes3,489 views
This document provides guidelines for students presenting their project work, including: - The presentation should be in PowerPoint without binding or plastic covers, and students should conduct a mock review with their guide before presenting. - The presentation should include sections on the project title, introduction, objectives, expected outcomes, literature review, methodology, individual contributions, results, progress, and a Gantt chart work plan. - References should be in IEEE or ASME style. Guidance is provided on formatting slides, using bullet points, citing figures, and the order and content of slides including the title slide and Gantt chart slide.
General Guidelines - First Review for B.Tech Mechanical VIII Sem
- 1. With lot of Thanks to Prof. Dr. P. Vivekananda Shanmuganathan for giving these useful guidelines General: - No plastic; no binding of the report. - Mock review with the guide essential. - Students should report 2-3 days prior to review to facilitate mock review with guide. - Draft copy of the report and the draft version of PPT must be emailed to the guide well before the arrival of the student. - Draft versions of the report and PPT are revised based on guide's feedback; Mock review to be conducted after this. - Progress of the work, contribution of individual members, and regularity in interaction with the guide will carry significant weightage. Contents of PPT: - Project Title: Keep a title page. Avoid using company logos. The project title, team members with registration numbers, and the name of the guide (without any spelling mistake) and the correct designation of the guide. - Introduction: 3-8 slides; Introduce the broad area of work, discuss the current scenario, the drawbacks in the current scenario worldwide, specific problems that the project guide + his team intend to tackle over the next couple of years. These specific problems are objectives in general. - Objective of the Project: Objectives are general in nature. These are basically what the guide and his team are focussing to solve in long term. The scope of the students' project will naturally be a small part of it. - Expected Outcome of the project: This actually defines the scope of the students' project. Students should outline the expected outcome of their project. In team projects, the specific contribution envisaged for each member of the team must be identified and highlighted. - Literature Review: Literature review must be included at this point. Literature review must be like a story-telling of the contribution of other researchers / industries in the area. Literature review should lead to problem definition, in which the expected outcome must be clearly outlined and explained. Journal papers published in the 21st century carry more weightage. Conference papers, books, data sheets, discussion with an expert in the field, websites, email communication, discussion on mailing lists / online groups could all contribute to literature. Any literature collected by the student during the review period must be highlighted. - Methodology: This basically the procedure outline of how the project team is going to realize the expected outcome. Tasks/activities / modules related to the project and brief description of the same may be given. Overall methodology must be presented in the form of a flow-chart or block diagram before going into the details. Software and equipment to be used must be outlined. Modelling and analytic procedures must be outlined, highlighted, and detailed if required. Why a particular tool or technique is used must be justified. - Individual Contribution: In team projects, efforts taken by the student in planning the project. - Results: Results include the any original contribution, data collected and analyzed, computer programmes written, simulation results, etc. Each piece of result must be discussed in relation to the expected outcome.
- 2. - Progress of Work: Design tools used must be listed, and the efforts of each team member in learning the tools must be presented, e.g., some tutorial exercises in case of software, knowledge gained related to any experimental design equipment. Progress of the work till date must be highlighted. Progress of the work, contribution of individual members, and regularity in interaction with the guide will carry significant weightage. - Plan of work (Gantt Chart: Months/weeks on X-axis and activities/sub-activities on Y-axis) Proposed activities to be completed by the next Review must also be mentioned. - Report (3-5 pages only) Report is basically a full-sentence form of the presentation. Keep it as short as possible. 5-6 pages of report is optimal. Move any long derivations or data or even tabulated results to appendix. Tips on preparing PPT: - Avoid full sentences and paragraphs in a PPT. - You may do your project outside. However, DO NOT use company logos anywhere in the project. - Except for theorems, laws and historic definitions however may be written as full sentences or paragraphs. - As a thumb rule, PPT file will contain mostly bulleted items and figures. - No bullet item may be more than 1.5 lines long. - Each bulleted item must be written in telegraphic language as in newspaper headlines. - Each figure that is NOT AN ORIGINAL concept of the student, must have the source cited beneath the figure. - Figure caption, if at all required, must be typed by the student and NOT CUT-PASTED although the FIGURE ITSELF MAY BE CUT-PASTED. Title Slide: - First slide is always a title slide. - Name of the VIT faculty will be listed first. - For students doing project outside, name of the outstation guide will be listed next to VIT faculty. - All are guides. No need to mention internal guide or external guide. - Names of guides should be printed without spelling mistakes. - Designation of the guides should be written in full as in Assistant Professor and NOT AS IN Asst. Prof, or AP, etc. - Do not abbreviate the names of the departments/organisations since the abbreviations are only for informal/spoken use: For example, - Use School of Mechanical & Building Sciences instead of SMBS, - Use Bharat Heavy Electricals Limited instead of BHEL, - Use Boiler Auxiliaries Unit instead of BAU. - Official or universal abbreviations must be used as abbreviations and in their correct form only: For example, - Use VIT University and NOT as VITU or Vellore Institute of Technology University. - Use NTPC Ltd. and NOT the old full name. - Provide full name and address of the organisations after the designation of the guides. - Provide the email id of the all the guides in the title slide.
- 3. Last-but-one Slide: - Gantt Chart (Activities Vs Time Chart) must be the last-but-one slide. - The Gantt chart should identify the list of activities (actually, the list of expected outcomes) on the vertical axis and the time period (in units of week, or months, or names of calendar months) on the horizontal axis. - The simplest way to draw a Gantt Chart for the project review purposes is just to use the Table Feature of MS-WORD, and draw horizontal bars (actually lines drawn with large thicknesses) or darken the cells relevantly. - Additional details of Gantt Chart may be found on Internet and text books. For example, Drawing Gantt using Excel: http://office.microsoft.com/en-us/excel/HA010346051033.aspx Wiki page on Gantt Chart: http://en.wikipedia.org/wiki/Gantt_chart Last Slide: - Last slide is always the list of references - List of references must be listed as per ASME or IEEE style.