Chapter 4 – System Requirements Analysis
4.1 Analysis of Current System Using a Flow Chart:
Customer:
This entity represents individuals or entities external to the organization who interact with the
inventory system by placing orders for products. Customers initiate the process by ordering
products.
Inventory System:
This is the core component of the current system being analyzed. It represents the inventory
management system within the organization. The inventory system interacts with external
entities (customers, suppliers) and internal stakeholders (managers) to facilitate various
inventory-related processes.
Supplier:
The supplier is an external entity that provides products to the organization. The inventory
system interacts with suppliers to manage product procurement and replenishment.
Manager:
The manager represents an internal stakeholder within the organization who oversees
inventory management activities. The manager may access the system to generate semester
reports, which could include information such as inventory levels, sales performance, and
other relevant metrics.
4.2 System Requirements
4.2.1 Functional Requirements
Functional requirements specify the actions or functions that the system must perform to
meet the users' needs and achieve its objectives. These requirements describe the system's
behavior and functionality in detail. In the context of the Inventory Management System,
functional requirements include:
Inventory Management: The system should allow users to add, update, and delete inventory
items. It should track inventory levels, handle stock replenishment, and generate alerts for
low stock levels.
Order Management: The system should support order processing, including order placement,
order fulfillment, and order tracking. It should handle customer orders, generate invoices, and
update inventory levels accordingly.
Reporting and Analytics: The system should provide comprehensive reporting capabilities,
allowing users to generate reports on inventory status, sales performance, and financial
analysis. It should support various report formats and customization options.
User Management: The system should have user authentication and authorization
mechanisms. It should support different user roles (e.g., admin, staff) with appropriate access
rights to system functionalities.
4.2.2 Non-functional Requirements
Non-functional requirements specify the qualities or attributes of the system, such as
performance, security, usability, and scalability. These requirements describe how the system
should behave or perform rather than what it should do. In the context of the Inventory
Management System, non-functional requirements may include:
Performance: The system should be responsive and perform efficiently, even with a large
volume of data. It should have fast response times for user interactions such as searching,
adding items to cart, and generating reports.
Security: The system should ensure the confidentiality, integrity, and availability of data. It
should implement authentication mechanisms, access control, data encryption, and audit trails
to protect sensitive information and prevent unauthorized access.
Usability: The system should be user-friendly and intuitive, with clear navigation and well-
designed user interfaces. It should require minimal training for users to understand and
operate the system effectively.
Reliability: The system should be reliable and available whenever needed. It should have
backup and recovery mechanisms to prevent data loss and ensure system availability in case
of failures.
Scalability: The system should be scalable to accommodate future growth and increasing user
demands. It should handle a growing number of users, transactions, and data volumes without
performance degradation.