Degree Audit at UC Berkeley

1. Degree Audit at UC Berkeley • Brief Overview • DARS for Students • DARS for Advisers • Transfer Courses and Exceptions • Batch Audits • Batch Audit Reporting System

2. Proposed Upgrade Schedule Fall 2007 – Present: DARS ver. 3.5.4 Spring 2011: DARS ver. 3.5.9.1 Summer 2011: Planned courses with Interactive Audit Fall 2011 or later: u.achieve ver. 4.0.7

3. DARS/u.achieve: A Table-Driven Application

4. DARwin/u.achieve Database • A collection of relational tables where: • DARS rules are maintained • Degree programs • Transfer articulation • Duplication of credit, etc. • Incoming audit requests are sent • Audit results are stored (batch reporting capability) • It is also used to store: • Student transfer courses • Student’s declared major, concentration/specialization • Student exceptions

5. Who uses the Degree Audit system? • Students: currently enrolled and newly admitted undergraduates • Default audit is for student’s current degree program • Can also run a “what if” audit • Can choose to exclude In Progress courses • Advisers: FERPA certification and security clearance • Read-only access to all students’ audits • Security clearance needed to enter exceptions for individual students (department level and/or college level) • Campus offices and administrators • Aggregate data informs campus planning decisions • How many Reading and Composition sections needed? • How many Graduate Student Instructors for next term?

8. Courses included in the audit • Transfer courses, including exams • Courses may articulate to an equivalent course at Berkeley, to a specific requirement (e.g. college requirement), or units only • Graded courses from Berkeley • Courses ‘‘in progress’’ (IP) are included (or excluded) by default; user can opt to exclude (or include) IP courses for each audit requested • Planned courses – requires Interactive Audit component • Interactive Audit allows “planned” or proposed courses to be incorporated into the audit. Courses are marked as “PL” • User can opt to include PL courses for each audit requested * Courses are listed chronologically in the Academic History requirement *

9. Academic HistoryChronological list of courses and exams used by the audit • At Berkeley, the Academic History requirement is displayed on every Degree Program. • CollegeSource provides the option of showing students’ academic history as part of DARSweb, with separate tabs for home courses, transfer courses, planned courses, and transfer evaluation. Courses can be sorted by user-specified fields (e.g. institution, date)

10. Academic History Requirement 1.Berkeley courses 2.Course-to-course articulation (many to one) 3. Course-to-course articulation (one-to-one) 4. Course-to-units only

11. Transfer Courses and Requirements 1. Course-to-requirement articulation 2. Berkeley courses 3. Course-to-course articulation (many-to-one)

12. Transfer Articulation Rules in DARwin

13. Course Screens in u.achieveHome Courses | Transfer Courses | Planned Courses | Transfer Evaluation

14. Exceptions Available to AdvisersGranted on a student-by-student basis Security: UC Berkeley advisers have read-only access to view audit results for all students, but can only enter exceptions for students in their school/college/major Advisers can enter the following types of exceptions: • Course Insertion • Course Placement • Course Removal • Unit or Course Count Waiver • Course Placement with Title Check • Pseudo Course Generation • Marker Exception (used for Concentrations or Emphases) DARS encoders can also change the default catalog year and enter multiple alternate catalog years for different requirements (university, college, major)

15. Interactive Audit and Planned Courses • Access to course planning functionality can be restricted by the institution, e.g. to advisers only • If a student were to enter planned courses (e.g. for a concentration), an adviser could review them. If approved, adviser could enter an exception, effectively “locking in” the courses until a subsequent change is approved. • User can choose to exclude planned courses from an audit • If planned courses are used, the anticipated grades, by default, affect the gpa reported on the audit

16. Planned CoursesStudent plans to enroll in course in the future

17. Entering Planned Courses

19. UC Berkeley Batch Reporting System • Developed for UC Berkeley by Gnarus Corporation in 2007–2008 • Ability to run batch audits by entering selected student ids • Ability to create and run online reports (e.g. Rdg & Comp not satisfied) • In 2008 CollegeSource acquired the software and the Gnarus degree audit division • CollegeSource plans to release an improved version of the software as part of the u.achieve 4.0 series: • BARS – Batch Audit Reporting System (name may change) • Demo presented at the 2010 Users’ Conference • Ability to run a batch audit for a selected student population • XML interface connects to the Student Information System to obtain student ids based on specific criteria (athletes, specific major, etc.) • No reporting capabilities at this time

23. Online Reports

24. Output (Job Queue) Tables • DARwin Version 3.0 A set of 3 tables containing a limited summary of requirement data, sub-requirement data and applied courses • DARwin Version 3.5 A more robust set of 4 tables including Accept/Reject courses • u.achieve Version 4.0 A complete set of 10 tables containing all information produced by the audit including text

25. Contact Information Raúl Infante Office of the Registrar UC Berkeley rai@berkeley.edu (510) 642-9245 Patti Ahuna Office of the Registrar UC Berkeley patahuna@berkeley.edu (510) 643-1138