Introduction

1.1 Purpose

We help food entrepreneurs bring their products and services to market at super

speed. Food-X partners with early stage companies from across the food supply
chain, from agriculture through consumer packaged goods, and helps these
companies grow fast through.

1.2 Document Conventions

None

1.3 Product Scope

Food-X helped us build and launch a market validated product, raise venture capital, and
ultimately exit to one of the leading technology companies in the

Project scope is the part of project planning that involves determining and documenting a
list of specific project goals, deliverables, tasks, costs and deadlines. The documentation of a
project's scope, which is called a scope statement or terms of reference, explains the
boundaries of the project, establishes responsibilities for each team member and sets up
procedures for how completed work will be verified and approved.

During the project, this documentation helps the project team remain focused and on task.
The scope statement also provides the team with guidelines for making decisions about
change requests during the project. Note that a project's scope statement should not be
confused with its charter; a project's charter simply documents that the project exists. Large
projects naturally tend to change as they progress. If a project has been effectively "scoped"
at the beginning, then managing these changes will be easier. When documenting a
project's scope, stakeholders should be as specific as possible to avoid scope creep, a
situation in which one or more parts of a project end up requiring more work, time or effort
because of poor planning or miscommunication. Effective scope management requires good
communication to ensure that everyone on the team understands the extent of the project
and agrees upon exactly how the project's goals will be met. As part of project scope
management, the team leader should solicit approvals and sign-offs from the various
stakeholders as the project proceeds, ensuring that the proposed finished project meets
everyone's needs
 1.4 Project Description

We are looking for reducing wastage Food system for your final year project
Everyone enjoys the functions with a lot of food and other products and most of them left
waste or unused .We all waste food for various reasons. Typically it’s as a result of there has
been an amendment of plans and it’s out of our management, however, most of the time
we tend to waste identical varieties of food for identical a pair of main reasons:
We’ve got bought or read an excessive amount of, or we’ve got forgotten to use it on time.
Regardless of the rationale why you throw out food, you got it and currently, It cost
accounting you to throw it out.
So, after you square measure throwing out food, or recording the food you’ve got wasted,
cash A note the explanations for your scraps and see if there square measure tiny changes
that you just will build to cut back this waste and prevent plenty of dollars.
To solve this problem we come up with a system which can take request from the users who
want get settle with the waste food they can request to donate or sell at cost to our systems
managers who comes to them at given time and pick the order and further park that food to
needy place where most people are without food according to need status.

2. External Interface Requirements

2.1 User Interfaces

 be attractive and pleasing to the eye.

 allow the user to try out different options easily.
 be easy to use.
 use suitable colours for key areas.
 use words that are easy to understand aimed at the type of user.
 have help documentation.

1.1 Hardware Interfaces

Specify the logical characteristics of each interface between the software product and the
hardware components of the system. This includes configuration characteristics (e.g.,
number of ports, instruction sets), what devices are to be supported, and protocols.
2.2 Software Interfaces

A Software Requirements Specification (SRS) is a document that describes the nature of a

project, software or application. ... This includes the purpose, scope, functional and
nonfunctional requirements, software and hardware requirements of the project.

2.3 Communications Interfaces

Specify the various interfaces to communications such as local network protocols, etc.
These are protocols you will need to directly interact with. If you happen to use web
services transparently to your application then do not list it here. If you are using a custom
protocol to communicate between systems, then document that protocol here so designers
know what to design. If it is a standard protocol.

3. System Features (Use Cases)

3.1 Use Case Diagram

Registration
Admin

Login

Navigate
Customer

Add Item

Remove Item Item

Review Order

Employ Replace Order

Receive for Order

Update Menu

Receive Confirmation

Check Out
3.2 Create Account

3.2.1 Name:

Create account.

3.2.2 Goal:

Everyone enjoys the functions with a lot of food and other products and most of them left
waste or unused .We all waste food for various reasons. Typically it’s as a result of there has
been an amendment of plans and it’s out of our management, however, most of the time
we tend to waste identical varieties of food for identical a pair of main reasons:

