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 50 of 79

Explore more Topics under Software Engineering

Q491.
What are the two classes of software attributes considered in measuring software complexity?
Discuss
Answer: (b).Intra-modular and inter-modular attributes Explanation:The type of software attributes considered in measuring software complexity can be broadly categorized into two classes: intra-modular attributes which are attributes of individual modules, and inter-modular attributes which are attributes of a system viewed as a collection of modules with dependencies.
Discuss
Answer: (c).To assess the quality of a design or program Explanation:The purpose of measuring software complexity in quantitative terms is to assess the quality of a design or program, to guide reengineering efforts, etc.
Discuss
Answer: (c).A metric that measures the effort needed to develop a piece of software Explanation:Size-based complexity metrics measure the size of a piece of software such as the number of lines of code, and it gives a fair indication of the effort needed to develop that piece of software.
Discuss
Answer: (d).A metric that measures the design quality of a piece of software Explanation:Structure-based complexity metrics measure the structure of a piece of software and is a good indicator of its design quality because a program that has a complicated control structure or uses complicated data structures is likely to be difficult to comprehend and maintain, and thus more complex.
Discuss
Answer: (d).By counting the number of lines of code Explanation:The easiest way to measure software size is to count the number of lines of code.
Q496.
What is the ideal size of a module according to (Weinberg, 1971)?
Discuss
Answer: (b).30 lines of code Explanation:In (Weinberg, 1971), for instance, the ideal size of a module is said to be 30 lines of code.
Discuss
Answer: (d).Based on research in psychology that suggests human memory has a short-term memory of about seven slots Explanation:This number seven can be traced back to research in psychology, which suggests that human memory is hierarchically organized with a short-term memory of about seven slots, while there is a more permanent memory of almost unlimited capacity.
Discuss
Answer: (d).All of the above Explanation:There are serious objections to the direct use of the number of lines of code as a complexity metric. Some programmers write more verbose programs than others. We should at least normalize the counting to counteract these effects and be able to compare different pieces of software. This can be achieved by using a prettyprinter, a piece of software that reproduces programs in a given language in a uniform way. A second objection is that this technique makes it hard to compare programs written in different languages. If the same problem is solved in different languages, the results may differ considerably in length.
Q499.
What does Halstead's method, also known as 'software science', use to overcome the problems associated with metrics based on a direct count of lines of code?
Discuss
Answer: (b).The number of unique operators and operands in the program Explanation:Halstead’s method, also known as β€˜software science’, uses a refinement of counting lines of code. This refinement is meant to overcome the problems associated with metrics based on a direct count of lines of code. Halstead’s method uses the number of operators and operands in a piece of software.
Discuss
Answer: (a).It's a research finding from psychology Explanation:The number seven can be traced back to research in psychology, which suggests that human memory has a short-term memory of about seven slots.

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!