UMS

University Management System

Object model and software by

Jean-Philippe Aumasson <jpnossa@free.fr>

Jean-Baptiste Langlois <jeanbaptiste.langlois@wanadoo.fr>

Cergy-Pontoise university, France

2004/2005

Contents

General use case

Actors' use cases

System states

Classes 1/2

Classes 2/2

Implementation

Human-machine interface

General use case

What ?

Software to manage a university educational system.

Who will use the program ?

University administration employees, teachers, students.

How ?

Employees and students on their private machines, or on public computers, like students only do.

=> Need to authentify users, and give them access restrictions.

Actors use cases

The system actors are the school employee, the teacher, the student:

Has total “write” access, can add/remove teachers, students, diplomas, careers, courses, and above all validate a step.

Can add his marks to the students, and perform all students actions.

Is allowed to view his personal information, and the lists of teachers, students, and courses.

System states

Notion of time, dynamic program

=> Need to simulate time

Schoolyear divided in 4 specific periods

=> At everytime, program in one of those states ~ cycle.

Start of year Half-year 1

Passing exams Half-year 2

Classes 1/2

System classes:

Career, Course, Cursus, Diploma, Mark, Person, Privileges, Sid, Tid, Student, Teacher.

A teacher is identified as his Sid, that is unique.

A Teacher is a subclass of Person, like Student.

An analog association for Student / Sid.

A user is viewed by the system as a set of privileges ~ the specification of his account.

Each known Person is a user => link of composition.

Classes 2/2

Classes Course, Cursus, Diploma.

Career ~ kind of studies (biology, etc...)

Diploma ~ any graduation obtainable (ie Master 2)

Course ~ a subject in a diploma (ie course of calculability in the year of Master 1 of the computer science career).

Any diploma has some courses => link of aggregation.

Implementation

PHP (functions) / HTML (HMI) / SQL (DB)

Pros:

PHP

Portability (local/Internet, Linux, Mac, Win...)

Easy database interaction (more than Java!)

Can be used on any computer without installation

HTML

Compatibility (viewable on any browser)

Easy-to-use interface.

Simple code, easy to modify.

Human-Machine Interface

All static HTML, only interaction components are rolling menus and buttons.

=> easy learning and use, fast loading.

No Javascript, XML, Flash, etc...

=> light and simple pages, portability ++.

Features

Different installations :

local installations

distant server installations

Security :

Role of include

Main actions monitoring with logs

Access protection: timeout, error 401, pwd...

Protected against worms

Customization :

4 skins

5 languages

Conclusion

Deadline respected

Multiusers system ID/pwd for each user.

Simulate several years of study, can:

Creation of careers, courses and diplomas.

Students can pass one or several exams.

Exams may be passed at passing exams.

Three type of marks (oblig., elim.,or normal).

Etc...

Licence : GNU/GPL

2005-01-14T13:34:20