Practical- 1

Aim
To create a system to perform the Stock maintenance

Software used
StarUML

Theory
Stock Maintenance System is a real time application used in the merchant’s day to day system. This is a
database to store the transaction that takes places between the Manufacturer, Dealer and the Shop Keeper
that includes stock inward and stock outward with reference to the dealer.

Problem Statement
The stock maintenance system must take care of sales information of the company and must analyze the
potential of the trade. It maintains the number of items that are added or removed. The sales person
initiates this Use case. The sales person is allowed to update information and view the database.

Purpose
The entire process of Stock maintenance is done in a manual manner. Considering the fact that the number
of customers for purchase is increasing every year, a maintenance system is essential to meet the demand.
So this system uses several programming and database techniques to elucidate the work involved in this
process.

Scope
 The System provides an interface to the customer where they can fill in orders for the item needed.
 The sales person is concerned with the issue of items and can use this system.
 Provide a communication platform between the customer and the sales person.

Here we assume ourself as the Dealer and proceed with the transaction as follows:
 The Manufacturer is the producer of the items and it contains the necessary information of the item
such as price per item, Date of manufacture, best before use, Number of Item available and their
Company Address.
 The Dealer is the secondary source of an Item and he purchases Item from the manufacturer by
requesting the required Item with its corresponding Company Name and the Number of Items required.
 The Dealer is only responsible for distribution of the Item to the Retailers in the Town or City.
 The Shop Keeper or Retailer is the one who is prime source for selling items in the market.
 The customers get item from the Shop Keeper and not directly from the Manufacturer or the Dealer.
 The Stock is the database used in our System which records all transactions that takes place between
the Manufacturer and the Dealer and the Dealer and the Retailer.

The functionality of a system can be described in a number of different use-cases, each of which
represents a specific flow of events in a system. It is a graph of actors, a set of use-cases enclosed in a
boundary, communication, associations between the actors and the use-cases, and generalization among
the use-cases

REAZAUR RAHMAN 10115003121

 The process of stock maintenance system is that the customer login to the particular site to place the order
for the customer product. The stock maintenance system are described sequentially through steps:
i. Login
The customer login to the particular site.
ii. Customer Details
They fill the customer details.
iii. Validate Customer
Customer details and their corresponding orders are validated
iv. Place Order
Customers place orders for the desired items.
v. Insufficient Balance
Customers must have sufficient balance to place order
vi. Inquiry
The sales person login and inquires the customer details and orders
vii. Track Order
Customers can easily track their order through system interface
viii. Cancel Order
Customers can dismiss their order as per their convenience
ix. Bill Customer
Bills are generated for their respective ordered products

Practical- 2

REAZAUR RAHMAN 10115003121

Aim
Document the Software Requirements Specification (SRS) for the identified system (Stock Maintenance
system).

Table of Contents
Table of Contents......................................................................................................................................3
1. Introduction.........................................................................................................................................4
1.1 Purpose..........................................................................................................................................................4
1.2 Scope.............................................................................................................................................................4
1.3 Definitions, Acronyms, and Abbreviations..................................................................................................4
1.4 References.....................................................................................................................................................4
2. Overall Description.............................................................................................................................5
2.1 Product Perspective.......................................................................................................................................5
2.2 Product Functions.........................................................................................................................................5
2.3 User Classes and Characteristics..................................................................................................................5
2.4 Operating Environment.................................................................................................................................5
2.5 Design and Implementation Constraints.......................................................................................................6
2.6 User Documentation.....................................................................................................................................6
2.7 Assumptions and Dependencies...................................................................................................................6
3. Specific Requirements........................................................................................................................6
3.1 External Interfaces........................................................................................................................................6
3.2 System Function...........................................................................................................................................7
3.3 Performance Requirements…………………………………………………………………………………………………………………… 7
3.4 Logical Database Requirements………………………………………………………………………………………………………………8
3.5 Design Constraints………………………………………………………………………………………………………………………………….8
3.6 Software System Attributes…………………………………………………………………………………………………………………….9
3.7 Other Requirements……………………………………………………………………………………………………………………………….9
4. External Interface Requirements......................................................................................................9
4.1 User Interfaces..............................................................................................................................................9
4.2 Hardware Interfaces....................................................................................................................................10
4.3 Software Interfaces.....................................................................................................................................10
4.4 Communications Interfaces........................................................................................................................11
5. Other Nonfunctional Requirements................................................................................................11
5.1 Performance Requirements.........................................................................................................................11
5.2 Safety Requirements...................................................................................................................................11
5.3 Security Requirements................................................................................................................................11
5.4 Software Quality Attributes........................................................................................................................11
6. Other Requirements.........................................................................................................................12
Appendix A: Glossary............................................................................................................................12
Appendix B: Analysis Models................................................................................................................12
Appendix C: Issues List..........................................................................................................................12

