Software Requirements Specifications for FOODTRO (Food Transfer and Receive Orders) Page No.

1. Introduction

1.1 Purpose

The online food ordering service is a local food cooperative website or application for customers
to provide more interactive menu so that the ordering process could be carried out. Ordering
food online is designed for its more flexibility and performance, some website or application are
make sure that the system has enough navigation function through the picture information or
significant logo to guide customer like students follow the steps to finish the ordering food
process, apart from that it has been constructed to dealing with large number of orders
simultaneously to prevent the food overload. Basically, this online ordering project illustrate how
to supervise for good performance and better services for the University users. In this astonishing
rate of online ordering may still hide some disadvantage or problem need to handle it, such as
website costs, infrastructure cost, security and fraud, privacy laws, computer ethics, advertising
cost and customer cost. However, all current ordering applications have more or less problems
that cause different groups of people to encounter some problems when using these
applications.

1.2 Document Conventions

Main Section Titles

Font: Times New Roman Face: Bold Size: 14

Sub Section Titles

Font: Times New Roman Face: Bold Size: 12

Other text Explanations

Font: Times New Roman Face: Normal Size: 12

1.3 Intended Audience and Reading Suggestions

This Document is created for: The Instructor of the course 'E-Learning' for their review and
monitoring progress of the project. The Software Development team for their use in analysis and
requirement.
 1.4 Product Scope

The name of our product will be “E-Learning” and its function is to control the interaction
between teachers and students. This product will provide the facility of performing all the basic teaching
methodology. The targeted user groups are the remote students who will be the main benefit bearer.

1.1 References

The following references are used in the preparing this SRS

o The SRS template and sample sent by Prof. Sachin Sharma .
o Guidance from Prof. Sharaddha
o Wikipedia
o www.Google.com

2. Overall Description
2.1 Product Perspective
The Perspective of this Application is to give the opportunity to student to learning something new or something
related to their carrier easily on a Internet platform . This Product provide a simple user Interface for student
where they can View the PDF file of their required Subject and it also give facility to the teacher to upload the PDF
file of their subject so many other student can learn from them. This software can be used for developing e-
learning courses that can later be released on the Internet or delivered in some other electronic medium.

2.2 Product Functions

The following are the main functions of the "E-Learning" product.
o Reduce the manual work of student for making notes .
o It provide notes various subject which is free of cost.
o It makes easy for Teachers to provide their notes to the Students.

2.3 User Classes and Characteristics

Admin:- The admin is authorized for managing the student and faculty data , all the major service are given to the
admin like upload file, view file, update database.

Teacher:- The teacher can upload the notes file which can viewed and download by other students.

Student:- The student is the user who can only view file and download the file which given by Admin/Teacher.
2.4 Operating Environment
This software package is expected to work in the following atmosphere:-

Microsoft stack consist of :

o OS-Window
o Java, Html, java-script.
o Mysql for RDMS in tomcat apache server.

2.5 Design and Implementation Constraints

Each user must keep their password as confidential. More over the user must have individual ID for creating a
login in the E-Learning.

Only Administrator can control user addition and deletion in the system. Also this group has the access to all the
official activities.

The main challenge faced during the implementation of this project was to upload file on the server.

2.6 User Documentation

o This package will come with user's manual as a guide to its interface activities.
o The details of
 Analysis
 Design
 Test Cases of this software package will be delivered along with this software.

3. External Interface Requirements

3.1 User Interfaces
The set of User Interface consists of:

o To Login into respective accounts by admin/teachers.

o To Add and modify files by admin/faculty.
o To view the files by student/admin/teacher.

3.2 Hardware Interfaces

Server Side:-
 o Operating System: Windows .
o Processor :Pentium 3.0GHz or higher.
o RAM: 256Mb or more.
o Hard Drive: 10GB or more.

Client Side:-

o Operating System: Windows

o Processor: Pentium III or 2.0GHz or higher.
o RAM: 256 Mb or more.

3.3 Software Interfaces

o Database: SQL Server .
o Application : JSP (Java Server Pages)
o Web Server :Tomcat Apache (Apache is a powerful Web server that provides a highly reliable, manageable
, and scalable Web application infrastructure)

3.4 Communications Interfaces

The Customer must connect to the Internet to access the Website:

o Dialup Modem of 52 kbps.

o Broadband Internet.
o Dialup or Broadband Connection with a Internet Provider.

4. System Features
This application provide various features which will reduce the mess and complexity of managing the whole notes
manually . This application provide a interface where a student can view and download the notes material
uploaded by admin/teachers.

