Software Engineering Case Study Analysis

This document presents a detailed analysis of a software engineering case study. It includes a breakdown of the system's requirements, flowcharts illustrating the user interactions, and various diagrams such as use case, activity, class, and sequence diagrams. The analysis delves into the responsibilities of different classes and actors involved in the system, providing a comprehensive understanding of the software's design and functionality.

Student details

Contents
Part I: Requirements gathering...................................................................................................................4
1 Owners view of the system..................................................................................................................4
2 Identification of the users of the system..............................................................................................5
Part II: Domain analysis...............................................................................................................................6
3 Domain definitions...............................................................................................................................6
Domain Scope..........................................................................................................................................6
4 Identification of domain concepts........................................................................................................7
Domain dictionary...............................................................................................................................7
Part 111. Behavioral Modelling...................................................................................................................8
5 Stakeholders.........................................................................................................................................8
6 Use case summary................................................................................................................................9
Online ordering....................................................................................................................................9
Inventory management.....................................................................................................................10
7 Complete use case description...........................................................................................................11
8 Use case diagram................................................................................................................................12
9 Activity Diagram.................................................................................................................................13
4 Structural and dynamic modelling..........................................................................................................14
10 Class analysis....................................................................................................................................14
Online ordering subsystem................................................................................................................14
Online inventory subsystem..............................................................................................................14
11 Class diagram....................................................................................................................................15
12 sequence diagram................................................................................................................................16
13 References............................................................................................................................................17

Table of figures
Figure 1: Use case diagram........................................................................................................................12
Figure 2: Activity diagram..........................................................................................................................13
Figure 3: Class diagram..............................................................................................................................15
Figure 4: Sequence diagram......................................................................................................................16

Part I: Requirements gathering
1 Owners view of the system
The following views give a conceptual view of the owner of the system.
Member management Sub-system:
• Managing memberships of the
cooperative by the managers
• Managing member profiles by the
members themselves
Events and stalls management sub-
system:
• Managing upcoming events by
adding, updating or removing event
details by the delegated managers
• Managing the market stalls by assigning
and unassigning to members of the
cooperative. This is done by the
managers
Online inventory subsystem:
• Enabling the members to manage
items by adding, updating or
removing items.
• Enabling the managers to manage
items for the members by adding,
removing and updating items

Online ordering sub-system:
• Enabling the customers to view
different items available for sale by
different members of the cooperative.
• Enabling the customers to create and
login to their accounts
• Enabling the customers to checkout
items and pay for them via PayPal or
Visa
Online Sales service sub-system:
• Accurately generating reports on a
weekly basis to be sent to the
members and the cooperative’s
accountant.
Online Accounting sub-system:
• Enabling the managers to efficiently
record payments paid to members
• Enabling the managers to record
arrears resulting from managerial
tasks.
• Enabling the accountant to view
records of payments
2 Identification of the users of the system
 Business users
 Cooperative members- Members of the cooperative offering items for sale
 Customers- purchase products from various members using the online ordering sub-
system

 Information system users
 Managers- Managers in charge of managing the cooperative by creating member
accounts, recording payments and arrears and managing the online catalogue system
for the members.
 Accountant- Accountant of the cooperative in charge of handling the cooperative’s
financial affairs.
Part II: Domain analysis
3 Domain definitions
 Member management sub-system
 Events and Stall management sub-system
 Online inventory subsystem
 Online ordering subsystem
 Online sales service subsystem
 Online accounting subsystem
Domain Scope
Artisans cooperative
Domain Scope
Domain Scope Outline
Member management The member management subsystem
manages member accounts creation and
management after the accounts have been
created.
Event and stall management The event and stall management sub-system
handles the creating of events, adding of
stalls, assigning and unassigning of stalls to
the members
Inventory management The online inventory subsystem is responsible
for managing the member products by adding,
removing or updating a product by the
member or the manager on behalf of an
absent member
Order management The online ordering subsystem is responsible
for creation of customer accounts, addition of
items to cart and payment for the items

checked out by the customer.
Sales service management The sales management subsystem is
responsible for generation of sales reports on
a weekly basis. The reports are sent to the
members
Accounting management subsystem The online accounting subsystem is
responsible for recording of payments to
members and recording of arrear by
managers. The information is viewed by the
accountant through this subsystem
4 Identification of domain concepts
Domain dictionary
Artisans cooperative
Domain Dictionary
Name Type Description
Sending request of member
account creation
Responsibility The managers are responsible
for sending requests for
account creation for new
members to the website
service provider.
Event management Process Event management is done by
the managers whereby they
add, update or remove events
Stall management process Stall management is done by
managers who are responsible
of adding, updating or
removing new stalls and then
assigning and unassigning of
the stall to the members
Product management Process The members are responsible

