Scribd
Upload
10 views24 pages

OOSE Project

The Stock Maintenance System aims to automate inventory management, reducing manual errors and improving decision-making through real-time tracking and detailed reporting. It addresses issues in existing systems such as inaccuracies, slow processes, and difficulty in tracking stock movement. The system includes various modules for user access, product management, and inventory tracking, ensuring a user-friendly experience and scalability for businesses.

Uploaded by

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

OOSE Project

The Stock Maintenance System aims to automate inventory management, reducing manual errors and improving decision-making through real-time tracking and detailed reporting. It addresses issues in existing systems such as inaccuracies, slow processes, and difficulty in tracking stock movement. The system includes various modules for user access, product management, and inventory tracking, ensuring a user-friendly experience and scalability for businesses.

Uploaded by

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

Object Oriented Software Engineering Laboratory–CCS356

Stock Maintenance System


Review Date:14.05.2025
Team Members:
J.Harini
(820422104028)
K.Iswarya
(820422104031)
K.Kaviya
Aim of the Project:
To design and implement an efficient Stock
Maintenance System that:

 Accurately tracks and manages inventory levels in


real-time.
 Reduces manual errors and paperwork through
automation.
 Enhances decision-making with detailed reporting
and analytics.
 Maintains optimal stock levels to avoid
overstocking or stockouts.
ISSUES IN THE EXISTING SYSTEM:
1.Manual Errors:
• Data entry mistakes due to human error.
• Inaccurate stock counts and reports.
2. Lack of Real-Time Updates:
• Inventory data is not updated instantly.
• Delays in reflecting stock-in and stock-out activities.
3. Time-Consuming Processes:
• Stock tracking and reporting are slow and tedious.
• Requires more manpower and time.
4. Overstocking or Stockouts
• Inability to forecast demand accurately.
• Leads to excess inventory or shortages.
5.Difficulty in Tracking Stock Movement
• No proper record of stock transactions.
• Hard to trace damaged, expired, or lost items.
Features of the proposed
system:
 The proposed Stock Maintenance System will
provide real-time tracking of inventory, helping to
reduce manual errors and save time. It will have a
user-friendly interface, low stock alerts, and
automatic updates for stock in and out.

 The system will generate useful reports, support


secure role-based access, and allow easy
categorization of products. These features will
improve accuracy, efficiency, and overall
management of stock.
System Architecture:
Software Requirement
Specification(SRS):
 A Software requirements specification (SRS), a requirements specification for a software
system, is a complete description of the behavior of a system to be developed and may
include a set of use cases that describe interactions the users will have with the software .

Software Requirements:
OS: Windows/Linux/macOS
Backend: Node.js / Django / Java Spring Boot
Frontend: React / Angular / Vue
Database: PostgreSQL / MySQL
APIs: RESTful
Browser: Chrome, Firefox
Hardware Requirements:
Server:
Processor: Quad-core processor
RAM: 8 GB
Storage: 500 GB SSD
Internet Connection: High-speed internet
Client:
Primary Devices: Computers or laptops
Optional Input Devices: Barcode scanners (optional)
Output Devices: Printers
Functional Requirement :
 User Access Control – Login, registration, and role-based
access(Admin, Staff).
 Product Management – Add, edit, delete products with details
like name, SKU, category.
 Stock In/Out Handling – Record and update inventory for
incoming and outgoing stock.
Non-Functional Requirements:

Performance: ≤2 sec response time


Uptime: 99.9%
Security: HTTPS, role-based access
Usability: Responsive, easy UI
Scalability: Support many users/products
Maintainability: Modular design

The purpose of the SRS is to:


1. Establish the basis for agreement between the customers and the
suppliers on what the software product is to do.
2. Provide a basis for developing the software design.
3. Reduce the development effort.
Module Decomposition:
The Stock Maintenance System is divided into different modules to efficiently
handle specific tasks related to inventory and stock management. These
modules help streamline the system’s functionality, making it more user-
friendly and easier to manage.

Types of Modules:
1.Login Module
2.Registration Module
3. Stock Entry and Requisition Module
4. Inventory Tracking Module
1.Login Module:

This module allows users to log in to the system using their ID and password.
Only authorized users with valid credentials can access their respective accounts.This
ensures secure authentication and protects the system from unauthorized access.

2.RegistrationModule:

In this module, new users of the system are registered. There are two types of
users in the system inventory managers and suppliers. Each user type has a specific
registration process and interface to enter their details, such as business information,
stock preferences, and contact details.
3.Stock Entry and Requisition Module:

This module allows authorized users, such as inventory managers, to enter


new stock details into the system. Users can specify the products, quantities, suppliers,
and required stock levels. This module also includes requisition functionalities where the
system can automatically generate stock orders when certain levels are reached.

4.Inventory Tracking Module:

This module is designed to help users track stock movements across the
system. It includes features to monitor stock levels, track incoming and outgoing
shipments, and manage real-time updates of inventory data. Users can filter inventory
based on product categories, stock status, or location.
UML DIAGRAMS:
1.Use Case Diagram
2.Class Diagram
3.Sequence Diagram
4.Collaboration Diagram
5.State Chart Diagram
6.Activity Diagram
Use Case
Diagram:
A use-case diagram is a
graph of actors, a set of use
cases enclosed by a system
boundary, communication
(participation) associations
between the actors and the
use cases, and generalization
among the use cases. It shows
the relationship among the
actors and use cases within a
system.
Class Diagram:
A class diagram is a
collection of static
modeling elements, such
as classes and their
relationships, connected
as a graph to each other
and to their contents;
their internal structures,
and their relationships to
other classes.
Sequence
Diagram:

Sequence diagram
describes the behavior of
the system by viewing the
interaction between the
system and its
environment . It
represents the class at
the top and their lifetime,
their interactions as
relations.
Collaboration
Diagram:
A Collaboration Diagram
(also known as a
Communication Diagram) is a
type of UML (Unified
Modeling Language) diagram
that shows how objects
interact with each other and
how messages are passed
between them to accomplish
a specific task.
State Chart
Diagram:
A state chart diagram
(also known as a state
diagram or state machine
diagram) is a type of diagram
used in software engineering
and systems modeling to
describe the dynamic
behavior of a system by
showing its various states and
the transitions between those
states.
Activity
Diagram:
An activity diagram is a
type of behavioral diagram in
the Unified Modeling
Language (UML) used to
model the workflow or
business processes of a
system. It shows the
sequence of activities and the
flow of control from one
activity to another.
OUTPUT:
Conclusion:
 The Stock Maintenance System provides an efficient, reliable, and user-
friendly solution for managing inventory in real-time. By automating core
functions such as stock tracking, product management, reporting, and
low-stock alerts, the system significantly reduces manual errors and
improves operational accuracy.
 With role-based access control, detailed reporting, and scalable
architecture, the system can support businesses of various sizes, helping
them maintain optimal inventory levels and make informed decisions.
Overall, the project meets its objectives by streamlining stock-related
processes, enhancing productivity, and laying a strong foundation for
future growth and integration.

You might also like