Clothes-Shop-Management-System

Analysis

Product Scope

  • Higher Efficiency: Better item tracking and staff management.
  • Better Control Over Business Processes and Needs.
  • Customer Satisfaction: With the quick and consistent service.
  • Highly accurate data: Does not wear out or get lost.
  • Facilitates Data Manipulation: Like removing or adding new records.
  • Improved Communication: Between staff and customers, and staff and administration.
  • Facilitates Transactions With The Customers.
  • Facilitates Tracking Stocks And Payments.
  • Higher Efficiency in Managing Payments.
  • Easier To Apply And Manage Discounts.

Product Value

Customers of the shop will always stay satisfied since articles will always be available. They won’t run out of stock, and if they did, they will be replaced with new ones. Garments will be categorized, and therefore, easy to find. The process of purchasing garments will be simple. Returning and replacing items will be fast and easy.

Intended Audience

  • Clothing Shop Managers
  • Boutiques Managers

Intended Use

The target of this program is to facilitate the management of the staff, and the garments being sold since it will contain records of the all the staff working and all the garments available. Garments and staff members can be removed, new ones can be added to any garment. All transactions will be recorded as well for later use, like if the customer wanted to return a garment.

General Description

This shop management system is a system that manages garment stores.
There are two points of view:
the admin’s and the cashier’s. The admin will manage verything about the store, from adding and removing garments, to increasing and decreasing prices, to adding a new staff member, and changing their salary.The cashier, on the other hand, can place orders and return garments.

Functional Requirements

The program must ask the user to log in.

The user must enter the username and the password.
If the username or the password was incorrect, the user must be informed and taken back to the login screen.

The program must determine whether the user was an admin or a cashier.

If the user was an admin:

They must have sufficient access to the system by allowing them to:

  • Have the ability to know the garments available, their ID, their name, price, quantity, category, available discounts, and description.
  • Manage the data like adding new garments, removing, and modifying existing garments(Like changing their name, price, description, stock, adding discounts …etc.).
  • Add, remove, and modify staff members. The modification includes changing their salary by giving them a raise or lowering their salary.
  • View staff members and see their personal info that includes ID, name, DOB, address, phone number, email, salary, position, gender, password … etc.
  • Search staff by ID, or name.
  • View the history, meaning all the orders that have been made by customers.
  • View the items according to their category, name, or ID.
  • See total earnings per day.
  • Search bills by ID, and date.

If the user was a cashier:

They should be able to place an order or return a garment, depending on the customer.
When placing an order:
  • They should enter the name of the garment/s the customer is buying and the quantity.
  • The cashier should be provided with a list of all the garments ordered by the customer, their price, quantity, date, a total price for each garment type based on its quantity, and a total price for all the garments together. If discounts were offered, they should be indicated.
  • The cashier should have the ability to remove any unwanted item or clear the whole cart.
  • After placing the order, these garments’ quantity should be decreased in the database. And the cashier should be provided with an electronic bill (displayed on the screen) that includes all the information that was displayed before placing the order, and the bill ID.
  • Then the cashier can start another order.
When returning an garment:
  • To return an garment the user must provide the name of the garment, and the date the garment was bought.
  • The customer cannot return a garment after two weeks.
  • If the date was valid, the garment should go back to the database and its quantity there must increase.

The system must provide information .

Diagrammatic Representation

The Diagram Has Been Designed By:

  • Srusht Sleman
  • Mabast Abdulqadir
  • Raman Mhedin
  • Hassan Sabah

Under The Supervision Of:

  • Mina Bassam