Context Diagram

Current System

AssistantRegistrar Information Report

InstructorInformation

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 DescriptionContext Diagram

Propose System

OLAN-BASED CLASS SCHEDULING OF BUKIDNON STATE BUKIDNONAdmin InformationReport

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

HASSYear LevelSectionTimeSubjectsRoomDayInstructor

HASS

HASS

HASSHASSHASS

Figure No. 3.Entity Relationship Diagram

Student_Id

HASLevel No. Year Level Instructor

Instructor_IdLevel nameMiddle Initial

AddressFirst Name

Contact

Last NameFigure No. 4. Instructor Year_Level

Instructor_Id

HAS Time Instructor

Time Span

Figure No. 5. Instructor Time

Day Initial InstructorHAS Day

Instructor_IdDay Name

Figure No. 6. Instructor - Day

Description InstructorHAS Room

Instructor_IdRoom no.

Figure No. 7. Instructor - Room

Level No.

Section no.Section name

Instructor_Id_IdLevel name

SectionHAS Year Level

Instructor_IdLevel No.

Figure No. 8. Year_Level - Section

SemesterInstructor Id

HAS Year Level Subject

Year LevelSubject Name

Subject Code

Figure No. 9. Year_Level - Subject

Data Dictionary

User Table(This table stores information of the user.)FieldNameData TypeSizeValueDescription

User_IdText10Not Null(PK)User id of user

PasswordNumber12Not NullPassword of user

Instructor Table(This table stores information of the instructor.)FieldNameData TypeSizeValueDescription

IdNumber12Not null(PK)Id of the student

First NameText25Not nullFirst name of astudent

Last NameText25Not nullLast name of a student

GenderText6Not nullGender of a student

AddressText50Not nullAddress of a student

Time Table(This table stores information of the time.)FieldNameData TypeSizeValueDescription

IdNumber12Not null(FK)Id of instructor

Time SpanNumber4Not nullTime span of the class

Room Table(This table stores information of the room.)FieldNameData TypeSizeValueDescription

Room_Num.Number10Not Null(PK)No. of the room

IDNumber10Not Null(FK)Id no. of the instructor

DescriptionText50Not NullDescription of the room

Subject Table(This table stores information of the Subject.)FieldNameData TypeSizeValueDescription

Subject_CodeNumber10Not Null(PK) Code of the subject

IDNumber10Not Null(FK)ID of the instructor

Subject_NameText50Not NullName of a subject

Section Table(This table stores information of the Section.)FieldNameData TypeSizeValueDescription

Section_NameText

20Not NullName of a section

Year_NameText20Not Null(FK) Name of the Year Level

Year Level TableFieldNameData TypeSizeValueDescription

Year_NameText10Not Null(PK)Name of the Year Level

IDNumber10Not Null(FK) Id no. of the instructor

NumeralsNumber10Not NullNumeral of the Year Level

(This table stores information of the Year Level.)

Day Table(This table stores information of the Day.)FieldNameData TypeSizeValueDescription

IdNumber10Not Null(FK)Id of the Day

Day_NameText10Not NullName of the Day

Day_InitialText5Not NullInitial of the Day

Administrator Use Case

Log In

Enter Instructors Info

Add New Instructor

Update Instructor Information

Enter Class Schedule

Update Class Schedule

Print Class Schedule

Log OutAdministrator

Figure No. 10. Administrator Use Case

Use Case DescriptionUSE CASE NAMEAdministrators Login

ACTORAdministrator

DESCRIPTIONAdmins use case is used to Login to the system.

NORMAL FLOW1. The Admin inputs were user name and password.2. The system verifies the user name and password.3. Use case instance terminates.

ALTERNATIVE FLOWIf the inputted user name and password are invalid, the admin has to enter a valid username and password.

PRE CONDITIONThe Admin has a registered account

POST CONDITIONThe Admin is authorized to manage the system.

ASSUMPTIONThe admin has a registered account.

Table 1: Use Case for Admin Log In

Figure No. 11. Use Case for Admin Log In

Table 2: Use Case for Admin Enter Instructor Information

USE CASE NAMEEnter Instructor Information

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to enter instructor information to the system.

NORMAL FLOW1. The Admin input the instructor information.2. The system will process and save the inputted data.3. Use case instance terminates.

