Himilayan Hotel System Analysis and Design

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.