4.1 Home Interface:

4.1.1 Description and Priority

This provide a interface where any student can view or download the notes which are uploaded by
the Admin/Teachers.
.1.2 Stimulus/Response Sequences
 S no. Stimulus from user Response from Application

1 The user can use about option . The Application will display the short
information about the organization

2 The user can select the course option The Application will display the list of course
from page drop down options. from which the user can select the required
course.

3 The user can select the course detailed The Application will display course detail
option from page drop down options. from which the user can select the required
course.

4 The user can click the signup\login The Application will display login / signup
option. page.

5 The user can click the contact option . The Application will display the contact
details of the organization.

6 The user can click the home option. The Application will display home page.

4.1.3 Functional Requirements

REQ-1: The user shall be able to view the contact and about of the organization.
REQ-2: The user shall be able to get to the login/signup page by clicking the login/signup
option .

4.2 Login/Signup :
4.2.1 Description and Priority
This provide a interface where any Teacher/Admin can login and Signup.

4.2.2 Stimulus/Response Sequences

S no. Stimulus from user Response from Application

1 The user can select the login option. The response will display the login from.

2 The user can select the signup option. The response will display the register from.
3 User can enter the login and password The Application will store the login and
in login form. password in a temporary text filed.

4 The user can click the signin button. The application will validate the user id and
password if the password is correct then it will
 display the user home page and if the id or
password is incorrect then it will display the
error message.

4 The user can click the signin button.
The application will validate the user id and
password if the password is correct then it will
display the user home page and if the id or
password is incorrect then it will display the
error message.

5 The user can enter the user details like The application will store the details in the
name, email id, password etc. database and display signup successfully and
send the user from the login page.

4.2.3 Functional Requirements

REQ-1: The user shall be able to fill the login/signup form .

REQ-2: The application should be able to store the details in the database .

4.3 Add and Remove notes:

4.3.1 Description and Priority:

This provide a facility where any Teacher/Admin can upload the notes material for the students.
4.3.2 Stimulus/Response Sequences

S no. Stimulus from the user Response from Application

1 The user can select the add notes option. The application will display the browsing notes
option.

2 The user can select the file which they want The Application will upload the selected file in the
to upload portal if the file is validate and display Upload
successful otherwise it will display the error message.

3 The use can select the remove notes option. The application will display the list of notes which user
can delete.

4 The user can select the notes file which they The application will remove the notes file from the
want to delete and click remove button records and display delete successful otherwise if
their is any problem then it will display the error.
 4.3.3 Functional Requirement:

REQ1:The user should be able to select the remove or add notes option.

REQ2: The user should be able to add or delete the required file.

4.4 View Notes

4.4.1 Description and Priority: This provide the user a facility to view the notes uploaded by
Admin/Faculty.
4.4.2 Stimulus and Response Sequence:

S no. Stimulus from the user Response from the Application

1 The user can select the view notes The application will display the list of
option. subject's notes which the user is authorized to
view.

2 The user select the subject whose The Application will display the notes file is
notes they want to see. the selected notes ia available otherwise it will
display error message 'File not found'

4.4.3 Functional Requirement:

REQ1:The user shall be able to select the required notes.

REQ2: The Application should display the notes of the selected subject.

4.5 Logout

4.5.1 Description and Priority:

The user shall be able to Logout.

4.5.2 Stimulus/Response Sequences Stimulus:

 S.no. Stimulus from the user Response from Application

1 User click the Logout Button User is logged out and index page is displayed.

4.5.3 Functional Requirements

REQ-1: The user shall be able to logout from the System.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
This software should be able to handle the following tasks:

a) At least 20 users can log in on an average of four hours a day for five days a week.
b) At least 100 students can log into that account for 3 hours for 5 days of the week.
c) It should be able to handle the MYSQL database of 100 teachers and 1500 student.

5.2 Safety Requirements

This application will ease the process of notes sharing on a big level efficiently ,it also decrease the manual work
of the teacher by making the notes file in the form of PDF.

5.3 Security Requirements

This software will:

a) Authenticate each user, who can upload notes.

b) When the user performs any action, authorize him/her to perform the action allowed for the user and
displays an error message if found to be unauthorized.

6. Other Requirements
All the other requirements are already mention in this doccumnet.
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may
wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms
specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition
diagrams, or entity-relationship diagrams.>

Appendix C: To Be Determined List

<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked
to closure.>