Assignment #3 – Task Analysis
Objectives
Perform and document a formal task analysis
Outcome Supported
CO2 – Develop a computer interface to meet a set of requirements.
Assignment
You will do (a minimum of) 2 task analyses – one of these will be a given system (see the discussion boards for the systems to choose from).
Required Task Analysis – On the discussion boards, you will have additional options for the task analysis. One system you can do a task analysis on is below.
Student Registration Process – The first analysis will be the documentation and analysis of the tasks of registration and payment for a class or classes. The analysis should go from the very beginning of the process (I don’t even know what to take) to the end of the process (I am now enrolled in classes and have paid). This will be a hierarchical task analysis – so you will be responsible for everything under the major heading – Register for Classes and the hierarchical level associated with the tasks. You are free to discuss the levels and sub-tasks on the discussion board.
This will be a hierarchical task analysis with the highest element in the Hierarchy
– Register for Classes
I will even help you with Level 2 of the hierarchy
1 – Register for Classes
1.1 – Select Class
1.2 – Select Sections for Selected Classes
1.3 – Repeat 1.1 to 1.2 until all classes are selected
1.4 – Complete Registration Process
1.5 – Submit Payment for Selected Classes
Why the numbering scheme? Simple – there may be a need to reference and return to a task. For example, in 1.2, in selecting sections for classes, you may find out there is no section available to fit your needs. In that case, you could either (1) seek an override or (2) select a different class. The second selection here will return you back to 1.1 since you will need to select different classes to take. The bottom line is you need to leave the reader with a true understanding of the task to be accomplished.
Secondary Analysis – Your System – In this analysis, you will take the system that you plan on building and document a task analysis of one task that is important or central to that system. Please note that there may be different tasks that can be performed in the Task Analysis, but you only need to do an analysis of one of the subsystems of your design. In your final design documentation, you will need a task analysis of ALL portions of your design.
This should be submitted as a single word or pdf file.
Information
A useful article is at http://www.uxmatters.com/mt/archives/2010/02/hierarchical-task-analysis.php This covers the process well, including the diagramming of the analysis. This example includes a lot of redundant information associated with the analysis in the filling out of forms. I do not typically include all this with the analysis as this is trivial to the overall purpose of the analysis. More important would be special information associated with specific fields on the form where there are special instructions.
HTA is a subset of the entire field of Business Process Modeling ( https://en.wikipedia.org/wiki/Business_process_modeling) and Business Process Mapping (https://en.wikipedia.org/wiki/Business_process_mapping), which contain many different methods for documenting business processes. It is worthwhile to take a look and read through these processes. It is highly likely that in your IT career, you will be involved with the analysis and documentation of business processes. These are also covered in some detail in CEN4801 System Integration.
Estimated Completion Time
This should take 3-4 hours to complete
Supporting Lectures
Multiple lectures are associated with being able to complete a task analysis, though the majority of the information is included under Task Analysis on the lectures page.
Recommendations
At this point, I highly recommend you come up with a method to communicate as a team and manage documentation as a team. Both the Microsoft OneDrive and Google Documents give you the ability to have multiple users access and contribute to the documentation that will become part of this project. Pick one and use it. Remember that you will need to give me access to the documentation so that I can grade it.
Questions and Answers
External Resources
http://www.uxmatters.com/mt/archives/2010/02/hierarchical-task-analysis.php –
https://loft.io/guide/eeole/hierarchical-task-analysis/
https://en.wikipedia.org/wiki/Task_analysis
Grading Criteria
A well-documented task analysis with sub-tasks correctly placed and identified is worth 10 points. Those that need more information to meet requirements will be returned with comments for editing.