Fsp Final Srs

A Software Requirement SpecificationOn

Food Safety Portal

Swami Keshvanand Institute of Technology, Management &Gramothan, Jaipur

In the partial fulfillment of Bachelor of technology in computer science and Engineering under Rajasthan Technical

University.

Submitted to: Submitted by:Prof. Dr. C M Choudhary Surbhi Gupta 09ESKCS121

(HOD CS) Swastik Pareek 09ESKCS123

Mr. Deepak Garg Somya Sharma 09ESKCS114

(Lecturer CS) Surbhi Baghla 09ESKCS120

Ms. Nidhi Jain

(Lecturer CS,Mentor)

Food Safety Portal Version<1.0>Software Requirement Specification Date: 15/10/2012Team Name S4

Table of contents

1. Introduction

1.1 Methodology…………………………………………………………………………………………………………………….3

1.2 Purpose…………………………………………………………………………………………………………………………….4

1.3 Scope…………………………………………………………………………..…………………………………………………. 4

1.4 Definitions, Acronyms and Abbreviations…………………………………………………………………………. 5

1.5 Tools Used ………………………………………………………………………………………………………………………. 6

1.6 References ………………………………………………………………………………………………………………………. 7

1.7 Technologies to be used …………………………………………………………………………………………………. 7

1.8 Overview ………………………………………………………………………………………………………………………... 7

2. Overall Description

2.1 Product Perspective ……………………………………………………………………………………………………….. 8

2.2 Software Interface ………………………………………………………………………………………………………….. 8

2.3 Hardware Interface ………………………………………………………………………………………………………… 9

2.4 Communication Interface ……………………………………………………………………………………………….. 10

2.5 Constraints ……………………………………………………………………………………………………………………… 10

2.6 Data flow Diagram………………………………………………………………………………………………………….. 11

2.7 E-R Diagram …………………………………………………………………………………………………………………….. 13

2.8 Database Design…………………………………………………………………………………………………………….. 14

2.9Class Diagram ………………………………………………………………………………………………………………… 16

2.10Use-Case Model …………………………………………………………………………………………………………….. 18

2.11 Architecture Design……………………………………………………………………………………………………….. 20

3. Specific Requirement

3.1 Activity Diagrams…………………………………………………………………………………………………………….. 21

3.2Sequence Diagrams………………………………………………………………………………………………………….. 25

4. Supporting Information…………………………………………………………………………………………………….. 28

Page 2S4/SKIT/CS-B(G2)


1. Introduction

1.1 Methodology

Rational Unified ProcessThe Rational Unified Process brings together elements from all of the generic process models, supportsiteration and illustrates good practice in specification and design. The RUP is normally described from three perspectives:

A dynamic perspective that shows the phases of the model over time.A static perspective that shows the process activities that are enacted.A practice perspective that suggests good practices to be used during the process.

Fig 1.1:Phases of RUP

The different phases in RUP are :-



InceptionThe goal of the inception phase is to establish a business case for the system. Identifying all externalentities that will interact with the system and defining these interaction. This information is used toassess the contribution of system to business.

ElaborationThe goals of the elaboration phase are to develop an understanding of the problem domain, establishan architectural framework, develop project plan and identify key project risks.

ConstructionThis phase is concerned with system design, programming and testing. Parts of the system are developedin parallel and integrated during this phase.

TransitionThis is the final phase of RUP and is concerned with moving the system from the development communityto the user community and making it work in real environment.

1.2 Purpose

Food Safety Portalis a web application which provides information related to restaurants of a city, market certifications,quality of food, dining guide, food handling, local diet/delicacies to everyone at their doorstep.The users living in the city or visitors of that city can connect through internet can get information about restaurants of that city, food related illness and restaurant guide.City employees can easily update an information and and others users also can submit feedback, suggestion for improvement on the web-site.

1.3 Scope There are three basic users - city residents, visitors and city employees. All users have their own profiles in FSP. City residents and visitors can search for restaurants and make online booking. They can also submit

feedback on any restaurant. City employees can view record of their customers (regular customers, weekend customer or new

customers). Restaurant guide views and manages the booking, performs day open and close activitiesand

calculates his commission. He also sends reports to admin. Admin has the authority to add/delete users, grant permission to city employees and restaurant

