0% found this document useful (0 votes)
81 views13 pages

Final Project

The document outlines a proposed database design project for Mang Inasal, a fast food restaurant chain. It describes the company profile, functional area of food service, current business processes, forms used, and a proposed system development life cycle approach. The project would involve analyzing requirements, designing database tables, developing the backend and user interface, integrating with other systems, testing functionality, and deploying the new employee database system.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
0% found this document useful (0 votes)
81 views13 pages

Final Project

The document outlines a proposed database design project for Mang Inasal, a fast food restaurant chain. It describes the company profile, functional area of food service, current business processes, forms used, and a proposed system development life cycle approach. The project would involve analyzing requirements, designing database tables, developing the backend and user interface, integrating with other systems, testing functionality, and deploying the new employee database system.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 13

Database Design for Mang Inasal, Robinson Lipa

__________

A Project Submitted to the College of Information Technology and Engineering

in partial fulfillment of the requirements

for the course

INFOMAN (Information Management)

__________

Submitted by:
Michael Joshua Sollestre
Kean Velasquez
James Gabriel

June 1, 2023
I. Company Profile
<Include a description of the company which includes, but not limited to:

Company Name, Size, Type of Business, Year Started, Number of Employees,

Nature of Business, etc)>

Company Name: Mang Inasal

Size: 570 stores nationwide

Type of Business: Restaurant

Year Started: December 12, 2003

Number of Employees:

Nature of Business: Fast-Food Chain

Founder: Edgar “Injap” Sia II

II. Functional Area

<Identify the functional area of the selected company that will be used in your final

project>

Functional Area: Food Service

Business Process/Flow in Inasal

1. Order Placement:

○ Customers place their food orders either through the counter, drive-thru, or online

platforms.

○ Cashiers or order takers receive the orders and enter them into the point-of-sale

(POS) system.
2. Food Preparation:

○ Kitchen staff receives the order details from the POS system.

○ Cooks and food preparation staff prepare the food items according to the order

specifications.

○ Quality control personnel ensure the food meets Jollibee's standards.

3. Order Assembly:

○ Once the food items are ready, they are passed to the assembly area.

○ The assembly staff checks the orders, adds condiments, and packages them for

delivery or pickup.

4. Delivery/Pickup:

○ For delivery orders, delivery riders are assigned to deliver the orders to

customers' addresses.

○ For pickup orders, customers collect their orders either at the counter or the

designated pickup area.

5. Payment:

○ Customers pay for their orders at the counter or through the designated payment

methods for online orders.

○ Cashiers or order takers handle the payment transactions and issue receipts.

6. Customer Service:

○ Frontline staff provide customer assistance, handle inquiries, and resolve any

concerns or complaints.
Personnel Involved in Inasal:

1. Cashiers/Order Takers: Responsible for taking customers' orders, handling

payments,

and issuing receipts.

2. Kitchen Staff: Cooks, food preparation staff, and quality control personnel involved in

food preparation.

3. Assembly Staff: Responsible for checking orders, adding condiments, and packaging

them for delivery or pickup.

4. Delivery Riders: Assigned to deliver orders to customers' addresses for delivery

orders.

5. Frontline Staff: Provide customer service, assist with inquiries, and handle

complaints.

Forms and Reports Used in Mang Inasal:

1. Order Slip: Used by cashiers or order takers to record customers' orders.

2. Receipts: Generated for each transaction as proof of payment.

3. Production Sheets: Used by kitchen staff to track food preparation requirements and

inventory.

4. Quality Control Checklists: Used by quality control personnel to ensure food quality

meets standards.

5. Delivery Log: Used to track delivery orders, assign riders, and record delivery details.

6. Complaint Forms: Used to document and track customer complaints or concerns.

7. Sales Reports: Generated to track sales performance, revenue, and other key

metrics.
8. Inventory Reports: Generated to track food and supplies inventory levels.

9. Customer Feedback Forms: Used to gather customer feedback and suggestions.

Functional Area

<Name and description>

Process Flow
Organizational Chart

Forms and Reports Used

III. System Development Life Cycle

<Conduct a study on the existing process on the selected functional area>

Planning:

The Employee Management System will be designed to have a better management

system and database.

System Design:

- Create a database schema to specify the structure of the Employee database, which

includes tables, relationships, and attributes.

- Determine the best database management system (DBMS) for storing and

retrieving employee data, taking into account issues such as scalability, security,

and performance.

- Define the user interface design while keeping usability and accessibility in mind.

Development:

- Create the necessary tables, columns, and relationships depending on the

design to implement the database structure.

- Create backend logic for data validation, storage, and retrieval.

- Create APIs or middleware components to connect the Employee database to

