Institution
Student Name
Student ID
Instructor
Date of submission
Planning, requirements modeling and analysis (65%)
Work Breakdown Structure (WBS) for Inventory Management System (IMS) Development.
Gantt Chart Based on Agile
Usecase: Order Processing
Expanded Use Case Descriptions
| Use case | Order Processing |
| Actors | Customer, System |
| Preconditions | Customer must be logged in. At least one item must be in the shopping cart. |
| Basic Flow: | 1.Customer browses available products.2.System retrieves and displays product details.3.Customer selects a product and adds it to the cart.4.Customer reviews cart and proceeds to checkout.5.System verifies stock availability.6.Customer confirms order.7.System generates a purchase order.8. Order details are stored, and the customer receives confirmation. |
| Post-condition | Order details are recorded in the system.Order status is updated accordingly. |
| Alternative Path | At step 3, if the customer applies a discount code, the system verifies and adjusts the final amount. At step 4, if the stock is insufficient, the system prompts the customer to adjust their order. At step 5, if the payment is pending, the system places the order on hold until confirmation is received. |
| Exceptional Path | At step 3, if payment fails due to an invalid card.At step 4, if the system encounters an error in stock verification, the order is paused, and the customer is notified.At step 6, if email confirmation fails, the system logs an error and retries after a defined interval. |
Use Case: Inventory Management
| Use case | Inventory Management |
| Actors | Admin, System |
| Preconditions | The admin must be logged into the system. The inventory database must be accessible. |
| Basic Flow: | The use case starts when the admin selects the inventory management module. The Admin adds, updates, or deletes a product. The System validates the product data includes Validate Product Data. The System updates stock levels include Update Stock Levels). The System generates an updated inventory report includes Generate Inventory Report). The System saves the changes and confirms the operation to the Admin. |
| Post-condition | Inventory data is updated in the system.Stock levels are correctly adjusted. |
| Alternative Path | At step 4, if the stock level of a product falls below the threshold, the system triggers a Low Stock Alert extends Low Stock Alert). At step 5, if sales trends indicate potential shortages, the system provides Stock Reorder Recommendations extends Stock Reorder Recommendation). |
| Exceptional Path | At step 3, if the Admin enters incomplete or incorrect product data, the system displays an error message and prompts for corrections.At step 4, if there’s a database connectivity issue, the system logs the error and notifies the Admin. At step 6, all modifications are logged for auditing extends Audit Log Entry). |
Steps involved in a communication diagram
- Identification of the use case: This is the initial steps of use case development. A Use Case Model provides a high-level overview of system functionalities and interactions with actors.
- Identification of objects and interactions. This encompasses objects used in the use case and how they interact with each other. For instance, Admin and systems are the objects. Interactions are the actions they perform. The admin interacts with the Inventory System to add or update product details.
- Definition of message flow and controls: The sequence of system object interactions emerges from the defined message flow mechanism which controls their operational process. The admin starts an inquiry to the Inventory System that both validates and updates the Database. Stock levels receive checks by the Stock Manager through which he activates Low Stock Alerts if necessary. System integrity is maintained through recorded changes made by the Audit Logger.
- Choose Diagram Type: A Sequence Diagram represents interactions in a step-by-step order using vertical lifelines. It clearly shows the time flow of messages exchanged between objects.
- Implement the sequence diagrams: This is the final steps which encompasses the implementation of the sequence diagram effectively.
Inventory Management system use case
Activity diagram for Order processing
Table of Domain Classes from Use Cases
| Domain Class | Attributes | Relationships | Associated Use Cases |
| Customer | CustomerID, Address, Phone | Places Orders, Makes Payments | Browse Products, Place Order, Payment Processing |
| Admin | AdminID, Permissions | Manages System & Users | Manage Inventory, View Reports |
| Product | ProductID, Name, Price, Stock | Linked to Orders, Inventory | Browse Products, Manage Stock, Order Processing |
| Inventory | InventoryID, Quantity, Location | Tracks Product Stock Levels | Manage Stock, Generate Reports |
| Order | OrderID, Date, Status | Includes Products, Customer | Place Order, Track Order, Cancel Order |
| Payment | PaymentID, Method, Amount | Linked to Orders & Customers | Payment Processing, Refund Management |
| Invoice | InvoiceID, OrderID, Date, Total | Generated from Orders | Generate Invoice, Process Payment |
Entity Relationship diagrams
Methodology Adopted.
The Agile (Scrum) Methodology will serves as the best methodology for the Inventory Management System (IMS) because it provides flexibility alongside iterative development and continuous feedback mechanisms (Slamet et al.,2024).Agile segmentation of development work into Sprints allows projects to reach delivery milestones regularly with enough room for change modifications. Scrum promotes efficient team collaboration through development of daily standups along with sprint reviews among developers’ testers and stakeholders. The Agile methodology enhances management quality by directing efforts toward fundamental features which include authentication and order processing and payment integration. The deployment method accelerates delivery which enables straightforward combination of security features and system improvements and new functionality and keeps operational reliability intact.
Design patterns to be implemented.
The inventory management system be developed using 3 designs patterns which include and not limited to; the factory patterns which adopted ensures objects creation is simplified. Hence this will enhance modularization. The single patterns were also applied during the development of the database. This is essential as it reduces redundancy and improves perfomance.
The observer patterns were adopted through for Alert stock and notifications. This inventory changes trigger through automatic updates. The Observer Pattern is useful for stock alerts and notifications, where inventory changes trigger automatic updates (Resmi Rachmawati et al., 2023).
Development plans.
The development plans will encompass the following resources and tools. This enhances the following process.
- Programming language to be used: Python and MYSQL.
- Resource: Visual studio code.
- Front end:HTML,CSS and Javascripts
- Version Control: GitHub
- Cloud Hosting: AWS
- CI/CD: Docker for containerization
Features Implementations (Tentative Priority)
| sprint | Feature |
| Sprint 1 | User Authentication & Role Management |
| Sprint 2 | Product & Inventory Management |
| Sprint 3 | Order Processing & Payment Integration |
| Sprint 4 | Report Generation & Stock Alerts |
| Sprint 5 | UI Enhancements & API Integrations |
| Sprint 6 | Testing, Security & Final Debugging |
Testing Plan
Unit Testing: Test individual modules (authentication, inventory updates).
Integration Testing: Ensure components work together (order processing with payment).
Security Testing: Validate authentication, SQL injection, and API security.
Maintenance Plan
Bug Fixing: Establish a regular cycle for patch updates.
Security Updates: Implement vulnerability scanning and data encryption strategies.
Feature Enhancements: Continuously integrate new features based on user feedback.
Prototypes.
Log In
Registration page.
Forgot password
User Dashboard
Key Metrics & Analytics Widgets designs
List of pending orders
List orders
Contact Us
Editing the products
Track orders and submit
Adding new products
Deleting a products
Generation of reports
Notification con pages
Payment page
References
Resmi Rachmawati, O. C., Deyana Kusuma Wardani, Wifda Muna Fatihia, Arna Fariza, & Hestiasari Rante. (2023). Implementing Agile Scrum methodology in the development of SICITRA mobile application. Jurnal RESTI (Rekayasa Sistem dan Teknologi Informasi), 7(1), 41-50. https://doi.org/10.29207/resti.v7i1.4688
Slamet, C., Budiman, I., Al-Amin, M. I., Ramdhani, M. A., & Gojali, D. (2024). Designing a marketplace system to assist incubators in higher education in fostering technopreneurship. TELKOMNIKA (Telecommunication Computing Electronics and Control), 23(1), 90. https://doi.org/10.12928/telkomnika.v23i1.26452
