Object-Oriented Modeling

Principles of Visual Modeling - Use Case Modeling - Writing good Use Cases - Activity Modeling - Finding Classes - Class Diagrams - Interaction Diagrams

115

0.0 (0)

S. F.

Lernen

S. F.

Über diese Lernkartei

This flashcard set covers advanced university-level concepts in object-oriented modeling, focusing on class diagrams, use cases, and sequence diagrams. It explores elements like classes, attributes, associations, and compartments, along with their relationships and roles in system modeling. Ideal for computer science students, this flashcard set helps understand and apply UML diagrams effectively, making it a valuable resource for those studying software design and development.

Karten

115

Lernende

Sprache

Englisch

Kategorie

Informatik

Stufe

Universität

Erstellt / Aktualisiert

10.08.2016 / 25.08.2016

Ähnliche Karteien

Lernkarten

What’s NOT an aim of visual modeling?

Visual modeling gives a template that guides us in constructing a system.

Visual modeling helps to visualize a system as we want it to be.

It permits to specify the structure or behavior of a system.

It shows the decisions we should make in the future.

An object has NO / NONE...

character

identity

state

behavior

Which one is NOT part of a class compartment?

class name

relationships (connections)

structure (attributes)

behavior (operations)

An object can represent a …. entity.

structural

hardware

conceptual

chemical

What is generalization?

Generalization is the ability to hide many different implementations behind a single interface.

It defines a hierarchy of abstractions in which a superclass inherits from one or more subclasses.

Generalization defines a hierarchy of abstractions in which a subclass inherits from one or more superclasses.

Generalization describes the “is part of”-relationship.

Which one of the following statements is NOT one of the four principles of modeling?

The best models are connected to reality.

The choice of model is important.

A single model is sufficient.

Levels of precision may differ.

Encapsulation is a basic principle of...

visual modeling

modeling

an object

object orientation

A mechanism / model element of the UML, which can contain other model elements, is called…

package

operation

multiple inheritance

polymorphism

A Use Case Model is used to....

identify the development requirements.

communicate with the sponsor.

communicate with end users and experts.

identify the platform requirements.

One Flow of Event of a Use Case can have…

one Basic Flow and one to many Alternative Flows.

many Basic Flows and many Alternative Flows.

one Basic Flow and zero to many Alternative Flows.

one Basic Flow and many Alternative Flows.

A Supplementary Specification contains the...

functionality, usability, ability, performance, supportability and design constraints of a system.

functionality, usability, reliability, performance, supportability and liability of a system.

functionality, usability, reliability, performance, supportability and design constraints of a system.

functionality, usability, reliability, performance, traceability and design constraints of a system.

An actor is NOT…

a passive information recipient.

part of the system.

a giver of information.

a human.

The name of a Use Case...

must not be several words in length.

should indicate what is achieved by the interaction with the actor.

could be the same name of another Use Case.

indicate what the system technical should achieve.

Actors can be found / are findable in the...

Use Case Model

Glossary

Activity Diagram

Problem Statement

What’s NOT part of a Use Case Model?

System boundaries

Actor

Use Case

Links

Which of the following is NOT included in a Use Case Specifications?

Use Case Diagrams

Links

Activity Diagrams

Flow of Events

What’s the main difference between an Alternative Flow and a Subflow?

An Alternative Flow increases the clarity, unlike a Subflow.

An Alternative Flow allows the internal reuse of requirements, unlike a Subflow.

An Alternative Flow returns always to the line, after it was called and it is called explicitly, unlike a Subflow.

A Subflow returns always to the line, after it was called and it is called explicitly, unlike an Alternative Flow.

What is the connection / relation between a Pre- and a Postcondition?

A Postcondition of one Use Case can be the Precondition for another Use Case.

A Postcondition describes the state of the system at the begin of the Use Case and a Precondition describes its state at the end of the Use Case.

A Postcondition of one Use Case has every time to be the Precondition for another Use Case.

Both, a Pre- and a Postcondition have every time to be described in the Use Case Specification.

How can you handle repetitive behavior in a Use Case Specification?

Repetitive behavior can be handled by the description of a Subflow.

Complex repetitive behavior should be described repetitive in the Basic Flow.

