PitzaDen_SRS

8/7/2019 PitzaDen_SRS

1/16

PitzaDen Automation System

Software Requirements SpecificationsVersion 1.0

November 2010


2/16

WarningThis is a hard copy of a document maintained on electronic media. It may not be the latestversion. Kindly ascertain the latest version from the Document Master List available with the

Project Leader.


3/16

DOCUMENT RELEASE NOTICE

Document Details:

Name Version No. Description

PitzaDen_SRS1.0 SRS document for PitzaDen

Automation System

Revision Details

Action taken(Add/Del/Change)

Preceding Page No. New Page No. RevisionDescription

This document and any revised pages are subject to document control. Please keep them up-to-date using the release notices from the distributor of the document.

Approved by: Date:

Authorised by: Date:


4/16

PREFACE

Purpose of this Document

This document describes the System Requirements Specifications of the PitzaDenAutomation System. This document lays down the software requirements for the applicationthat have been captured through a detailed study of the business workflow and functions .

Intended Audience

This document is intended for use by the designers of the system, and for those who may berequired to maintain it. The document will enable them to understand all aspects of thesystem in detail. It will enable the PitzaDen Automation System to know that TCS hascaptured all the requirements.

Acronyms and Abbreviations

Abbreviation/Acronym Description

PAS PitzaDen Automation System


5/16

TABLE OF CONTENTS

1. INTRODUCTION..................................................................................................................4

1.1 BACKGROUND.......................................................................................................................41.2 SCOPE...............................................................................................................................41.3 KEY ASSUMPTIONS, DEPENDENCIES, CONSTRAINTSAND OVERRIDING PRIORITIES.................................51.4 USER CLASSESAND CHARACTERISTICS......................................................................................51.5 HARDWAREAND SOFTWARE PLATFORM......................................................................................61.6 APPLICATION SECURITY..........................................................................................................6

2. FUNCTIONAL REQUIREMENTS.........................................................................................7

2.1 ADD PIZZA..........................................................................................................................72.2 UPDATEPIZZATOPPING...........................................................................................................82.3 ADDTOPPING.......................................................................................................................92.4 VIEWMENU........................................................................................................................102.5 PLACE ORDER...................................................................................................................11

2.6 USE CASE DIAGRAM...........................................................................................................122.7 CONCEPTUAL CLASS DIAGRAM : -..........................................................................................13

3. USER INTERFACE SPECIFICATIONS..............................................................................14

3.1 MAIN MENU......................................................................................................................143.2 SCREEN LAYOUTFOR OWNER................................................................................................143.3 SCREEN LAYOUTFOR CUSTOMER...........................................................................................14

4. OTHER REQUIREMENTS..................................................................................................15

4.1 USER ACCESS CONTROLAND SECURITY..................................................................................154.2 PERFORMANCE REQUIREMENTS..............................................................................................15

Total Number of pages: 15


6/16

1. Introduction

1.1 Background

This document outlines the software requirement specification for the PitzaDen AutomationSystem. It is the outcome of the Analysis Phase during which discussions were held with theusers. The objective of this Analysis Phase was to:

Define the scope for the PitzaDen Automation System

Serve as the baseline for the design of the PitzaDen Automation System

Any changes to requirements after acceptance of this document will be through appropriateChange Management procedure, as detailed in the contract.

Both the user and designer should go through the document carefully in order to ensure that: All the user requirements which need to be supported by the system have been identified

and detailed.

The document is a clear and unambiguous statement of functionality required from thesystem for the design and development team.

The document can be used as a basis for development of the System Test data.

It is essential to identify the problems, if any, with the basic structure of the proposed systemat this stage. If these are not taken care of at this stage, it may be difficult to incorporate thedesired modifications to overcome the shortcomings at a later stage.

Client Details:PitzaDen is a newly setup pizza shop that requires an automated system to provide better

services to its customers..

Project Details:Develop an application that allow the owner to handle addition and modification of Pizza andwill allow customer to view menu and place a order for pizza.

Broad Requirements:

Adding Pizza and toppings into the system.

Updating Pizza topping.

Viewing pizza menu and placing order for pizza

1.2 ScopeThe Scope of the project is to develop an automated system for -

Adding new Pizza .

