PRACTICAL NO.

Aim:
To perform system analysis of an Inventory Management System: Software Requirement
Specification.

Theory

1. Introduction

The Inventory Management System (IMS) is designed to create and maintain information about
products, suppliers, and customers for efficient management of inventory processes. Through this
application, suppliers can register their inventory details, customers can place orders, and the admin
can manage the entire inventory system. The system is aimed at providing an online platform to
manage stock levels, process orders, and monitor inventory trends efficiently. Admin has the main
authority to perform additions, deletions, and modifications in the system.

2. Purpose

The purpose is to meet the modern-day challenges of inventory management by efficiently handling
stock levels, ensuring timely updates, and maintaining supply chain consistency. The Inventory
Management System (IMS) aims to serve as a robust tool for tracking and managing stock in real
time, ensuring minimum discrepancies and maximum availability. This document delineates the
features of IMS, serving as a guide for developers and a validation document for clients.

3. Problem Definition

Traditional inventory management systems often rely on manual processes, leading to delays, errors,
and inefficiencies. For instance, when a product is out of stock, it may take considerable time to
replenish due to a lack of real-time updates. Furthermore, manual documentation may result in data
duplication, loss, or incorrect record-keeping. The goal is to create an automated and centralized
platform for managing inventory operations, ensuring seamless stock tracking and efficient
communication between stakeholders.

4. User Requirements

1. Auto-check for reorder levels of stock.

2. Maintain accurate records of stock transactions and updates.

3. Support fast searching for products in inventory.

4. Provide real-time alerts for low stock levels.

5. Ensure suppliers and customers have accurate information about stock availability.

6. List product availability at any given time.

7. Enable efficient management of supplier and customer information.

 8. Provide notifications for inventory updates or stockouts to relevant stakeholders.

5. System Requirements

• The system should auto-detect low stock levels and notify the relevant stakeholders.

• Maintain detailed information about each product, categorized by type, supplier, and
availability.

• Enable efficient management of inventory transactions, such as stock additions, removals,

and adjustments.

• Support fast searching of inventory records to locate required items quickly.

• Ensure accurate delivery of products to customers and correct stock allocation for orders.

• The system should alert users about product restocking needs and upcoming promotions.

• Notifications about system updates should be sent via email, SMS, or through the app
interface.

6. Functional Requirements

Login
The system provides security features through username-password matching, ensuring only
authorized users can access the system with appropriate access levels.

• Admin

o Input: Username, Password

o Output: Invalid Login, Update Inventory, Log Out

Product Registration
Allows suppliers to register new products in the system.

• Input: Product ID, Name, Category, Quantity, Price, Supplier Details

• Output: Successfully Registered

Stock Management
Enables staff to manage stock from procurement to sales, including tracking stock levels, expiry
dates, and restocking alerts.

• Input: Product Details, Quantity Updates

• Output: Updated Stock Records

Supplier/Customer Management
Maintains records of all suppliers and customers, including transaction history and contact details, in
a centralized database.

• Input: Supplier/Customer ID
 • Output: List of Transactions

Reporting
Generates pre-defined reports such as stock availability, supplier details, customer orders, and
inventory trends.

• Input: Admin Username, Admin Password

• Output: Daily Report, Monthly Report, Annual Report

7. Non-Functional Requirements

Availability
The system should be accessible at all times, with backups available for data recovery in case of
hardware failure or database corruption, ensuring 24x7 availability.

Data Security
Implements automatic logouts after inactivity and ensures secure handling of sensitive data,
including encryption for supplier and customer information.

Correctness
Ensures accurate stock details and order matching with minimum discrepancies.

Maintainability
The inventory system should be easy to maintain, with regular updates and accurate record-keeping
of stock.

Usability
Ensures the system is user-friendly, with a standardized pricing system for products.

Extensibility
Supports the addition of new functional requirements, such as integrating with third-party logistics
platforms.

Performance
Minimizes delays in system interactions, with a response time of under 20 seconds for key
operations.

Reliability
The system is designed to handle high reliability, ensuring smooth operations and secure data
handling.

This format mirrors the structure and detailed explanations of the Blood Bank Management System,
tailored for an Inventory Management System
PRACTICAL NO. 3

Aim:
To perform the function-oriented diagram: DFD Diagram for Inventory Management System.

Theory

Data Flow Diagram (DFD)

A Data Flow Diagram (DFD) is a graphical representation of the flow of data through a system. It
illustrates the processes, data stores, and external entities interacting within the system.

Description

1. Context-Level Data Flow Diagram (DFD Level 0):

o The context-level DFD describes the entire Inventory Management System as a

single process.

o It shows the interactions between the system and external entities like Suppliers,
Customers, and Admin.

o The diagram depicts input and output data flows, representing the entire system as a
single bubble.

2. Inventory Management System DFD Level 0:

o This level focuses on the overall structure of the system.

o The main process represents the Inventory Management System as a single entity
with external entities interacting with it.

