| Faculty: | SCHOOL OF COMPUTING | Academic Year: | 2008/2009 |
| Department: | COMPUTER SCIENCE | Semester: | 1 |
| Module: | PROGRAMMING METHODOLOGY - CS1101S | ||
| Note: | Feedback on module in general | ||
| Qn | Items Evaluated | Module Avg Score | Nos Responded |
|---|---|---|---|
| 1 | Overall opinion of the module. | 4.727 | 33 |
| 2 | Grade likely to get for the module. | 4.485 | 33 |
| 3 | Difficulty level of the module. | 4.273 | 33 |
QN\SCORE | 5 | 4 | 3 | 2 | 1 |
Qn 1: Overall opinion of the module. | Excellent | Good | Satisfactory | Unsatisfactory | Poor |
Qn 2: Grade likely to get for the module. | A | B | C | D | F |
Qn 3: Difficulty level of the module. | Very Difficult | Difficult | Average | Easy | Very Easy |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | Excellent | Good | Satisfactory | Unsatisfactory | Poor |
| | | ||||||
Module | | | 24 (72.73%) | 9 (27.27%) | 0 (.00%) | 0 (.00%) | 0 (.00%) |
Module at Same Level (Dept) | | | 237 (17.10%) | 570 (41.13%) | 416 (30.01%) | 117 (8.44%) | 46 (3.32%) |
Module at Same Level (Fac) | | | 315 (13.17%) | 1059 (44.29%) | 804 (33.63%) | 157 (6.57%) | 56 (2.34%) |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | A | B | C | D | F |
| | | ||||||
Module | | | 19 (57.58%) | 11 (33.33%) | 3 (9.09%) | 0 (.00%) | 0 (.00%) |
Module at Same Level (Dept) | | | 343 (25.62%) | 531 (39.66%) | 312 (23.30%) | 120 (8.96%) | 33 (2.46%) |
Module at Same Level (Fac) | | | 534 (22.88%) | 1152 (49.36%) | 485 (20.78%) | 130 (5.57%) | 33 (1.41%) |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | Very Difficult | Difficult | Average | Easy | Very Easy |
| | | ||||||
Module | | | 11 (33.33%) | 20 (60.61%) | 2 (6.06%) | 0 (.00%) | 0 (.00%) |
Module at Same Level (Dept) | | | 356 (25.70%) | 672 (48.52%) | 299 (21.59%) | 48 (3.47%) | 10 (.72%) |
Module at Same Level (Fac) | | | 397 (16.63%) | 936 (39.21%) | 930 (38.96%) | 109 (4.57%) | 15 (.63%) |
| Q1. | Please comment on the strengths and weaknesses of the module, and suggest possible improvements. |
| 1. | Very good lecture. Not much improvement needed! The strength of the module is that the Prof is aware of how to teach his students. Sometimes, he didnt teach alot, but throw us into doing problem sets where we can finally grasp the concept! Very good! |
| 2. | concepts taught are rather difficult to grasp for those without programming knowledge and without alot of time onhand. however tutorials and problem sets given force students to think so that students can learn new things in the process instead of being spoonfed |
| 3. | It is a very interesting module, but the workload is a tad heavy. Granted, we've been fore-warned about the heavy workload prior to the start of the module, but I find that the workload is pretty taxing. I'm very interested in Scheme, and because of this module, I end up spending an excessive amount of time on the Problem Sets and end up compromising on my other modules. |
| 4. | should focus on only one programming language-scheme...the teaching of Java looks rush |
| 5. | The module is especially tough regardless whether or not the students taking it has some prior programming background, which is in tandem with the objective of the module: Managing Complexity. The fact that such a huge (and obscure) thinking concept can be fit into a single module really proves that the module employs the right staff and the right teaching materials. Possible improvements would require more support from the School so that more interesting and mind-boggling problem sets could be tailored for students (robot soccer perhaps?), and perhaps by employing a CA system (which the current marking system approximates to). This way, students may be given more time and resources to internalise what they learn in lectures and tutorials and work in projects, be it as a group or individual. The practical exam may perhaps be broken down to two instances as well, to reduce the workload on the students while at the same time ensuring that students are not only studying for the sake of a single exam. This may mean more work to the teaching team, but given the small size of the class, it should not be impossible to implement. |
| 6. | Strengths: The teaching staff is very helpful and they care a lot about the students. So students will not feel 'lost' in the module, because of office hours are held on weekdays and students can also get help from the IVLE forum. Weaknesses: There are a lot of materials to cover, so Java topics cannot be covered very well. The students who take this module have different backgrounds (some have Java background, C++ background, or no programming backgrounds at all). This makes it harder to pace the lessons to suit everyone perfectly. |
| 7. | Strengths of this modules includes being able to learn really cool and advance stuff ! Improvements possible would be to teach perhaps > 2 programming languages at one go. |
| 8. | Good module to learn programming, overall. Very interesting but tough subject matter. Unique module for 1st year students. |
| 9. | Good Lecturer. |
| 10. | I think this module is generally good for teaching of the programming concepts. It makes us think more on the problem solving concepts rather than programming syntax. However, the bridging to Java is quite brief, which might be a disadvantage when we have to continue with 1102S in Java. |
| 11. | Perhaps to recommend more to those with Java programming background due to the huge jump involved from 1101S to 1102S in terms of Java competency. |
| 12. | There is too much things that we need to learn within a semester. However I think it also help us get a better start of university life. the fast phase of everything in university life enable us learn how to muti task and also to cope with it. Since Scheme is all about managing complexity, I think it also help us in the future module. |
| 13. | this module is really helpful for first year student who is unfarmiliar with programming. learning concepts is the main aim. From this background, students can go further. The weak point is the gap between CS1101S and CS1102S which makes some last lectures of Scheme (cover Java) is not very easy to catch. |
| 14. | The module gives students a very stong foundation in programming. |
| 15. | nil |
| 16. | The workload cannot reflect the MCs assigned to this module, namely, workload is a bit heavy than expected. Lecturer Dr Ben is excellent. Lectures are vivid and quite comprehensive. All the PS are brilliant designed so that people suffered first and learned afterwards. Many thanks to Dr Ben for bringing me a good start in computing and many thanks to all TAs for your hard work through this whole semester. |
| 17. | Very good module taught by excellent lecturer and strong support team of the tutors. |
| 18. | I'm very impressed by this module. It's wonderful..The teaching team is excellent!!!! I'm sure it is the best of the best modules in SOC |
| 19. | This module enhances my thinking a lot. But it's a bit too fast and the work load is too much. |
| 20. | The java part is a little blur and would be better if begins with some basic principles. especially for students who has no programming experience. |
| 21. | good |
| 22. | Some parts are obscure, need to be slowly elaberate. |
| 23. | The module teaches me not only a programming langwage, but also new ways of thinking. However, the workload of this module is too heavy, this module costs me several times more time than any other modules I take this sem. |
| 24. | Very interesting, but a bit of time wasting for year 1. |
| 25. | strength: demonstrate programming concepts and thinking weakness: too fast and unable to understand and apply all the stuffs |
| 26. | - Made us learn programming concepts and not the syntax in another aspect. - A lot of helplines for people who were weak. - Recitation is a good way to revise the concepts learnt during lecture. - Pace was a bit fast for people who did not program before. - Java conversion was very fast paced. - Since streams is unique only in Scheme and not used in other languages, why not drop it? Make the last problem set in Java instead of stream to make people have more hands on practice with Java. |