adplus-dvertising

Welcome to the Software Design Concepts MCQs Page

Dive deep into the fascinating world of Software Design Concepts with our comprehensive set of Multiple-Choice Questions (MCQs). This page is dedicated to exploring the fundamental concepts and intricacies of Software Design Concepts, a crucial aspect of Software Engineering. In this section, you will encounter a diverse range of MCQs that cover various aspects of Software Design Concepts, from the basic principles to advanced topics. Each question is thoughtfully crafted to challenge your knowledge and deepen your understanding of this critical subcategory within Software Engineering.

frame-decoration

Check out the MCQs below to embark on an enriching journey through Software Design Concepts. Test your knowledge, expand your horizons, and solidify your grasp on this vital area of Software Engineering.

Note: Each MCQ comes with multiple answer choices. Select the most appropriate option and test your understanding of Software Design Concepts. You can click on an option to test your knowledge before viewing the solution for a MCQ. Happy learning!

Software Design Concepts MCQs | Page 55 of 79

Explore more Topics under Software Engineering

Q541.
What is the definition of global flow in the context of information flow between modules in a system?

a.

A global flow from module A to module B exists if A updates some global data structure and B retrieves from that structure.

b.

A global flow from module A to module B exists if A invokes B and passes it a parameter.

c.

A global flow from module A to module B exists if B invokes A and A returns a value.

d.

None of the above

Discuss
Answer: (a).A global flow from module A to module B exists if A updates some global data structure and B retrieves from that structure. Explanation:A global flow from module A to module B exists if A updates some global data structure and B retrieves from that structure.
Q542.
Using notions of local and global data flow, Shepperd defines the β€˜complexity’ of a module M as

a.

Complexity(M) = fan-in(M) x fan-out(M)

b.

Complexity(M) = fan-in(M) / fan-out(M)

c.

Complexity(M) = fan-out(M) / fan-in(M)

d.

Complexity(M) = (fan-in(M) x fan-out(M))^2

Discuss
Answer: (d).Complexity(M) = (fan-in(M) x fan-out(M))^2 Explanation:The complexity of a module M is defined as Complexity(M) = (fan-in(M) x fan-out(M))^2 where, fan-in(M) is the number of (local and global) flows whose sink is M, and fan-out(M) is the number of (local and global) flows whose source is M.
Q543.
Who proposed the information flow measure?

a.

Henri and Kafura

b.

Shepperd

c.

Henri

d.

Both a and b

Discuss
Answer: (d).Both a and b Explanation:The best known attempt to measure the total level of information flow between the modules of a system is due to Henri and Kafura (1981). Shepperd (1990) also studied the information flow measure extensively and proposed several refinements.
Q544.
What is the purpose of the information flow metric?

a.

To determine the quality of software systems

b.

To identify spots in the design that deserve attention

c.

To define the distance between elements

d.

To determine the cohesion between elements

Discuss
Answer: (b).To identify spots in the design that deserve attention Explanation:If some module has a high fan-in, this may indicate that the module has little cohesion and an excessive increase from one level to the next might indicate a missing level of abstraction.
Q545.
What is the relationship between information-flow metric and the abstract data type architectural style?

a.

The style results in modules with low fan-in and fan-out

b.

The style results in modules with high fan-in and fan-out

c.

The style does not affect the information flow metric

d.

The style results in modules with equal fan-in and fan-out

Discuss
Answer: (b).The style results in modules with high fan-in and fan-out Explanation:The abstract data type architectural style easily results in modules with a high fan-in and fan-out.
Q546.
How does the choice of measure affect the grouping of elements?

a.

It determines the distance between elements

b.

It defines the friendship between elements

c.

It does not affect the grouping of elements

d.

It determines the cohesion between elements

Discuss
Answer: (b).It defines the friendship between elements Explanation:The measure chosen, in a sense, determines how we define 'friendship' between elements.
Q547.
What is WMC(Weighted Methods per Class) in the context of object-oriented metrics?

a.

A measure of the distance of a class to the root of its inheritance tree

b.

A measure of the complexity of a method

c.

A measure of the size of a class

d.

A measure of the relationships between modules

Discuss
Answer: (c).A measure of the size of a class Explanation:WMC (Weighted Methods per Class) is a measure for the size of a class in the context of object-oriented metrics. The assumption is that larger classes are generally less desirable and take more time to develop and maintain.
Q548.
What does DIT stand for in the context of object-oriented metrics?

a.

Distance of Inheritance Tree

b.

Depth of Inheritance Tree

c.

Distance of Interface Tree

d.

Depth of Interface Tree

Discuss
Answer: (b).Depth of Inheritance Tree Explanation:DIT (Depth of Inheritance Tree) is the distance of a class to the root of its inheritance tree in the context of object-oriented metrics.
Q549.
What is the formula for WMC(Weighted Methods per Class)?

a.

WMC = Ξ£ci

b.

WMC = Ξ£ci-1

c.

WMC = Ξ£ci^2

d.

WMC = Ξ£ci-2

Discuss
Answer: (a).WMC = Ξ£ci Explanation:The formula for WMC (Weighted Methods per Class) is WMC = Ξ£ci, where i is the complexity of method i.
Q550.
What is the purpose of WMC in object-oriented metrics?

a.

To measure the complexity of a method

b.

To measure the relationships between modules

c.

To measure the distance of a class to the root of its inheritance tree

d.

To measure the size of a class

Discuss
Answer: (d).To measure the size of a class Explanation:The purpose of WMC (Weighted Methods per Class) in object-oriented metrics is to measure the size of a class. The assumption is that larger classes are generally less desirable and take more time to develop and maintain.
Page 55 of 79

Suggested Topics

Are you eager to expand your knowledge beyond Software Engineering? We've curated a selection of related categories that you might find intriguing.

Click on the categories below to discover a wealth of MCQs and enrich your understanding of Computer Science. Happy exploring!

Computer Hardware

Explore the tangible components of computers with our Computer Hardware MCQs. Learn...

Digital Communication

Master the basics of electronic communication with our Digital Communication MCQs....

DBMS

Get a firm grasp on database systems with our DBMS MCQs. Explore relational...

Software Architecture and Design

Get a strong hold on the blueprint of software systems with our Software Architecture...

Compiler Design

Unravel the process of translating source code into executable programs with our...

Java Spring Framework

Enhance your Java development skills with our Spring Framework MCQs. Learn about...

Wireless and Mobile Communications

Get to grips with modern communication technologies with our Wireless and Mobile...

MongoDB

Learn the leading NoSQL database with our MongoDB MCQs. Understand everything from...

Formal Languages and Automata Theory

Discover the mathematical models of computation with our Formal Languages and...