Refil-Part and Petalalna and Reymiel (Updated)

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 56

Phase 1 to Phase 3 Database System Enterprise

University of Caloocan City


Biglang Awa St. Grace Park East, Caloocan City
Telephone number: 310-6856

Computer Studies Department

PHASE 1

(System Planning)

HSIRI Hotel All-in-One


Self-Service System

Prepared By:
BSIS – 3B
Duran, Rsidy
Estrada, Mark Lexter
Petallana, Louie
Refil, Cristian Paul
Verutiao, Reymiel

Prepared to:
Prof. Catherine Llena MPA, MIT
Database System Enterprise, Professor

1|Page
Phase 1 to Phase 3 Database System Enterprise

PHASE 1: SYSTEM PLANNING

System planning is the first phase in developing a


system. It organizes the details before implementing
the action. It also entails making decisions about how
and what to do in order to achieve a system goal.

The planning phase involves the entire team to


gathers data and searches for as much information as
possible. it also requires the team to organized the
activities required to attain a particular goal. This
will determine the feasibility of the proposed project.
The team has systems or processes in place to make sure
everything runs smoothly. Planning should be put into
action in order to attain corporate objectives.

This Phase shows the System planning accomplished


by Rsidy Duran, Mark lexter Estrada, Louie Petallana,
Cristian Paul Refil, and Reymiel Verutiao.

2|Page
Phase 1 to Phase 3 Database System Enterprise

Introduction

In the ever-evolving landscape of the hospitality industry,


hotels face the challenge of enhancing guest experiences while
keeping up with technological advancements. Many establishments
strive to integrate automated systems to streamline operations, yet
some continue to rely on outdated, manual processes. The HSIRI
Hotel All-in-One Self-Service System aims to bridge this gap by
offering a comprehensive, tech-savvy solution for both guests and
hotel staff.

Unlike traditional manual systems, which can be inefficient and


prone to errors, the HSIRI Hotel All-in-One Self-Service System
provides a seamless, integrated platform for managing all aspects
of a guest's stay. This includes everything from self-booking and
real-time availability updates to communication with hotel staff
for services like room service, housekeeping, and laundry. By
automating these processes, the system significantly enhances
operational efficiency and guest satisfaction.

The system also empowers hotel administrators with tools to


customize room preferences, manage user accounts, and monitor guest
requests, all from a centralized admin panel. However, it's
important to note some limitations, such as the absence of direct
payment processing and guest login security, as well as potential
technical challenges like connectivity issues or system downtime.

Our proposal for the HSIRI Hotel All-in-One Self-Service System


is driven by the need to modernize hotel operations and improve the
3|Page
Phase 1 to Phase 3 Database System Enterprise

overall guest experience. By adopting this innovative solution,


hotels can ensure a smooth, convenient, and enjoyable stay for
their guests, while also optimizing their internal processes.

4|Page
Phase 1 to Phase 3 Database System Enterprise

System Request Summary

In the hotel industry, traditional manual processes for


managing guest services can become a significant impediment as
operations expand. To address this, the HSIRI Hotel All-in-One
Self-Service System is proposed as an innovative solution designed
to integrate mobile booking and a wide array of guest services,
providing a comprehensive and seamless experience for guests.

Relying solely on manual processes for booking, guest


assistance, and service management can hinder a hotel's growth and
efficiency. Manual documentation increases the risk of misplaced
records, introduces inefficiencies, and makes it difficult to
provide a smooth guest experience. Moreover, the lack of real-time
updates and communication channels can lead to delays and errors in
service delivery.

The HSIRI Hotel All-in-One Self-Service System aims to overcome


these challenges by offering a digital platform that ensures real-
time availability and pricing updates, automates the booking
process, and facilitates easy communication between guests and
hotel staff for various services such as room service,
housekeeping, and laundry. The system also empowers administrators
with tools to customize room preferences, manage user accounts, and
monitor guest requests effectively.

However, it's important to recognize some limitations of the


proposed system. It does not support direct payment transactions,
requiring guests to settle payments through traditional methods.
5|Page
Phase 1 to Phase 3 Database System Enterprise

Additionally, the customer panel operates in guest mode only,


lacking login security, and the system may face technical
challenges like connectivity issues or downtime.

