Download
computer science faculty meeting abet assessment activities n.
Skip this Video
Loading SlideShow in 5 Seconds..
Computer Science Faculty Meeting ABET/Assessment Activities PowerPoint Presentation
Download Presentation
Computer Science Faculty Meeting ABET/Assessment Activities

Computer Science Faculty Meeting ABET/Assessment Activities

346 Views Download Presentation
Download Presentation

Computer Science Faculty Meeting ABET/Assessment Activities

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Computer ScienceFaculty MeetingABET/Assessment Activities Prepared by David Workman CS Assessment Coordinator April 5, 2007

  2. Agenda • Review of Assessment and ABET Time Line • Review of Program Objectives & Outcomes • Review of ABET (a-i) • Summary of Course Descriptions and Data Collected to Date • Next Steps: • Collect Student Evaluation Data (ABET) • Collect Course Assessment Data • Produce/Update Course Syllabii

  3. Time Line • Jan 2008 Institution requests accreditation. • Feb - May 2008 Institution prepares self study report • Jun - Aug 2008 Visit team chairs assigned, visit dates set, team members selected, reports sent to teams • Sep - Dec 2008 Accreditation visit takes place, draft evaluation report generated within 2 weeks of visit • Nov'08 - Jan'09 Draft evaluation report edited and sent to institution • Dec'08 - Feb'09 Institution sends draft response to ABET • Feb – Mar 2009 Evaluation report revised based on institution response. • July 2009 Accreditation Commission (CAC, EAC) meet to take final action • Aug – Sep 2009 Institution mailed notice of action and final evaluation statement.

  4. Time Line Apr08 Mar08 Sep07 Mar07 Dec07 May07 Jul07 Nov07 Jan08 Jan07 Summer 2007 Fall 2007 Spring 2008 Data Collection Assessment & Evaluation/Analysis/Program Improvement

  5. Inventory Curriculum Define (Refine) Objectives Program objectives Current CurriculumStatus Define (Refine) Outcomes & Measures ProposedChanges toObjectives ProposedChanges toOutcomes & Measures Make Changes to Curriculum Collect Internal Assessment Data ProposedChanges toCurriculum Faculty Review Of Assessment Results Collect External Assessment Data EECS Assessment Process External Measurement Alumni Survey (Yes)(Spr 07) Industrial Survey (No) Internal Measurement CS Exit Survey (Yes) (Indirect) Foundation Exam (Yes) (Direct) Course Content (Yes) (Fall 06)(TBD) (Spr 07)

  6. Approved CS Objectives • Objective 1 To give CS graduates the knowledge and skills necessary to participate as an effective team member or team leader in the development of large computer and software systems covering a broad range of engineering and scientific applications. • Objective 2 Prepare CS graduates for professional careers in roles including, but not limited to, the following: computer programmer, software engineer, software systems designer, software applications developer, technical software project lead, computer systems analyst, computer systems programmer, software applications tester and maintainer. • Objective 3 To prepare CS graduates with the knowledge and skills to do advanced studies and research in computer science and related engineering and scientific disciplines. • Objective 4 To equip CS graduates with the communication skills, both oral and written, to become an effective team-oriented problem solver as well as an effective communicator with non-technical stakeholders in computer and software systems development, maintenance and administration.

  7. Approved IT Objectives • Objective 1 To prepare IT graduates with the knowledge and skills necessary to be an effective professional contributor or leader in the design, administration and management of information technology systems, databases and networks commonly used by industry, government, education, research and non-profit organizations. • Objective 2 To prepare IT graduates for professional careers in roles including, but not limited to, the following: IT manager, IT systems analyst, network designer, network administrator, network security administrator, web applications developer, webmaster, database administration, IT project lead, IT quality assurance. • Objective 3 To equip IT graduates with the communication skills, both oral and written, to become an effective team-oriented problem solver as well as an effective communicator with non-technical users of information technology systems and applications. • Objective 4 To prepare IT graduates with the knowledge and skills to conduct advanced studies and research in disciplines for web-based applications, networking, information storage and retrieval, IT security, electronic commerce.

  8. CAC Proposed Changes

  9. CC2001 Knowledge Areas • DS. Discrete Structures (43 core hours) • PF. Programming Fundamentals (38 core hours) • AL. Algorithms and Complexity (31 core hours) • AR. Architecture and Organization (36 core hours) • OS. Operating Systems (18 core hours) • NC. Net-Centric Computing (15 core hours) • PL. Programming Languages (21 core hours) • HC. Human-Computer Interaction (8 core hours) • GV. Graphics and Visual Computing (3 core hours) • IS. Intelligent Systems (10 core hours) • IM. Information Management (10 core hours) • SP. Social and Professional Issues (16 core hours) • SE. Software Engineering (31 core hours) • CN. Computational Science (no core hours)

  10. Course Content Documentation • Instructor • Textbooks • ABET/CAC (a)-(i) • CC2001 Topics and Subtopics • Lecture Topics and Schedule (Mapped to 3 & 4) • Assignment Schedule and Descriptions (Mapped to 3 & 4) • Size data on Programs (SLOC) by Language • Size data on Technical Documents by Type (Pages) • Number of Oral Presentations by Topic • Assessment Topics, Outcomes Assessed, Assessment Mechanism, Assessment Thresholds. • Student performance (Score & Letter grade) wrt Assessment Topics for all students passing the course. URL = http://www.cs.ucf.edu/~workman/talks/

  11. Data Collected to Date

  12. Data to be Collected Summer 2007 Syllabus (New) – Syllabus must be written. Syllabus(Upd) - Syllabus must be updated. Required Courses – Evaluation Data for Exams and Assignments must be Collected (High, Med, Low) - Assessment Data must be collected for the designated outcomes Elective Courses - Evaluation Data for Exams and Assignments must be Collected (High, Med, Low)