Requirements Document
Section 1: Problem Analysis
Description of the Problem
2
Background of the Customer
2
Strategic Direction of the Hotel
2
Constraints and Scheduling
2
Users and Basic Functionality
3
Hotel Operation Information
3
Major Current Problems
3
System Capabilities and Scope
3-4
Conceptual Flow Diagram
4
Feasibility
4-6
Section 2: Elicitation Techniques
Structured/Closed Interview
7
Questionnaire
8 - 10
Section 3: Elicited Requirements
Functional Requirements
11 – 14
Non-Functional Requirements
14 - 15
Interview Questions and Answers
16 - 21
Appendix:
Section 1:
Description of the Problem
Our design team has been approached by the management of a hotel to produce a
software package …..
Background of the Customer
In conference with a key stakeholder of the hotel Mr. Cysneiros, we have been
able to obtain a general overview of the company and identify their current highlevel goals of the prospective system. Mr. Cysneiros indicated that ….
Strategic Direction of the Hotel
There is currently only one hotel in operations and …..
Constraints and Scheduling
Due to the customer using a commercial off the shelf product …..
Users and Basic Functionality
The design team will need to take into consideration both the hotels customer
base as well as their …..
Hotel Operation Information
There are three different room rates.
Major Current Problems
The stakeholder also discussed several problems they are encountering with the
current software.
2
System Capabilities and Scope:
The hotel application to be designed will meet the following overall objectives:
a) Handle
Conceptual Flow Diagram
The following is a concept diagram disseminating the design teams view of the
hotel reservation / booking process from a very high level.
Feasibility Analysis:
Introduction
This section of the report provides a detailed assessment of the project in terms
of whether the expected benefits and costs are realistic and if this project has a
reasonable chance of success. To thoroughly consider this projects feasibility,
the following five areas of risk were assessed.
 Economic Feasibility
 Operational, Organizational and Cultural Feasibility
 Technological Feasibility
 Schedule Feasibility
 Resource Feasibility
.
1
1
Satzinger W. “John. Systems Analysis and Design in a Changing World.” Thompson Learning, 2000, p51
3
Section 2
Elicitation Techniques

After preliminary assessments have been made regarding the
knowledge domain of the Hotel Management Sub-system, we
decided to gain more insight regarding the domain. By using proven
elicitation techniques
Design Implications:
Section 3: Elicited Requirements
Functional Requirements:
Guest Reservation Subsystem:
Introduction: Stakeholders of a hotel have asked us to create a software system
that will control a hotel. .
Goal:
Functional Requirements List: (The system must incorporate the following)
1) Internet reservations must be possible.
Billing Subsystem:
Introduction:
Non - Functional Requirements:
Overall Hotel Application:
Introduction: The following is a list of Non- functional requirements elicited
with regards to the operations of the hotel application to be designed. All
information was revealed from interviewing the key stakeholder of the hotel, the
customer responses via the questionnaire as well as practical knowledge of the
current business environment in Canada.
Non-Functional Requirements List: (The system must)
4
1) Have high usability as a key requirement
5
Appendix – Not Mandatory just illustration to a
a possible line of work
Interview Questions and Answers:
Purpose: By conducting a one on one interview with a significant Stakeholder we will
be able to gain a better understanding of the problem and goals of the organization. In
doing so we will be able to elicit the requirements for the proposed software.
Project Overview: Elicit the requirements for software to control a Hotel. The software
must handle guest reservation and room allocation. Billing system is a must. Control of
foods and beverages should be integrated and also provide administrative reports
allowing decisions regarding stock, price purchasing orders etc.
Background and Contact Information of Interviewee:
Interviewee: Luiz Marcio Cysneiros – Stakeholder
E-mail:
cysneiro@yorku.ca
Interview Information:
Date:
October 9th, 2003
Time:
12:00pm
Location:
3009 Tel Building
Prepared Questions and Responses:
Overview of customer, problem, and environment
General Hotel Questions
6