Q48,p3,j15. A software design is highly modular if:

A) Cohesion is functional and coupling is data type.
 B)Cohesion is coincidental and coupling is data type.

c) Cohesion is sequental  and coupling is content type.
D) Cohesion is functional and coupling is stamp type.
Answer A.

Q47,p3,j15. A design concept refinement is a.

A) Top down Approach.
B) Complimentary of abstraction concept.
C)Process of elaboration.
D)All of the above.
Answer D

Q46,p3,j15.Adaptive maintenance is a maintenance which---------------------------------------

A)correct errors that were not discovered till testing phase.
B) is carried out to port the existing software to new environment.
C)improves system performance.
D)both b.c
Answer D.

Q45,p3,j15, Requirement prioritisation and negotiation belongs to.

A) requirement validation.
B) Requirement elicitation.
C)Feasibility study.
D)Requirement reviews.

Answer B.

Q44,P3,J15 Which design metric is used to measure the compactness of the program in terms of line of code.?

A) Consistency.
B) Conciseness.
C) Efficiency.
D) Accuracy.

Answer B.

Q43,p3,j15. Verification.

A) Refers to the set of activities that ensure that software correctly implements a specific function.
B)Give answers to questions- Are we building the product right.
C)requires execution of software.
D) Both A,B
Answer D

Q42,p3,j15.Module design is used to maximize cohesion and minimize coupling. which one of the follwing is the key to implement this rule.

A) Inheritance.
B)Polymorphism .
C)Encapsulation.
D) Abstraction.
Answer C.

Explanation.

The basic idea underlying modular design is to organize a complex system (such as a large program, an electronic circuit, or a mechanical device) as a set of distinct components that can be developed independently and then plugged together. Although this may appear a simple idea, experience shows that the effectiveness of the technique depends critically on the manner in which systems are divided into components and the mechanisms used to plug components together. The following design principles are particularly relevant to parallel programming.  Ensure that modules hide information.

• related functions that can benefit from a common implementation or that are used in many parts of a system,

• functionality that is likely to change during later design or deployment,

• aspects of a problem that are particularly complex, and/or

• code that is expected to be reused in other programs.

The benefits of modularity do not follow automatically from the act of subdividing a program. The way in which a program is decomposed can make an enormous difference to how easily the program can be implemented and modified. Experience shows that each module should encapsulate information that is not available to the rest of a   program. This information hiding reduces the cost of subsequent design changes.