1. S.I.E Development
Project
Administration of Sick Notes
Application
Group Members
 Jarred Osborne
211045047
 Tariq Rajie
202032353
 Siraaj Arnold
211052884
 Zikhona Ngacase
211033782
 Mandisi Blou
211014486
 Reinier Eiman
212252739
 Bradley Baartman
209215178
 Thawir Jakoet
212087266

2. Table of Contents
1. Introduction ...................................................................................................................................2
1.1 Purpose....................................................................................................................................2
1.2 Scope .......................................................................................................................................2
1.3 Overview ..................................................................................................................................2
2. Description.....................................................................................................................................3
2.1 Product Functions .....................................................................................................................3
2.2 Operating Environment .............................................................................................................3
2.3 User Characteristics...................................................................................................................3
2.5 Design & Implementation Constraints ........................................................................................4
2.6 Assumptions & Dependencies....................................................................................................4

3. 1. Introduction
1.1 Purpose
The purpose of thisuser requirementsdocumentistodescribe the functional andnon-functional
requirementsforthe developmentof anAdministrationof SickNotessystem.ListedBelow isthe
processesandexplanationsdescribingthe systemanditsfunctionality.
1.2 Scope
The Administrationof SicknotessystemisanApplicationwhichwill improve the currentmanual-system
beingusedbyCape PeninsulaUniversityof technology.Userswill be able tostore informationdirectly
intothe University’sdatabase aswell asretrieverelevantinformationneeded.The systemisspecifically
designedforLecturersandSecretarieswhowill be the mainentitiesinvolvedinthe usage of the system.
The systemwill workasa complete userinterface thatwill allow the usertoread/write informationto
and froma database, thusimprovingthe currentprocessesinvolvedinstoring/retrievingSickNote
Recordsof students.
1.3 Overview
Section2 defines the general functionsof the application,itsoperatingenvironment,user
characteristics,anddesign andimplementation constraints,alongwithourassumptions.

4. 2. Description
2.1 Product Functions
Administrator
 Admin will be able toinsert,modifyanddeleterecords
 Scan inhardcopy “SickCertificate”documentsandstore itas a digital copy
 Scan an identification cardusingabarcode scannerto retrieve required credentialsandstore
the information intoadatabase.
Normal Users
 General Users will be able tologintothe system
 Afterloggingin,all relevantrecords pertainingtothe specificuserwillbe retrieved
2.2 Operating Environment
The Administrationof SickNotesSystemisanapplicationthatwill operate overacloudcomputing
networkplatform, therefore allowingboth Administrators andNormal Users accessto the system
directlyfroma remote location.
2.3 User Characteristics
 Users of the systemare mainlyLecturersandSecretaries
 Users of the systemare assumedtohave basicknowledge of ComputerApplicationTechnology
 Technicianswouldneedtobe trainedthroughworkshopsaboutthe applicationand itsinternal
modules.
 The technical trainingwouldbe implementedtoallow technicianstofix small problemsthat
couldarise such as hard diskcrashes,systemfailuresorpowerfailures.

5. 2.5 Design & Implementation Constraints
 The “Sick Note Administration”systemwillbe operational 24hoursa day.
 MS AccessandSQL will be usedas the database andengine respectively.
 AdministratorsandUsersmayaccess the applicationfromanycomputerthathas Internet
browsingcapabilitiesandanInternetconnection.
 AdministratorsandUsersmusthave theircorrectusernamesandpasswordstoenterintotheir
accounts anddo actions.
 The informationof all usersmustbe storedina database thatis accessible bythe application.
2.6 Assumptions & Dependencies
The application needs the following third party products
 MicrosoftAccessserverto store the database.
 Mendix todevelopthe application.
The success of this system depends on
 The uploadingof the certificatesshouldbe secure andfast.
 The applicationshouldbe user-friendly.
 End usershouldbe satisfied.
 Techniciansshouldbe welltrained.
 A stable internetconnectiontostore andretrieve documents.