guide to generate and view. He also views the complainsand feedback of users and takes necessaryactions.

1.4 Definitions, Acronyms and AbbreviationsPage 4

S4/SKIT/CS-B(G2)


FSPFood Safety Portal:It’s a web application that provides online food related services

for people.Admin

Administrator:He has the authority to add/delete users, grant permission to city employees and restaurant guide.

RGRestaurantGuide:He manages bookings of restaurants.

WASCEWebSphere Application Server Community Edition: It is an application server that run and supports J2EE and web service applications.

DB2Database_2: A database management system that provides a flexible and efficient databaseplatform to maintain records of restaurants, customers, admin.

JSPJava Server Pages: It is used to create dynamic web content.

J2EEJava 2 Enterprise Edition: A programming platform which is a part of java platform fordeveloping and running distributed java.

UMLUnified Modeling Languageis a standard language for writing software blueprints. The UML may be used to visualize, specify, construct and document.

XMLExtensible Markup Languageis a text based format that let developers describe, deliverand exchange structured databetween a range of applications to client for display and manipulation.

HTTPHypertext Transfer Protocol: It’s a service protocol.

RADRational Application Developeris a development tool that helps to design web pagesand also helps to design the diagrams like ER, Database schema diagrams and to generate DDL.



1.5 Tools Used

Application architecture – JAVA, J2EEJAVAJava is an object-oriented programming language developed by Sun Microsystems a company best known for its high end UNIX workstations. Java language was designed to be small, simple, and portable across platforms, operating systems, both at the source and at the binary level, which means that Java programs (applet and application) can run on any machine that has the Java virtualmachine (JVM) installed.

J2EEJava Platform, Enterprise EditionorJava EEis a widely used platform for server programmingin the Java programming language. The Java platform (Enterprise Edition) differs from the JavaStandard Edition Platform (Java SE) in that it adds libraries which provide functionality to deployfault-tolerant, distributed, multi-tier Java software, based largely on modular components runningon an application server.

Web server – WASCEWebSphere Application Server Community Edition(from now on WASCE) is a free, certifiedJava EE 5 server for building and managing Java applications. It is IBM's supported distribution ofApache Geronimo that uses Tomcat for servlet container and Axis 2 for web services. Over 15WASCE developers are committers in the Apache Geronimo project.

Development tool –RADIBM Rational Application Developer for WebSphere Software (RAD) is an integrated development environment (IDE), made by IBM's RationalSoftware division, for visually designing, constructing,testing, and deploying Web services, portals, and Java (J2EE) applications.

Database platform – DB2DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications and supports the J2EE and web services standards.

Design tool – Rational Software ModelerIBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational Software Modeleris built on the Eclipse open-source software framework and includes capabilities focused on visualmodeling and model-driven development (MDD) with the UML for creating resilient, thought-outapplications and web services.



1.6 References Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh. Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books. IBM TGMC Sample Synopsis. IBM – www.ibm.in/developerworks . Java - www.sun.com Wikipedia - www.wikipedia.com Database Management Systems – Navathe Complete Reference - J2EE - Keogh.

1.7 Technologies to be used DB2: Relational Database Management System. RAD: Rational Application Developer. WASCE: Websphere Application Server Community Edition. Rational Software Modeler.

1.8 Overview

Existing System: Registration for users Discussion forum

Drawbacks: Remote area users and people who doesn't have knowledge of internet cannot use

the system.Proposed System:

Registration for city residents, visitors, city employee - help the users who doesn't have knowledge of internet to use the system.

Our Plan: Registration for users. Online maintenance of restaurant record. Online bookingfacility. Usersreviews and ratings for restaurants.

2. Overall DescriptionPage 7

S4/SKIT/CS-B(G2)


2.1 Product Perspective

Fig 2.1 Product Perspective

2.2 Software Interface

Client on InternetWeb Browser, Operating System (any)Client on IntranetWeb Browser, Operating System (any)Web ServerWASCE, Operating System (any)Data Base ServerDB2, Operating System (any)Development EndRAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),WebSphere(Web Server)



2.3 Hardware InterfaceMinimum Requirements:Client SideProcessor RAM Disk Space

Client SideProcessor RAM Disk Space

Internet Explorer - 6 Intel Pentium III or AMD -800 MHz

