Software Requirements Chapter 11 Quiz
18 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is a common question an analyst can ask to encourage customers to acknowledge lower priority requirements?

  • What are the consequences of omitting this requirement? (correct)
  • Is there a deadline for implementing this requirement?
  • How many other requirements depend on this one?
  • Is this requirement critical for the project?

    • What is the primary indicator of a successful prioritization process?

  • Complex pairwise comparison techniques
  • Lengthy discussions about each requirement
  • Having all requirements treated with equal priority
  • Agreement among stakeholders on priorities (correct)

    • Which prioritization technique involves stakeholders making binary decisions about requirements with respect to business objectives?

  • Pairwise comparison
  • In or out method (correct)
  • MoSCoW method
  • Three-level scale ranking

    • What is the main flaw if all requirements end up with similar priority after a prioritization process?

    <p>Failure to prioritize effectively</p> Signup and view all the answers

    Which question can help stakeholders determine the impact of postponing a requirement to a later release?

    <p>What would be the consequence of omitting this requirement?</p> Signup and view all the answers

    What characterizes the 'In or out' method of requirement prioritization?

    <p>Making binary decisions about each requirement</p> Signup and view all the answers

    What is the purpose of assigning a unique priority sequence number to each requirement?

    <p>To facilitate pairwise comparisons between requirements</p> Signup and view all the answers

    Why is grouping requirements into small sets recommended?

    <p>To reduce the complexity of pairwise comparisons</p> Signup and view all the answers

    What distinguishes high-priority requirements from medium-priority requirements?

    <p>The urgency for implementation</p> Signup and view all the answers

    How does the three-level scale (high-medium-low) help in requirement prioritization?

    <p>By categorizing requirements based on importance and urgency</p> Signup and view all the answers

    What makes pairwise comparisons challenging when dealing with a large number of requirements?

    <p>Complexity of the requirements themselves</p> Signup and view all the answers

    Why should stakeholders agree on what each level means in the three-level scale?

    <p>To make the scale useful for assessing priority</p> Signup and view all the answers

    Why is prioritization important in software development?

    <p>To manage competing demands for limited resources and deliver the most critical functionality early</p> Signup and view all the answers

    What purpose does prioritization serve in the software development process?

    <p>To plan construction to provide maximum business value quickly at the lowest cost</p> Signup and view all the answers

    In the context of requirement prioritization, what is the significance of 'MoSCoW'?

    <p>It is a technique to prioritize requirements based on 'Must-haves', 'Should-haves', 'Could-haves', and 'Won't-haves'</p> Signup and view all the answers

    Who is responsible for prioritizing requirements according to the text?

    <p>The business analyst (BA)</p> Signup and view all the answers

    When should prioritization of requirements start?

    <p>At the beginning of the project</p> Signup and view all the answers

    What problem does prioritization aim to solve in software development?

    <p>Deal with competing demands for limited resources</p> Signup and view all the answers

    More Like This

    Use Quizgecko on...
    Browser
    Open
    Browser
    Browser