 Good morning to all of you, myself, Hashmi Essay and my colleague, S.G., both of us are from MGM School of Engineering, Nanded, Maharashtra. At the outset, I would like to thank my director, ma'am, Dr. Mrs. Geetha Lathkar and my chairman, Sri Kamal Keshwarji Kadam, due to whom I am here. And I would like to also express our deep sense of gratitude to Dr. D.B. Phataksar, who has accommodated us even after the online registration got closed down. So, thank you, sir, for all that you did for us. Today, just a brief intro about our college. MGM started in 1984 and already we had completed 25 years. It started in 84 with just two streams, that is computer science and civil engineering. Under the leadership of our chair minister, that is Kamal Keshwarji Kadam, who was an education minister and his alumnus of IIT Bombay. And right now our campus is of 34 acres and it has got a strength of 1500 students. We have got five UG programs in different disciplines of engineering and we have got two PG programs in engineering disciplines. And we have even collaborated with the Pittsburgh State University of the U.S. for offering master's programs as well as UG programs over there. And we have even collaborated with Oracle, IBM, and Microsoft, and many more companies to provide training to the students and for the development of the infrastructure at our campus. Our college is affiliated to Swami Ramananthith Matwari University, which can be found on this URL, srtmu.n.ac.n. Now, going towards the syllabus of computer programming, in our university pattern, we have got two courses on computer programming. One is the fundamental of computer programming, which is common for all the branches. And after that, that is in second year, we have got UPS programming, which is only for the IIT and the CAC branches. So here we'll just look into the syllabus of this particular computer programming, which is common for all the branches. Now, all the students, irrespective of the discipline, they will be studying this fundamentals of computer programming. This course is made up of 125 marks. And 80 marks are for the theory exams, which are conducted by the university. And tests, which are conducted at the college level, you can call the internal exams, which are of 20 marks. And the practicals or the term work we call it, it is of 25 marks. Totally, the course is made up of 125 marks. Out of that, 80 marks are university exams and 45 marks are at the college level. And this course, for this course, every week, we have to conduct four hours of theory sessions. And two hours of practical are conducted for this particular course. The course is divided into six units. As you can see over there, the different units are there. Like you have unit one, it talks about the computer fundamentals. And it will be covered in six hours. Unit two, it talks about the data structures. It is covered in six hours. The third unit is for eight hours. It talks about the arrays. And the fourth unit is about pointers. It is covered in six hours. And the next unit is on structures and unions. It is covered in eight hours. And after that, the sixth unit is on file system. It is covered in six hours. Totally, the course is delivered in 40 hours duration in the whole semester. And the test, which we conduct, is after every two units. After completing two units, we have got the first test. After two units, we have got the second test. And finally, after the rest of the two units, we have got the third test. Now, the textbook that is followed for this course by our university is programming with, say, that is Venugopal. Another book is from Rakesh Agrawal. And the third one is Yeshwant Connector. And there are a few reference books which are followed for this particular course. As far as practicals are concerned, we have got a list of 11 practicals. Again, in the first few practicals, we tell the students about the basics of the computers and the other peripheral devices. In the next session, we talk about the basics of the Unix. That is how to open a Unix and how to compile the programs in GCC and how to edit the programs in GCC. And then after that, the students go for implementing the different programs on the different concepts in the Unix programming, sorry, in the C programming environment. Like, we have got a couple of programs on loops and so on, like arrays. Programs on structures, units, and so on. Here, just we give the topic, we don't give a specific program. The reason behind this is if we give a specific, like, you should write a program for computing perimeter of a particular thing, or if a problem statement is exclusively given as a list of program assignments. What was happening? Some in the nearby, like, institutes or other small roadside shops, what they do, they prepare the solutions. And all for the all 40 programs which are given completely, the solutions are ready made available and the students, they don't spare the time to, like, to write the programs on their own. And that's why here, the things are just vaguely written. You have to write the programs on arrays. So, for every semester, what array program will be there, it will differ from faculty to faculty. And that's why the chances of copying from other sources gets reduced because the different institutes or the other vendors who want to provide some solutions, they don't know what type of programs are getting executed or are getting conducted in that particular semester. So, that was about the programming that we take in our college. Then regarding the evolution, that is evaluation pattern, we have, like, the term work we call, it is internal 25 marks. Typically it is for the practical evolution or maybe the programming evolution. So, therein we have got 20% is for the attendance and 20% is for writing the journals. And the 20% marks are there for the assignments and the 40% is for the viva. So, the viva is conducted at the end of the semester based on the complete syllabus of that particular course or for the computer programming. And we have got progressive evolution by conducting the test. In the control, we conduct three tests, each one of 20 marks. And out of that, the best of two, that is, the average is taken. And the university papers, it is of 80 marks and it is of three hours, wherein there are, like, 10 questions and the students have to attempt any six. Again, that question, it depends on, like, the question paper will have both the, like, programming and there is some theoretical stuff into that and the other things. The computing facilities at our, you know, college, we have got nine labs and we have got more than 250 IBM pieces. We are having EDUSAT lab already set up. We have got seven servers from IBM. We have got four MBPS Lease Line and the whole campus is connected by a fast Ethernet and OFC connectivity. And I would like to show you the question papers which we have. This is the university papers that is conducted, like, at the end of the sem. Typically, it is for the 2009. As you can see here, it is of 80 marks and it is a three-hour paper. Some instructions over there are given and we have, the paper is divided in two sections, section A and section B. Section A is of 40 marks and section B is of 40 marks. Typically, section A is on the first three units and section B is on the rest of the three units. Again, it is not essential that the sections should be covering that specific part. It depends on the faculties. Those who design the question papers. Now, most, as you can see, this is the first question. Then we have got other questions over there, like talks about the flow chart. Then we have got something related to the the handling of the program but a statement is given and they have to write a program in C and a thing is given here. They have to generate, that is, an output which would look like this. Then we have got some hand-drawn and this was one section. Here, like, again, we have got to write a program for addition of two three-in-two-three matrices and again, hand-drawn of the program and here we have got a section B wherein, like, some theory questions are there and after that you have got a few programs given that the students have to write the programs like this is the ten questions we have got. So, this is the fundamental course which is compulsory for all the branches. Apart from this, in our campus, we have got the BCS, we have got the MCS, even they have got a computer programming that is fundamental course with a little bit of variations here and there but in all, in my campus, like every semester or every year, I can say, nearly seven to eight hundred students are undertaking a course on computer programming that is fundamentals of computer programming and basically using C only but for the next semesters, only the computer and the IT students will go for object-oriented programming concepts and maybe C++ or using Java. What do you mean by the journal writing? The students, like whatever programs are they are supposed to write, first of all they have to write the logic of that. Statement is given, okay. You will be given, like, write a program to print the mark sheet of the students. So, that will be the problem assignment statement and in that, they will write the logic. What way they are going to have? They may write an algorithm for that particular program and after that, they may even draw the flowchart for that program and then they will come to the lab. In the lab, they will do the coding. They will take the, they will execute the program and they'll show the output to the faculty and then they have to take the printout of that particular program and that printout plus the other stuff that they have written related to that program, that will be their one program assignment. That way for the whole semester, they'll be doing somewhere around 30 to 35 different programming assignments and that will be put together in a file, in a journal and that will be submitted to the department. Yeah, it will be similar to the project record. No, because the term, in our university, this term is being used since quite long. The file that is prepared is called as a journal. So, of course, when we talk about the research, the journal is something different. It's not in that context. Yeah, we have like minimum 75 is compulsory and above 75, like if a student has got 90% and above, he will be getting 5 marks, 5 out of 5, because it is for 25 marks and that's why the attendance works out to be 5 marks and if they are somewhere between 85 to 90, he gets 4 marks, then 80 to 85 will be getting 3 marks and 75 and above, he will be getting 2 marks. That way we have the division of the marks for the attendance. This is one question not only to you but to everybody else. This first course, typically what is the percentage of students who fail? How much? 5-0. So, sir, I disagree with him. No, it won't vary, but in your university is 50%. What about Nandi? 400. No, no, I am talking about the first course in programming. Just this first one, I am not talking about general failure. This subject, programming. Like, sir, in our case, it is somewhere around 30 to 35%, not more than that, like 70% or sometimes 75%. 30 to 35%. One-third, roughly. 20%. 20%. Here is a question that I have as a teacher. Let's say it varies between 20 to 50%, which is non-zero. Now, if a first-year student comes to my college who has no clue about programming, not required to know programming and if the student fails, who is responsible student or teacher? If a single student fails, there is some problem with that. We also have failures, by the way. The point is, does our system, not just the teachers, but the system as a college, university, do we take this accountability or responsibility? Is there any serious discussion every year as to how you can reduce the failure? At our college, we have this thing. So, what is the feedback mechanism? Meaning, does it, so, net outcome, for example, I can understand, first time when you start a close, there would have, let's say, 25% failure. Over the last five years, the percentage has remained same. Then there is some concern. Yeah, that's, it varies. Vacation batch, that's the makeup classes. So, normally what we see is, if we simply push the student and make them pass things, we ask the dean to university, the evaluation is in our own hands, but we never do that because the students will never learn anything. No, no, no, that's not the point. The point is not passing them. So, what we do is, we conduct vacation classes and we have extra lab because during vacation time they'll be learning only this for 20, 25 days. So, they can really understand the basic concepts and then they pass. So, they can use something like a repeat course or something. Yeah, yeah, they have to repeat the course. No, that is there everywhere. Even in IIT, same thing, that if you flunk a course, you'll have to re-register for it sometime. Not a supplementary. If they fail, they have to repeat the course. You may have supplementary or whatever. The issue is, I like that approach better where you have a summer vacation class because supplementary means that student is only reappearing for evaluation. Whereas, actually the reason that student failed is because student was not adequately prepared. Now, supplementary is for a genuine reason. If they have medical reason, if they fail to appear for the end semester exam, we give supplementary, but it's not for a real failure case. So, here's a question. Because if I see the number of classes, for example, number of lectures or the labs, very well-defined, sufficient number of hours, et cetera, et cetera. Yet, if such large number of students fail, what is it that we are missing as teachers? Sir, I would like to add one point to this because in our admission system, because typically in Maharashtra State, what happens? The admission, they are centralized. So, like in the first, we have got multiple rounds of the admission process. Oh, the colleges start late in the first round. Yeah, the colleges start early, but the students get admitted late because what happens in the first round? I mean, the lectures start late. Lectures are started in the beginning only. Students come. Yeah, that's like... Okay, thank you very much.