Requirement Types 1. Why should we care? 2. What are they? 3. How should we use them? RTP IIBA Chapter, April 26 th , 2008 Razvan Radulian, VP of Marketing Founder & President of Why-What-How Consulting, LLC
A condition or capability needed by a stakeholder to solve a problem or achieve an objective .
A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents. Note: “solution…” replaces old “system…” in BABOK 1.6
A documented representation of a condition or capability as in (1) or (2).
“ Aoccdrnig to a rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.”
Would you like to scramble your emails to your manager?