Software Requirements Essentials: Core Practices for Successful Business Analysis by Karl Wiegers & Candase Hokanson

Software Requirements Essentials: Core Practices for Successful Business Analysis by Karl Wiegers & Candase Hokanson

Author:Karl Wiegers & Candase Hokanson
Language: eng
Format: epub, mobi, pdf
Publisher: Addison-Wesley
Published: 2023-03-15T00:00:00+00:00


Representation in different forms. There are many ways to depict requirements knowledge beyond natural-language text. Creating more than one representation using different thought processes lets you compare them to find problems. Excellent ways to find requirement problems are to create diagrams or tables to accompany the text and to build prototypes. Such alternative views of the requirements also facilitate clear communication with developers and other team members. See Practice #11, “Create requirements models,” and Practice #12, “Create and evaluate prototypes.”

Prioritization. No team can simultaneously implement everything in its backlog of pending work. Negotiating requirement priorities lets the decision makers sequence the work in a way that is technically sound and delivers the maximum, most timely customer value. See Practice #13, “Prioritize the requirements.”

Assumed and implied requirements. Stakeholders sometimes assume that the solution will include certain functionality without them having to say so explicitly. Those assumptions can lead to disappointments; telepathy and clairvoyance are not effective requirements tools. The presence of certain functionality sometimes implies that other functionality is needed, again without explicitly calling it out. For example, an undo function implies a redo function. Decomposing a high-level requirement into a set of lower-level requirements to fully understand its complexity is one way to discover those implications and manage expectations.

Taking the time to carefully think about your requirements is well worth the investment. The potential rework you avoid by reducing requirements errors before they’re cast into code easily pays for the time you spend on requirements analysis.



Download



Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.