Uzma Nisar
$2/hr
Virtual Assistant
- Reply rate:
- 70.83%
- Availability:
- Full-time (40 hrs/wk)
- Age:
- 29 years old
- Location:
- Islamabad, Islamabad Capital Territory, Pakistan
- Experience:
- 6 years
FYP
Software Design Description
For
Bazaar Buddy
Reviving Traditional Shopping
Submitted by
Muzna Khan, GCPKI00531
Nida Fatima, GCPKI00611
Uzma Nisar, GCPKI00454
Supervised by
Engr. Iram Hina
Department of Software Engineering, Grafton College, Islamabad.
20th December 2019
Software Design Description for Bazaar Buddy
Page ii
Table of Contents
Index of Tables ............................................................................................................................. iv
Revision History .............................................................................................................................v
1. Introduction ..............................................................................................................................1
1.1
1.2
Purpose ........................................................................................................................................ 1
Scope ........................................................................................................................................... 1
2. Design methodology and software process model .................................................................2
3. System overview .......................................................................................................................3
3.1
3.2
Architectural design..................................................................................................................... 3
Process flow/Representation........................................................................................................ 7
4. Design models ........................................................................................................................-
Class Diagrams .......................................................................................................................... 13
Sequence Diagrams ................................................................................................................... 16
State Transition Diagram ........................................................................................................... 21
Data Flow Diagram (level 1) ..................................................................................................... 26
5. Data design .............................................................................................................................28
5.1
Data dictionary .......................................................................................................................... 28
6. Algorithm & Implementation ..............................................................................................-
Login: ........................................................................................................................................ 29
Admin ........................................................................................................................................ 30
Salesperson: ............................................................................................................................... 32
Public User: ............................................................................................................................... 34
7. Software requirements traceability matrix .........................................................................37
8. Human interface design .........................................................................................................39
8.1
Screen images ............................................................................................................................ 39
8.2 Screen objects and actions ............................................................................................................... 43
Admin can also keep record of his employees...............................................................................44
9. Appendix I ..............................................................................................................................44
Software Design Description for Bazaar Buddy
Page iii
Table of Figures
Figure 1 Waterfall Model................................................................................................................ 2
Figure 2 3-tier Architecture for BB ................................................................................................ 3
Figure 3 DFD level 0 ...................................................................................................................... 4
Figure 4 Flow diagram .................................................................................................................... 5
Figure 5 ERD .................................................................................................................................. 6
Figure 6 Login Activity Diagram ................................................................................................... 7
Figure 7 Inventory Management Activity Diagram........................................................................ 8
Figure 8 Employee Management Activity Diagram ....................................................................... 9
Figure 9 Shopping list Activity Diagram ...................................................................................... 10
Figure 10 Search Shop Activity Diagram ..................................................................................... 11
Figure 11 Search Product Activity Diagram ................................................................................. 12
Figure 12 Employee Class Diagram ............................................................................................. 13
Figure 13 Roles Class Diagram .................................................................................................... 14
Figure 14 User Class Diagram ...................................................................................................... 15
Figure 15 Login Sequence Diagram ............................................................................................. 16
Figure 16 Public User Sequence Diagram .................................................................................... 17
Figure 17 Admin Sequence Diagram ............................................................................................ 18
Figure 18 Product Search Sequence Diagram .............................................................................. 19
Figure 19 Shopping List Sequence Diagram ................................................................................ 20
Figure 20 Create Shopping List State Diagram ............................................................................ 21
Figure 21 Update Shopping List State Diagram ........................................................................... 22
Figure 22 Add Item to Inventory State Diagram .......................................................................... 23
Figure 23 Product Search State Diagram ...................................................................................... 24
Figure 24 Salary and leave Management State Diagram .............................................................. 25
Figure 25 Admin DFD level 1 ...................................................................................................... 26
Figure 26 Public User DFD Level 1 ............................................................................................. 27
Figure 27 Side Menu Bar .............................................................................................................. 39
Figure 28 Main Screen .................................................................................................................. 39
Figure 29 Admin Profile ............................................................................................................... 40
Figure 30 Nearest shop search ...................................................................................................... 40
Figure 31 Product search through image scanning ....................................................................... 40
Figure 32 Employee Management ................................................................................................ 41
Figure 33 Inventory Management ................................................................................................. 41
Figure 34 Side menu bar for shop keeper ..................................................................................... 42
Figure 35 Daily tips ...................................................................................................................... 42
Figure 36 Queries handling ........................................................................................................... 42
Software Design Description for Bazaar Buddy
Page iv
Index of Tables
Table 1: Revision History ............................................................................................................... v
Table 2: Evaluation History ........................................................................................................... vi
Table 3 Requirements Traceability Matrix ................................................................................... 37
Software Design Description for Bazaar Buddy
Page v
Revision History
Table 1: Revision History
Name
Bazaar Buddy
Date
20_12-19
Reason for changes
Initial Version
Version
1.0
Software Design Description for Bazaar Buddy
Page vi
Application Evaluation History
Table 2: Evaluation History
Comments (by committee)
Action Taken
*include the ones given at scope time both in doc and
presentation
Supervised by
Engr. Iram Hina
Signature______________
Software Requirements Specification for Bazaar Buddy
Page 1
1. Introduction
The days are getting busier. Now a days, people prefer online shopping rather than shop themselves
from market but many of them face certain issues like long waiting for the delivery or mostly not
getting the right product, which you have ordered. The quality is compromised. So why not to shop
by yourself within no time and no tension of late delivery and compromise in quality “Bazaar Buddy”
will be an interactive mobile application which will be supplant of shop assistant or salesperson of
the shop/mart. It will be listing shops and mart available in your area and will be maintaining positive
business relationships to ensure future sales. Also have information of in stock product and helps in
management. It will help customers to find the goods and products they are looking for. Answering
queries from customers and finding details of the product. It may also will be keeping up to date with
special promotions and putting up displays.
1.1 Purpose
As it is the era of modern technology people prefer shopping online while sitting on their couch rather
than visiting markets and finding items. We are going to revive our traditional shopping technique
through our interactive android app “BAZAAR BUDDY”. As the name indicates the application will
be recompensing shop assistant or salesperson and will be performing most of his duties like query
handling of customers, help them finding products, telling detail about product etc. Customers get
desired product within his locality. Also, the application will be helpful for business owner he can
manage record of his inventory through it and do promotions. Then, for most priority is that public
who are the major stake holders will shop in complete satisfactory and efficient manner. So, there is
no need of hiring large force of full-time employees as salesperson, or there is not more need to wait
for long delay delivery packages which most of the times are wrong products just install a single app
as integral solution of all your problems.
1.2 Scope
Due to rapid growth of technology, business organizations have switched over from the traditional
method of selling goods to electronic method of selling goods. The major concerns are regarding
online frauds. Sometimes, there is disappearance of shopping site itself. In addition, the online
payments are not much secured. Customers must be careful in revealing their personal information.
So, the interactive app “Bazaar Buddy” will help user to shop in safe and satisfactory manner.
Moreover, customers will shop in no pressure because most of times the sales representatives try to
influence the buyers to buy the product. So, the app will also provide personal attention to customers
and help them in purchasing goods. There will be no Long delays to get your product. User can buy
their desired product from the nearest located shop. The retailer will also be free of managing his
employees as the human resource will decrease. As retailers continue to embrace technology to get
closer to customers and enrich the in-store experience, the role of the shop assistant will evolve. With
customers increasingly demanding support with self-service technology and expecting a more
Software Requirements Specification for Bazaar Buddy
Page 2
connected experience, digital skills will soon be a prerequisite for any customer assistant position,
and the role as we know it will likely be no more.
2. Design methodology and software process model
Design methodology provides a logical and systematic means of proceeding with the design process
as well as a set of guidelines for decision-making. The design methodology provides a sequence of
activities, and often uses a set of notations or diagrams. Waterfall is the most sequential choice as our
process of developing the system is step wise. Typically, one stage must be finished before the next
can begin, which can help with organization and assignments. We have locked or requirements in
requirement gathering phase. And till now design phase is also completed. So, we can say that in
design methodology two phases of Waterfall model is translated according to Bazaar Buddy. For
Developing we are using Object oriented programming approach.
Figure 1 Waterfall Model
Software Requirements Specification for Bazaar Buddy
Page 3
3. System overview
3.1 Architectural design
We are using 3 tier architecture for our system. SO, by modularizing the user interface, business logic,
and data storage layers it will easy to develop and maintain the system. These three layers consist of:
Data Layer: The data tier comprises of the database/data storage system and data access layer. Bazaar
Buddy will be having SQL Databases because of having large amount of data.
Application Tier- This tier contains the functional business logic which drives an application’s core
capabilities. Written in Java which will act as a bridge between User interface and data access point.
Presentation Tier- The presentation tier is the front-end layer in the 3-tier system and consists of the
user interface. It displays content and information useful to an end user of Bazaar Buddy and
communicates with other layer of architecture.
Figure 2 3-tier Architecture for BB
Software Requirements Specification for Bazaar Buddy
Page 4
3.1.1 Data Flow diagram (level 0)
The system Bazaar buddy will be having databases for the storing data. Whenever the external entities
i.e. Shop owner, Shop keeper or public user generate any request the query is sent to systems
databases and it respond back so the system respond back to the entity which made request.
Figure 3 DFD level 0
Software Requirements Specification for Bazaar Buddy
Page 5
3.1.2 Overall Flow Diagram of System:
The system Bazaar Buddy will be having 3 major entities as user these are Shop Owner or Admin,
Shop Keeper or Employee and Public User or Customer. Shop Owner will have control over
employees he can view add or remove employee, data will be provided by employees themselves.
Shop owner can also manage salary with the help of attendance and experiences. One major
functionality is to manage inventory which has all detail of in stock items, he can add, delete, edit
information regarding them. The other entity is Shop keeper or employee which will be assisting shop
owner to exceed his business by developing positive customer relationship by responding their
queries in efficient manner. He can also edit his profile which will help shop owner to manage
employees. He can also have products information access from inventory. Public user will be having
their major functionalities. He can have his shopping list within the system which he can add delete
or edit. In addition to that he can search shops either by its name or by location. Furthermore, Public
user will be having all products details simply by scanning product image or by product name. The
information in inventory will be giving data regarding desired product.
Figure 4 Flow diagram
Software Requirements Specification for Bazaar Buddy
Page 6
3.1.3 Entity Relation Diagram:
“Person” is a parent entity and its child entities are “Salesperson” and “User” as they have some
common attributes like name, contact number and address etc. User can create shopping list, can
search for nearest shop/marts and can view, search and buy products. And the salesperson can manage
the products by adding, deleting or updating products in databases.
Figure 5 ERD
Software Requirements Specification for Bazaar Buddy
Page 7
3.2 Process flow/Representation
3.2.1 Activity Diagram for Login:
This is Activity diagram for Login. Pre-Condition for the activity is that user must be registered to
the system. So, when logging in he needs to provide username & password. Validation of provided
data will done if it is invalid user can go to forget password or either end the activity. Else if the
provided credentials are valid user can access various other functionalities accordingly and this
activity will be ended, user will perform various other activities afterwards.
Figure 6 Login Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 8
3.2.2 Inventory Management:
After login the Businessowner or Admin can have control over the inventory. He can add new
products to inventory along with all details. He can also Update inventory by adding deleting or
editing information regarding products or stock. Admin can view product and have all details related
to it if the product doesn’t exist it will report that product not found.
Figure 7 Inventory Management Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 9
3.2.3 Employee Management:
When the Admin/ Businessowner logged into the system he can go to Employee management and
can manage data over there. He can view his employees’ profile and add or remove them. Despite
that he can also manage attendance and experience which will calculate and manages salary
accordingly.
Figure 8 Employee Management Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 10
3.2.4 Shopping List
A public user can have their shopping list within the application. This diagram shows how this activity
will be going to perform. The user can perform various sub activities he can just view already created
list or delete it. He can also edit list by adding or removing items. The user can create new shopping
list by adding items.
Figure 9 Shopping list Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 11
3.2.5 Search Shop
This activity diagram shows how public user will be going to perform activity for shop search.
Authenticated user can search shop by its specified title if shop found it will show all details related
to it otherwise system report that shop not found. In addition to that for customer ease the system will
be automatic searching all he nearest located shop and give list of them user will select his desired
shop and see details regarding it.
Figure 10 Search Shop Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 12
3.2.6 Search Product:
The Activity diagram for the search of product is shown. The Public user how has valid login
credentials can login and have access. The user have choice between to search through image or by
text. If he wants to search through image he simply scan the product and for text search user will
specify product name, After searching products from data sources if product found or some other
related product found it will give details regarding them if not system shows product not found.
Figure 11 Search Product Activity Diagram
Software Requirements Specification for Bazaar Buddy
Page 13
4. Design models
4.1 Class Diagrams
4.1.1 Employee
Employee is a Parent class and it helps all the major data of employee working in a shop. These data
will be use in salary management, leave management and attendance. When employee log-in, it will
authenticate with the given data and attendance will manage salary etc. The authentication of
employee is depending on data saved in database.
Figure 12 Employee Class Diagram
Software Requirements Specification for Bazaar Buddy
Page 14
4.1.2 Role
In this diagram, Permission class is acting as a parent class and all other classes are acting as child
class. But all other classes like child classes are independent in nature. They only need permission
from parent class to execute their other functionalities.
Figure 13 Roles Class Diagram
Software Requirements Specification for Bazaar Buddy
Page 15
4.1.3 Users
In this diagram, business owner class is acting as a parent class and other individual in a company
are associated or dependent on business owner and the both details are dependent or composed of
individual and company, and the contact is composed on company and individual classes. Business
owner has each batch code for the products and the features including their type, title etc.
Figure 14 User Class Diagram
Software Requirements Specification for Bazaar Buddy
Page 16
4.2 Sequence Diagrams
4.2.1 Login
In this sequence diagram, it is shown that how will login module work? First when user login to the
account but if he/she forgot the password. user will click on the “Forgot Password”. A request will
be sent. Otherwise, the login details will be sent for verification. Then these details will be matched
to original details in database. For this first the authentication for accessing it will be provided. If the
user clicked for “Forgot Password”, an email will be sent to reset password. Or if the login details are
invalid reply will be sent back to user along with destroying sessions and tokens and logout. Else if
login details are valid, user will login successfully.
Figure 15 Login Sequence Diagram
Software Requirements Specification for Bazaar Buddy
Page 17
4.2.2 Public User
This is sequence diagram in which it is shown that how public user will use the application. First,
he/she will login to use the application. When login successfully, he/she will be able to use the app
further. User can create shopping list by selecting products and then save/update his/her list. Similarly,
user can search for the nearest shop to their location by switching-on their GPS location or by entering
the name of an area. In addition, user can scan image to get the product details.
Figure 16 Public User Sequence Diagram
Software Requirements Specification for Bazaar Buddy
Page 18
4.2.3 Admin:
In this sequence diagram, it is shown that how admin could use the application. Admin can do
customer management, inventory management and employee management. First, he/she will login to
use the application. When login successfully, he/she will be able to use the app further. Admin can
do profile management by adding information about him/her and his/her business. Similarly, he/she
can manage inventory by adding, editing or deleting items/products and their details. He/she can
manages the counts of stocks. Shop Owner will have control over employees he can view add or
remove employee, data will be provided by employees themselves. Shop owner can also manages
salary with the help of attendance and experiences.
Figure 17 Admin Sequence Diagram
Software Requirements Specification for Bazaar Buddy
Page 19
4.2.4 Product Search
This sequence diagram is about for searching product. First, user will run the application. The main
page will be displayed. User will request to open the Product tab which will be displayed. Then if
user want to search the product by text, it will simply enter the name of product or if user wants to
search product by image, it will simply click the image and scan it. The system will send the text or
either image to database or search it. The searched result will be sent back to user and displayed.
Figure 18 Product Search Sequence Diagram
Software Requirements Specification for Bazaar Buddy
Page 20
4.2.5 Shopping List
Creating a shopping list helps user in many ways. Following sequence shows to create shopping list.
First opening the product page that will be displayed. Then user will search product (which is
explained before), select desired product. Then if the selected product are out of stock, a message will
be displayed. Otherwise it will show the quantity box for the product quantity. User will enter the
quantity and click “Add” to add them in shopping list. The system display a message to continue
selecting product for adding in list or want to quit. If user select “Yes” then it will jump up to the step
of searching product. Else it will save/cancel changes and quit.
Figure 19 Shopping List Sequence Diagram
Software Requirements Specification for Bazaar Buddy
Page 21
4.3 State Transition Diagram
4.3.1 Creating Shopping List
This state diagrm is about the shopping list. At first, machine is idle. Then on command of creating
shopping list it will be in the state accordingly. Then it will be in adding product state. It will ask to
add more product if the answer is “Yes” it go back to adding product state and if the answer is “NO”,
it will ask to save the list. Same case, if the answer is “Yes” it will save the list and if the answer is
“NO”, it will cancel the changes and quit. It will go to end state.
Figure 20 Create Shopping List State Diagram
Software Requirements Specification for Bazaar Buddy
Page 22
4.3.2 Updating Shopping List
This state diagrm is about the updating shopping list. At first, it will display the existing shopping
lists.. Then on command of updating shopping list it will be in the state accordingly. It will sk rather
to add products or delete. It will be in adding product state if user choose “Add product”. It will add
products which is described before. . It will be in delete product state if user choose “Delete product”.
It will ask to save the list. If the answer is “Yes” it will save the list and if the answer is “NO”, it will
cancel the changes and quit. It will go to end state
Figure 21 Update Shopping List State Diagram
Software Requirements Specification for Bazaar Buddy
Page 23
4.3.3 Add Item to Inventory
This state diagrm is about the adding item to inventory. At first, machine is idle. Then on command
of open inventory page it will be in the state accordingly. Then it will be in adding product state. It
will ask to add more product if the answer is “Yes” it go back to adding product state and if the answer
is “NO”, it will ask to save it. Same case, if the answer is “Yes” it will save it and if the answer is
“NO”, it will cancel the changes and quit. It will go to end state.
Figure 22 Add Item to Inventory State Diagram
Software Requirements Specification for Bazaar Buddy
Page 24
4.3.4 Product Search
This state diagrm is about the searching product. At first, machine is idle. There is a choice rather
search by text or image. By choosing ‘by text’, user has to enter nameof product otherwise user has
to tke image. If the user enter name, it will send the text to database else it will scan image. The
system will show the result. That will either exist or not. If the product doesnot exist then it will show
the message and ask to search more. If the answer is “Yes” it go back to initial state and if the answer
is “NO”, it will quit. It will go to end state. If the product does exist then it will display them. User
will select desired product. System will display the details of selected product and will ask to search
more. If the answer is “Yes” it go back to initial state and if the answer is “NO”, it will quit. It will
go to end state.
Figure 23 Product Search State Diagram
Software Requirements Specification for Bazaar Buddy
Page 25
4.3.5 Salary and Leave Management
This state diagrm is about the employee management. At first, admin/shopowner will register his/her
employee. If the employee is login system will show him/her active and admin can view his/her salary
details. Active employee may has applied for leave. The request may approved, rejected or in pending
state. If the employee is logout it will show him/her inactive. Deleted accounts of employee show
them invalid.
Figure 24 Salary and leave Management State Diagram
Software Requirements Specification for Bazaar Buddy
Page 26
4.4 Data Flow Diagram (level 1)
4.4.1 Admin
Admin or Shop Owner will have to login (1.0) which Is authenticated by DB. One major functionality
is to manage inventory (2.0) which has all detail of in stock items, he can add, delete, edit information
regarding them. Furthermore, he has control over employees (3.0) he can view add or remove
employee data will be provided by employees themselves. Shop owner can also manage salary with
the help of attendance and experiences. He can also manage profile (4.0) by editing it and edit shop
info (5.0) time to time to keep customer updated. All data is stored, Updated and fetch from respective
databases.
Figure 25 Admin DFD level 1
Software Requirements Specification for Bazaar Buddy
Page 27
4.4.2 Public User
Public User is required to register (1.0) himself/ herself first. User can login (2.0) after validation of
all credentials. He can also Edit his profile (3.0). In addition to that he can search shops (4.0) either
by its name or by location. Furthermore, Public user will be having all products details (5.0) simply
by scanning product image or by product name. The information in inventory will be giving data
regarding desired product. Despite that He can have his shopping (6.0) list within the system which
he can add delete or edit. The databases are requested and responded accordingly.
Figure 26 Public User DFD Level 1
Software Requirements Specification for Bazaar Buddy
Page 28
5. Data design
Data of the application will be in SQL data base.
• The data contained in the database are related to entities i.e. Shop, Shop Owner, Shop keeper,
Products, Public users.
• The relationships between data items refers to what entity is doing what like Shop Owner is
managing his shop profile. Public User is searching for products etc.
• There are also certain constraints to access data for example to provide credentials before
login to system. If system authenticate or validate it the user is allow to access other data.
5.1 Data dictionary
A
Admin/Shop owner/Businessowner:
Admin is a shop owner or businessowner who owns the shop or business. All the functions like
inventory management or employee management etc. are under his/her control.
Attendance Management:
Attendance management will allow shop-owner to manage his/her employees’ attendance or the hours
of working. It will help to track record of employees’ working hours or days and the leaves which
will help in salary management also.
B
Bazaar Buddy (BB):
BB refers to a system or an application that will helps public customers to shop in a friendly way and
shop owner/businessowner to manage his/her shop activities or sales activities.
E
Employee Management:
Employee management help businessowner to keep record of his/her employees’ working in
statistical form or report form.
I
Inventory Management:
Inventory management module helps shop-owner and salesperson to maintain and have control over
inventory and in-stock information related to product available in his/her shop.
L
Leave Management:
Leave management help admin to leave or take off. It will also help in attendance which is calculated
for his/her salary at the end of month.
P
Profile Management:
Software Requirements Specification for Bazaar Buddy
Page 29
Profile management will allow user either it’s a shop-owner or public user or an employee to manage
his profile. He/she can edit, update or delete his/her information in it. Businessowner can also create,
edit or update the shop’s profile, in which he/she can add the shop’s name, address and location etc.
Public User/Customer:
Public user/customer is a person that searches the product, select and buys the products. He/she is a
person for which the application will be developed, and can enjoy the features and facilities provided
by the system.
Q
Query Management:
Query management is a communication channel between a customer and a shop keeper. The customer
will make queries as he needed and the shopkeeper has to respond on it.
S
Salary Management:
Salary management module will help shop-owner to keep all the financial related data which includes
pay role etc. It will auto generate salary according to employee grade, leaves, attendance, working
hours and performance.
Shop Keeper/Salesperson/Employee:
Shop keeper/salesperson is a manager who manages the shop activities and also helps in sales of the
product.
6. Algorithm & Implementation
6.1 Login:
Enter Email
Enter Password
If(Email==true && Password==true){
Open home page
}
else{
print "Invalid Password or Email"
NewUser = print "Are you new user? (Yes/No)"
switch(NewUser){
case "no":
goto step 2
break
case "yes":
create_account()
break
}
Software Requirements Specification for Bazaar Buddy
}
create_account(){
Enter User Name
Enter Email
Enter Password
Enter Contact_Number
if(Password < 8 characters){
print Password should not be less than 8 characters
Enter Password
}
elseif(Password does not have special characters)
print Your Password should contain special characters
Enter Password
}
if(user_name == already exist){
print Try some another name. Its is already exist
Enter User Name
}
6.2 Admin
Enter choice
switch(choice){
case "Inventory Management"
Inventory_Management()
break
case "Employee Management"
Employee_Management()
break
case "Edit Profile"
Edit_Profile()
break
}
Inventory_Management(){
Open Inventory page
Enter choice
switch(choice){
case "View Inventory"
Search Product Category to be View
if found{
Page 30
Software Requirements Specification for Bazaar Buddy
Display Product Details
}
else{
print "No Product Exist"
}
break
case "Create New Category"
Insert Product Category to be added
Save and Exit
break
case "Update Product Info"
Search Product Category to be Updated
if found{
Edit New Product || Edit Existing Product
}
else{
print "No Product Exist"
}
break
case "Delete Product"
Search Product Category to be deleted
if found{
Select Product to be deleted
Delete Selected Product
}
else{
print "No Product Exist"
}
break
}
}
Employee_Management(){
Open Employee Management page
Enter choice
switch(choice){
case "View"
Search Employee to be View
if found{
Display Employee Details
Page 31
Software Requirements Specification for Bazaar Buddy
}
else{
print "No Employee Exist"
}
break
case "Register/Add New Employee"
Add New Employee
Make Employee Profile
Add Employee Info
Save and Exit
break
case "Delete Employee"
Search Employee Record to be deleted
if found{
Select Employee to be deleted
Delete Selected Employee
}
else{
print "No Employee Exist"
}
break
}
}
Edit_Profile(){
Open Profile page
Edit name, Image, Email, user_name
Save OR Cancel
Exit
}
6.3 Salesperson:
Enter choice
switch(choice){
case "Inventory Management"
Inventory_Management()
break
case "Query Management"
Query_Management()
break
Page 32
Software Requirements Specification for Bazaar Buddy
case "Edit Profile"
Edit_Profile()
break
}
Inventory_Management(){
Open Inventory page
Enter choice
switch(choice){
case "View Inventory"
Search Product Category to be View
if found{
Display Product Details
}
else{
print "No Product Exist"
}
break
case "Create New Category"
Insert Product Category to be added
Save and Exit
break
case "Update Product Info"
Search Product Category to be Updated
if found{
Edit New Product || Edit Existing Product
}
else{
print "No Product Exist"
}
break
case "Delete Product"
Search Product Category to be deleted
if found{
Select Product to be deleted
Delete Selected Product
}
else{
print "No Product Exist"
}
Page 33
Software Requirements Specification for Bazaar Buddy
break
}
}
Edit_Profile(){
Open Profile page
Edit name, Image, Email, user_name
Save OR Cancel
Exit
}
Query_Management(){
Open Query Page
Enter choice
switch(choice){
case "Add Query"
Enter Query Response
break
case "Update Query"
Change Query Response
break
case "Delete Query"
Delete Query
break
}
}
6.4 Public User:
Enter choice
switch(choice){
case "Shopping List"
Shopping_List()
break
case "Product Search"
Product_Search()
break
case "Nearest Shop"
Nearest_Shop()
break
case "Edit Profile"
Page 34
Software Requirements Specification for Bazaar Buddy
Edit_Profile()
break
}
Edit_Profile(){
Open Profile page
Edit name, Image, Email, user_name
Save OR Cancel
Exit
}
Nearest_Shop(){
switch(choice){
case "By Location"
if(GPS_of_User == ON){
Show All Shops/Marts Of Specified Location with information
}
else{
Print "Switch ON your Location"
}
break
case "By Area"
Enter Area Name OR Longitude/Latitude
Disply All Shops/Marts Of Entered Area with information
break
}
}
Shopping_List(){
Open Shopping_List Page
switch(option){
case "Create Items"
Open Product Category page
Select Products to be added in List
Add their Counts
Save OR Cancel
break
case "View List"
Open Saved Shopping List
break
Page 35
Software Requirements Specification for Bazaar Buddy
case "Delete List"
Delete Selected List
break
case "Update List"
switch(choice){
case "Add Products"
Open Product Category page
Select Products to be added in List OR Add their Counts
Save OR Cancel
break
case "Delete Product"
Select Product to be deleted
Delete or Cancel
break
}
break
}
}
Product_Search(){
switch(choice){
case "by image"
Take image
Scan image
if (image == Item in database){
Display Images with details
}
else{
Print "Product not found"
}
break
case "by text"
Enter Product Name
if (Product_Name == Item in database){
Display Images with details
}
else{
Print "Product not found"
}
Break}}
Page 36
Software Requirements Specification for Bazaar Buddy
Page 37
7. Software requirements traceability matrix
Table 3 Requirements Traceability Matrix
Req.
Number
Ref. Item
Design Component
Component Items
FR01
Class Diagram
Inventory_Class
addInventory(),
editInventory(),
deleteInventory(),
searchInventory()
FR01
DFD
Admin Level 1
Manage Product
FR01
Activity Diagram
Inventory Management
Add new product
Update Inventory
View product
FR01
Sequence
Diagram
Admin’s perspective
Inventory Management
FR01
State Diagram
Add items in inventory
Add products
FR02
Class Diagram
Employee Class
addEmployee(),
editEmployee(Int),
deleteEmployee(Int),
searchEmployee()
FR02
DFD
Admin Level 1
Manage Employee
FR02
Activity Diagram
Employee Management
Manage Employee,
Manage Attendance,
Manage Leave,
Manage Experience
FR02
FR02
Sequence
Diagram
Admin
Employee Management
State Diagram
Salary and leave
Management
Salary,
Register,
Leave,
Software Requirements Specification for Bazaar Buddy
Page 38
Delete account
FR04
DFD
User Level 1
Search nearest shop
FR04
Activity Diagram
Search Shop
Search shop
FR04
Sequence
Diagram
Public User
Nearest Shop
FR05
Class Diagram
Product Class
description
FR05
DFD
User Level 1
Search Product
FR05
Activity Diagram
Search Product
Show Product Details
FR05
Sequence
Diagram
User’s Perspective
Product
FR05
Sequence
Diagram
User and Database
Product
FR05
State Diagram
Product Search
View Details
FR06
DFD
User Level 1
Create Shopping List
FR06
Activity Diagram
Shopping List
View,
Edit,
Create,
Delete
FR06
Sequence
Diagram
Shopping List
Public User
Add product to shopping
list,
Shopping List
FR06
State Diagram
Add Shopping List,
Update Shopping List
Add products,
Update List
Software Requirements Specification for Bazaar Buddy
Page 39
8. Human interface design
8.1 Screen images
8.1.1 Public User Perspective
Figure 28 Main Screen
Figure 27 Side Menu Bar
Software Requirements Specification for Bazaar Buddy
Figure 30 Nearest shop search
Page 40
Figure 31 Product search through image scanning
8.1.2 Admin or Shop Owner Perspective
Figure 29 Admin Profile
Software Requirements Specification for Bazaar Buddy
Figure 33 Inventory Management
Figure 32 Employee Management
Page 41
Software Requirements Specification for Bazaar Buddy
Page 42
8.1.3 Shop Keeper Perspective
Figure 34 Side menu bar for shop keeper
Figure 35 Daily tips
Figure 36 Queries handling
Software Requirements Specification for Bazaar Buddy
8.2 Screen objects and actions
User can do following actions in his User Interface:
User can View profile. And update it.
He can search for nearest shop just by clicking to it
User can also search for product detail
Admin can Mange his inventory details
Page 43
Software Requirements Specification for Bazaar Buddy
Page 44
Admin can also keep record of his employees
Shop keeper can view add or respond quires
9. Appendix I
o https://moqups.com/?utm_source=mockupscom
o https://www.jinfonet.com/resources/bi-defined/3-tier-architecture-completeoverview/
o https://creately.com/blog/diagrams/class-diagram-relationships/
o https://www.geeksforgeeks.org/unified-modeling-language-uml-state-diagrams/
