Test with answers: UML language - basic concepts.

1 0

The test contains questions regarding the basic structural entities of the UML, types of relationships and entities. It covers a class diagram, use cases, and a state diagram. There are questions about fields and class attributes.

1) (of 17): The UML was designed to:

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; +

2) (of 17): The UML vocabulary includes the following building blocks:

а) relationships; +

b) diagrams; +

c) annotations;

d) classes;

e) entities; +

f) interfaces;

3) (of 17): In the UML language, the interface is:

а) 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;

4) (of 17): The main structural entities of the UML include the following:

а) classes; +

b) interfaces; +

c) machines;

d) cooperation; +

e) precedents; +

f) states;

g) components; +

5) (of 17): The following types of relations are defined in the UML:

а) dependence; +

б) association; +

в) structuring;

г) generalization; +

д) implementation; +

е) aggregation; +

6) (of 17): The following entity types are defined in the UML:

а) generalized;

b) structural; +

c) behavioral; +

d) combinational;

e) grouping; +

f) annotation; +

g) subordinates;

7) (of 17): An actor is:

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

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

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

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

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

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

8) (of 17): Team Foundation Server:

а) 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;

9) (of 17): Class diagram:

а) 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; +

10) (of 17): The following relationships can exist between use cases in a use case diagram:

а) aggregation;

b) dependence;

c) use; +

d) expansion; +

e) association;

11) (of 17): The Logical View tab of the Rational Rose package contains:

а) class diagrams; +

b) state diagrams; +

c) component diagrams;

d) activity diagrams; +

e) diagrams of cooperation; +

f) deployment diagrams;

12) (of 17): A class diagram can contain:

а) events;

b) primary school;

c) classes; +

d) interfaces; +

e) packages; +

f) relationships; +

g) final class;

h) objects; +

13) (of 17): The class contains the following fields:

a) class name; +

b) class attributes; +

c) class operations; +

d) input data;

e) output data;

f) class properties;

14) (of 17): Class attribute specified in the following form (see Fig. 1):

Fig. 1. This class attribute in UML means...

а) 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;

15) (of 17): A particular case of an association relationship is:

а) excluding association; +

b) generalization relation;

c) limitation relation;

d) aggregation relation; +

e) the ratio of the composition; +

f) relationship of dependence;

16) (of 17): The following diagrams can be used to model the behavior of a system in UML:

а) 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;

17) (of 17): The state diagram is used to describe the behavior of such system components as:

а) an instance of the class; +

b) automatic machine;

c) use case; +

d) actor; +

e) attitude;

f) interface;

g) operation; +

h) method; +

i) node;