•
•
Project Title
Super Mart Billing System
Section:W-1
Submitted By:
M.Tahir ul Qadri F2017065018
Raza Ali F2017065194
Muneeb Ahmad F2017065166
Fashih ul Haq F2017065
University of Management and Technology
C-II Johar Town Lahore Pakistan
• Introduction
• Motivations
• Project Overview
The project is on super Mart Billing. Super Mart is the place where customers
come to purchase their daily using products and pay for that So, there is a need to
calculate the bill for the customer.
• Problem Statement
This supermarket management system has realized the transmission and control of large
goods, so as to facilitate the management and decision of sales, and reduce a big burden
for supermarkets and supermarket managers. It also can help to improve the work efficiency
of supermarket.
• Objectives
The project is relatively simple to understand as there are just a few features.
Understanding the source code will give you the idea regarding file handling:
how to add, remove, edit, and search data or info to/from file.
Listed below are the key features of this project:
• Bill Report: It shows the bill report of all the items added in
supermarket billing system.
• Add, Remove or Edit items: With this feature you can add, remove
and modify item details. In add items, you can add information or
details such as item no., item name, manufacturing date, price,
quantity, tax percent, and many more.
• Show item details: This feature allows users to see the items and the
corresponding details given for the item while adding the item.
• Requirements analysis
• List of Actors
Primary Actor:
Customer
Secondary Actor:
Admin,Staff
• List of use cases
UC-1 Add new Item Admin will add new Items in database.
UC-2 Edit Item Admin can edit the items in data base.
UC-3 Delete Item Admin can delete the item from database.
UC-4 Show Item Details Staff will control all the items details.
UC-5 Bill Receipt Customer will have the the report of the bill.
UC-6 Payment Customer will pay the bill.
Super Mart Billing System
Use Case Diagram
• Use Cases
Any three use cases form the list must be elaborated here (do NOT select login or registeration)
Use Case ID: UC-2
Use Case Enter a short name for the Use Case using an active verb phrase. e.g. Withdraw Cash
Name:
Created By: Muneeb Ahmad Last Updated By:
Date Created: Last Revision Date:
Actors: Primary Actor : Customer
Secondary Actor : Staff,Admin
Description: [Provide a brief description of the reason for and outcome of this use case.]
Trigger: Authenticate user/staff/Admin
Preconditions: Customer must select Product and from the shop to buy.
Post conditions: Customer gets computerized invoice for the products he/she brought.
Normal Flow: • Customer will order item
• System will process payment
• Customer will pays bill
• System will process bill receipt
• Customer will get bill receipt
Alternative Flows: 4a. If customer cancelled order
[Alternative Flow 1 – Not in • Use Case resumes on step 1 of normal flow
Network] 4b. if the customer wants to add item in order
• Use Case resumes on step 1 of normal flow
Note: Insert a new row for each distinctive alternative flow. ]
Exceptions: [Describe any anticipated error conditions that could occur during execution of the
use case, and define how the system is to respond to those conditions.
e.g. Exceptions to the Withdraw Case transaction
2a. In step 2 of the normal flow, if the customer enters and invalid PIN
• Transaction is disapproved
• Message to customer to re-enter PIN
• Customer enters correct PIN
• Use Case resumes on step 3 of normal flow]
Includes: [List any other use cases that are included (“called”) by this use case. Common
functionality that appears in multiple use cases can be split out into a separate use case
that is included by the ones that need that common functionality. e.g. steps 1-4 in the
normal flow would be required for all types of ATM transactions- a Use Case could be
written for these steps and “included” in all ATM Use Cases.]
Frequency of Use: [How often will this Use Case be executed. This information is primarily useful for
designers. e.g. enter values such as 50 per hour, 200 per day, once a week, once a
year, on demand etc.]
Special Requirements: Printer should be available in the Mart.
Assumptions: Database Access, Network Connectivity
Notes and Issues: [List any additional comments about this use case or any remaining open issues or
TBDs (To Be Determined) that must be resolved. e.g.
• What is the maximum size of the that a use can have?]
