Kasagpan Web and Mobile Application
COMP 3059 – Capstone Project I
Software Requirements Analysis and Design
TABLE OF CONTENT
1. Introduction
1.1. Purpose
1.2. Scope
2. System Overview
2.1. Project Perspective
2.2. System Context
2.3. General Constraints
2.4. Assumptions and Dependencies
3. Functional Requirements
3.1. Functional Requirements
3.1.1. Guest Reservation
3.1.2. Manage Reservation
3.1.3. View Hotel Information
3.1.4. Open Social Media
3.2. Use Cases
3.3. Data Modelling and Analysis
3.4. Process Modelling
4. Non-Functional Requirements
5. Logical Database Requirements
5.1. File Format
5.2. Accessibility and Security
6. Approval
1. Introduction
1.1. Purpose
Our team will be creating Kasagpan Hotel web and mobile application in order to illustrate and manage the interactions and flow of data within the business. The application will enable potential guests to navigate hotel information, book rooms, manage their booking, review their hotel experience, and share their booking through social media. This will allow the customers to confirm their reservation in real-time anywhere without having to bother with time-consuming emails, faxes and reservation staff. The website and mobile application will be updated to keep up with today’s changing technology.
1.2. Scope
The objective for completion of this project is to build a seamless and intuitive website and incorporate into android and IOS platforms. Our mission is to make sure our client is satisfied with the overall application and to solve all the problems from the existing application. The scope of this project to make sure we complete each task in order as the other tasks all depend on the previous. Benefits of using our application will maximize the guest experience by providing tools that will enhance their hotel experience. It will also be designed in a way that guest will be able to use this application to plan around their own individual needs.
2. System Overview
2.1. Project Perspective
The project perspective of this project is to replace the hotel websites’ current system, which is in need of improvements in many areas. The existing user interface was made with the use of a third party web development platform, due to this it minimizes the flexibility of the website. Our plan is to add a stylish user interface for the website and mobile integration for easy accessibility, on both Android and iOS platforms.
With the application we plan to implement, we offer comprehensive reservation confirmation information, which leaves the guests in no doubt as to the details of their booking. All this information will be displayed in the secure Hotel Database, which needs a login and password from the admin and receptionist to access.
2.2. System Context
Strategic issues in regards to the system will involve encouraging guest to use the tools given to them to enhance their booking experience. By having social media integration, it will allow the guest to network with other individuals. This system will specifically address a particular reservation and give guests the flexibility to manage their booking anytime. With this system, it will be introduced as a new way to effectively encourage guest to visit the hotel using the tools implanted within this system.
2.3. General Constraints
- It must be implemented by April 2017
- The platforms will be tested on existing technical infrastructures
- Cross-Browser Compatibility
- Database management (Users may spam/overload the database with false/empty accounts) – Should be managed and functional at all times.
2.4. Assumptions and Dependencies
This project makes the following assumptions:
- High-end computers for fast application loading and executions
- High-speed Internet access available
- Project information changes
- API integration
This project is dependent on:
- Each task must be completed before the other task starts
- Implementation can’t start before prototyping begins
- Testing and debugging can’t occur until a prototype has been made
- The final application can’t be published until it meets all the criteria from the stakeholder
3. Functional Requirments
3.1. Functional Requirments
3.1.1. Guest Reservation
- Guest must be able to reserve a room through the website or through the mobile application.
3.1.2. Manage Reservation
- Guest must be able to view, edit and cancel their reservation through the website or the mobile application
3.1.3. View Hotel Information
- The local map will have points of interest.
- When a user clicks on a point of interest, basic information about the point will be displayed.
- Rating and reviews must be displayed in the hotel web and mobile application and guest must be able to add their own review or ratings through the web and mobile application.
- The weather must be available for guest.
3.1.4. Open Social Media
- The user will be able to open specific social media apps from the website and the mobile application.
3.2. Use Cases
3.3. Data Modelling and Analysis
Normalized Data Model Diagram
Activity Diagrams
Sequence Diagrams
UML Class Diagram
3.4. Process Modelling
Data Flow Diagram
4. Non-Functional Requirments
WEBSITE
- The system must never crash.
- The database must be up all the time.
- Having a short time of response (380 ms per request) tested with 4000 requests at the same time, the performance has been classified as high and reliable.
- The code must be easy to maintain.
- A software developer must be able to correct any defects.
Accuracy
- Using the clever query to request the right information and having several ways to specify the data, the marge of error is 0%.
- The good design will make the user understand and use the app easy and fast, not having too many options but the essentials and leaving a space for any specific request. Very intuitive to the user.
- Most of the Database query is going to be used in the code of the web and mobile app.
MOBILE
Since the app will be built natively for each platform (iOS and Android), there will be no overhead to convert the shared code from one platform to the other. Furthermore, the app will be able to utilize the latest features each platform has to offer. The user interface will be fluid with logical placement of elements.
- It will be easily maintainable by anyone will knowledge of how to code Android or iOS apps.
- Due to the simplicity of the app (only has to retrieve information and display it), it can be used on a variety of devices (does not have to be the newest mobile devices).
- The code will be well documented to ensure future developers of the app will understand how it works.
- The app will have a secure connection to the web application to ensure that no one can intercept the data.
5. Logical Database Requirements
A database will be used to store user information such as reservation, guest details, login and password. Also, a database will be used to populate when a guest needs to manage their reservation and account details. Our web and mobile application will be compliant with ensuring the accuracy and consistency of keeping their information confidential.
5.1. File Format
Each user will have a unique ID, booking ID, first and last name, email address and user type. Their email will allow them to receive booking information or booking confirmation. Each guest will have their own booking, as well as access to the reservation they are booked on a specific date. Each user will also be able to access hotel information, hotel feedback, and amenities. All entries in the database will be sorted by its unique ID in their respective tables. There is a guest table that will contain the ID and the booking ID.
5.2. Accessibility and Security
Guest will only be able to access their own reservation, and account information, therefore no guest can view another guest’s reservation and account information. Only admins will be able to modify anything to do with hotel information and reservations. Each password will be hashed with SHA256 encryption before being stored in the database for added security.
6. Approval
The signatures below indicate their approval of the contents of this document.
