University Business Modeling Assignment: UML Diagrams Solution

This document presents a comprehensive solution to a business modeling assignment focusing on UML diagrams. The solution begins by identifying user stories and their acceptance criteria, which serve as the foundation for the subsequent use case modeling. The use case descriptions detail the scenarios, actors, and flows of activities for various processes, such as board renting, reallocation, customer feedback, and purchasing. Class diagrams are then developed to model the system's structure, followed by state machine diagrams illustrating the lifecycle of a board. A system sequence diagram is provided to demonstrate interactions within a selected use case. The assignment further includes user interface prototypes and an entity-relationship diagram. Finally, a bibliography is included to support the work. The solution is designed to provide a complete business modeling analysis using UML diagrams, as required by the assignment brief.

Running head: UML DIAGRAMS
UML Diagrams
Name of the Student:
Name of the University:
Author Note

1
UML DIAGRAMS
Identifying User Stories
User Story 1
User Story
As a customer, I would like to rent boards and make payments for them in the system.
Acceptance Criteria
1. Customer should be able to place request
2. Customer deposit should be recorded
3. Customer should receive their refund
4. The boards are to be returned to the system
5. The customer should be able to provide a feedback
User Story 2
User Story
As a staff I want to get notification and reallocate the boards
Acceptance Criteria
1. The over stock and under stock areas are to be identified
2. The reallocation is to be done by the staffs
User Story 3
User Story
As a management user I want to view the feedbacks and make a review
Acceptance Criteria
1. The customer feedbacks are to be stored in the system.

2
UML DIAGRAMS
2. The management should be presented the feedbacks
3. The review of the management is to be stored in the system
User Story 4
User Story
As Wax on wax off, I want to sell second hand boards.
Acceptance Criteria
1. Customer should be able to purchase the second hand boards.
Use Case modelling
Use Case Descriptions
Use Case Description for Board Renting
Use Case Name Board Renting
Scenario The customer would be renting a board and making the payment of
the rent involved.
Triggering event The request for renting
Brief Description The customer would be requesting for a board and board would be
allocated to him whenever a board is made available by the system.
Actors Customers, Staffs
Related Use Cases Board Renting, Return Board, Make Deposit
Stakeholders Customers, staffs, system
Preconditions Requesting for a board

3
UML DIAGRAMS
Post conditions Deposit money
Flow of activities Actors System
1. Request board
2. Rent Board
3. Deposit Money
4. Return Board
1. Allocate board
2. Store details
3. Make refund
4. Allocate board
Exception condition In case there are over allocation of boards the reallocation of the
boards are to be done by the staffs in the organization.
Use Case Description for Board Reallocation
Use Case Name Board Reallocation
Scenario The board is to be reallocated by the staffs in case there are over
allocation or under allocation.
Triggering event Over stocking, under stocking
Brief Description The boards would be returned to the stock by the customers
Actors Staffs
Related Use Cases Identify overstocking, identify understocking
Stakeholders Staffs
Preconditions Identify overstocking, identify understocking
Post conditions Refund money
Flow of activities Actors System
1. Reallocate boards 2. Indicate over stocking or
under stocking
Expression Identifying the over stocking or under stocking condition itself is an

4
UML DIAGRAMS
condition exception.
Use Case Description for Customer Feedback
Use Case Name View Feedbacks
Scenario
Triggering event Feedback
Brief Description The feedbacks are viewed by the management
Actors Management
Related Use Cases Feedbacks
Stakeholders Management, Customer
Preconditions Feedback
Post conditions Review
Flow of activities Actors System
1. Feedback
2. View feedback
3. review
1. Record Feedback
2. Show Feedback
3. Record Review
Exception condition In case there is, no feedback from the customer for a particular,
booking the reviews would not be obtained.
Use Case Description for purchasing boats
Use Case Name Purchase boats
Scenario The Wax On wax off
Triggering event The customers need to buy a boat at cheap price
Brief Description The customers would be buying boats from the Wax On and Wax

5
UML DIAGRAMS
off vendor
Actors Customer, Wax On Wax Off
Related Use Cases Sell Second hand Boats, Purchase Boats
Stakeholders Customer, Wax On Wax Off
Preconditions Sell second hand boats
Post conditions Purchase boats
Flow of activities Actor System
1. Select boat
2. Purchase boats
1. Show boats
2. Record Purchase
Exception condition No exceptions

6
UML DIAGRAMS
Use case Diagram

7
UML DIAGRAMS
Class diagram
State machine diagram

8
UML DIAGRAMS
System sequence diagram
User interface
Prototype 1

9
UML DIAGRAMS
Prototype 2
Prototype 3

10
UML DIAGRAMS
Prototype 4

11
UML DIAGRAMS
Entity Relationship Diagram