Notes : $40$ events $($mandatory$)$in table whether it is temporal $,$ state, external event $.$I would like to see at least $20($mandotory$)$

features listed here. not from chatgpt. Please provide at least $10$ system$($mandatory$)$ objectives here.$($otherwise i will dislike$)$

Read instruction in the photo and write $40$ events in the table and use format in the pic.

Project Critical Success Factors $10$ points. unique and plagiarism free.Al$-$BasedAl$-$Based Restaurant App $-$ Phase $1$

Phase $1$

You are required to create a project charter in the template that is shared after the problem

description.

There is no limit on the number of pages $/$ numbers of events $/$ number of classes $/$ number of

use cases in all the phases of project work.

Anything that is reasonable and pertinent to the project must be included. Creativity is highly

encouraged. Please follow the instructions carefully.

Problem

Many local restaurants across the city have apps with varying degrees of functionality.

However, due to a lack of a dedicated platform, local businesses struggle to grow their

customer base and offer effective online meal delivery services.

Several customers spend a lot of time not only commuting, but also waiting for their meals at

the restaurant. An information system that would support the expansion and viability of

regional food enterprises should be developed.

This project aims to create a software application that links clients with nearby eateries, allows

online ordering, optimizes delivery logistics$,$ and improves user experience overall, alert

customers on delays in real$-$time, alternative routes$/$restaurants in a pro$-$active manner to

avoid delays and delivering food in a timely manner.

The app should work in tandem with a centralized information system that would continuously

update and communicate food availability in real$-$time.

The app can be a constant companion to diners and alert them$/$guide them with short and

user$-$friendly messages or through any other user$-$friendly mode, on any deals available at the

nearby restaurants.

Project Charter Template

Project Purpose:

A short descriptive statement about the purpose of the project. It should be very short,

no more than $3$ to $4$ sentences.

Project Roles$/$Responsibilities:

These represent the roles and names of each member of the team and the

responsibilities that each has. Include probable users who will assist with the project.

For each member provide an overview of their skills and expertise as well.

Event Table:

The event table is inserted here $($refer to Event Table Template with Examples$)$

I would like to see at least $40$ events. There should be a minimum of $10$ External, $10$

Temporal, and $10$ State events. The remaining $10$ events can be split between the three

groups as you see fit.

Features List: $($From User$/$UI perspective i$.$e$.$ Functional like requirements$)$

The list of features is a list of abilities$/$capabilities that the solution will have. The

features are stated from the perspective of the user. An example might be "that the

system must provide for on$-$line entry of all orders". I would like to see at least $20$

features listed here.

System Objectives: $($From an overall system$/$performance standpoint, i$.$e$.$ Non$-$

Functional like requirements$)$

System objectives are stated from the perspective of the Information Technology group.

An example might be "that all transactions must provide less than $2$ seconds response

time". Please provide at least $10$ objectives here.

Project Critical Success Factors $($Probable$)$:

These represent the factors that will make the project a success. An example might be

"that a business user$($stakeholder$)$ is available to the project full time.". Please provide

at least $10$ factors here.

Preliminary Technical Architecture:

The preliminary technical architecture represents technologies that are under

consideration for application. Examples might be$,".$NET along with the MS$-$SQL

database server".

Event Table Template with Examples:

The event table lists the external, temporal and state events that are to be part of the

software solution.