This initiative aims to replace the inefficiencies of manual


documentation with a modern, streamlined approach, enhancing the
guest experience and optimizing hotel operations. By implementing
the HSIRI Hotel All-in-One Self-Service System, hotels can align
their services with contemporary technological standards and ensure
a more efficient and enjoyable stay for their guests.

6|Page
Phase 1 to Phase 3 Database System Enterprise

Findings

Following an interview with hotel staff, it was revealed that


the hotel currently relies on manual processes for booking rooms,
managing guest requests, and updating room availability. This
manual approach consumes valuable time as employees must log
bookings and guest information manually, diverting them from their
core responsibilities. Additionally, communicating with guests for
services such as room service, housekeeping, and laundry involves
inefficient manual tracking.

Project Scope:
 Self-Booking and Check-In: The proposed HSIRI Hotel All-in-One
Self-Service System aims to streamline the room booking and
check-in procedures for guests.
 Automated Guest Details: Guest data will be automatically
recorded upon booking and stored in a secure database, ensuring
a smooth check-in process.
 Real-Time Availability and Pricing: The system will provide
real-time updates on room availability and pricing, enabling
guests to make informed decisions.
 Guest Assistance and Communication: Guests can easily request
services and communicate with hotel staff through the system,
enhancing the overall guest experience.
 Admin Tools: Authorized personnel will have the ability to
customize room preferences, manage user accounts, and monitor
guest requests efficiently.

Constraints:
 Payment Transactions: The system does not support direct
payment transactions; guests must settle payments through
traditional methods.
 Login Security: The customer panel operates in guest mode only,
without login security.

7|Page
Phase 1 to Phase 3 Database System Enterprise

 Technical Limitations: The system may face issues such as


connectivity problems or downtime, which could impact its
effectiveness.
 Device Compatibility: The system is designed primarily for use
on PC desktops or laptops, limiting accessibility on mobile
devices.

8|Page
Phase 1 to Phase 3 Database System Enterprise

(SWOT) Strength, Weaknesses, Opportunities, and Threats

Strengths
 Efficient Booking and Check-In: Facilitates efficient room
booking and check-in processes for hotel guests.
 Comprehensive Guest Data Management: Easily manages and
organizes guest details and preferences.
 Time-Saving: Provides quick access to recent booking and guest
service records.
 Error Minimization: Minimizes the risk of human error in
booking and service requests.
 Scalability: Can handle a large volume of guest and service
records.

Weaknesses
 Payment Limitations: Lack of direct online payment transactions
limits payment convenience.
 Login Security: Limited to guest mode access without login
security for guests.
 Technical Dependence: System effectiveness is contingent on
stable connectivity and uptime.

Opportunities
 Enhanced Guest Experience: Streamlines the booking and service
request process, improving the overall guest experience.
 Operational Efficiency: Reduces the workload for hotel staff by
automating administrative tasks.
 Data-Driven Decisions: Provides comprehensive data that can be
analyzed to improve hotel management and guest services.

Threats
 Internal Risks: Potential for internal misuse or sabotage by
hotel staff.
 Market Competition: Presence of many competitors in the hotel
industry offering similar or advanced technological solutions.

9|Page
Phase 1 to Phase 3 Database System Enterprise

Feasibility
Operational
 HSIRI Hotel All-in-One Self-Service System: This system
eliminates the reliance on manual techniques for managing guest
bookings and service requests, ensuring that data is secure and
accurate. The digital platform enhances the hotel's operational
efficiency by providing reliable services for handling guest
information and preferences.

Economical
 Cost-Effectiveness: The system accurately manages room bookings
and service requests on a real-time basis, reducing the need
for manual paperwork and saving time and effort for both guests
and hotel staff. This not only streamlines the booking and
service process but also contributes to the overall cost-
effectiveness of the system.

Technical
 Technical Resources: The technical resources required for the
HSIRI Hotel All-in-One Self-Service System include computers
and secure databases for efficient operation. The system needs
stable internet connectivity to ensure real-time updates and
communication between guests and hotel staff.

Schedule
 Implementation Feasibility: The proposed system is feasible in
terms of schedule, aligning with the objectives of providing an
easy and efficient booking and service management process for
hotel guests. The technical requirements are readily available,
ensuring a timely implementation of the system.

