Software Design Specification

The Software Design Specification Outline

1. Introduction
1.1 Purpose of this document
This software design specification is made with the purpose of outlining the software
architecture and design of the foodready website in detail. The document will provide
developers an insight in meeting client’s needs efficiently and effectively. Moreover the
document facilitates communication and understanding of the website by providing
several views of the website design. The document will provide a framework to the
programmers through describing the high level components and architecture and
interfaces
1.2 Scope of the development project
Food ready can be used by thousands of users at the same time. Main
purpose of the application is to grow businesses of restaurants and provide
quality food to the customer at their doorstep. Restaurants can make their
profile and add dishes available in their menu and customers can simply
explore the restaurants and order available dishes.

1.3 Definitions, acronyms, and abbreviations Acronyms:

1) SRS: Software Requirements Specification
2) SDS: Software Design Specification
3) Software Testing Service Abbreviations 1) Number: No.
2) Document: doc

1.4 References www.foodpanda.com

1.5 Overview of document
4.1 User Login/Signup/Forgot Password 4.1.1 Description and Priority It is of high
priority since user would register and only then can they perform a bidding on to a
property. This would also store all the records and activities the customer has made and
can resume where they had left off. 4.1.2 Stimulus/Response Sequences The user would
enter his/her credentials and press login, the system will cross check the credentials from
the backend database. If the credentials are correct then the system will redirect the
customer to user dashboard. If the credentials are wrong then Forget Password feature
would recover the password for the customer. 4.1.3 Functional Requirements REQ1 -
user interface requiring the credentials of the user. REQ2 - Cross checking the credentials
at the backend from the database REQ3 redirecting to user dashboard where the relevant
information of the said user is already loaded from the database.

2. System architecture description

This section provides an overview and rationale for the program's data and architectural design
decisions.

2.1 Section Overview

This section describes the architectural design of the PIA website. The high level
components and their interactions, suitable architectural patterns and design decisions
applied to the whole website. The next content of this section is General Constraints,
which contains the requirements about the section, which includes hardware and software
environments, interface requirements, external data representations, performance
requirements, network requirements, etc. The Data Design section describes the structure
of any databases, external files, and internal data structures and the Program Structure
describes the architectural model chosen and the pictorial representation of major
components. In the last section alternatives are considered, it's justified if I have used any
alternative model.

2.2 General Constraints

● An internet connection is required
● The HTTP protocol will be used to facilitate communications between the client
and server. The website supports Google Chrome and Mozilla Firefox and all
web browsers.
● The software and hardware requirements for the development of this project are
not many and are already available as free as open source.
● The work for the project is done with the current equipment and existing software
technology.