srs_supplemental.docx

SRS Homework Project for

David M. Jones

Bed and Breakfast Management System

SRS

1. Introduction

1.1 Purpose

The purpose of this SRS document is to provide a detailed description of the Bed and Breakfast Management System. It will detail the purpose and features of this software and hardware system. It will describe what the system will do and its constraints. Also it will detail human interaction, program input and output.

1.2 Scope

This system will be a Bed and Breakfast Management System. It will manage reservations and monitor expenses and profits. The design is to enable automatic reservations based on room availability by a given date. The will enable customers enter desired stay and duration dates to see what rooms are available and what the rate is. Once the start and end dates for the selected room are entered, the customer will make a reservation by paying a deposit payment for one day. The payment is made by entering a credit card number. In addition to payment information, the customer's name, address, and phone number are inputted. Reservations are held without guarantee for an agreed upon date. If the reservation is not guaranteed by that date, the reservation will be dropped.

1.3 Definitions, acronyms, and abbreviations

Guest – The person paying to stay at the bed and breakfast

Guarantee – A contract between the owners of the bed and breakfast and the prospective guest the the selected room will be available within the reservation dates

ERD - Entity Relationship Diagram

1.4 References

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.

1.5 Overview

The next section, Overall Description, of this document provides an overview of this system's functionality. It describes the product functions , requirements for its operation, and expected operation outcome. The Specific Requirements section is written primarily for the development of the software for this system and details the system functionality.

2. Overall description

2.1 Product Perspective

The Bed and Breakfast Management System is a self-contained system. It is a system that can be used with any Bed and Breakfast operation. It that has 2 main database structures. The first database structure is for room reservations. It has the following entities: room availability, rate, reservations, customer information. The second database structure is for financial record keeping. It has the following entities: AR, AP, GL and record the customer payments. The GL has the profit-loss report. The financial database receives input from payments. It is used for all financial transactions. It also has user input for expenses and output for monies in payments, and the profit-loss statement. There are two types of users: customer and supplier. The hardware is a network of desktop computers, a central computer that manages the databases, and an Internet web server that is a service leased from a web server company. The operating system are Windows 7 Profession for staff users, Linux for the database server of the reservation and financial systems.

2.2 Product Functions

The functions of the Bed and Breakfast Management System are as follows.

2.2.1 Room reservation lookup

2.2.2 Reservation entry

2.2.3 Guest entry

2.2.4 Guest check out

2.2.5 Payment processing

2.2.6 Profit report

2.3 User characteristics

The users of the BBMS are staff and managers of a small bed and breakfast operation. They have sufficient knowledge on using the Windows operating system and computer hardware. They will have training on operating the BBMS software.

2.4 Constraints

There are no constrains other than what is needed to operate a small bed and breakfast operation.

2.5 Assumptions and dependencies

In order for the BBMS to operate the following assumptions are made:

2.5.1 The business provides a computer on which the BBMS can run.

2.5.2 The business provides a telephone service with which the customer can call in to make a reservation.

3. Specific Requirements

3.1 External interface requirements

The requirements are to enable the user interaction with the BBMS.

3.1.1 User interfaces

3.1.1.1 Main menu – Displays choice of making a reservation, checking a guest out, and printing the profit report.

3.1.1.2 Calendar – Displays any reservations by calendar days a room may have.

3.1.1.3 Reservations – Provides a means to make a reservation

3.1.1.4 Check out – Charges any amount owed by a selected guest and removes the reservation for the room the guest stayed in.

3.1.1.5 Profit report – Display the total of all payments made by a given range of months.

3.2 Objects

The following is a decomposition of attributes and methods as represented in the ERD.

3.2.1 Rooms

The Room attributes are:

3.2.1.1 roomNumber – The room number

3.2.1.2 dailyRate – The cost per day to stay in the room

3.2.1.3 reserved – A boolean value to indicate if a room is reserved or not

3.2.1.4 reservationId – The ID number belong to the reservation assigned to the room

3.2.2 Guests

The guest attributes are:

3.2.2.1 lastName – The guest’s last name

3.2.2.2 firstName – The guest’s firstname

3.2.2.3 address – The guest’s address

3.2.2.3 phoneNumber – The guest’s telephone number

3.2.2.4 creditCardNumber – The guest’s credit card number

3.2.2.5 creditCartExpDate – The expiration date of the credit card

3.2.3 Reservations

3.2.3.1 guestId - ID number of guest who is making the reservation

3.2.3.2 roomId – The room number the reservation is made for

3.2.3.2 roomNumber – The room number the guest will stay in

3.2.3.3 startDate – The first day of the stay

3.2.3.4 lastDay – The last day of the stay

3.2.3.5 guaranteed – A boolean value to indicate if the room is reserved

3.2.3.6 guaranteeDate - The date the reservation guaranteed for

3.2.4 Payments

3.2.4.1 guestId - ID number of guest who is making the payment

3.2.4.2 paymentDate – The date the payment was made

3.2.4.3 amountPaid – The amount paid for the room so far

3.2.4.4 totalAmoutn – The total amount that is payable