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

Project Management Plan (PMP)

“Pizza Shop Management Website”


PROPOSED SYSTEM BACKGROUND
1. Introduction
We propose to create a Pizza Shop customer and order management system. This system will
use a backend SQL database to store customer, menu and order information. It will be customer
facing, for customers to take orders, view the food menu and other misc. information about the pizza
shop (open hours, location etc).
The project development is not an easy job. Every aspect of the ‘software design’ project
should be well analyzed and data should be in a very structured manner. Duplicity of the data should
be avoided, to the point and descriptive fields should be taken. I have put my best efforts to
computerize the process of Academic System and other relevant details for ready reference to the
best of my information about this. It is a very comprehensive and complicated job, which involves
many persons; whatever I have analyzed is detailed portion of record entries.
The main outcome is shown through the help of different reports. Various reports that are
made in the project are: -
 List of products
 List of Pizza detail
 Management of Customer

2. Overview
The proposed system will be created using Java for front and back end development, and using SQL for our
database. The system will be designed as a website that Pizza shop customers can access to create new
orders, and also view store information. This will include a menu viewer, customer order forms and storage
of customer address and name information. This is will be a completely new system designed from the
ground up rather than a modification of an existing system.
System process:

3. System Requirements:

The users require a system that has the following features.


 A user-friendly graphical user interface.
 An informative and intuitive website
Two major categories of system requirements are functional and non-functional requirements that
used to demonstrate the system’s functionalities.

4. Functional requirements

Create Order
Primary Actor Customer
Goal in Context Create a new food order for delivery/pick-up
Trigger User wants to order food
Priority High

View Menu
Primary Actor Customer
Goal in Context View food items for sale and price information
Trigger User wants to see what items are for sale
Priority High

New Customer
Primary Actor Customer
Goal in Context Create a new customer entry in system database
Trigger User is ordering food
Priority High

View Customers
Primary Actor Employee
Goal in Context View list of customers and associated addresses
Trigger Employee wants to view customer info
Priority High

5. Nonfunctional requirements

- System should create a smooth user experience.


- Accessing data from the remote server should maintain reasonable (<400ms) response times to
queries.
- Should support using third party hosting services that represent >99% uptime for stability.
- Code maintained should follow Model-View-Controller principles
- Should contain clear and concise documentation.

6. Hardware requirements
Use of a remote hosting server that is industry known and has reliable up times and data transfer
rates.

Table 1 Hardware Specification

HARDWARE SYSTEM MINIMUM


REQUIREMENTS

Processor Intel(R) Core(TM) i5


CPU

Hard disk size 320GB

RAM 4GB

7. Software requirements
Table 2 Software specifications

SOFTWARE SYSTEM MINIMUM REQUIREMENTS

Client Operating System Windows 10 and higher.

Web server Apache.

Server Operating System Windows 2010

Database Management System MySQL server version.

Web browser Mozilla Firefox, Google chrome etc.

Programming Languages PHP, HTML, CSS, and bootstrap.

Text Editor ATOM


8. System models

9. MVC of Project
10.SQL Database

11. Graphical User Interface


a) Main menu
b) Customer Detail Form

c) Order billing form

You might also like