0% found this document useful (0 votes)
9 views3 pages

2-5: Write The Flow of Events and Specify All Fields For The Use Case That You Drew in Exercise 2-4. Do Not Forget To Specify Any Relationships

The document outlines the flow of events for the 'UpdateTariff' use case involving a CentralComputerSystem and ticket distributors, detailing the activation, maintenance, database updates, and acknowledgment processes. It also describes a class diagram for a book and its components, extending it with attributes for each class and introducing an abstract class to consolidate common attributes. Additionally, it mentions a sequence diagram for a 'warehouseOnFire' scenario, specifying the initial message sends among various objects.

Uploaded by

maroelbob045
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views3 pages

2-5: Write The Flow of Events and Specify All Fields For The Use Case That You Drew in Exercise 2-4. Do Not Forget To Specify Any Relationships

The document outlines the flow of events for the 'UpdateTariff' use case involving a CentralComputerSystem and ticket distributors, detailing the activation, maintenance, database updates, and acknowledgment processes. It also describes a class diagram for a book and its components, extending it with attributes for each class and introducing an abstract class to consolidate common attributes. Additionally, it mentions a sequence diagram for a 'warehouseOnFire' scenario, specifying the initial message sends among various objects.

Uploaded by

maroelbob045
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

2-5: Write the flow of events and specify all fields for the use case

UpdateTariff that you


drew in Exercise 2-4. Do not forget to specify any relationships.

Flow of events:
1. The CentralComputersystem activates the "Update tariff'' function of the fickef distributore
availahle on the network.

2. The ticket distributor disables the traveler interface and posts a sign indicating
that the ticket distributor is under maintenance.

3. The ticket distributor waits for the new database from the
CentralComputerSystem.

4.After waiting a minute for the ticket distributors to reach a waiting state, the
CentralComputerSystem broadcasts the new database.

5. The ticket distributor system receives the new database of tariff.

6. After acknowledgment, the ticket distributor enables the traveler interface and
can issue tickets at the new tariff.
7. The CentralComputerSystem checks if all ticket distributors have acknowledged the new database.

2-6: Draw a class diagram representing a book defined by the following


statement: “A book
is composed of a number of parts, which in turn are composed of a number
of chapters.
Chapters are composed of sections.” Focus only on classes and
relationships.

Book

Part

Chapter

Section

This exercise checks the student's understanding of basic aspects of class diagrams, including:
-Classes are represented with rectangles.
-The attribute and operations compartment can be omitted.

2-9: Extend the class diagram of Exercise 2-6 to include the following
attributes:
• a book includes a publisher, publication date, and an ISBN
• a part includes a title and a number
• a chapter includes a title, a number, and an abstract
• a section includes a title and a number.

Book Part Chapter Section

publisher:Person title:String title:String title:String


publicationDate:Date number: Integer number:Integer number:int
iSBN:integer[4] abstract:String
2-10: Consider the class diagram of Exercise 2-9. Note that thePart, Chapter,
and Section
classes all include title and number attributes. Add an abstract class and an
inheritance
relationship to factor out these two attributes into the abstract class.

Numbered Components

Title: String
Number: Integer
Abstract:String

Book Part Chapter Section

publisher:Person title:String title:String title:String


publicationDate:Date number: Integer number:Integer number:int
iSBN:integer[4]

2-13:Draw a sequence diagram for the warehouseOnFire scenario of Figure 2-21.


Include
the objects bob, alice, john, FRIEND, and instances of other classes you may
need.
Draw only the first five message sends.

You might also like