10 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Recommendation

The HSIRI Hotel All-in-One Self-Service System features a user-


friendly Graphical User Interface (GUI) designed to comprehensively
manage various aspects of hotel operations. Implementing this
system is highly recommended to address the primary challenges
faced by the hotel, particularly in managing guest bookings,
service requests, and room availability.

 Enhanced Efficiency for Hotel Staff: Hotel personnel will


experience enhanced efficiency in monitoring bookings, updating
guest records, and managing various service requests.
 Streamlined Booking Process: The proposed system simplifies the
booking process, ensuring a user-friendly experience for guests
from booking to check-out.
 Hassle-Free Guest Services: The system reduces manual work by
automating guest service requests and communications, providing
a seamless experience for guests.
 Accurate and Accessible Records: The system offers accurate and
easily accessible records of guest interactions and service
requests, saving time and effort for staff.
 Organized Data Management: The system contributes to the
efficient organization of booking and service data, making it
faster and more reliable for the hotel's operations.

Implementing the HSIRI Hotel All-in-One Self-Service System


will be highly beneficial, providing a solution that aligns with
the hotel's objectives of efficient booking processes, user-
friendly interfaces, and streamlined record-keeping. This system
will significantly enhance operational efficiency and guest
satisfaction, positioning the hotel as a modern and competitive
establishment.

11 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Gantt Chart

System Planning
 2nd Week of March: Preparation of the proposal and
identifying a hotel to gather detailed information for
the proposal.
 March 14th: Proposal approval and obtaining a
recommendation letter from the school.
 March 15th: Visit to the selected hotel to interview
staff and gather initial data.
 March 19th: Review and finalization of interview
questions.

System Analysis
 4th Week of March: Evaluation and selection of the hotel
for system implementation.
 1st Week of April: Investigation and analysis of all
gathered information from the hotel.

System Design
 3rd Week of April: Designing the system model based on
the hotel's requirements.
 4th Week of April: Finalizing the complete design of the
system model.

System Implementation
 1st Week of May: Implementation of the constructed HSIRI
Hotel All-in-One Self-Service System.
 2nd Week of May: Training and practice sessions to ensure
smooth operation of the system.

System Maintenance
 The HSIRI Hotel All-in-One Self-Service System will be
utilized by the hotel staff and authorized
administrators for system maintenance and operations.

12 | P a g e
Phase 1 to Phase 3 Database System Enterprise

13 | P a g e
Phase 1 to Phase 3 Database System Enterprise

System Requirements

Desktop or Laptop:

 Processor: Intel® i3 7th gen or Higher


 1.8 GHz or Higher
 Minimum of 6GB RAM
 At least 32GB HDD space
 64-bit operating system, x64-based processor
 Monitor
 Keyboard
 Mouse

Estimated Cost

Regarding on the cost of the system, here’s the


diagram shows the total cost of creating this system.
The following will be paid only once while the
developers are creating the system.

DESCRIPTION QUALITY/DAYS COST TOTAL


ELECTRICITY BILL FOR
Every 30 DAYS ₱126 ₱126
COMPUTER
Device of the System PC /
1 ₱15,000 ₱15,000
LAPTOP
Installation of System ₱5,000 ₱5,000
TOTAL ₱20,126

14 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Expected Benefits

Company

 This system will be classified as eco-friendly by


reducing the use of paper.
 It will give accurate records of the client of the
HSIRI Hotel.
 The staff and customer job will be efficient by
saving time and effort in keeping records and
booking.
 It will be secured, only the admin or any
authorized person can access the data from the
system.
 Computation of in this system will be accurate

15 | P a g e
Phase 1 to Phase 3 Database System Enterprise

COMPARISON OF THE MANUAL AND COMPUTERIZED OPERATION

Manual System
ITEMS QUANTITY/DETAILS PRICE TOTAL
Yellow Pad
Paper 2 set (when it 160.00 160.00
runs out they
will buy a new
one)
Ballpen
(Panda Crystal 25 pcs. per box 250.00 250.00
Ballpen)
TOTAL: P535.00

