Ieee Software Requirement Specification
Ieee Software Requirement Specification
Ieee Software Requirement Specification
SPECIFICATION
SUPERMARKET MANAGEMENT
SYSTEM
PREPARED BY
H R HARSHITHA
1
TABLE OF CONTENTS:
I. INTRODUCTION
1. Problem Definition
2. Purpose
3. Scope
4. User and Literature Survey
5. Definitions and Abbreviations
6. References
7. Overview
3.Non-functional Requirements
i. Performance Requirements
ii. Design constraints
2
IV. DATA MODEL AND DESCRIPTION
1. Data Description
i. Data objects
ii. Relationships
iii. Data Dictionary
VI. PLANNING
1) Team Structure
2) Process Model
VII. CONCLUSION
VIII. INDEX
3
I.INTRODUCTION
1. Problem Definition
4
2. Purpose
3. Scope
5
recognizing the interest objects such as rayon labels including the desired
products, products themselves, or employees of the market. The interact
with the user will be maintained by labeling the moving or non-moving
recognized interest objects in real-time. The application will also provide
information about the found products’ cost and quality. The interaction
will continue until the user quits application. Labeling objects will be
both according to the chosen list and the previously specified features of
the identified objects.
6
5. Definitions and Abbreviations SRS:
6. References
7
7. Overview
8
starting menu, which consists of a list of predefined products that the
supermarket provides. The interface allows the user to choose from the
products. After the choice, the interface changes into a real-time camera
scene, and until the user quits the application, the interface remains as a
video. This video consist of the real scene enriched by surrounding
information by labeling in terms of augmented reality. The interface quits
by the demand of the user.
Creating Lists frodam the Products -The program allows user to choose
the products that he wants and adds them to the list or delete the
products that he does not want from the list.
9
Labeling- The program can label the detected objects according to their
features like wanted, on-sale, high-quality and popular.
10
III. Specific Requirements
III.2.Functional Requirements-
11
III.2.i. User Functional Requirements
Add product Description: The user shall add the product to the list.
Assumption: The list is already defined and displayed on the screen. The
screen is on menu mode, it’s not displaying the output of the camera yet.
Delete product Description: The user shall delete the product from the
list
Assumption: The list is already defined and displayed on the screen. The
screen is on menu mode, it’s not displaying the output of the camera yet.
How: The user deletes the current product from the list.
Load List Description: The user shall load the list to the program’s
memory
Assumption: The list is already defined and displayed on the screen. The
screen is on menu mode, it’s not displaying the output of the camera yet.
Quit Description: The user shall exit from the application whenever he
wants
How: Using ESC button of the keyboard the user exits the program
12
III.2.iii. Real Time Handler Functional Requirements
Recognize Salesmen
Recognize Product
How: When the products which are already defined are decoded, the
object is recognized with 95% accuracy.
Label Product
How: After the products are recognized, their names, cost and number of
units are displayed.
Bill Products
How: The bill is calculated after all the products with their costs and
number of units are entered.
13
III.3. Non-functional Requirements
I. Performance requirements
This section will give information about the data objects, their
attributes and the complete data model.
14
1. Data Description
This section will give information about the data objects related to
this project, the relationship among them, the attributes of the data
objects and the complete data model with data objects functions
included.
I. Data objects
ii. Relationships
15
iii. Data Dictionary
Product
Sales Person
The first state is the start state in which the application starts and
invokes enter the product selection mode event. In that state, the user
may choose to add an item to the chosen product list or delete an item
from the chosen product list. If adding event is chosen, the next step will
be add item to the chosen product list state, or if removing event is
chosen, the next step will be remove item from the chosen product list
state. After those events, if the user wants, he can add another items to
the list or delete another items from the list by following the same
states. When adding and deleting choices are finished, the list will be
loaded with the load event. Each of them are labelled according to their
features, when a product is recognized, it moves into product label state,
when recognized by the salesman. When the user wants the application
to go to end state, by the quit event the end state is achieved.
VI. Planning
17
1. Team Structure
This team’s members have known each other for a long time and have
experience on division of labor since they have worked together on
several projects previously. Every member’s opinion is important to each
other and the experience and knowledge of developments tools are
nearly the same. Thus, our team’s structure is decided as “Democratic
de-centralized” structure. We plan to divide the workload equally.
2. Process Model
VII. Conclusion
18
that this application will perform is explained one by one. User and
function relationships, user roles and characteristics are modeled.
Finally, we presented the team structure and basic expected schedule
and the process model of our team.
VIII. INDEX
19