Guidelines for Final Year B.

Tech Mechanical Engineering Projects

This is the guidelines for final year B.Tech Mechanical Enginnering project work. The duration for the project is around one year. It is preferred that a project is implemented by a team of four students, but if necessary, the number can be extended to five students, which depends on its scope, varied technology, expense and the volume of work.
Selection of Project First step is Idea/Topic hunting. This can be done by various ways like. Select a company / organization / institute concerned for project work. Discuss with concerned persons, your specific requirements and select the subject/topic in their consultation. Discuss with your faculty concerned, before making a choice of your subject/topic. Consult experts in the field to make a right choice of the subject. Study various articles / news items etc. appearing in dailies, weekly, monthly magazines to look for a desired topic. Discussions with the relevant firm may help select a proper topic. A critical eye can help you spot the right topic for your project..

After the preliminary screening of the topic we can follow the below steps. 1. Title of the project [Start time T0 + 1 week] The Title of the project means the selection of the relevant project idea/topic from number of choices. This should be carefully decided by the student after discussing with the project guide. The student and guide are assumed to be aware about general requirements for the academic need, the current technological pursuits and the customers/market need or the requirements. This title may slightly change (not basic idea) during or after the completion of the project feasibility study (section-6). 2. Introduction of the project [Start of T0 + 2 week] After the selection of the project topic you must check/answer the following terms..

1.The relevance and importance of the project : 2. why this project, what exists now, what is required and what would be realized as end product. 3. Mention briefly about : technology, models, processes, testing. 4. Expected performance and limitations. ( Write a brief (1 or 2 pages) introduction of the project explaining its relevance and importance.Write about the usages and the benefits.)

3. Requirements [Start of T0 + 3 week] The next step is analyse the requirements/ actual needs of the project and the required specification,components and features of the project. The requirements come or taken or generated from users. Here it is from academic need. Based on the academic needs, the current technological pursuits and method, finding or knowing what the customers/markets need or require, write in steps the project requirements The requirements are expressed in simple language, understandable by one and all people and certainly not only by subject specialists. Avoid using any technical language, that make sense to only few individuals. Write about 10 or 15 important requirements and put them in order according to their importance or preference based on some criteria. Mention how well the end product would be matured, realized and usable. Remember that each of these requirements are to be later analyzed so as to generate general design inputs. From these general design inputs, the designers would generated detail technical design specifications at system / subsystem level.

4. Feasibility study [Start of T0 + 5 week] Requirements were listed in section-3 and therefore the project feasibility study may start. The feasibility study of project must be completed within 4 weeks, considering all aspects of the project mentioned below. (a) Preliminary work done : Write if any related laboratory experiment performed in previous semesters? Write if any related courses/study done in the previous or current semester? (b) Resources available (RA) : Indicate the desired resources within the course or software tools, test data, test facility, integration and demonstration facility. (c) Confidence Factor (CF): Mention your confidence in exploiting the above mentioned resources. 5. Scope / Objectives: [Start of T0 + 9 week] By doing the project feasibility, the uncertainties and ambiguities are reduced. The team is now definite about Resources, Confidence,Viability, Realizeability, Inadequacy and many such factors. Set clearly the project objectives considering the following : The project start and completion date : time two semesters, The number of personnel/work force : Divide the team The quality or standard : as per B.Tech. course. Write very clearly in 1, 2, 3 or more steps the scope/objectives set for the project. The objectives must reflect or address to what exactly is proposed to implement. (While writing the scope , use technical terms like : Software, tools, coding, test, input and outputs, test platforms, standards, simulation, models, techniques, processes, algorithms, hardware systems, methods, fabrications, implementation, integration, accuracy, reliability, installation etc.)

At this stage the Title of the project and its Scope/Objectives are usually agreed and frozen and will not change under normal situation. 6. Requirement Analysis [Start of T0 + 10 week] The general requirements were listed in section-3. To meet in these requirements the feasibility study of project was completed in section-4. The scope/objective of the project have been frozen in section-5. Now analyze these requirements one by one so as to generate general design inputs. Within 4 weeks, the requirement analysis must evolve into : The understanding of over system functioning. The Identification of all standalone or separable functions that may be accomplished as subsystem level task. Identify technologies and group then in to tasks they are to perform. Identify the critical technologies if any ? Conceptualize, and draw an overall system level block diagram which indicating all identified subsystems and their input/output need. Indicate of overall system functionality considering the subsystems level tasks. Prepare a list of component systems, peripheral devices, interfaces/joints , displays, computing and network environment etc. Prepare a list of software, operating systems, drivers etc if any. - Prepare a list of application software, case tools, simulators, databases, visualization and graphics support etc. Listing of I/O specification of not required to buy but used. Listing of test data at the inputs, type of tests to be performed during development and the making of the subsystems, and tests

required during runtime or execution.

Conclude the requirements : Highlight what is already available and what will be newly created or required for the timely completion of the project. Formulate general design inputs. 7. Activity Time Schedule [Start of T0 + 12 weeks] The way, method or the manner in which the project will be executed. Draw a suitable representation indicating the manner in which the project would be executed - from the start to the completion date. The representation is usually a PERT/CPM chart; OR (the X- axis shows time (from start to completion) and the Y- axis shows all project activities.) The time resolution of the X-axis can be monthly but for a small duration (about one year) project the time resolution can be weekly. The activities listed on Y-axis includes all important activities of the project. The body of the chart illustrates the start and completion date of each activity. It should clearly indicate the spread of each activity,their relative start and completion time, and how many tasks wouldrun in parallel. The project activities include Project start date, deciding the project : Title Relevance and importance of the project : writing Introduction Framing of project : Study about Project : Freezing of Project : General design inputs :

Requirements Feasibility study Scope/Objectives Requirements Analysis Implementation Project report System and subsystem level working : design Convert all designs into procedure/reality : Performance evaluation at system/subsystem level : Testing Documentation of all above activities : The activity time schedule must reflect all such things. The documentation is a continuous process from day one, the start of the project.

8. Detail Design [Start of T0 + 13 weeks] Start of system and subsystem level detail design that continues for 6 weeks. Typically a detail design includes : Design a detail from the conceptual layout, level block schematic (in section-6), And within architectural indicate every subsystem then identify every small entity of their input/output and design. Draw functional block diagrams , data flow diagrams for every small entity, subsystem, overall system and other considerations if any. Write the detailed procedure and methods. End of 15 weeks.

Here comes the semester break. 9. Implementation and Testing [Start of T0 + 18 week] The next 10 weeks are for the implementation of the detail design done in section-8 so as to realize the end product, the Scope/Objectives of the project stated in section-5. Start from the detailed plan. Convert all above designs (at the entity, subsystems, system levels) into reality/experiment/simulation. Execute or Run the activity, - step by step for each module, subsystem or any other entity considered necessary for the purpose implementation. -performance evaluation and design validation. Finally integrate all subsystems so as to realize the over system. Perform all system level test, evaluate the results -compare with the project scope/objects (section5) and the requirements (section 6). 10. Project Completion Report [Start of T0 + 28 week] The time left for the completion of the project is 2 weeks. Complete all documentation. Make the Project Report ready for submission. -Make PPT and be ready for presentation. End of 30 weeks.

Note : The time allocations for completing different activity may vary by few weeks from one project to another, but the total time remains same.