Lecture 3: CTT Example: "Online Article Submission System"
Interactive Audio Lesson
Listen to a student-teacher conversation explaining the topic in a relatable way.
Overview of CTT
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Today, we're discussing ConcurTaskTrees, or CTT, a powerful way to analyze complex user tasks. What do you think CTT is?
Is it a method to break down tasks into smaller parts?
Exactly! CTT helps us organize complex tasks into hierarchical structures. Can anyone give me an example of when we might use CTT?
Maybe when designing something like a website where users submit forms?
Good example! Now, letβs look at our case study: submitting an article to an online journal.
Breaking Down the Submission Process
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
We start with the goal: 'Submit Article to Journal'. Can someone tell me the first step?
Access the submission portal!
Yes! This decomposition has two paths: logging in as an existing user or registering a new account. Why do you think these options are important?
They provide flexibility for new users versus returning users.
Exactly! Flexibility is key. Now onto the next stepβwhat does preparing the article involve?
CTT Notation and Processes
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Letβs look at how we represent these tasks using CTT notation. What do hierarchical trees represent in our tasks?
They show the relationship between tasks, right?
Correct! Now, who can explain what a 'User Task' versus an 'Application Task' is?
A User Task is performed by the user, while an Application Task is handled automatically by the system.
Great! Now let's practice how we define these tasks in our CTT model.
Practical Application of CTT
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Using our CTT model, what insights can we draw about user interactions during article submission?
We can identify which tasks are optional and which are mandatory!
Exactly! This helps in designing user-friendly interfaces. What about identifying cognitive load?
We can streamline tasks that require a lot of mental effort!
Yes! And by minimizing cognitive load, we enhance overall user experience.
Final Review and Q&A
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
To wrap up, what are the key components we discussed in the process of submitting an article?
We discussed accessing the portal, preparing files, entering details, reviewing, and confirming submission.
Excellent! And can someone summarize why CTT is beneficial for this task?
It helps us identify all steps, including optional and mandatory tasks, which makes it easier to design.
Perfect summary! Always remember how task modeling impacts interface design.
Introduction & Overview
Read summaries of the section's main ideas at different levels of detail.
Quick Overview
Standard
This section illustrates the ConcurTaskTrees (CTT) methodology with a detailed example of submitting an article to an online journal system. It outlines the various tasks involved, their decompositions, and interactions, showcasing the structured approach of CTT in analyzing user-centered processes.
Detailed
Detailed Summary
The section centers on the application of ConcurTaskTrees (CTT) in modeling a complex user task: submitting an article to an online journal system. It outlines how to break down the overarching goal of submitting an article into multiple components and interactions using CTT notation.
Overall Goal
The primary goal identified is to "Submit Article to Journal". This task is complex and involves various sub-goals, decomposed further into meaningful tasks.
Decomposition of Goal
The decomposition is structured as follows:
1. Access Submission Portal: This involves logging in as an existing user or registering a new account.
2. Prepare Article Files: Users create a new submission entry, upload the article and other necessary files, and may edit previously uploaded files.
3. Enter Submission Details: This includes entering metadata, and optionally adding co-authors and selecting reviewers.
4. Review and Confirm: Users review their submission details before finalizing the process.
5. Receive Submission Confirmation: Finally, the task closes with the user receiving a confirmation message.
CTT provides a precise method to visualize the relationships and sequences of tasks, enhancing understanding of user interactions and system behaviors necessary for effective interface design. The inclusion of concurrency, optionality, and task allocation showcases the flexibility needed in real-world applications, making CTT a robust tool for human-computer interaction design.
Audio Book
Dive deep into the subject with an immersive audiobook experience.
Overall Goal of the Submission Process
Chapter 1 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
Overall Goal:
0. Submit Article to Journal (Abstract Task)
Detailed Explanation
The overall goal for the task model is to submit an article to a journal. This encapsulates all the processes and steps a user must undertake to complete the task. It's the highest-level objective that organizes all the subsequent actions and sub-goals in a hierarchical structure.
Examples & Analogies
Think of the overall goal as a big project at school, like writing a thesis. Your ultimate goal is to complete the thesis, just as in our example the goal is to submit an article.
Decomposition of the Overall Goal
Chapter 2 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
Decomposition of Goal 0:
β Plan 0: 1 >> 2 >> 3 >> 4 >> 5
Detailed Explanation
This plan shows how the overall goal (submitting an article) is broken down into smaller tasks. Each numbered task (1 through 5) represents a critical step within the larger process, with '>>' indicating the sequence in which these tasks must be completed. This systematic breakdown helps in understanding complex processes by focusing on one step at a time.
Examples & Analogies
Imagine assembling a new piece of furniture. The overall goal is to have the furniture ready. Each step, like 'assemble the legs' (task 1), 'attach the tabletop' (task 2), etc., represents a sequential part of that overall task.
Access Submission Portal
Chapter 3 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
- Access Submission Portal (Abstract Task)
β Plan 1: 1.1 [] 1.2
Detailed Explanation
This task focuses on accessing the submission portal. It offers two options: either log in as an existing user or register as a new user (the '[' symbol indicates a choice). This reflects flexibility since users may already have an account or need to create one first to proceed.
Examples & Analogies
Consider trying to enter a club. You can either show your membership card if you are a member (login) or fill out a form to join if you are a new visitor (registration).
Detailed Steps for Accessing the Portal
Chapter 4 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β 1.1 Login as Existing User (Interaction Task)
β Plan 1.1: 1.1.1 >> 1.1.2 >> 1.1.3
β 1.1.1 Enter Username (Interaction Task)
β 1.1.2 Enter Password (Interaction Task)
β 1.1.3 Click Login Button (Interaction Task)
Detailed Explanation
If the user chooses to log in, they go through a series of steps: first, they will enter their username, then their password, and finally, they will click the login button. This sequence clearly outlines how the user engages with the system to access the portal.
Examples & Analogies
This is similar to entering a password to unlock your phone. You input your ID, follow it with your password, and then press 'Enter' to gain access.
Registering a New Account
Chapter 5 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β 1.2 Register New Account (Interaction Task)
β Plan 1.2: 1.2.1 >> 1.2.2 >> 1.2.3
β 1.2.1 Fill Registration Form (Interaction Task)
β 1.2.2 Submit Registration (Interaction Task)
β 1.2.3 Verify Email (User Task - external to system, but part of user's overall goal)
Detailed Explanation
If the user opts to register a new account, they will fill out a registration form, submit it, and then verify their email. This shows a clear linear flow of necessary actions to successfully create an account.
Examples & Analogies
Think about signing up for a mailing list: you enter your details into a form, send it off, and then check your email to confirm you're on the list. This step is crucial to ensure that the user becomes active in the system.
Preparing Article Files
Chapter 6 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
- Prepare Article Files (Abstract Task)
β Plan 2: 2.1 >> 2.2* >> 2.3?
β 2.1 Create New Submission Entry (Interaction Task)
β Plan 2.1: 2.1.1 >> 2.1.2
β 2.1.1 Click "New Submission" (Interaction Task)
β 2.1.2 System Generates Submission ID (Application Task)
Detailed Explanation
This task involves preparing the article files needed for submission. First, the user creates a new submission entry, which involves clicking a button and the system generating a unique ID for that submission, facilitating tracking and management.
Examples & Analogies
Itβs like applying for a loan: you fill out a form to create a new application, and then the bank gives you a reference number to track your loan status.
Uploading Article Files
Chapter 7 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β 2.2 Upload File (Interaction Task - Iterative, for main article, figures, data, etc.)
β Plan 2.2: 2.2.1 >> 2.2.2 >> 2.2.3 >> 2.2.4
β 2.2.1 Select File from Local System (Interaction Task)
β 2.2.2 Initiate Upload (Interaction Task)
β 2.2.3 Display Upload Progress (Application Task)
β 2.2.4 Confirm Upload Success (Application Task)
Detailed Explanation
This step involves uploading the actual article and any associated files (like images). The plan outlines a sequence where the user selects a file, initiates the upload, and then the system provides feedback on progress and confirms if the upload was successful.
Examples & Analogies
Picture sending an email: you choose a file to attach, press 'send', and then see a progress bar showing the attachment is uploading. If everything goes well, you receive confirmation that the email was sent successfully.
Optional Step: Edit Uploaded Files
Chapter 8 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β 2.3 Edit Uploaded Files? (Interaction Task - Optional, if user realizes a mistake)
β Plan 2.3: 2.3.1 >> 2.3.2
β 2.3.1 Delete File (Interaction Task)
β 2.3.2 Re-upload File (Interaction Task)
Detailed Explanation
This optional step allows the user to edit any uploaded files if they notice an error. If the user chooses to edit, they can delete the incorrect file and upload a corrected version.
Examples & Analogies
Itβs like realizing you sent a wrong photo in a message, where you can delete that photo from your chat and then send the right one instead.
Entering Submission Details
Chapter 9 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
- Enter Submission Details (Abstract Task)
β Plan 3: (3.1 >> 3.2 >> 3.3) | | (3.4 | | | 3.5?)
Detailed Explanation
During this phase, users enter the necessary details about their submission. The plan indicates that entering the article title, abstract, and other information must occur sequentially, while adding co-authors and selecting reviewers can happen in parallel. This flexibility helps streamline user input and enhances the user interface.
Examples & Analogies
Think of setting up a new social media profileβfirst, you fill in your name and bio (sequential steps), but you can also add friends or choose privacy settings while youβre updating your profile details at the same time.
Reviewing and Confirming Submission
Chapter 10 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
- Review and Confirm (Abstract Task)
β Plan 4: 4.1 >> 4.2 >> 4.3 |[> 4.4
Detailed Explanation
In this step, users review their submission summary and confirm it by accepting the terms and conditions. Once they click 'Submit', they cannot go back and editβindicated by the disabling operator. This emphasizes the importance of making sure everything is correct before finalizing the submission.
Examples & Analogies
Before filing taxes, you review your forms and confirm you have completed everything correctly. Once you hit 'Submit', you canβt change any details, making sure you double-check beforehand.
Receiving Submission Confirmation
Chapter 11 of 11
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
- Receive Submission Confirmation (Abstract Task)
β Plan 5: 5.1 | | 5.2 | | 5.3?
Detailed Explanation
The final step involves receiving confirmation of the submission, which may include an on-screen message and an email confirmation. Thereβs also an optional step for printing a receipt. This ensures the user has tangible evidence of their submission.
Examples & Analogies
When you place an online order, you get an email confirmation and might see a 'Thank you for your order' message on the screenβthis reassures you that your order has gone through successfully.
Key Concepts
-
Hierarchy in CTT: Represents relationships between tasks.
-
Concurrency in Tasks: Describes tasks that can occur simultaneously.
-
User vs. Application Tasks: Differentiates tasks based on user involvement.
Examples & Applications
Submitting an article to a journal where tasks include logging in, uploading paper, and receiving confirmation.
An online shopping process that requires adding items to a cart and then checking out.
Memory Aids
Interactive tools to help you remember key concepts
Rhymes
To submit your work with ease, follow these steps like a breeze.
Stories
Imagine a scholar who visits a portal, logs in with their details, uploads their manuscript, and receives a confirmation β a journey through the CTT!
Memory Tools
A Simple Way to Remember: A β Access, P β Prepare, D β Details, R β Review, C β Confirm.
Acronyms
A PDRC
Access
Prepare
Details
Review
Confirm.
Flash Cards
Glossary
- ConcurTaskTrees (CTT)
A formal task modeling notation that represents complex, concurrent user tasks systematically.
- User Task
Tasks performed by the user, which require their direct interaction.
- Application Task
Tasks executed automatically by the system without user intervention.
- Hierarchical Structure
A way to organize tasks into parent-child relationships to clarify dependencies.
Reference links
Supplementary resources to enhance your learning experience.