5.2.1.

7 Site Adaptation Requirement

There are no special requirements in the customer site to deploy the
system. Moreover, requirements for software interfaces will cover the site
adaptation requirements.

5.2.2 Product Function

1. Reservation and Booking System.

Includes the rules of the hostel.

Allows students to choose their room based on their gender.
Includes a description field of their room condition.
When a student confirm, the room number will be changed to
occupy in the database.
Ability to modify a booking.
//tak pasti
Allows addition, deletion and modification of information on
room.
Displays the status of the reservation.
Records the vacancy of the room.

2. Room Payment.

Allows online room payment included the penalty.

Includes the list of penalty.
Charges the current room as necessary.
Includes details of payment.
Receives notification.
Allows addition, deletion and modification of information on
penalty.
Records payment.

3. Report or Complaint.

Provides a space the allow student to complaint.

Tracks all the problems or complaints in the hostel.
Allows addition, deletion and modification of information on
rule.

4. Announcement

Allows addition, deletion and modification of information on

announcement.

5.2.3 User Characteristics

There are 4 kinds of users for the proposed system
o Administrator
Administrator is the one who monitors all users and user transactions .Admin has to
maintain the data of every student profile in database. When the request given by the
user admin checks the availability of the user account then it forwarded to the student
database. Admin haves the complete information related to every student database
and all the information related to the students. All the data is maintained at the Admin
level. Admin is having the rights to restrict any database.
o Hostel Management
Hostel manager is the person charge for the approving the reserved
room. They will update about the vacancy of the rooms and the
details of the housemate. If the reserved is approved, they will
announce the successful status. They are also responsible for
updating the hostel announcement such as the current activities
held at the hostel. Also, hostel manger have the right to charge and
inform the student if they break the hostels rules.
o Students
Every student who have register his/her name under this university will have an ID
which allowed him/her to bbok the room in hostel . The student will have a database
and a student account to access his Data. These permission shall be showed after
administrator approval. Student can check his data weather its true or need to some
changes.Also he can check the monthly reports of their penalties, room payment and
other stuffs.
o Maintainer
Maintainer only can access the complaint or reports received, just
like receiving an email. The report shall contains the room number
or the receiver track which can be access by the maintainer. Also,
they can update the actions taken for the report or complaint.

5.2.4 General Constraints

The general constraints of our system can be to implement the system in
such a way that it causes least crashes and the system exceptions are
handled properly. The unauthorized data issue must be handled carefully
so that the privacy is maintained and no one can access the data expect
for the authorized user. The GUI is only in English. Login and password is
used for identification of students. This system is working for single server
and limited to HTTP/HTTPS.

5.2.5 Assumptions and Dependencies

o The details related to the student, rooms, report.
o Administrator is created in the database already.
dummy database
o Roles and tasks are predefined.

//tak pasti -

5.2.6 Apportioning of Requirements

The audio and visual alerts will be deferred because of low importance at
this time.