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

Explore more Topics under Software Engineering

Q581.
What are the reasons for the design process not being rational?

a.

Intangibles of design processes

b.

Accidents that happen to befall many a software project

c.

Users know exactly what they want

d.

No changes are made during the project

Discuss
Answer: (a).Intangibles of design processes Explanation:There are many reasons why the design process cannot be rational. Some of these have to do with the intangibles of design processes per se, some originate from accidents that happen to befall many a software project.
Q582.
Which design approach meets the requirement of a software architecture?

a.

Bottom-up approach

b.

Top-down approach

c.

Neither of the above

d.

Both of the above

Discuss
Answer: (c).Neither of the above Explanation:A bottom-up or top-down approach does not meet the requirement of a software architecture, since in both these approaches only part of the solution is available at intermediate points in time.
Q583.
What is the first guideline offered by Parnas (1978) for a sound functional decomposition?

a.

Apply the information hiding principle

b.

Apply the uses-relation and place the dependencies in a hierarchical structure

c.

Try to define extensions to the base machine step by step

d.

Try to identify subsystems and start with a minimal subset

Discuss
Answer: (d).Try to identify subsystems and start with a minimal subset Explanation:The first guideline offered by Parnas (1978) for a sound functional decomposition is to try to identify subsystems and start with a minimal subset, adding functionality incrementally.
Q584.
What is the purpose of the information hiding principle in functional decomposition?

a.

To apply incremental extensions to the base machine

b.

To create a layered system structure

c.

To create a hierarchical tree structure of system components

d.

To minimize the visibility of a module's design details

Discuss
Answer: (d).To minimize the visibility of a module's design details Explanation:Parnas (1978) states the guideline of applying the information hiding principle, which is aimed at minimizing the visibility of a module's design details.
Q585.
How does the idea of incremental extensions to the base machine align with a layered architectural style?

a.

It creates a strict hierarchical tree structure of system components

b.

It results in a layered system structure

c.

It aligns with a virtual machine view of the module hierarchy

d.

It results in a flat system structure

Discuss
Answer: (c).It aligns with a virtual machine view of the module hierarchy Explanation:Parnas (1978) states that applying incremental extensions to the base machine results in the concept of a virtual machine, and each layer in the system hierarchy can be viewed as a machine. This aligns with a layered architectural style.
Q586.
What is the goal of the uses-relation guideline in functional decomposition?

a.

To minimize the visibility of a module's design details

b.

To create a layered system structure

c.

To create a hierarchical structure of the dependencies obtained

d.

To try to identify subsystems and start with a minimal subset

Discuss
Answer: (c).To create a hierarchical structure of the dependencies obtained Explanation:The guideline of applying the uses-relation and trying to place the dependencies thus obtained in a hierarchical structure is aimed at creating a hierarchical structure of the dependencies obtained.
Q587.
What is Data Flow Design (SA/SD)?

a.

A program structure represented as a set of structure charts.

b.

A two-step process of data flow design.

c.

A method of transforming a logical design into a program structure.

d.

A functional decomposition with respect to the flow of data.

Discuss
Answer: (b).A two-step process of data flow design. Explanation:Data Flow Design (SA/SD) is a two-step process consisting of Structured Analysis (SA) and Structured Design (SD).
Q588.
What is the purpose of Structured Analysis in Data Flow Design (SA/SD)?

a.

To refine the diagram to improve the functional decomposition of the system.

b.

To transform the logical design into a program structure.

c.

To model the Universe of Discourse.

d.

To map the information flow contained in data flow diagrams into a program structure.

Discuss
Answer: (c).To model the Universe of Discourse. Explanation:Structured Analysis (SA) is the first step of the Data Flow Design (SA/SD) process and it addresses the modeling of the Universe of Discourse.
Q589.
What is Structured Design in Data Flow Design (SA/SD)?

a.

A proper requirements analysis method.

b.

A strategy to map the information flow contained in data flow diagrams into a program structure.

c.

A functional decomposition with respect to the flow of data.

d.

A two-step process of data flow design.

Discuss
Answer: (b).A strategy to map the information flow contained in data flow diagrams into a program structure. Explanation:Structured Design (SD) is the second step of the Data Flow Design (SA/SD) process and it is a strategy to map the information flow contained in data flow diagrams into a program structure.
Q590.
What is the purpose of a context diagram in SA/SD?

a.

To depict the interaction of the system with the environment

b.

To describe the structure of the input and output to the central process

c.

To transform the logical design into a program structure

d.

To perform a proper requirements analysis method

Discuss
Answer: (a).To depict the interaction of the system with the environment Explanation:The purpose of a context diagram in SA/SD is to depict the interaction of the system with the environment, which is the collection of external entities.
Page 59 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!

MySQL Database

Enhance your knowledge of relational databases with our MySQL MCQs. Understand...

Computer Architecture

Unveil the science behind computer design with our Computer Architecture MCQs. Topics...

Embedded Systems

Dive into the world of specialized computing systems with our Embedded Systems MCQs....

PHP

Venture into server-side scripting with our PHP MCQs. Cover everything from syntax...

Neural Networks

Dive into the world of Artificial Intelligence with our Neural Networks MCQs. Uncover...

Data Structures and Algorithms

Journey through the fundamentals of Data Structures and Algorithms with our extensive...

DBMS

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

Human Computer Interaction

Enhance your knowledge of Human-Computer Interaction with our specialized MCQs....

Wireless and Mobile Communications

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