3.2.3 Input:

The user inputs a username, password, e-mail, and demographic information.

3.2.4 Output:

The user is either told that the account creation was successful or that it failed.

3.2.5 Main Scenario:

A user connects to the cluster monitoring system wishing to use its features. Before
he or she can access the system, however, he or she must have a valid account.

3.2.6 Pre-condition:

The user must be connected to the system with a supported web browser.

3.2.7 Steps:
Step 1: The user is shown a log in/create account screen.
Step 2: The user chooses ‘Create Account’ option.
Step 3: The user enters requested details (i.e. username and password).
3.2.8 Post-condition

The user receives his or her account

3.2.9 Exceptional Scenario 1

In the case of an error, the user will be told that the account creation was
unsuccessful.

3.2.10 Example
3.3 Login

3.3.1 Name:

Login

3.3.2 Goal:

The purpose of this feature is to grant valid users access to system resources.

3.3.3 Input:

The user inputs a username and a password.

3.3.4 Output:

The user is either told that they were successful in logging into the system or that
their username and password combination was invalid.

3.3.5 Main Scenario:

A user connects to the cluster monitoring system wishing to use its features. Before
he or she can access the system, however, he or she must log into the system using a
valid account.

3.3.6 Pre-condition:
3.3.6.1.1.1.1 The user must be connected to the system with a supported web browser.
The user must also have a valid account.
3.3.7 Steps:
Step 1: The user is shown a log in/create account screen.
Step 2: The user chooses ‘Login’ option.
Step 3: The user enters requested details ( username and password).

3.3.8 Post-condition

The user is granted access to the system.

3.3.9 Exceptional Scenario 1

In the case that the user does not have a valid account, or the user inputs invalid
data, he or she will be denied access to the system. The error message will only
specify that the combination of username and password provided was invalid.

3.3.10 Example
3.4 Logout

3.4.1 Name:

Logout

3.4.2 Goal:

The purpose of this feature is to close the current user’s GUI session, allowing him or
her to leave and not grant other people access to his or her account.

3.4.3 Input:

The user clicks on the ‘logout’ button.

3.4.4 Output:

The screen is returned to the main login/create account screen.

3.4.5 Main Scenario:

A user has finished monitoring the cluster and wishes to leave. To prevent
unauthorized access, the user wants to return the current computer to its initial
state.

3.4.6 Pre-condition:

The user must be connected to the system with a supported web browser and
logged in with a valid user account.
3.4.7 Steps:
3.4.7.1 Step 1: The user clicks the ‘logout’ button.
3.4.8 Post-condition

The user is no longer logged in.

3.4.9 Example

3.5 Update User

3.5.1 Name:

Update User

3.5.2 Goal:

The purpose of this feature is to allow the user to update his or her demographic
information, or to allow an administrator user to change general user’s access level.

3.5.3 Input:

The user or administrative user clicks the ‘update user’ button.

If an administrative user selects this button, he or she will be given a list of users.
Once the administrative user selects a user to modify, he or she will be presented
with that user’s demographic info and access level. The administrative user will then
be able to modify this content.

If a general user selects this button, he or she will bypass the list of users and be
brought to his or her own information. The general user will not, however, be
presented with his or her access level. The general user will then be able to modify
this content.

3.5.4 Output:
A user is either told that the account update was successful or that it failed.

Checkpoint

User Admininstrator

4 System Features:

DFD:

Zero level

Login Remove Item Admin

LogIN
Navigat User Add Item

User Location Review Order

Sing In
Make Profile
Enter
User Email Login

Enter Password

View Profile

Enter Email Enter

Password

Manage

Upload User Record

Record Admin

Upload Menu Record

Data Record
 Data

Use Case Diagram

Administrator. User Patient

Admin: Login

Add Navigat

Add Item

Remove Item

Add Login User

Change Password
Sequence Diagram

:LogIn :Data Base :User Item

<<UI>> Controller Homepag Detail

Enter login details Login details

Accepted

Incorrect Login
Not yet time

For items

Update Item

Info in database