Comparative analysis on Laravel and Cake PHP and use

of suitable technology for designing and developing a

Hotel Support System.

Module: Information System Project

Submitted by: Sabin Shahi Submitted to: Dr. Martin Stanton

NCC ID: 00151608

Date: 8th June,2018

 Statement and Confirmation of Own Work

Programme/Qualification name: BSc (Hons) in Business Computing and Information

Systems
All NCC Education assessed assignments submitted by students must have this statement as
the cover page or it will not be accepted for marking. Please ensure that this statement is either
firmly attached to the cover of the assignment or electronically inserted into the front of the
assignment.

Student declaration
I have read and understood NCC Education’s Policy on Academic
Dishonesty and Plagiarism.
I can confirm the following details:
Student ID/Registration number: 00151608
Name: Sabin Shahi
Centre Name: Softwarica College of IT & E-commerce
Module Name: Information System Project
Module Leader: Dr. Martin Stanton
Number of words: 1075 words

I confirm that this is my own work and that I have not plagiarized any part of it. I have also noted
the assessment criteria and pass mark for assignments.

Due Date: 8/6/2018

Student Signature: Sabin Shahi
Submitted Date: 8/6/2018
Contents
Title.............................................................................................................................................. 4
Background and research............................................................................................................4
Introduction.............................................................................................................................. 4
Aim........................................................................................................................................... 4
Objectives................................................................................................................................ 5
Development............................................................................................................................... 6
Requirements........................................................................................................................... 6
Functional Requirements......................................................................................................6
Non- functional Requirements..............................................................................................7
Prioritization of Requirements...............................................................................................7
Methodology............................................................................................................................ 8
System Architecture.................................................................................................................8
Use Case Diagram................................................................................................................... 9
Activity Diagram..................................................................................................................... 10
Sequence Diagram................................................................................................................ 11
Learning..................................................................................................................................... 12
Planning and Progress.............................................................................................................. 13
Project Plan............................................................................................................................ 13
Work Breakdown Structure.................................................................................................13
Gantt Chart......................................................................................................................... 14
Tracking Gantt.................................................................................................................... 15
Risk Analysis (Management)..................................................................................................15
References................................................................................................................................ 16
Title
The project is about the comparison between the two framework of php Laravel and cake php
and that uses the suitable technology for development of the hotel support system.

Background and research

Introduction
It’s difficult to find out the services that are provided by a hotel to customers so the system will
provide the detail information about the services of the respective hotels. It allows a customer to
book the room and also provide online payment system to the customers. In order to develop
the system two framework of php Laravel and cake php are compared and the appropriate one
will be used.

Comparison between Laravel and cake php are as follows:

 CakePHP framework is based on (HMVC) Hierarchical model view controller
architecture while Laravel framework is based on (MVC) model view controller
architecture.
 Laravel is open source web framework and free to use while cakePHP is also and open
source web framework but it’s not free of cost.
 Laravel framework is based on the concept of the object oriented database model while
CakePHP is based on the concept of document oriented database model.
 Laravel framework is easy to use compared to CakePHP because Laravel provides the
Artisan facility to the developers.
 For the effective documentation Laravel is ahead CakePHP.
 CakePHP framework is famous for making the small projects and blog site while Laravel
framework is suitable for large scale web applications.
 Laravel provides advanced facilities for the data backup compared to CakePHP.
Both of the framework has its own advantage and disadvantages but the system cannot be
developed using the two framework so the appropriate framework will be used to develop the
system. My SQL is used to create database. (Kundariya)
Aim
The aim of the project is to research on the both the framework Laravel and CakePHP and use
the appropriate framework to create the system.

Objectives
The objectives of the projects are:
 To gain information about both the framework Laravel and CakePHP.
 To research about the web site development and designing.
 Gathering requirements for the project.
 Learn to develop project plan and finishing the project according to the project plan.
Development
Requirements
The method of studying the needs and the hopes of the system is known as the requirement
analysis. The requirement analysis is classified into two parts functional and non-functional
requirement. Functional requirement decides what system will do while non- functional
requirement about the working pattern of system.
The functional and non-functional requirements of the projects are:

