Overview of Software Engineering: Use Case and Sequence Diagrams

This article provides an overview of software engineering with use case and sequence diagrams for adding a new host, booking a reservation by youth, and more.

Running head: OVERVIEW OF SOFTWARE ENGINEERING
Overview of Software Engineering
Name of Student-
Name of University-
Author’s Note-

1OVERVIEW OF SOFTWARE ENGINEERING
Question 1:
Use case Diagram for Add new host by admin
Figure 1: Use Case for Add new host by admin
(Source: Created by User)
Use Case Description-

2OVERVIEW OF SOFTWARE ENGINEERING
The use case diagram that is described in this assignment describes adding a new host to
the system of OABS. The admin is responsible for adding a new host to the system. Use case
description. The use case above represents registration of new host to admin in the online
accommodation system. The host can request a registration by the admin or register themselves.
The admin need to login so as to register a new host as indicated in the diagram with an include
relationship between the admin login and register new host use cases. A host can also register
themselves and thereafter be approved by a logged in admin. A registered Host can then login to
the system. The straight lines represent Association relationship and the dotted line with arrow
represent include relationship. Both host and Admin are primary actors. Registration approval or
rejection by the admin includes host registration. The host have to register for approval or
rejection by the admin to occur, thus include relationship between Host registration and admin
approval or rejection. Once the host is registered they can login to the system.

3OVERVIEW OF SOFTWARE ENGINEERING
Sequence Diagram for Accepting or Rejecting a Host Request
Figure 2: Sequence Diagram for Accepting or Rejecting a Host Request
(Source: Created by User)
The classes associated with the host are facility, accommodation and reservation. A
composition relationship exists between host and facility. Facility cannot exist without the host.
A facility belongs to host. A has one to many relationship exists whereby a host can have one or
many facilities but a facility can only belong to one host. A reservation must have a host
associated with. A reservation can only be associated with one host but a host can have many
reservations. Host provides accommodation to the traveler thus there is a composition
relationship between host and accommodation as that are cannot be accommodation without a

4OVERVIEW OF SOFTWARE ENGINEERING
host. The host needs to login to the account of the OABS. Then the server forwards the details of
the host to the admin for approval or rejection. The admin then checks the server for approving
the details of the host and then decides to approve or to reject the host request.

5OVERVIEW OF SOFTWARE ENGINEERING
Sequence Diagram for Sending message to the Host
Figure 3: Sequence Diagram for Sending message to the Host
(Source: Created by User)
In this sequence diagram of sending a message to host. The admin can send message to
the host and the host can reply to the message of the admin. The admin firsts sends message to
the server of OABS and then the message is send to the host and then the host reply accordingly.

6OVERVIEW OF SOFTWARE ENGINEERING
Sequence Diagram for Promoting the Host
Figure 3: Sequence Diagram for Promoting the Host
(Source: Created by User)
The admin also has the accessibility to promote the host. The host sends the request of
promotion to the admin through the server and the server then forwards the message to the admin
for approval. If the user approves the request for the promotion, then the host is promoted to the
next level.

7OVERVIEW OF SOFTWARE ENGINEERING
Question 2:
Use Case for booking a reservation by youth
Figure 4: Use Case for Book a reservation by youth
(Source: Created by User)

8OVERVIEW OF SOFTWARE ENGINEERING
Classes associated with reservation are paymentTxn, host, accommodation, traveler and
group. A composition relationship exists between traveler/group. A reservation cannot exist
without a traveler or a group of travelers. Traveler can have zero or more reservations. Group can
also have zero or more reservations. A reservation can only belong to one group or one traveler.
A reservation must be associated with one host bur a host can be associated with one or more
reservations. A payment transaction can only be associated with one reservation but a reservation
can be paid in several transactions. Reservation fulfils accommodation. A reservation can be
associated with zero or many reservation. The use case above shows the use case for booking a
reservation. The use case for making reservation for youth includes many work. The youth first
register on the OABS network for doing a reservation. After successful reservation, the youth
can search for rooms that are available on the network server. The youth can also make a group
booking form the host. The user can contact the host to make a group booking for OABS. The
youth also needs to select the date of booking that the youth wants and proceeds with the
booking if rooms is available. The youth also has the ability to cancel the booking if the user
wants to cancel the trip. The trip that is selected by the host can be canceled. The youth involved
in the system can also give feedback about the host in their system if the host is also involved
with the system.

9OVERVIEW OF SOFTWARE ENGINEERING
State Transition Diagram for Registering on OABS
Figure 5: State Transition Diagram for Registering on OABS
(Source: Created by User)
This above diagram shows about registering of the youth in the network of OABS. When
a new youth wants to arrive in the system, then the youth has to register on the system. The
youth can register by entering the details on the server of the OABS. The admin accepts the
registration process or can even reject them. If the registration is accepted by the admin, the
server of the system stores the details in the server and the registration is successful. If the
registration is rejected by the admin, then the admin, the youth needs to enter all the details again
to proceed with the registration.
State Transition Diagram for Booking Room

10OVERVIEW OF SOFTWARE ENGINEERING
Figure 6: State Transition Diagram for Booking Room
(Source: Created by User)
The room booking system of OABS, the youth selects the rooms first and requests the
room for some selected date. If room is available for the selected date, then the rooms gets
confirmed to the client. The room that is confirmed can also be canceled by the youth or the host
who books a room. If the selected room is not available, then the booking is kept on hold in the
waiting list. If the room gets vacant by the time, the room is allocated to the youth and if not, the
rooms booking gets cancelled automatically.

11OVERVIEW OF SOFTWARE ENGINEERING
Question 3:
Activity Diagram for Add a New Host
Figure 7: Activity Diagram for Add a New Host
(Source: Created by User)
Question 4:
The prototyping tool that can be used for verifying the client requirement is Balsamiq Software
application tool. This is wire framing tool, which helps the developer to t work faster as well as

12OVERVIEW OF SOFTWARE ENGINEERING
smarter. The tool produces a good experience sketching representing the design on a whiteboard.
This tool help to design the wireframes fast. But for using the Balsamiq tool, the developer needs
a little time as well as effort and can redesign when needed.

13OVERVIEW OF SOFTWARE ENGINEERING
Bibliography
Rumbaugh, James, Grady Booch, and Ivar Jacobson. The unified modeling language reference
manual. Addison Wesley, 2017.
Wang, Chunhui, Fabrizio Pastore, Arda Goknil, Lionel Briand, and Zohaib Iqbal. "Automatic
generation of system test cases from use case specifications." In Proceedings of the 2015
International Symposium on Software Testing and Analysis, pp. 385-396. ACM, 2015.
Jena, Ajay Kumar, Santosh Kumar Swain, and Durga Prasad Mohapatra. "A novel approach for
test case generation from UML activity diagram." In Issues and challenges in intelligent
computing techniques (ICICT), 2014 international conference on, pp. 621-629. IEEE, 2014.
Yue, Tao, Lionel C. Briand, and Yvan Labiche. "aToucan: an automated framework to derive
UML analysis models from use case models." ACM Transactions on Software Engineering and
Methodology (TOSEM) 24, no. 3 (2015): 13.
Da Silva, Alberto Rodrigues. "Model-driven engineering: A survey supported by the unified
conceptual model." Computer Languages, Systems & Structures 43 (2015): 139-155.