Description

This document contains a description of the data model and SQL schema for the MyMyUNSW database, to be used in Project 1.
Background
UNSW handles its administrative information using a version of the PeopleSoft product called Campus Solutions. This system is normally accessed via the MyUNSW portal and is maintained by the NSS unit in UNSW IT, and so it’s variously called PeopleSoft, Campus Solutions, MyUNSW and NSS. The database behind the system is hosted on a large Oracle server, and throughout this document will be referred to as the NSS database.
The PeopleSoft system was installed in 2000 and has been modified/extended over the years to encompass:
• human resources (staff/employees, payroll, etc.)
• financials (purchases, income/expenditure, etc.)
• academic (students, courses, classes, enrolment, etc.)
It is in the process of being upgraded to the latest version of Campus Solutions (CS9).
The current NSS database is separate from the UNSW Handbook, which records all of the official information related to course and program/degree requirements. To support on-line enrolment, NSS does represent some course information, such as pre-requisites, co-requisites and exclusions, as well as enrolment quotas. However, it maintains this information independently to the Handbook, which leads to potential inconsistency. Worse, NSS maintains no information at all about program/degree requirements, which means that students cannot use NSS to monitor their progress through their degree.
The MyMyUNSW database aims to implement a superset of the contents of the NSS database, including:
• people: staff, students
• infrastructure: buildings, rooms, facilities
• organization: faculties, schools, centers
• academic: programs, streams, subjects, courses, classes
Note: there are two places in this schema where we deviate from current UNSW terminology.
A stream is a new term that refers to what the current UNSW Handbook calls a plan or specialization. Streams also encompass the collections of courses that comprise majors and minors in many degrees. Also, in our schema, we use the terms subject and course to talk about a unit of study (subject) and a particular offering of a subject in a given semester (course). UNSW confusingly calls both of these a course, although it also sometimes uses the term course offering for the second.
The academic information includes subject pre/co-requisites and program/degree requirements, as well as all of the descriptive material from the UNSW handbook. This assemblage of information means that the MyMyUNSW database can be used as a basis for:
• on-line course and class enrolments
• managing room allocation and time-tabling
• monitoring progress through programs
• producing the UNSW Handbook
Only the first, and part of the second, of these are provided by the current PeopleSoft system.
Data Model and Schema
This section aims to give an overview of the data model. It concentrates mainly on the entities and their relationships. The details of attributes are provided by comments in the SQL schema.
Some considerations in the development of our data model:
• UNSW runs a number of teaching terms each year (these are also called sessions or semesters)
• a subject is a unit of study in a particular area (e.g. introductory programming, database systems, etc.); a subject is defined primarily by its syllabus
• a course is a particular offering of a subject in a particular teaching term; it has a course convener (also called lecturer-in-charge), perhaps an enrolment quota, and is associated with a number of classes
• a class is a teaching activity at a scheduled time in a scheduled place; examples of classes are lectures, tutorials and labs; a class is associated with a course
• a degree is an award given to a student who completes a specified program of study
• a program is a named program of study leading to one or more degrees
• a stream specifies the precise requirements for study in a specific area; it is used to implement the notions of major and minor
• in a particular program, students choose at least one stream from a range of possible streams (in a double degree, they will choose two streams, one from each set of streams for the constituent degrees); the program will specify precisely what are the allowed/required combinations of streams
there are several different types of requirements:
o subject requirements (core subject, electives, limitations) o stream requirements (e.g. must take one from the BCom majors) o program requirements (e.g. must be enrolled in 3648 to take SENG1010) o UOC requirements (e.g. overall plan needs at least 144 UC) o WAM requirements (e.g. must have WAM of at least 65 for Hons) o stage requirements (e.g. must be in stage 2 of program to take COMP2 courses)
o stream requirements (e.g. complete one major from a set of majors) o miscellaneous requirements (e.g. industrial training)
• in specifying requirements, we frequently need to deal with sets of academic objects (either programs or streams or subjects); we call these (generically) academic groupings
• we use subject groups in specifying subject requirements; each subject group has a name (e.g. “level 3/4 COMP courses”) and an associated set of subjects
• similarly for stream groups (e.g. “set of BA majors”) and program groups (e.g. “all programs offered by CSE”)
• a subject requirement specifies: a subject group, a number of UOC associated with the group, whether this number is a minimum or maximum requirement; this is flexible enough to allow us to describe:
o core requirements (group size 1, must complete 1 course from the group) o alternatives (several related courses, must complete 1 of them) o professional electives (set of courses from one area, must complete k of them) o limitations (e.g. no more than 72 UC of level 1 courses)
• in terms of the ideas above, programs and streams are defined as collections of requirements; a particular student must satisfy all of the requirements before they are regarded as having completed the program or stream
• how to determine whether a student has satisfied requirements depends on the type of requirement:
o for UOC, use the course enrolment information o for course requirements, use the course enrolment information o for miscellaneous, must explicitly record that the student has met them
(because there’s no other data that will allow us to work it out)
• at any given time, each student is enrolled in one program, one or more streams (associated with the program), and generally several courses and classes within those courses; we need to record all four kinds of enrolment
• for enrolment in a program, it is useful to know when the student’s enrolment commenced, when it ended (if it has ended), and their current status (e.g. active, on leave, etc.)
• a schedule describes when in a stream particular courses should be taken; in our terms, it will relate subject groups to streams and associate specific (year,semester) combinations with them