Functional Requirements
FR1 Sign up
Description: Sign up
Input: Giving the required information for signup.
Output: Sign up successful.
Rational: Providing access to authorized users.
Dependency: N/A
Source: Author
FR2 Login
Description: Login
Input: Valid username and password
Output: error massages is shown and send the user to login page in case of invalid username
and password, for valid username and password user are shown the required page.
Rational: Providing access to authorized users.
Dependency: Sign up(R1)
Source: Author
FR3 Add/Delete/Book Room
Description: Add/Delete/Book Room
Input: required information
Output: Add/Delete/Book Room details
Rational: Provide information to the users if task is successfully completed.
Dependency: N/A
Source: Author
FR4 Service
Description: hotel services
Input: required information
Output: details about the services provided
Rational: Provide information of required services
Dependency: Depends on user
Source: Author

Non- functional Requirements

NFR1 Performance
Description: Quick result should be provided by the system.
Rational: In case of delay output users will demotivated to use system.
Dependency: N/A
Source: Author

Prioritization of Requirements
For the priotize of the requirement MoSCoW prioritization is used which is as followed:

Requirements Priority
FR1: Sign up Must Have
FR2:Login Must Have
FR3:Add/Delete/Edit Room Should Have
FR4:Services Should Have
NFR1:Performance Should Have

(Coleyconsulting.co.uk, 2016)
Methodology
Waterfall methodology is used to complete the project. (Waterfall Model, 2016)

System Architecture
System architecture provides the detail information about the components used in the system
and the relationship among them. The diagram is shown below:
Use Case Diagram
Use case diagram is a representation of interaction between user and the system. It helps to
gather information about the functional requirements of the system.
Activity Diagram
Activity diagram shows the flow from one operation to another operation. The dynamic behavior
of the system is represented through activity diagram. It is similar to flowchart and show the
flows of the operation. The activity diagram of the system is shown below:
Sequence Diagram
Sequence diagram shows the flow of message within the system. In other hand this diagram
can be said as event diagram which shows the interaction between the component of the
system. The sequence diagram of the system is shown below:
Learning
At the time of research, I have learned to develop an application in PHP programming language
in Laravel framework which has enhanced my skills and gained new information about it and
also learned about cake PHP framework too.
Some knowledge I have gained in this project are:
1. Proper documentation
Creating good report for the application was gained by me, format is also learned for
developing report of application.

2. Gathering information
I have also learned how to gather information to develop proper report and gathering
resources.

3. SQL queries
I have also learned to execute difficult queries in MySQL.

4. Developing UML diagrams

UML diagrams are the behavior of operation of the system created like use case, activity
diagram, gantt chart etc. which defines the application.

5. Different tools and technologies are used

I have used many technologies like visual paradigm, Microsoft project, star UML etc. to
obtain successful result of application.
Planning and Progress
Project Plan
Beginning and end of application was well-defined. It is the process which defines when will the
project will be completed. It is completed using gantt chart. When and how the application is
developed is defined by this phase. Gantt chart shows the progress of the project and how it is
carried out, it was created using Microsoft Project 2010.

Work Breakdown Structure

Gantt Chart
Tracking Gantt

Risk Analysis (Management)

Risk can be known as the success and failure rate of project. Each and every project has risk.
Either risk is low or high in any project development. Risk analysis can also be known as the
process of minimizing the danger of project can face.

Risk Likelihood Consequences Action

System Failure Medium High Timely Maintenance
File Theft Low Low High security
Measures
Natural Calamities Low Medium Regular backup
Less knowledge and Low High Research on required
unskilled man power things for project
References
 Kundariya, H., (No date). Laravel vs CakePHP: The Ultimate Battle For The Supremacy.
[Online] Available at: https://medium.com/esparkbiz/laravel-vs-cakephp-the-ultimate-
battle-for-the-supremacy-12b238cfa430 [Accessed date: 25th May 2018]
 Waterfall Model, (2016). Waterfall Model. [Online] Available at: http://www.waterfall-
model.com [Accessed date: 1st June 2018]
 Coleyconsulting.co.uk. (2016). MoSCoW Prioritisation method. [online] Available at:
http://www.coleyconsulting.co.uk/moscow.htm [Accessed date: 2nd June 2018]