ALTERNATIVE FLOWIf the inputted user name and password are invalid, the admin has to re-enter a valid username and password.

PRE CONDITIONThe Admin has the valid data to entry.

POST CONDITIONThe Admin will be able to enter and save datas.

ASSUMPTIONThe 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 NAMEView Information

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to view information of the system.

NORMAL FLOW1. The admin search the instructor to view data information.2. The system shows all data being search.3. Use case instance terminates.

ALTERNATIVE FLOWIf the admin will search a wrong data, the admin should verify and re-enter the data being search.

PRE CONDITIONThe admin should have a correct and valid data to be search.

POST CONDITIONThe admin will be able to view instructor information to be checked.

ASSUMPTIONThe 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 NAMEAdd New Instructor

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to add new instructor information.

NORMAL FLOW1. The admin will add new instructor information.2. The system will save the data.3. Use case instance terminates.

ALTERNATIVE FLOWIf the data is invalid the admin will re-enter the data that is valid.

PRE CONDITIONThe admin should have a valid data for the new instructor.

POST CONDITIONThe admin will be able to input new instructor.

ASSUMPTIONThe admin has a valid data being input

Figure No. 14. Use Case for Admin Add New Instructor Information

Table 5: Use Case for Admin Update Instructor Information

USE CASE NAMEUpdate Instructor Information

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to update instructor information.

NORMAL FLOW1. The admin search and input new datas and update instructor informations.2. The system will show the data to be update3. Use case instance terminates.

ALTERNATIVE FLOWIf the admin will input wrong or invalid data, the admin has to re-enter a valid data to be update.

PRE CONDITIONThe admin should have valid datas to update.

POST CONDITIONThe admin will be able to update the instructor information.

ASSUMPTIONThe 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 ScheduleUSE CASE NAMEEnter Class Schedule

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to enter class schedule information to the system.

NORMAL FLOW1. The Admin input the class schedule.2. The system will process and save the inputted data.3. Use case instance terminates.

ALTERNATIVE FLOWIf the inputted user name and password are invalid, the admin has to re-enter a valid username and password.

PRE CONDITIONThe Admin has the valid data to entry.

POST CONDITIONThe Admin will be able to enter and save datas.

ASSUMPTIONThe Admin has a valid data entry.

Figure No. 16. Use Case for Admin Enter Class Schedule

Table 7: Use Case for Admin Add New Schedule

USE CASE NAMEAdd New Schedule

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to add new schedule.

NORMAL FLOW1. The admin will add new schedule.2. The system will save the data.3. Use case instance terminates.

ALTERNATIVE FLOWIf the data is invalid the admin will re-enter the data that is valid.

PRE CONDITIONThe admin should have a valid data for the new schedule.

POST CONDITIONThe admin will be able to input a new schedule.

ASSUMPTIONThe admin has a valid data being input

Figure No. 17. Use Case for Admin Add New Schedule

Table 8: Use Case for Admin Update Class ScheduleUSE CASE NAMEUpdate Class Schedule

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to update class schedule information.

NORMAL FLOW1. The admin search and input new datas and update class schedule informations.2. The system will show the data to be update3. Use case instance terminates.

ALTERNATIVE FLOWIf the admin will input wrong or invalid data, the admin has to re-enter a valid data to be update.

PRE CONDITIONThe admin should have valid datas to update.

POST CONDITIONThe admin will be able to update the class schedule information.

ASSUMPTIONThe admin should have correct data entry to update.

Figure No. 18. Use Case for Admin Update Class Schedule

Table 9: Use Case for Student Print Class Schedule

USE CASE NAMEPrint Class Schedule

ACTORStudent

DESCRIPTIONStudents use case that is use to printclass schedule information from the system.

NORMAL FLOW1. The students print the info data information.2. The system shows all data being search.3. Use case instance terminates.

ALTERNATIVE FLOWIf the student will print a wrong data, the student should verify the data being print.

PRE CONDITIONThe student should have a correct and valid data to be print.

POST CONDITIONThe student will be able to print class schedule information to be checked.

ASSUMPTIONThe student should have correct data being print.

Figure No. 19. Use Case for Admin Print Class Schedule

Table 10: Use Case for Admin Log-OutUSE CASE NAMEAdmin Log-Out

ACTORAdministrator

DESCRIPTIONAdmins use case that is use to logout.

