Mikko Majander, Simone Scarduzio, Wedha Effendy
Users
- Students
- Teachers and lecturers
- Management
- Personnel
- library
- study affairs office
- international affairs office
- IT-services
- Security
Teacher use cases
- Manage workspace of a course
- Modify user permissions (example: allow users to make announcements)
- Add documents
- Make assignments
Student use cases
TYPE OF USERS
#1 Class participant
Type of users
Degree students
Exchange students
Users whose native language is english *
Users whose native language is finnish *
Users whose native language is not finnish or english *
* Tuubi is localized in finnish and english. It may contain vocabulary that exists in the same context only in Tuubi.
A simple persona (should this be a stereotype?) / slide 26
Name: Spock
A role or job title: Has been studying information technology in Metropolia for two years.
Quotes in the personas language: (if I'd know what this really means)
Relevant demographics: (Demographic about one person?) Spock is either male or female. There is approximately n-thousand students of information technology in Metropolia.
Descriptions that reveals goals, motivations, pain points:
Sharing information can be done different ways and if teachers doesn't have a common tool for that, there might be many different kind of ways they keep students informed and share course material an assignments. This can be a problem for student: without a common tool information you need is stored in different places and you need to remember where (bookmarks).
Communication in a big organization or community is challenging. To make information and activities transparent you need to be able to inform everyone about everything. But not everyone want's to know about everything. Therefore Tuubi can help, because user can choose those notifications, messages and workspaces he/she is interested in.
Descriptions that describe primary activities this user type will engage in, where and in which social relations
Work, meet people in gatherings and around activies.
Feature opportunities and design imperatives / slide 29
- ease of learning
- retention
- efficiency
- reliability
- interactivity
- user satisfaction
- user convenience
- necessity for proficiency
- importance of accuracy
Student use cases
Class participant:
- General
...
- repsonsibilities and activities
- Sees the courses
...
- Sees the courses Receive messages from the teacher
- Can download documents (slides, tasks, materials) and open external links
- Can submit an assignment
- Receive feedback
- See events in the calendar
- Browse the members of group (like classmates)
- Have a discussion on the discussion boardFor Student Read Student guide
...
Number of users
...
- the whole students Students of Metropolia (approximately nearly 14 000 of which maybe 8 000 present at the time)
...
Computer skills
...
- Moderate, fairly good
...
Domain expertise
...
Tool ecology / Software ecosystem
...
- Very broad. External calendar, Word, Office-programs, Organizers, Statistical analysis software, Graphip design software, etc. with Tuubi. You can upload different kind/any kind of file formats to Tuubi. Tool ecology of Tuubi is very broad.
...
Collaborators
...
- Teachers
...
Pain Points
...
- Simpligying commnicationcommunication, a bridge between students and teacher.
...
Usage contexts
...
- People are using Tuubi as communication tool (receiving messages and notifications from teachers and Metropolia generally) and as a information space for course-spesicfic information. Information can be shared via Tuubi.
- On computers of students and staff, at home or at school.
...
Frequency of use
...
- Daily
Tool ecology
Tool ecology of Tuubi is very broad.
...
Helpful notes for the assignment:
Tool ecology = group of tools. Example do you use external calendar, pen and paper, Word etc. with Tuubi.
MB: Good start. Now just finish the task one with the tool ecology and the descripyion of the stereotypical user of the segment of your focus, specify the most important usability criteria for the user segment you focus on and move to task 2, where you use the usability criteria to choose your testing method, place, time, tasks etc and then do the pilot test. Please finish the task 1 and 2 this week (i.e., week 47) we do the pilot testing in the week 48.