Presented By:

Muhammad Asad 2016277

Muhammad Arham Ud Din 2016275
Muhammad Zain ul Abideen 2016249
 INTRODUCTION

• Greenland Premium Hypermarket is a megastore which sells each sorts of

product.

• It is a product and employee management system.

• How does the supermarket operates in the background is explained with the help
of OOD concepts and techniques.
 USE CASE DIAGRAM

• Use case diagrams specify the events of a system and their flows.

• It describes the user’s interaction with the system.

• The relationships between and among the actors and the use cases are made.
SIMPLE USE
CASE
DIAGRAM
COMPLETE
USE CASE
DIAGRAM
• Both the Admin and Cashier will have access to Log in

• Log in will verify the password before granting access

The Admin will have access to the Employee Management system

• Search a specific employee

• Hire or fire an employee

• The admin has all the control on the products.

• It can search, add, remove or update a product(e.g. price)

• The admin can search a supplier whose stock is about to end.

The Cashier has access to the Sales Management System.
• It can add or remove a product.
• It can generate bill and tell us about product’s price.
The Admin hass access to the Total Sales from the Report.
• It can look for a particular day’s sale.
The cashier while accepting payment has an option of accepting

• payment via cash

• Payment via Credit Card

 SEQUENCE DIAGRAM
• A sequence diagram is an interaction diagram that emphasizes the time ordering of
messages.

• It shows a set of objects and the messages sent and received by those objects.
 CASHIER SEQUENCE

• Cashier will attempt to log in

• Log in class will verify information from database
• If logged in, cashier will create cart
• Cart will get inventory item from inventory class
• Inventory class will generate items from database
• Cart will generate bill
• Cart will send sold list to supply Management
• Supply Management will change Inventory parameters
• Inventory class will update parameter and save updated parameters
and depleted list in database
 ADMIN SEQUENCE

• Admin will attempt to log in

• Log in class will verify information from database
• If logged in, Admin can update database.
• Update means, admin can add, remove or change data in the
database.
• Admin can change data of Employees and Inventory
• Admin can also display bill from database
 CLASS DIAGRAM
• It describes the structure of a system by showing the system's classes, their
attributes, operations, and the relationships among objects.

• They are the only UML diagrams, which can be mapped directly with object-
oriented languages.
 DESIGN PATTERNS
We have used the following Design Patterns:

• Singleton Pattern

• Strategy Pattern

• Observer Pattern
SINGLETON
• Used to ensure that only one instance of a particular class ever gets created
We have used this in inventory class so that only one object of an item is created.

STRATEGY
• Strategy lets user choose multiple strategies on run time.
We have used this in Payment class. It will let user choose whether to pay cash or pay from card.

OBSERVER
• The observer pattern allows objects to keep other objects informed about events occurring
within a software system
We have used this in Inventory and supply chain classes. Inventory will observe supply chain.
THANK YOU