adplus-dvertising

Welcome to the Requirements Engineering MCQs Page

Dive deep into the fascinating world of Requirements Engineering with our comprehensive set of Multiple-Choice Questions (MCQs). This page is dedicated to exploring the fundamental concepts and intricacies of Requirements Engineering, a crucial aspect of Software Engineering. In this section, you will encounter a diverse range of MCQs that cover various aspects of Requirements Engineering, 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 Requirements Engineering. 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 Requirements Engineering. You can click on an option to test your knowledge before viewing the solution for a MCQ. Happy learning!

Requirements Engineering MCQs | Page 18 of 30

Explore more Topics under Software Engineering

Q171.
What is the goal of goal-driven requirements engineering?

a.

To create a graph connecting high-level goals to lower-level requirements

b.

To decompose high-level requirements into lower-level ones

c.

To link requirements to specific stakeholders

d.

To elicit and structure requirements in a hierarchical structure

Discuss
Answer: (a).To create a graph connecting high-level goals to lower-level requirements Explanation:Goal-driven requirements engineering aims to create a graph connecting high-level goals to lower-level requirements, which can be reasoned about to validate that certain goals are reached or to detect conflicts.
Q172.
What are the different types of relationship that can be included in goal-driven requirements engineering?

a.

AND-relations and OR-relations

b.

Conflicting and supporting relationships

c.

Parent-child relationships

d.

All of the above

Discuss
Answer: (a).AND-relations and OR-relations Explanation:In goal-driven requirements engineering, requirements can be refined into a set of subrequirements that together satisfy the parent requirement. The subrequirements are AND-related, and other types of relationships such as OR-relations can also be included.
Q173.
What is the purpose of collecting and organizing requirements from different perspectives in goal-driven requirements engineering?

a.

To identify and resolve conflicts between different stakeholders

b.

To create a hierarchical structure of goals and requirements

c.

To gather information about different quality concerns

d.

All of the above

Discuss
Answer: (a).To identify and resolve conflicts between different stakeholders Explanation:Collecting and organizing requirements from different perspectives in goal-driven requirements engineering allows for the identification and resolution of conflicts between different stakeholders, and different quality concerns can also be taken into account.
Q174.
What is the purpose of the gIBIS system in goal-driven requirements engineering?

a.

To capture early design decisions

b.

To store, trace and manipulate the diverse types of information gathered during the requirements engineering phase

c.

To provide an automated system for resolving conflicts between different stakeholders

d.

All of the above

Discuss
Answer: (b).To store, trace and manipulate the diverse types of information gathered during the requirements engineering phase Explanation:The gIBIS system is designed to capture early design decisions and store, trace and manipulate the diverse types of information gathered during the requirements engineering phase.
Q175.
Who usually propagates the business viewpoint during requirements engineering?

a.

End users

b.

Management stakeholders

c.

Library employees

d.

Journal subscribers

Discuss
Answer: (b).Management stakeholders Explanation:The business viewpoint is usually propagated by management stakeholders.
Q176.
Who usually propagates the personal viewpoint during requirements engineering?

a.

End users

b.

Management stakeholders

c.

Library employees

d.

Journal subscribers

Discuss
Answer: (a).End users Explanation:The personal viewpoint is usually propagated by end users.
Q177.
At what stage do end users tend to ascribe to business requirements?

a.

Early stage

b.

Middle stage

c.

Late stage

d.

Never

Discuss
Answer: (a).Early stage Explanation:The end users tend to ascribe to business requirements at an early stage.
Q178.
What is the MoSCoW scheme used for in requirements prioritization?

a.

To distinguish between mandatory and optional requirements

b.

To prioritize customer preferences into five categories

c.

To differentiate between attractive and boring features

d.

To order customer requirements along a single axis

Discuss
Answer: (a).To distinguish between mandatory and optional requirements Explanation:The MoSCoW scheme is used to distinguish between four types of requirements: Must haves, Should haves, Could haves, and Won't haves. These categories are used to prioritize the requirements and ensure that the most important ones are realized.
Q179.
What is the Kano model in requirements prioritization?

a.

A model used to order requirements along a single axis

b.

A scheme used to distinguish between mandatory and optional requirements

c.

A classification of user preferences into five categories

d.

A way to differentiate between attractive and boring features

Discuss
Answer: (c).A classification of user preferences into five categories Explanation:The Kano model classifies user preferences into five categories: Attractive, Must-be, One-dimensional, Indifferent, and Reverse. This model is used to better understand the customers' requirements and how they value different features in a system.
Q180.
What does the Kano model suggest about offering attractive features to customers?

a.

Offering these features is not important

b.

Offering these features will not excite customers

c.

Offering these features is what will really excite customers

d.

Offering these features is not feasible

Discuss
Answer: (c).Offering these features is what will really excite customers Explanation:According to the Kano model, offering attractive, so-called "killer features" is what will really excite customers. These features are seen as the key to satisfying customers and making the system appealing to them.
Page 18 of 30

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!

C Programming

Master one of the most widely used programming languages with our C Programming MCQs....

MongoDB

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

MySQL Database

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

Cryptography and Network Security

Secure your knowledge of information security with our Cryptography and Network...

Digital Image Processing (DIP)

Delve into the techniques of enhancing digital images with our Digital Image...

Visual Basic

Enhance your knowledge of Microsoft's event-driven programming language with our...

DBMS

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

CSS

Polish your web design skills with our CSS MCQs. Learn about selectors, properties,...

PHP

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