DC SUSHI.

COM
Table of Contents
Title Page number

Table of Contents ……….…………………………………………………………………………………………………….2

Project Charter ……….………………………………………………………………………………………………………… 3

Project Charter Detail ………………………………………………………………………………………………… 3 & 4

Current System one Diagram ………………………………………………………………………………………….… 5

Future System one Diagram ……………………………………………………………………………………………… 6

2
 Project Charter
General project Information CHARTER DATE: 3 July 2023

Project Name DC SUSHI.COM

Project Manager Yalda Qasemi

Expected Start Date 01-Dec-2023

Expected completion Date 01-Mar-2024

Project Details
Project Description Customers of Dc Sushi.com restaurant must physically
walk into the restaurant and register them self to be able
to have access to the website online and be able to order
through website. But there are certain issues with their
registration process:
 There is no synchronization (Customers entered
information doesn’t save into the website
automatedly)
 Lake of security
 No validation happening
3
Objectives  Improve security of logging in process: improving
the website security by not accepting any other
code than the received code by the provided
phone number or email address.
 Improve validation concepts and steps: by adding
two factor authorization into the process.so that
way the customer can get the code through the
provided email address or phone number.
 Establish Synchronization: prepare and improve
the system for better synchronization, so the
system be able to automatically safe all the
entered data so the customer safes time with not
reentering the same data again and can get access
anytime anywhere.
In Scope  Logging in security can be improved.
 The two-factor authorization can be added and
improved.
 The entered data in the restaurant can be saved in
the system automatically.
Out of scope  Not bringing any changes in the logo.
 Not updating the ordering steps.
Deliverables  More secure and trustable online system and
validated system.
Risks  While we will be working on the website the
application might be down for a little while. So,
customers might not be able to get access to
register or order any food.
 Deleting the application accidentally

Estimated Cost $7,500

Stake holders Project Manager: Yalda Qasemi

And approvers Approvers: Robert Smith and Michael Stevenson

Current System 1 Diagram

4
Future System 2 Diagram

5
  Methodology
Waterfall

6
  Business Requirements

BR1 Data Validation: Need to verify the entered 4 unique digit code in our system.
BR2 Synchronization: The entered code needs to go to the database and match the code,
and base on the customers given information.
BR3 Getting pin on phone: Set up API that will send customers data to the 3rd party
D7_verify and it is responsible for sending the code to the customer’s provided email
address or phone number.

1. Identify the current situation.

Define what is important for you in your department or organization.

2. Set S.M.A.R.T goals of where you want to end up.

Your goals should be specific, measurable, achievable, relevant and time bound. List a few goals that
meet these criteria.

7
3. Analyze gaps between where you are & where you want to be.
Get to the details of why you aren’t as successful as desired. Is there an issue with processes, personnel
or something else? List culprits here.

4. Establish a plan to close existing gaps.

Now that you’ve identified the issues it’s time to solve them. Develop action items that bridge the gaps
between you and your end goals.

8
9