Guidelines for Interns
Collect temporary identiy cards.
Get electronic access to students' area. Sign-off
Submit the project report - "Black Book".
Return the temporary identiy cards.
Students' electronic access to the institute servers will be disabled on the last day of project. Objectives
Students are expected to show a great amount of dedication in executing the project from the design stage to a deployable fully-functioning "product". Project Orientation
The students who are selected to do a project in TIFR will have to undergo a preliminary orientation course which will cover basic technology involved in the project. During this course, the students will have to complete any assignments according to the schedule given to them.
Orientation Programme - 2012
Orientation Programme - 2013
Orientation Programme - 2014 Project Assessment
The initial assessment of the project will be undertaken by the supervisor and project leader. Once the initial assessment is satisfactory and cleared, the project will be finally assessed by the project head / project manager. The projects are gauged under the following qualities: General Competence
The specific areas in which you will be assessed are management and organisation, reliability and punctuality, overall technical competence, and your individual contribution to the project. Technical achievement
This assesses the main technical output from the project. It addresses specific issues such as the design, correctness, elegance, usability etc. of the final product and the significance of the work in relation to the expectation of management. Report
The project report has to be prepared well in advance at least 10 days before project demonstration date assigned to your project. Please read "How to write a structured Project Report?" for guidelines in preparing the report. Certificate will be given only after submission of completed project report in soft copy. Project Presentation and Demonstration
One of the most important skills assessed is your ability to communicate your ideas and work. As part of the assessment you will be required to give a presentation and demonstration of your project to your assessment team at least 2 weeks before the final date of project submission to college. Plan and structure your presentation beforehand. Awards
There are various categories of certificates issued at the end of project period. They are The top projects recommended by the assessment team will be given appreciation letters. The work has to meet the quality, time and delivery guidelines defined for each project. Only very few projects get into this "Exceptionally Well Executed" category. Students of all "Completed Projects" will get the Completion Certificates. If the work delivered by the student / team is not satisfactory, the students may just get a Participation Certificate and NOT a Completion Certificate. Project Documentation User Guide
For projects which result in a new piece of software you should provide a proper user guide providing easily understood instructions on how to use it. A particularly useful approach is to treat the user guide as a walk-through of a typical session, or set of sessions, which collectively display all the features of your system. Technical details of how the package works should be in the body of the report. Keep it concise and simple. The extensive use of diagrams illustrating the package in action will prove particularly helpful. Administrator's Guide
For projects which require the intervention of administrator, the administrator guide needs to be prepared which has to clearly articulate the operations which are to be performed by the administrator and also should provide a proper admin guide providing easily understood instructions on how to use it. Technical details of how the system works should be in the body of the report. Keep it concise and simple. Developer's Guide
For all projects you should provide a proper Developer Guide which should reflect on the technical nuts and bolts in the system and should be a clear reference for any future modifications or enhancements to the project. It should follow the exact pattern of a detailed and final software design document with relevant diagrams, workflow diagrams etc. which will throw full insight into the internals of the application and application logic. The extensive use of sequence diagrams illustrating the package in action will prove particularly helpful.