REAZAUR RAHMAN 10115003121

 4

1. Introduction
1.1 Purpose
The purpose of this document is to outline the functional and non-functional requirements for
the development of a stock maintenance system. This system aims to facilitate the effective
management of inventory levels, track stock movements, and update stock information within
a warehouse or distribution center. By keeping track of stock levels, orders, sales, and
deliveries, the system helps ensure that the right amount of stock is available at the right time
to meet customer demand. This not only prevents stockouts and overstocking but also helps
optimize inventory levels, reducing carrying costs and improving overall efficiency.
Additionally, the system provides insights into stock movement and trends, which can be
used for better decision-making, such as identifying fast-moving items, forecasting demand,
and optimizing supplier relationships. Overall, a stock maintenance system plays a crucial
role in enhancing operational efficiency, improving customer satisfaction, and maximizing
profitability for a business.

1.2 Scope
The Stock Maintenance System is designed to manage stock levels, track inventory, and
generate reports for a retail business. It will include features for adding new stock items,
updating stock levels, and generating alerts for low stock. Additionally, the system should
provide insights into stock performance and trends to help make informed decisions
regarding stock replenishment and inventory management strategies. It encompasses all
aspects related to the management and tracking of inventory within a business

1.3 Definitions, acronyms, and abbreviations

Definitions:
 Stock Maintenance System (SMS): The software system designed to manage and track
inventory levels, orders, sales, and deliveries of a business.
 Inventory: The stock of goods or materials a business holds for sale.
 Supplier: A person or organization that provides goods or services to a business.
 Customer: A person or organization that purchases goods or services from a business.
 Product: The goods or items that are available for sale in the inventory.
 Stock Keeping Unit (SKU): A unique code assigned to each distinct product for tracking
and inventory management purposes.
 Order: A request made by a customer to purchase goods from the inventory.
 Sales: The process of selling goods from the inventory to customers.
 Delivery: The process of transporting goods from the inventory to the customer's location.
 Reorder Level: The minimum quantity of a product that should be maintained in the
inventory to avoid stockouts.

1.4 References
https://www.geeksforgeeks.org/software-requirement-specification-srs-format/

REAZAUR RAHMAN 10115003121

 5

2. Overall Description

2.1 Product Perspective

The stock maintenance system, from a product perspective, is a comprehensive software
solution designed to efficiently manage all aspects of inventory control within a business. It
serves as a centralized platform for tracking stock levels, orders, sales, and deliveries. The
system provides real-time visibility into inventory levels, enabling businesses to optimize
stock levels, reduce stockouts, and improve overall operational efficiency. Additionally, the
system offers features for managing suppliers and customers, facilitating seamless
communication and collaboration. With its user-friendly interface and robust functionality,
the stock maintenance system enhances inventory management processes, leading to
improved productivity and profitability for the business. The Stock Maintenance System will
be a standalone application that interacts with a database to store and retrieve stock
information. It will interface with other systems for data exchange.

