Sie sind auf Seite 1von 45

Context Diagram

Current System

Registr
ar

Information

Information

Assistan
t

Report

Instruct
or

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

Context Diagram

Propose System

O
LAN-BASED CLASS SCHEDULING OF BUKIDNON STATE BUKIDNON
Information

Admin

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

Day

HASS

Instructo
r

HASS

Time

HASS

HASS

Subjects

HASS

Year
Level

HASS

Room

Figure No. 3.Entity Relationship Diagram

Section

Student_Id

HAS

Instructor

Year Level

Middle Initial

Instructor_Id

Level name

Address

First Name
Last Name

Contact

Figure No. 4. Instructor Year_Level

Instructor_Id

Instructor

Level No.

HAS

Time

Time Span

Figure No. 5. Instructor Time

Day Initial

Instructor

HAS

Day

Instructor_Id

Day Name

Figure No. 6. Instructor - Day

Description

Instructor

HAS

Room

Instructor_Id

Figure No. 7. Instructor - Room

Room no.

Level No.
Instructor_Id

Year Level

Section name

Section no.

Level name
HAS

Section

Instructor_Id

Level No.

Figure No. 8. Year_Level - Section

Semester

Year Level

HAS

Instructor Id

Subject

Subject Name
Subject Code
Figure No. 9. Year_Level - Subject

Data Dictionary

Year Level

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

FieldName
User_Id

Data Type
Text

Size
10

Value
Not Null

Password

Number

12

Not Null

Description
(PK)User id of
user
Password of user

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

FieldName
Id

Data Type
Number

Size
12

Value
Not null

First Name

Text

25

Not null

Last Name

Text

25

Not null

Gender

Text

Not null

Address

Text

50

Not null

Description
(PK)Id of the
student
First name of
astudent
Last name of a
student
Gender of a
student
Address of a
student

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

FieldName
Id

Data Type
Number

Size
12

Value
Not null

Time Span

Number

Not null

Description
(FK)Id of
instructor
Time span of the

class

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

FieldName
Room_Num.

Data Type
Number

Size
10

Value
Not Null

ID

Number

10

Not Null

Description

Text

50

Not Null

Description
(PK)No. of the
room
(FK)Id no. of the
instructor
Description of
the room

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

FieldName
Subject_Code

Data Type
Number

Size
10

Value
Not Null

ID

Number

10

Not Null

50

Not Null

Subject_Name Text

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

Description
(PK) Code of
the subject
(FK)ID of the
instructor
Name of a
subject

FieldNam
e
Section_Na
me
Year_Name

Data Type

Size

Value

Description

Text

20

Not Null

Text

20

Not Null

Name of a
section
(FK) Name of the
Year Level

Year Level Table


FieldNa
me
Year_Na
me
ID

Data Type

Size

Value

Description

Text

10

Not Null

Number

10

Not Null

Numeral
s

Number

10

Not Null

(PK)Name of the
Year Level
(FK) Id no. of the
instructor
Numeral of the
Year Level

(This table stores information of the Year Level.)

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

FieldNa
me
Id
Day_Na
me

Data Type

Size

Value

Description

Number
Text

10
10

Not Null
Not Null

(FK)Id of the Day


Name of the Day

Day_Initi
al

Text

Not Null

Initial of the Day

Administrator Use Case

Log In
Enter Instructors Info

Add New Instructor


Update Instructor Info
rmation
Enter Class Schedule

Update Class Schedule

Print Class Schedule

Administrator

Log Out

Figure No. 10. Administrator Use Case

Use Case Description

USE CASE NAME

Administrators Login

ACTOR

Administrator

DESCRIPTION

Admins 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.
If the inputted user name and
password are invalid, the admin has
to enter a valid username and
password.
The Admin has a registered account

ALTERNATIVE FLOW

PRE CONDITION
POST CONDITION

The Admin is authorized to manage


the system.

ASSUMPTION

The 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 NAME

Enter Instructor Information

ACTOR

Administrator

