Professional Documents
Culture Documents
This Study Resource Was: The Use Case View Is NOT Used For
This Study Resource Was: The Use Case View Is NOT Used For
The use case A may not necessarily be performed every time B is performed;
The use case A has to be performed every time B is performed;
The use case B has to be performed every time A is performed;
None of the above.
QUESTION 2
1. The use case view is NOT used for:
describing the internal behavior of the system;
m
er as
describing the externally visible behavior of the system;
co
describing how users interact with the system;
eH w
understanding the flow of work that an object or a component performs;
o.
defining the behavior of an object in the system.
rs e
ou urc
QUESTION 3
Explain how you can redraw the use case diagram of ‘Restaurant Booking’ system project
o
without the ‘Staff’ actor and making no use of actor generalization. Do the two versions of the
aC s
diagram describe the same facts, from the point of view of the restaurant’s operations?
vi y re
Answer:
This study source was downloaded by 100000828747844 from CourseHero.com on 07-01-2021 03:00:51 GMT -05:00
https://www.coursehero.com/file/70121963/Assesment-3docx/
Please follow the link for redrawn diagram
https://drive.google.com/file/d/1c_dMkJbSKrnOOxJPfaiiJRbKpMDGlCUc/view?usp=sharing
With ‘Staff’ actor removed and making no use of actor generalization, the redrawn use case
diagram is shown below. In such scenario, an explicit presentation of the association with the
Display Bookings use case has been done for both the Receptionist and Head Waiter actors. In
order to simplify the drawing of the associations, the actors have been drawn twice. Note that
the meaning of the diagram is not altered because of this.
In the diagram shown in the question there is an actor Staff who only has the ability to display
bookings. Therefore, even if both figures specify the same capabilities for the Receptionist and
Head Waiter actors, they as not quite equivalent.
Making no use of actor generalization hasn’t made any difference in our case here since this is
a simple diagram. There is not much difference in complexity between the versions and they
m
both describe the same facts from the point of view of the restaurant’s operations. However, in
er as
more complicated diagrams, the use of actor generalization can significantly reduce the number
co
of associations that have to be shown, thus simplifying the diagram.
eH w
In this particular example, I prefer the diagram provided as the solution to the question as it is
o.
rs e
more comprehensive and shows detailed structure of use case. I think it is more convenient to
ou urc
understand the restaurant’s operation by the reference of it.
o
aC s
vi y re
QUESTION 4
1. Extend the description of the ‘Record booking’ use case described in Lesson 3 to cover
ed d
the situation where the receptionist tries to double-book a particular table. Would this be an
ar stu
ANSWER
The following scenario describes a possible approach to this situation where the receptionist
sh
This study source was downloaded by 100000828747844 from CourseHero.com on 07-01-2021 03:00:51 GMT -05:00
https://www.coursehero.com/file/70121963/Assesment-3docx/
3. If the data entered already exists and overlaps with the booking made with the same
table, this means that the table is already reserved. In such case, an error message is issued by
the system to alert the receptionist about overlapping.
4. The receptionist makes the acknowledgement of the error message, and the use case
(reservation process) terminates. No reservation is made at the end.
The provided scenario can be classified as an exceptional course of events. The results have
diverted from the normal flow because of a mistake made by the user.
QUESTION 5
1. How detailed a use case description should be?
A use case diagram is a graphic depiction of the interactions among the elements of a system.
m
er as
A use case is a methodology used in system analysis to identify, clarify, and organize system
co
requirements. In this context, the term "system" refers to something being developed or
eH w
operated such as a mail—order product sales and service web site. Use case diagrams are
o.
employed in UML (Unified Modeling Language), a standard notation for the modeling of real-
world objects and systems. rs e
ou urc
System objectives can include planning overall requirements, validating a hardware design,
testing and debugging a software product under development, creating an online help
reference, or performing a consumer—service—oriented task. For example, use cases in a
o
product sales environment would include item ordering, catalog updating, payment processing,
aC s
The boundary, which defines the system of interest in relation to the world around it.
The actors, usually individuals involved with the system defined according to their roles.
ed d
The use cases, which are the specific roles played by the actors within and around the system.
ar stu
The relationships between and among the actors and the use cases.
is
Th
sh
This study source was downloaded by 100000828747844 from CourseHero.com on 07-01-2021 03:00:51 GMT -05:00
https://www.coursehero.com/file/70121963/Assesment-3docx/
Powered by TCPDF (www.tcpdf.org)