2.2 Product Functions

 Manage stock items
 Update stock levels
 Generate stock reports
 Alert for low stock levels
 Supplier Management
 Customer Management
 Order Management
 Warehouse Management

2.3 User Classes and Characteristics

 Stock Manager: Responsible for managing and monitoring the inventory, including
stock levels, orders, and deliveries.
 Supplier: Provides goods or services to the business and may need access to the system
to update product information, pricing, and delivery schedules.
 Customer: Places orders for products and may need to track order status and access past
order history.
 Administrator: Manages user accounts, permissions, and system settings.
 Auditor: Reviews and audits the inventory management processes and data for accuracy
and compliance.

2.4 Operating Environment

The operating environment of a stock maintenance system includes the hardware, software,
and network requirements necessary for the system to function properly. The system should
be able to run on standard desktop and server hardware, including processors, memory, and
storage that meet the system's performance and scalability requirements. It should also be
compatible with common operating systems such as Windows, macOS, and Linux. The
software environment should include a database management system (DBMS) for storing and
managing inventory data, as well as any additional software components required for the
system to operate, such as web servers or application servers. The system should be able to
communicate over standard network protocols such as TCP/IP and should be secure against
unauthorized access and data breaches. The system will run on Windows, macOS, and Linux
operating systems. It will require a minimum of 2GB RAM and 1GB of free disk space.

REAZAUR RAHMAN 10115003121

 6

2.5 Design and Implementation Constraints

Design and implementation constraints for a stock maintenance system may include
hardware, software, and regulatory factors. Hardware constraints could involve the
compatibility of the system with existing hardware infrastructure, such as barcode scanners or
inventory tracking devices. Software constraints may relate to the choice of programming
languages, frameworks, and databases that are compatible with the organization's IT
environment. Regulatory constraints could include compliance with industry standards and
regulations governing inventory management and data protection. Additionally, budget and
time constraints may influence the design and implementation process, requiring careful
planning and prioritization of features. The system will be developed using Java and MySQL
for the database. It will utilize a GUI for user interaction.

2.6 User Documentation

User documentation for the stock maintenance system should include comprehensive guides
and manuals to help users understand and effectively use the software. This documentation
should cover a range of topics, including how to navigate the system, how to perform
common tasks such as managing inventory, placing orders, and generating reports, as well as
troubleshooting tips and best practices. It should be written in clear and concise language,
with step-by-step instructions and screenshots where applicable to make it easy for users to
follow along. Additionally, the documentation should be organized logically, with a table of
contents and index for quick reference, and it should be regularly updated to reflect any
changes or updates to the system.

2.7 Assumptions and Dependencies

Assumptions
 Stable Internet Connection: The system assumes that there will be a stable internet
connection available to facilitate real-time updates and communication with suppliers and
customers.
 Accurate Product Information: It is assumed that the product information, such as
pricing, descriptions, and availability, provided by suppliers is accurate and up-to-date.
 Reliable Suppliers: The system assumes that suppliers will consistently provide the
required products in a timely manner and adhere to agreed-upon terms and conditions.
 Customer Data Accuracy: It is assumed that customer information, such as contact
details and order history, provided to the system is accurate and up-to-date.
 Data Security: The system assumes that appropriate measures are in place to ensure the
security and confidentiality of sensitive information, such as pricing, inventory levels, and
customer data.
Dependencies
 Hardware: The system depends on the availability and proper functioning of hardware
components, such as servers, computers, and networking equipment.
 Software: The system depends on the availability and proper functioning of software
components, such as the operating system, database management system, and application
software.
 External Services: The system depends on external services, such as payment gateways,
shipping providers, and communication services, to facilitate various functions, such as

REAZAUR RAHMAN 10115003121

 7

processing payments and delivering orders.

 Regulatory Compliance: The system depends on compliance with relevant laws and
regulations, such as data protection laws and tax regulations, to ensure legal operation.
 User Training: The system depends on users being properly trained to use the system
