Software Engineering: Use Case Description, Prototype Designing, and System Requirements

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student:
Name of the University:
Author Note

1
SOFTWARE ENGINEERING
Task 1
Use Case description: Add new host by admin
Use Case Name: Add new host
Scenario: The admin would be able to add new host.
Triggering Event: The admin would be entering the details of the host.
Brief Description: The admin would be able register the host into the new system.
Actors: The Admin
Related Use Case: Not applicable
Stakeholders: The host
Precondition: The host has to provide the details to the guardians.
Post Condition: The Admin can put the approved hosts on the reserve list
Flow of Activities: Actor System
1. Enter host details
2. Register host
1. Accept details
2. Store the details of the host
Exception Conditions: The host is already registered to the system.

2
SOFTWARE ENGINEERING
Sequence Diagram
Task 2
Use Case description: Book a reservation by youth
Use Case Name: Book a reservation
Scenario: The youth will make a booking for the group.
Triggering Event: The search and book the available rooms.
Brief Description: The youth would be able to search the available rooms and
Actors: The Youth
Related Use Case: The youth can select the dates for the travel.
Stakeholders: The youth

3
SOFTWARE ENGINEERING
Precondition: The youth has be registered in the system.
Post Condition: The youth should be paying the booking fees in advance.
Flow of Activities: Actor System
1. Enter search criteria
2. Select the rooms
3. Make payment
1. Show the list of available
rooms.
2. Request dates
3. Booking confirmation
Exception Conditions: The rooms are not available for service.