Skip to content
ProjectsWritingAboutCVLinks
WA
Hire me
HomeProjectsWritingAboutCVLinks

Have a useful problem?

Let's make the next
thing worth using.

© 2026 Wasif AliBuilt around evidence, not hype. Privacy
WASIF ALI
Home/Projects/Pharmacy Management System

Case study, Desktop · Java

Pharmacy Management System
Pharmacy system · OOP project

A desktop pharmacy system with role-based access, MySQL inventory and real-time stock updates.

Coursework project — 2025.Desktop · Java
View source All projects

Context

The problem

A pharmacy juggles stock, sales and three kinds of users. Pharma Ease gives each role — admin, seller, customer — exactly the screens they need.

My role: Object Oriented Programming project, Air University Kamra.

Implementation

How it works

Separate the roles

Admins manage stock, sellers sell, customers browse — one codebase, three views.

Keep stock honest

Every sale updates MySQL inventory immediately.

Implementation highlights

  • Role-based access: admin, seller, customer
  • MySQL inventory management and sales tracking
  • Real-time stock updates
  • Modular class design with controller pattern and Swing UI

Evidence

What can be verified

The points below summarize the public repository and owner-provided CV where noted. Read the source for implementation details before drawing further conclusions.

Roles3

Admin, seller, customer.

Boundaries

Limitations and next questions

  • Academic OOP project; desktop-only.
  • No live deployment; runs against a local MySQL database.
Evidence-first note: a live demo demonstrates an interface and workflow; it does not by itself prove security, scale, or real-world impact.

Technical overview

JavaSwingMySQLJDBCOOP

Project links

Inspect the original implementation and, where available, the live application.

Repository

Last content review: 14 November 2026. Details may change as project repositories evolve.

Continue exploring

Related work.

Full-Stack

University Course Management System

A university course platform with student/admin roles, secure login and full course management — bcrypt password hashing, JWT sessions and role-based access.

Full-Stack

AccessDesk

A role-based customer access portal: one MySQL database shared by four API-key roles, each with its own row limits, credit allowance and visible fields — enforced on the server.