Computerized System
ITEMS QUANTITY/DETAILS PRICE TOTAL
Electricity 70watts * 10 hrs.
Bill for 1000 126.00 126.00
Computer
* 0.7kWh*6*30 days COST PER MONTH: P126.00/month

The difference between 2 systems, in manual system


operation the company spent P410.00 pesos a month while
in computerized system operation the company spent
126.00 pesos a month. They can save 284.00 pesos per
month. With just the saved money from converting manual
system into computerized, hsiri hotel can retrieve the
payment for computer system in just 3yrs, and the
computer in computerized system can be used up to 5-
10yrs before needing to change hardware or upgrade.
With the help of this monitoring system.

16 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Appendix – A
Company Profile / Company History

HSIRI Hotel, a renowned hospitality brand, entered the


Philippine hotel industry with the aim of revolutionizing
the guest experience across the country. The concept
originated from a vision to provide unparalleled comfort
and convenience to travelers, setting new standards in the
hospitality sector.

Founded by a team of visionary entrepreneurs, HSIRI


Hotel was established on the principles of exceptional
service, attention to detail, and a commitment to guest
satisfaction. Drawing inspiration from global hospitality
trends, the founders sought to create a hotel brand that
seamlessly blended luxury with affordability.

In line with the Filipino tradition of warm


hospitality, HSIRI Hotel expanded its presence to the
Philippines, introducing innovative concepts and
personalized services to meet the diverse needs of guests.
The founders recognized the importance of offering a
comprehensive range of amenities and facilities to ensure
a memorable stay for every visitor.

The franchise model became instrumental in HSIRI Hotel's


expansion strategy in the Philippines, establishing a
network of hotels in key tourist destinations nationwide.
The success of the franchise model underscores the brand's
dedication to providing a superior hospitality experience
for Filipino and international guests alike.

Since its introduction to the Philippine market, HSIRI


Hotel has emerged as a preferred choice for travelers
seeking comfort, convenience, and luxury. The brand's
unwavering commitment to excellence and continuous
17 | P a g e
Phase 1 to Phase 3 Database System Enterprise

innovation has earned it a reputation as a leader in the


Philippine hospitality industry, with properties in major
cities such as Manila, Quezon City, and Cebu.

Driven by a mission to redefine hospitality standards,


HSIRI Hotel embodies the ethos of personalized service,
attention to detail, and a relentless pursuit of guest
satisfaction. As a beacon of hospitality excellence, HSIRI
Hotel remains dedicated to providing unforgettable
experiences and creating lasting memories for all guests
in the Philippines.
Mission

 To enhance the guest experience by providing a comprehensive and


seamless self-service system that streamlines hotel operations
and empowers guests to customize their stay according to their
preferences.

Vision

 To revolutionize the hospitality industry by offering an


innovative All-in-One Self-Service System that transforms the
guest experience, creating a welcoming and personalized
environment where every guest feels valued and at home.

Goals

 To provide convenient and accessible hotel solutions that empower


guests to tailor their stay to their individual needs and
preferences, fostering a sense of community and support within
the hotel environment.

18 | P a g e
Phase 1 to Phase 3 Database System Enterprise

19 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Appendix – B

Fact Finding

NAME: Anytime Fitness Staff DATE: Dec.


TIME: 4:30 PM
1.How many rooms does your hotel have available in
total? A total of 41 rooms. 10 rooms from Deluxe,
14 rooms from Premium, and 4 rooms from VIP.
2.How can I extend my time in the room that I get?
The staff will call you and will ask you if you
would like to extend. If yes one of the members
of staff will go to your rooms and you will give
the payment to him, after that the staff will
pay at the counter.
3.Is there a reservation in your hotel? Is a
downpayment required to book a room?
How long does the reservation expires if the customer
is out of reach.
Yes, but to have a reservation we are making
sure first that the customer will surely get the
room that he/she reserved. No downpayment. Most
likely 1 hour only because if he/she didn’t
return the room can be access by another
customers if there is.
4.What are the differences between your hotels room
categories?
o The difference between our hotel rooms are their
spaces. For the Deluxe the space is small, for
the Premium the space is Medium, and for the VIP
the space is large.
20 | P a g e
Phase 1 to Phase 3 Database System Enterprise

5.How many floors does your hotel have?


