User Stories and Use Case Modeling for Squeaky Surf

Desklib provides solved assignments and past papers to help students succeed.

User Stories
As Squeaky surf, I want to add the functionality of the service & repair as to replace them to with ex-
surf boards.
Acceptance criteria
 The customer done with the payment before the services & repair.
 The replacement with the ex- surf boards.
 Supplier will add in the portfolio.
 The customer needs to be registered.
As Squeaky surf, I want to track the history records as to avoid the bad brands & to replace the
stocks.
Acceptance criteria
 The system to scan the records.
 The records should be entering in to the system.
 Track the past records that need to be exchanged.
As a customer, I want the functionality to rent the board as it will easy to borrow & return the board
online.
Acceptance criteria
 The customer needs to be register.
 The lookup must be by the account number or the customer name.
 The boards will be sorted by the location.
As a Staff member, I want to use the trailer & pick up to relocate the board as to reduce the
undersupply & oversupply.
Acceptance criteria
 The system need to be detecting the stocks.
 Provide the trailer & pickups.
As a customer, I want the system for payment as to there will not any splitting of bills.
Acceptance criteria
 No bill split on the one customer for the full transaction of rental.
 Deposits will refund at the time of board returning.
 The customer needs the identification on the hiring time.
 The charges of the rental will be applied on the categories.
 The deposit will be applied on the credit card of the customer.

As Squeaky surf, I want the feedback form as to detect the customer problem & to review the
information.
Acceptance criteria
 The feedback form will be review by the staff members & will link the information’s.
 The feedback form will handed to customer for hiring the surf board.
 This will help to get the detail of the customer & board.
As Squeaky surf, I want to add various boards of stocks as to provide the flexibility to the customers.
Acceptance criteria
 The board will available only for limited time.
 It consist Malibu, Longboard, Funboard, fish & Shortboard.
 The system will manage the business effectively & easily.

Use case modelling
Use case name: Add stocks of boards
Scenario: Add boards stock for the customers
Triggering event: If customers need to purchase different &
new boards.
Brief description: this will arise in the marketing & customer
have their choice to select the board
according to them.
Actors: Admin
Related use case:
Stakeholders: staff members & customers
Pre-conditions: Store place is required.
Various other stocks are added.
The customer may select any board.
Post-conditions: The customer need to pay the rent for the

selected boards.
Activities flow: Actors
1. The admin
will overview
the boards.
2. The boards
upload by the
administrator.
3. Approved &
allocate the
board to the
particular
customer.
System
1. The system
show the
boards.
2. Let the
customers
select the
boards.
Exception conditions: 1. The board will not available.
2. The boards will not display.

Class Diagram Modelling

State Machine Modelling

System Sequence Diagram

Modelling the database