make software for users, not stakeholders
Post on 27-Jan-2015
108 Views
Preview:
DESCRIPTION
TRANSCRIPT
Make Software for Users,not Stakeholders
Rostyslav BelmehaFront-End Developer @SoftServe
1. Converting Ideas into Apps2. Design
a) Requirements Specificationb) Solution
AGENDA
Converting Ideas into Apps
Converting Ideas into Apps
Requirements
Design
Implementation
Verification
Maintenance
DesignRequirements Specification
Design. Requirements Specification
Process:
• business analysts and designers create a clear picture of the product• decisions are based on previous experience, stereotypes of users'
needs, personal preferences• the emphasis is on graphic design element, rather than interaction
and usability
Problems:
• random stereotypes about the user;• personal preferences;• wishes of the end users who do not know about the rest of the opportunities
that new software will offer;• decision belongs to someone whose status is higher.
Design. Requirements Specification
Aspects, which are left out of focus:
• The goals of the user;• Convenience and efficiency;• Intuitiveness and ease of use.
Design. Requirements Specification
DesignSolution
Design. Solution
Creating personas
• sex• age• education• family situation• level of computer education• etc
Design. Solution
Choosing the key persona
• personal experience of the UX specialist• communicate with potential users
Design. Solution
Test prototype with real users
• UX specialist define a set of specific tasks• test sessions a few times• representing the result in numbers
Methods which should be applied:
• Understanding portrait of typical users• Creating personas and defining tasks for each workflow• Iterative approach to interface design• End user testing
Design. Solution
Conclusion
Questions?
top related