introductio1

4
1.0. INTRODUCTION 1.1. Purpose This document will allow for a complete understanding of what is to be expected of the HRCBS to be constructed. The clear understanding of the HRCBS and its’ functionality will allow for the correct software to be developed for the end user and will be used for the development of the future stages of the project. This document will provide the foundation for the project. From this document, the HRCBS can be designed, constructed, and finally tested. This document will be used by the software engineers constructing the HRCBS and the hotel end users. The software engineers will use the SRS to fully understand the expectations of this HRCBS to construct the appropriate software. The hotel end users will be able to use this document as a “test” to see if the software engineers will be constructing the system to their expectations. If it is not to their

Upload: carlrivera

Post on 19-Jul-2016

213 views

Category:

Documents


0 download

DESCRIPTION

123456789

TRANSCRIPT

Page 1: INTRODUCTIO1

1.0. INTRODUCTION

1.1. Purpose

This document will allow for a complete understanding of what is to be

expected of the HRCBS to be constructed. The clear understanding of the HRCBS

and its’ functionality will allow for the correct software to be developed for the

end user and will be used for the development of the future stages of the project.

This document will provide the foundation for the project. From this document,

the HRCBS can be designed, constructed, and finally tested.

This document will be used by the software engineers constructing the

HRCBS and the hotel end users. The software engineers will use the SRS to fully

understand the expectations of this HRCBS to construct the appropriate software.

The hotel end users will be able to use this document as a “test” to see if the

software engineers will be constructing the system to their expectations. If it is

not to their expectations the end users can specify how it is not to their liking and

the software engineers will change the document to fit the end users’ needs.

1.2. Document Conventions

This document features some terminology which readers may be unfamiliar

with.

Page 2: INTRODUCTIO1

1.3. Intended Audience and Reading Suggestions

This document is written for the researchers, software developers,

advanced practitioners, documentation writers, and users involved in CDN

domain to initiation an open discussion for exploring development opportunities

regarding the internetworking between CDNs. Section 2 discusses the steps that

are to be undertaken to “bring-up” or “cease” an internetworking arrangement

between CDNs. In the next section, system features with their functional

requirements are presented to highlight the major services provided by the

intended product. Then the external interface requirements highlighting the

logical characteristics of each interface between the software product and the

users are discussed. Finally, this specification is concluded with the reference

documents on which this document is based on.

1.4. Scope of project

The software product to be produced is a Hotel Reservation and

Centralized Billing System which will automate major hotel operations. The first

subsystem is a Reservation and Booking System to keep track of reservations and

room availability. The second subsystem is the Tracking and Selling Food

System that charges the current room. The third subsystem is a General

Management Services and Automated Tasks System which generates reports to

audit all hotel operations and allows modification of subsystem information.