sometimes, we wish to allow a student to vary from the standard requirements of their degree plans; there are three types of substitutions:
o substitution: replace one course by another within a program o advanced standing: get credit for a course from elsewhere (or from a partly-completed UNSW degree) to use in place of some course in a program
o exemption: get recognition for having studied a course elsewhere so that this can be used as a pre-requisite for further study at UNSW
Treat the ER data model description below as an overview, and consult the SQL schema for full details. The ER diagrams below make a number of simplifications to the complete SQL schema: many attributes are omitted, some names are changed (e.g. entity names are singular here, but plural in the SQL schema). The SQL schema has a detailed description of its naming conventions, which we won’t repeat here. There is also a summary version of the schema available, which might be useful as a quick reference once you’re familiar with the details of the schema.
To make the presentation clearer, the data model is presented in a number of sections.
People/Courses/Terms
Entities and relationships related to students/staff/courses/terms …

Comments:
• the Person entity would clearly have much additional data associated with it in a real implementation (contact details, etc.)
note that the use of Subjects.id rather than Subjects.code as a primary key actually allows us to implement multiple versions of a given subject; we also need to know the period over which the particular version is relevant, and this is recorded in the subject record
• in reality, a course offering has a lot of other information associated with it (e.g.
enrolment quotas, assessment schemes, classes); some of these appear in the database, some don’t
• the n:m relationship allows multiple staff to be associated with the teaching of a given course offering; one of these staff is required to be a course convener (this could have been implemented via an extra field in the Courses table to force the above constraint, but since it’s also a Role, we decided to implement it as such and do the constraint via a trigger)
Programs/Streams/Degrees
Entities related to programs/streams/degrees …

… and relationships between them …

Comments:
here, we show minimal attributes for the Program, Degree and Stream entities; see the schema for full details
a program leads to one or more degrees (e.g. BSc, BE/BCom)
• a degree occurs in at least one program (e.g. straight BE, BE/BCom, BE/BSc)
Requirements
Entities and relationships related to requirements …

Comments:
• every requirement is either a o UOC … student must meet minimum/maximum UOC limits o stage … student must be in specified stage of program
o WAM … student must meet minimum/maximum WAM limits o inProgram … student is currently enrolled in one of a set of programs o inStream … student is currently enrolled in one of a set of streams o inSubject … student is currently enrolled in one of a set of subjects o doneProgram … student has completed requirements of program(s) o doneStream … student has completed requirements of stream(s) o doneSubject … student has successfully completed subject(s) o compound … combines other requirements via boolean operator o miscellaneous … other non-computable requirement (e.g. industrial training)