A total of four floor including the rooftop.

21 | P a g e
Phase 1 to Phase 3 Database System Enterprise

6.Are the categories on your hotel floor the same?

As in all Deluxe rooms are on the first floor, all


Premium rooms are on the second floor, and all VIP
rooms are on the third floor?
No, there are different room categories on each floor.
7.How do you keep track of the people that make reservations
at your hotel?
We are giving them a stab, a stab with numbers
to verify what rooms they choose and how many
hours they book.

After that, we will record it in our yellow


paper. The names are not included, it is just a
mandatory for us to have a record on how many
customers are availing our hotel.
8.Is your hotel open for 24/7? What are the shifting hours of
your staff?
Yes. There are a total of three shifting hours
of our employee. First, 8:00 a.m. – 4 p.m.,
Second, 4:00 p.m. – 12:00 a.m., Third, 12:00 am
– 8:00 a.m.Do you have menus or different cooks of food for
sale?
o Oo, madame pa kaming tinitinda pero ang pinaka
mabenta samen ay liempo sisig, at ung kalahating
manok.
9. Does your hotel have a social media platform?
Our hotel doesn’t have any social media
platform.

Interviewed By: Rsidy Duran and Louie Petallana

22 | P a g e
Phase 1 to Phase 3 Database System Enterprise

Proof of Interview

Store Picture

23 | P a g e
Phase 1 to Phase 3 Database System Enterprise

PHASE 2: SYSTEM ANALYSIS

The main objective of the phase is to understand


the proposed project and build a foundation for the
systems design phase.

The proposed system could help the HSIRI hotel to


manage their booking and helpdesk system

You identify the business-related requirements for


the new information system, including outputs, inputs,
processes, performance, and controls.

This Phase shows the System analysis accomplished


by Louie S. Petallana, Rsidy Duran, Mark Lexter
Estrada, Reymiel Verutiao and Cristian Paul Refil.

24 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Requirements Modeling / Sale and Product Monitoring


During requirements modeling, systems developers
must identify and describe all system requirements.
System requirements is a characteristics or feature
that must be included in information system to satisfy
business requirement and be acceptable to users.

The proposed system for booking and helpdesk


system. This proposed system is developed to make it
easy for the HSIRI hotel to manage booking and helpdesk
system.

System requirements fall into five general


categories: outputs, inputs, processes, performance,
and controls.

Output:
 The system will display the available
products
 The system will display the available rooms.
 The system admin should be capable of
creating new products, services and others
on helpdesk.
Input:
 The admin must manage and supervise the
system.
 The employee must be input all the details
of the new created products.
Process:
 he system must determine the quantity of
available room in the branch

25 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Performance:
 The system can do basic functions such as
update, delete, or add data.
 The system can accommodate large quantity of
data without malfunctioning.
Control:
 Only the admin/authorized person can update,
delete, or add data.
 The system has C.R.U.D functions.
Data and Process Modeling
Graphical methods like flow chart will be used to
describe the system. One of the popular methods is to
draw a set of data flow diagrams.

1. Data Flow Diagrams (DFD)

A data flow diagram (DFD) shows how data moves


through a system it also shows program processing
steps.

A set of DFDs provides a graphical model that shows


what the system does, not how it does it.

DFD Symbols:

Process symbol

 Receives input data and produces output.

26 | P a g e
Phase 1 to Phase 3 System Analysis and Design

 Referred to as a box.

Data flow symbol

 Represent the flow of data on one or more data


items.
 Its symbol is a line with a single or double
arrowhead.

Entity Symbol

 A rectangle that represents an entity.

Data store symbol

 Represent data that the system stores.


 The physical characteristics of a data store are
unimportant because you are concerned only
 with a logical model.
 Is a flat rectangle that is open on the right side
and closed on the left side.

Creating a Set of DFDs

Create a graphical model of the information system


Based on your fact-finding results.

Performing three main tasks

Step 1: Draw a context diagram

Step 2: Draw a diagram 0 DFD

Step 3: Draw the lower-level diagrams

Context Diagram DFD for a Sale Monitoring System


27 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Diagram 0 DFD for a HSIRI HOTEL

28 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Context Diagram for a HSIRI HOTEL

29 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Lower Level 1 DFD for a HSIRI HOTEL System

