©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
CEN4010 - Module 4 Study Guide Solutions
UML (Unified Modeling Language) - ANSWER✔✔--is a notation that resulted from the unification of
OMT (Object Modeling Technique) and OOSE (Object Oriented Software Engineering).
-Provides a standard notation that can be used by all object-oriented methods.
-Is composed of multiple notations or diagrams:
--Use Case Diagrams
--Class Diagrams
--Sequence Diagrams
--State Chart Diagrams
--Activity Diagrams
Pareto Principle - ANSWER✔✔-You can solve 80% of the modeling problems by using 20% UML
UML Diagrams - ANSWER✔✔--Use case diagrams
--Describe the functional behavior of the system as seen by the user
Page 1/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
-Class diagrams
--Describe the static structure of the system: Objects, attributes, operations and associations
-Sequence diagrams
--Describe the dynamic behavior between objects of the system
-State chart diagrams
--Describe the dynamic behavior of an individual object
-Activity diagrams
--Describe the dynamic behavior of a system, in particular the workflow.
Use Case Diagram - ANSWER✔✔--Used during requirements elicitation and analysis to represent
external behavior ("visible from the outside of the system")
-An Actor represents a role, that is, a type of user of the system
-A use case represents a class of functionality provided by the system
-Use case model: The set of all use cases that completely describe the functionality of the system.
Use Case Diagram: Actors - ANSWER✔✔--An actor is a model for an external entity which interacts
(communicates) with the system:
Page 2/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
--User
--External system (Another system)
--Physical environment (e.g. Weather)
-An actor has a unique name and an optional description
-Examples:
--Passenger: A person in the train
--GPS satellite: An external system that provides the system with GPS coordinates.
Use Case Diagram: Textual Description - ANSWER✔✔--Use cases can be described textually, with a focus
on the event flow between actor and system
-The textual use case description consists of 6 parts:
1.Unique name
2.Participating actors
3.Entry conditions
4.Exit conditions
5.Flow of events
Page 3/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
6.Special requirements.
-Textual Use Case Description Example
1. Name: Purchase ticket
2. Participating actor: Passenger
3. Entry condition:
--Passenger stands in front of ticket distributor
--Passenger has sufficient money to purchase ticket
4. Exit condition:
Passenger has ticket
5. Flow of events:
--1. Passenger selects the number of zones to be traveled
--2. Ticket Distributor displays the amount due
--3. Passenger inserts money, at least the amount due
--4. Ticket Distributor returns change
--5. Ticket Distributor issues ticket
Page 4/55
FIRST PUBLISH OCTOBER 2024
CEN4010 - Module 4 Study Guide Solutions
UML (Unified Modeling Language) - ANSWER✔✔--is a notation that resulted from the unification of
OMT (Object Modeling Technique) and OOSE (Object Oriented Software Engineering).
-Provides a standard notation that can be used by all object-oriented methods.
-Is composed of multiple notations or diagrams:
--Use Case Diagrams
--Class Diagrams
--Sequence Diagrams
--State Chart Diagrams
--Activity Diagrams
Pareto Principle - ANSWER✔✔-You can solve 80% of the modeling problems by using 20% UML
UML Diagrams - ANSWER✔✔--Use case diagrams
--Describe the functional behavior of the system as seen by the user
Page 1/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
-Class diagrams
--Describe the static structure of the system: Objects, attributes, operations and associations
-Sequence diagrams
--Describe the dynamic behavior between objects of the system
-State chart diagrams
--Describe the dynamic behavior of an individual object
-Activity diagrams
--Describe the dynamic behavior of a system, in particular the workflow.
Use Case Diagram - ANSWER✔✔--Used during requirements elicitation and analysis to represent
external behavior ("visible from the outside of the system")
-An Actor represents a role, that is, a type of user of the system
-A use case represents a class of functionality provided by the system
-Use case model: The set of all use cases that completely describe the functionality of the system.
Use Case Diagram: Actors - ANSWER✔✔--An actor is a model for an external entity which interacts
(communicates) with the system:
Page 2/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
--User
--External system (Another system)
--Physical environment (e.g. Weather)
-An actor has a unique name and an optional description
-Examples:
--Passenger: A person in the train
--GPS satellite: An external system that provides the system with GPS coordinates.
Use Case Diagram: Textual Description - ANSWER✔✔--Use cases can be described textually, with a focus
on the event flow between actor and system
-The textual use case description consists of 6 parts:
1.Unique name
2.Participating actors
3.Entry conditions
4.Exit conditions
5.Flow of events
Page 3/55
, ©EMILLECT 2024/2025 ACADEMIC YEAR. ALL RIGHTS RESERVED
FIRST PUBLISH OCTOBER 2024
6.Special requirements.
-Textual Use Case Description Example
1. Name: Purchase ticket
2. Participating actor: Passenger
3. Entry condition:
--Passenger stands in front of ticket distributor
--Passenger has sufficient money to purchase ticket
4. Exit condition:
Passenger has ticket
5. Flow of events:
--1. Passenger selects the number of zones to be traveled
--2. Ticket Distributor displays the amount due
--3. Passenger inserts money, at least the amount due
--4. Ticket Distributor returns change
--5. Ticket Distributor issues ticket
Page 4/55