many of the requirement types refer to a set of academic objects (e.g. set of subjects in an elective group); such sets are represented by the AcadObjectGroups table a requirement can be negated via a flag in the requirement record
• using min, max and academic object sets allows you express requirements like o must complete between 24 and 36 UOC from COMP3* courses (subject group)
o must complete one major from the BA majors (stream group) o must be enrolled in a CSE degree (program group)
• if a requirement is really a logical combination of other requirements, it can be expressed as a compound requirement; a compound requirement combines a set of requirements via logical AND or logical OR; compound requirements can be nested
• note that the sets of requirements for Programs, Streams and Subject pre-requisites are implicitly conjunctive (i.e. you need to satisfy all of them before you have completed the Program or Stream or met the pre-requisite requirement for the Subject)
• miscellaneous requirements pick up all of the other non-course-related requirements that exist in various degrees (e.g. industrial training for Engineers); since there are no enrolments records or other kinds of records to check that these were completed, we need an explicit link between the student and the requirement to indicate this
Academic Object Groups
Groups of academic objects that are central to the definition of requirements…

an academic object group (AcObjGroup) specifies a set of academic objects of one type (e.g. a set of streams, set of programs, etc.)
each AcObjGroup has a name which describes its purpose and is used for looking up groups when programs and streams are being defined
o by enumeration (explicitly associating each member to the group) o by giving a regexp pattern to identify the members (e.g. COMP3.*) o by giving an SQL query to lookup the members and return a set of IDs
• in the case of a set of requirements, you can also specify the logic of how the members are defined (conjunction or disjunction)
Enrolment
Relationships for various kinds of enrolment …

Comments:
• students initially start at UNSW by enrolling in a program
• once enrolled, they choose a specific stream (or streams) to study within that program
• this requires them to enrol in courses, and they generally enrol in one or more classes in the course (note that NSS uses enrolment in the lecture class as the way of indicating that a student is enrolled in a course; our schema does not do this)
• all these notions of enrolment have different kinds of information associated with them
• note that the mark alone is not sufficient to determine whether a student has successfully completed a course; they need a passing grade to ensure this (the set of grades indicating a pass includes SY, PC, PS, CR, DN, HD … there is also a PT grade which is no longer used but is included to allow us to deal with old data)
Variations
Variations of meeting requirements within programs…

Comments:
• the purpose of a variation is to indicate that a student has effectively completed one course at UNSW, without necessarily having enrolled in and passed that course
• there are three kinds of variation: substitution, advanced standing, exemption
• a substitution might be used to replace a core course in a plan by some other course if the core course is not available
• advanced standing gives credit towards a degree, based on study towards a different degree either at UNSW or elsewhere (typically, advanced standing is only granted when the degree containing the course was not completed)
• including courses from other institutions means that we need a representation for them; we have used a very simple representation
• finally, exemptions allow us to record that a student has some specific background knowledge (to use as a pre-requisite for some other course); an exemption does not confer credit towards a degree, however
SQL Schema

We have developed an SQL schema based on the above data model. With the above background, you are now in a good position to examine this schema, keeping in mind that the schema does not follow precisely what has been specified above in all cases.
Database Contents
The student/course/enrolment part of the database has been populated using real data which was transformed to make it anonymous (i.e. names, marks, enrolments changed to protect the innocent). The subject/program part of the database was populated by a mixture of data from MAPPS, plus enrolment data. In fact, some of the MAPPS data is derived from an earlier version of this database, where information was scraped from the UNSW Online Handbook. The class data was populated using data from the UNSW timetable site. The requirements part will be populated from data in the MAPPS database. There will also be some subsequent manual tweaking of the data to ensure that there are interesting tuples to play with.
Note that the task of populating such a large database is extremely time-consuming and so many parts of the database are unpopulated or populated only very thinly. Some parts have data that is close to reality, while others have data that is a pale shadow of reality. In order to get a feeling for what is actually present, you must spend some time exploring the database when it is eventually populated.