Quality Assurance Committee
Quality Assurance Committee (Nov 2012 – August 2013)
Useful Links:
ACM Education Policy Committee (http://www.acm.org/public-policy/education-policy-committee)
Computer Science Curricula 2013 – ACM/IEEE-CS Joint Task Force (http://ai.stanford.edu/users/sahami/CS2013/)
ABET Criteria for Accrediting Computing Programs, 2013 – 2014 (http://www.abet.org/DisplayTemplates/DocsHandbook.aspx?id=3148)
NAQAA (http://www.naqaae.eg)
CS2013 Curricula Matrix Edited by myself to show core 1, core 2, and elective topics in separate columns, but this is based on the strawman report, which is now updated in the Ironman report.
NSF/IEEE-TCPP Curriculum Initiative – I proposed to integrate PDC topics in multi-courses using this proposal (PDC_mhelal_CCIT_AASTMT), and it was accepted in 30/7/2013.
CCIT join about 80 current early adopters from the previous five rounds of competition. The support can attempt to provide access to a heterogeneous Linux cluster with multi-core and GPU compute nodes. The support require that we need to carry out detailed evaluation and provide feedback to the curriculum working group each Spring as follows:
1 Update the tables of Appendix I for courses you are teaching by inserting Bloom level, number of hours for topics covered, and hints on “How a topic was taught/integrated in existing topics.” We may also add new topics if you employ those. The direct link to Appendix I is http://www.cs.gsu.edu/~tcpp/
2. We will share and disseminate the course syllabi, content, and teaching material by posting them at CDER resource site maintained at http://www.cs.gsu.edu/~tcpp/
3 Provide data and results of the proposed evaluations. If possible, provide statistical data on pre-post tests for individual students in your courses on PDC topics.
I will receive contributor-level access in due course to upload to CDER resource site. Any faculty staff member interested in joining the program, please forward to me the contributed material and I will upload it.
