SDD Done
SDD Done
Bahawalpur
Department of Information Technology
For
Supervisor
Mr. Faisal Shehzad
Supervisedby
Mr. Faisal Shehzad
Signature___________
Introduction
Hotel management is one of the business sectors that shows constant progressions in use of
technologies. This process of evolving includes computerized room reservation and hotel
resource management. There are also few head turning advancements with self-check-ins,
self-checkouts, and mobile room key accesses. As there are always front and back runners in
a race, there are also hotels in developing countries who still uses time consuming paper-
based employee and hotel service management system. In such hotels, making reservation is
hard since customer does not know the existence of the hotels, except locals. Even if their
existence is known, one has to make a phone call or contact local travel agents to make room
reservations. The hotel management system designed in this paper delivers basic services of
providing hotel information, allow users to reserve and cancel rooms, process reservation
payments online through hotel website. It also provides organized hotel room and employee
management system. The analysis phase of the system development plan is the phase where
the behavioral and functional features of the system are identified. It answers the questions
like ‘what the system does?’, ‘who are the primary users?’ and ‘what is its functional
capacity?’ This is achieved by classifying and identifying system specifications as functional
and non-functional system requirements. Functional requirements determine the basic
features of the system that indicate what input it takes, how it processes it and what outputs it
gives. The non-functional requirements define the quality attributes of the system including
performance, security, and other system capabilities.
Design methodology and software process model
This work also includes threat modeling of the system which has become the essential part of
system design as data is always required to be in movement. This section identifies potential
threats that could lead to loss of confidentiality, integrity, and availability of the system. This
is done by decomposing the system into components, sampling out possible threats and
suggesting prevention techniques.
System overview
The following points are considered the general objective of the research
Control and research the real life workflow and be able to understand and identify
o real life and business problems.
To purpose a solution to the problem identified.
Analyze and design a solution that fulfills Sale Purchase is the process of efficiently
monitoring the constant flow of units into and out of an existing inventory. This process
usually involves controlling the transfer in of units in order to prevent the inventory from
becoming too high, or dwindling to level that could the operation of the company in the
difficulties. Sale Purchase is very important for big business and private owned organization
especially where there are a lot of orders are being placed every day and there are a lot of
materials and the maintenance is really important which the system will do and also will
record the time taken to process an order and this system is really important as it can help the
organization to be alerted when the level of inventory is very low and focus on the three
aspects of sale purchase and prevent from failures in the future
Architectural design
System architectures have two major components, hardware, and software. The hardware
component includes client computers, servers and network that connects the two. In the
hardware architecture the client computers are responsible for displaying information and
1
passing commands, in another word, as an input and output medium of the system whereas
the server process and stores data. This relationship is defined in the server-client architecture
of the system. Software architecture is an abstraction of the software component of a system
that describes the behaviour of the system and how its elements communicate with each
other. It provides different architectural views to different audiences such as architects,
programmers, evaluators, configuration managers and customers. This divisions provides
detailed descriptions such as the functionality of the system (user interface), how the
components connect to each other and work together, non-visible/non-functional features of
the system, how the development should be managed and how the software is implemented
on the hardware infrastructure. Software architecture is shaped based on the most important
requirements of the system. These requirements are classified as functional and non-
functional requirements.
Process flow/Representation
The Project work will ensure reservation of hotel rooms, staff management, and resource
management. A “Use Case” scenario is the room search for room reservation. Users may face
difficulties searching between available and booked rooms, but the automated system would
search more efficiently with the proficient search algorithm. All details of the rooms are
stored in the database servers and can be retrieved or modified with very little stress. Another
“Use Case” is the accounts receivable and payable field of the F&A module. The accounts
receivable simply captures all funds coming-in with their sources and dates while the
accounts payable displays the money going-out of the organization with their destination. The
business flow is quite simple; however, to accomplish all these tasks is burdensome for both
the customer side and the hotel side without an efficient and integrated hotel management
system.
The design (Graphical) must be comprehendible and not clumsy to the user; easy to
use, and easy to understand.
The system should be able to generate reports and print out information on users
demand. The system must have access levels based on user roles such as Manager-
2
Administrator-Accountant-Other staff.
3
Design models [along with descriptions]
ClassDiagram
4
SequenceDiagram
5
State TransitionDiagram
6
Data FlowDiagram
7
Schematic diagram
8
Timing diagram
9
Data design
Database design is the process of producing a detailed data model of database. This data
model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a data definition language, which can then be used
to create a database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are the
tables and views. In an object database the entities and relationships map directly to object
classes and named relationships. However, the term database design could also be used to
apply to the overall process of designing, not just the base data structures, but also the forms
and queries used as part of the overall database application within the database management
system (DBMS).
The process of doing database design generally consists of a number of steps which will be
carried out by the database designer.
Appendix I
Cookies:
These are text files sent to a user’s browser related to how the customer interacts with
the website. Often users will get a pop-up that requests that the user “shares cookies.”
After confirmation, the information in these text files is sent back over to the server,
based on how the user responded and interacted with the site.
DB Database
Data Grid View Control which Showing data in a Grid view
OLMS Online Labour Management System
CRUD Create, Read, Update, Delete
User Someone who interact with the software
PHP HyperText Preprocessor
SQL Structured Query Language