Professional Documents
Culture Documents
SRS For Online Pizza Store PDF
SRS For Online Pizza Store PDF
Chapter 1:
Study and Prepare documentation for different Software Process
Models
1. Waterfall model
2. Incremental model
3. RAD model
4. Prototype model
5. Spiral model
1. Waterfall model
The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each
phase must be completed fully before the next phase can begin. At the end of each phase, a
review takes place to determine if the project is on the right path and whether or not to continue
or discard the project. In waterfall model phases do not overlap.
Diagram of Waterfall-model:
Requirement Analysis
Design
System Testing
Maintanance
Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought out in the concept stage.
No working software is produced until late during the life cycle.
High amounts of risk and uncertainty.
Not a good model for complex and object-oriented projects.
Poor model for long and ongoing projects.
Not suitable for the projects where requirements are at a moderate to high risk of
changing.
2. Incremental model
In incremental model the whole requirement is divided into various builds. Multiple
development cycles take place here, making the life cycle a multi-waterfall cycle. Cycles are
divided up into smaller, more easily managed modules. Each module passes through the
requirements, design, implementation and testing phases. A working version of software is
produced during the first module, so you have working software early on during the software
life cycle. Each subsequent release of the module adds function to the previous release. The
process continues till the complete system is achieved.
Generates working software quickly and early during the software life cycle.
More flexible, less costly to change scope and requirements.
Easier to test and debug during a smaller iteration.
Customer can respond to each built.
Lowers initial delivery cost.
Easier to manage risk because risky pieces are identified and handled during it’d
iteration.
3. RAD model
Diagram of RAD-Model:
Business modeling: The information flow is identified between various business functions.
Data modeling: Information gathered from business modeling is used to define data objects
that are needed for the business.
Process modeling: Data objects defined in data modeling are converted to achieve the business
information flow to achieve some specific business objective. Description are identified and
created for CRUD of data objects.
Application generation: Automated tools are used to convert process models into code and the
actual system.
Testing and turnover: Test new components and all the interfaces.
RAD should be used when there is a need to create a system that can be modularized in
2-3 months of time.
It should be used if there’s high availability of designers for modeling and the budget is
high enough to afford their cost along with the cost of automated code generating tools.
RAD SDLC model should be chosen only if resources with high business knowledge are
available and there is a need to produce the system in a short span of time (2-3 months).
4. Prototype model
The basic idea here is that instead of freezing the requirements before a design or coding can
proceed, a throwaway prototype is built to understand the requirements. This prototype is
developed based on the currently known requirements. By using this prototype, the client can
get an “actual feel” of the system, since the interactions with prototype can enable the client to
better understand the requirements of the desired system. Prototyping is an attractive idea for
complicated and large systems for which there is no manual process or existing system to help
determining the requirements. The prototype are usually not complete systems and many of the
details are not built in the prototype. The goal is to provide a system with overall functionality.
Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model. It might take a while for a system to be
built that allows ease of use and needs minimal training for the end user.
Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.
5. Spiral model
The spiral model is similar to the incremental model, with more emphasis placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and
Evaluation. A software project repeatedly passes through these phases in iterations (called
Spirals in this model). The baseline spiral, starting in the planning phase, requirements are
gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral.
Requirements are gathered during the planning phase. In the risk analysis phase, a process is
undertaken to identify risk and alternate solutions. A prototype is produced at the end of the
risk analysis phase. Software is produced in the engineering phase, along with testing at the
end of the phase. The evaluation phase allows the customer to evaluate the output of the
project to date before the project continues to the next spiral.
Chapter 2:
Developing SRS
For
Mom’s Pizza Store
2.1 Introduction
2.1.1 Purpose
This document gives detailed functional and non-functional requirements for Mom’s Pizza
Store – an online pizza ordering system. The purpose of this document is that the requirements
mentioned in it should be utilized by software developer to implement the system.
2.1.2 Scope
This system allows people to order their favorite delicious pizzas online from Mom’s Pizza
Store. With the help of this system customer should able to order their favorite pizza’s from
Mom’s Pizza Store from anywhere. The information about store and every pizza is also
provided.
2.1.3 Overview
This system provide easy solution to the customer to order the item he/she wants directly
through internet without visiting the store.
This system replaces old Pizza Stores where lots of crowd of people is there by online Pizza
Store. Moreover conventional Pizza Store requires more and big manpower compare to this
system. This system is developed with new geo-location like features in HTML 5 for more
customer comfort.
2.3 Requirements
This section describes different types of users of the system in 3.3.1. In the following paragraph
3.3.2, the functional requirements for each type of user are listed. 3.3.3 Lists the non-functional
requirements of the system.
Users
Three types of users should be able to use the system: customer, employee and administrator.
Customers are users who visit the website and can create orders by customizing pizzas,
selecting products and entering customer details. Employees are the group of users that work
with the ordering system on a daily basis. Employees will have their own accounts to log on to.
They are the ones responsible for processing orders. Since Customer users do not need a log in,
employees who process telephone orders can use the system as a Customer and enter the
telephone order directly into the system as they take the order from the calling customer.
The administrator, or super user, has the ultimate control of the system, he can add, change or
delete ingredients and products, as well as add, change, or delete employee accounts.
1 Customers
1.1 The user must be able to create a new order.
1.2 The user must be able to customize a pizza by:
1.2.1 The user must be able to view a list of available ingredients.
1.2.2 The user must be able to add an ingredient to a custom pizza
1.2.3 The user must be able to remove an ingredient from a custom pizza
1.2.4 The user must be able to get graphical feedback from selecting ingredients. A photo of a
pizza will contain the newly selected ingredient combined with previous selected ingredients.
1.3 The user must be able to add a custom pizza to an order.
1.4 The user must be able to view a list of available non-pizza products.
1.5 The user must be able to add non-pizza products to an order.
1.6 The user must be able to see a list of custom pizzas and non-pizza products that are added to
the order.
1.7 The user must be able to change the amount of a custom pizza.
1.8 The user must be able to change the amount of a non-pizza product.
1.9 The user must be able to delete a custom pizza from an order.
1.10 The user must be able to delete a non-pizza product from an order.
1.11 The user must be able to see the total price of an order.
1.12 The user must be able to choose a delivery date and time that is up to two weeks ahead.
1.13 The user must be able to add the name and address of the customer.
1.14 The user must be able to clear the current order to start a new one.
1.15 The user must be able to confirm the order.
2 Employees
2.1 The employee must be able to log in and out.
2.2 The employee must be able to view a list of available orders and their custom pizzas.
2.3 The employee must be able to mark orders as “prepared”.
2.4 The employee must be able to mark order as “delivered”
2.5 The employee must be able to mark order as “failure to deliver”
2.6 Only users with respective rights (employee) must be able to use all these
“Employees” features.
L. C. Institute of Technology, Bhandu Page 19
Mom’s Pizza Store
3 Administrators
3.1 The administrator must be able to log in and out.
3.2 The administrator must be able to add/delete/edit orders.
3.3 The administrator must be able to add/delete/edit ingredients.
3.4 The administrator must be able to add/delete/edit non-pizza products.
3.5 The administrator must be able to add/delete/edit other users.
3.6 The administrator must be able to view an order log.
3.7 Only users with respective rights (administrators) must be able to use all these
“Administrators” features.
The user interface must be highly interactive so that all users may be able to operate the system
as easily and fluently. GUI would be used for creating home page with navigation bar and other
pages for respective categories.
Internet connection
The PHP and MYSQL must be installed
Any browser
2.7.2 Reliability
The system should be highly reliable and it should generate all the updated information in
correct order.
2.7.3 Availability
2.7.4 Maintainability
The system should be maintainable in such a manner that if any new requirement occurs then it
should be easily incorporated in an individual module.
2.7.5 Reusability
Chapter 3:
Developing Use case diagram
For
Mom’s Pizza Store
Use-Case Diagram
Chapter 4:
Developing Data Dictionary
For
Mom’s Pizza Store
Data Dictionary:
Table – 1 for Mom’s Store information
tblStore
Sr Field Name Data type Size Is Null Constrain Default Description
no value
1 strid int - No - It indicates id of store
2 Strname varchar 50 No - Name of the Store
3 stated Int - - Foreign key Name of city, it belong to which state.
6 Createddate date - No - It is used to store date in which it
created
Chapter 5:
Developing Data Flow Diagram
For
Mom’s Pizza Store
DFD level - 0
DFD level-1
Chapter 6:
Developing Class diagram
For
Mom’s Pizza Store
Class diagram
Chapter 7:
Developing Sequence Diagram
For
Mom’s Pizza Store
Sequence Diagram
Chapter 8:
Developing E-R diagram
For
Mom’s Pizza Store
E-R diagram
Chapter 9:
Developing Activity diagram
For
Mom’s Pizza Store
Activity Diagram 1
Activity Diagram 2
Activity Diagram 3
Activity Diagram 4
Chapter 10:
Prepare Time Line Chart
For
Mom’s Pizza Store
SRS Phases
35
30
25
20
SRS Phases
15
10
0
Requirement Requirement Analysis Design Coding
Gathering
Timeline Diagram
4. Screen Shots
5. Conclusion
Mom’s Pizza Store will make great impact on our conventional stores with
lots of new features and comfort. As it’s an online store customer is going to love it
because it’s going to save your lots of time in this daily fast life. It’s geo-location
feature is eye-catching for all the customers and will help a lot to customers. It’s
easy to use navigation and simple though beautiful GUI are going to be praised by
all for sure. It’s one of the State-of –the art site for new Pizza Stores.
6. Reference’s
1. http://en.wikipedia.org/wiki/SDLC
2. http://en.wikipedia.org/wiki/Rapid_application_development
3. http://www.technotrice.com/rad-model-software-engineering/
4. http://www.studymode.com/essays/Srs-Of-Online-Pizza-Ordering-
1389543.html
5. http://creately.com/diagram/example/hmqrqsik1/Perfect+Pizza+-+Context-
Level+Data+Flow+Diagram
6. http://creately.com/diagram-
community/all?pg=5&term=ER%20diagram%20for%20online%20pizza%20
ordering
7. http://creately.com/diagram-
community/all?term=activity%2520diagram%2520for%2520online%2520piz
za%2520ordering