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 11 of 30

Discuss
Answer: (c).To reach a consensus among a group of users through written communication Explanation:The Delphi technique is an iterative process in which information is exchanged in written form among a group of users until a consensus is reached.
Q102.
What is one way to overcome the problem of some users having more influence than others in discussion sessions?
Discuss
Answer: (c).Using the Delphi technique Explanation:The Delphi technique is used to overcome the problem of some users having more influence than others in discussion sessions by allowing all participants to reflect and provide input on the requirements until a consensus is reached.
Discuss
Answer: (c).When users refuse to decompose tasks any further Explanation:The major heuristic for task analysis is that at some point users tend to ‘refuse’ to decompose tasks any further. For instance, when being asked how the member identification is checked, the library employee may say ‘Well, I simply check his id.’ At this point, further decomposition is meaningless.
Discuss
Answer: (b).It studies instances of tasks Explanation:Scenario-based analysis Instead of looking for generic plans as in interviews or task analysis, the analyst may study instances of tasks. A scenario is a story which tells us how a specific task instance is executed. The scenario can be real or artificial.
Discuss
Answer: (d).A method for verbalizing what one is doing and making an audio or video recording thereof Explanation:The think aloud method is a fairly unobtrusive technique to study people at work. It is often used to assess prototypes or existing information systems. The method is asking the library employee to verbalize what he is doing and making an audio or video recording thereof.
Q106.
In scenario-based analysis, what type of scenarios can be used?
Discuss
Answer: (c).Both real and artificial Explanation:Scenario-based analysis uses scenarios that can be real or artificial. An example of a real scenario is that the analyst observes how a library employee handles an actual user request, Alternatively, we may construct artificial scenarios and discuss these with the user.
Discuss
Answer: (a).To gain a better understanding of the requirements Explanation:Scenario-based analysis serves as a paper-based prototype to gain a better understanding of the requirements.
Q108.
What is another name for scenario-based analysis when tied to a UML-type of modeling?
Discuss
Answer: (a).Use-case analysis Explanation:When tied to a UML-type of modeling, scenario-based analysis is often called use-case analysis.
Discuss
Answer: (c).It is only done in a haphazard way Explanation:Scenario-based analysis is often done in a somewhat haphazard way, which can make it difficult to determine if enough scenarios have been drawn up and if a sufficiently accurate and complete picture of the requirements is obtained.
Q110.
From what perspective can scenarios be looked at?
Discuss
Answer: (d).All of the above Explanation:Scenarios can be looked at from different perspectives such as the process aspect, showing how the system proceeds through successive states, the user perspective, how will the user interact with the system, what functionalities will she be offered, and the design perspective, leads to discussions about alternatives from which a certain choice has to be made.

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!