Himilayan Hotel System Analysis and Design

This case study focuses on the system analysis and design of Himilayan Hotel. It covers different systems life cycles, feasibility study, systems investigation, data modeling, and functional and non-functional requirements.

Running head: HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
System Analysis and Design: A Case Study of
Himilayan Hotel
Name of the Student
Name of the University

1HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Table of Contents
Task 1: Different Systems Life Cycles............................................................................................2
1.1 Description of Different Information System Life Cycle Models:........................................2
1.2 Stages of Selected Life Cycle Model: V-Shaped Model.....................................................13
Task 2: Feasibility Study...............................................................................................................14
2.1 Components of a Feasibility Report:...................................................................................14
2.2 Importance of Feasibility Analysis:.....................................................................................17
Task 3: Systems Investigation.......................................................................................................18
3.1 System Requirement Investigation:.....................................................................................18
3.1.1 Investigation and Analysis Methodology:.....................................................................18
3.1.2 Constraints:....................................................................................................................20
3.1.3 Operational Requirements:............................................................................................20
3.2 Data Modeling:....................................................................................................................21
3.3 Functional and Non-Functional Requirements:...................................................................24
3.4 Addressing System Requirements:......................................................................................25
References:....................................................................................................................................26

2HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Task 1: Different Systems Life Cycles
The Systems Lifecycle Models are broadly known as the software development life cycle
models. The SDLC or software development life cycle illustrates and incorporates organized
phases that are essential part for developing an information system. Based on the needs of the
owner from proposed information system, a system is characterized and its features are
designed. Different SDLCs, used in this modern era, are developed or modified (from
conventional models) according to the requirement significant for developing the proposed
system (Alshamrani and Bahattab 2015). With increase in the demand of complex information
systems, the software engineers and project managers are adapting new SDLC models that are
more flexible and accept change of scope. In the following section mainly four SDLC models
has been described in brief, along with the benefits and drawbacks of these models.
1.1 Description of Different Information System Life Cycle Models:
Model 1 - Waterfall Model: The Waterfall Model is one of the oldest SDLC models and
is considered as the sequential flow of progress. There are five stages in waterfall model.
Development progress goes from one phase to the next without having any opportunity to come
back to the previous one except staring the phase from the beginning (Vijayasarathy and Butler
2016). The software development projects which do not focus on changing the requirements
after the designing phase starts are suitable for employing Waterfall Model.
Stages of Waterfall SDLC: Waterfall Model has five phases. The phases are
requirements gathering and analysis, designing, execution, testing and releasing. In the
execution phase the codes are written and actual software is developed. The releasing phase is
used for deploying the final product into organization’s environment.
The first stage in waterfall SDLC is requirement gathering and analysis. In this stage, the
project team collects the business and user requirements. The project team uses various fact

3HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
finding and information gathering techniques to collect the requirements. The system analyst
then uses the collected information (business and user requirements) to generate the system
requirements. These requirements are verified so that only the essential and meaningful
requirements can be considered by the project.
The designing phase is based on the process of developing designs of the proposed
systems. The system designs are developed on the basis of the accepted system requirements.
The designers create various UML diagrams, database designs and network models. All these
designs are essential to understand the behavior, internal communication and components of
the system.
In the execution phase, the whole system is actually developed step by step. The coding
part of the system is done within this phase. The developers of the project understand the
designs and make the system as mentioned in those designs.
The testing phase is used for validating and verifying the test. The first test is finding
bugs, done by the developers. The testing team checks whether the developed system
performs intended tasks or not. This process is repeated until a suitable product is developed.
The releasing phase can be referred as deployment phase. In this phase, the system is
deployed within the customer organization’s environment.
Advantages Dis-Advantages
The users of the system can easily
understand what software they will use and
its features as all the things are already
defined
Change of requirements in the final phases of
the project can lead to uncertain outcomes
including project failure
The approach toward the development of the
system is structural
It is not possible in any way to go back to
any of the previous phase without initiating

4HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
the work from the beginning of that phase
and continue in sequential manner
All the phases within this model is well
defined and completely understandable
This model is not flexible in term of
incorporating new scopes within the project
after it startsScheduling the project is very easy as all the
requirements are pre-defined
Every phase in the Waterfall Model has
particular deliverables
The project is costlier than other models due
to maintenance of proper planning and
documentationEach of things in this model is checked and
verified at each phase thus leading to early
detection of errors
Model 2 – V-Shaped Model: The model is considered to be the extension of the
Waterfall Model. In this model, the progress bar does not point downward in a linear fashion.
Instead, the progress bar starts to climb upwards after the implementation phase, thus forming a
V-Shaped graphical view. The early testing of the requirements, architecture and designs of the
project makes V-Shaped Model different from the Waterfall Model.
Stages of V-Shaped SDLC: The V-Shaped model has business requirement analysis,
system design, architectural design, module design, coding, unit testing, integration testing,
system testing phase, business requirements testing phases. The business requirement
analysis, system design, architectural design, module design phases are associated with unit
testing, integration testing, system testing phase, business requirements testing phases
correspondingly.
Stage 1 - Verification Phases: The Business Requirement Analysis is the first phase of
V-Shaped SDLC Model. The project manager and business analysts tries to understand the

5HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
problem form customer’s perspective (Rastogi 2015). In this stage the acceptance test design
planning is carried out.
System Design is the second stage in the V-Shaped Model. In this phase, the complete
system is designed. The designs serves as the reference copy of system test plan, developed
within this phase.
Architectural Design Phase is the stage where the architecture of the proposed system
is understood and developed. This architectural design of the system is also known as the High
Level Design.
Module Design Phase the internal designs of the HH System will be defined (Chowdhury
et al. 2018). The designers take into account that low level designs must be compatible with
various modules present in the system.
Stage 2 - Coding Phase: The modules of the proposed HH System are evaluated in
this phase and converted into sections of codes. The developers and manager deiced what is
the best suitable coding language to develop the system and meet the architectural needs
(Rastogi 2015). The system is developed step by step based on the understanding of designed
modules.
Stage 3 – Validation Phase: Unit Testing is done at the very beginning of validation.
This phase concentrates mainly on the codes. The purpose of this phase to eliminate the bugs
before any other validation activity is carried out.
Integration Testing Phase carries out the testing of architecture designed in the
Architectural Design Phase (Sarker et al. 2015). The communication between the internal
modules of the system is done here.

6HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
In order to test the designs of the system, the system testing phase has been developed.
The system functionality is mainly checked within this phase. This phase has great contribution
toward solving compatibility issues.
The business requirements are tested within acceptance testing. The compatibility of the
software with the business is validated within this testing phase.
Figure 1: Waterfall Model Phases
(Source: Created by Author)

7HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Figure 2: V-Shaped Model Phases
(Source: Created by Author)
Advantages Dis-Advantages
This model is very easy to understand and
simple to apply within project
This project is less flexible than Waterfall
Model which indicates this model is not
suitable for big and complex projects
Each of the phases defined within the model
has specific set of deliverables
The scopes can be adjusted but by paying a
huge cost and chances of being successful is
very less
As the testing is done in the early phases of
the project, the chance of getting success is
higher than Waterfall Model
This model does not produce any prototype,
therefore the users and owner of the system
do not have any idea regarding how the
product will look like until the completion of
implementation phase
This model is great for those projects which The path of eliminating the issues, found

8HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
has easily understandable requirements during the testing stages, is not clear and
often leads to project delay and financial
issues
The product can be verified and validated in
the early stages of the development project
This project is costly like Waterfall Model, in
some cases it is costlier than Waterfall Model
Model 3 – Prototyping Model: As the name suggests, Prototyping Model mainly
focuses on developing incomplete models of the software in the early stages of the project. The
approach of developing the prototypes has been taken into account for reducing the gap
between the customer requirements from the system and developer’s understanding of the final
product (Vijayasarathy and Butler 2016). This model is widely adopted by various organizations
because Prototyping Model is very flexible and provide insights of the final product from the
beginning.
Stages of Prototyping SDLC Model: This SDLC model has six phases in total.
However, the stages does not executed sequentially. The quick design, building prototyping,
customer evaluation and refining prototyping is done continuously as a loop until the required
product is not obtained.
The first stage is requirement gathering. This stage refers to the process of identifying
the requirements of the system. The project team uses various information collection processes
to identify the essential requirements. The basic concept of this model is coping with the new
requirements. That is why the project team does not consider this phase as a crucial one and
jumps to the design phase without wasting too much time.
The quick design stage is actually the design phase of the model. As the name
suggests, the project team does some basic designs to graphically present the gathered

9HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
requirements. These designs are enough to establish a general idea of the components of the
system.
In the prototype building part, the system components are created separately. The
project team does not develop the final product as a whole, instead they develop different
components of the system one at a time.
Customers have a great part in this mythology. The developed prototypes are evaluated
by allowing the customers to use it and provide their feedbacks. These feedbacks are collected
and analyzed. The suitable feedbacks are considered to be valid and used for redeveloping the
prototypes.
In the next phase, the prototypes are modified based on the feedbacks of the customers.
In some cases, almost fifty percent of the actual model is changed. After the model is
considered to be properly functioning and meets customer needs, the product is send to next
phase.
At the final stage, the engineer product, all the developed prototypes are brought
together and a complete product is developed. The product is also deployed in the customer
environment in this phase.
Figure 3: Prototyping Model Phases
(Source: Created by Author)

10HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Advantages Dis-Advantages
The cost for implementing this model far less
than Waterfall Model. Moreover, the model
requires less time.
The analysis is not effective. If the user is not
able to understand the prototype and does
not have any idea regarding the final product,
the project will suffer in the long run
The possibility of delivering wring user
objectives to the developers is very high
The involvement of the user in the project is
significant
The additional time required for developing
the prototypes increase complexity
The prototype implements are costly
approach so project manager cuts down
other project related activities
Model 4 – Spiral Model: If the elements of prototyping and designing is combined in a
specific model then it would result in holding advantages of both the top-down and bottom-up.
The reason behind the successful adoption within numerous of software development projects
is having both the top-down and bottom-up benefits (Alshamrani and Bahattab 2015). This
model is well-known for its capability of combining characteristics of Waterfall Model and
Prototyping Model.

11HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Figure 4: Spiral Model Phases
(Source: Created by Author)
Stages of Spiral SDLC Model: Identification, design, construct or build and evaluation
and risk analysis are the four stages of spiral model. These stages are also known as object
determination, identify and resolve risk, development and test and planning of integration.
In the objective determining method, the requirements of the project are identified.
Based on the business and user requirements, the project team and customer organization
determines the objectives of the project. These objectives will act the guideline of the projects.
In the second phase, the system drafts are developed along with the designs of the
system. The second phase provide guidelines for verifying and validating the developed drafts
and designs.

12HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
In the third stage, the porotypes of the proposed system are developed. These concept
is directly borrowed from the prototyping model. The prototypes are used for identifying flaws in
the developed preliminary models so that detailed designs of the system can be developed. The
final system is developed in the third phase.
In the final phase, the test and development plans are created and executed.
Advantages Dis-Advantages
The severe issues are identified at the early
stages of the project thus providing better
idea of the cost and time estimation
The cost and time required for developing the
final product is more than other models
The developers are engaged in developing
the system from early stages
The re-usability option of elements of the
project is very low
The risk management approach of this model
is very good and it allows developing the
system into various stages
The risk managers need special skills to
handle risks thus leading to conclusion that
additional cost have to be spent for hiring
specialized risk managers
The Selection of Suitable Model (V-Shaped Model): As the proposed System
Himilayan Hotel will be handling the customer centric work, the requirements are easily
understandable. The project manager will have all the essential requirements before initiating
the designing the phase. The possibility of scope creep is very less as Himilayan Hotel has
complete idea of what product they need. This suggests that congenital predictive models are
best suited for this project. That is why the V-Shaped SLDC model has been selected for HH
System project. The organization does not need any prototypes. Therefore, the idea of spiral or
prototyping can be turned down.

13HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
1.2 Stages of Selected Life Cycle Model: V-Shaped Model
The procedural or staged life cycle in a system investigation as the stages divides the
tasks into separate sections. The tasks with same purpose are grouped in a single stage thus
providing better understand and control over the project activities. The procedural/staged
lifecycle models are used for organizing the tasks in a project. Taken as an example, there are
fifty tasks in a project. The project manager is not using any procedural/staged model. The issue
will arise when the team will require something that is essential for carrying out a task but never
considered as important. The procedural/staged does not only manages the tasks and organize
them in order but also assists in identifying the hidden factors that are essential for the project to
be successful.
The stages of the V-Shaped model are described in the following sections.
Stage 1 - Verification Phases: The system and business analysts of Himilayan Hotel
System project will communicate with the Himilayan Hotel staff, manager and owner to identify
their requirements from the system. The project team also carry out a survey and analyze the
documents of Himilayan Hotel to identify the hidden factors of the business.
The designers of the system will create the USE Case and other interaction diagrams to
understand the interaction of the user with the system.
The system designers will select the type of servers, database and internal elements to
design the architecture of the system. The system architecture will be considered as the
blueprint of the system.
Himilayan Hotel System’s internal designs like class diagrams, sequence diagram,
database diagrams, network diagrams and few more diagrams will be created in this phase.
Stage 2 - Coding Phase: The Himilayan Hotel System will be consisted of separate
components. In the coding phase, the system components will be developed. The developers

14HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
will create the website using the ASP.NET and SQL server technology along with the JAVA or
Python based internal system.
Stage 3 – Validation Phase: The de-bugging of the codes will be done by the coders in
this phase.
The system architecture testing a crucial step toward the development. The testing team
verifies whether the developed architecture is accurate or not in the architecture verification
phase.
The system testing phase will be carried for verifying the the Himilayan Hotel System
designs. The designs like USE CASE, class, ERD and many other diagrams will be tested in
this phase.
The main and most crucial testing is requirement testing. In this phase, the business
requirements will be validated to check whether the requirements are as per business objectives
or not. Most of the business requirements of Himilayan Hotel System will be related to customer
processes.
Task 2: Feasibility Study
2.1 Components of a Feasibility Report:
The components of the feasibility report are technical feasibility, economic feasibility,
legal feasibility, operational feasibility and scheduling feasibility. The technical illustrates that the
proposed project must be carried out by using the most relevant technology. The project should
not consider complex and costly technologies if not highly required.
The economic feasibility is for identifying whether the proposed project can deliver profits
to the organization. Taken as an example, the project may cost one million dollar. The

15HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
organization will not expect the system to recover all the invested money in one year. But the
system must be able to deliver profits from third or fourth year after installment.
The legal feasibility may seem like an ordinary matter but it is so powerful that the
organization can get failed if not poorly managed. The system must be developed by following
legal rules. The system should also follow various state and national legislations for carrying out
daily operations. Otherwise, any organization or customer can lodge a complaint against the
organization.
Operational feasibility is for supporting the project by stating that the final product can
support all the business processes effectively and efficiently. The system must be capable of
capturing the objective of each process and carry out the task actively.
Scheduling feasibility is also an important factor in the feasibility study. The customer
organization has plans for using the system from a time when the business is high. If the project
team is not able to deliver the project within time then the organization will face loss even before
installing the system. Thus this feasibility component is a very essential part of system feasibility
study.
The following section represents the feasibility report of the selected organization.
Technical Feasibility: As the Greenwich Rose Hotel wants to control the budget of the
project technical aspects, the website will be developed using ASP.NET and SQL Server. Both
the technologies are free. The internal system can be developed using JAVA or Python and
again these two technologies are free. The only capital related concern is project team member
payment.
Economic Feasibility: The project is using free technologies so the cost of the
development will reduce automatically. However, the V-Shaped Model require more time and
capital therefore, the system functionalities will be effective but cost of the Greenwich Rose

16HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Hotel project will be higher than usual. The salary of SQL Server and ASP.NET developers are
higher than MySQL and PHP developers.
Legal Feasibility: The system will be developed by following the legal requirements.
The Greenwich Rose Hotel system operations will not violate any of the rules implemented by
State or National Government. The organization will devote enough time to understand what is
legal and what is illegal.
Operational Feasibility: After completing the project, the biggest advantage the
Greenwich Rose Hotel will receive is automation of processes. The Greenwich Rose Hotel will
not use paper based working concept as the system database will hold all the information in a
more secure way for a very long time. The organization customers will be able to contact
organization 24*7 using the website.
Scheduling Feasibility: The Greenwich Rose Hotel project is estimated to be
completed within 6 months. One development team will be working on the website and the other
team will work on internal system. The required time is very suitable for the organization as the
hotel will have time to test the system before peak season.
Information Collecting and Fact Finding Techniques Used in Creating the Feasibility
Report are interviews, questionnaires and Observation. The manager and analysists were
responsible for conducting the interviews and questionnaire. The whole project team was
involved in carrying out the process of observation under the supervision of project manager.
The analysts will develop various questions for different uses of the system for interview
process. The analysts will conduct interview with individual users to gather their feedback on the
questions and their answers will recorded in a log file. A set of ten questions are considered to
be efficient for collecting information through interview process. The questionnaire is a more
generic approach where the users will be providing their thoughts on different questions and

17HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
discussion topic. This process is different from interview process based on the venue and
process of collecting data. In case of questionnaire, the participants will be providing their
thoughts through their individual system. As in the selected project all the questionnaire will be
crated in google form. The analysts will be using these collected information to create PI-Charts
and tables. In this case, SPSS analysis method will be used. The observation process will be
carried out under the supervision of project manager. In this process the project manager will
observe the conventional processes used by Himilayan Hotel.
2.2 Importance of Feasibility Analysis:
The reason behind using the feasibility analysis are as following.
i. The project manager will be greatly benefitted by the economic feasibility as this
study will assist the project to convince the stakeholders of the project. The
investors and owner of the organization will be able to identify how much
profitable this project and is will consider change of project cost as normal hazard
in the project progress.
ii. Feasibility study will recognize new business opportunities for the organization
such as the organization will be able to understand how the business can be
expanded
iii. The project manager and development will be able to have an idea on which pal
form they have to develop the system. This will allow then to prepare themselves
for conventional issues and challenges for creating system on that specific
platform
iv. The business alternatives are get lesser. This illustrates that the organization can
concentrate on their core business and improve business patterns to make more
profit.

18HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
v. The timescale of the project completion is an essential part to know for the
project owner. The study also helps the organization to know how the system will
help in processing the business activities. The organization can create plans for
business based on the date on which they will start using the system within
business. Taken as an example, the organization can choose to convert their
mass power toward services while the system will be handling most of the back
office processes.
vi. Makes the decision making process more efficient and effective. The managers
and owners of the organization will get proper assistance in terms of making
business related decisions.
Task 3: Systems Investigation
3.1 System Requirement Investigation:
3.1.1 Investigation and Analysis Methodology:
System Investigation: The Himilayan Hotel (HH) System is proposed for executing the
customer centric works like online reservation, online payment, automatic bill generation,
customer data maintenance and many more. The system will store all the customer and
business process related data in a database. The customer will be able to access the system
functions through a website (Bahill and Madni 2017). The website will be designed for the
customer interaction with business, however the staff of Himilayan Hotel will interact with the
system through a different application, installed within the computers. The system will be
connected to the printers and other IoT devices within the hotel to collect data automatically.
The system will also send e-mail to customers for various purposes like sending promotion,
notification and payment related information.

19HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Analysis Methodology: The project team will consist of various skilled and well
experienced employees who are expert in their individual fields. They will hold meeting several
times before starting the project, so that every aspect of the final product can analyzed and
verified (Elbanna 2016). During this process, the project manager and other responsible
employee(s) will interact with organization owner, managers and staff to collect sufficient data to
form a meaningful idea of the proposed system. The project team will analyze various possible
actions that can be undertaken to complete the project and select only the most suitable one.
The Unified Modeling Language or UML is a great tool for analyzing a software systems
characteristics. The UML assists the project team to understand the behavior of the proposed
system along with providing an idea of the elements essential for completing the system (Al-
Refaie 2015). The UML use case diagram will be able to graphically demonstrate how the
users, customers, managers, internal staff and few more, of the system will be interacting with
the system.
The Scope of the system are as following.
i. The system will be covering all the customer centric processes and convert most
of the processes into automated tasks
ii. The system will handle the payment process both the online and at the hotel
iii. The system will collect the customer activities related data and analyze it to
produce various patterns
Every system, no matter how well developed, has some flaws and limitations. The
Himilayan Hotel system limitations are as following.
i. The system will not be able to produce business patterns that can assist in
expand business (Bahill and Madni 2017)
ii. The system will not be highly protected against the cyber attacks

20HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
iii. The interaction of the staff with the system will be very limited
SDLC Methodology is a significant part of every information system development
project. This project will be carried out by following the processes of V-Shaped model. This
model will allow the owner of the project to have proper documentation of all the stages.
3.1.2 Constraints:
The system will be deployed with a cloud environment, thus it is easy to manage the
performance and capacity of the system. However, including new sections within the system will
not be an easy task. To include a new function in the system will require testing the compatibility
of the proposed module with the existing system architecture. The customer will not be able to
access the system if the server goes down and Himilayan Hotel will not be able to do anything
about it. It is because all the power is provided within the hands of the Host Owner. The
schedule of the project will suffer due to unclear requirement, wrong response from Himilayan
Hotel owner and managers. As the organization does not have any idea of using a system
within their business environment, they will not have proper idea of what kind of internal
functions the Himilayan Hotel System must have to support the business.
3.1.3 Operational Requirements:
The system users will get a good feedback from Himilayan Hotel in terms of customer
service. The system will have a “mail us” section and “call us” section. The customer can mail
their queries if the situation is not urgent and in case of emergency the 24*7 online customer
service center can be contacted. Himilayan Hotel will employ a system administrator who will
handle all the issues in the computers installed in hotel premises and check internal networking
configuration. All the IoT devices will be connected to the main system through the network path
(Ayeh, Au and Law 2016). The system will be connected to the “backup and recovery”
technology which will collect all the data from the cloud and store it elsewhere so that in case
any data is corrupted or deleted, that data can be retrieved from backup and recovery server.

21HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
The Audit Trail of the system will be done in every six months. This trial is essential as many
times security holes in the system are found after audit trials.
3.2 Data Modeling:
Figure 5: Entity Relationship Diagram
(Source: Created by Author)

22HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Figure 6: Context Diagram
(Source: Created by Author)

23HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Figure 7: Data Flow Diagram Level 1
(Source: Created by Author)

24HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Figure 8: Data Flow Diagram Level 2
(Source: Created by Author)
3.3 Functional and Non-Functional Requirements:
Functional Requirements: The functional requirements of the proposed Himilayan
Hotel System has been described below.
i. Authorization: Himilayan Hotel System will have different types of users such as
customer, staff, owner and managers. All the individual user types will perform
separate tasks on the system (Ahmad, Belloir and Bruel 2015). Authorization
implements the access permission which check which user can access which
function and information.
ii. Authentication: Authentication means verifying the registration of the user. If the
user is not registered in the system, then the user will not be able to access
specific information and tasks of the system.

25HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
iii. Data Storing: Storing the data collected from various sources needs to be stored
so that processes can be dynamic and different processes can be run
simultaneously. The data will be stored in a cloud based environment.
Non-Functional Requirements: The non-functional requirements illustrates the
characteristics of the system. The non-functional requirements are as following.
i. Scalability: As mentioned before, the scalability will allow the organization to
manager the resources of the system as per business requirements. The
CLOUD based Himilayan Hotel System will efficient enough to scale the
resources and save cost in lean seasons (Khan et al. 2016).
ii. Security: Security is a significant part of the system. The security allows the
organization to safeguard the customer and business data.
3.4 Addressing System Requirements:
The system will address the authentication and authorization using the backend codes.
The best option for developing the Himilayan Hotel Website is ASP.NET and SQL Server
database (Prince 2016). The C# code will be used in such way that when a user try to access
an unauthorized section, the website redirect the user to the home page. The database will
record the username and password of the user. This username and password will be used at
the time of login. The login process represent the authentication in the website. A database
engineer will develop the designs of the system database and covert the designs into actual
database. These databases will be connected to the ASP.NET application using configuration
tools. The database developer will write the SQL codes to access data as per business need
(Larson et al. 2015). The security and scalability will depend upon the service provider.
Himilayan Hotel will contact with the hosting organization and ask them to implement security
and manage resources.

26HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN

27HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
References:
Ahmad, M., Belloir, N. and Bruel, J.M., 2015. Modeling and verification of functional and non-
functional requirements of ambient self-adaptive systems. Journal of Systems and Software,
107, pp.50-70.
Al-Refaie, A., 2015. Effects of human resource management on hotel performance using
structural equation modeling. Computers in Human Behavior, 43, pp.293-303.
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer Science
Issues (IJCSI), 12(1), p.106.
Ayeh, J.K., Au, N. and Law, R., 2016. Investigating cross-national heterogeneity in the adoption
of online hotel reviews. International Journal of Hospitality Management, 55, pp.142-153.
Bahill, A.T. and Madni, A.M., 2017. Discovering system requirements. In Tradeoff Decisions in
System Design (pp. 373-457). Springer, Cham.
Chen, H.M., Kazman, R. and Haziyev, S., 2016. Strategic prototyping for developing big data
systems. IEEE Software.
Chopra, M. and Kapoor, N., 2016. Choosing the Right Approach: Comparative Study of
Software Process Models. International Journal, 4(3).
Chowdhury, A.Z.M., Bhowmik, A., Hasan, H. and Rahim, M.S., 2018. Analysis of the Veracities
of Industry Used Software Development Life Cycle Methodologies. arXiv preprint
arXiv:1805.08631.

28HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Chuan, A., Graham, P.L., Wong, D.M., Barrington, M.J., Auyong, D.B., Cameron, A.J.D., Lim,
Y.C., Pope, L., Germanoska, B., Forrest, K. and Royse, C.F., 2015. Design and validation of the
regional anaesthesia procedural skills assessment tool. Anaesthesia, 70(12), pp.1401-1411.
Elbanna, S., 2016. Managers' autonomy, strategic control, organizational politics and strategic
planning effectiveness: An empirical investigation into missing links in the hotel sector. Tourism
Management, 52, pp.210-220.
Floricel, S. and Piperca, S., 2016. Project management between will and representation. Project
Management Journal, 47(3), pp.124-138.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: Dealing Non-Functional
Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), pp.7-
13.
Larson, P.Å., Birka, A., Hanson, E.N., Huang, W., Nowakiewicz, M. and Papadimos, V., 2015.
Real-time analytical processing with SQL server. Proceedings of the VLDB Endowment, 8(12),
pp.1740-1751.
Lowet, E., Roberts, M., Hadjipapas, A., Peter, A., van der Eerden, J. and De Weerd, P., 2015.
Input-dependent frequency modulation of cortical gamma oscillations shapes spatial
synchronization and enables phase coding. PLoS computational biology, 11(2), p.e1004072.
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques for
the practicing project manager. John Wiley & Sons.

29HIMILAYAN HOTEL SYSTEM ANALYSIS AND DESIGN
Pani, P. and Behera, A.P., 2017. Communication inventory: Selection and validation with an
Indian population sample. Asian Journal of Management, 8(3), pp.805-808.
Prince, P.P., 2016. Software Development On ASP. Net (Doctoral dissertation, East West
University).
Reka, S.S. and Ramesh, V., 2016. Demand side management scheme in smart grid with cloud
computing approach using stochastic dynamic programming. Perspectives in Science, 8,
pp.169-171.
Sarker, I.H., Faruque, F., Hossen, U. and Rahman, A., 2015. A survey of software development
process models in software engineering. International Journal of Software Engineering and Its
Applications, 9(11), pp.55-70.
Sinnott, C.S., 2014. The RAF and Aircraft Design: Air Staff Operational Requirements 1923-
1939. Routledge.
Tang, B., Sandhu, R. and Li, Q., 2015. Multi‐tenancy authorization models for collaborative
cloud services. Concurrency and Computation: Practice and Experience, 27(11), pp.2851-2868.
Vijayasarathy, L.R. and Butler, C.W., 2016. Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.
Vijayasarathy, L.R. and Butler, C.W., 2016. Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.