other systems, such as time and attendance or payroll management.

Testing:
- Unit test the separate components of the Employee database to ensure they

work properly.

- Conduct integration testing to ensure that the Employee database interacts with

other systems or modules.

- Perform system testing to assess the Employee database's overall functioning,

data integrity, and performance.

- Conduct user acceptance testing (UAT) with stakeholders to ensure that the

system satisfies their needs.

Deployment:

- Prepare the infrastructure for hosting the Employee database, such as servers,

network setups, and security measures.

- Transfer any current employee information to the new database.

- In the production environment, deploy the database system.

- Users should be given the required training and instructions on how to use the

employment database efficiently.

Maintenance and assistance:

- Create mechanisms for ongoing maintenance, such as backups, monitoring, and

security upgrades.

- Fix any difficulties or bugs discovered after deployment with bug fixes or system

updates.

- Collect user and stakeholder feedback to identify areas for improvement or new

features.

- Plan for future upgrades and scalability in response to changing business


requirements.

Analysis:

Determine the Project Scope and Objectives:

- Define the personnel database system's purpose and goals.

- Determine the project's scope, including the exact functionalities and features

that will be included.

- Determine key stakeholders and learn about their requirements and

expectations.

Conduct a Needs Analysis:

- To gather requirements, and interview HR department representatives and other

stakeholders.

- Identify the present personnel management process's pain spots and

inefficiencies.

- Determine the new system's intended features, functions, and performance

requirements.

Define User Roles and Use Cases:

- Recognize the many user roles in the employee database system, such as HR

administrators, managers, and employees.

- Define use cases to record each user role's interactions and activities.

- Determine the permissions and access levels required for various user roles.
Data Analysis:

- Examine the data types that must be recorded in the Employee database, such

as personal information, job history, skills, certificates, and performance records.

- Determine the dependencies, relationships, and limitations of the data.

- Identify any data privacy or security concerns, and ensure compliance with

applicable legislation.

Risk Evaluation:

- Determine potential hazards and roadblocks to the development and

implementation of the Employee database system.

- Determine the repercussions of each risk and propose mitigation strategies.

Document the Analysis Results:

- Complete documentation documenting the analytical process, including

requirements, use cases, data analysis, integration needs, and dangers, should

be prepared.

- Share the analysis results with stakeholders for review and approval

Detailed System Design:

- Create a database schema to specify the structure of the employee database,

which includes tables, relationships, and attributes.

- Determine the best database management system (DBMS) for storing and

retrieving employee data, taking into account issues such as scalability, security,

and performance.
- Define the user interface design while keeping usability and accessibility in mind.

Implementation

Database Design and Development:

- Create the database schema that determines the structure of the employee

database based on the findings of the investigation.

- Choose the best database management system (DBMS) and configure the -

database environment.

- Based on the design, create the relevant tables, columns, and constraints, and

connections.

Development of the backend:

- Create the logic for the backend to manage data validation, storage,

retrieval, and manipulation.

- Apply business principles and algorithms to the processing of personnel

data.

- Create APIs or middleware components to allow data to be exchanged

with other systems or modules.

User Interface Design:

- Create the user interface (UI) for the employee database system.

- Use screens, forms, and interactive features to collect and present

personnel data.

- Ensure that the UI is user-friendly and intuitive and that it corresponds to


the defined user roles and use cases.

Integration Improvement:

- Integrate with other systems or modules, such as time and attendance

monitoring or payroll management.

- Create data sharing protocols and APIs to facilitate smooth integration.

- Thorough testing is required to assure data consistency and dependability during

integration.

Implementation of Security:

- Implement suitable security measures to secure employee data while adhering to

applicable rules.

- Configure access controls and permissions according to user roles and

responsibilities.

- To protect sensitive information, use encryption, authentication, and authorisation

systems.

Deployment:

- Prepare the infrastructure for hosting the employee database system,

such as servers, networks, and security measures.

- Transfer any current employee information to the new database.

- Deploy the system to production, ensuring seamless integration with

current systems and minimal downtime.

- Users should be given the appropriate training and instructions on how to

use the personnel database system efficiently.


Maintenance

- Create monitoring systems to track system performance, detect problems,

and maintain data consistency.

- Maintain and support the system on an ongoing basis, addressing any

bugs, issues, or enhancement requests.

- To ensure data security and system stability, update the system on a

regular basis with security patches and upgrades.

- Gather user feedback to identify areas for improvement and future

additions

IV. Database Design

<Based from the Design of your Information System, design your Database using the

Database Life Cycle as your guide.>

Database Initial Study

Database Design

Implementation and Loading

Testing and Evaluation

Operation

Maintenance and Evolution

You might also like