Flagship Vision for FIU SCIS SCIS Curriculum Management by Oscar Aparicio and Gabrielle Moestar Fall-2012 Mentor: Tim Downey Client: Eric Johnson Flagship Vision for FIU SCIS
Outline Background Problem Scenario Current System Proposed Solution Conclusion & Future Work
Background What is a curriculum? Where can I find it? Website Major Map Catalog
Website
A guide designed to help you graduate in a timely manner Major Map A guide designed to help you graduate in a timely manner The map is divided by semesters and contains courses required for your major, notes and critical indicators.
Catalog A complete enumeration of major’s offered by the department with its associated courses.
In common… COP 2210 COP 3337 COP 4710 ……..
The information is inconsistent!!! Problem Scenario The information is inconsistent!!! What electives should I take next semester? Looks at curriculum. COP 3402: Fundamentals of Computer Systems. Tries to register on panthersoft. Course doesn’t exist. Goes to Advisor. Advisor: Fundamentals of Computer systems is no longer CDA 3103. There are one too many places to update minor changes, that impacts the students directly.
Current System USER Advisor A Advisor B Maintained by an advisor in an xml formatted file. Designed and maintained by an advisor in a .docs or .pdf formatted file Populated and maintained by an advisor in a .docs or .pdf formatted file. Advisor B
Proposed Solution Course Info & Requirmenets Curriculum Major Map Advisor A Catalog A centralized location where the advisor can create and update course information and requirements which are updated Advisor B
Interface Student View User Interface Interaction and view Allows instructors to keep all documents in sync without maintaining different files for each document. Allows students to view the correct courses and major requirements.
What happens in the background?
Scenario
Scenario
What is in this database?
Catalog Versioning Active Catalog Catalog 2 Catalog 3 Data Data Data Version 2 catalog 3 Data Version 3 catalog 1 Data catalog Data Version 2 catalog 3 Data Version 3 catalog 1 Active Catalog catalog 2 Catalog 2 catalog 3 Catalog 3
Data Redundancy??? Garbage? Inefficient?? Data Redundancy??? Garbage?
Even Better!!! Catalog 1 Catalog 2 Catalog 3 Data Version 1
Result Activate catalog 2 Active Catalog 1 Prospective Catalog 2
Conclusion / Future Work User friendly system Versioning data Accurate propagation of information Low data redundancy Future Work Algorithm for major map Expand access with web services Automatic creation of charts Integration with PantherSoft
Questions?