{"id":37780,"date":"2025-03-19T19:30:07","date_gmt":"2025-03-19T09:30:07","guid":{"rendered":"https:\/\/myassignmenthelp.info\/assignments\/?p=37780"},"modified":"2025-03-19T19:30:09","modified_gmt":"2025-03-19T09:30:09","slug":"planning-requirements-modeling-and-analysis-2363630","status":"publish","type":"post","link":"https:\/\/myassignmenthelp.info\/assignments\/planning-requirements-modeling-and-analysis-2363630\/","title":{"rendered":"Planning, requirements modeling and analysis-2363630"},"content":{"rendered":"

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

Institution<\/strong><\/strong><\/p>\n\n\n\n

Student Name<\/strong><\/strong><\/p>\n\n\n\n

Student ID<\/strong><\/strong><\/p>\n\n\n\n

Instructor<\/strong><\/strong><\/p>\n\n\n\n

Date of submission<\/strong><\/strong><\/p>\n\n\n\n

Planning, requirements modeling and analysis (65%)<\/strong><\/strong><\/p>\n\n\n\n

Work Breakdown Structure (WBS) for Inventory Management System (IMS) Development.<\/strong><\/strong><\/p>\n\n\n\n

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

Gantt Chart Based on Agile<\/strong><\/p>\n\n\n\n

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

Usecase:<\/strong>\u00a0Order Processing<\/strong><\/p>\n\n\n\n

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

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

Use case<\/strong><\/strong><\/td>Order Processing<\/strong> <\/td><\/tr>
Actors<\/strong> <\/td>Customer, System <\/td><\/tr>
Preconditions<\/strong> <\/td>Customer must be logged in. At least one item must be in the shopping cart.<\/td><\/tr>
Basic Flow:<\/strong> <\/td>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. <\/td><\/tr>
Post-condition<\/td>Order details are recorded in the system.Order status is updated accordingly.<\/td><\/tr>
Alternative Path<\/td>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.<\/td><\/tr>
Exceptional Path<\/td>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.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Use Case: Inventory Management<\/strong><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
Use case<\/strong><\/strong><\/td>Inventory Management<\/strong><\/td><\/tr>
Actors<\/strong> <\/td>Admin, System <\/td><\/tr>
Preconditions<\/strong> <\/td>The admin must be logged into the system. The inventory database must be accessible.<\/td><\/tr>
Basic Flow:<\/strong> <\/td>The use case starts when the admin<\/strong> selects the inventory management module. The Admin<\/strong> adds, updates, or deletes a product.  The System<\/strong> validates the product data includes Validate Product Data<\/strong>.  The System<\/strong> updates stock levels include Update Stock Levels<\/strong>).   The System<\/strong> generates an updated inventory report includes Generate Inventory Report<\/strong>). The System<\/strong> saves the changes and confirms the operation to the Admin<\/strong>.<\/td><\/tr>
Post-condition<\/td>Inventory data is updated in the system.Stock levels are correctly adjusted.<\/td><\/tr>
Alternative Path<\/td>At step 4, if the stock level of a product falls below the threshold, the system triggers a Low Stock Alert<\/strong> extends Low Stock Alert<\/strong>).   At step 5, if sales trends indicate potential shortages, the system provides Stock Reorder Recommendations<\/strong> extends Stock Reorder Recommendation<\/strong>).<\/td><\/tr>
Exceptional Path<\/td>At step 3, if the Admin<\/strong>\u00a0enters incomplete or incorrect product data, the system displays an error message and prompts for corrections.At step 4, if there\u2019s a database connectivity issue, the system logs the error and notifies the Admin<\/strong>. \u00a0At step 6, all modifications are logged for auditing extends\u00a0Audit Log Entry<\/strong>).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Steps involved in a communication diagram<\/strong><\/strong><\/p>\n\n\n\n