{"id":37876,"date":"2025-04-16T22:02:34","date_gmt":"2025-04-16T12:02:34","guid":{"rendered":"https:\/\/myassignmenthelp.info\/assignments\/?p=37876"},"modified":"2025-04-16T22:02:36","modified_gmt":"2025-04-16T12:02:36","slug":"inventory-management-system-2363331","status":"publish","type":"post","link":"https:\/\/myassignmenthelp.info\/assignments\/inventory-management-system-2363331\/","title":{"rendered":"Inventory Management System-2363331"},"content":{"rendered":"

<\/p>\n\n\n\n

Introduction <\/h1>\n\n\n\n

Global Tech Corp. is a rapidly expanding firm that provides sophisticated technology packages. It recently tried to implement an automated inventory management program to help with warehouse operations. However, the implementation failed because poor system design and lack of a thorough analysis occurred. This failure resulted in waste, financial losses, and customer unhappiness. To prevent such similar problems, the company needs a sound method to design and build systems (Adzgauskaite et al., 2025).<\/p>\n\n\n\n

A proposed new inventory management system will help optimize operations, eliminate errors and make sure the warehouse runs smoothly. The system will have user registration and login, manage purchase of products, sales and purchase reports, payment processing and good sales tracking. These will assist administrators and customers to make informed decisions utilizing real-time information.<\/p>\n\n\n\n

The project will adopt the Agile methodology which includes the ability to adapt, receive continuous feedback, as well as, iterative development. Agile will enable the team to rapidly respond to change, increase productivity, and result in a quality system. Development process will include planning, design, coding, testing, and deployment in short iterations. Contact with stakeholders will see that needs are met. By adopting this methodology, the new inventory management system will be reliable, flexible and intuitive \u2013 meeting the company\u2019s needs in the efficient way (Aratchige et al., 2024).<\/p>\n\n\n\n

1. Planning, Requirements Modeling, and Analysis<\/h1>\n\n\n\n

1.1. Scope Identification and Project Planning<\/h2>\n\n\n\n

The project is to design and implement an inventory control system for Global Tech Corporation. It includes functionalities like user login, product management, purchase and sales tracking, payment handling and report display. The new system will help to improve efficiency, minimize mistakes, and facilitate smooth warehouse operations. Agile methodology will be employed to build the system incrementally and iteratively allowing for ongoing refinement and stakeholder feedback (Day, 2025).<\/p>\n\n\n\n

Work Break Down Structure<\/strong><\/strong><\/p>\n\n\n\n

A Work Break Down Structure (WBS) assists in breaking tasks down into smaller, manageable pieces. It breaks down the project into broad phases like planning, design, development, testing, and deployment. Each phase is then detailed into individual tasks.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The Gantt Chart<\/strong><\/strong><\/p>\n\n\n\n

The Gantt Chart is task scheduling based on Agile method. It sets up start and end dates for each task, ensuring project deadlines are achieved. The chart provides a clear visualization of dependencies among tasks to assist in resource allocation and tracking the progress.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

1.1. Use Case Modeling<\/h2>\n\n\n\n

Use case diagram<\/strong><\/strong><\/p>\n\n\n\n

A Use Cases Diagram shows the way the various actors interact with the system. The diagram shows the main functions of the system and the roles of users in these functions. For an Inventory Management System, the actors may include Administrators, Store Managers and Customers, with use cases like adding inventory, updating stock, generate reports and orders. The diagram helps to define system boundaries and user roles. It helps the stakeholders to understand the interactions between users (Lenberg et al., 2024).<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

High-Level Use Case Descriptions<\/strong><\/strong><\/p>\n\n\n\n

A High-Level Use Case Description gives an outline of system capabilities without being too detailed. Each use case contains the actor(s) and short description, a system response. For example, the “Add Inventory” use case includes the Admin, who enters new product details. The system checks and stores the data. The Generate Reports use case allows the Store Manager to request for a list of reports, and the system provide relevant stock details. These descriptions can help to define the functional requirements.<\/p>\n\n\n\n

Table <\/em>2<\/em>: High-Level Use Case Descriptions<\/em><\/em><\/p>\n\n\n\n

Use Case<\/strong><\/strong><\/td>Actors<\/strong><\/strong><\/td>Description<\/strong><\/strong><\/td>System Response<\/strong><\/strong><\/td><\/tr>
Manage Users<\/strong><\/td>Admin<\/td>The admin adds, removes, or updates user accounts.<\/td>System validates inputs and updates the user database.<\/td><\/tr>
Add Inventory<\/strong><\/td>Admin, Store Manager<\/td>The actor inputs new product details, including name, quantity, and price.<\/td>System validates and stores the inventory data.<\/td><\/tr>
Update Stock<\/strong><\/td>Admin, Store Manager<\/td>The actor updates product stock levels based on new shipments or sales.<\/td>System updates stock levels and maintains logs.<\/td><\/tr>
Generate Reports<\/strong><\/td>Admin, Store Manager<\/td>The actor requests inventory or sales reports.<\/td>System retrieves relevant data and presents reports.<\/td><\/tr>
Place Orders<\/strong><\/td>Store Manager, Customer<\/td>The actor selects products and confirms an order.<\/td>System processes the order and updates stock levels.<\/td><\/tr>
View Product Availability<\/strong><\/td>Customer<\/td>The actor checks the availability of products.<\/td>System retrieves and displays stock information.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Expanded Use Case Descriptions<\/strong><\/strong><\/p>\n\n\n\n

An Expanded Use Case Description describes in detail how a system performs a task. For example, in “Add Inventory,” Admin logs in, chooses the option, fills in product information, and saves them. The system checks and saves the information. If a field is empty, it asks for it.<\/p>\n\n\n\n

In the Report Generation section, the Store Manager picks the report option, the type of report, and the system retrieves the required information. If no data is available it will inform the user. These descriptions help to accurately provide system requirements, ensuring that systems are fully functional and can properly report errors (Tetteh, 2024).<\/p>\n\n\n\n

Table <\/em>3<\/em>: Use Case 1: Add Inventory<\/em><\/em><\/strong><\/em><\/strong><\/p>\n\n\n\n

Actor:<\/strong> Admin<\/p>\n\n\n\n

Aspect<\/strong><\/strong><\/td>Description<\/strong><\/strong><\/td><\/tr>
Preconditions<\/strong><\/td>Admin must be logged in.<\/td><\/tr>
Steps<\/strong><\/td>1. Admin selects “Add Inventory”.
2. Enters product details (name, quantity, price).
3. Clicks “Save”.
4. System validates and stores the data.<\/td><\/tr>
Postconditions<\/strong><\/td>Product is added to the database.<\/td><\/tr>
Exceptions<\/strong><\/td>If fields are missing, the system prompts for completion.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Table <\/em>4<\/em>: Use Case 2: Generate Reports<\/em><\/em><\/strong><\/em><\/strong><\/p>\n\n\n\n

Actor:<\/strong> Store Manager<\/p>\n\n\n\n

Aspect<\/strong><\/strong><\/td>Description<\/strong><\/strong><\/td><\/tr>
Preconditions<\/strong><\/td>Store Manager must have access rights.<\/td><\/tr>
Steps<\/strong><\/td>1. Store Manager selects “Reports”.
2. Chooses a report type (e.g., monthly sales).
3. System fetches data and generates the report.<\/td><\/tr>
Postconditions<\/strong><\/td>Report is displayed or downloaded.<\/td><\/tr>
Exceptions<\/strong><\/td>If no data is available, the system notifies the user.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/a>1.1. Interaction and Behavior Modeling<\/h2>\n\n\n\n

Sequence Diagram<\/strong><\/strong><\/p>\n\n\n\n

A Sequence Diagram illustrates how a system works step by step. It helps to see how the various parts of the system relate. First, determine the process to display like “Add Inventory.” Then, list next who or what is affected, the Admin, System, and Database. Then, list each action in sequence. For example, the admin fills in product details, the system verifies them and the database stores them. Use arrow to indicate messages between them. If there is an alert, the system can give a warning. This diagram is helpful because it shows that tasks are carried out in a sequence. It assists developers to build system efficiently.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Figure <\/em>5<\/em>: Sequence diagram<\/em><\/em><\/p>\n\n\n\n

Explanation of Developing a Sequence Diagram<\/strong><\/strong><\/p>\n\n\n\n

Sequence Diagram shows how various parts of a system interact step by step. To create one:<\/p>\n\n\n\n