Lower Level 1.1 DFD for a HSIRI HOTEL System

30 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Lower Level 1.2 DFD for a HSIRI HOTEL System

Lower Level 2.0 DFD for a HSIRI HOTEL System

31 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Lower Level 2.1 DFD for a HSIRI HOTEL System

32 | P a g e
Phase 1 to Phase 3 System Analysis and Design

2. Data Storage and its relationships


Data storage determine the content of the database
and its tables that will be used in the storage and
retrieval of data

HSIRI HOTEL SYSTEM DATABASE

3. Data Dictionary
A Collection of data in central storage of
information about the system’s data. An analysis of the
data collected and documented about the system. It also
defines and explains all the data elements in the
system.

A data element, also called a data item or field,


33 | P a g e
Phase 1 to Phase 3 System Analysis and Design

is the smallest piece of data that has meaning.

34 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Label: ID
Module: gym_members Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label: NAME
Module: gym_members Alias: NAME
Type and Length: Text Default Value: None
Source: Database Acceptable Value: Text
Security: Admin User Responsibility: Admin
Description and Comments: The name of the client
Label: BIRTHDAY
Module: gym_members Alias: BDAY
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The Birthday of client/customer
Label: ADDRESS
Module: gym_members Alias: ADDRESS
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: The address of the client/customer

Label: EMAIL
Module: gym_members Alias: EMAIL
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The email of the client/customer

35 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Label: PHONE NUMBER


Module: gym_members Alias: PHONE_NUMBER
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The contact number of the
client/customer

Label: DURATION
Module: gym_members Alias: DURATION
Type and Length: Varchar 30 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the duration of plan that they avail
Label: REGISTERED
Module: gym_members Alias: REGISTERED
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the registered date for clients
Label: EXPIRATION
Module: gym_members Alias: EXPIRATION
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: expiration of their plan that they avail

Label: BILL
Module: gym_members Alias: BILL
Type and Length: VarChar 255 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The bill for the duration that they
avail

Label: YOGA
Module: gym_members Alias: YOGA
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: STRIKEFITNESS

36 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Module: gym_members Alias: STRIKEFITNESS


Type and Length: Varchar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: MUAY THAI
Module: gym_members Alias: MUAY THAI
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: MOTION FITNESS
Module: gym_members Alias: MOTIONFITNESS
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: GROUP POWER


Module: gym_members Alias: GROUPPOWER
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: ZUMBA
Module: gym_members Alias: ZUMBA
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: POUND
Module: gym_members Alias: POUND
Type and Length: Varchar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: HITSTEP
Module: gym_members Alias: HITSTEP
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin

37 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Description and Comments: The program/class of Anytime Fitness


Label: CARDIO
Module: gym_members Alias: CARDIO
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: RAYTONATOR
Module: gym_members Alias: RAYTONATOR
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: ID
Module: unpaid Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label: NAME
Module: unpaid Alias: NAME
Type and Length: Text Default Value: None
Source: Database Acceptable Value: Text
Security: Admin User Responsibility: Admin
Description and Comments: The name of the client
Label: BIRTHDAY
Module: unpaid Alias: BDAY
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The Birthday of client/customer
Label: ADDRESS
Module: unpaid Alias: ADDRESS
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: The address of the client/customer

Label: EMAIL
Module: unpaid Alias: EMAIL
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
38 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Description and Comments: The email of the client/customer

Label: PHONE NUMBER

Module: unpaid Alias: PHONE_NUMBER


Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The contact number of the
client/customer

Label: DURATION
Module: unpaid Alias: DURATION
Type and Length: Varchar 30 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the duration of plan that they avail
Label: REGISTERED
Module: unpaid Alias: REGISTERED
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the registered date for clients
Label: EXPIRATION
Module: unpaid Alias: EXPIRATION
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: expiration of their plan that they avail

Label: BILL
Module: unpaid Alias: BILL
Type and Length: VarChar 255 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The bill for the duration that they
avail
Label: YOGA

Module: unpaid Alias: YOGA


Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: STRIKEFITNESS
39 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Module: unpaid Alias: STRIKEFITNESS


