ITC508 Object Modelling: Enrolment System Elaboration

Desklib provides solved assignments and past papers to help students succeed.

ITC508 - OBJECT MODELLING
ASSESSMENT ITEM 2 - ELABORATION PHASE
Student ID:
Student Name:
[1]

Table of Contents
List of Figures............................................................................................................................2
Introduction................................................................................................................................3
Requirements..............................................................................................................................4
Functional...............................................................................................................................4
Non-Functional......................................................................................................................5
Use Case Diagram......................................................................................................................7
1. Student Use Case................................................................................................................8
2. Course Coordinator Use Case............................................................................................8
3. Admin Use Case.................................................................................................................9
Fully Developed Use Case Scenario....................................................................................10
Class Diagram..........................................................................................................................12
Class Diagram Documentation............................................................................................12
Event-partitioned System Model..............................................................................................13
Event-partitioned Diagram Documentation.........................................................................13
Conclusion................................................................................................................................14
References................................................................................................................................15
List of Figures
Figure 1: Use Case Enrolment System.......................................................................................5
Figure 2: Class Diagram.............................................................................................................9
Figure 3: Event-partitioned Diagram.......................................................................................10
[2]

Introduction
The Melbourne's leading university, called the National University, provides various facilities
such as diploma, graduation & graduation in courses such as Information System, I.T.,
Accounting, Business as well as Law, Arts as well as Humanities. The university has 3
semesters to offer, i.e. Term-1, Term-2 & Term-3 beginning in various segments of the whole
year. The university is planning to implement the enrolment system so as to decrease the
energy as well as time in the process of student enrolment & reduce overall enrolment
process sophistication.
[3]

Requirements
Functional
Functional requirements are those requirements that address specific goals for students to
register, such as adding a class, dropping a class, & enrolling in the system. Functional
requirements address the requirements for achieving a specific user scenario goal. Functional
requirements define what should be done by the system. Design of the system details the
overall plan for stating the functional requirements for the whole system. The software's
requirements are as follows: login, registration, & name, add a course, delete a course, search
a course, discussion forum, announcement activity, grade & change at any time & release the
result.
The first step in the enrolment process is registration. So, the student will have to register
first, and then they can access the enrolment system. The users will be asked to give
information such as name, address & email address followed with the student id number
which will be mentioned in the COE letter. Once the user entered the details & saved them,
he/she will be redirected to the page where course selection will be made. The user will have
many options for the major subject such as IT, Info Systems, Business, & Accounting & Arts
with the term selected for the course. Once the overall process of subject & term selection is
done, then the system will verify the details entered by the student if they are correct or not.
After verification, the user will be shown a list of all the available courses in the chosen term.
The user can select between 3-4 courses & accordingly the class timings too. The student will
be shown with the class strength (40 is the maximum strength). Another major functional
requirement is the payment option. After all the above processes are completed, the user will
be redirected to the payment portal where he/ she will pay for the enrolment. There will be
various options given for payment like the master card & debit card or designated acc. no.
Once the user pays, the system will then verify the whole submission & then generate a
receipt of the transaction (Laplante, 2017).
As we know the user will have to access the system, before moving to the enrolment screen,
each user must log in. Similarly, while exiting the enrolment system, each user must also sign
out. Every user must log in to access the system. Now on the enrolment page, the user will be
shown different data related to the particular student who is logged in. There is various
information shown to the user such as course name, student strength in every course so that
the student will be able to choose which of the following course is the most liked & which
[4]

one is the most disliked. This page will also show the lecture schedule for the courses in
which the user is enrolled. If the student chooses a course of which he has not passed the pre-
requisite, there should be a proper check to manage it. Similarly, it is not possible to enrol a
student in more than a no. of courses.
Non-Functional
Requirements which aren’t covered in the functional requirements ae to be covered in the
non-functional requirements. They determine criteria that evaluate the functioning of the
system instead of particular behaviours. The system’s architecture details the plan for
implementing non-functional requirements (Abrahamsson, Salo, Ronkainen & Warsta, 2017).
The nature of the system is decided by the non-functional requirements. Non-functional
requirements deal with reliability, performance, safety & other factors not related to specific
functionality. Maintainability, documentation, execution, use capability, etc. Non-functional
requirements address reliability, performance, safety, interoperability, privacy & other
variables that are requirements which are not linked to specific functionality. Maintainability,
documentation, implementation & use capability, etc. (Laplante, 2017).
There are various non-functional requirements which should be fulfilled while developing the
project which is as follows:
 Privacy
