The High Level Scope of the Project

Write The High-Level Scope of the Project and Project Requirements for the
"Open table" which is described in the attached document. It is about Design Pre-Order
System is created for Open-table.
This section is used to define the high level logical boundaries of the project. The emphasis is on the ‘Goal(s’)
of the project. It will include a high level statement of purpose. The anticipated deliverables for the proposed
project (both the ceremony of the project process as well as the product or service that is to be produced.)
Provide enough explanation and detail for the reader to be able to understand what is being proposed.
Detailed Project Requirements
This section of the document lists specific requirements, detailed deliverables (specific products or services)
that the project is expected to deliver. This section lists specific requirements (functional and non-functional) for
project. It may include features, functions, look, feel, design, operations, rules, regulations, policies,
procedures, or compliance concerns that must be met.
Requirements may be divided into the following sections:

1. User requirements. These are requirements written from the point of view of end users, usually expressed in
   narrative form
2. System requirements. These are detailed specifications describing the functions the system must be
   capable of doing
3. Interface requirements. These are requirements about the user interface, which may be expressed as a list,
   as a narrative, or as images of screen mock-ups.
   · User Requirements (Functional)
   Requirements should be written from the point of view of end-users, expressed in a narrative form. They
   should describe the required look, feel, and behavior of the solution(s). This may come from business rules,
   policies, procedures, regulations, or law. Discovery typically is through the elicitation sessions with users,
   stakeholders, and other stakeholders.
   · System Requirements (Non-Functional)
   Detailed system requirements (Note: for a systems related (IS/IT) project, which impose constraints on the
   design or implementation of a system solution, such as performance requirements, security requirements,
   volume of use requirements, or reliability requirements.

Sample Solution