Type and Length: Varchar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: MUAY THAI
Module: unpaid Alias: MUAY THAI
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: MOTION FITNESS
Module: unpaid Alias: MOTIONFITNESS
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: GROUP POWER


Module: unpaid Alias: GROUPPOWER
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: ZUMBA
Module: unpaid Alias: ZUMBA
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: POUND
Module: unpaid Alias: POUND
Type and Length: Varchar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
Label: HITSTEP
Module: unpaid Alias: HITSTEP
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness
40 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Label: CARDIO
Module: unpaid Alias: CARDIO
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: RAYTONATOR
Module: unpaid Alias: RAYTONATOR
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The program/class of Anytime Fitness

Label: ID
Module: delete_members Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label: NAME
Module: delete_members Alias: NAME
Type and Length: Text Default Value: None
Source: Database Acceptable Value: Text
Security: Admin User Responsibility: Admin
Description and Comments: The name of the client
Label: BIRTHDAY
Module: delete_members Alias: BDAY
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The Birthday of client/customer
Label: ADDRESS
Module: delete_members Alias: ADDRESS
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: The address of the client/customer

Label: EMAIL
Module: delete_members Alias: EMAIL
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
41 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Description and Comments: The email of the client/customer

Label: PHONE NUMBER

Module: delete_members Alias: PHONE_NUMBER


Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The contact number of the
client/customer

Label: DURATION
Module: delete_members Alias: DURATION
Type and Length: Varchar 30 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the duration of plan that they avail
Label: REGISTERED
Module: delete_members Alias: REGISTERED
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the registered date for clients
Label: EXPIRATION
Module: delete_members Alias: EXPIRATION
Type and Length: VarChar 60 Default Value: None
Source: Database Acceptable Value: Number
Security: Admin User Responsibility: Admin
Description and Comments: expiration of their plan that they avail

Label: BILL
Module: delete_members Alias: BILL
Type and Length: VarChar 255 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The bill for the duration that they
avail

Label: ID
Module: inout_members Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label:CUSTOMER ID

42 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Module: inout_members Alias: CUSTOMERID


Type and Length: VarChar 255 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: This is for the customer id
Label: LOG DATE
Module: inout_members Alias: LOGDATE
Type and Length: VarChar 255 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the client/customer logdate
Label: TIME IN
Module: inout_members Alias: TIMEIN
Type and Length: VarChar 255 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The timein of the client/customer

Label: AM STATUS
Module: gym_members Alias: AM_STATUS
Type and Length: VarChar 255 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The status of the client/customer

Label: TIME OUT


Module: inout_members Alias: TIMEOUT
Type and Length: VarChar 255 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The timeout of the client/customer

Label: PM STATUS
Module: gym_members Alias: PM_STATUS
Type and Length: VarChar 255 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The status of the client/customer

Label: ID
Module: timeout Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number

43 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Security: Admin User Responsibility: Admin


Description and Comments:
ID of clients
Label:CUSTOMER ID
Module: timeout Alias: CustomerID
Type and Length: VarChar 50 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: This is for the customer id
Label: LOGOUT DATE
Module: timeout Alias: Logoutdate
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the client/customer logout date
Label: LOGOUT TIME
Module: timeout Alias: LogoutTime
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: The logout time of the client/customer

Label: ID
Module: timein Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label:CUSTOMER ID
Module: timein Alias: CustomerID
Type and Length: VarChar 50 Default Value: None
Source: Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: This is for the customer id
Label: LOGOUT DATE
Module: timein Alias: Logoutdate
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
Character
Security: Admin User Responsibility: Admin
Description and Comments: the client/customer logout date
Label: LOGOUT TIME
Module: timein Alias: LogoutTime
Type and Length: VarChar 60 Default Value: None
Source: Product Database Acceptable Value: Variable
44 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Character
Security: Admin User Responsibility: Admin
Description and Comments: The logout time of the client/customer

Label: ID
Module: instructor Alias: ID
Type and Length: Int 11 Default Value: None
Source: Database Acceptable Value: Integer Number
Security: Admin User Responsibility: Admin
Description and Comments:
ID of clients
Label: Class
Module: instructor Alias: Class
Type and Length: text Default Value: None
Source: Database Acceptable Value: text
Security: Admin User Responsibility: Admin
Description and Comments: This is for class/program of
client/customer

