Category: Feature Descriptions

Feature Descriptions are compiled into a document and are based upon client requirements and ideas, internal brain storm sessions, and any research that has been performed. The idea is to gather all of the “expert” opinions on what the software “should do” before development begins, and to hold this document up after that work is done to see if the application works as described afterwards.

Answers the following questions:

What features support the client's business objectives?

What kind of information does the target need and want to know and how can that be presented on the site?

To determine the level of usability for a website, one or more usability experts “walk” through a set of the most typical user tasks supported by the website, one-step-at-a-time. At each step in a task procedure, the evaluator(s) asks themselves the following four questions[1] about their expectations of users’ behaviors:

Will the user try to achieve the right effect?

Will the user notice that the correct action is available?

Will the user associate the correct action with the effect to be achieved?

If the correct action is performed, will the user see that progress is being made toward solution of the task?

The evaluator(s) attempts to come up with a “success story” for each step in the process. If she cannot come up with one, she instead creates a “failure story” and assesses why the user might not accomplish the task based on the interface design. These insights are then used to improve the usability of the website or application.

This is an example of a functional process flow that documents how to implement a Flash banner on the SeaBase website for the Boy Scouts in the Site Core CMS web application. Documentation on website maintenance is key to keeping the websites functional and for future improvements and updates. SeaBase Flash Documentation – Warning Large […]

While at imc2 I worked with the Express Scripts’ team to streamline the online registration and prescription renewal processes, while maintaining core system functionality. The end solution, which had to account for a number of factors including privacy, authorization and accessibility, significantly reduced task times and improved the overall user experience.