effectively and efficiently, reducing the risk of errors and improving productivity.

3. Specific Requirements
3.1 External Interfaces
 User Interface (UI): The interface through which users interact with the system to perform
actions such as managing stock, placing orders, and viewing reports. This can include web
interfaces, desktop applications, or mobile apps.
 Application Programming Interface (API): Interfaces that allow other software systems
to interact with the stock maintenance system. This can include APIs for retrieving product
information, updating stock levels, and processing orders.
 Database Interface: The interface that allows the stock maintenance system to interact
with the database where information such as product details, stock levels, and order history is
stored.
 External System Interfaces: Interfaces that enable the stock maintenance system to
communicate with external systems such as accounting software, inventory management
systems, and e-commerce platforms. This can involve exchanging data such as sales orders,
inventory levels, and customer information.

3.2 System Function

 Add Stock Item: Users can add new stock items to the system.
 Update Stock Level: Users can update the stock level of existing items.
 Generate Report: Users can generate stock reports based on specified criteria.
 Alert: The system will generate an alert for low stock levels.
 Order Management: Manages the process of ordering new stock items.
 Stock Tracking: Monitors stock levels, including reordering points and historical usage.
 User Management: Manages user accounts and permissions.
 Security: Ensures data security and integrity through authentication and authorization
mechanisms.

3.3 Performance Requirements

 Response Time: Define the maximum acceptable time for the system to respond to user
actions (e.g., retrieving stock information, processing transactions).
 Throughput: Specify the number of transactions or operations the system should be able to
handle within a given time period (e.g., number of transactions per second).
 Concurrency: Describe the system's ability to handle multiple users or processes accessing
and updating stock information simultaneously.
 Scalability: Define how the system should scale to accommodate increasing numbers of
users, transactions, or data volume without significantly affecting performance.

REAZAUR RAHMAN 10115003121

 8

 Availability: Specify the required uptime of the system (e.g., 99.9%) and how quickly it
should recover from failures.
 Resource Usage: Define the acceptable levels of CPU, memory, and disk usage to ensure
the system operates efficiently without overloading the hardware.
 Data Integrity: Ensure that the system maintains the integrity of stock information,
avoiding data corruption or loss.
 Security: Ensure that the system provides adequate security measures to protect stock data
from unauthorized access, modification, or disclosure.
 Reliability: Define the system's ability to perform consistently and predictably under
normal and abnormal conditions.

3.4 Logical Database Requirements

 Data Model: Define the data entities (e.g., products, suppliers, customers, orders,
inventory) and their relationships (e.g., one-to-many, many-to-many).
 Data Storage: Specify the types of data storage required (e.g., relational database, NoSQL
database) and justify the choice based on scalability, performance, and other relevant factors.
 Database Schema: Provide a detailed description of the database schema, including tables,
columns, primary keys, foreign keys, and indexes.
 Data Integrity: Define rules for maintaining data integrity, such as constraints (e.g.,
unique, not null), cascading updates, and deletes.
 Data Security: Describe measures to ensure data security, including access control,
encryption, and auditing.
 Data Migration: Specify how existing data will be migrated to the new system, if
applicable, including data cleansing and transformation processes.
 Data Backup and Recovery: Define strategies for backing up and recovering data to
prevent loss in case of system failure or other disasters.
 Data Archiving: Specify how data will be archived to free up space in the active database
while retaining access to historical data.
 Performance Requirements: Define performance metrics (e.g., response time,
throughput) and specify performance requirements for the database to meet the system's needs.
 Scalability: Describe how the database can scale to handle increasing amounts of data and
user load over time.
 Interoperability: Specify any requirements for the database to integrate with other systems
or databases.
 Data Access: Describe how data will be accessed, including queries, reports, and data
exports.
 Data Governance: Define policies and procedures for managing data quality, privacy, and
compliance with regulations (e.g., GDPR, HIPAA).
 Data Dictionary: Provide a data dictionary that defines the meaning and structure of all
