Software Components set 4

31Que:When elements of module are grouped because the output of one element serves as input to another and so on, it is called ________ .
a.Functional cohesion
b.Sequential cohesion
c.Communicational cohesion
d.Procedural cohesion
32Que:From the following which method will be adopted in Reuse process?
a.Either by keeping requirements same and adjusting components
b.By keeping components same and modifying requirements
c.Both a and b
d.None of the above
33Que:Which tools are used to represent the system components, data and control flow among various software components and a system structure in a graphical form?
a.Process modeling tools
b.Project management tools
c.Diagram tools
d.Documentation tools
34Que:The data dictionary contains descriptions of each software
a.control item
b.data object
c.diagram
d.both a and b
35Que:Which of these is not an element of an object-oriented analysis model?
a.Behavioral elements
b.Class-based elements
c.Data elements
d.Scenario-based elements
36Que:Polymorphism reduces the effort required to extend an object system by
a.coupling objects together more tightly.
b.enabling a number of different operations to share the same name.
c.making objects more dependent on one another.
d.removing the barriers imposed by encapsulation.
37Que:When the overall flow in a segment of a data flow diagram is largely sequential and follows straight-line paths, _________ is present.
a.low coupling
b.good modularity
c.transaction flow
d.transform flow
38Que:When a single item that triggers other data flow along one of many paths of a data flow diagram, ________ characterizes the information flow.
a.high coupling
b.poor modularity
c.transaction flow
d.transform flow
39Que:In transaction mapping the first level factoring results in the
a.creation of a CFD
b.derivation of the control hierarchy
c.distribution of worker modules
d.refinement of the module view
40Que:A successful application of transform or transaction mapping to create an architectural design is supplemented by
a.entity relationship diagrams
b.module interface descriptions
c.processing narratives for each module
d.both b and c