BWI-OOM 2.Semester

Exam Questions

0.0 (0)

S. W.

Étudier

S. W.

À propos de ce fichier

This flashcard set covers university-level computer science concepts, focusing on UML diagrams like class, sequence, and communication diagrams, as well as use case modeling and object-oriented principles. It delves into relationships, behaviors, and specifications within systems, making it invaluable for students and professionals aiming to master software design and analysis. The multiple-choice format helps reinforce understanding of key terms and practices.

Cartes-fiches

Utilisateurs

Langue

Anglais

Catégorie

Informatique

Niveau

Université

Créé / Mis à jour

24.06.2016 / 24.06.2016

Fichiers de cartes similaires

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

one to many

exactly one

zero

zero to many

one to many

exactly one

zero

zero to many

A Control Class…

models information that is long-lived (persistent).

controls the key concepts of the system.

controls the behavior of a Use Case.

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.

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

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

only important objects will be identified.

several terms may refer to the same object.

the language is too clear.

one term refers to exactly one object.

only important objects will be identified.

several terms may refer to the same object.

the language is too clear.

one term refers to exactly one object.

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

Entity

Boundary

View

Control

Entity

Boundary

View

Control

Classes should NOT have…

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

a descriptive name.

a clear description.

a set of related responsibilities.

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

a descriptive name.

a clear description.

a set of related responsibilities.

Boundary Classes can NOT be…

User-interface classes

Device-interface classes

System-interface classes

Controller-interface classes

User-interface classes

Device-interface classes

System-interface classes

Controller-interface classes

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.

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.

Boundary Classes can be found in the...

Activity Diagram.

Use Case Model.

Glossary.

Use Case Description.

Activity Diagram.

Use Case Model.

Glossary.

Use Case Description.

Which diagram type is NOT part of the Interaction Diagrams?

Timing Diagram

Sequence Diagram

Activity Diagram

Communication Diagram

Timing Diagram

Sequence Diagram

Activity Diagram

Communication Diagram

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

relationship

message

object

link

relationship

message

object

link

Which element is NOT part of the Collaboration Diagram?

link

actor

object

use case

link

actor

object

use case

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

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

they have exactly the same notation elements.

they show both the execution occurrence of messages.

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 have exactly the same notation elements.

they show both the execution occurrence of messages.

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

A Sequence Diagram shows…

relationships, in addition to interactions.

links between the objects, which participate in the interaction.

the explicit sequence of messages.

how objects are related to each other and how they interact.

relationships, in addition to interactions.

links between the objects, which participate in the interaction.

the explicit sequence of messages.

how objects are related to each other and how they interact.

For a reflexive message, …

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

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

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 arrow may start and finish on the lifeline of two different objects.

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

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.

Which relationship/ association type CAN’T be modeled in the Class Diagram?

message

aggregation

generalization

reflexive association

message

aggregation

generalization

reflexive association

The Class Diagram is a UML diagram type of the….

Behavioural Diagrams

Interaction Diagrams

Communication Diagrams

Structural Diagrams

Behavioural Diagrams

Interaction Diagrams

Communication Diagrams

Structural Diagrams

Each association should have…

two multiplicities for each end of the association.

one multiplicity for each end of the association.

several multiplicities for each end of the association.

zero to many multiplicities for each end of the association.

two multiplicities for each end of the association.

one multiplicity for each end of the association.

several multiplicities for each end of the association.

zero to many multiplicities for each end of the association.

The generalization models a…

“zero to many”- relationship

“many to many”- relationship

“kind of”- relationship

“whole-part” - relationship

“zero to many”- relationship

“many to many”- relationship

“kind of”- relationship

“whole-part” - relationship

The Class Diagram describes…

the interactions between objects.

the dynamic view of the system.

the implementation view of the system.

the static view of the system.

the interactions between objects.

the dynamic view of the system.

the implementation view of the system.

the static view of the system.

The aggregation models a…

“zero to many”- relationship

“type of”- relationship

“whole-part”- relationship

“kind of” - relationship

“zero to many”- relationship

“type of”- relationship

“whole-part”- relationship

“kind of” - relationship

What is generalization?

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

Generalization describes the “is part of”-relationship.

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

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

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

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

Generalization describes the “is part of”-relationship.

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

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

An object has NO / NONE...

identity

behaviour

character

state

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

identity

behaviour

character

state

An object can represent a …. entity.

hardware

conceptual

chemical

structural

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

hardware

conceptual

chemical

structural

Which one is NOT part of a class compartment?

relationships (connections)

structure (attributes)

class name

behavior (operations)

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

relationships (connections)

structure (attributes)

class name

behavior (operations)

What’s NOT an aim of visual modeling?

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

It shows the decisions we should make in the future.

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

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

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

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

It shows the decisions we should make in the future.

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

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

Encapsulation is a basic principle of...

visual modeling

modeling

an object

object orientation

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

visual modeling

modeling

an object

object orientation

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

The best models are connected to reality.

A single model is sufficient.

Levels of precision may differ.

The choice of model is important.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The best models are connected to reality.

A single model is sufficient.

Levels of precision may differ.

The choice of model is important.

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

polymorphism

package

multiple inheritance

operation

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

polymorphism

package

multiple inheritance

operation

A Use Case Model is used to....

communicate with the sponsor.

identify the platform requirements.

identify the development requirements.

communicate with end users and experts.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

communicate with the sponsor.

identify the platform requirements.

identify the development requirements.

communicate with end users and experts.

A Supplementary Specification contains the...

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

functionality, usability, reliability, performance, traceability 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.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

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

functionality, usability, reliability, performance, traceability 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.

The name of a Use Case...

could be the same name of another Use Case.

must not be several words in length.

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

indicate what the system technical should achieve.

could be the same name of another Use Case.

must not be several words in length.

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

indicate what the system technical should achieve.

One Flow of Event of a Use Case can have…

one Basic Flow and one to many Alternative Flows.

one Basic Flow and many Alternative Flows.

one Basic Flow and zero to many Alternative Flows.

many Basic Flows and many Alternative Flows.

one Basic Flow and one to many Alternative Flows.

one Basic Flow and many Alternative Flows.

one Basic Flow and zero to many Alternative Flows.

many Basic Flows and many Alternative Flows.

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

Problem Statement

Use Case Model

Activity Diagram

Glossary

Problem Statement

Use Case Model

Activity Diagram

Glossary

An actor is NOT…

a giver of information.

a passive information recipient.

a human.

part of the system.

a giver of information.

a passive information recipient.

a human.

part of the system.

What’s NOT part of a Use Case Model?

System boundaries

Actor

Links

Use Case

System boundaries

Actor

Links

Use Case

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

Use Case Diagrams

Links

Activity Diagrams

Flow of Events

Use Case Diagrams

Links

Activity Diagrams

Flow of Events

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

Number and title each step

Describe the steps

Describe the steps again in the Alternative Flows

Structure the flow into steps

Number and title each step

Describe the steps

Describe the steps again in the Alternative Flows

Structure the flow into steps

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

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

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

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

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

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

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

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

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

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

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

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

A Postcondition of one Use Case has every time to 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.

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

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

A Postcondition of one Use Case has every time to 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.

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 aids the team communication and understanding of the system.

A Use Case facilitates the agreement with the customer.

A Use Case facilitates the hardware-decisions.

A Use Case is easy to understand.

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

A Use Case facilitates the agreement with the customer.

1 / 48

Cartes-fiches

A Sequence Diagram shows…

relationships, in addition to interactions.

links between the objects, which participate in the interaction.

the explicit sequence of messages.

how objects are related to each other and how they interact.

For a reflexive message, …

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

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

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.

Which relationship/ association type CAN’T be modeled in the Class Diagram?

message

aggregation

generalization

reflexive association

The Class Diagram is a UML diagram type of the….

Behavioural Diagrams

Interaction Diagrams

Communication Diagrams

Structural Diagrams

Each association should have…

two multiplicities for each end of the association.

one multiplicity for each end of the association.

several multiplicities for each end of the association.

zero to many multiplicities for each end of the association.

The generalization models a…

“zero to many”- relationship

“many to many”- relationship

“kind of”- relationship

“whole-part” - relationship

The Class Diagram describes…

the interactions between objects.

the dynamic view of the system.

the implementation view of the system.

the static view of the system.

The aggregation models a…

“zero to many”- relationship

“type of”- relationship

“whole-part”- relationship

“kind of” - relationship

Étudier

BWI-OOM 2.Semester

Créer ou copier des fichiers d'apprentissage

Cartes-fiches

Veuillez vous connecter

Google

Apple ID

Microsoft

Switch edu-ID

Edulog

Google

Apple ID

Microsoft

Switch edu-ID

Edulog