Test: UML language - basic concepts.

1 0

a) model systems as a whole, from concept to executable file, using object-oriented methods;

b) create a modeling language that can be used not only by humans, but also by computers;

c) combine the existing visual modeling languages like OMG, CORBA, ORG;

d) solve the problem of scalability, which is inherent in complex systems designed to perform critical tasks;

a) relationships;

b) diagrams;

c) annotations;

d) classes;

e) entities;

f) interfaces;

a) a set of roles and other elements that, working together, produce some joint effect that is not reduced to a simple sum of terms;

b) a description of the sequence of actions performed by the system, which produces an observable result that is significant for a certain actor;

c) a set of operations that define a service (set of services) provided by a class or component;

d) it is a physical replaceable part of the system that corresponds to a certain set of classes and provides its implementation;

a) classes;

b) interfaces;

c) machines;

d) cooperation;

e) precedents;

f) states;

g) components;

a) dependence;

b) association;

c) structuring;

d) generalization;

e) implementation;

f) aggregation;

a) generalized;

b) structural;

c) behavioral;

d) combinational;

e) grouping;

f) annotation;

g) subordinates;

a) an external entity in relation to a computer system, which can only supply information to the system;

b) an external entity in relation to a computer system, which can only receive information from the system;

c) the inner essence of a computer system, which can only supply information to the system;

d) an external entity in relation to a computer system that interacts with this system;

e) the inner essence of a computer system, which can only receive information from the system;

f) the inner essence of a computer system, which can both receive information from the system and supply information to the system;

a) version control system;

b) it is a product of Microsoft Corporation;

c) this is an Intel Corporation product;

d) includes a version control system;

e) includes a system that supports data collection for generating reports;

f) includes a system for collaborating on software development projects;

g) a system for collaborative work on software development projects;

h) includes an automatic testing system;

i) a system that supports data collection for generating reports;

j) automatic testing system;

a) corresponds to the statistical type of the system;

b) corresponds to the dynamic form of the system;

c) it is the organization of a set of classes and dependencies existing between them;

d) a special case of an activity diagram;

e) corresponds to the static type of the system;

f) serves to model the process of messaging between objects;

g) serves to model the static structure of the classes of the system and the connections between them;

a) aggregation;

b) dependence;

c) use;

d) expansion;

e) association;

a) class diagrams;

b) state diagrams;

c) component diagrams;

d) activity diagrams;

e) diagrams of cooperation;

f) deployment diagrams;

a) events;

b) primary school;

c) classes;

d) interfaces;

e) packages;

f) relationships;

g) final class;

h) objects;

a) class name;

b) class attributes;

c) class operations;

d) input data;

e) output data;

f) class properties;

a) means that this class attribute cannot be changed in the program when working with this type of objects;

b) means that this class attribute can be changed in the program when working with this type of objects;

c) means that the given class attribute has the public scope type;

d) means that all objects of this class can have several different windows, each of which will be a trapezoid;

e) means that this class attribute has a protected type scope;

f) means that all objects of this class can have windows of the same size in the form of a trapezoid;

a) excluding association;

b) generalization relation;

c) limitation relation;

d) aggregation relation;

e) the ratio of the composition;

f) relationship of dependence;

a) use case diagram;

b) state diagram;

c) deployment diagram;

d) package diagram;

e) node diagram;

f) activity diagram;

g) sequence diagram;

h) diagram of cooperation;

i) class diagram;

j) placement diagram;

a) an instance of the class;

b) automatic machine;

c) use case;

d) actor;

e) attitude;

f) interface;

g) operation;

h) method;

i) node;