Updating toppings of pizza

Adding new Toppings.

Viewing menu of the available pizzas.

Placing order for pizza/s.

Business Users:

Owner

Customer


7/16

Geography: Local

Target System: An application to shift all the work from the manual system to an automatedsystem

Out of Scope:

Payment handling for orders placed

1.3 Key Assumptions, Dependencies, Constraints andOverriding Priorities

The successful execution of the assignment will depend on the following factors:

Assumptions1. User authentication has not been taken into consideration in the system as it is not a

major scope point. For simplicity, user will be decided using 1st level of menu.2. A pizza may/may not contain toppings.3. Pizza has Veg/non-Veg flag as an attribute based on its toppings. If any of the

toppings is non-veg, pizza will be categorized as a non veg pizza, otherwise veg.4. Type of topping (veg/ non-Veg) is decided by the Owner. It is not decided on the

basis of topping name fed into the system.5. For any selected pizza, if toppings with same name are fed multiple times for

addition or modification of pizza, the same topping will be added only once in thepizza.

6. In the menu, pizza name, type of pizza (veg/non veg) and price for all threesize(Small/Medium/Large) will be displayed

7. While modifying Topping of a pizza, the entire topping list will be replaced with thenew list provided and the type of pizza (Veg/Non veg) will be updated accordingly.

8. While adding new Pizza, topping list is not mandatory. If no topping is provided,default topping will be added and displayed as NIL and type as veg.

Dependencies

1. Involvement of the end users in signing off this SRS document.2. Availability of System Software from the client for development.3. Availability of installed hardware/System software for implementation.

Constraints

1. Payment handling is out of scope of the system.2. System is not required to provide facility to update topping details

1.4 User Classes and Characteristics

OWNERThe functionality that the owner can perform

1. AddPizza2. UpdatePizzaTopping

3. AddTopping


8/16

CUSTOMER The functionality that the customer can perform

1. View pizza menu.2. Place an order for pizza.

1.5 Hardware and Software Platform

Hardware Platform:P3 1Ghz processorRAM 128MBHard disk space 20GB

Software Platform:Windows 2000 & above with JDK 1.5.DR.JAVA for implementation

1.6 Application Security

1. User authentication has not been taken into consideration in the system .User isdecided using 1st level of menu.


9/16

2. Functional Requirements

The Functional Requirements are provided in the form of use cases that explain the importantprocesses that are going to be implemented in the system.

2.1 Add Pizza

Use Case UC1: Add Pizza

Level: User goal

Scope: PitzaDen Automation System

Primary Actor: Owner

Stakeholders and interests:Customer: Can view menu of pizza including the newly added pizza and place order as perinterest.Owner : Wants the system to accurately store the details of pizza .PitzaDen : Wants to automate addition of pizza.

Preconditions: none.

Success Guarantee: Pizza details given by the owner is recorded. Pizza Id is generated.Main Success Scenario:

1. Owner enters the pizza details into the system.2. System validates the pizza details..3. System validates for uniqueness of pizza name.4. System Prompts for confirmation of addition of pizza.5. Owner Confirms addition.6. System generates a Pizza Id for the pizza7. The pizza details are saved in the system8. The pizza is added in the menu .

Extensions:2a. Invalid input data.Sytem displays an error message.

3a. Duplicate Pizza name .System displays an error message.System displays menu.4a.Owner wants to alter the pizza details.Owner cancels addition process.System displays menu.7a. System fails to save the pizza details provided due to power outage.System displays an error message.

System displays menu.


10/16

Domain Model from UC1

2.2 UpdatePizzaTopping

Use Case UC2: Modify Toppings Of Pizza

Level: User goal



Stakeholders and interests:

Customer: Can view menu of pizza with the recently modified pizza and place order as perinterest.

Owner: Wants the system to accurately store the details of toppings of Pizza.PitzaDen: Wants to automate addition of toppings of Pizza .

Preconditions: Before modifying toppings of Pizza,that particular Pizza must exist.

Success Guarantee: Toppings of Pizza details given by the owner is recorded. Pizzatoppings modified successfully message is displayed to the user.

Main Success Scenario:

1. Owner enters the required pizza into the system.2. Owner enters the new list of toppings of pizza into the system.3. System validates the list of toppings .