6. 3. System Requirements
3.1 Development Language – Java
 Java has been chosen as a developer language to assist in developing the new
proposed system.
 We will make use of the oracle database in order to store, update and alter
information.
 The reason for choosing java was quite simple; our development team finds it easy
to code within this language and their familiar with this environment as this is
somewhat of their comfort zone.
 Using the oracle database to store information was also an easy decision as we will
be attempting to create pl/sql procedures to incorporate within Net Beans.
3.2 I.D.E – Net Beans
 The system layout (i.e. the look and feel of the system) will be created in net beans.
 All coding done in net beans will be that of java coding.
 Net Beans is equipped with much better revision control.
 Net beans has two features which stand out in software development including the
dropdown form feature as well as the github feature which allows software
developers to both work on the same application that can be uploaded and
downloaded directly to the cloud.
 Net beans is also known to run on various platforms(i.e. windows, mac os, Linux,
etc.) to accommodate a wider user frame

7. 3.3 Database – Oracle – SQL Developer
 The oracle database will be used in order to store all relevant data that will be
updated/ edited or deleted.
 We also feel that oracle builds efficient and effective databases.
 Since the whole group is familiar with using oracle for a database, it helps the
progress of this new system flow much more smoothly, as coding will be applied
more effectively seeing we all have knowledge in this area.
The reason for choosing this database is because of the fact that coding will be done within
oracle and saved as procedures and or triggers which will be used in a manner to assist in
making this system as feasible as it possibly can be.

8. 3.4 System Architecture
server
* Secretary scans student card
* Secretary scans sick note of student
Secretary updates student database
Lecturers retrieves student reports
Student
Admin
Lecturer
Student Report
Report will be produce for each student
Sick Note System
Architecture
Lecturers views student reports
Figure 1 - System Architecture

9. Core Goal
The core goal of the depiction above is to illustrate how the system is intended to work.
You will have the student that will produce his/her sick note to the admin clerk along with
his/her student card. The admin clerk will scan the student’s card with a bar code scanner
in order to open up a file with all the students details displayed before her/him. The next
step will be to get an electronic copy of the sick note within the student’s folder thus the
admin clerk will scan the sick note and store it to the particular students file. A report will
be generated with details such as; student particulars, specific dates that a student missed
out on exams or assessments as well as a total number of times that a student has missed
exams/assessments.
Lecturers will get the privilege to access the system with his or her unique credentials.
Once access has been granted the lecturer can view any students report based on how
many times he has missed assessments etc.
Reasons for the above architecture
 Ability to store, search, retrieve, and print electronic images of scanned paper
documents associated with an account.
 The electronic format must follow an intuitive flow for data entry and provide
features such as highlighting, table driven drop down lists, pre populated fields, re-
centering and capturing system dates.
 Import all existing electronic account information into new data repository. Verify
that data meets all current business rules.
 Scanned documents should be made readily available for email or for display needs.
 Image Scanning will take advantage of existing software Solutions.
 Account History Report specified/categorized by student number and course ID.
 Account Notification Mail Merge Report.
 Scan Search, Retrieve and Print Document.
 Minimum of 2 months of parallel testing against existing process.
 Create detailed and meaningful user documentation.

10.  Create a condensed training course (Estimate 2 Hours) to be attended by ###
employee over a specified period.
 Ensure data security and integrity, allow for security anomalies to be inserted or
documented for maintenance administration
 Administration levels should be implemented to limit access to critical information
without authorization
 Detailed work breakdown structure will be created to insure a minimum amount of
operational interruption.
The above listed reason for the architecture is but a few reasons that we want to
implement as core mandatory functions/features to the system. Moving the current manual
system to an electronic suite can be seen as the future for a university of technology seeing
in today’s life how technology seems to be changing at a rapid pace, what better way than
to move technology ahead on our own grounds. Using this system will improve the current
system in place as it is more feasible, easier, reliable and quite adaptable to implement. We
believe that the new system will be beneficial to the university.