Software Engineering
Uploaded by
Harry BorthSoftware Engineering
Uploaded by
Harry Borth1.
Introduction
Global Tech Corporation, a leading technology company, embarked on an ambitious
project to develop a next-generation automated infrastructure system to support
warehouse management. As part of this initiative, the company decided to implement
a new Inventory Management System (IMS) to streamline operations in Nepal. However,
due to inadequate system design and analysis, the initial implementation of the IMS
was unsuccessful. The system lacked modularity, scalability, and maintainability,
leading to operational inefficiencies, financial losses, and customer
dissatisfaction.
In response to these challenges, Global Tech Corporation has decided to place a
strong emphasis on proper system design and analysis for future projects. The goal
is to avoid repeating past mistakes and to ensure that the new system is robust,
efficient, and capable of meeting the company's operational needs. The proposed IMS
will incorporate Object-Oriented Analysis and Design (OOAD) principles to create a
system that is modular, scalable, and easy to maintain.
Specification
The proposed Inventory Management System (IMS) will include the following key
functionalities:
User Access Control:
The system will allow users, including Admin and Customer, to register and log in
to access their specific roles and functionalities.
Purchase Order Management:
Add Purchase: Users will be able to record new purchases of products from
suppliers.
View Purchase: Users can review past purchase details, with the option of comparing
prices between similar products.
Report Generation:
Purchase Report: Tracks in new inventory acquisitions, detailing quantities, costs,
and suppliers.
Sales Report: Provides information on total sales, quantities, and profit/loss over
different periods to aid decision-making for admins.
Sales Management:
The system will allow users to view sales orders, delivery methods, addresses,
contact information, and dispatching details.
Product Management:
Add Product: Enables users to input new products into the inventory system.
View Product: Provides quick access to current stock levels, sales history, and
supplier data.
Payment Processing:
The system will include a secure payment option for buyers to pay for their
purchases. Payment data will be securely stored and integrated with the inventory
management system.
These features are designed to address the inefficiencies of the previous system
and provide a comprehensive solution for managing inventory, sales, and customer
interactions. By implementing these functionalities, Global Tech Corporation aims
to improve operational efficiency, reduce financial losses, and enhance customer
satisfaction.
2. Planning Diagrams WBS and Gantt Chart
Figure 1 2. Planning Diagrams WBS and Gantt Chart
3. Use Case Diagram
Figure 2 use case diagram
4. High-Level Use Case Description:
1.1 High-Level Use Case Description for Register User:
Use Case: Register User
Actor: Customer / Admin
Description: The Register User use case allows a new user (or Admin) to create an
account in the Inventory Management System (IMS). The user provides personal
details such as name, email address, physical address, and a secure password. The
system validates the input data to ensure it meets the required criteria (e.g.,
valid email format, strong password). Once the details are validated, the system
registers the user in the database and sends a confirmation email containing a One-
Time Password (OTP) to the user’s email address. The user must verify their email
by entering the OTP, after which they are redirected to the login page to access
the system. This process ensures that only legitimate users can register and access
the system, enhancing security and data integrity.
Expanded Use Case Description:
Use Case: Register User
Actor: Customer / Admin
Description: The new user submits personal details such as name, email, address,
and password, which are validated and registered in the system. Upon successful
registration, the user receives a confirmation message and can log in to the
system.
Typical Course of Events:
Actor Actions
System Response
1. The user enters personal details (name, email, password, address, etc.).
2. The system validates the details entered by the user.
3. The system sends a confirmation message with an OTP to the user’s email.
4. The user receives the confirmation message and submits the OTP to the server.
5. The system verifies the OTP and redirects the user to the login page.
6. The user logs into the system with registered credentials.
7. The system authenticates the user and grants access to its resources.
Alternate Course of Events:
Line 2: If the user submits incomplete or invalid information, the system reverts
to Line 1 and prompts the user to re-enter the details.
Line 2: If the email submitted by the user is already registered, the use case ends
with a message prompting the user to either log in or recover their password.
Line 5: If the user submits an expired OTP, the system reverts to Line 3 and sends
a new OTP to the user’s email.
1.2 High-Level Use Case Description for Make Payment:
Use Case: Make Payment
Actor: Customer
Description:
The Make Payment use case allows a customer to pay for the products they have
purchased in the Inventory Management System (IMS). The customer selects the items
they wish to purchase, and the system calculates the total amount. The customer
then provides payment details (e.g., credit card information), which are validated
by the system. Upon successful validation, the payment is processed, and a
confirmation message is sent to the customer. This use case <<includes>> validating
the payment and <<extends>> sending a confirmation message to ensure a secure and
user-friendly payment process.
Expanded Use Case Description:
Use Case: Make Payment
Actor: Customer
Description:
The Make Payment use case allows a customer to pay for the products they have
purchased in the Inventory Management System (IMS). The customer selects the items
they wish to purchase, and the system calculates the total amount. The customer
then provides payment details (e.g., credit card information), which are validated
by the system. Upon successful validation, the payment is processed, and a
confirmation message is sent to the customer. This use case <<includes>> validating
the payment and <<extends>> sending a confirmation message to ensure a secure and
user-friendly payment process.
Typical Course of Events:
Actor Actions
System Response
1. The customer selects the items to purchase.
2. The system calculates the total amount.
3. The customer provides payment details (e.g., credit card information).
4. The system <<includes>> validates the payment details.
5. If the payment is valid, the system processes the payment.
6. The system <<extends>> sends a confirmation message to the customer.
7. The customer receives the confirmation message.
8. The system updates the inventory and marks the items as sold.
Alternate Course of Events:
Line 4: If the payment details are invalid (e.g., incorrect card number or expired
card), the system prompts the customer to re-enter the payment details.
Line 5: If the payment processing fails (e.g., due to network issues), the system
notifies the customer and allows them to retry the payment.
Line 6: If the confirmation message fails to be sent (e.g., due to an invalid email
address), the system logs the error and notifies the customer to check their
payment status manually.
