# [[Course 3. Client Needs and Software Requirements]] [[Course 3. Client Needs and Software Requirements]] [[Course 3. Week 2. User Interaction.]] [[Week 3. Writing Requirements]] --- ## Week 4. Quality Requirements ### Criteria for User Stories - Requirements need to be **Correct**. - How to make user stories to be CLEAR (Single Interpretation) - Everyone should have one interpretation **- Technical and review exercise** - Reviewing requirements for ambiguity - Supplement requirements with wireframe - **Consistent** user stories - User Stories that don't conflict - **Feasible** User stories - Can be implemented with technologies within scope and cost, schedule. - **Traceable** - Each requirements have traceable source codes, and testable. Everything should be related. - Unique identifier ![[_e968493abbd564d219d5fe992130681f_AmbiguousRequirementsStudyGuide-Color.pdf]] ### Ambiguous Requirements - Reduce confusion, and miscommunication, and work done wrong - Words that causes ambiguity - Have conversations with stakeholders to reduce ambiguity. Clarify. - Do not want a user story to be interpreted in different ways. - Indirect Words - e.g Should and Could - What circumstances will outcome happen? "i may win.." what circumstances signify win? - words like "processed".. what does it mean? It's a Vague word, because it didn't contain any information on what specific actions will happen. - Usually actions words. - Completion Words. "and so on..", "so forth".. "also". It's not clear what else should be included. - Persuasion words - Ascertaining an opinion, is it factual? - Qualifiers words - "all", "every", "only." etc (refer to the chart) - Comparatives - Comparing things. Be specific what attribute are we comparing. - Quantities - Instead of "some", specific minimum number, or specific amount. - In Summary, specific exactly what you are referring. - Positional words - "appear before", does it mean immediately before, or as long as it's before? - Temporal - related to time and event "when" "for" .. --- # Module 4: Supplemental Resources ## Listed below are selected resources related to the topics presented in this module. ### Criteria for User Stories _Explains the INVEST and SMART acronyms for writing good user stories._ "INVEST in Good Stories, and SMART Tasks | XP123." 2010. 19 Nov. 2015 <[http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/](http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/)> ### Ambiguous Requirements _A fun and informative article that compares the perfect requirement to a unicorn (you wish it existed, but it doesn’t). It goes through some techniques for removing ambiguities from your requirements._ "7 Steps to Avoid the Ambiguous Requirement and Maybe ... - Netcentric." 2015. 12 Jul. 2016 <[https://www.netcentric.biz/blog/2015/05/avoid-ambiguous-requirement.html](https://www.netcentric.biz/blog/2015/05/avoid-ambiguous-requirement.html)> _Karl Wiegers, who is a titan when it comes to writing requirements, goes through 10 requirement traps that you should try to avoid, and Ambiguous Requirements is one of them._ "Karl Wiegers Describes 10 Requirements Traps to ... - Process Impact." 2009. 12 Jul. 2016 <[http://processimpact.com/articles/reqtraps.html](http://processimpact.com/articles/reqtraps.html)> _A very detailed paper on how to avoid ambiguity in requirements specification. Not a necessary read unless you are interested in exploring the subject in more detail._ Tjong, SF. "Avoiding Ambiguity in Requirements Specifications - the David R ..." 2008. <[https://cs.uwaterloo.ca/~dberry/FTP_SITE/students.theses/TjongThesis.pdf](https://cs.uwaterloo.ca/~dberry/FTP_SITE/students.theses/TjongThesis.pdf)>