Squeaky Surf Rental System: Business Modeling and System Design Report

Verified

Added on  2023/01/23

|8
|511
|67
Report
AI Summary
This report presents a comprehensive business modeling and system design analysis of a board rental system. It begins with the identification of user stories, detailing customer interactions such as renting boards, paying deposits, and returning boards. The report then employs use case modeling to describe system functionalities, followed by class diagrams, state machine modeling, and system sequence diagrams to visually represent the system's structure and behavior. User interface design, including a login interface and a dashboard, is also provided. Finally, the report includes database modeling using an ERD to illustrate the system's data structure. The report references Connolly and Begg (2015) and Pressman (2017) to support the design methodologies.
Document Page
Assignment Part B –
Business modelling
Section 1 - Identifying user stories
User story1
Customer want to rent a board on squeaky surf renting system.
Acceptance criteria.
1. Customer is already login in system
2. Searches by location and view from available boards.
3. Pay deposit.
4. Indicates number of boards customer need to Rent
5. Board is given to customer.
6. System records a transaction.
User story 2
Customer wants to pay deposit.
Acceptance criteria.
1. Customer already requested for board.
2. Customer uses credit card to pay deposit.
User story 3
WaxOff-WaxOn Sells boards to squeaky surf .
Acceptance criteria.
1. Board are out of stock
2. Staffs orders for new boards.
User story 4
Staff verify feed back form.
Acceptance criteria.
1. Customer already rented board and used them.
2. Customer provides status of boards.
3. Customer is satisfied with boards.
User story 4
Customer returns board.
Acceptance criteria.
1. Customer already used board .
2. Customer is satisfied.
3. Customer is bills are over.
Page | 1
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Section 2 - Use case modelling.
According to Pressman (2017) stated that uml diagrams represents most of requirements of systems.
Table 1 shows use case descriptions of rental system.
Use Case Brief Use Case Description
Renting Customer is using renting system to rent
boards
Depositing Customer uses credit card to deposit payment
Returning boards Customer returns board after using
Pays charges Customers pays bills.
Selling and repair Sells and repairs boards
Page | 2
Document Page
Figure 1 below shows use case diagram of Squeaky Surf Rental system.
Page | 3
Document Page
Section 3 – Class diagram modeling
Figure 2 below shows a class diagram of board rental system.
Section 4 – State Machine modelling.
Figure 3 below shows state machine modelling of board rental system.
Page | 4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Section 5 – System Sequence Diagram
Figure 4 below shows use case renting sequence diagram
Page | 5
Document Page
Section 6 - Designing the user interface
Figure 5 belows shows a loging user interface of renting system.
Figure 6 below shows a dashboard of renting system.
Page | 6
Document Page
Section 7 – Modelling the data base
Connolly and Begg (2015) demonstrated that data modelling enable developer to understand well
requirement of system.
Figure 7 below shows ERD of renting system.
Page | 7
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
References.
Connolly, M. & Begg, C 2015, Database systems A practical approach to
Design, implementation and management. (6th Ed.). Harlow, Essex, England:
Addison-Wesley (Pearson Education Limited).
Pressman, S,R,Ph.D. (2017).Software Engineering. Practitioner’s Approach (8thEd.).
Inc., 1221 Avenue of the Americas, New York, McGraw-Hill.
Page | 8
chevron_up_icon
1 out of 8
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]