DESCRIPTION

Admins use case that is use to


enter instructor information to the
system.
1. The Admin input the instructor
information.
2. The system will process and
save the inputted data.
3. Use case instance

NORMAL FLOW

ALTERNATIVE FLOW

PRE CONDITION
POST CONDITION
ASSUMPTION

Figure No. 12.

terminates.
If the inputted user name and
password are invalid, the admin has
to re-enter a valid username and
password.
The Admin has the valid data to
entry.
The Admin will be able to enter and
save datas.
The Admin has a valid data entry.

Use Case for Admin Enter Instructor Information

Table 3: Use Case for Admin View Instructor Information

USE CASE NAME

View Information

ACTOR

Administrator

DESCRIPTION

Admins use case that is use to view


information of the system.
1. The admin search the
instructor to view data
information.
2. The system shows all data
being search.
3. Use case instance terminates.
If the admin will search a wrong data,
the admin should verify and re-enter
the data being search.

NORMAL FLOW

ALTERNATIVE FLOW

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.
The admin should have correct data
being search.

ASSUMPTION

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

Admins use case that is use to add


new instructor information.
1. The admin will add new
instructor information.
2. The system will save the data.
3. Use case instance terminates.
If the data is invalid the admin will reenter the data that is valid.
The admin should have a valid data
for the new instructor.

NORMAL FLOW

ALTERNATIVE FLOW
PRE CONDITION
POST CONDITION
ASSUMPTION

The admin will be able to input new


instructor.
The admin has a valid data being

input

Use Case for Admin Add New Instructor Information

Figure No. 14.

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.
1. The admin search and input
new datas and update
instructor informations.
2. The system will show the data
to be update
3. Use case instance terminates.
If the admin will input wrong or invalid
data, the admin has to re-enter a
valid data to be update.
The admin should have valid datas
to update.

NORMAL FLOW

ALTERNATIVE FLOW
PRE CONDITION
POST CONDITION
ASSUMPTION

The admin will be able to update the


instructor information.
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

Admins use case that is use to


enter class schedule information to
the system.
1. The Admin input the class
schedule.
2. The system will process and
save the inputted data.
3. Use case instance
terminates.
If the inputted user name and
password are invalid, the admin has
to re-enter a valid username and
password.
The Admin has the valid data to
entry.

NORMAL FLOW

ALTERNATIVE FLOW

PRE CONDITION
POST CONDITION
ASSUMPTION

Figure No. 16.

The Admin will be able to enter and


save datas.
The Admin has a valid data entry.

Use Case for Admin Enter Class Schedule

Table 7: Use Case for Admin Add New Schedule

USE CASE NAME

Add New Schedule

ACTOR

Administrator

DESCRIPTION

Admins use case that is use to add


new schedule.
1. The admin will add new
schedule.
2. The system will save the data.
3. Use case instance terminates.
If the data is invalid the admin will reenter the data that is valid.
The admin should have a valid data
for the new schedule.

NORMAL FLOW

ALTERNATIVE FLOW
PRE CONDITION
POST CONDITION
ASSUMPTION

The admin will be able to input a new


schedule.
The 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 Schedule


USE CASE NAME

Update Class Schedule

ACTOR

Administrator

DESCRIPTION

Admins use case that is use to


update class schedule information.
1. The admin search and input
new datas and update class
schedule informations.
2. The system will show the data
to be update
3. Use case instance terminates.
If the admin will input wrong or invalid
data, the admin has to re-enter a
valid data to be update.
The admin should have valid datas
to update.

NORMAL FLOW

ALTERNATIVE FLOW
PRE CONDITION
POST CONDITION
ASSUMPTION

Figure No. 18.

The admin will be able to update the


class schedule information.
The admin should have correct data
entry to update.

Use Case for Admin Update Class Schedule

Table 9: Use Case for Student Print Class Schedule

USE CASE NAME

Print Class Schedule

ACTOR

Student

DESCRIPTION

Students use case that is use to


