Professional Documents
Culture Documents
COMSATAS UNIVERSITY
ISLAMABAD VEHARI CAMPUS
Software Requirement Specification
(Artificial Intelligence Shopping System)
1 Introduction:
This document describes the requirement specifications of artificial
intelligence shopping system.
This document includes functional requirements, non-functional
requirements of the system. The scenarios and the use case model of
the artificial intelligence shopping system are created as a part of
requirements analysis. The system models are included in the
Requirements Analysis document.
Success Criteria:
Customers can frequently buy products.
Saves customers time.
Make correct bill of products.
Send bill to the right customer and cut the bill through his E
wallet.
Customer’s satisfaction with AI Shopping System.
2 Current System:
The current system used in shopping stores includes a cashier desk. The
customers buy products and take them to cashier counter where it take
a lot of time in counting the products, making bill and for payment. And
if less cashier counters are there then it will become worst. To
overcome such issues and seeing the need of this modern world we
introduce AI Shopping System.
3 Proposed System:
Our proposed system uses AI technology to detect a person while
he/she is shopping, it will automatically detects if a customer pick a
product or drop a product and when customer moves out of store the
system sends bill to its E mail and also it cuts the bill from customer E
wallet.
3.12 Security:
System should provide security to personal information of customers.
3.13 Login:
System allows only those customers that are signed with the system.
3.14 Performance:
System can work without any flaws in the performance.
3.16 Updates:
System can send correct and timely.
3.17 Refund:
System can make easy refunds in case of wrong transactions.
3.18 Maintainability:
System is easy to maintain make changes, make updates.
3.19 Response Time:
System response should be fast it can make calculations fast.
3.20 Availability:
The system should provide easy availability to the customer.
3.21 Usability:
It provides easy usability to the customers. The customer should feel
comfort while in touch with system.
3.22 Packaging:
The application is internal department use only and will not be
packaged and sold as a retail product.
Functions:
Login.
Privacy/Security.
Identify Users.
Monitors Customers.
Records of Products.
Records of Customers.
Monitors Products.
Perform Calculation.
Send Bill.
Cut Bill.
Send Updates.
Actors:
Customer.
Management Team.
Database.
4.1.1 Use Case Description:
Scenario:
Customer goes in store pickup what he wants and went out of the
store no cashier problems and system send bill on his E-mail and cuts
through his E-wallet.
Actors:
Customer.
Management Team.
Database.
Pre-conditions:
Login.
Have E-wallet.
Valid Identity.
Post-Condition:
Take Products.
Related Use Cases:
Verified users.
Login.
E-wallet.
Stake holders:
Management Team.
Flow of Activity:
Exception Conditions:
Name of a class.
Attributes:
Customer Name.
Customer ID.
Customer Phone Number.
Functions / Operations:
Relation:
Customer has a dependency relation with AI Software and Store.
Management Team:
Name of a class.
Attributes:
Name.
ID's.
Contact numbers.
Functions / Operations:
-Manages store.
-Manages System -Software.
Relation:
Name of a class.
Attributes:
o Name.
o ID's.
o Contact numbers.
Functions / Operations:
o Maintain Data:
o -Customer Data.
o -Products Records.
Relation:
Name of a class.
Attributes:
o Software.
Functions / Operations:
Relation:
o Customer.
o Management Team.
o Database Team.
4.3 Activity Model:
This model or diagram represents the activity of system that is
performed step by step.
4.3.1 Activity Flow model Description:
This mode shows how the system activates will perform step by step.
Activity Flow:
5.1 Introduction: