1. Preparing for an Accreditation Visit David Workman, Susan Bethel (CS) Ron DeMara, Damla Turgut (Cpe) Kalpathy Sundarum (EE) School of Electrical Engineering and Computer Science University of Central Florida April 3, 2009

2. Outline Background Formation of the School of EECS – Program Objectives & Outcomes – Curriculum Unification Unified Assessment Process – Two Assessment Cycles – Curriculum Oversight and Review Committees – Instruments for Data Collection and Analysis Preparing for the Visit – Self Study (Project) – Assessment Website – Mock Review – Course Materials Display Post Mortem

3. Background Institutional Effectiveness and Program Improvement (1996) (Operational Excellence and Assessment Support) OEAS Annual Assessment Cycle – Write/Revise Assessment Plan ( Program Objectives & Measures) – Collect Assessment Data (Senior Exit Survey, Alumni Survey, IAB ) – Review Data and Report Results Program Objectives – CpE and EE (ABET a-k) – CS & IT (Roll your own) CS joins College of Engineering (CECS) 1999 College Accreditation in 2002 – CpE and EE (ABET) – CS (CSAB)

4. Formation of the School of EECS Established in Fall 2005 – CS, IT, CpE and EE Unified Mission and Common Interests Planning for 2008 Accreditation (Fall 2006) – Develop Program Objectives – CS and IT accredited under new ABET/CAC – Define a Unified Assessment Process Curriculum Unification – Identify and Eliminate Course Duplication – Re-structure Pre-requisites – Revise Curricula – Implement in Fall 2007 – Concerns

5. Unified Assessment Process

6. Course Descriptions Title and Number Pre-requisites Course Custodian Textbooks & References Topic Outline Course Outcomes – Assessment Instruments (Embedded Exam Question, Project Deliverables ) – Performance Threshold ( Expected level for students passing the course) – Mapping to Program Outcomes ( for each Program for which course is required)

7. Assessment Data Collection Spreadsheet Outcome Mapping#1#3Total Pts Total Outcome #1 Total Outcome #3 Q1…Qm Student 11310231310 … Student n871587 Max Pts151025 Threshld12618#1 Threshld#3 Threshld Mean Stdev

8. Table 2: Outcome Mapping Pgm1Pgm2Pgm3…PgmN Course Outcome #1X% Course Outcome #2Y% … Course Outcome #MZ% Totals2/21/11/20/1

9. Table 3: Program Performance Pgm1Pgm2Pgm3…PgmN Course12/21/11/20/1 Course23/53/4 … CourseM2/53/3 Totals5/73/63/5

10. Writing the Self Study Writing of the Self Study is a Project – Requires a Manager or Coordinator – Requires Planning (Time & People) – Requires Commitment from Contributors – Requires full cooperation of unit administrator Involves People at all Levels in the Academic Organization – College – Department /School – Library – Personnel – Enrollment Services Involve People with Special Knowledge – Administration (Personnel & Budget) – Accounting – Graduate Coordinator – Undergraduate Coordinator – Lab Supervisor – Systems Admin

11. Creating an Assessment Website Access to Information – Mission, Objectives, Outcomes (for each Program) – School Assessment Process – Course Descriptions (each Program) – Assessment Reports (each Program) – Program Performance Summaries (Table 3) Visit our Website http://abet.eecs.ucf.edu/

12. Mock Review When to Schedule – After Self Study has been completed – Some Course Display Materials should be available – Leave time for changes before submitting Self Study to ABET Benefits to Computer Engineering – Statements of Program Ojectives – Student/Faculty Ratio – Paper Trail of Assessment Process – Demonstrate “Closing the Loop” Benefits to Computer Science – Weakness with Assessment Data ( only one cycle ) – Concern about assessing program outcomes – Concern about address CAC a-k Benefits to Information Technology – Deficiencies in curriculum – Pre-mature (withdraw application for accreditation)

13. Course Displays & Team Workplace

15. Other Preparation Advice Prepare Faculty – Know the Assessment Process – Know where to Find Information – Be familiar with Self Study Prepare Labs for Visit – Tidy – Safety Issues – Security Procedures and Access

16. Post Mortem Computer Engineering – Concern: Student/Faculty Ratio (36:1) Remedy – Concern: Faculty supporting Software Engineering Remedy Computer Science – Weakness: Regular Collection of Assessment Data (2 or more cycles) Remedy – Concern: Covering and Assessing CAC (e)(g)(h) Remedy – Concern: Teaching Faculty keeping current in discipline Remedy

17. Questions? Thank You!