128 MB 100 MB

Server SideProcessor RAM Disk Space

RAD Intel Pentium III or AMD -800 MHz

1 GB 3.5 GB

DB2 - 9.5 256 MB 500 MB (Excluding DataSize)

Recommended Requirements:C

Client SideProcessor RAM Disk Space

Internet Explorer - 6 All Intel or AMD - 1 GHZ 256 MB 100 MB

Server SideRAD All Intel or AMD - 2 GHZ 2 GB 3.5 GB

DB2 - 9.5 512 MB 500 MB(Excluding DataSize)

2.4 Communication InterfacePage 9

S4/SKIT/CS-B(G2)


Client (customer) on Internet will be using HTTP/HTTPS protocol. Client (system user) on Internet will be using HTTP/HTTPS protocol.

2.5 Constraints Login and password is used for the identification of users. GUI is only in English. Limited to HTTP/HTTPS. This system is working for single server.

2.6 Data Flow Diagram



0-Level DFD

In 0 level data flow data diagram user will request for registration or login (if already registered). Non registered users can view city map and templates and also search for restaurant andrestaurant guide.

1-Level DFD


user

Food Safety Portal

do registration /login

Validate user

View map

View templates

Search restaurant

Admin

Application form

Confirmation


2.7E-R Diagram


R_id E_id

User

Registration Process admin

Getting Information

Submit form

Registration confirmation

Registration rejection

User Record

Check User Status

Application form

confirmation

rejection

View templates

Search restaurant

View city map

Restaurant Guide

Contacts

Do booking

Submit feedback



City resident

id

name

password

Contact no

DOB

gender

occupation

City employeehas updat

booking

Restaurantguideadmin restaurantapprove has

approves

manages

feedback

submit

G_id

G_name

Res_idRes_name

address

B_id

date

timeF_id

content

name

address

DOB

password

contact

Admin_id


2.8 Database Design

Tables

User Table

Serial No Field name Data type Constraint1 User Id Varchar Primary key2 User name varchar3 Password Varchar4 Security Question Varchar5 Secqurity Answer Varchar6 Email id Varchar7 Contact no Numeric8 Address Varchar9 City Varchar10 DOB Date

Admin Table

Serial No Field name Data type Constraint1 Admin Id Varchar Primary key2 Admin name Varchar3 Password Varchar4 Security Question Varchar5 Secqurity Answer Varchar6 Email id Varchar7 Contact no Numeric8 Address Varchar9 City Varchar10 DOB Date

Restaurant Table

Serial No Field name Data type Constraint1 Rest Id Varchar Primary key2 Rest name Varchar3 Contact no numeric4 Address Varchar5 City Varchar



Restaurant Guide Table

Serial No Field name Data type Constraint1 Guide Id Varchar Primary key2 Guide name Varchar3 Password Varchar4 Security Question Varchar5 Secqurity Answer Varchar6 Email id Varchar7 Contact no numeric8 Address Varchar9 City Varchar10 DOB date

Template Table

Serial no Field name Data type Constraint1 Name Varchar Primary key2 Type Varchar3 Size Varchar4 Location Varchar

Booking Table

Serial No Field name Data type Constraint1 Booking Id Varchar Primary key2 User id varchar3 guide id Varchar4 Res id Varchar5 guide rates numeric6 Date Date7 Time Date



2.8 Class Diagram

In Class Diagram each class defines the attributes and methods. Each class is connected to other class according to the functionality.

C



City ResidentClass: It has attributes like user id, user name, password,email-id,contact no,address,city and date of birth. The class city resident is conncted to restaurant class,template class and feedback class for booking a restaurant,to use templates and to give feedback about the restaurant and restaurant guide.

Restaurant Class: Attributes of reataurant class are id, name, address, contact no, and password. The functions it performs are booking(), review() and update(). It is connected to city resident and restaurant guide with M:M cardinality.

Restaurant Guide Class: Its attributes are id, name, contact no, email-id , address, password and rate. It has functionality of set up a deal between user and restaurant.

Admin Class: Admin is administrator who can look at all the activities which are goinng on. Its attributes are id, name, password, email-id, contact no, address, city. A feedback form is submitted to the admin and according to the feedback he can rate the restaurants and restaurant guide.

