[[Software Product Management Specialization]] > [[Course 3. Client Needs and Software Requirements]] ## Week 2. User Interaction https://www.coursera.org/learn/client-needs-and-software-requirements/home/week/2 A major duty of a software product manager is eliciting and expressing requirements from your client. This module will walk you through the basics of client interactions and requirements elicitation and expression. You will learn how to create the best product for your end users, how to conduct productive client meetings, and various ways of expressing requirements. These techniques will provide you with the tools you will need to confidently interact with your client as well as satisfy them with the “right product”. ### User Considerations - END USER - Who is the end user? If the end user don't like it (easier to use), they will not use it. - StakeHolder - Who is affected by the project. Anyone including end user - User Interface #### Who are we building the product for? The Stakeholders - Primary users - People who use it all the time. End users (patients, case managers) - Secondary users - e.g Waiter - Tertiary users - Who make decision of the product (boss). Hospital Human Computer Interaction - is the discipline that focus on how people interact with software. User friendly, intuitive to use. Developer don't think like lay person. ==Develop for the beginner and expert.== #### Limitations - Good software accommodate their users limitation - Perceptual / sensory limitations - 5 Senses. e.g colourblindness - Physical limitations - E.g children not the same as adults. Left and right handedness. (placement of the button) - Cognitive Limitations - Memory limitations. George A Miller, psychologist: Can only remember 7 items. Working memory. - Cultural Limitations - Cultural differences, e.g the use of color means different things. - Symbols, Language - Marking of X for choices. in Japan, a X means rejections. ### Cultural differences ### Involving clients - Taking the idea from clients from their head, interact to draw out , discuss a solutions together. - Revisit requirements frequently - Number the requirements with unique numbers. - Create a glossary for the product, so everyone refer to the term. Increase clarity. - Sources to elicit requirements - Interview end users - Conduct feasibility studies - Watch end users using the product - Consult user manuals for similar products Turn the requirements into prioritised product backlog, and create a prototype. It should be a conversation, to elicit vision/goals of the product. Requirement should not merely be based on what client said. (elicit it). Suggest new ideas and solutions. Ask good questions. Open questions. ==Ask "Why?" Ask WHY... why are we doing this?== Simon Sinek, TED Talk [[202011252022 Good questions lead to good answers]] Client decide what is more important to them, not development team. [[Good questions to ask clients to elicit requirements]] ### Use cases - Ivar Jacobson developed the concept of Use Case in 1986. - ![[Screenshot 2022-05-23 at 9.08.47 PM.png]] - Name: - Actors: Roles - Goals - Triggers: Push of a button - Pre-Condition: - Post-Condition: - Basic Flow: Sunny day scenarios - Alternate Flows - Exceptions: When will it not work - Qualities : Should be technology independent. **Use Case Diagram** - High level visual representation of all the tasks supported by the product. ![[Screenshot 2022-05-23 at 9.12.44 PM.png]] - Each feature contain a Use Case. e.g View Bill. ![[Screenshot 2022-05-23 at 9.16.19 PM.png]] Exception : No order placed. ### Wireframes assignment - Or a Mockup. - Keep it simple. - Basic functions and end user tasks. - where to put buttons etc. - Blueprint, -- not 3D rendering. ==Don't prematurely decide on a solution== ### StoryBoard - Sequential order. - High level user experience. Of use cases. ![[Screenshot 2022-05-23 at 9.49.34 PM.png]] - When and how the user use the product - Always imagine how users use the product. - Each storyboard for each features - This keep product vision alive, ensure every production member on the same page, use in marketing and general purposes. Like demo. **Another kind of storyboard. Visual requirements before development** Each state of the product depict ![[Screenshot 2022-05-23 at 9.54.00 PM.png]] Also can be use to create training manual. --- # Module 2: Supplemental Resources ## Listed below are selected resources related to the topics presented in this module: ### User Considerations _This is a list of resources about Human-Computer Interaction. It can point you to various readings about different aspects of HCI._ "HCI Bibliography : Human-Computer Interaction Resources." 17 Nov. 2015 <[http://hcibib.org/](http://hcibib.org/)> _An article about how web design user interfaces are changed in different cultures._ "Cross cultural considerations for user interface design." 2014. 17 Nov. 2015 <[http://www.humanfactors.com/newsletters/cross-cultural-considerations-for-user-interface-design.asp](http://www.humanfactors.com/newsletters/cross-cultural-considerations-for-user-interface-design.asp)> _A 20 minute video about how the purpose, or the question “why” is important when designing and marketing products. Very interesting, a must-watch!_ "TED Talks - Simon Sinek - How great leaders inspire action ..." 2013. 17 Nov. 2015 <[https://www.youtube.com/watch?v=a6kbcERdmCw](https://www.youtube.com/watch?v=a6kbcERdmCw)> _The webpage of Simon Sinek, and the Power of Why. This corresponds to the above video, if you wanted to read more._ "Start With Why." 2011. 17 Nov. 2015 <[https://www.startwithwhy.com/](https://www.startwithwhy.com/)> ### Use Cases _A thorough explanation of Use Cases. It includes examples and tips for creating Use Cases and Use Case Diagrams._ "Use Case Examples -- Effective Samples and Tips." 2006. 19 Nov. 2015 <[http://www.gatherspace.com/static/use_case_example.html](http://www.gatherspace.com/static/use_case_example.html)> _A further explanation of Use Cases. Also shows some good links to additional resources about Use Cases._ "What is use case? - SearchSoftwareQuality - TechTarget." 2010. 19 Nov. 2015 <[http://searchsoftwarequality.techtarget.com/definition/use-case](http://searchsoftwarequality.techtarget.com/definition/use-case)> _Your typical Wikipedia explanation. Includes a good example._ "Use case - Wikipedia, the free encyclopedia." 2011. 19 Nov. 2015 <[https://en.wikipedia.org/wiki/Use_case](https://en.wikipedia.org/wiki/Use_case)> ### Wireframes _A great explanation about how to wireframe. Gives various examples._ "A Beginner's Guide to Wireframing - Web Design - Tuts+." 2014. 19 Nov. 2015 <http://webdesign.tutsplus.com/articles/a-beginners-guide-to-wireframing--webdesign-7399> **_Examples of Wireframes_** _A resource that points to various examples and wireframing tools._ "I wireframes - The ultimate source of inspiration ... - Tumblr." 2009. 19 Nov. 2015 <http://wireframes.tumblr.com/> **_Wireframe Tools_** _A tool for creating wireframes for websites or applications._ "Balsamiq. Rapid, effective and fun wireframing software ..." 2011. 19 Nov. 2015 <[https://balsamiq.com/](https://balsamiq.com/)> _An excellent mockup tool. Can be used for wireframes, charts, blueprints, diagrams, etc. The program does cost money, but has a free trial._ "OmniGraffle - The Omni Group." 2012. 19 Nov. 2015 <[https://www.omnigroup.com/omnigraffle](https://www.omnigroup.com/omnigraffle)> _A really cool web-tool that can turn any website into a wireframed version of the site._ "Wirify – The web as wireframes." 2011. 19 Nov. 2015 <[http://www.wirify.com/](http://www.wirify.com/)> ---