1. Degree Audit: It’s Much More Than Setup Neumann University Aston, PA Larry S. Friedman (lfriedma@neumann.edu), Registrarlfriedma@neumann.edu Lorraine Fulker (lfulker@neumann.edu), Assistant Registrarlfulker@neumann.edu James A. Williams (williaja@neumann.edu), Administrative Analystwilliaja@neumann.edu

2. Initial Questions to Consider….. What are the goals in developing Degree Audit?  Enhance academic advisement  Assist in curriculum development  Enable students to track academic progress  Increase student awareness of degree requirements and progression  Record waivers/exceptions to program requirements  Facilitate degree certification  Create/increase comfort level with the Student Administrative System (particularly via Web Advisor)

3. Initial Questions to Consider….. Who Is your BASIC audience for Degree Audit?  Faculty/Advisors  Deans/Department Chairs  Students

4. Initial Questions to Consider….. How do you convince Deans and faculty that Degree Audit is a better way to advise students?  SHOW THEM, SHOW THEM, SHOW THEM!!! Arrange individual training sessions Use examples unique to each division/department Create “what if” scenarios Be able to explain what a Degree Audit evaluation is Provide documentation  Be prepared for questions (and resistance)

5. What is a Degree Audit Hierarchy? How you want the Degree Audit to flow –Order in which Academic Requirements are checked –Specific to General (or vice versa) –Determined by the Special Processing Code of the ST.VALCODES ACAD.REQMT.TYPES

6. What is a Degree Audit Hierarchy? Datatel’s delivered Degree Audit flow:  Major (MAJ) requirements  Core (GEN) requirements  Allied (OTH) requirements  General (ELE) electives Neumann’s Degree Audit flow:  Core (GEN) requirements  Major (MAJ) requirements  Allied (OTH) requirements  Minor (MIN) requirements  General (ELE) electives

7. What is a Degree Audit Hierarchy? How you want Degree Audit to look –Order in which requirements are printed –Specified in the Academic Program Requirements (APRS) screen for each program In Neumann’s Degree Audit output:  Core (GEN) requirements  Major (MAJ) requirements  Allied (OTH) requirements  General (ELE) electives

8. Degree Audit Hierarchy [cont.] Determine where requirements can be used twice. For example, a major requirement could also satisfy a core requirement. Don’t be afraid to question requirements Be able to explain requirements in STANDARD ENGLISH Minimize the use of RULES

9. SETTING UP PROGRAMS…. There are multiple components to each program in Degree Audit….  Academic Program Name  Academic Program Requirements  Academic Program Sub-requirements

10. ACADEMIC PROGRAM NAME For each previously established Academic Program Code, you need two basic components that utilize your institution’s naming conventions…  Degree Type… [M.S., B.A., B.S., A.A.]  Content Area … [ACT, BIO, etc.] Example: BS.ACT

11. ACADEMIC PROGRAM NAME [2] For double majors, add the additional major code to the original program.  BS.ACT.BUS [This program would represent a double major in both Accounting and Business Administration] For programs with minors, add to the program code with a minor code…  BS.ACT.BUS.MINOR [Bachelor’s of Science with a major in Accounting and Minor in Business Administration]

12. PROGRAM REQUIREMENTS Block Registration FA SAPESIS

13. PROGRAM REQUIREMENTS (Development Course)

14. PROGRAM REQUIREMENTS (Activity Eligibility Rule)

15. PROGRAM REQUIREMENTS

16. PROGRAM REQUIREMENTS [2]

17. PROGRAM REQUIREMENTS [3]

18. PROGRAM REQUIREMENTS [4]

19. PROGRAM REQUIREMENTS [5]

20. PROGRAM REQUIREMENTS [6]

21. PROGRAM REQUIREMENTS [7]

22. PROGRAM REQUIREMENTS [8]

24. PROGRAM REQUIREMENTS [9]

25. PROGRAM REQUIREMENTS [10]

26. PROGRAM REQUIREMENTS [11]

27. MINOR REQUIREMENTS

28. MINOR REQUIREMENT [2]

29. MINOR REQUIREMENTS [3]

30. NARRATIVE RULE FOR HEADER AND FOOTER PARAGRAPHS PERSON WITH LAST.NAME NE ‘’

31. HEADER NARRATIVE

32. FOOTER NARRATIVE

33. USING DEGREE AUDIT

34. USING DEGREE AUDIT [2]

35. USING DEGREE AUDIT [3]

36. USING DEGREE AUDIT [4]

37. USING DEGREE AUDIT [5]

38. ITEMS FOR SUCCESS  Know your audience  Have Realistic Expectations  Know your academic environment Know the curriculum and academic programs Evaluate/understand inherited data Look for LOGICAL progression in requirements Recommend changes as needed  Make Degree Audit SIMPLE AND CLEAR Use KISS method in setup, training and documentation Assume NO PRIOR KNOWLEDGE among users  Think and Test, Test, Test  Make friends!!!!!!!!!!!!!!!!!!!!

39. QUESTIONS