154
edits
Changes
→Topics Discussed
Cathy Leung, Elliott Coleshill, Peter McIntyre, Mark Fernandes, Ian Tipson, Marcel Silva, Danny Abesdris, John Selmys, Andrew Smith, Sunny Shi, Peter Liu, Chris Szalwinski
===== General Topics Discussed =====
* IPC144 - CL - we should compress the list of topics covered in depth by all instructors in the course - CS asked CL to create a list of the key topics (variables, control flow, pointers, functions, arrays, structs, files) - CL students should be directed to other topics without spending too much time
* IPC144/BTP100 - JS, AS, IT, CS - malloc and free should be introduced in IPC144/BTP100 - would precede new and delete in second semester and set a better groundwork for understanding memory management and manipulation in third semester
* unit testing OOP244/BTP200 - AS Test 1 results show good distribution of grades - should problem with high DNAs needs to be introduced gradually - several standard tools are availableinvestigated
* ICA - CL - a non-credit pre-course should be created for students to learn basic tools and skills such as git at their own discretion - no objections
* CDOT - MF, CS, IT - skills specifically required for working in CDOT should be taught separately in a non-credit course run and taught by CDOT faculty - students who wish to work in CDOT should be encouraged to take these courses to improve their chances of getting hired at CDOT (no objection)
* Best Practices - DA, IT - a set of best teaching practices should be collected to assist faculty in the programming courses
* Fresh Assignments - CL, IT, MF - a culture of creating fresh assignments should encouraged - many faculty simply recycle old assignments (no objections, some skepticism)
* Stacked Assignments - IT, CL - students who have not completed one part of a stacked assignment should receive an object version of that assignment so as not to be held back relative to other students in the class
* Content Heavy - DA - DA noted that programming courses are still content heavy
* Stacked Assignments unit testing - IT, CL AS - students who have not completed one part of a stacked assignment should receive an object version of that assignment so as not to be held back relative to other students in the classintroduced gradually - several standard tools are available* ===== OOP344/BTP300 - =====Learning outcomes:* comfort with inheritance (abstract base classes, multiple inheritance), polymorphism (interfaces, virtual functions, templates), data management, data structures (linked lists and multi-dimensional arrays), standard template library, function objects, lambda expressions, collections of objects and containers, file streams, multi-threading - * remove cross-platform coding, variadic functions,* need new assignments
== To Be Done ==