This document tracks the ABET CAC accreditation for the B.S. in Computer Science.
- 2009-2010 Accreditation Policy and Procedure Manual
- 2009-2010 Criteria for Accrediting Computing Programs
- 2009-2010 Proposed Changes to the Accreditation Criteria
- Computing Self-Study Questionnaire (Word Doc)
- Computing Self-Study Questionnaire Supplement (Word Doc)
- ACM Computer Science Curriculum 2008
We are in the process of replacing the document server, so for the moment the links to the local copies have been disabled. Thanks!
Board of Directors
Course Content Matrix
Course Folder Checklist
In order to complete the accreditation process for the B.S. degree in Computer Science, materials must be collected for assessment from each course (required and elective) in the program. The courses must measure the outcomes specified for each course. The faculty should be in charge of the creation and collection of all materials with the help of the lab assistants. The following must be documented and collected for each course.
- A standard syllabus for each course must be constructed that meets the accreditation guidlines. A template for the standard syllabus is available as a word document: syllabus.doc.
- A set of objectives and outcomes needed for the course needs to be documented in accordance with program objectives and outcomes. The material collected must show that the students meet the objectives through the outcomes of the course.
- For each graded assignment (tests, homeworks, labs, projects, programs, essays, presentations, etc.), six (6) examples of student work will be collected. This work should be converted to electronic form unless the submitted work is already electronic. These examples should include:
- Two (2) examples of excellent work for the graded assignment
- Two (2) examples of average work for the graded assignment
- Two (2) examples of poor work for the graded assignment
- An end-of-course assessment must be performed by the faculty for the course being taught to assess the course for meeting the defined objectives.
All documentation will be collected electronically and kept on the document server and all documentation will be kept in the course folders on the wiki server. For assistance in scanning documents into PDF files, see Yu Qian in the main office. All electronic sources need to be converted to PDF files and can be done through Microsoft Word.
Privacy issues are of great importance in the collection process. The department is bound by federal law through the Family Educational Right to Privacy Act (FERPA) of 1974, which restrict institutions from releasing student information. Therefore, all record of student name and student ID must be removed BEFORE the document is scanned. Be careful to examine each sample to remove all instances that would identify the student's work. Edit electronic versions to remove all instances of a student's identity before converting to PDF form. Any hard copies of the original work created for scanning should be destroyed after converting to PDF form.
- CS 2114 Structured Programming* (coordinator: Jason Causey)
- CS 2124 Object-oriented Programming* (coordinator: Gidget Scrivner)
- CS 3113 Data Structures* (coordinator: Dr. Ed Hammerand)
- CS 3213 Assembly Language Programming* (coordinator: Dr. Hai Jiang)
- CS 3223 Operating Systems* (coordinator: )
- CS 4433 Artificial Intelligence* (coordinator: )
- CS 4543 Database Systems* (coordinator: Dr. Hung-Chi Su)