User requirements document

Uses your system voice; voice and rate in settings.

Q7901856Snapshot

≈ 3 min read

Names in other languages

  • mkДокумент за кориснички барања
  • EnglishUser requirements document
  • 中文使用者需求文件
  • 简体中文使用者需求文件
  • 繁體中文使用者需求檔案

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

The user requirement(s) document (URD) or user requirement(s) specification (URS) is a document usually used in software engineering that specifies what the user expects the software to be able to do. Once the required information is completely gathered it is documented in a URD, which is meant to spell out exactly what the software must do and becomes part of the contractual agreement. A customer cannot demand features not in the URD, while the developer cannot claim the product is ready if it does not meet an item of the URD. The URD can be used as a guide for planning cost, timetables, milestones, testing, etc. The explicit nature of the URD allows customers to show it to various stakeholders to make sure all necessary features are described. Formulating a URD requires negotiation to determine what is technically and economically feasible. Preparing a URD is one of those skills that lies between a science and an art, requiring both software technical skills and interpersonal skills.

The user requirement(s) document (URD) or user requirement(s) specification (URS) is a document usually used in software engineering that specifies what the user expects the software to be able to do. Once the required information is completely gathered it is documented in a URD, which is meant to spell out exactly what the software must do and becomes part of the contractual agreement. A customer cannot demand features not in the URD, while the developer cannot claim the product is ready if it does not meet an item of the URD. The URD can be used as a guide for planning cost, timetables, milestones, testing, etc. The explicit nature of the URD allows customers to show it to various stakeholders to make sure all necessary features are described. Formulating a URD requires negotiation to determine what is technically and economically feasible. Preparing a URD is one of those skills that lies between a science and an art, requiring both software technical skills and interpersonal skills.

See also

Product requirements document Market requirements document Requirements management Use case

References

External links

ISO 25065 "User requirements specification"

Text derived from https://en.wikipedia.org/w/index.php?oldid=1320136970 under CC BY-SA 4.0; modifications have been made.

Provenance

snapshot user-requirements-document-888919-9478cd4e04e9c776 · hash 9478cd4e04e9c77621eb6840f9c03a55e58cbc340dae5df3a6a87c4873590d44 · captured 1762123145.0 · version history

Cite this page as: encyclopegia.org, “User requirements document”, snapshot user-requirements-document-888919-9478cd4e04e9c776. https://encyclopegia.org/a/user-requirements-document

Sources cited in this revision

No external citation was extracted for this revision. That is a statement about the source, not a claim that none exists.