Business Modeling Project - Squeaky Surf - System Analysis and Design

This project focuses on business modeling for Squeaky Surf, a boat rental company. It begins by identifying user stories from customer, inventory manager, staff, and manager perspectives, outlining acceptance criteria for each. The project then constructs a use case diagram to illustrate system processes, accompanied by detailed use case descriptions. Class diagrams are created to represent the system's structure, including relationships between entities. State machine diagrams model the lifecycle of a board, while sequence diagrams detail interactions within a specific use case. The project also includes a user interface wireframe and an entity-relationship diagram for database design. Finally, a bibliography of relevant sources supports the analysis and design components.

Running head: BUSINESS MODELLING
Business Modelling
Name of Student-
Name of University-
Author’s Note-

1BUSINESS MODELLING
Table of Contents
Section 1: User Stories.....................................................................................................................1
Section 2: Use Case Modelling........................................................................................................3
Section 3: Class Diagram Modelling...............................................................................................6
Section 4: State Machine Modelling................................................................................................7
Section 5: Sequence Diagram Modelling........................................................................................8
Section 6: User Interface.................................................................................................................9
Bibliography..................................................................................................................................10

2BUSINESS MODELLING
Section 1: User Stories
User Story 1:
As a customer, I need to put my personal details, and the type of boat that I want to hire.
Acceptance Criteria:
1. The customer will have a unique identification number by which the customer can be
identified in the system.
2. The customer will need to see the details of the boat which they want to hire.
3. The customer needs to pay rent of the boat and they needs to select the payment method.
4. The customers also needs to pay the deposit money for hiring boat from Squeaky Surf.
User Story 2:
As an inventory manager, I have to keep a look on the inventory of the company and maintain
the under supply and oversupply of the boats.
Acceptance Criteria:
1. The manager needs to have an interface to enter the description of the boats that are
currently available in the stock.
2. The inventory manager needs to check the quantity of boats in each location and determine
the undersupply and oversupply of the boat.
3. The inventory manager needs to take the responsibility to transfer the boats from one
location to another.
4. The inventory manager also needs to track all other materials that the company rents the
customer.

3BUSINESS MODELLING
User Story 3:
As a staff of Squeaky Surf, I have to input the details of the customer in the system at the time
of booking.
Acceptance Criteria:
1. There should be a proper interface where staff can input the names and other personal
details of the customer.
2. There should also be a specific list of boats which is to be selected according to the choice
of the customer.
3. The duration of the boat is also to be selected by the staff according to the choice of the
customer.
4. The payment page that is to be handled by the staffs should take the initial payment of the
customer through credit card and should calculate the due payment after returning boat and
other materials.
User Story 4:
As a manager of the company, I have to maintain the quality of boats and maintain their
safety.
Acceptance Criteria:
1. After the quality check of the boats the manager needs to sends the boats for repairing to the
manufacturer.
2. The manager can also buy seconds hand boards from the manufacturer.
3. The manager can contact other manufacturers for boat supply and boat servicing.

4BUSINESS MODELLING
Section 2: Use Case Modelling
Figure 1: Use Case Diagram
(Source: Created by Author)
Use Case Name Login the system
Scenario When the staff login at different location of Squeaky
Triggering When the organization opens in the morning, the staff at every location

5BUSINESS MODELLING
Event needs to login in the system for performing different tasks in the system.
Brief
Description
When the staffs wants to enter boat information in the system or enter the
customer information, the staff needs to login first with own id and
password. After logging in the system, the staffs will be able to input the
information of the customer and enter their deposit and their boat booking
time in the database of the system so that the staffs at other location gets
to know about the time and charge for the boat accordingly.
Actors Staff and the database administrator
Related Use
Case
Checks credentials is the related use case as when the staff enters the
login id and password, the database administrator checks the credentials
and shows message of successful login or unsuccessful login.
Stakeholders Marketing manager, the stock manager, the owner of Squeaky Surf, and
sales manager.
Pre-conditions There should be an interface for the staffs to login in the system.
The staffs should have their personal information stored previously in the
database of the system so that they can log in the system at the time of
work.
Post-Conditions The user id and password that are submitted by the staff should be valid.
The interface should show successful login message after login.
The staff will be able to enter the name and other details of the customer
in the system.
Flow of
Activities
Actor System
1. Enter Login userID 1.1 The system validates the userid and

6BUSINESS MODELLING
and password password.
2. The actor clicks on
the login button.
2.1 If the credentials matches, then the system
shows login successful, otherwise try again
message is popped up.
Exception
Condition
1. The interface is not good.
2. The network connectivity is not good.
Use Case Name Maintains the stock in each location
Scenario Each location needs to check with over stock and under stock.
Triggering
Event
When the quantity of stocks becomes low in a particular location and
there is a need of shuffling the stocks from one location to other.
Brief
Description
The customers can takes the boats and other materials from one location
of Squeaky Surf to some other location, the stock at one location increases
while on other location decreases. So, the staffs need to relocate them as
required. There should be equal number of boards available in each of the
locations and for that this use case is to be carried out.
Actors Staff and database administrator
Related Use
Case
View Stocks
Stakeholders Marketing manager, the stock manager, the owner of Squeaky Surf, and
sales manager.
Pre-conditions The staffs needs to view the stocks of a particular location.

7BUSINESS MODELLING
If the stock is less than the preferred stock, then this use case is carried.
The quality of the boards are also to be checked if they are in need of
replacement.
Post-Conditions The stocks are relocated from one location to another after they are
calculated.
The stocks that will be relocated should be in good quality so that it does
not need any servicing.
Flow of
Activities
Actor System
1. The actor needs
view the stocks
1.1 The system shows the stocks that are
available.
2. The actor needs to
relocate the stocks
2.1 The system shows the updated stocks after
relocating.
Exception
Condition
1. The system should calculate proper quantity to stocks for relocation.
Section 3: Class Diagram Modelling

8BUSINESS MODELLING
Figure 2: Class Diagram of Squeaky Surf
(Source: Created by Author)

9BUSINESS MODELLING
Section 4: State Machine Modelling
Figure 3: State Machine Diagram of Squeaky Surf
(Source: Created by Author)

10BUSINESS MODELLING
Section 5: Sequence Diagram Modelling
Figure 4: Sequence Diagram of Squeaky Surf
(Source: Created by Author)

11BUSINESS MODELLING
Section 6: User Interface
Figure 5: Wireframe of Squeaky Surf
(Source: Created by Author)

12BUSINESS MODELLING
Section 6: Entity Relationship Diagram
Figure 6: Entity Relationship Diagram
(Source: Created by Author)

13BUSINESS MODELLING
Bibliography
Afanasyev, Alexander, and Nikolay Voit. "MULTIAGENT SYSTEM TO ANALYSE
MANUFACTURING PROCESS MODELS." In Uncertainty Modelling in Knowledge
Engineering and Decision Making: Proceedings of the 12th International FLINS Conference, pp.
444-449. 2016.
Newman, Russell, Victor Chang, Robert John Walters, and Gary Brian Wills. "Model and
experimental development for Business Data Science." International Journal of Information
Management 36, no. 4 (2016): 607-617.
Morecroft, John DW. Strategic modelling and business dynamics: A feedback systems approach.
John Wiley & Sons, 2015.
Abdelkafi, Nizar, and Karl Täuscher. "Business models for sustainability from a system
dynamics perspective." Organization & Environment 29, no. 1 (2016): 74-96.