NORMAL FLOW1. The admin will log out his account.2. The system will process to exit.3. Use case instance terminates.

ALTERNATIVE FLOWIf the admin forget to log out the admin should open the application again to assure that she has already log out.

PRE CONDITIONThe admin should save all data before logging out.

POST CONDITIONThe admin will be log out.

ASSUMPTIONThe admin has saved all the data.

Figure No. 20. Use Case for Admin Log-Out

Sequence Diagram

System DatabaseUser Interface

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

User InterfaceSystem DatabaseAdmin

1. Display Login

3. Input Instructor Information 2. Instructor Information 4. Save Information

Figure No. 22. Sequence Diagram for Add New Instructor

System DatabaseUser Interface 1. Display Instructor Information

Admin 3. Search Instructor 2. Information 4. Display Search Data

Figure No. 23. Sequence Diagram for View Data

1. Display Admin Page

Admin

2. New Instructor Info 3. Input Instructor Info

4. Save Information

Figure No. 24. Sequence Diagram for New Instructor

AdministratorSystem DatabaseUser Interface

1. Display Instructor Page

2. Update Information 3. Search Instructor 4. Display Instructor Data

5. Enter Information

6. Save Information

Figure No. 25. Sequence Diagram for Update Instructor Information

User InterfaceSystem DatabaseAdmin

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 DatabaseUser Interface 1. Display Class Schedule Information

Admin 3. Search Class Sched 2. Information 4. Display Search Data

Figure No. 27. Sequence Diagram for View Class Schedule

2. Display Schedule Page

Admin

2. New Class Sched Info 3. Input Class Sched Info

4. Save Information

Figure No. 28. Sequence Diagram for New Class Schedule

AdministratorSystem DatabaseUser Interface

2. Display Schedule Page

2. Update Information3. Search Schedule 4. Display Sched Data

5. Enter Information

6. Save Information

Figure No. 29. Sequence Diagram for Update Class Schedule

User InterfaceSystem DatabaseAdministrator

Save

Log Out

Exit Page

Figure No. 30. Sequence Diagram for Administrator Log Out

Activity Diagram

Enter PasswordEnter User Name

Invalid User Invalid Name Password

Figure No. 31. Activity Diagram of Admin Log In

Save InformationValidInput InformationInstructor InformationDisplay Admin PageValidEnter UserName & Password

N

N

Y

Figure No. 32. Activity Diagram for Admin Enter Instructor Information

ValidDisplay Search DataSearch InstructorInformationDisplay Instructor Information

N

Y

Figure No. 33. Activity Diagram for Admin View Information

ValidSave InformationInput Instructor InformationNew Instructor InformationDisplay Admin Page

N

Y

Figure No. 34. Activity Diagram for Admin Add New Instructor

Display Search InformationSearch InstructorInstructor InformationDisplay Instructor Information

Update Instructor Information

Save Instructor Information

Figure No. 35. Activity Diagram for Admin Update Instructor Information

Save InformationValidInput InformationSchedule InformationDisplay Admin PageValidEnter UserName & Password

N

N

Y

Figure No. 36. Activity Diagram for Admin Enter Schedule Information

ValidDisplay Search DataSearch ScheduleInformationDisplay Schedule Information

N

Y

Figure No. 37. Activity Diagram for Admin View Information

ValidSave InformationInput Schedule InformationNew Schedule InformationSchedule Information

N

Y

Figure No. 38. Activity Diagram for Admin Add New Schedule

Save Schedule InformationUpdate Schedule InformationDisplay Search InformationSearch ScheduleSchedule InformationDisplay Schedule Information

Figure No. 39. Activity Diagram for Admin Update Schedule Information

Display Schedule InformationPrintSave

Figure No. 40. Activity Diagram for Admin PrintSchedule

Exit PageLog outSave DataSchedule Information Page

Figure No. 41. Activity Diagram for Admin Log Out

Data Flow Diagram

Admin Add Information

1.0Save Information

Reports

Instructor Class Schedule

Figure No. 42. Data Flow Diagram of Class Scheduling System

RESULTS AND DISCUSSION4.1Implementation of the Program Prototype

4.1.1 Database Functional Description Important functions apply to all tables in the database. 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 invalid values that are not needed in the database. It will prompt also when 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 Process Narrative 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.