August 2018
Beginner
594 pages
22h 33m
English
Content preview from Software Architect's Handbook
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Software must be useful, and not just usable
Keep in mind that, regardless of how usable the software is, it must have utility. For a system to have utility, it must provide the functionality that its users need. Being usable is great, but in order to be useful, it must also have utility. Users must be able to accomplish their goals and the software must serve its purpose.
Is the software system meeting the needs of the users? Is it useful to them? Even if the software system provides a nice visual experience, without usefulness it will not be a good user experience.