data elements used in the system.

3.5 Design Constraints

 Hardware Constraints: Specifications regarding the hardware components required to run
the system, such as servers, storage devices, and network equipment.

REAZAUR RAHMAN 10115003121

 9

 Software Constraints: Specifications regarding the software components required, such as

operating systems, databases, and other applications.
 Performance Constraints: Requirements related to the system's performance, including
response times, throughput, and scalability.
 Security Constraints: Specifications regarding the system's security requirements, such as
authentication, authorization, and data encryption.
 Legal and Regulatory Constraints: Compliance requirements with laws and regulations
related to stock maintenance, such as data protection laws and industry standards.
 Budget Constraints: Limitations on the budget allocated for the development and
maintenance of the system.
 Time Constraints: Requirements related to project timelines and deadlines for the
implementation of the system.
 Interoperability Constraints: Specifications regarding the system's ability to interact with
other systems, such as compatibility with existing software or hardware.
 Usability Constraints: Requirements related to the user interface and user experience of
the system, including accessibility and user training needs.
 Environmental Constraints: Specifications regarding the environmental conditions under
which the system will operate, such as temperature, humidity, and power supply requirements.

3.6 Software System Attributes

 Reliability: The system should be reliable in managing stock information and transactions,
ensuring data integrity and availability.
 Performance: It should be able to handle a large volume of stock transactions efficiently,
with minimal response times.
 Scalability: The system should be scalable to accommodate future growth in terms of stock
items and transaction volume.
 Maintainability: It should be designed in a way that allows for easy maintenance, updates,
and enhancements.
 Security: The system should ensure data confidentiality, integrity, and availability,
protecting against unauthorized access and data breaches.
 Usability: The system should be user-friendly, with a well-designed interface for easy
navigation and use by stock managers and other users.
 Compatibility: It should be compatible with existing hardware, software, and operating
systems used within the organization.
 Availability: The system should be available whenever needed, with minimal downtime for
maintenance or upgrades.
 Interoperability: It should be able to communicate and exchange data with other systems,
such as accounting or ERP systems, using standard protocols.
 Compliance: The system should comply with relevant regulations and standards, such as
data protection laws and industry standards for stock management.

3.7 Other Requirements

 The system should be able to export reports in PDF and Excel formats.
 It should support multiple languages for international users.

4. External Interface Requirements

4.1 User Interfaces
 Login page

REAZAUR RAHMAN 10115003121

 10

 Username field
 Password field
 Login button
 Dashboard
 Menu bar with options for different functionalities (e.g., Add Stock, Update Stock,
View Stock, Generate Reports)
 Summary of stock status (e.g., total items, low stock items)
 Recent transactions or alerts)
 Add Stock Form
 Item name
 Item description
 Quantity
 Price per unit
 Submit button
 Update Stock Form
 Search field to find item to update
 Fields to update quantity or price per unit
 Update button
 View Stock
 Table displaying current stock details (item name, description, quantity, price per unit)
 Search and filter options
 Export button for downloading stock details
 User Profile
 User Information (e.g., name, role)
 Option to change password
 Logout button

4.2 Hardware Interfaces

 Barcode Scanner: Handheld barcode scanner with USB interface.
 Printer: Thermal Printer for printing labels
 Computer/Server: Minimum requirements- Intel Core i5 processor, 8 GB RAM, 256 GB
SSD.
 Display: Touchscreen monitor with a minimum resolution of 1920 x 1080 pixels.
 Network Interfaces: Ethernet Interface for connecting to the local network.
 Storage Devices: 500 GB hard drive for storing system data
4.3 Software Interfaces
 Database Management System: The system should interface with a database (e.g.,
MySQL, PostgreSQL) to store stock information.
 Operating System: The system should be compatible with common operating systems
(e.g., Windows, Linux).

REAZAUR RAHMAN 10115003121

 11

 Web Browser: The system should be accessible via a web browser for easy user
interaction.
 Programming Language: The system should be developed using a specific
programming language (e.g., Java, Python).

4.4 Communication Interfaces

 APIs: The system should provide APIs for integration with other systems, such as
accounting software or e-commerce platforms.
 Email Notifications: The system should send email notifications for alerts, updates, and
reports.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
 The system should be able to handle a large number of transactions concurrently
without significant performance degradation.
 Response times for queries and transactions should be within acceptable limits, even
under peak load conditions.

5.2 Safety Requirements

 The system should be available 24/7, with a target uptime of at least 99.9%.
 It should be able to recover quickly from failures, with minimal data loss.

5.3 Security Requirements

 The system should implement appropriate security measures to protect sensitive data,
including user authentication, access control, and data encryption.
 It should comply with relevant regulatory requirements (e.g., GDPR, HIPAA).

5.4 Software Quality Attributes

Here are the some software quality attributes for a stock maintenance system:
 Reliability: The system should be reliable, ensuring that stock data is accurate and
transactions are processed correctly without errors or data loss.
 Maintainability: The system should be easy to maintain and update, with well-structured
code, clear documentation, and modular design to facilitate changes and enhancements.
 Usability: The system should be user-friendly, with an intuitive interface that allows users
to easily navigate and perform tasks efficiently.
 Performance: The system should perform efficiently, with fast response times for queries
and transactions, even under high load conditions.
 Security: The system should be secure, implementing measures such as user
authentication, access control, and data encryption to protect sensitive information.
 Scalability: The system should be scalable, able to handle an increasing number of users,
transactions, and data volume without significant degradation in performance.
 Compatibility: The system should be compatible with various devices, operating
systems, and software to ensure seamless integration and use in different environments.
 Accuracy: The system should maintain accurate stock data, ensuring that inventory levels
are correctly updated and reflected in the system.

REAZAUR RAHMAN 10115003121

 12

6. Other Nonfunctional Requirements

Appendix A: Glossary
 Stock Maintenance System (SMS): The software system designed to manage and track
inventory levels, orders, sales, and deliveries of a business.
 Inventory: The stock of goods or materials a business holds for sale.
 Supplier: A person or organization that provides goods or services to a business.
 Customer: A person or organization that purchases goods or services from a business.
 Product: The goods or items that are available for sale in the inventory.
 Stock Keeping Unit (SKU): A unique code assigned to each distinct product for tracking
and inventory management purposes.
 Order: A request made by a customer to purchase goods from the inventory.
 Sales: The process of selling goods from the inventory to customers.
 Delivery: The process of transporting goods from the inventory to the customer's location.
 Reorder Level: The minimum quantity of a product that should be maintained in the
inventory to avoid stockouts.

Appendix B: Analysis Models

 Use Case Diagram
 Actors: Customer, Supplier, Stock Manager
 Use Cases: Manage Stock, Place Order, Manage Supplier, Manage Customer

 Activity Diagram
 Represents the flow of activities in the system for managing stock, placing orders,
managing suppliers, and managing customers

 Class Diagram
 Classes: Product, Supplier, Customer, Order, stock
 Attributes and relationships between classes

 Sequence Diagram
 Represents the interactions between actors and the system for specific use cases like
placing an order, managing stock, etc.

Appendix C: Issues List

 Stock Out Issue: The system should alert the stock manager when the stock of a product
falls below the reorder level.
 Delivery Delay Issue: The system should track the status of orders and alert the stock
manager if there are any delays in delivery.
 Incorrect Stock Level Issue: The system should have mechanisms in place to ensure
that the stock levels are accurately updated to avoid discrepancies.
 Supplier Management Issue: The system should provide features for managing supplier

REAZAUR RAHMAN 10115003121

 13

information, such as contact details, pricing agreements, etc.

 Customer Management Issue: It should manage customers info, such as contact details.

REAZAUR RAHMAN 10115003121