Template Class: Template class has attribute like type of that template, file name, file size. This class is connected to the users. Users can view the template which are based on food safety.

Feedback Class: Feedback class has attribute id, date, subject, content and name of the user who submitted the feedback. It is associated to the user with M:1 cardinality that means one user can submit more then one feedback.

Visitor Class: Visitor can visit the website without logging in. They can use the templates and can also see the city map for finind the location of restaurants.



2.9Use Case Diagram



DESCRIPTIONSign In :The user has to Sign In in order to .

View profile:Every registered user has his/her own profile containing personal details.

Update profile:The user has the option to update his/her own profile.

Select Restaurant or Restaurant Guide :The user can select restaurant based on various criteria.

Do Booking:The user can request for booking to a particular restaurant.

Interact with restaurant guide:The user can interact with guide .

Feedback :The user can submit feedback on restaurant or restaurant guide to admin.

Search :

The user can search for a particular item in website by entering the keyword.



2.10Architecture Diagram


Registration UI

Login UILogin UI

Registration UI

Search UI Search UI

Feedback UIFeedback UI

Booking UI Booking UI

Login

Restaurant guide/ user/Reataurant

Feedback

Booking


3. Specific Requirement

3.1 Activity Diagrams

User Registration Activity:

Initially user is made to fill all mandatory fields filled in registration form. Once the user clicks submit,the username is verified. If the username is already present, then the user is again taken back,so that he can change the username. If the username is not present then it checks for password andremaining mandatory fields. If any of the mandatory field is left empty or filled incorrect, then theuser is informed to enter the correct values. Once all these verifications are succeeded, then the registration is done.Login Activity:



User is made to enter the username and password, if he is signing in through his id then he has to be entered,after that entered values are verified. If it is a valid username and password, then the user is logged in, orelse they are asked to re enter the correct values.

Feedback Activity:Page 22

S4/SKIT/CS-B(G2)


After submitting the feedback form the admin views this feedback and analyse it. According to the feedback submitted by users he updates the rates of restaurant and restaurant guide. Rates of a restaurant or guide makes it easy to choose a restaurant and guide.

Book Deal Activity



After the user logged in if the user wants to do online booking then either he can select a restaurant guide or directly contact to the restaurant. Now the deal will be confirmed by the restaurant and the report will be displayed to the user.



3.2 Sequence Diagram:

Validation Sequence Diagram:

When a user enter user name and password for login then these values are forwarded to the database for validation. If the validation is successfull it will display user profile and if the validation is failed it will display a error page indicating that user name or password is incorrect.



Booking sequence diagram:

User search for a restaurant or restaurant guide, these search parameters are forwarded to the database and searched in the database for related keywords. Then the search result is displayed to the user.

After selecting a restaurant user request for booking with date and time. Restaurant approves or reject the user request and display the result to the user.



Feedback Sequence Diagram

User enters feedback then submit it. After clicking on submit button this feedback is stored in the database. Noe this feedback is visible to the users , Restaurant guide and admin. Admin can use the feedback to rates the restaurant and guide.



Supporting Information

ACAbbreviations · 5Client on Internet · 8Acronyms · 5 Client on Intranet · 8 Acronyms · 5 Communication · 9Administrator · 16 Constraints · 11AJAX · 7, 13 Construction · 9Analysis · 3 Design · 14D EData Base · 15 Elaboration · 4DB2 ·6 ER Diagram · 13Definitions ·6 Existing System · 7Development End · 8Drawbacks · 7H IHardware · 9 Inception · 4HTML · 8 Interface · 9,10,11HTTP · 5 Introduction · 4J MJ2EE · 6, 13 Methodology.3Java · 6JSP · 5,6O POperating System · 6, 8 Product Perspective · 8Our Plan· 7 Proposed System ·7Overall description· 8 Purpose · 4Overview ·7R SRestaurant.5 Scope · 4Restaurant Guide.5 Sequence · 24RAD · 5 Software · 8References · 7Rational Unified Process · 3T UTransition· 4 User Technologies · 6,7 UML · 5

Use-case · 18,19WWASCE · 6


Date post:	21-May-2017
Category:	Documents
Upload:	rajat-gupta
View:	240 times
Download:	0 times

Fsp Final Srs

Documents