What This Document Is
This document is a chapter excerpt focused on requirement prioritization within the context of systems and software development. It explores the challenges of balancing competing demands when resources are limited, and introduces various techniques for determining which requirements should take precedence. It’s part of the course materials for CPSC 541 at California State University, Fullerton.
Why This Document Matters
This material is essential for students and professionals involved in software engineering, systems analysis, and project management. It’s particularly relevant when working on projects with fixed timelines and budgets, where making informed decisions about scope is critical. Understanding prioritization methods helps ensure that development efforts focus on delivering the most valuable functionality first.
Common Limitations or Challenges
This excerpt provides an overview of prioritization concepts and techniques. It does not offer a comprehensive guide to implementation or detailed case studies. Users will still need to apply these concepts to specific project contexts and navigate the complexities of stakeholder negotiation. The document also doesn’t cover tools for managing requirements beyond the techniques described.
What This Document Provides
The full document details the importance of prioritizing requirements, and presents several prioritization techniques including: “In or Out”, pairwise comparison and rank ordering, a three-level scale (High, Medium, Low), and the MoSCoW method (Must, Should, Could, Won’t). It also introduces Quality Function Deployment (QFD) as a more analytical approach, and provides a formula for calculating priority based on value, cost, and risk. The excerpt also highlights the difficulties in achieving consensus among stakeholders with differing expectations.