45 | P a g e
Phase 1 to Phase 3 System Analysis and Design

4. Hierarchy plus Input-Process-Output (HIPO)


Chart
A flow chart that provides a graphical technique
for designing and documenting the system. It also shows
the hierarchical structure of related modules on a
system.
A set of tasks to be performed by Booking and
Monitoring System

ROOM & PRODUCTS 1.1. MANAGE


MONITORING SYSTEM
TRANSACTION/PAYMENTS
1.SALES RECORD 1.2. PAYMENT RECORDS
2.PRODUCTS RECORD 2.1. PROCESS ORDER
3.INVOICE 2.2. PRODUCTS STOCK
3.1 INVOICE PREPARATION
PROCESS
3.2. REPORT

46 | P a g e
Phase 1 to Phase 3 System Analysis and Design

5. Input-Process-Output (IPO) Chart

A diagram that lists all input, all processes, and


all output

Name of Module: ANYTIME-FITNESS MEMBERSHIP MANAGEMENT


SYSTEM
Input: Store_User, Output: All of the sales
Store_Password, and products data of
Admin_User, lembest
Admin_Password,
Create Data, Add Sales,
Add Order, Add Product,
Edit Data, Delete Data
Process: The System will provide data for Sales and
Products.
Calls: Manage Sales and Table: Sales / Products
Products Database
Name of Module: SALES RECORD
Input: Store_User, Output: All of the sales
Store_Password, record of Lembest and can
Admin_User, be manipulated by the
Admin_Password, Edit user.
Sales, Delete Sales
Process: The system will show all the sales record.
Calls: Manage Sales Record Table: Sales Database
Name of Module: PRODUCTS RECORD
Input: Store_User, Output: All of the product
Store_Password, record of lembest and can
Admin_User, be manipulated by the
Admin_Password, user.
Edit Product, Delete
Product, Create Product
Process: The system will show all product data and
user can edit, delete, and create new products in the
system.
Calls: Manage Product Table: Product Database
Records

47 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Name of Module: INVOICE


Input: Store_User, Output: All of the Items
Store_Password, Add Sales of lembest and can add
sales record
Process: The system will collect the order and provide
another sales and product update to its database
Calls: Manage Customer Table: Sales / Products
Database
Name of Module: MANAGE TRANSACTIONS / PAYMENTS
Input: Store_User, Output: All order List of
Store_Password, Add Sales Customer
Process: The system will provide the order details of
the customer
Calls: Manage payments Table: Sales Database
Name of Module: PAYMENTS RECORD
Input: Store_User, Output: Sales record of
Store_Password, Add Sales payments
Process: The System will automatically save the
payment or sales record to its database
Calls: Monitor Sales Table: Sales Database
Record
Name of Module: PROCESS ORDER
Input: Store_User, Output: All order details
Store_Password, Add Order, of customer
Add Sales
Process: The system will process and automatically
record the order to its product
Calls: Monitor Product Table: Products Database
Records
Name of Module: PRODUCT STOCKS
Input: Store_User, Output: All quantity of
Store_Password, available stock products
Admin_User,
Admin_Password, Edit
Product, Delete Product,
Create Product
Process: The system will show how many products are
available.
Calls: Available Stock Table: Products Database
Products

48 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Name of Module: INVOICE PREPARATION PROCESS


Input: Store_User, Output: It will show the
Store_Password, Add Order, preparation process before
Add Sales proceeding to payment.
Process: The system will provide a response to
customer
Calls: Manage invoice to Table:
customers
Name of Module: REPORT
Input: Store_User, Output: It will show all
Store_Password, Add Order, the reports in sales.
Add Sales
Process: The system will report the completed sales to
its database.
Calls: Add sales record Table: Sales Database

49 | P a g e
Phase 1 to Phase 3 System Analysis and Design

PHASE 3: SCREEN LAYOUT

Screen 0

Screen 1

50 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.1

Screen 1.2

51 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.3

Screen 1.4.0

52 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.4.1

Screen 1.4.2

53 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.5

Screen 1.6

54 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.7

Screen 1.8.0

55 | P a g e
Phase 1 to Phase 3 System Analysis and Design

Screen 1.8.1

56 | P a g e

You might also like