BC KS CM Planning Phase

IUG Meeting August 2012

BC Systems Background

• Mainframe (UIS)– Custom mainframe system currently used for Financial

Aid, Course Catalog and Enrollments, Student Accounts• Course Description Database (CDD)– Custom APEX database– Maintains course description information because

mainframe couldn’t store it• BC Portal– Displays information from UIS for course offering info

and CDD for course catalog info

Planning Phase Goals

• Evaluate the work done during the Proof of Concept and determine how much work can be reused

• Determine the scope and approach for implementation of Curriculum Management

• Develop strategy and approach for converting data from UIS and the Course Description database into KS Curriculum Management

• Develop strategy and approach for KS Curriculum Management integration to other BC systems

Don’t create a process that doesn’t currently exist just to use functionality in CM

Planning Phase Approach

• Functional Meetings (bi-weekly)– Bi-weekly working group meetings– Review KS CM functionality– Review UIS functionality– Review CDD functionality

• Technical Meetings (as needed)– Data Conversion– Integration

• Advisory Group (monthly)– Discuss Scope and Policy issues

KS CM Scope Decisions

• Course Info– In scope; have a few BC fields to add

• Governance– May use to identify School and Dept but BC does not

currently have a defined workflow for course approvals; out of scope

• Course Logistics– In Scope; may not use course formats

• Learning Objectives– No concept of this at BC; out of scope

KS CM Scope Decisions (con’t)

• Course Requisites– Some rules in UIS; some text in CDD; in scope but will be

manually configured to the extent possible• Active Dates– In scope

• Financials– Out of scope given that this currently resides in Student

Accounts• Authors and Collaborators– Out of scope given not planning to use approval process

KS CM Scope Decisions (con’t)

• Supporting Documents– Out of scope given not planning to use approval

process• Programs– Determined to be out of scope until have a better

sense of how these will be used in KS Enrollments

KS CM Policy Decisions

• Course Renumbering– Subject code approval– Course number approval– Process approval

• Scope– Programs– Learning Objectives– Course Requisites

Project Deliverables

• Implementation scope and approach document• New course number strategy document• Strategy and approach for converting data from UIS and the

Course Description database into KS Curriculum Management• Strategy and approach document for KS Curriculum

Management single sign-on integration through the BC portal• Strategy and approach document for KS Curriculum

Management integration with other BC systems• KS Curriculum Management Implementation Project Charter• KS Curriculum Management Implementation Project Plan• KS Curriculum Management Risk Management Plan• KS Curriculum Management Budget