3. Inventory Management System DFD Level 1:

o The Level 1 DFD breaks down the high-level process into its main sub-processes.

o It highlights the primary functions carried out by the system, such as:

▪ User Management

▪ Stock Management

▪ Supplier Management

▪ Customer Order Management

▪ Login Management

4. Inventory Management System DFD Level 2:

o The Level 2 DFD breaks down each sub-process from Level 1 into more detailed sub-
processes.

o It provides specific details about the system's internal functioning, representing data
flows between the main modules and their sub-modules.
 o Level 2 diagrams ensure the modules and their data flow are well-detailed and
correspond to the Level 1 diagram.

PRACTICAL NO. 4 Aim: To perform user’s view analysis of Blood Bank management System: Use Case
Diagram.

Theory: Use Case Diagram Description

• The use case diagram are usually referred to as behavior diagram used to describe the actions of all
user in a system.

• All user describe in use case are actors and the functionality as action of system.

• This Use Case Diagram is a graphic depiction of the interactions among the elements of Blood Bank
Management System.

• The use case diagram for example blood bank management system. These illustrations describe the
system’s general and specific processes.

• It represents the methodology used in system analysis to identify, clarify, and organize system
requirements of Blood Bank Management System.

• The main actors of Blood Bank Management System in this Use Case Diagram are: Super Admin,
System User, Donor, Anonymous Users, who perform the different type of use cases such as Manage
Blood, Manage Blood Group, Manage Blood cells.

• Manage Donor, Manage Stock, Manage Order, Manage Patient, Manage Users and Full Blood Bank
Management System Operations.

• Major elements of the UML use case diagram of Blood Bank Management System are shown on
the picture below.

• The Blood Bank Management System Use Case Diagram is used to show the processes involved
when users invoke the software.

• It depicts the structure of the system behavior. Additionally, the diagram consists of processes (use
cases) and users or “actors”.

• It uses defined symbols to describe the overall flow of the system.

• The admin donor and patient are the actors present in the diagram.

• The system components are or the functions are registration, login , search blood donors, blood
request , blood donate, and inquiry.

• The arrows used here shows the association relationship between them.
### **PRACTICAL NO. 5**

**Aim:** To draw structural view diagram of **Inventory Management System**: Class Diagram

---

### **Theory: Class Diagram**

**Description**

- Class diagram is a static diagram. It represents the static view of an application.

- Class diagram is not only used for visualizing, describing, and documenting different aspects of a
system but also for constructing executable code of the software application.

- Class diagram describes the attributes and operations of a class and also the constraints imposed on
the system.

- The class diagrams are widely used in the modeling of object-oriented systems because they are the
only UML diagrams, which can be mapped directly with object-oriented languages.

- Class diagram shows a collection of classes, interfaces, associations, collaborations, and constraints.
It is also known as a structural diagram.

- It is a designed Structure that Shows the system's classes and their relationship. It is made to guide
programs along with the System development.

- It Contains the Systems class attribute methods as well as the relationships between Classes: The
Class diagram makes sure that your system development is in line with what Should be its functions.

- Classes included in the System are inventory, user registration, supplier, order, and stock. The
arrows Show the relationships among the classes.

- The diagram depicts the name and attributes of the classes and relationships. It resembles a
flowchart in which classes are represented as boxes with three rectangles inside each box.

- The top rectangle has the class’s name; the middle rectangle contains the class’s properties; and the
bottom rectangle contains the class’s methods, commonly known as operations.
PRACTICAL NO. 6

Aim: To draw behavioral view diagram of Inventory Management System: Sequence, Activity, and
State Chart Diagram.

Theory

1. Sequence Diagram

Description

• A sequence diagram is a unified modeling language (UML) diagram that illustrates the
sequence of messages between objects in an interaction.

• A sequence diagram consists of a group of objects that are represented by lifelines and the
messages that they exchange over time during the interaction.

• A sequence diagram shows the sequence of messages passed between objects. Sequence
diagrams can also show the control between structures between objects.

• A sequence diagram is a Unified Modeling Language (UML) diagram that illustrates the
sequence of messages between objects in an interaction.

• A sequence diagram consists of a group of objects that are represented by lifelines and the
messages that they exchange over time during the interaction.

• A sequence diagram shows the sequence of messages passed between objects. Sequence
diagrams can also show the control structures between objects.

• For example, lifelines in a sequence diagram for an inventory scenario can represent a
customer, warehouse manager, or supplier.

• The communication between the customer, warehouse manager, and supplier is represented
by messages passed between them. The sequence diagram shows the objects and the
messages between the objects.

• In this sequence diagram, the transfer of messages can be seen. The supplier registers items
to be added to the inventory. The supplier receives a receipt after the inventory is updated.

• The messages are shown through generalization arrows. The warehouse sends stock details
for updating as well as requests for reordering.

• The warehouse receives an acknowledgment.

