Context Diagram
Current System
Information
Report
Information
Narrative Description of Current System
The instructor will give information to the registrar such as full name,
address and contact.The registrars give information to the office assistant for a
class schedule of an instructor. The office assistant will givea class schedule to
instructor.
Figure No. 1.The Current System Flow_Narrative Description
Assistan
t
Registr
ar
Instruct
or
O
LAN-BASED CLASS SCHEDULING OF BUKIDNON STATE BUKIDNON
Context Diagram
Propose System
I
nformation
Report
Narrative Description of Propose System
The admin will stand as the registrar which input all the information of an
instructor to the system. The registrar is also a responsible to search and print the
class schedule of an instructor.
Figure No. 2.The Propose System Flow_Narrative Description
Class Scheduling Entity Relationship Diagram
Figure No. 3.Entity Relationship Diagram
HASS
Year
Level
Section
Time
Subjects
Room
Day
Instructo
r
HASS HASS HASS HASS HASSFigure No. 4. Instructor – Year_Level
Figure No. 5. Instructor –Time
Student_Id
HAS
Level No. Year Level
Instructor
Instructor_Id Middle Initial Level name
Address First Name Contact Last Name Instructor_Id HAS Time Instructor Time Span
Figure No. 6. Instructor - Day
Figure No. 7. Instructor - Room
Day Initial
Instructor HAS Day
Instructor_Id Day Name
Description
Instructor HAS Room
Figure No. 8. Year_Level - Section
Figure No. 9. Year_Level - Subject
Data Dictionary
Level No.
Section no. Section name Instructor_Id Level name
Section HAS Year Level Instructor_Id Level No. Semester Instructor Id HAS
Year Level Subject
Year Level Subject Name
User Table
(This table stores information of the user.)
FieldName
Data Type
Size
Value
Description
User_Id
Text
10
Not Null
(PK)User id of
user
Password
Number
12
Not Null
Password of user
Instructor Table
(This table stores information of the instructor.)
FieldName
Data Type
Size
Value
Description
Id
Number
12
Not null
(PK)Id of the
student
First Name
Text
25
Not null
First name of
astudent
Last Name
Text
25
Not null
Last name of a
student
Gender
Text
6
Not null
Gender of a
student
Address
Text
50
Not null
Address of a
student
Time Table
(This table stores information of the time.)
FieldName
Data Type
Size
Value
Description
Id
Number
12
Not null
(FK)Id of
instructor
class
Room Table
(This table stores information of the room.)
FieldName
Data Type Size
Value
Description
Room_Num.
Number
10
Not Null
(PK)No. of the
room
ID
Number
10
Not Null
(FK)Id no. of the
instructor
Description
Text
50
Not Null
Description of
the room
Subject Table
(This table stores information of the Subject.)
FieldName
Data Type
Size
Value
Description
Subject_Code
Number
10
Not Null
(PK) Code of
the subject
ID
Number
10
Not Null
(FK)ID of the
instructor
Subject_Name Text
50
Not Null
Name of a
subject
Section Table
FieldNam
e
Data Type
Size
Value
Description
Section_Na
me
Text
20
Not Null
Name of a
section
Year_Name Text
20
Not Null
(FK) Name of the
Year Level
Year Level Table
FieldNa
me
Data Type Size
Value
Description
Year_Na
me
Text
10
Not Null
(PK)Name of the
Year Level
ID
Number
10
Not Null
(FK) Id no. of the
instructor
Numeral
s
Number
10
Not Null
Numeral of the
Year Level
(This table stores information of the Year Level.)
Day Table
(This table stores information of the Day.)
FieldNa
me
Data Type Size
Value
Description
Id
Number
10
Not Null
(FK)Id of the Day
Day_Na
me
Day_Initi
al
Text
5
Not Null
Initial of the Day
Administrator Use Case
Log In
Enter Instructor’s Info
Add New Instructor Update Instructor Info
rmation Enter Class Schedule
Update Class Schedule
Administrator
Figure No. 10. Administrator Use Case
Use Case Description
Table 1:
Use
Case
for
Admin
Log In
Log OutUSE CASE NAME Administrators Login ACTOR Administrator
DESCRIPTION Admin’s use case is used to Login to the system.
NORMAL FLOW 1. The Admin inputs were user name and password.
2. The system verifies the user name and password.
3. Use case instance terminates.
ALTERNATIVE FLOW If the inputted user name and password are invalid, the admin has to enter a valid username and password.
PRE CONDITION The Admin has a registered account POST – CONDITION The Admin is authorized to manage
the system.
ASSUMPTION The admin has a registered account.
Figure No. 11.
Use Case for Admin Log In
Table 2: Use Case for Admin Enter Instructor Information
USE CASE NAME Enter Instructor Information ACTOR Administrator
DESCRIPTION Admin’s use case that is use to enter instructor information to the system.
NORMAL FLOW 1. The Admin input the instructor information.
2. The system will process and save the inputted data. 3. Use case instance
terminates.
ALTERNATIVE FLOW If the inputted user name and
password are invalid, the admin has to re-enter a valid username and password.
PRE CONDITION The Admin has the valid data to entry.
POST – CONDITION The Admin will be able to enter and save data’s.
ASSUMPTION The Admin has a valid data entry.
Figure No. 12.
Use Case for Admin Enter Instructor Information
Table 3: Use Case for Admin View Instructor Information
USE CASE NAME View Information ACTOR Administrator
DESCRIPTION Admin’s use case that is use to view information of the system.
NORMAL FLOW 1. The admin search the instructor to view data information.
2. The system shows all data being search.
3. Use case instance terminates. ALTERNATIVE FLOW If the admin will search a wrong data, the admin should verify and re-enter the data being search.
PRE CONDITION The admin should have a correct and valid data to be search.
POST – CONDITION The admin will be able to view instructor information to be checked. ASSUMPTION The admin should have correct data
being search.
Figure No. 13.
Use Case for Admin View Instructor Information
Table 4: Use Case for Admin Add New Instructor
USE CASE NAME Add New Instructor ACTOR Administrator
DESCRIPTION Admin’s use case that is use to add new instructor information.
NORMAL FLOW 1. The admin will add new instructor information.
2. The system will save the data. 3. Use case instance terminates. ALTERNATIVE FLOW If the data is invalid the admin will
re-enter the data that is valid.
PRE CONDITION The admin should have a valid data for the new instructor.
POST – CONDITION The admin will be able to input new instructor.
input
Figure No. 14.
Use Case for Admin Add New Instructor Information
Table 5: Use Case for Admin Update Instructor Information
USE CASE NAME Update Instructor Information ACTOR Administrator
DESCRIPTION Admins use case that is use to update instructor information. NORMAL FLOW 1. The admin search and input
new data’s and update instructor information’s.
2. The system will show the data to be update
3. Use case instance terminates. ALTERNATIVE FLOW If the admin will input wrong or invalid
data, the admin has to re-enter a valid data to be update.
PRE CONDITION The admin should have valid data’s to update.
POST – CONDITION The admin will be able to update the instructor information.
ASSUMPTION The admin should have correct data entry to update.
Figure No. 15.
Use Case for Admin Update Instructor Information
Table 6: Use Case for Admin Enter Class Schedule
USE CASE NAME Enter Class Schedule ACTOR Administrator
DESCRIPTION Admin’s use case that is use to enter class schedule information to the system.
NORMAL FLOW 1. The Admin input the class schedule.
2. The system will process and save the inputted data. 3. Use case instance
terminates.
ALTERNATIVE FLOW If the inputted user name and
password are invalid, the admin has to re-enter a valid username and password.
PRE CONDITION The Admin has the valid data to entry.
POST – CONDITION The Admin will be able to enter and save data’s.
ASSUMPTION The Admin has a valid data entry.
Table 7: Use Case for Admin Add New Schedule
USE CASE NAME Add New Schedule ACTOR Administrator
DESCRIPTION Admin’s use case that is use to add new schedule.
NORMAL FLOW 1. The admin will add new schedule.
2. The system will save the data. 3. Use case instance terminates. ALTERNATIVE FLOW If the data is invalid the admin will
re-enter the data that is valid.
PRE CONDITION The admin should have a valid data for the new schedule.
POST – CONDITION The admin will be able to input a new schedule.
ASSUMPTION The admin has a valid data being input
Table 8: Use Case for Admin Update Class Schedule
USE CASE NAME Update Class Schedule ACTOR Administrator
DESCRIPTION Admin’s use case that is use to update class schedule information. NORMAL FLOW 1. The admin search and input
new data’s and update class schedule information’s.
2. The system will show the data to be update
3. Use case instance terminates. ALTERNATIVE FLOW If the admin will input wrong or invalid
data, the admin has to re-enter a valid data to be update.
PRE CONDITION The admin should have valid data’s to update.
POST – CONDITION The admin will be able to update the class schedule information.
ASSUMPTION The admin should have correct data entry to update.
Table 9: Use Case for Student Print Class Schedule
USE CASE NAME Print Class Schedule
ACTOR Student
DESCRIPTION Student’s use case that is use to printclass schedule information from the system.
NORMAL FLOW 1. The students print the info data information.
2. The system shows all data being search.
3. Use case instance terminates. ALTERNATIVE FLOW If the student will print a wrong data,
the student should verify the data being print.
PRE CONDITION The student should have a correct and valid data to be print.
POST – CONDITION The student will be able to print class schedule information to be checked. ASSUMPTION The student should have correct data
being print.
Figure No. 19.
Use Case for Admin Print Class Schedule
Table 10: Use Case for Admin Log-Out
ACTOR Administrator
DESCRIPTION Admin’s use case that is use to logout.
NORMAL FLOW 1. The admin will log out his account.
2. The system will process to exit.
3. Use case instance terminates. ALTERNATIVE FLOW If the admin forget to log out the
admin should open the application again to assure that she has already log out.
PRE CONDITION The admin should save all data before logging out.
POST – CONDITION The admin will be log out.
ASSUMPTION The admin has saved all the data.
Figure No. 20.
Use Case for Admin Log-Out
User Interface System Database
Admin
1. Click on Log-in button 2. Type Username and password
3. Valid Username and password
Figure No. 21.
Sequence Diagram for Admin Log In
1. Display Login
System Database User Interface
3. Input Instructor Information 2. Instructor Information
4. Save Information
Figure No. 22.
Sequence Diagram for Add New Instructor
1. Display Instructor Information
System Database User Interface
3. Search Instructor 2. Information
4. Display Search Data
Figure No. 23.
Sequence Diagram for View Data
1. Display Admin Page Admin
Administrator
System Database User Interface
2. New Instructor Info 3. Input Instructor Info
4. Save Information
Figure No. 24.
Sequence Diagram for New Instructor
1. Display Instructor Page Admin
User Interface System Database
Admin
2. Update Information 3. Search Instructor
4. Display Instructor Data
5. Enter Information
6. Save Information
2. Display Login
3. Input Class Sched Information 2. Class Sched Information
4. Save Information
Figure No. 26.
Sequence Diagram for Enter Class Schedule
System Database User Interface
1. Display Class Schedule Information
3. Search Class Sched 2. Information
4. Display Search Data
Figure No. 27.
Sequence Diagram for View Class Schedule
Administrator
System Database User Interface
2. Display Schedule Page
2. New Class Sched Info 3. Input Class Sched Info
4. Save Information
Figure No. 28.
Sequence Diagram for New Class Schedule
2. Display Schedule Page Admin
User Interface System Database
Administrator
2. Update Information 3. Search Schedule
4. Display Sched Data
5. Enter Information
6. Save Information
Save
Log Out
Exit Page
Figure No. 30.
Sequence Diagram for Administrator Log Out
Activity Diagram
Enter Password Enter User Name
Invalid User Invalid
Name Password
Figure No. 31.
Activity Diagram of Admin Log In
N
Save Information Valid Input Information Instructor InformationDisplay Admin Page
Valid
N
Y
Figure No. 32.
Activity Diagram for Admin Enter Instructor Information
Valid
Display Search DataSearch Instructor Information
N
Y
Figure No. 33.
Activity Diagram for Admin View Information
Valid Save Information Input Instructor Information
New Instructor Information Display Admin Page
N
Y
Figure No. 34.
Activity Diagram for Admin Add New Instructor
Display Search InformationSearch Instructor Instructor Information Display Instructor Information
Figure No. 35.
Activity Diagram for Admin Update Instructor
Information
Update Instructor Information
Save Instructor Information
Save Information Valid Input Information Schedule InformationDisplay Admin Page
Valid
N
N
Y
Figure No. 36.
Activity Diagram for Admin Enter Schedule Information
Valid
Display Search DataSearch ScheduleInformation Display Schedule Information
N
Y
Figure No. 37.
Activity Diagram for Admin View Information
Valid Save Information Input Schedule InformationNew Schedule Information
N
Y
Figure No. 38.
Activity Diagram for Admin Add New Schedule
Save Schedule Information Update Schedule InformationDisplay Search InformationSchedule InformationSearch Schedule Display Schedule Information
Figure No. 39.
Activity Diagram for Admin Update Schedule
Information
Display Schedule Information Print
Figure No. 41.
Activity Diagram for Admin Log Out
Data Flow Diagram
Exit Page Log out Save Data
Add Information
Reports
Class Schedule
Figure No. 42.
Data Flow Diagram of Class Scheduling System
RESULTS AND DISCUSSION 4.1 Implementation of the Program Prototype
4.1.1 Database Functional Description
Important functions apply to all tables in the database.
Admin
1.0 Save Information
4.1.1.1 ADD
Process Narrative
The ADD function allows the user of the system to enter new record. ADD function can be use only by those who have registered in the system and have the right or privilege to add new record.
There are different fields assigned to the admin. Admin has a Username and a password to access the system. The admin which is assign for class scheduling can enter new record of the instructor and schedules.
Restriction/Limitation
The system will automatically reject those values being input that are irrelevant or do not match the required data type for each field. The inputted values must have the correct data type for each field.
Performance Requirements
A message will prompt the user whenever there are repeated and
some fields are empty and those field that are auto-generated data type will automatically increment e.g. ID No.
4.1.1.2 SAVE/UPDATE Process Narrative
The SAVE function allows the user to save the inputted record in
the database. The UPDATE function makes changes of what the authorized user want.
Restriction/Limitation
The SAVE and UPDATE functions can save and change some of
the records that are stored in the database. However, to prevent falsification of information there are fields that cannot be edited like the ID No. Changes can only be made for specific fields.
Performance Requirements
The system will prompt a message asking the user for a confirmation before some changes is stored. It will also prompt a message if editing or updating of information is done or not.
4.1.1.3 DELETE
The DELETE function allows the user to remove the selected record that the user wants to delete. The delete function permanently removes the chosen record.
Restriction/ Limitation
The system will delete the record that the user wants to delete. The DELETE function permanently removes the record from the database. However, only the admin and the payroll personnel have the right to delete the record.
Performance Requirements
The system prompts a message that aware the user that the record will be permanently deleted and cannot longer retrieve it. The decision will be choose by the user if he will continue to delete it or abort it.
