Well-formed requirements share a set of quality characteristics, including being correct, complete, consistent, unambiguous, testable, traceable, and modifiable. An unambiguous requirement has only one possible interpretation, so every stakeholder, developer, and tester understands it identically. The word "quickly" is subjective: a business sponsor might expect a two-second response, an analyst might accept ten seconds, and an engineer might consider a minute acceptable for a large query. Because the statement can be read in several ways, it fails the unambiguous standard most directly. The usual remedy is to replace the vague term with a measurable criterion, for example that the dashboard must display within three seconds for ninety-five percent of requests under normal load. Doing so also makes the requirement testable, a related characteristic that the vague wording violates as a secondary consequence. Traceability, option B, concerns whether a requirement can be linked back to its business need and forward to design, development, and test artifacts; the wording of the statement does not affect it. Modifiability, option C, concerns whether the requirement can be changed without disrupting others and likewise is unrelated to vagueness. Precise requirements reduce rework and disputes during delivery of data science projects. Reference: Data Science Fundamentals Study Guide – Data Science Process: Defining Data Requirements and Quality Characteristics.
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit