Workload matrix

Tiew Wen Yuen Armos Raj Joshua Rakesh

TP019738 TP014614 TP024031
Introduction

ER modeling

Normalization
Process
Database schema

Data dictionary

SQL statement

Screen shot

System development
Timetable
FYP
Consultation hours
Introduction
A database is a collection of information organized to provide efficient retrieval. The collected
information could be in any number of formats (electronic, printed, graphic, audio, statistical,
combinations). There are physical (paper/print) and electronic databases. A database could be as
simple as an alphabetical arrangement of names in an address book or as complex as a database
that provides information in a combination of formats.

The Lecturer Schedule Management System is a database system which can be used by lecturers
and students to plan consultations, FYP presentation schedules, and Midpoint schedules and
integrate these with the lecturer’s time table. From this system, lecturers can place and publish
the schedule for the consultation hours while students are able to book appointments/ slots for
the published consultation schedule. This system will feature the adding, modifying and deleting
of records as well as a login feature for both students and admins. The purpose of this system is
to be able to process the booking and scheduling of appointment and consultation hours with
lecturers in an organized manner. In the following segments we will display how this is done and
exactly how convenient it is for all parties involved.
ER modeling
Business rules
A business rule defines or constrains one aspect of your business that is intended to assert
business structure or influence the behavior of your business. Business rules often focus on
access control issues, for example, lecturers are allowed to input and modify the marks of the
students taking the courses they instruct, but not the marks of students in other seminars.
Business rules may also pertain to business calculations, for example, how to convert a
percentage mark (for example, 91 percent) that a student receives in a seminar into a letter grade
(for example, A-). Some business rules focus on the policies of your organization, perhaps the
university policy is to expel for one year anyone who fails more than two courses in the same
semester.

Lotus University’s Lecture Schedule Management System uses various business rules in relation
to their database. These rules specify the capabilities of the students, admins, and lecturers when
using the Lecture Schedule Management System. The business rules that have been applied are:

Admin

 Update timetable
 Publish FYP ( Final Year Project )
Lecturer

 View FYP
 View timetable
 Publish consultation hours
 Update consultation hours
Student

 Book consultation hours

 View lecturer timetable
 View presentation timetable
 Book consultation hours
 View lecturer name
 View day/time
Database schema
Normalization process

UNF
 Schedule system (timetable_ID, venue, intake, intake size, module, day, time, lecturer, consultation_ID,
venue, day, time, date validation, FYP_ID, day, time, venue, date, staff_ID, name, student_ID, name,
intake, lecturer_ID, name, module)

1NF
 Schedule system (timetable_ID, venue, intake, intake size, module, day, time, lecturer, consultation_ID,
date validation, FYP_ID, date, staff_ID, student_ID, lecturer_ID, module)

2NF
 Admin( staff_, name)
 Student (student_ID, name, intake)
 Lecturer (lecturer_ID, name, module)
 Timetable (timetable_ID, venue, intake, intake size, module, day, time, lecturer)
 Consultation hours (consultation_ID, venue, day, time, date validation)
 FYP (FYP_ID, day, time, venue, date)
Data dictionary
A Data Dictionary is a reference work of data about data (metadata) which is compiled by a
systems analyst to guide them through the analysis, design and implementation stages. It is more
commonly known as the central storehouse of information on the system’s data. Others define it
as a document which is used to collect and coordinate specific data terms, as well as confirm
what each term means to different people in the organization. A Data dictionary is used to
provide documentation, eliminate redundancy, and validate the data flow diagram for
completeness, and accuracy.

Data Dictionary includes:

 Data Flow
 Process
 External Entity
 Data Store

Data Flow
Name – Lecturer Registration
Description – Input details for registration
Origin – Lecturer
Destination – Verification
Record- Registered Members

Name – Student Registration

Description – Input details for registration
Origin – Student
Destination – Verification
Record- Registered Members

Name – Successful Registration

Description – Registration completed
Origin – Registration
Destination – Registry Information
Record-

Name – Module Details

Description – Module information
Origin – Administrator
Destination – Managing Module
Record- Module File

Name – Verification
Description – Identify invalid details
Origin – Obtain Information
Destination – Successful Registration
Record-

Name – Details Of Intake

Description – Intake Details Which Used For Create And Edit Intake.
Origin – Registry Information
Destination – Registry Information
Record- Intake Record
Name – Reject
Description – Failed to register for verification.
Origin – Verification
Destination – Admin
Record-

Name – Modify Intake

Description – Changes intake
Origin –
Destination –
Record- Intake Record

Name – Student List

Description – Students currently registered
Origin – Student
Destination – Verify Student’s Intake
Record- Registry Information

Name – Intake Code

Description – Identifying The Intake To Let The Admin To Schedule It Within The
Others Intakes.
Origin – Intake
Destination – Time Table Scheduling
Record-
Name – Class
Description – Classroom information, location and occupancy
Origin – Classroom
Destination – Schedule Time Table Of Classroom
Record- Admin

Name – Presentation/Time Table Scheduling

