UPCASE
Method for self-assessing the capability of usability process of SEs

You have to check Fully achieved (if the organization performs the practice described in the item), Partially achieved (if the organization performs
the practice described in the item sometimes) or Not achieved (if the organization does not perform the practice described in the item).

Check out the Glossary and Examples of work products in case of doubt.


Usability Process 1. Specify stakeholder and user requirements



Not achieved
Partially achieved
Fully achieved

Description: Identify and describe the purpose of the system, this is, the objective(s) that the user wants to achieve using the system.
Example of work product: Purpose(s) of the system.
Example of techniques: Survey, brainstorming, interview, observation.



Not achieved
Partially achieved
Fully achieved

Description: Identify the stakeholder's requirements regarding the behavior and performance of the system. The requirements cover each aspect of the system related to its use and its interface in a context of use.
Example of work product: System performance and behavior requirements desired by the user.
Example of techniques: Survey, brainstorming, interview, observation.



Not achieved
Partially achieved
Fully achieved

Description: Define an explicitly statement for each usability requirements, regarding its effectiveness, efficiency and user satisfaction based on the context of use analysis. The statements should be measurable objectives.
Example of work product: A list of usability requirements.
Example of techniques: Benchmarking with concurrent systems, synchronic analyzes formal work analyses.


   |   |   |   |    
 
 

SUPPORT

About  |  Privacy Policy  |  Terms of Service