ACADEMIC INFORMATION AND REGISTRATION SYSTEM OPUS-College

Some Primary Points of Interest Customization Will only be done by the core developers on the kernel of the system (database, primary logic) Will be done by local system developers on User Interface on the one hand and the Reporting (output of the system) on the other.. AND: Specific requirements should be realized through plug-in Modules. Changes on inefficient processes within the university so that the system fits optimally, instead of adapting the system to the inefficient reality. Sustainability (central and local) Does heavily depend on the functionality (system does what users want) And also on the availability of a professional (technical and functional) support organisation, built up of local people. Empowerment (local) Users of the system: learn them how to get the optimal use out of the system. This requires the readibility to change processes and habits of working. IT-developers: focus (in their training) on the transition aspects or objects of the system: interface and reports.

Some Primary Points of Interest “ Focus on how to USE the system NOT how to BUILD it ” (Ed Simons)

A short definition “Opus-College” is the name of a web-based information system for the registration and consultation of information on: Students (personal data, study plan, examination results, previous educational career, absence registration, etc..). Curriculum (structure and content: grades, study programmes, courses, exams, tests...). Lecturers & other staff (all staff members involved in the academic education process). Organizational units (faculties, departments, laboratories, institutes,...). Note: if wanted OPUS-College can also be used as a HRM-system, given the extensive data on staff members which can be stored in the system.

Technical aspects in a nutshell The Opus-College system is based on and built with open source software tools, notably:  JAVA and the JAVA Spring Development Framework for the application.  Ibatis for the persistence (communication of the application with the database).  PostgreSQL as the database.  A web browser as the user interface. Being a web-based application, the browser is all a user needs to work with the system, both for the registration, update and consultation of information and the functional management of the system.  Apache Tomcat as the web server (container).

OPUS-College or eSURA: what’s in a name?  The general or generic name of the system is “OPUS-College”, where OPUS stands for “Open University Systems”, indicating the open source character of the system. The Mozambican or Portuguese instance or implementation of the system is called “eSURA”, which in Portuguese means: (electronic) system for academic registration. The Zambian version is called ‘opus’.  So it is possible that you will see and hear the 2 names being used.

The users OPUS-College is meant for. a. Academic Registry personnel: to register students, and linked information, possibly also information on the organisational units and their studies (depending whether this is centrally organised in the university); further: to produce student cards, diploma’s etc... out of the system. b. Branch, School/Faculty or Department administrators: to register information about their staff members, studies and courses taught and to consult information on their staff and students (if this is decentrally organised in the university), to produce student cards, diploma’s etc... out of the system (if decentrally organised). c. Lecturers: to enter information about the subjects they teach, the exam results they supervise, and possibly their personal data (depending on what the university policy is on what teachers may enter in the system) and to consult information on their students, subjects and exams they supervise. d. Students: to consult information on their study plan, the courses they (have to) follow, their exam results, etc...

The modules of OPUS-College. OPUS-College is a full modular system, based on the OSGI-modular framework for JAVA applications: a revolutionary new service-oriented architecture for the JAVA programming environment. The module structure of OPUS-College is as follows (version as per 1st of December 2011):  A Core Module or Kernel common for all institutions implementing OPUS- College and dealing with all data registration and update functions.  Additional Modules, which can be specified and tailored to the needs and situation of a country or even an individual institution. Currently the following additional modules are in OPUS-College:  A Report Module which holds all the output functions of OPUS-College and which can be tailored to the needs and (style) requirements of each individual university.  A Scholarship Module for registering information about student scholarships.

The modules of OPUS-College. The module structure of OPUS-College at the end of the project (July 2012) will also contain:  An Accommodation Module which holds all the information on housing for students and related payments  A Fees Module for registering information on the fees paid by students.  A Bank Interface between the Bank or the Financial System and the Fees and Scholarship Module in the Student System  Optionally : A Timetable Module for the timetabling and rostering of classrooms and examinations.

Some Modeling and Technical Notes. Object Model

Person Opus User Address Study Organizational Unit Student Subject is 1..* has 1..* Has 1 concerns 1 is authorised for 1..* BA= Subclass from (A is a subclass from B) Legenda: = Association from object = Shortcut for an association from object taught by 1..* (version ) Study YearSubject Block Staff Member has 0..1 has 1..* has 0..* Role has 1..* Branch Has 1..* Study plan has 1..* Grade Type has 1..* has *..* Institution belongs to 1 Has 1..* has 0..* Examination has 1..* Subject Result has 0..1 has 1..* Examination Result Exam Result has 0..1 Contract has 1..* has 0..* has 1..*