I have one.
We can vote on whether to have it or not later.
Marks Automation System (Continuation)
It was partly carried out in PSOC-2012 (But we can start afresh, because that might be a little messed up.)
Abstract
Currently teachers manually enter marks for every subject of every student for every semester(each branch) in an excel sheet.
Also the students has to go to the teacher to see their marks. Some go in short break, some in lunch break, some after college, some after a week, some never.
What we can do?
1. Go to each department, speak to a few teachers and confirm whether this process is still existing and whether its tedious for them.
2. If most of them say Yes. Then it is a problem.
How do we solve this problem?
Create an intranet site where both student, teacher, department office staff can login.
A teacher can login and update the marks of all the students for the subjects that he/she is handling.
A student can login and see the marks of all the subjects that he/she has taken up.
The admin/department staff can login and download details as excel.
Advantages
This process will eliminate the teacher having to move to and fro department office and interacting with so many students who just want to see their marks at various times.
This process also eliminates the work to be carried out by department staff.
Also the students can check their marks with ease for T1, T2 etc.
What went wrong for completion of this?
The reason why this couldn't complete in the summer was because it was single person working (Abhinav) and it was a little too much for him to learn it entirely and implement it.
How can we do this right this time?
We create a 5 member engaged team who are really really interested.
We decide on the right technology (unlike last time where we had decided to do everything from scratch html, css, javascript (not even jquery), php) - use some framework instead.
Sit with the team and provide them focused training on the framework(one of us who has knowledge in that area), source control (git - sandeep) and decide on documentation techniques.
Sit with them when they kick start so that they get a hang and then can completely maintain this on their own.
We can also do code reviews now and then to see if they are doing it right.
(All this looks complicated, but if we split helping them amongst ourselves should be possible).