4. System Prompts for confirmation of modification of toppings of pizza.5. Owner Confirms modification.6. System displays successful modification of toppings of pizza.7. The Toppings /pizza details are saved in the system8. The pizza with modified toppings is reflected in the menu .

Extensions:2a. Invalid input data.Sytem displays an error message.4a.Owner wants to change the selected toppings.Owner cancels modification process.System displays menu.

7a. System fails to save the toppings of pizza provided due to power outage.


11/16

System displays an error message.System displays menu.

2.3 AddTopping

Use Case UC3: Add Toppings

Level: User goal



Stakeholders and interests:Customer: Can view menu including the newly added topping and place order as per interest.Owner: Wants the system to accurately store toppings details .PitzaDen: Wants to automate addition of toppings.

Preconditions: none.

Success Guarantee: Topping details given by the owner is recorded. Topping Id isgenerated.Main Success Scenario:

1. Owner enters the topping details into the system.2. System validates the topping details..3.Data validation for uniqueness of topping name.4.System Prompts for confirmation of addition of topping.5. Owner Confirms addition.6.System generates a Topping Id for the topping.7.The topping details are saved in the system

Extensions:2a. Invalid input data.Sytem displays an error message.3a. Duplicate Topping name .System displays an error message.System displays menu.4a.Owner wants to alter the Topping details.Owner cancels addition process.System displays menu.7a. System fails to save the Topping details provided due to power outage.System displays an error message.System displays menu.


12/16

2.4 ViewMenu

Use Case UC4: View Menu

Level: User goal


Primary Actor: Customer


Customer: Can view menu and place order as per interest.PitzaDen: Changes/addition in Pizza/toppings can be reflected dynamically in menu .

Preconditions: None.

Success Guarantee:Menu is displayed successfully.Main Success Scenario:

1. Customer enters into the PitzaDen shop.2. Customer requests to view menu in the system.3. Menu is displayed successfully to the customer.

Extensions:3a. System fails to display the menu due to power outage.System displays an error message.System displays menu..

2.5 Place Order

Use Case UC5: Place Order

Level: User goal


Primary Actor: Customer


Customer: Can place order as per interest.PitzaDen: By knowing the demand of pizza ,more profit can be achieved.

Preconditions: None

Success Guarantee:Order is placed by the customer. Bill amount is displayed.Main Success Scenario:

1. Customer enters into the PitzaDen shop.2.Customer requests to view menu in the system.3.Menu is displayed successfully to the customer.4.)The customer enters pizza name,quantity and size as per interest.


13/16

5.)System Prompts for confirmation of the order.6.) Customer Confirms the order.7.)Bill amount is displayed to the customer.

Extensions:

5a.Customer wants to alter the Order details.Customer cancels Order process.System displays menu.7a. System fails to show the bill amount details due to power outage.System displays an error message.System displays menu.

2.6 Use Case Diagram


14/16

2.7 Conceptual Class Diagram : -


15/16

3. User Interface Specifications

The following may be the possible output screens for the application

3.1 Main Menu

1. Owner2. Customer3. Exit

Enter Choice:

3.2 Screen Layout for Owner1. Add Pizza2. Modify Pizza Topping3. Add Topping4. Back Menu5. Exit

Enter Choice:

3.3 Screen Layout for Customer

1. View Menu2. Place Order

Enter Choice:


16/16

4. Other Requirements

The other requirements may include the user access control and security requirements andperformance requirements.

4.1 User Access Control and Security

Security provisions may be made at the following levels:

Operating System Level

Each user may be given separate log-in Id and password. They may be divided into threegroups.

Application Usermay have access to Application software only. These users may not have

any access to the Operating System commands outside of Application Menus

Besides it will be possible to set or change the password interactively. Each user or group ofusers will have access to certain screens/functions of the system relevant to his area ofoperation. Each user will have to log-on to the system using the correct user name andpassword. In case of an invalid combination of these two codes, the system will display anerror message and prevent further processing.

4.2 Performance Requirements

Performance requirements specify the performance characteristics of the system likeresponse time, throughput etc.

The response time of the application will be 100 milliseconds.The throughput of the application will be about 99%.

Documents

PitzaDen_SRS