printclass schedule information from
the system.
1. The students print the info
data information.
2. The system shows all data
being search.
3. Use case instance terminates.
If the student will print a wrong data,
the student should verify the data
being print.
The student should have a correct
and valid data to be print.

NORMAL FLOW

ALTERNATIVE FLOW
PRE CONDITION
POST CONDITION
ASSUMPTION

Figure No. 19.

The student will be able to print class


schedule information to be checked.
The student should have correct data
being print.

Use Case for Admin Print Class Schedule

Table 10: Use Case for Admin Log-Out


USE CASE NAME

Admin Log-Out

ACTOR

Administrator

DESCRIPTION

Admins use case that is use to


logout.
1. The admin will log out his
account.
2. The system will process to
exit.
3. Use case instance terminates.
If the admin forget to log out the
admin should open the application
again to assure that she has already
log out.
The admin should save all data
before logging out.

NORMAL FLOW

ALTERNATIVE FLOW

PRE CONDITION
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

Sequence Diagram

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

User Interface

System Database

Admin

1. Display Login

3. Input Instructor Information


2. Instructor Information
4. Save Information

Figure No. 22.

Sequence Diagram for Add New Instructor

User Interface
1. Display Instructor Information

System Database

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

User Interface
Figure No. 24.

System Database

Sequence Diagram for New Instructor

Administrator

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 Interface

Admin

System Database

2. Display Login

3. Input Class Sched Information


2. Class Sched Information
4. Save Information

Figure No. 26.

Sequence Diagram for Enter Class Schedule

User Interface

System Database

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

User Interface

Figure No. 28.

System Database

Sequence Diagram for New Class Schedule

Administrator

2. Display Schedule Page

2. Update Information 3. Search Schedule

4. Display Sched Data

5. Enter Information

6. Save Information

Figure No. 29.

Administrator

User Interface
System
Database
Sequence Diagram
for Update Class
Schedule

Save

Log Out

Exit Page

Figure No. 30.

Sequence Diagram for Administrator Log Out

Activity Diagram

Enter User Name

Enter Password

Invalid User
Name

Invalid
Password

Figure No. 31 .

Activity Diagram of Admin Log In

Enter UserName & Password

Valid

Valid
Display
Admin
Page
Instructor
Save
Input Information
Information

Figure No. 32 .

Activity Diagram for Admin Enter Instructor Information

Display Instructor Information

Information
Valid
Display
SearchSearch
Instructor
Data

Figure No. 33 .

Activity Diagram for Admin View Information

Display Admin Page

New Instructor Information


Valid
InputSave
Instructor
Information
Information

Figure No. 34 .

Activity Diagram for Admin Add New Instructor

Display Instructor Information

Instructor Information
Display
Search
Search
Instructor
Information

Update Instructor Information

Save Instructor Information

Figure No. 35 . Activity

Diagram for Admin Update Instructor


Information

Enter UserName & Password

Valid
Valid
Schedule
Display
Save
Input Information
Admin
Information
Page

Figure No. 36 . Activity

Diagram for Admin Enter Schedule Information

Display Schedule Information


Valid
Display
Search
Information
Search
Schedule
Data

Figure No. 37 . Activity

Diagram for Admin View Information

ScheduleValid
Information
Input
New Save
Schedule
Schedule
Information
Information
Information

Figure No. 38 .

Activity Diagram for Admin Add New Schedule

Display Schedule Information


Update
Save
Display
Schedule
Search
Schedule
Schedule
Search
Schedule
Information
Information
Information

Figure No. 39 .

Activity Diagram for Admin Update Schedule


Information

Display Schedule Information


Save
Print

Figure No. 40 .

Activity Diagram for Admin PrintSchedule

Schedule Information Page

Save Data

Log out

Exit Page

Figure No. 41 . Activity

Diagram for Admin Log Out

Data Flow Diagram

Add Information

Admin

1.0
Reports

Class Schedule

Figure No. 42 .

Save
Information

Instructor

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.

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.