Muffakham Jah College of Engineering and Technology Department of Information and Technology Date: 21st Dec 2013

Common Best Practices for Programming Labs BE- IT I-IV Years I-II Semester Programming Labs (effective from 2013-14) Draft Copy Dear Colleagues, With an aim to improve the student strength, bring seriousness among students and make our existing labs more practical oriented and effective I took the opportunity of eliciting the views of our senior colleagues (T&NT) and also other colleagues and thus prepared a draft copy of Common Best Practices for Programming Labs. I put before you the same for your valuable suggestion before formulating the final copy. The points to be covered under CBPPL are as follows: 1. Wearing of ID cards by students and faculty (T&NT) mandatory. 2. Student to be given attendance for lab only up to only up to 30 minutes post commencement of lab. In case a student comes late i.e. more than 30 minutes post commencement of lab, he/she is to be allowed but no attendance would be given. This should be made clear to the students from time to time. 3. Students should sign log register before accessing the system. 4. No use of cell phones in labs either by students, faculty or the lab staff during conduct of lab. (Phones should be put in silent mode) 5. Emergency or urgent calls can be attended. it is preferred to restrict the call duration to as least as possible. i.e. faculty may be called by their higher ups or they may be required to give urgent message to their peers or higher ups) 6. Faculty needs to be on time or at least 5 minutes early before or on time to the labs. 7. Students should not be allowed to go out during the lab session except emergency. 8. Faculty should mandatorily place a copy of the lab schedule, lab assignments and lab manual with the lab faculty (hardcopy). 9. Lab faculties should take active part in the lab vis--vis become aware of the lab course, help in debugging and monitoring students.

Muffakham Jah College of Engineering and Technology Department of Information and Technology Date: 21st Dec 2013

Common Best Practices for Programming Labs BE- IT I-IV Years I-II Semester Programming Labs (effective from 2013-14) Draft Copy 10.Faculty (T&NT) should avoid browsing the internet during lab an ongoing lab session. 11.Especially in Mini-Project labs student browsing activity should be monitored judiciously. 12.For every lab, the lab faculty should make maintaining of observation book by students mandatory. The observation book should be checked and signed by the respective lab faculty in every lab session. 13.Faculty should prepare the lab assignment list and week wise lab questions completion and intimate the same to students and keep a hardcopy of the same with the lab staff. 14.All faculties should maintain a separate register to record activity done by each student in each lab session. (This helps in knowing which students are lagging behind and who are regularly irregular so that corresponding monitoring can be made easy). Even a report for completion of lab assignments by students should be maintained. 15. Faculty should mark the student attendance on the same day of the lab session. 16.As we all know that we have charts displayed in our labs for the respective course labs conduction in them. In this regards, I want the lab course faculties to review the charts displayed with respective lab course, and get them revised by giving it as assignment to the students concerned. 17.Further a standard format needs to be followed for all the charts. For this I request the lab Incharges to sit together and come out with a common standard format and place the same before the Head for review. 18. A common lab certificate format to me made for lab record i.e. a template and the same kept in the lab with the lab staff so that students do not face the problem of knowing the certificate format. [ the format again need to be prepared by the lab Incharges and place before head for review] 19.Conduct of Internal lab exams should be in the 2nd Last week from the Last Instruction date. A common mechanism for distribution of marks should also be formulated in the benefit of the students. 20.For each lab, a lab related question bank with respect to programs and implementation tools be prepared for the benefit of the students.

Muffakham Jah College of Engineering and Technology Department of Information and Technology Date: 21st Dec 2013

Common Best Practices for Programming Labs BE- IT I-IV Years I-II Semester Programming Labs (effective from 2013-14) Draft Copy I am happy to inform that our Lab faculty has agreed to the proposal of making themselves available in other labs during their free lab sessions so as to make student monitoring and lab executions more effective. Also this would serve our lab faculty in learning the lab course and better equip them. Further there is proposal for students of 3rd year for their mini project work that they me given a project related to network setup and management and specialized open source software installation and maintenance. For this one or two faculties need to make students prepare a proposal and get it executed under their supervision with the support of our lab faculty.

I thus put before you all the above points for your review and valuable suggestions.

Maniza Hijab, Head IT-Dept.