Scribd
Upload
15 views17 pages

Analysis and Design TEMPLATE

Uploaded by

itslaibaramzan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views17 pages

Analysis and Design TEMPLATE

Uploaded by

itslaibaramzan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Project Name:

Supermarket Management System

Analysis and Design Phase

Project Participants:

Submitted to: Sir Arsal Mehmood


Chapter One

Business Requirements and Rules

The proposed system (Supermarket Management System) will provide three logins at the initial interface
i.e. Admin, Seller, and Customer. These are the person with attributes ID, Name, Phone No, Username,
and Password. There is no other person who is of interest to the supermarket. And a person can only be
an admin, seller, or customer at a single time. Admin will be able to manage the product lines
(ProductLineID, ProductLineName), Products (ProductID, ProductName), Customers, and Seller’s
information.

The products are grouped into several product lines. A particular product belongs to only a single product
line but a product line contains many products.

Sellers will be able to sell/add different products. Customers can submit orders for many products; a
product may be there in a number of orders and for each order, the record of OrderQuantity is also
maintained. Customers will be able to view the product categories(product lines) and product details and
will be able to make purchases by adding items to the cart at the end, an Invoice, bearing an invoice
number and invoice date, is generated which can then be printed out. A single invoice is issued to only a
customer, but a customer may be assigned multiple invoices.

Business Rules:

• Access to the functionality of the system is not possible unless correct username and password
along with correct role selected is entered.
• A particular product belongs to only single product line but a product line contains many products.
• Customer can submit orders for many products and a product may be there in a number of orders
• A single invoice is issued to only a single customer but a customer may be assigned with multiple
invoices.
• The Customer must not be able to modify the products details.
• Seller cannot view the Customer’s details.
• System must generate a comprehensive error message on each exception.

List of Final Entities


1. Admin
2. Seller
3. Customer
4. Product
5. Invoice
6. Order
7. ProductLine
8. OrderLine

List of Final Relationships


• Admin manages Products
• Admin manages Seller’s Data
• Seller sells Products
• The invoice is assigned to the Customer
• Customer submits Orders
• ProductLine contains(includes) products
• Order contains products
EERD
Tables Converted from EERD

PERSON

ID Name PhoneNo Username Password PersonType

ADMIN

AdminID

SELLER

SellerID

CUSTOMER

CustomerID

PRODUCT_LINE

ProductLineID ProductLineName AdminID

PRODUCT

ProductID Name AdminID ProductLineID SellerID

ORDER

OrderID OrderDate CustomerID

ORDER_LINE

OrderID ProductID Quantity

INVOICE

InvoiceNumber InvoiceDate CustomerID


Chapter Two

Tables After 3NF


3NF

PERSON

ID Name PhoneNo Username PersonType

LOG_IN

Username Password

ADMIN

AdminID

SELLER

SellerID

CUSTOMER

CustomerID

PRODUCT_LINE

ProductLineID ProductLineName AdminID


PRODUCT

ProductID Name AdminID ProductLineID SellerID

ORDER

OrderID OrderDate CustomerID

ORDER_LINE

OrderID ProductID Quantity

INVOICE

InvoiceNumber InvoiceDate CustomerID

Forms and Forms Layout

• Splash Form
• Login Form

• Products Form
• Form for Admin to View Seller’s Data

• Customer Form

• Seller Form
• Admin Form

• Form for Seller to Add Products


• Categories Form
• Form for Admin to View Customer’s Data

• Manage Seller Form


• Purchase Products Form

• Form for Customer to View Categories


Reports and Reports Layout

• Sales Report for Admin in Standard Layout.


• Purchases Report for Admin in Standard Layout.
• Invoice for Customer in Standard Layout.
• Seller’s Report for Admin in Standard Layout.
• Customer’s Report for Admin in Standard Layout.

Chapter Three
Final Classes of the Project:

• Person
• Log_in
• Seller
• Admin
• Customer
• Product
• Order
• Product_Line
• Order_Line
• Invoice

Methods and Data types of Classes:

Person

Display info():void

CheckLoginInfo():string
Log_in

ToString() : string

Seller

Sell_products():void

Customer

PurchaseProducts():void

SubmitOrder():void

printReciept() : void

Product

Display_data() : void
Admin

AddProduct() : void

EditProduct() : void

DeleteProduct() : void

ViewSellersData() : void

ViewCustomersData() : void
Class Diagram

_____________________________________________________________________________________

You might also like