Vous êtes sur la page 1sur 12

12.The best models ate connected to . . . . . . . . . . . ..

[01S08]
1. reality.
2. functionality.
3. casuality
4. visualityl
JNTUK ONLINE Examinations-2010 [OOAD-Mid1]
13.A . . . . . . . . is a generic template for objects.
1. Which one of the following is not principale of
[02D01]
modeling? [01D01]
1. program
1. Choose your models well
2. class.
2. Every model may not be expressed at different
at different levels of decision. 3. procedure.
3. The best models are connected to reality. 4. method.
4. No single model is sufficient. 14.A . . . . . . . . method of an object cannot be
2. Which one of the following view express the accessed by oher objects. [02D02]
requirements of the system? [01D02] 1. protected.
1. Usecase 2. private.
2. Design 3. public.
3. Process 4. general.
4. Implementation. 15.In an object-oriented approach the main building
3. UML is a - - - - - - - - - modeling language. [01M01] block of all software is the . . .. . .. [02M01]
1. general - purpose. 1. class
2. object-purpose. 2. function.
3. architecture-purpose. 3. procedure.
4. code-purpose. 4. module.
4. We build models so that we can better - - - - - the 16.The . . . . . . . . . . . . . approach to software
system we are developing.[01M02] development is decidedly a part of the mainstream.
1. misunderstand [02M02]
2. understand 1. algorithmic.
2. object-oriented.
3. guide
4. misguide. 3. procedural.
5. - - - is a central past of all the activities that lead up 4. modeled.
to the deployment of good software.[01S01] 17.In an algorithmic approach the main building block
1. Modeling of all software is the . . . . . . . .[02S01]
2. Coding 1. class.
3. Testing 2. abstract class.
4. Analysis 3. object.
4. module.
6. What is a model? [01S02]
1. A model is a modification of reality 18. Visualizing, specifying, constructing, & documenting
2. A model is a justification of reality object-oriented systems are exactly the purpose
3. A model is a simplification of reality of the . . . . . . . . .... [02S02]
4. A model is a constucation of reality 1. C language.
7. UML stands for [01S03] 2. C++ language.
1. Uniform Modeling Langage 3. pascal language .
2. Unified Modeling Langage 4. Unified modeling language.
3. United Modeling Langage 19.In . . . . . . . . , any program can call any other
4. Unique Modeling Langage program. [02S03]
1. modular.
8. Models tell us to - - - - - - - - a system as it is (or) as
we want it to be.[01S04] 2. object.
1. visualize 3. procedural.
2. specify. 4. component.
3. constructing. 20.An object contains . . . . . . . . . . . . . . .. [02S04]
1. attributes & methods.
4. document.
9. Models permit us to - - - - - - - - the structure or 2. only attributes.
behavior of a system[01S05] 3. only methods.
1. visualize 4. classes.
2. specify. 21.In abstraction, we concentrate on . . . . . . . . ..
3. constructing. [02S05]
4. document. 1. minor details.
10.Models give us a template that guides us in . . . . . . 2. procedures.
. . . system. [01S06] 3. processes.
4. important details.
1. visualize
2. specify. 22.. . . . . . . helps us in protecting privacy of objects.
3. constructing. [02S06]
1. Encapsulation
4. document.
11.Models . . . . . . . . the decisions we have made. 2. Abstraction.
[01S07]
1. visualize
2. specify.
3. constructing.
4. document.
3. Inheritance. 33.An . . . . . . is a collection of operations that specify a
4. Polymorphiism . service of a class or component. [03S05]
23.A . . . . . . . is rendered as a rectangle with tabs. 1. interface
[03D01] 2. active class
1. interaction. 3. use case
2. node. . 4. interaction
3. component. 34.A . . . . . is a physical & replaceable part of a system
4. state. that conforms to and provides the realization of
24.Which one of the following is grouping thing? Set of interfaces. [03S06]
[03D02] 1. node 2. Class 3. Componet 4. Collaboration
1. class . 35.A node is rendered as a . . . . . . . . . . . . .. [03S07]
2. package. 1. rectangle.
3. use case. 2. ellipse.
4. collaboration. 3. cube.
25.An . . . . is a class whase objects own one or more 4. square.
processes or threads and therefore can initiate 36.A . . . . . . . . is rendered as a rounded rectangle.
Control activity. [03D03] [03S08]
1. Active class. 1. interaction.
2. Abstact class. 2. node.
3. Alternate class. 3. component.
4. Interface class. 4. state.
26.Which one of the following is not structural thing? 37.A . . . . . . . is rendered as an ellipse with dasned
[03G01] lines. [03S09]
1. class . 1. class.
2. package. 2. collaboration.
3. use case. 3. vsecase.
4. collaboration. 4. component.
27.An interface is rendered as . . . . . . . . . . . .. 38.Which one of the following diagram is an interation
[03M01] diagram? . [04D01]
1. cube 1. class.
2. squre. 2. object.
3. rectangle 3. sequence.
4. circle. 4. statement
28.An . . . is a behavior that comprises a set of 39.A . . . . . . . . . diagram is an interaction diagram
messages exchanged among a set objects within a that emphasizes the structural organization of the
particular context to accomplish a specific purpose. objects that sends and recive messages. [04D02]
[03M02] 1. collaboration.
1. interface. 2. object.
2. active class. 3. sequence.
3. use case. 4. component.
4. interaction. 40.The UML’ s . . . . . provide a semantic backplane that
29.. . . . . . . . things are the names of UML models. contains all the ports of all the models of a
[03S01] system, each part related to one another in a consistent
1. Structural fashion. [04D03]
2. behavioral 1. adornments .
3. grouping 2. specifications.
4. annotational 3. common divisions.
30.. . . . . . . . things are the dynamic parts of UML 4. extendbility mechanisms.
models. [03S02] 41.. . . . . . . . . is a special kind of association,
1. structure. . respresenting a structural relationship between a whole
2. behavioral. and its parts. [04M01]
3. grouping. 1. dependency.
4. annotational. 2. Aggregation.
31.. . . . . . . things are the organizational parts of UML 3. Generalization.
models. [03S03] 4. Realization. .
1. structure 42.A . . . . . . . . . . relationship is rendered as a solid
2. behavioral line with a hoiiow arrowhead pointing to the parent.
3. grouping [04M02]
4. annotational 1. dependency.
32.. . . . . . . . things are the explanatory prts of UML 2. Aggregation.
models. [03S04] 3. Generalization.
1. structure 4. Realization.
2. behavioral 43.A . . . diagram shows the configuration of runtime
3. grouping processing nodes and the components that live on
4. annotational them. [04M03]
1. usecase. 53.A . . . . . . . . extends the vocabulary to the
2. activity. UML,allowing you to create new kinds of building block
3. deployment. that
4. component. are derived from existing ones out that are specific to
44.A . . . . . . . . . is a semantic relationship between your problem. [04S10]
two things in which a change to one thing may affect 1. tagged value.
the semantics of the ther thing. [04S01] 2. stereotype.
1. dependency. 3. Constraint
2. generalization. 4. Adornmrnts.
3. realization. 54.. . . . . . . . . is the fourth phase of the process when
4. message. the software is turned into the hands of the user
45.An . . . . . . . . is a structural relationship that community. [05D01]
describes a set of links, a link being a connection 1. Inception.
Among 2. Blaboration.
objets. [04S02] 3. Construction.
1. interaction. 4. Transition.
2. association. 55.The coding phase roughly maps to the . . . . phase.
3. interface. [05D02]
4. dependency. 1. inception.
46.A . . . . . . . . . is a spelization relationship in which 2. elaboration.
objects of the specialzed element are substitutable 3. construction.
for objects of the generalized element. [04S03] 4. trasition.
1. dependency. 56.An . . . . . . . . . is one that involves managing a
2. generalization. streams of executable releases. [05M01]
3. realization. 1. usecuse-driven.
4. message. 2. iterative process.
47.A . . . . . . is a semantic relationship between 3. incremental process.
classifiers where in one classifier specifies a contract 4. architecture-centric.
that 57.The architecture model baseline is usually ready in
another classifier gnarantees to carry out. [04S04] the . . . . . . . . phase. [05M02]
1. dependency. 1. inception.
2. generalization. 2. elaboration.
3. realization. 3. construction.
4. message. 4. trasition.
48.UML includes . . . . diagrams. [04S05] 58.The users get a chance to test the system in the . . .
1. seven. . . . . . phase. [05M03]
2. eight. 1. inception.
3. nine. 2. elaboration.
4. ten. 3. construction.
49.Which one of the following diagram address the 4. trasition.
dynamic view of a system? [04S06] 59.The . . . . . view of a system encompasses the use
1. class. cases that describe the behavior of the system as
2. object. seen by its end users, analysis and testers. [05S01]
3. component. 1. design
4. statechart. 2. usecase
50.Which one the following diagram address the static 3. process
view of a system? [04S07] 4. deployment.
1. interaction. 60.The . . . . . . . view of a system encompasses the
2. activity. classes, interfaces ,and collaborations that form the
3. statechart. vocabulary of the problem and its solution. [05S02]
4. component. 1. design
51.A . . . . . . . extends the properties of a UML building 2. usecase
block, allowing you to create new information in 3. process
that element’s specification. [04S08] 4. deployment
1. tagged value. 61.The . . . . . . . . view of a system encompasses the
2. stereotype. threads and processes that form the system’s
3. Constraint concurrency and syncnronization mechanisms. [05S03]
4. Adornmrnts. 1. design
52.A . . . . . . . . extends the semantics of a UML 2. usecase
building block ,allowing you to add new rules or modify 3. process
existing ones. [04S09] 4. deployment
1. tagged value. 62.The . . . . . view of a system excompasses the nodes
2. stereotype. that form the system’s hardware topology on
3. Constraint which the system executes. [05S04]
4. Adornmrnts. 1. design
2. usecase 4. Procedure.
3. process 73.An . . . . . . . . . . . is a named property of a class
4. deployment that describes a range of values that instance of the
63.The . . . . . . . . view of a system excompasses the property may held. [06S02]
components and files that are used to assemble and 1. item.
release the physical system. [05S05] 2. Attribute.
1. implementation. 3. Operation.
2. usecase 4. Entity. .
3. process 74.An . . . . . . . . . . . . is the implementation of a
4. deployment service that can be requested from any object of the
64.The analysis phase roughly maps to the . . . . . . . . . class to affect behavior. [06S03]
phase. [05S06] 1. item.
1. inception. 2. attribute.
2. elaboration. 3. operation.
3. construction. 4. entity.
4. trasition. 75.A . . . . . . . . is a contract or an obligation of a class.
65.The design phase roughly maps to the . . . . . . . . . . [06S04]
phase. [05S07] 1. usability.
1. inception. 2. responsibility
2. elaboration. 3. package.
3. construction. 4. state.
4. trasition. 76.A . . . . . . . is just the face the class at the neor end
66.Aggregation is a . . . . . . . . . kind of relationship . of the association presents to the other end of the
[06D01] association. [06S05]
1. is-a. . 1. name.
2. to-a. 2. role.
3. was-a 3. multiplicity.
4. has-a. 4. aggregation.
67.Use . . . . . . . . . only when you have an is a- kind-of 77.Dependency relationship is rendered as. [06S06]
relationship. [06D02] 1. Shown in figure (a)
1. dependency. 2. Shown in figure (a)
2. association. 3. Shown in figure (a)
3. aggregation. 4. Shown in figure
4. generalization. (a)
68.Use . . . . . . . . only when the relatioshop you are Figure(a)
modeling is not structural. [06D03] Figure(a)
1. dependencies. Figure(a)
2. associations. Figure(a)
3. aggregations. 78.Generalization relationship is rendered as. [06S07]
4. generalizations. 1. Shown in figure (a)
69.. . . . . . . . . . . can be drawn in a separate 2. Shown in figure
comportment at the bottom of the class icon. [06M01] (a)
1. usability. 3. Shown in figure
2. responsibility (a)
3. package. Figure(a)
4. state. Figure(a)
70.An association that connects exactly two classes is 4. Shown in figure
called a . . . . . . . . . .. [06M02] (a) .
1. binary association. Figure(a)
2. Terihy association. Figure(a)
3. normal association. 79.Association is relationship is rendered as. [06S08]
4. single association. 1. Shown in figure(a)
71.You can explicity specify that there are more 2. Shown in
attributes or properties than shown by ending each list figure(a)
with an . . . . . . . . . . . .. [06M03] 3. Shown in figure(a)
1. circles. 4. Shown in figure(a)
2. sequeres. Figure(a)
3. ellipsis. Figure(a)
4. stereotypes. Figure(a)
72.A . . . . . . . . . is a description of a set of objects that Figure(a)
store the same attributes,operations,relationships 80.Aggregation relationship is rendered as. [06S09]
& semantics. [06S01] 1. Shown in figure(a)
1. class. 2. Shown in figure(a)
2. Entity. 3. Shown in
3. Function. figure(a)
90.A . . . . . . . . . . is rendered as a tring eccloed by
brackets and placed neor the associated element.
[07S04]
1. note.
2. Stereo type.
3. tagged value.
4. constraint.
4. Shown in figure(a) 91.which one of the following standard stereotype
Figure(a) specifies that the classifier is a Stereo types, that may
Figure(a) be applied to other elements? [07S05]
Figure(a) 1. Stereo type
Figure(a) 2. Documentation
81.. . . . . . . . . . . . diagrams are especially important 3. Exception
in modeling the function of system. [07D01] 4. Metaclass
1. statecnort. 92.A . . . . . . . . . . . . is a semantically classed
2. deployment. abstraction of a system,meaning that it represents a
3. Activity complete and self-consistent simplification of reality
4 . sequence. ,created in order to better understand the system.
82.You use . . . . . . . diagrams to illustrate data [07S06]
structures, the static snapshots of instances of the 1. diagram.
things 2. View.
found in class diagrams. [07D02] 3. Model.
1. Usecase. 4. Sub system.
2. object. 93.Which one of the following diagram is a structural
3. collaboration. diagram? [07S07]
4. sequence. 1. Use case.
83.Implementation view consists of . . . . . . . . 2. Activity.
diagrams. [07D03] 3. component.
1. class 4. statechart.
2. interaction 94.Which one of the following diagram is a behavioral
3. component diagram? [07S08]
4. dedloyment 1. class. .
84.The UML specifies one standerd stereotype that 2. objects.
applies to notes is . [07M01] 3. component.
1. requirement. 4. sequence.
2. metaclass. 95.Wich one of the following attribute declaration is
3. exception. legal of name,multiplication & type?
4. powertype. [08D01]
85.From the following diagrams you can convert from 1. name : string.
one to the other without loss of information. 07M02] 2. + orgin.
1. sequence & collaboration. 3. head:*item.
2. sequences & class . 4. namejO.1J : string.
3. collaboration & usecase. 96.An operation is said to be polymorphic when
4. deployment and usecase. [08D02]
86.. . . . . . . . . diagrams emphasize the event-ordered 1. you can specify operations with the same
behavior of an object, which is especially usefull in signature at different print in the hierarchy.
modeling reactive system. [07M03] 2. you can specify operations with the different
1. statechart. signature at same print in the hierarchy
2. sequence. 3. you can specify operations with the different
3. component. signature at different print in the hierarchy
4. deployment. 4. you can specify operations with the same signature
87.Notes may be attached to more than one element by at same print in the hierarchy
using . . . . . . . . . .. [07S01] 97.. . . . . . . . . . . is a physical element that exists at
1. associations. run time and that represents a computational
2. dependences. Resource,generally having at least some memory and
3. generalizations. often processing capability. [08D03]
4. aggregations. 1. signal.
88.. . . . . . . . . . . are textualor graphical items that are 2. Component
added to an element’s basic notation and are used 3. Node
to visualize details from the element’s specification. 4. Subsystem
[07S02] 98.A well structured classifier is . . . . . . . . . . . .
1. Notes. coupled. [08D04]
2. Stereo types. 1. fightly.
3. Tagged values. 2. loosly.
4. Adornments. 3. sequentially.
89.A tagged value is redered as a . . . . . . . . . enclosed
by brackets and placed below the name of
another element. [07S03]
1. integer.
2. float. .
3. string.
4. varchar.
4. parallely. 3. Node.
99.The visibility of private is . [08G04] 4. Usecase
1. + 110.. . . . . . . . . stereotype specifies a class whose
2. # attributes and operations are all class scoped. [08S09]
3. - . 1. Signal.
4. I 2. Component
100.. . . . . . . . . . is a specification of the range of 3. Node.
allowable cordinalities that a set may assume. [08M01] 4. Usecase
1. visibility. 111.Which one of the following stereotype is used to
2. scope. apply to dependency relationships among
3. attribute. packages? [09D01]
4. multiplicity. 1. extend.
101.A . . . . . . . . . . . is a parameterized element. 2. access.
[08M02] 3. include.
1. class. 4. become.
2. object. 112.Which one of the following constraint in
3. template. generalization relationships,apply only in the context of
4. activeclass. multiple inheritance. [09D02]
102.A . . . . . . . . . is a mechanism that describes 1. overlapping.
structural and behavioral features. [08S01] 2. Complete.
1. class. 3. Incomplete.
2. Classifier. 4. Implementation.
3. Object. 113.. . . . . . . . . . stereotype specifies that the source
4. Entity. is given special visibility into the target. [09D03]
103.The visibility of public is [08S02] 1. derive.
1. 5 2. friend.
2. # 3. refine.
3. - 4. use.
4. I 114.. . . . . . . . . . . . stereotype specifies that the
104.The visibility of protected is . [08S03] target is an historical ancestor of the source. [09M01]
1. + 1. send.
2. # 2. copy.
3. - 3. trace.
4. I 4. extand.
105.Which one of the following stereotype specifies a 115.. . . . . . . . . . standard constrint specifies that
classifier whose objects are all classes? [08S04] objects of the parent may have no more than one of the
1. metaclass. children as a type [09M02]
2. power type. 1. complete.
3. stereotype. 2. Incomplete.
4. utility. 3. Disjoint.
106.. . . . . . . . . . . . is a physical and replacable part of 4. Overlapping.
a system that conforms and provides the 116.Which one of the following constraint that relate to
realization of a set of interfaces. [08S05] changeablity of the instances of an association?
1. signal. [09M03]
2. Component. 1. implicit.
3. Node . 2. frozen.
4. Subsystem. 3. ordered.
107.. . . . . . . . .. is specification of an asynchronous 4. become.
stimulus communicated between instances. [08S06] 117.. . . . . . . . . . . . stereotype specifies that the
1. Signal. source instantiates the target template using the given
2. Component. actual parameters [09S01]
3. Node 1. bind.
4. Subsystem 2. derive.
108.. . . . . . . . . . . is a description of a set of sequence 3. friennd.
of actions, including variants,that a system 4. powertype.
performs that yields an observable result of value to a 118.Which one of the following stereotype specifies that
particular actor. [08S07] the source is at a finer degree of abstraction than
1. Signal. the target? [09S02]
2. Component 1. bind
3. Node. 2. friend
4. Usecase 3. derive,
109. . . . . . . . . . stereotype specifies a classifier whose 4. refine.
objects are the children of a given parent. [08S08] 119.A semantic variation of generation in which a child
1. Signal. may have more than one parent is called. [09S03]
2. Component 1. single inheritance.
2. multiple inheritance. 1. classes
3. inheritance. 2. objects
4. double inheritance. 3. interfaces .
120.Which one of the following stereotype is used in 4. names
generalization relationships? [09S04] 130.An__is a collection of operations that are used to
1. send. specify a service of a class/component. [10S01]
2. trace. 1. item
3. implementation. 2. interface
4. instantiate. 3. integrity
121.A . . . . . . . . is a semantic relationship between 4. iterative
classifiers in which one classifiers a contract that 131.. . . . . . . . . . stereo type specifies a package that
another classifier guarantees to carry out. [09S05] is only a view on some other Package [10S02]
1. association. 1. facade
2. Generalization. 2. frame work
3. Composition. . 3. stub
4. Realization. 4. system
122.. . . . . . . . . . . . . is really just a special kind of 132.A . . . . . . is the behavior of an entry participating
association is specified by adorning a plain association in a particular context. [10S03]
with a field diamond at the whole end. [09S06] 1. type
1. Composition. 2. component
2. Interface specifier. 3. Name
3. Association class. 4. Role
4. Realization class. 133.Stereotype specifies a package consisting mainly of
123.. . . . . . . . . . . is an association attitude whose patterns [10S04]
values partition the set of objects related to an object 1. facade
across an association. [09S07] 2. frame work
1. Navigation 3. stub
2. Visibility. 4. system
3. Qualification. 134.A . . . . . . is a general purpose mechanism for
4. Composition. organization elements into groups. [10S05]
124. . . . To constraint specifies that the relationship is 1. type.
not manifest but,rather,is only conceptual. [09S08] 2. Role.
1. implicit. 3. Package.
2. frozen. 4. Class.
3. ordered. . 135.A . . . . . . is rendered as a tabbed folder. [10S06]
4. become. 1. class
125.. . . . . . . . . stereotype specifies that the source 2. component
operation invokes the target operation. [09S09] 3. node
1. become 4. package
2. call . 136.A . . . . . . . . . . . is a parameterized element.
3. copy. [11D01]
4. send. 1. class.
126.A . . . . . . relationship is rendered as a dashed 2. object.
directed line with a large open arrowhead pointing to 3. template.
the relationship [10D01] 4. active class.
1. generalization. 137.which diagrams are similar to class diagrams ?
2. Realization. [11M01]
3. Aggregation. 1. component and deployment
4. Dependency 2. object and deployment
127.. . . . . . . . stereotype specifies a package that 3. state chart & object
serves as a proxy for the public contents of another 4. flow chart & state chart
package [10D02] 138.Which one of the following attribute declaration is
1. facade legal of name, multiplication & type? [11M02]
2. frame work 1. name : string.
3. stub 2. + orgin.
4. system 3. head:*item.
128.Which one of the following stereotype specifies that 4. namejO.1J : string.
the source package has access to the contents 139.. . . . . . is the process of transforming a model into
of the target? [10M01] code through a mapping to an implementation
1. import language. [11S01]
2. export 1. forward engineering
3. frame work 2. reverse engineering
4. stub 3. revise engineering
129.. . . . . . . . may also be used to specify a contact 4. refine engineering
for a use case or subsystem. [10M02]
1. interaction
2. object
3. use case
4. activity
152.An object diagram is essentially the static port of
an . . . . . . . diagram [12S03]
140.. . . . . is the process of transforming code into a
1. interaction
model through a mapping from a specific
2. object .
implementation language. [11S02]
3. use case
1. forward engineering
4. activity
2. reverse engineering
153.. . . . . . . . is a concrete manifestation of an
3. revise engineering
abstraction [12S04]
4. refine engineering
1. object
141.Class diagrams are not useful [11S03]
2. class
1. to model the vocabulary of a system
3. state
2. to model simple collaborations
4. component
3. to model a logical database schema
154.. . . . . . . diagrams let you model static data
4. to model simple interactions
structures [12S05]
142.common use of class diagrams is [11S04]
1. object
1. to model simple interactions
2. class
2. to model object diagram
3. state
3. to model the vocabulary of a system
4. component
4. to model the life cycle of a system.
155.. . . . . . . is an instance of a class [12S06]
143.You can explicitly specify that there are more
1. interaction
attributes or properties than shown by ending each list
2. use case
with an . . . . . . . .. [11S05]
3. activity
1. circles. .
4. object
2. squares.
156.. . . . . . . . . . . can be drawn in a separate
3. ellipsis.
comportment at the bottom of the class icon. [13D01]
4. stereotypes.
1. usability.
144.Aggregation is a . . . . . . . . . kind of relationship .
2. responsibility.
[11S06]
3. package.
1. is-a.
4. state.
2. to-a.
157.Which one of the following diagram is used to
3. was-a.
model a logical database schema ? [13G01]
4. has-a.
1. a code into a model
145.A . . . . . . . is a mechanism that describes
2. a model into test
structural and behavioral features.[11S07]
3. a code into design
1. class.
4. a model into a code
2. classifier.
158.To model a schema [13M01]
3. object.
1. create a class diagram that contains these
4. entity. classes & mark them as persistent
146.The static part of an interaction diagram is [12D01]
2. create a class diagram that contains these classes &
1. class diagram
mark them as database
2. deployment diagram
3. create a class diagram that contains these classes &
3. component diagram
mark them as java
4. object diagram
4. create a class diagram that contains these classes &
147.Anonymous object is declared as [12D02]
mark them as schema
1. p:person
159.A . . . . . . . . . is a contract or an obligation of a
2. p: .
class. [13M02]
3. :person
1. usability.
4. p:q:person
2. responsibility.
148.A link in object diagrams is rendered as [12M01]
3. package.
1. dashed line
4. state.
2. solid line
160.Which one of the following diagrams is used to
3. direction triangle
model simple collaborations ? [13S01]
4. filled diamond
1. object 2. class 3. use case 4. activity
149.Object diagrams are used to model [12M02]
161.Forward engineering in UML is the process of
1. class structures
transforming [13S02]
2. solid structures
1. a code into a model
3. object structures
2. a model into test
4. activity structures
3. a code into design
150.An . . . . . . . diagram is essentially an instance of a
4. a model into a code
class diagram [12S01]
1. interaction
2. object
3. use case
4. activity
151.An . . . . . . diagram represents one static frame in
the dynamic story board represented by an
interaction diagram [12S02]
3. template.
4. active class.
172.Which one of the following diagram is used to
model a logical database schema ? [14S01]
1. a code into a model
2. a model into test
162.Reverse engineering in UML is the process of
3. a code into design
transforming [13S03]
4. a model into a code
1. a code into a model
173.. . . . . . . diagrams let you model static data
2. a model into test
structures [14S02]
3. a code into design
1. object
4. a model into a code
2. class
163.An operation is said to be polymorphic when
3. state
[13S04]
4. component
1. you can specify operations with the same
174.Class diagrams are not useful [14S03]
signature at different print in the hierarchy.
1. to model the vocabulary of a system
2. you can specify operations with the different
2. to model simple collaborations
signature at same print in the hierarchy
3. to model a logical database schema
3. you can specify operations with the different
4. to model simple interactions
signature at different print in the hierarchy
175.common use of class diagrams is [14S04]
4. you can specify operations with the same signature
1. to model simple interactions
at same print in the hierarchy
2. to model object diagram
164.. . . . . . . . . . . is a physical and replicable part of a
3. to model the vocabulary of a system
system that conforms and provides the realization
4. to model the life cycle of a system.
of a set of interfaces. [13S05]
176.A well structured object diagram. [15D01]
1. signal.
1. is focused on communicating one aspect of a systems
2. Component.
dynamic process view
3. Node.
2. representation one frame in the static story board
4. Subsystem.
represented by an interaction diagram.
165.The visibility of private is . [13S06]
3. representation one frame in the dynamic story
1. + 2. # 3. - 4. I board represented by an interaction diagram
166.An operation is said to be polymorphic when 4. representation one frame in the static story board
[14D01] represented by an class diagram
1. you can specify operations with the same
177.. . . . . . . . is a concrete manifestation of an
signature at different print in the hierarchy
abstraction [15D02]
2. you can specify operations with the different
1. object
signature at same print in the hierarchy
2. class
3. you can specify operations with the different
3. state
signature at different print in the hierarchy
4. component
4. you can specify operations with the same signature
178.A well structured object diagram [15M01]
at same print in the hierarchy 1. is not minimalist as to inform the reader about
167.You can explicitly specify that there are more semantics that are important
attributes or properties than shown by ending each list 2. is not minimalist as to misinform the reader about
with an . . . . . . . . . . . .. [14D02] semantics that are important
1. circles. 3. is so minimalist as to misinform the reader about
2. squares. semantics that are important
3. ellipsis.
4. is so minimalist as to inform the reader about
4. stereotypes. semantics that are important
168.. . . . . is the process of transforming code into a 179.. . . . . . diagrams model the instances of things
model through a mapping from a specific contained in class diagrams. [15M02]
implementation language [14D03] 1. class
1. forward engineering 2. use case
2. reverse engineering
3. activity
3. revise engineering 4. object
4. refine engineering 180.which one of the following diagram is used to
169.Class diagrams are not useful [14G04] model object structures? [15S01]
1. to model the vocabulary of a system 1. class
2. to model simple collaborations 2. use case
3. to model a logical database schema 3. activity
4. to model simple interactions 4. object
170.Which one of the following diagrams is used to 181.Forward engineering an . . . . . . is theoretically
model simple collaborations ? [14M01] possible but programmatically of limited value [15S02]
1. object 1. class diagram
2. class . 2. object diagram
3. use case 3. use case diagram
4. activity
171.A . . . . . . . . . . . is a parameterized element.
[14M02]
1. class.
2. object.
192.. . . . . . action creates an object [16S04]
1. create
2. establish
3. creator
4. establisher
193.The programming language like C++ is [16S05]
4. activity diagram
1. statically typed
182.. . . . . . diagrams reflect some of the concrete or
2. dynamically typed
proto typical objects that live in the running system
3. casually typed
[15S03]
4. formally typed
1. class diagram
194.. . . . . . diagrams permit you to model the lifetime
2. object diagram
of an object [17D01]
3. use case diagram
1. collaboration
4. activity diagram
2. sequence
183.An . . . . . . diagram represents one static frame in
3. activity
the dynamic story board represented by an
4. state chart
interaction diagram. [15S04]
195.Which one of the following diagram is largely
1. interaction
isomorphic ? [17D02]
2. object
1. activity
3. use case
2. use case
4. activity
3. sequence
184.An object diagram is essentially the static port of
4. behavioral
an . . . . . . . diagram. [15S05]
196.When you model an interaction you typically
1. interaction
include both . . . . . & . . . . . [17M01]
2. object .
1. class and use case
3. use case
2. messages and roles
4. activity
3. states and components
185.An . . . . . . . is a behavior comprises a set of
4. objects and information
messages exchanged among a set of objects within a
197.. . . . . . . is defined as that you can take one and
context to accomplish a purpose [16D01]
transform it into the other without loss of information
1. iteration
[17M02]
2. activity 1. isomorphic
3. use case 2. collaboration
4. interaction
3. interaction
186.. . . . . . . stereotype specifies that the
4. deployment
corresponding object is visible because it is the
198.A . . . . . . . . consistent specifies that the instance
dispatches of the operation [16D02]
or link is created during execution of the enclosing
1. associate 2. self 3. global 4. local
interaction. [17S01]
187.A . . . . is a specifications of a communication 1. new
between objects that conveys information with the 2. destroyed
expectation that activity will ensure [16M01] 3. transient
1. link 4. transform
2. call 199.A . . . . . . . . constraint specifies that the instance
3. message
or link is treated during execution of execution of
4. statement
the enclosing interaction [17S02]
188.. . . . . . . stereotype specifies that the
1. new
corresponding objects is visible because it is in an 2. destroyed
enclosing 3. transient
scope [16M02] 4. transform
1. associate 200.A . . . . . . constraint you to model the instance or
2. self . link is treated during execution of the enclosing
3. global
interaction but is destroyed before completion of
4. local
execution. [17S03]
189.. . . . stereotype specifies that the corresponding
1. new
objects is visible because it is in an local scope
2. destroyed
[16S01] 3. transient
1. associate 4. transform
2. self 201.. . . . . diagrams permit you to model the structural
3. global links that may exist among the objects in an
4. local
interaction [17S04]
190.An object may commit suicide by destroying itself 1. collaboration
with [16S02] 2. sequence
1. kill 3. activity
2. murder 4. state chart
3. destroy
4. die
191.. . . . . action sends a signal to an object [16S03]
1. call
2. send
3. move
4. call by
214.What distinguishes collaboration diagrams from
sequence diagrams ? [19D02]
1. There is the random number
2. There is the sequence number
3. There is the object lifeline
4. There is the focus of control
202.You can specifies a procedural or nested flow of 215.An object life time is the . . . . . . that represents
control rendered using . . . [17S05] the existence of an object over a period of time.
1. a filled solid square [19M01]
2. a filled solid cube 1. vertical dashed line
3. a filled solid rectangle 2. horizontal dashed line
4. a filled solid arrow head 3. vertical line
203.Which of the following diagram is largely 4. horizontal line
isomorphic ? [17S06] 216.What distinguishes sequence diagrams from
1. activity collaboration diagrams ? [19M02]
2. collaboration 1. There is the object life line
3. use case 2. There is the focus of messages
4. behavioral 3. There is the path
204.Objects lifelines end with the receipt of the 4. There is the sequence number
message stereotype as . . . . . . [18D01] 217.Sequence diagram is a [19S01]
1. create 2. destroy 3. kill 4. murder 1. structural diagram
205.A . . . . . diagram emphasizes the time ordering at 2. behavioral diagram
messages [18D02] 3. flat diagram
1. collaboration 4. annotational diagram
2. sequence 218.Collaboration diagram is a [19S02]
3. activity . 1. structural diagram
4. use case 2. behavioral diagram
206.A . . . . . . diagram is a table that shows objects 3. flat diagram
arranged along the X-axis and messages ordered in 4. annotational diagram
increasing time along Y-axis. [18M01] 219.. . . . . . stereotype specifies that the corresponding
1. collaboration object is visible because it is the dispatches of the
2. sequence operation. [19S03]
3. activity 1. associate
4. use case 2. self .
207.A . . . . . . diagram is an interaction diagram that 3. global
emphasizes the structural organization of the objects 4. local
that send and receive messages. [18M02] 220.. . . . . . . stereotype specifies that the
1. collaboration corresponding objects is visible because it is in an
2. sequence enclosing
3. activity scope. [19S04]
4. use case 1. associate
208.Interaction diagrams are [18S01] 2. self
1. sequence diagrams & collaboration diagrams 3. global
2. collaboration diagrams & use case diagrams 4. local
3. sequence diagrams & activity diagrams 221.. . . . stereotype specifies that the corresponding
4. activity diagrams & state chart diagrams objects is visible because it is in an local scope.
209.. . . . . action sends a signal to an object [18S02] [19S05]
1. call 2. send 3. move 4. call by 1. associate
210.. . . . . . action creates an object [18S03] 2. self
1. create 3. global
2. establish 4. local
3. creator 222.. . . . . . diagrams permit you to model the lifetime
4. establisher of an object. [19S06]
211.The programming language like C ++ is [18S04] 1. collaboration
1. statically typed 2. sequence
2. dynamically typed 3. activity .
3. casually typed 4. state chart
4. formally typed 223.Collaboration diagrams use . . . . . . . relationship
212.When you model an interaction you typically [20D01]
include both . . . . . & . . . . .[18S05] 1. depending
1. class and use case 2. association
2. messages and roles 3. generalization
3. states and components 4. message
4. objects and information 224.A well- structured interaction diagram [20D02]
213.Which one of the following diagrams has the
sequence number ? [19D01]
1. sequence
2. collaboration
3. activity
4. use case
1. is focused on communicating two aspects of a
systems dynamics.
2. is focused on communicating four aspects of a
systems dynamics
3. is focused on communicating three aspects of a
systems dynamics
4. is focused on communicating one aspects of a
systems dynamics
225.Common modeling technique of interaction diagram
is [20M01]
1. to model flows of control by time ordering
2. to model flows of control by use cases
3. to model flows of control by states
4. to model flows of control by use ordering
226.To model flow of control by time ordering [20M02]
1. set the life line for each class
2. set the life line for each use case •
3. set the life line for each state
4. set the life line for each object
227.. . . . diagrams do a better job of visualizing
complex iteration and branching and of visualizing
multiple concurrent flow of control than do sequence
diagrams. [20S01]
1. Use case
2. Collaboration
3. Activity
4. State chart.
228.. . . . . . . is defined as that you can take one and
transform it into the other without loss of information
[20S02]
1. Isomorphic
2. Collaboration
3. Interaction
4. Deployment
229.You can specifies a procedural or nested flow of
control rendered using . . . . . . . .[20S03]
1. a filled solid square
2. a filled solid cube
3. a filled solid rectangle
4. a filled solid arrow head
230.. . . . . action sends a signal to an object [20S04]
1. call
2. send
3. move
4. call by