HOTEL RESERVATION SYSTEM

Systems Analysis and Design
Details

Overview of the Proposed System
Writing report cards for students is an overwhelming experience for novice and experienced teachers. Reports cards are usually done three times a year in elementary schools and 3-4 times for high school students. Teachers must evaluate and record student’s marks and then decide on honest comments in regards to the student’s weaknesses and strengths. Teachers are often given limited space for commences and their comments are evaluated by principals, and they decide to reject or accept the comments.
The purpose of this database system is to give convenience for the teachers in making report cards of their students; by this system teachers won’t need calculators anymore in computing the grades of the students because this system will compute the grades and average grade of the students. Plus faster, faster, easy and more suitable way of finding student’s file as well as you can assure security using this database system.

Event 1: Log-in to the grading report system This process describes the instructor when he/she log-in into the system to make new record of student.

Event 2: Input/update record This process describes when the instructor input/update record of a student. This is used when there are changes in the record of a student if ever there is a mistake.

Event 3: Input student information This is where the student input his/her information to view his/her record into the grading report system.

Event 4: View student record This is where the student can view his/her grades into the grading report system.

Event 5: Generate report This is the process where the instructor and the student can generate the report of the grade he views.

Event 6: log-out This is the event when the instructor log-out into the grading report system.

System Models

Use Case Diagram

Class Diagram

Use Case Specification

Use Case 1. Log in to grading report system
USE CASE NAME: Log in to grading report system.
ACTOR: Instructor
DESCRIPTION: This use case describes the process when the instructor log-in into the grading report system.
NORMAL COURSE: 1. The Instructor enters password. 2. Log in succesfully. 3.End of Use Case
ALTERNATIVE COURSES: 1. If the password is incorrect, retype the password.
PRECONDITION: Instructor must have password.
WORK FLOW : Log in to grading report system

POST CONDITION: Log in into the system successfully.
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

Use Case 2. Input/update record to grading report system
USE CASE NAME: Input/Update record
ACTOR: Instructor
DESCRIPTION: This use case describes the process when the instructor input/update record to grading report system.
NORMAL COURSE: 1. The Instructor add and edit record of student. 2. Input/update successfully. 3.End of Use Case
ALTERNATIVE COURSES: 1. If the instructor finishes adding or editing record of the student, the instructor fined student record.
PRECONDITION: The instructor has logged-in in the system.
WORK FLOW : Input/update to grading report system

POST CONDITION: The instructor has successfully inputted/updated student record.
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

Use Case 3. Input student Information to grading report system
USE CASE NAME: Input student Information
ACTOR: Student
DESCRIPTION: This use case describes the process when the student input student information.
NORMAL COURSE: 1. Input student information. 2. Student input information successfully. 3. View student report. 3.End of Use Case
PRECONDITION: The student information form has activated by the instructor.
WORK FLOW : Input student information to grading report system

POST CONDITION: The student has successfully inputted student information.
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

Use Case 4. View student grade to grading report system
USE CASE NAME: View student record
ACTOR: Student
DESCRIPTION: This use case describes the process when the student view grade.
NORMAL COURSE: 1. Input student information. 2. View student grade. 3. Student view grade successfully. 3.End of Use Case
PRECONDITION: The student must input student information.
WORK FLOW : View student grade to grading report system

POST CONDITION: The student view grade successfully
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

Use Case 5. Generate report to grading report system
USE CASE NAME: Generate report
ACTOR: Student, Instructor
DESCRIPTION: This use case describes the process when the student and instructor generate report.
NORMAL COURSE: 1. Input student information/ input instructor information 2. Generate report 3. Generate report successfully 3.End of Use Case
PRECONDITION: The student and instructor must input student information before generating report.
WORK FLOW : Generate report to grading report system

POST CONDITION: The student and instructor generate report successfully
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

Use Case 6.Log-out to grading report system
USE CASE NAME: Log-out to grading report system
ACTOR: Instructor
DESCRIPTION: This use case describes the process when the instructor log-out to the system.
NORMAL COURSE: Happy Path :
1. Instructor log-out the system.
PRECONDITION: 1. The instructor opens grading report system.
2. The instructor must log-in.
WORK FLOW : Log-out to grading report system

POST CONDITION: Log out into the system successfully
ASSUMPTIONS: Extension to use case notation.
SPECIAL REQUIREMENTS: Optional.

System Sequence Diagram

Figure 1: Instructor log-in into the system

Figure 2: Input/update record

Figure 3: Input student information

Figure 4: Student view grade

Figure 5: Student generate record

Figure 5.1: Instructor generate record

Figure 6: Instructor log-out into the system

User Interfaces