adplus-dvertising
frame-decoration

Question

What are the two ways to structure a set of requirements?

a.

Hierarchical structure and viewpoint

b.

Goal-driven structure and hierarchical structure

c.

Viewpoint and goal-driven structure

d.

Stakeholder-driven structure and hierarchical structure

Posted under Software Engineering

Answer: (a).Hierarchical structure and viewpoint Explanation:One way to structure a set of requirements is in a hierarchical structure, where higher-level requirements are decomposed into lower-level ones. The other method is to link requirements to specific stakeholders, called viewpoints.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What are the two ways to structure a set of requirements?

Similar Questions

Discover Related MCQs

Q. What is the relationship between the subrequirements in a refinement structure?

Q. What type of link is used to connect conflicting requirements in a goal-driven requirements engineering approach?

Q. What is the main focus of different viewpoints in requirements engineering?

Q. What is the main goal of using the gIBIS system?

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

Q. What are the different types of relationship that can be included in goal-driven requirements engineering?

Q. What is the purpose of collecting and organizing requirements from different perspectives in goal-driven requirements engineering?

Q. What is the purpose of the gIBIS system in goal-driven requirements engineering?

Q. Who usually propagates the business viewpoint during requirements engineering?

Q. Who usually propagates the personal viewpoint during requirements engineering?

Q. At what stage do end users tend to ascribe to business requirements?

Q. What is the MoSCoW scheme used for in requirements prioritization?

Q. What is the Kano model in requirements prioritization?

Q. What does the Kano model suggest about offering attractive features to customers?

Q. What is the MoSCoW scheme in requirements prioritization?

Q. What are the four types of requirements in MoSCoW?

Q. What does the Kano model classify user preferences into?

Q. What is the main goal of prioritizing requirements in market-driven software development?

Q. What are the sources of information used to derive the list of requirements for a product in market-driven software development?

Q. What is the relationship between prioritizing requirements and scoping in software product lines?