Please enable JavaScript.
Coggle requires JavaScript to display documents.
Bridging the Gap between User Needs and User Requirements - Coggle Diagram
Bridging the Gap between User Needs and User Requirements
Conclusion
Table is a useful way to make user understand / useful for desginers for use case
Table helps designers translate user requirement / Write user case from user POV
User cases diagram assist desginer to gain coherant view of product
user needs garhering are a must to develop usable product
Difficulty Representing User Requirement
Document describe technical details and implementation
Easiest way of describing user requirement for technical designers
Fundamental Problem = How to introduce user POV and needs for designer
Should be understandable for user
Enables them to provide feedback
Unable to gather feedback by traditional method
Prototypes and mock-ups
user face problem getting an overview of system functionality from paper
Designer have difficulties remembering / conveying user requirement in prototypes
Require more things to define the functionality and communicate it to user
Use case Driven Approach
Popular approach
Software engineering provide help
Good way of capturing user's need and requirement
Widely accepted among designers
Resembling scenarios of uses
Use case as object oriented methodology
Possible sequences of interaction between system and actor
Real life practice is different
use case was written without knowledge of user need
Documentations are not read by users
Use case written from technical POV, but not from user POV
Example of case studies
Develop user requirement elicitation method
Gather user / customer needs by direct contact
Use user POV to develop usable product
Task given by company example
Vaisala ( new Version )
Identifying stakeholders
Gathering user needs
Describing user need for use cases
Kone ( new Version )
Identifying stakeholders
Gathering user needs
Describing user need for use cases
Documenting use cases
Tekla ( new Product )
Identifying stakeholders
Gathering user needs
Documenting use cases
Gathering user feedback
Concluded with stakeholder identifitcation was necessary in order to consider finding whom to gather user needs
Describing user needs for use cases
Kone Case
User studies were reported in written document
Photograph / video were used to represent user needs
Designer finds document and photograph are useful
But study team conclude its the most challenging part
Other company
Not easy for technically oriented designer to user user needs in product developement
Able to write user study report
Unable to use the doc in user requirement definition
Usage of box-diagram to describe task sequences
Convey Users POV
Linked task sequences steps to users problem and possibilities
Designer got insight better
Documenting Use cases
User need table and list based- required documents
User case of descriptions was userful
Help designer to gain a higher-level view of product requirement / identifying missing details