Professional Documents
Culture Documents
Refil-Part and Petalalna and Reymiel (Updated)
Refil-Part and Petalalna and Reymiel (Updated)
Refil-Part and Petalalna and Reymiel (Updated)
PHASE 1
(System Planning)
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
2|Page
Phase 1 to Phase 3 Database System Enterprise
Introduction
4|Page
Phase 1 to Phase 3 Database System Enterprise
6|Page
Phase 1 to Phase 3 Database System Enterprise
Findings
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
8|Page
Phase 1 to Phase 3 Database System Enterprise
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
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:
Estimated Cost
14 | P a g e
Phase 1 to Phase 3 Database System Enterprise
Expected Benefits
Company
15 | P a g e
Phase 1 to Phase 3 Database System Enterprise
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
16 | P a g e
Phase 1 to Phase 3 Database System Enterprise
Appendix – A
Company Profile / Company History
Vision
Goals
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
21 | P a g e
Phase 1 to Phase 3 Database System Enterprise
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
24 | P a g e
Phase 1 to Phase 3 System Analysis and Design
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.
DFD Symbols:
Process symbol
26 | P a g e
Phase 1 to Phase 3 System Analysis and Design
Referred to as a box.
Entity Symbol
28 | P a g e
Phase 1 to Phase 3 System Analysis and Design
29 | P a g e
Phase 1 to Phase 3 System Analysis and Design
30 | P a g e
Phase 1 to Phase 3 System Analysis and Design
31 | P a g e
Phase 1 to Phase 3 System Analysis and Design
32 | P a g e
Phase 1 to Phase 3 System Analysis and Design
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.
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: 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
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
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
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
Label: STRIKEFITNESS
39 | P a g e
Phase 1 to Phase 3 System Analysis and Design
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
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
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: 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
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
46 | P a g e
Phase 1 to Phase 3 System Analysis and Design
47 | P a g e
Phase 1 to Phase 3 System Analysis and Design
48 | P a g e
Phase 1 to Phase 3 System Analysis and Design
49 | P a g e
Phase 1 to Phase 3 System Analysis and Design
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