Business Modelling for Desklib

This document provides an overview of business modelling for Desklib, including user stories, use case modelling, class diagram modelling, state machine modelling, system sequence diagram, user interface design, and database modelling. It covers topics such as identifying user stories, use case descriptions, class diagrams, state machine modelling, system sequence diagrams, user interface design, and database modelling. The document also includes references to relevant literature.

Assignment Part B –
Business modelling
Section 1 - Identifying user stories
User story1
Customer need to hire a board.
Acceptance criteria.
1. Customer request for a board.
2. Search for board
3. Pays deposit.
4. Customer receives board.
5. Transaction is complete.
User story 2
Customer makes payment.
Acceptance criteria.
1. Board is requested.
2. Customer uses credit card to pay deposit.
3. Customer full pay all charges.
User story 3
Brain’s board shop Sells and repair boards.
Acceptance criteria.
1. Company need new board and repairing of old one
2. Order of boards is made.
User story 4
Returning board.
Acceptance criteria.
1. Customer used board.
2. Customer is satisfied.
3. Deposit is given back to customer.
4. Customer pays all charges.
Page | 1

Section 2 - Use case modelling.
Sommerville (2016) suggested that modelling using uml languages ensures requirements are
collected during modelling.
Table 1 shows use case descriptions of Renting system
USE CASE #1 Renting board
Initiating Actor Squeaky Surf.
Actor’s goals To hire board
Participating actors Staff
Pre-conditions The CUSTOMER has not yet paid for deposit.
Post-conditions Customers pays deposit and a board is given to
customer.
Success Scenario i. Customer receives board.
ii. Customer returns good.
USE CASE #2 Repairing and selling boards
Initiating Actor Brain’s board shop
Actor’s goals To repair and sales board.
Participating actors Staff
Pre-conditions The staff identify there is need to repair and buy
new boards.
Post-conditions Inquires of repairing and buying boards are
received from Squeaky Surf.
Success Scenario i. Boards are available.
ii. WaxOff-WaxOn repairs and sells
broads.
USE CASE #2 Payment
Initiating Actor customer
Actor’s goals To pay for a board
Participating actors Payment system
Pre-conditions Deposit is not yet paid
Post-conditions Deposit is paid and customer given boards.
Customer returns board and pays for bills.
Success Scenario i. Customer has money to pays for charges.
Page | 2

ii. Deposit is paid.
iii. Charges are settled
Page | 3

Diagram 1 below showing use case diagram of Board Rental system.
Section 3 – Class diagram modelling.
Diagram 2 below shows a class diagram of board rental system
Page | 4

Section 4 – State Machine modelling.
Figure 1 below shows state machine modelling of board rental system.
Page | 5

Section 5 – System Sequence Diagram
Figure 2 below shows use case renting sequence diagram
Page | 6

Section 6 - Designing the user interface
Figure 3 belows shows a loging user interface of renting system.
Figure 4 below shows a dashboard of renting system.
Page | 7

Section 7 – Modelling the data base
Pressman (2016) suggested that Entity relationship diagrams show real world problems and can
be transferred to real system
Figure 5 below shows ERD of renting system.
Page | 8

References.
Sommerville, I (2016). Software engineering (10th Ed.).
University of St Andrews, Scotland: Pearson.
Pressman, S,R,Ph.D. (2017).Software Engineering. Practitioner’s Approach (8thEd.).
New York, McGraw-Hill.
Page | 9