for adding, updating and
removing products from their
inventory by using this
process.
Customer registration Process New customers register to the
system through this process
after which they can starting
adding items to the cart and
checking them out.
Raising queries process Customers can raise queries
using this process. Queries
are raised on a certain
product.
Responding to queries Responsibility Members are responsible for
responding to queries raised by
customers concerning their
products.
Ordering items Process Customers can make an order
for items by use of this
process
Sending sales report to
customers
Role Appointed managers are
supposed to send the reports
generated by the sales service
to customers
Part 111. Behavioral Modelling
5 Stakeholders
Artisans cooperative
Stakeholders and actors
Name Description
Members Cooperative’s artisans who offer different

products for sale.
Managers Member of the cooperative appointed to
manage the cooperative throughout the year.
Customers Buy products using the online ordering sub-
system.
Accountant Handles the financial services of the
cooperative.
6 Use case summary
Online ordering
Growing Abundance
Online Ordering: Use Case Summary
ID Name Description Actors
1 Viewing of items The customer views
different items
available for sale.
Logged in customers
and non-logged in
customers
2 Addition of items to
the cart
Customer adds items
to the cart
Customer
3 Checking out Customers checks out
items in the cart to
make an order
Customer
4 Payment Customer male’s
payment for the items
he or she has checked
out.
Customer
5 Raising a query for a
certain product
This use case
involves raising of a
query about a product
Customer

6 Responding to a
query
This use cases
involves responding
to a query raised by a
customer.
Customer, manager
7 View orders This use case
involves viewing
orders placed by a
customer
Customer, manager
8 Customer login This use case
involves the customer
logging in to
checkout items.
Customer
9 Customer register This use case
involves registration
of a customer to the
system
customer
Inventory management
Growing Abundance
Online Ordering: Use Case Summary
ID Name Description Actors
1 Member login The member logins
to the system through
this use case
Member
2 Manage product A product is managed
through the use of this
use case. This includes
adding a product,
Member, Manager

updating a product or
removing a product
7 Complete use case description
Use Case: Update product
ID: #001
Priority: High
Summary: The member updates a product after a market
stall through this use case.
The manager can do it on behalf of the
member if the member is absent
Primary Actor: Member
Supporting Actors: Manager (If the member is unavailable)
Stakeholders: Business stakeholders and operational
stakeholders
Generalization:
Include: Fetching the product
Extend:
Precondition: The member must be logged in to their
account for them to update a roduct
Trigger: Update product link
Normal Flow:  Customer selects a update product
 Customer selects the product
 Customer enters the new quantity
 Customer saves the quantity
 System saves the product
Sub-Flows: Save product
 System checks the new quantity
 System saves the quantity if its correct
Alternate Flow/ Exceptions: The quantity entered is wrong (Is not an
integer)

 System prompts the user to enter the
correct amount.
Post-Condition: Save button is pressed
Non-Behavioral Requirements: The website should fetch details of a product
very fast
Open Issues: The Credit card details are invalid.
Users selects an invalid option for bookings.
Source: Given Case study
Author: Author of the document
Revision & Date 06-10-2017
8 Use case diagram
Figure 1: Use case diagram

9 Activity Diagram
Figure 2: Activity diagram

4 Structural and dynamic modelling
10 Class analysis
Online ordering subsystem
Artisans Cooperative
Online Ordering: Preliminary Class Candidates
Class Responsibilities Use Cases
customer  Adds items to cart
 Logins to his or her account
 Add item to cart
 Login
Order  Items in the cart and the details of the
customer make up an order
 Checkout items
 Make payment
Query  A query is raised by the customer on a
certain product
 Raise query
 View query
payment  Payment made is equivalent to the order  make payment
Payment
mode
 Used to make payment  Make payment
cart  Contains items  Add item to cart
product  Products are added to the cart  Add item to the cart
 View products
email  Notification email is sent to the
appropriate member or manager when
an order is successful
 Make payment
Online inventory subsystem
Artisans Cooperative
Inventory Management: Preliminary Class Candidates
Class Responsibilities Use Cases
member  Manages products in the inventory after
a market stalls or an event
 Add product
 Update product
 Delete product

manager  Manages products on behalf of the
member is the member is not available
 Add product
 Update product
 Delete product
11 Class diagram
Figure 3: Class diagram

12 sequence diagram
Figure 4: Sequence diagram

13 References
Booch, G. (1999). The unified modeling language user guide. Google Books.
Fowller, M. (1997). UML distilled. Google Books.