Chapter 3_Unified Modeling Language (copy)

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/33

flashcard set

Earn XP

Description and Tags

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

34 Terms

1
New cards

Unified Modeling Language

is a graphical language for modeling software systems.

2
New cards

Unified Modeling Language

is not a programming language.

3
New cards

Unified Modeling Language

It is a set of diagrams that can be used to specify, construct, visualize, and document software designs.

4
New cards

Unified Modeling Language

has diagrams to assist in every part of application development, from requirements gathering design, coding, testing, and deployment.

5
New cards

Unified Modeling Language

most commonly used modeling language.

6
New cards

early 1990s

UML was developed in the _____

7
New cards

Grady Booch, James Rumbaugh, and Ivar Jacobson

UML was developed by three leaders in object-modeling world

8
New cards

class diagram

is to depict the classes within a model.

9
New cards

UML class diagram

In an object-oriented application, classes have attributes (member variables), operations (member functions) and relationships with other classes. The _____ can depict all these things quite easily.

10
New cards

icon

fundamental element of the class diagram representing a class

11
New cards

-

private

12
New cards

+

public

13
New cards

#

protected

14
New cards

~

package

15
New cards

none

default

16
New cards

static

indicated underline in attribute or method

17
New cards

final

indicated by the word final in the identifier

18
New cards

abstract

indicated italic text for the abstract class, interface and an abstract keyword

19
New cards

metamodel

UML is unique in that it has a standard data representation. This representation is called the _____.

20
New cards

metamodel

is a description of UML in UML.

21
New cards

metamodel

It describes the objects, attributes, and relationships necessary to represent the concepts of UML within a software application.

22
New cards

Association

represents a relationship between two or more classes, showing that instances of one class are connected to instances of another class.

23
New cards

Aggregation

is a special type of association where one class contains or is composed of another class.

24
New cards

Aggregation

It is depicted using a diamond shape.

25
New cards

Composition

is a stronger form of aggregation where the child objects cannot exist independently of the parent object.

26
New cards

Composition

It is also depicted using a diamond shape, but with a solid line.

27
New cards

Dependency

represents a weaker form of relationship where one class relies on another class, but changes in the dependent class do not necessarily affect the independent class.

28
New cards

Inheritance

represents the "is-a" relationship between classes, where one class inherits the properties and behaviors of another class.

29
New cards

Realization

is a relationship that signifies the implementation of a contract (i.e., an interface) by a class.

30
New cards

Realization

It's often used to show that a class provides the actual implementation for the methods declared in an interface.

31
New cards

Realization

This is commonly referred to as "interface realization" or "class realization" in UML diagrams

32
New cards

Directed association

is used to indicate a unidirectional relationship between two classes.

33
New cards

Directed association

It implies that one class is aware of the other, but the reverse may not be true.

34
New cards

Directed association

This can be depicted using an arrowhead on the association line.