Student Name: Weight: 5%

Student ID: Marks: /18

Assignment: Creating a Sequence Diagram

Introduction

Each use case in a use case diagram represents part of the functionality of your system, and a sequence diagram visually documents the sequence of steps within one individual use case. In this assignment, you will create sequence diagrams to represent two of the use cases within the system.

Scenario

Refer to the Business Case for Assignments document for the scenario.

Instructions

Working individually, create a sequence diagram for the use cases specified by your instructor. Revise the Class Diagram you submitted in the previous assignment to include the necessary attributes and classes. This is important for the continuity of the project.

Use Microsoft Visio or an equivalent tool and follow the UML standards discussed in class.

Any reasonable assumptions should be documented as notes within your diagram. For example, you may assume that a failed transaction does not result in an infinite loop.

Give your diagrams relevant titles and include your name.

This assignment may be completed during a provided work period or outside of scheduled class time.

Save/export your diagram as a PDF document and upload them to Brightspace.

This assignment is due as per the due date listed on Brightspace.

Marking Criteria

Category	Needs Improvement	Adequate	Good	Marks
Objects	Missing objects. (0 marks)	Most objects are included. (2 marks)	All required objects are included, following the object: class naming convention. (4 marks)	/4
Actors	Missing required actors. (0 marks)	Incorrect symbols used, or actors included without a label. (2 marks)	All relevant actors identified and labelled. Appropriate symbols are used for human and non-human actors. (4 marks)	/4
Lifelines	Missing lifelines. (0 marks)	Some lifelines are missing, or missing a termination point. (1 mark)	Lifelines are included for all actors and objects, with termination points if applicable. (2 marks)	/2
Messages and frames	Missing more than half of the required messages. (0 marks)	Some messages are missing, or errors in line type or arrowhead. (4 marks)	All required messages are included, using the correct line type and arrowhead. Frames are labelled and used correctly. (8 marks)	/8
Total				/18

For the Business Case, it is beneath it;

Business Case: Hotel Booking System

Your friend has a series of rental properties and has asked you to put your ITSD skills to use to build her a booking system. After interviewing her, you generate the following summary of requirements:

Each property will have a landing page that displays the name of the property, its address, the number of beds and bathrooms, and a list of available amenities.

Customers will start their booking in one of two ways:

They can enter their desired dates and see all available properties.

They can choose a specific property and view its availability.

Once the property and dates have been selected, the customer is prompted to enter the number of guests, and their name and contact information.

After these data are entered, the customer is brought to a confirmation page. There is a button to edit, which allows them to adjust their dates, number of guests, name, and email address, or to choose a different property and restart the booking process. When they click the Confirm button, they are redirected to a third-party payment system to pay for the booking.

If the payment goes through, a confirmation code is generated and the customer receives an email with their confirmation details.

If the payment is not successful, the booking remains in pending state and the customer may try again or cancel the booking request.

The system will have a section where customers can input their booking confirmation code to view the details of their reservation, add any additional notes or requests, or request a cancellation. Cancellations made more than 7 days in advance receive a 50% refund.

Staff can see all upcoming visits or all upcoming visits for a specific property. Staff can edit the checkout date of current and future bookings or cancel future bookings. Any changes or cancellations will send an automated email to the customer for their reference.

Cancelled bookings remain on file for six months and completed bookings remain on file for two years.

Important: Do not make any assumptions when designing this system. Ask your client (your instructor) for any needed clarification.

NEED HELP PLS