Description – Schedule for students to view the date for their presentations and
timetables
Origin – Admin
Destination – Registry Information
Record- Intake Record

Name – Consultation Hours Scheduling

Description – Schedule for students to view and book consultation hours with their
lecturers
Origin – Lecturers
Destination – Consultation Hours
Record-

Process
Name – Registration
Number – 1.0
Description – Store Lecturer And Student Details In The User File
In Data Flows - Lecturer And Student Details.
Out Data Flows – Registration Complete, Reject Registration
Process Description – ID IC = 900810-02-1234
Registration Complete
Else
Registration User Reject

Name – Managing Subject

Number – 2.0
Description – Create, Store, Manage, And Edit Subject Details By Program Leader
In Data Flows – Details Of Subject
Out Data Flows – Complete Successfully Or Reject Operation.
Process Description – IF Field = IT
Complete Successfully
Else
Reject Operation
Name – Course Management
Number – 3.0
Description – Create And Edit Course Details
In Data Flows – Details Of Course And List Of Subject
Out Data Flows – Manage Complete, Reject Manage
Process Description – IF Valid Data
Manage Complete
Else
Reject Manage

Name – Insert Information Into Intake

Number – 4.0
Description – Collect Information From Required Data Store To Edit Intake.
In Data Flows – Details Of Intake And Student List.
Out Data Flows – Successfully Update, Edition Rejected
Process Description – IF Valid Intake Data
Successfully Edit
Else
Edition Rejected

Name – Manage Intake

Number – 5.0
Description – The Creation And Edition Of Intake Details By Admin
In Data Flows – Details Of Intake
Out Data Flows – Successfully Managed, Managing Intake Has Rejected
Process Description – IF Students List = True
Successfully Managed
Else
 Managing Intake Had Rejected

Name – Consultation Hours Scheduling

Number – 6.0
Description – Booking of consultation hours by students to lecturers
In Data Flows – Capacity, Lecturer Information, Classroom Location, Intake Code.
Out Data Flows – Schedule Consultation Hours, Rejected
Process Description – IF Time Booked
Schedule Consultation Hours
Else
Rejected

Name – Time Table Scheduling

Number – 7.0
Description – Gather Various Information And Schedule The Time Table
In Data Flows – Capacity, Lecturer Information, Classroom Location, Intake Code.
Out Data Flows – Schedule Time Table, Rejected
Process Description – IF Time Not Booked
Schedule Time Table
Else
Rejected

External Entity
Name – Student
Description – Students Are The External Entity Who Can View The Time Table and
Consultation Hours To Attend Them.
In Data Flows – Time Table Scheduling/ Consultation Hours Scheduling
Out Data Flows – Student Information

Name – Lecturer
Description – Students Are The External Entity Who Can View The Time Table and
Consultation Hours To Meet With Their Lecturers.
In Data Flows – Time Table Scheduling / Consultation Hours Scheduling
Out Data Flows – Lecturer Information

Name – Administrator
Description – Administrator Who Manage The Intake, Classroom, Lecturer, Student,
Timetable and FYP.
In Data Flows – Information Of Students.
Out Data Flows – Intake Information, Classroom Information, Course Information,
Lecturer Information.
Data Store
Name – Members
Alias – Registered Members file
Description – Details of registered students and lecturers.
In Data Flows – Member Details
Out Data Flows – Lecturers And Students Details.
Contents – ID + Names + Address + Telephone No
Volume And Frequency- Big, frequent

Name – Subject
Alias – Subject File
Description – Details of subjects offered and available.
In Data Flows – Details of Subjects
Out Data Flows – Information Of Subject.
Contents – ID + Names + Field + Level
Volume And Frequency- Small, not frequent

Name – Course
Alias – Course File
Description – Details of course offered and available.
In Data Flows – Details of Course.
Out Data Flows – Information of Course
Contents – ID + Names + Subject ID + Duration
Volume And Frequency- Medium, not frequent.
Comments - Subjects ID Are Store In This File As A Foreign Data
Name – Intake
Alias – Intake File
Description – Intakes Of Details Are Stored. .
In Data Flows – Details Of Intakes With Updating.
Out Data Flows – Subject Information.
Contents – Intake No + Names + Description + Date Of Intake + Students List + ID
Of Course.
Volume And Frequency- Big, frequent
Comments – Foreign data are noted as Course and students list.

Name – Time Table

Alias – Time Table File
Description – Information Of Time Table Are Stored.
In Data Flows – Details Of Time Table
Out Data Flows – None
Contents – ID + Date And Start Time + End Time And Date + Venue + Intake
Number
Volume And Frequency- Large, frequent
Comments – Foreign data are noted as numbers of intakes.

Name – Consultation Hours Schedule

Alias – Consultation Hours File
Description – Information Of Consultation Hours Are Stored.
In Data Flows – Details Of Consultation Hours
Out Data Flows – None
Contents – ID + Date And Start Time + End Time And Date + Venue + Intake
Number
Volume And Frequency- Large, frequent
Comments – Foreign data are noted as numbers of intakes.