Collaborative Work Systems Inc.

Engineering Human Centered Collaborative Systems for Complex Work Environments

Collaborative Work Systems Inc.

Engineering Human Centered Collaborative Systems for Complex Work Environments

Socio-Technical Work System Evaluation

CWS recommends multiple evaluations, starting early in the development life-cycle, and combining different methods. This is because a socio-technical work system at a particular level of maturity affords particular approaches and because there are tradeoffs between methods. What would be best may not always be practical due to resources or other constraints, which makes understanding the requirements and benefits of each approach in relation to the needs of the project all the more important.

Name

Purpose

Requirements

Results

Usability Inspection

Identify user interface elements that don't meet standard guidelines and suggest possible solutions.

User interface documentation: display designs, intended users, and scenarios / use cases.

A summary of effective design approaches found and a detailed list of issues, severity ratings, and potential solutions.

Usability Testing

Study performance by intended user type(s), given realistic scenarios, in a controlled environment following the principles of experimental design.

User interface documentation, executable software or storyboards, and access to users.

Quantative data for targeted measures of performance, and potential solutions for issues identified.

Pluralistic Evaluation

Identify design issues by walking through use scenarios with end users.

User interface documentation, storyboards, and access to users.

A list of issues identified, severity ratings, and potential solutions.

Situation Awareness Assessment

Identify users ability to perceive, understand, and predict what will happen next in user interfaces where maintaining user situation awareness is a primary goal.

User interface documentation, executable software or storyboards, and access to users.

Important data not perceived, information not well understood, and events not predicted accurately.

Collaboration Assessment

Identify who provided or consumed information from whom, and what tools they used to collaborate.

Access to users for questionnaire completion, or access to relevant logs / communications.

A list of leading information providers, consumers, and tools used. Line graphs to show change over time. Network graphs to summarize collaboration, reveals groupings, and connections between groups.

Risk Assessment

Identify paths to negative effects in a user interface and assess the level of risk for each.

User interface documentation, executable software or storyboards, and access to users.

List of risks identified, level of risk assessment (severity x frequency) for each, classification of problem type, and potential solutions.


Name: Usability Inspection
Purpose: Identify user interface elements that don't meet standard guidelines and suggest possible solutions.
Requirements: User interface documentation: display designs, intended users, and scenarios / use cases.
Results: A summary of effective design approaches found and a detailed list of issues, severity ratings, and potential solutions.

Name: Usability Testing
Purpose: Study performance by intended user type(s), given realistic scenarios, in a controlled environment following the principles of experimental design.
Requirements: User interface documentation, executable software or storyboards, and access to users.
Results: Quantative data for targeted measures of performance, and potential solutions for issues identified.

Name: Pluralistic Evaluation
Purpose: Identify design issues by walking through use scenarios with end users.
Requirements: User interface documentation, storyboards, and access to users
Results: A list of issues identified, severity ratings, and potential solutions.

Name: Situation Awareness Assessment
Purpose: Identify users ability to perceive, understand, and predict what will happen next in user interfaces where maintaining user situation awareness is a primary goal.
Requirements: User interface documentation, executable software or storyboards, and access to users.
Results: Important data not perceived, information not well understood, and events not predicted accurately.

Name: Collaboration Assessment
Purpose: Identify who provided or consumed information from whom, and what tools they used to collaborate.
Requirements: Access to users for questionnaire completion, or access to relevant logs / communications.
Results: A list of leading information providers, consumers, and tools used. Line graphs to show change over time. Network graphs to summarize collaboration, reveals groupings, and connections between groups.

Name: Risk Assessment
Purpose: Identify paths to negative effects in a user interface and assess the level of risk for each.
Requirements: User interface documentation, executable software or storyboards, and access to users.
Results: List of risks identified, level of risk assessment (severity x frequency) for each, classification of problem type, and potential solutions.

< Services Overview Education & Training >



Facebook Linkedin Copyright (c) 2006-2022, Collaborative Work Systems (CWS), Inc