Task Analysis
- Team Strategy Case Analysismatching Dell: Ibm - Case Analysis MATCHING DELL: IBM Strategic Management Group IBM: Content 1. Introduction...
- Comparison Of Menu Techniques - Design: (See Pic Experiment) 4 Section 3: Hypotheses 5 Section 4: Results and analysis 6...
- Human Resource - how it connects with strategic goals, and how organizational resources can best be used....
- Cook Chill Coursework - in calories and this must be emphasised in the product name and the product's packaging....
- Instruction Design - objectives for the total program and each element ? analysis of outcomes or objectives...
Submitted by lucy7733 on 06/30/2008 05:21 PM
- Category: Technology
- Words: 333
- Pages: 2
- Views: 28
- Popularity Rank: 2293
Task Analysis
What is Task Analysis?
Task Analysis is the process of breaking down a task and analyzing it with respect to human psychological physical requirements.
Task analysis clarifies and organizes knowledge about work, whether computerized or not. These techniques can be used to accurately design systems that do what users must do to accomplish work goals.
What Does Task Analysis Enable me to Do?
Task Level
1. Elicit descriptions of what people do
Process Level
1. Specify functional requirements
2. Devise a new process
3. Automate the process
Human-System Interaction Level
1. Measure system complexity and learnability
2. Evaluate systems against usability goals
3. Evaluate system safety
4. Predict human-system performance
5. Predict difficulties in system use
6. Develop training tools
Object Oriented Task Analysis (OOTA) (shorter, if not sweeter!)
Method
* OOTA describes a task in terms of all of the tools or objects necessary to
successfully meet the task goal.
Recommended Tasks
* This method tends to be product oriented
Advantages
* It is a good tool for interface designers, as it is generally better to first identify user interface objects and then determine the underlying processes.
Disadvantages
Software Systems Task Analysis (SSTA)
Method
* SSTA describes a task in terms of users' needs relating to data.
* SSTA supports the development of operational sequence diagrams, which are predominantly used in software design.
*
* Decision --> Operation ----> Inspection ------> Storage...
You must Login to view the entire paper.
If you are not a member yet, Sign Up for free!
