Business Modeling Project: Squeaky Surf System Design and Modeling

This project presents a detailed business modeling solution for a system, likely for a surf board rental business named Squeaky Surf. The assignment begins with the identification of user stories, outlining the needs and expectations of different user roles such as customers, staff, and administrators. These user stories are then used to create a use case diagram, visually representing the system's main functionalities and interactions. The project continues with the creation of a class diagram, illustrating the system's data structures and relationships, followed by a state machine diagram that models the lifecycle of a surfboard. System sequence diagrams are included to show the message flow between system components. The project also contains a user interface design and an entity-relationship diagram for database structure. The solution demonstrates a strong understanding of business analysis and system design principles, providing a well-structured and comprehensive model of the proposed system. The assignment concludes with a bibliography of the sources consulted.

Running head: BUSINESS MODELING
Business modeling
Name of the Student
Name of the University
Author’s Note:

1BUSINESS MODELING
Table of Contents
User Stories:.....................................................................................................................................2
Use Case Diagram:..........................................................................................................................4
Class Diagram:.................................................................................................................................7
State Machine Diagram:..................................................................................................................8
System Sequence Diagram:.............................................................................................................9
User Interface:...............................................................................................................................10
Entity Relationship Diagram:........................................................................................................11
Bibliography:.................................................................................................................................12

2BUSINESS MODELING
User Stories:
User Story 1: As a customer I want to hire a board from Squeaky Surf.
Acceptance Criteria:
i. Customer can select the boards that are available for hire
ii. Customer must share the identification number
iii. If customer is registered then customer has to be registered first
User Story 2: As a staff I want the customer to pay the deposit first
Acceptance Criteria
i. The customer has a working credit card from where deposit can be debited
ii. The customer is already registered
iii. The system is connected to a card reader which can debit the amount
iv. The system displays the details of the customer
v. The interface allows the staff to select the board and quantity of it
vi. The system automatically shows the deposit amount based on board quantity
User Story 3: As a customer I want the return the board
Acceptance Criteria
i. The customer can return the board to a different tent
ii. The customer can see the charge of the hire collectively of all the boards
iii. The customer will get the cash credited after boards are returned
iv. The staff will get an interface where the damage details can be recorded

3BUSINESS MODELING
v. Based on the damage details, the staff can enter fine amount which will not be
credited
User Story 4: As a staff I want to register the customer into the system
Acceptance Criteria
i. The customer will provide name, address, contact number
ii. The system will provide an identification number to the customer
iii. This identification number will be unique
User Story 4: As an administrator I want to check the stock of boards at each tent
Acceptance Criteria
i. Administrator can categorize the boards available in each tent
ii. Each tent will have different identification number and location
iii. The system will allow creating reports based on boards hired from each tent for a
certain period of time
iv. The system will allow the admin to update the details as manual transportation
may be done to make balance in board availability in each tent
User Story 5: As an administrator I want to send the damaged board for service
Acceptance Criteria
i. The administrator can see the damage status of the boards
ii. They can check move the board to under service status
iii. The admin can also check the status of the board after service is done and if
properly done then can move the board to tents and update board details in tents

4BUSINESS MODELING
User Story 6: As a service provider I want to update the status of the board
Acceptance Criteria
i. The system will to update whether the work is complete
ii. The service provider can also update that board cannot be serviced
iii. They can share the invoice each month for the service provided
iv. The system will make the service payment transfer to bank account after approval
from Admin
Use Case Diagram:

5BUSINESS MODELING

6BUSINESS MODELING

7BUSINESS MODELING
Class Diagram:

8BUSINESS MODELING
State Machine Diagram:

9BUSINESS MODELING
System Sequence Diagram:

10BUSINESS MODELING
User Interface:

11BUSINESS MODELING
Entity Relationship Diagram: