UML diagrams

main concepts of OOP ,classes, objects, instances, methods, polymorphism, inheritance, encapsulation.

3 more concepts: polymorphism, inheritance, encapsulation.

Internal operation call is called ______

Reflexive Messages

Class diagram is _____ diagram

Structural diagram

UML stands for _____

Unified Modeling Language

Behavioral diagrams(required) are ____ , _____ , ______

Use case diagram , State machine diagram , Activity diagram

use cases are group of ____ that the system performs

actions

sequence or flow of Activities are represented in _____ diagrams

activity

use cases show the relationship between ____ and _____

actors and system

the link/relation between actors and use cases is called ______

association

Generalization relationships are used when two or more use cases have commonalities in _____ , structure, and ______.

behavior , purpose/goal

activity diagram is ____ diagram

behavioral

use case diagram is ____ diagram

behavioral

A class is the _____ from which individual objects are created.

blueprint

a composite state consists of sub states , they can be sequential or _____

concurrent/parallel

Modeling stands for : describing ______ system with ______ level of abstraction

describing software system with high level of abstraction

actors interact directly/indirectly with the system

directly

abstraction =?

essentials not detailed

actors are an ______ part of the system

external

UML depends on the programming language

false

"Stickman" notation represents robots actors

false "Stickman" notation represents only human beings actors

<<include>> shows an optional execution

false <<extends>>

A use case is always a noun

false A use case is always an action verb

OOP languages permit low level of abstraction

false OOP languages permit higher level of abstraction

State is put in ellipse

false State: Rounded rectangle

The axes in a sequence diagram: horizontal represents timeline

false The axes in a sequence diagram: - horizontal: which object/participant is acting - vertical: timeline (down -> forward in time)

UML is a programming language

false UML is a diagraming language

a sequence diagram can describe multiple scenarios

false a sequence diagram can describe single scenario

actors are same as the programmers

false actors are external users

actors are random users

false actors are typical users have same behavior with respect to a given use case

actors have different behavior to a use case

false actors have same behavior with respect to a given use case

an activity diagram shows 'what'

false an activity diagram shows 'How' , while a Use case shows 'What'

descendant are actors whom their role is inherited

false ancestor are actors whom their role is inherited by descendant

state diagram is interaction diagram

false behavioral

<<include>> is a relationship between actors and use cases

false between use cases

use cases is put in circles

false ellipse

in activity diagram , activity is a single step

false every action is a single step within an activity (sequence of behavior/actions)

extend arrow is pointed to the option

false extend arrow is pointed to the base

the fork joins multiple flows to one outgoing flow

false fork get one ingoing flow and several outgoing flows

sequence diagram is behavioral diagram

false interaction diagram

for non-human actors the internal functionalities is detailed as well

false internal functioning of non-human/systems involved must NOT be detailed

actors can be only humans

false it can be other systems using this system

use case diagram describes how the use cases are behavioring

false it only shows what are the expected behaviors and not how

join has several sequential outgoings

false join has several concurrent outgoings

merge node has several mandatory flows to get an outgoing flow

false merge node has several POSSIBLE incoming flows and single outgoing flow ( one flow is enough to the outgoing to be executed/done )

each use case should be linked to an actor

false not all use cases are linked to actors

all objects included in the sequence diagram belongs to the system

false objects can also be actors being found at its frontiers ( border of the system )

objects in sequence diagram can be only instances of a class

false objects can be also external actors

actors as objects need an activation box

false only objects, actors are external to the system

a use case diagram emphasized on time ordering

false sequence diagram

the link between actors and use cases in doubled line

false single line

in state diagram : the [guard] is necessary to be indicated

false the event is mandatory in state transition since it's the cause of it

The extended use case can be executed always

false the extended use case is usually executed under certain conditions. the option cannot be executed when the base is not executed

the language in (UML) describes methodology/procedure

false the language expresses an idea only

in Asynchronous Message the execution of the sender is blocked till the return message

false the sender doesn't wait for a return message to continue working

the system shows results to the secondary actor

false the system shows results to the primary actor

use case is a system function that is always automatic

false use case is a system function that can be either manual or automatic

use cases are messages in the use case diagram

false use cases are functionalities inside the system

use cases has a single concept which is showing the use cases only

false use cases has 3 main concepts: 1-actors reveal 2-use cases reveal 3-interactions between the two above

in vertical axes in sequence diagram vertical: timeline (down -> ____ in time)

forward

dynamic diagram is same as _____

interaction diagram

sequence diagram is _____ diagram

interaction diagram

holds a list of internal actions or state (do) activities (behaviors) that are performed while the element is in that state. is called_______

internal activities compartment

Combined interaction fragments are

logical groupings represented by a rectangle and containing the conditional structures that affect the flow of messages

Partition horizontal swim lane always

no Partition horizontal or vertical swim lane.

Used to separate actions within an activity done by diff actors is called_______

partition

you can perform a single task in different ways by ________ ( a concept in OOP )

polymorphism

____ actor causes exchanges with the system

primary

actors can modify____ in the system and ask the system for _____

state/data , information

a decision node has single input flow

true

actors have specific role within the system

true

each use case includes a primary scenario 0 to more secondary

true

extend use case add behavior to the extension points

true

in state diagram : event: causes the change in state.

true

in state diagram : the [guard] and /reaction are optional

true

included arrow is pointed to the essential

true

objects are put in solid rectangles

true

state diagram uses finite state transitions

true

synchronous message sender is dependent on the return message , else the rest of the action are blocked

true

the event is mandatory in state transition since it's the cause of it

true

use case diagram does not show order and workflows

true

use case diagram specified the functional requirement of a system

true

Encapsulation

when you group variables and methods into ONE class ( CSCI300 main thing )