Repetitive behavior can be handled by the description of an Alternative Flow.

Repetitive behavior can be handled by describing it in the Glossary.

What’s NOT a benefit of a Use Case Model?

A Use Case facilitates the hardware-decisions.

A Use Case is easy to understand.

A Use Case facilitates the agreement with the customer.

A Use Case aids the team communication and understanding of the system.

What means CRUD?

Cancel, Read, Update and Delete

Carried, Read, Update and Develop

Creatable, Reusable, Usability and Development

Create, Read, Update and Delete

Should you model the “Log in “ as a Use Case?

No, because “Log in” is an “outstanding” function of the system.

No, because it does not produce results of value to an Actor.

Yes, because “Log in” is a function of the system.

Yes, because in many cases “Log in” captures a complex behavior and it is included in other Use Cases.

What’s NOT an important point to detail the Basic Flow of a Use Case?

Describe the steps

Number and title each step

Describe the steps again in the Alternative Flows

Structure the flow into steps

A decision is used to...

execute a different sequence of actions, depending on a condition.

join the merged flows at the end of the conditional behavior.

join the brached flows at the end of the conditional behavior.

execute parallel sequences of actions, depending on conditions.

An action is...

a state, that does something to the behavior of a system.

noted as an Use Case Diagram.

noted as an Activity Diagram.

a function, that does something to the state of a system.

A time event models...

the date and time.

the duration of one action.

a sending or a receiving event.

a waiting period or a time interval.

The difference between an object and an input/ output pin is, that...

a pin shows, which in- or output is required by an action and an object node shows only, that the object is not yet available.

a pin shows, which in- or output is required by an action and an object node shows only, that the object is available.

an object shows, which in- or output is required by an action and a pin shows only, that the object is available.

a pin shows, which pre- or postcondition is required for an action and an object shows only, that the object is available.

The parallel occurrence of actions means, that...

they will finish one after the other.

they can not be finished at the exact same time.

they will finish at the exact same time.

they will not needfully finish at the exact same time.

Which one of the following is NOT an Analysis Class type (Stereotype)?

Entity

View

Boundary

Control

Boundary Classes can NOT be…

Controller-interface classes

Device-interface classes

User-interface classes

System-interface classes

A Use Case has …. Control Class(es).

zero to many

zero

exactly one

one to many

A pitfall, when identifying nouns, to find Entity Classes, could be that…

the language is too clear.

only important objects will be identified.

one term refers to exactly one object.

several terms may refer to the same object.

Potential sources for finding Entity Classes are the…

Use Case Model, Activity Diagram and Glossary.

Glossary, Activity Diagram and Use Case Specifications.

Glossary, Business Domain Model and Use Case Specifications.

Sequence Diagram, Activity Diagram and Glossary.

Classes should NOT have…

a descriptive name.

a clear description.

a set of related responsibilities.

a name, which is redundant with the name of another class.

A Control Class…

models the interaction between the system’s surroundings and its inner workings.

models information that is long-lived (persistent).

controls the key concepts of the system.

controls the behavior of a Use Case.

An association, between two communication partners in the Communication Diagram is called…

relationship

link

object

message

Which diagram type is NOT part of the Interaction Diagrams?

Communication Diagram

Timing Diagram

Sequence Diagram

Activity Diagram

Which element is NOT part of the Collaboration Diagram?

object

actor

use case

link

For a reflexive message, …

the arrow is shown as a horizontal solid arrow from the lifeline of one object to the lifeline of another object.

the arrow may start and finish on the lifeline of two different objects.

the arrow is shown as a vertical solid arrow from the lifeline of one object to the lifeline of another object.

the arrow may start and finish on the lifeline of the same object.

The MOST IMPORTANT connection between Sequence Diagram and Communication Diagram is, that…

the Communication Diagram can be converted to the Sequence Diagram, without losing any information.

the Sequence Diagram can be converted to the Communication Diagram, without losing any information.

they show both the execution occurrence of messages.

they have exactly the same notation elements.

Lernen

Object-Oriented Modeling

Lernkarteien erstellen oder kopieren

Lernkarten

Bitte melde dich an

Google

Apple ID

Microsoft

Switch edu-ID

Edulog

Google

Apple ID

Microsoft

Switch edu-ID

Edulog