• The inventory system provides stock details to customers according to needs. The inventory
system receives orders as well as acknowledgments for the stock.

2. Activity Diagram

Description

• An activity diagram is a behavioral diagram, i.e., it depicts the behavior of a system. An

activity diagram portrays the control flow from a start point to a finish point showing the
 various decision paths that exist while the activity is being executed. We can depict both
sequential processing and concurrent processing of activity using an activity diagram.

• A well-designed blueprint that greatly aids in system development is the Inventory

Management System Activity Diagram.

• It displays how the inventory management system behaves while interacting with its users or
customers.

• The UML Activity Diagram for the Inventory Management System also gives programmers
creative ideas and tells them what to do as they build the system.

• Suppliers and the Inventory Manager would be the users that are important in creating an
activity diagram for the Inventory System.

• It would be a lot simpler for you to create the interactions and activities in the system if you
knew who would be using it.

• The system’s actions toward its users will then be predictable to you. So, you should keep in
mind that your system should be easy for people to use and work well. Let me explain what
it is and does. Inventory Management System programmers need activity diagrams to
determine how the software interacts with users.

• Activity diagrams tell programmers how to make and use software. If you want user-friendly,
easy-to-use software, complete the activity diagram.

• The activity diagram shows how activities move and how the Inventory Management System
and its users should communicate. Your readers and users will learn how to use the system
via its activity diagram. To explain how the Inventory System might work, utilize a UML
activity diagram.

3. State Chart Diagram

Description

• A state diagram is a type of diagram used in computer science and related fields to describe
the behavior of systems.

• State diagrams require that the system described is composed of a finite number of states;
sometimes, this is indeed the case, while at other times this is a reasonable abstraction.

• Many forms of state diagrams exist, which differ slightly and have different semantics. A state
chart diagram describes a state machine. State machine can be defined as a machine that
defines different states of an object, and these states are controlled by external or internal
events.

• State chart diagram describes the flow of control from one state to another state. States are
defined as a condition in which an object exists, and it changes when some event is
triggered.

• The most important purpose of a state chart diagram is to model the lifetime of an object
from creation to termination. State chart diagrams are also used for forward and reverse
engineering of a system. However, the main purpose is to model the reactive system.
• The following state diagram shows the transitions of many states. The state changes of the
inventory system occur when an action is initiated.

• After the inventory system is accessed, the state changes to login or register page according
to the respective user. After that page, the state changes to checking of the authentication of
the user, whether it exists, and if yes, the following user enters their respective section. The
next state shows the display of the respective section page
PRACTICAL NO. 7

Aim: To draw implementation view diagram of Inventory Management System: Component

Diagram.

Theory: Component Diagram

Description

• A component is a logical unit block of the system, a slightly higher abstraction than classes.

• It is represented as a rectangle with a smaller rectangle in the upper right corner with tabs or
the word written above the name of the component to help distinguish it from a class.

• The inventory management system UML component diagram explains the sketch of the
required software and hardware components and the dependencies between them.

• These components are labeled to clarify their part in the system’s operation. They were
represented by symbols that explain their function and role in the overall inventory
management operation.

• The component diagram of the inventory management system has 7 components and 2
nodes, which are the receipt printer, login, desktop, keyboard, database interface, and
inventory database server. The 2 nodes are personal computer and database connection.

• The component transaction database is also dependent on nodes. The deployment diagram
shows the scenario when the system is deployed.

• It has 4 nodes represented with boxes and relationship connections. The nodes are the
inventory management system, the customer’s device, the admin’s device, and the database
(system server).

• The system server node contains a developed database that will hold the details of the
system online.

• For the connection, the system is connected to the server database using a private network,
which enables it to pass a connection to the devices and enable users to access the system
and database. The admin and the customer then can communicate using an online or
internet connection.
PRACTICAL NO. 8

Aim: To draw environmental view diagram of Inventory Management System: Deployment Diagram.

Theory: Deployment Diagram

Description

• A deployment diagram is a UML diagram type that shows the execution architecture of a
system, including nodes such as hardware or software execution environments, and the
middleware connecting them.

• Deployment diagrams are typically used to visualize the physical hardware and software of a
system. Using it, you can understand how the system will be physically deployed on the
hardware.

• Deployment diagrams help model the hardware topology of a system compared to other
UML diagram types, which mostly outline the logical components of a system.

• Deployment diagrams are used to visualize the topology of the physical components of a
system, where the software components are deployed.

• Deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.

• The inventory management system UML deployment diagram explains the sketched
relationship between software and hardware. These sketches also include the software and
hardware components to clarify their part in the system’s operation.

• They were represented by nodes, and the connections were represented by labeled arrows.
The admin’s PC has access to the system’s back end and can monitor the system’s server.

• The deployment diagram shows the scenario when the system is deployed. It has 6 nodes
represented with boxes and components within.

• A deployment diagram for inventory management system is used to describe the system’s
operation, showing the hardware and software components that run in each node, and
explaining the connections between them