Sunday, March 17, 2013
CS619 Final Project and viva voce marking
Disclaimer: This post & the information has nothing to do with official announcements or procedures of marking in Virtual University of Pakistan. This is solely my own opinion, based on my own experience & observations.
Students who have already chosen a Final project or are finished with their viva & waiting for results are curious about what exactly is the markings procedure or how are marks distributed. Here is what I know of. If you have more information, or something to add, please leave a comment I will add it here:
1. Viva, your final presentation is the most important bit of your cs619 course. Even though I have heard that 75% is the documentation you have already submitted & 25% is the viva, but eventually it all comes down to viva. Because during viva is exactly when you make your final impression. Documents you have submitted can all be made by other people, or paid to be made, but your real creativity is shown during viva.
2. I believe they include some specific marks for your personality, your knowledge of subjects you have learnt in 2 (or 4)years, your attitude & your ability to enter the market as a professional.
3. I once raised a question, and I asked from many people, what is the worst case scenario? What can be the reasons for getting failed in project & the only reason I have found so far, regardless of what those people with an F say, its your lack of knowledge about the thing you are trying to pass as your own. You are considered a cheater only when you get caught. Not that cheating is good stuff but I have been where rest of us have been or still are.
4. If you are purchasing your code, make sure you purchase from a source about which you are sure they are not passing around same source code to many students. Ask for a reference from someone who has got it done. A copy case is immediately marked as failed. Its one & only reason for an F in cs619.
5. When you are purchasing code from someone, make sure you get it well ahead of your viva date. This way you have plenty of time to at least learn your code. Many students are under the impression that if they purchase the code, they can save their behind, no, its not just that. You have to know each bit of your code well. Its actually with everything. when you tell someone something is your own, you have to be very well-aware of each detail involved. Otherwise no one is foolish enough to believe your too innocent eyes.
6. No one expects you to have too professionally done work. Even supervisors are not fools they already know that you are just learning & are just a beginner so keep it simple. If your work is too professionally done, then they will pose more & more questions just to test your level of knowledge.
7. Your grasp & your knowledge is the only thing that can get you through. The lesser you know, and they feel that its the least you know, more are the chances they will prolong your viva session. Some people have even reported a viva session of up to an hour. This is because more you say, deeper you get stuck. Say less, to the point keep calm.
Students who have already chosen a Final project or are finished with their viva & waiting for results are curious about what exactly is the markings procedure or how are marks distributed. Here is what I know of. If you have more information, or something to add, please leave a comment I will add it here:
1. Viva, your final presentation is the most important bit of your cs619 course. Even though I have heard that 75% is the documentation you have already submitted & 25% is the viva, but eventually it all comes down to viva. Because during viva is exactly when you make your final impression. Documents you have submitted can all be made by other people, or paid to be made, but your real creativity is shown during viva.
2. I believe they include some specific marks for your personality, your knowledge of subjects you have learnt in 2 (or 4)years, your attitude & your ability to enter the market as a professional.
3. I once raised a question, and I asked from many people, what is the worst case scenario? What can be the reasons for getting failed in project & the only reason I have found so far, regardless of what those people with an F say, its your lack of knowledge about the thing you are trying to pass as your own. You are considered a cheater only when you get caught. Not that cheating is good stuff but I have been where rest of us have been or still are.
4. If you are purchasing your code, make sure you purchase from a source about which you are sure they are not passing around same source code to many students. Ask for a reference from someone who has got it done. A copy case is immediately marked as failed. Its one & only reason for an F in cs619.
5. When you are purchasing code from someone, make sure you get it well ahead of your viva date. This way you have plenty of time to at least learn your code. Many students are under the impression that if they purchase the code, they can save their behind, no, its not just that. You have to know each bit of your code well. Its actually with everything. when you tell someone something is your own, you have to be very well-aware of each detail involved. Otherwise no one is foolish enough to believe your too innocent eyes.
6. No one expects you to have too professionally done work. Even supervisors are not fools they already know that you are just learning & are just a beginner so keep it simple. If your work is too professionally done, then they will pose more & more questions just to test your level of knowledge.
7. Your grasp & your knowledge is the only thing that can get you through. The lesser you know, and they feel that its the least you know, more are the chances they will prolong your viva session. Some people have even reported a viva session of up to an hour. This is because more you say, deeper you get stuck. Say less, to the point keep calm.
SHARE THIS POST
Author: Mohammad
Subscribe to:
Post Comments (Atom)
0 comments: