Artisans Cooperative Online Ordering System Design

This assignment focuses on designing the Online Ordering Subsystem for an Artisans Cooperative. Students need to create an activity diagram illustrating the system's workflow, followed by structural and dynamic modeling using class diagrams and sequence diagrams. The task involves identifying relevant classes, their responsibilities, and use cases within both the Online Ordering and Inventory Management subsystems.

1.Requirements Gathering
1.1. Owner’ view
Manage Accounts
 Maintain profile
 Manage payment
through gateway.
 Online notifications
Manage contributors
 Allow members create
account
 Add/remove products
from website
Manage products
 Record information on
new products
 Record information on
artist of product
 Record buyer of the
product
Manage sales
 Record information on
amount of product sold
Manage reports
 Weekly reports
 Pay reports for artists
 Monthly reports
payment

1.2. Users
 Business users - Manager and non-manager, contributors
 Information system users – Customers, artists, bank
2. Domain Analysis
1. Domain definition and domain scope
Artisans Cooperative
Domain Scope
Domain Scope Outline
Online ordering All those activities which come directly into contact with ordering orders on online fall
within this domain:
 Registration
 View product
 Manage shopping cart
 Make payment
Inventory
management
All those activities which come directly into contact with managing product stocks fall
within this domain:
 Add Product
 Delete product
 Update product
Sales
management
All those activities which come directly into contact with managing sales fall within this
domain:
 Monitor sales weekly
 Monitor sales monthly
Report
management
All those activities which come directly into contact with generating reports fall within
this domain:
 Generate reports
 Email reports
User
management
All those activities which come directly into contact with managing users fall within this
domain:
 Manage manager/non-manager
 Manage members/contributors
2. Identify the domain concepts from the domain definition and scopes. Categorise the concepts into
processes, functions, roles, objects, and business rules. You need to list them in a domain
dictionary table using the following template:
THIS IS NEED TO BE DONE IN THIS QUESTION?
(ADD MORE CONCEPTS. MAKE SURE YOU COVER ALL TYPES. USE SAME NAMES YOU
USED BEFORE)/.
Artisans Cooperative
Domain Dictionary
Name Type Description
Registration Process Adding a member to add or delete products. The process collects
new or changed personal information for a new or a current
member. Performed by manager
Registration Object The profile for providing platform to add/update product to a
member.
Manager Role Performs registration

A product Object Any artefact managed by the member
Buyer Role Purchase product from online system
Update inventory Process Adding, deleting and updating the stock of product. Performed by
member or manager.
Member Role Add/Delete product
Product catalogue Object It includes product name, id, price and description.
Credit card Object It is used for online payments.
Payment gateway Process It will be integrated for making online transactions.
Shopping cart Object It includes list of items to be purchased.
Sales report Object Weekly and monthly generated reports.
User profile
management
Function Manages all user accounts i.e. add, remove and update an account.
3. Behavioural Modelling
3. Stakeholders of the system
THERE ARE MORE STAKE HOLDERS ADD THEM
(THERE ARE MORE STAKHOLDERS)
Artisans Cooperative
Stakeholders & Actors
Name Description
Contributor A person who is a member of the company and can add/remove products on
online catalogue.
Manager A person who is a member of the company and manages contributors and
inventory.
Non-manager A person who is a member of the company and manages stall related activities.
Buyer A person who purchases an order online.
Managers An entity or a group who manages the website and takes decisions on the basis of
sales report.
Finance staff Purchases items from suppliers, give quotation, generate reports.
ICT officer Manages web portal data, manages product catalogue, order management, etc.
4. Create a Use Case Summary for both the Online Ordering and Inventory Management subsystems
of the Artisans Cooperative
Artisans Cooperative
Online Ordering: Use Case Summary
ID Name Description Actors
100 Make account An online account is created by the customer on
the website.
Customer, Manager
110 Manage shopping
cart
After registration, customer login in the system
and select products and add them in his/her cart.
Customer
120 Make payment Once, he/she finalizes the cart, then he/she
makes payment through either credit card or
PayPal.
Customer
130 Manage notification A notification is sent to customer and manager
on successful order creation
System
140 Manage shopping Customer makes orders through selecting items Customer

cart into the shopping cart.
Artisans Cooperative
Inventory Management: Use Case Summary
ID Name Description Actors
200 Add products An authorized contributor/member adds a
product in the online catalogue through his/her
account.
Contributor
201 Delete product An authorized contributor/member deletes a
product in the online catalogue through his/her
account, if required
Contributor
202 Update inventory When a product is sold on the website, an email
is triggered and manger decreases the count of
that particular product stock.
Manager
203 Manage supply When level of stock goes less than available, then
manager places orders for new stock.
Manager
214 Manage catalogue The contributors are allowed to updates online
catalogue with new or updates in products.
Contributors

5. Use case- online inventory being manually updated after a market stall
Use Case: Update inventory
ID: PO_101
Scope: Inventory management
Priority: 2/10
Summary: Once an order is completed, an email is triggered to the manager and then manager
manually updates the stock of the products.
Primary Actor: Manager/Contributor
Supporting Actors: System (Inventory)
Stakeholders: Manager – Prepare the list of items to be updated
Contributor – Must receive the information about updated stock.
Generalization: -
Include: 200: Search an item
Extend: -
Precondition: -
Trigger: Customer bought the product at a market stall
Normal Flow: 1. Customer makes the payment and order is processed.
2. Contributor/Manager searches for the product ID.
3. Contributor/Manager then decreases the count by number of items delivered to
the customer.
Sub-Flows: -
Alternate Flow/
Exceptions:
2.1.: Member not available then, an email is sent to manager.
2.2 Manager logs in the account using his credentials.
Post-Condition: Inventory has been updated successfully.
Non-Behavioral
Requirements:
-
Open Issues: -
Source: -
Author: [Name]
Revision & Date -
6. Use case diagram – Inventory management sub-system.
PLEASE REMOVE THE CONTRIBUTOR PERSON FROM FOLLOWING ONLY
MEMBER AND MANAGER IS FINE

7. Activity diagram for the Online Ordering subsystem.

I. Structural and Dynamic Modelling
After completing the behavioural modelling, you will continue with structural and dynamic
modelling.
8. Identify classes for both the Online Ordering and Inventory Management subsystems. List each
class, along with responsibilities and the use cases they are associated with, using the following
table templates.
FIX THIS
NEED 5 OF THEM

Artisans Cooperative
Online Ordering: Preliminary Class Candidates
CUSTOMER Responsibilities Use Cases
 customerID  Registration
 customerName  To manage order
 customerAddress  To make payment
 email
 Username
 password
PAYMENT  paymentID  To make Payment
 paymentamount
ORDER  orderID  To Create order
 orderDate  To Manage order
 orderStatus
PRODUCT  productID  To create product
 productName  To delete product
currentStock  To update product
NOTIFICATION notificationID  To generate notification
notificationDate
FIX THIS
NEED 5 OF CANDIDATES
Artisans Cooperative
Inventory Management: Preliminary Class Candidates
Class Responsibilities Use Cases
MEMBER  memberID  Manage inventory
 memberName  Search item
PRODUCT  productID  To create product
 productName  To delete product
 currentStock  To update product
SUPPLIER  suuplierID  To order items
 supplierName 
 address 
 email 
PAYMENT paymentID To make Payment for supplier
paymentamount
ALERT alertID To generate alert for low stock
alertDate
alertForItemID
9. Class diagram with associations and multiplicity information for the Online Ordering subsystem.

10. Sequence diagram for online order on the Artisans Cooperative website.