o The enrolment system must protect the overall privacy of the user.
o The enrolment system must prevent students from checking other’s grades.
o The enrolment system must provide with a customized user visibility personal
information policy.
 Availability
o The enrolment system must be highly available.
o The enrolment system must not have unpredicted down-time.
o The system should be available for 24*7.
o The enrolment system must only have downtime at hours which are of low
intensity.
 User- Friendly
o The overall system must be user-friendly.
o The enrolment system should be a bilingual system for all the other countries
students.
[5]

o There should be only a one-time login for accessing every content on the
enrolment system.
o A user-friendly user interface which will remain consistent for the whole
session created by the user.
o For all the students there should be a descriptive UI for when the user needs
some information regarding something he/she will read it.
 Overall Accessibility
o The enrolment system should have a high accessibility
o There should be additional features as well, for example, the system should
have functionality for the blind students as well as some audio feature.
 Secure System
o The overall enrolment system should be secure as it contains information of all
the students.
o Only the student who is authorised for the account credentials he/she is given
will be used to access the portal (Laplante, 2017).
 Inter-operability
o The overall enrolment system must have a high inter-operability
o The enrolment system must export to widely used timetable formats
(permitting users to import timetabled lessons into a private calendar)
[6]

Use Case Diagram
Figure 1: Use Case Enrolment System
[7]

[8]

1. Student Use Case
Brief
The student has access to the enrolment system, can register, login, view grades, pay fees.
View schedule & course details, choose major & term etc.
Description Step-By-Step
 Students registers
 The student chooses major & term
 The student chooses course & time schedule
 Student Pays
 Student gets enrolled.
 The student chose the time schedule
o The system displayed a schedule list for the course
 The student chose to view grades
o The system displayed the grades.
2. Course Coordinator Use Case
Brief
The course coordinator has access to the enrolment system, can add grades, add a course, can
do student enrolment, view student details & view reports.
Description Step-By-Step
 Coordinator selects add grades
o The system lets the coordinator add grades to the student
 Coordinator selects student details
o The system displays particular student details
 Coordinator selects to add a course
o The system lets the coordinator add a course to the subject.
[9]

3. Admin Use Case
Brief
The admin has access to the enrolment system, can log in, add department or edit it, can view
user details & also remove the user, & verifies the user registered (Bhuyan, Ray & Das,
2017).
Description Step-By-Step
 Admin chooses to edit or adds department
o The system lets the admin make changes to the department
 Admin chooses view user details
o The system displays user details
 Admin verifies the user registered.
[10]

Fully Developed Use Case Scenario
Name Enrolment System
Actor Student, admin
Stakeholders Student, Project Manager, coordinator
Description Student wants to view the time schedule for the course he/she is enrolled in.
Pre-condition  The user must be registered on the system. If not registered then no
access to the system would be given.
 To view the system portal the student must log in. If not logged in, no
details will be shown.
 The enrolment system will be kept fully secure as only the authorised
users will be able to access the account.
[11]

Process Flow Action System
The student registers on the
enrolment system
The system requests the student for
details such as name, mobile,
student ID etc.
The student is asked for choosing
the major with the course & time
schedule.
The system requests the student to
choose from the given choices.
After the selection of the courses is
completed, students pay the fees
The system requests the student to
pay the fees via credit card, debit
card or any other payment mode.
The student now is registered & is
ready to login to the system
The system requests the student to
enter login credentials to enter the
portal
Student goes to the course section The system displays the home page
from where the student can go to
the course section
The student selects the course &
view timetable
The system displays the time
schedule of the course in which the
student is enrolled in.
Student wants to download the time
schedule
The system displays an option to
download the particular time
schedule.
Post Conditions As soon as the student is done with the work on the enrolment system, the
student must destroy the session by logging out of the system.
Handling Exceptions  If the login credentials are entered wrongly, an error will be thrown
that either the password or the ID is wrong.
 The system might be under maintenance so, throwing an error of
under maintenance on the system’s page.
 Unable to download error throw if the servers are not able to fetch the
files from the cloud.
[12]