Page History

 1

----
Here we comment WinhaWille student portal.

Users of Winha Wille are students.

h3.   Segmentation


h4.


h4. 1.Students


h4.

*   All metropolia students in       different campuses.

* International  and       National Finnish students
* Different campus students such       as : Leppävaara, Myyrmäki, Tikkurila, Bulevardi  etc...
* Different Departement       students  such as : Media Engineering, IT Technology,Art Design,       Music,Nurse,  Social Services, Environment etc..
* Different Groups:       DAP07S,CAP06S,TI08S1E  etc...

h3.


h3. 2.Teachers


h3. 3.Other Support staff 

# h3. Activities:

* getting student data
* changing address
* check the confirmed participation
* check the completed courses
* check the study guide line
* checking the courses offered for the department
* enrolling for the courses that are offered
* changing the data language
* checking the enrollment status(season)


h4. Focal roles for the winha wille website


International student, Media Engineering or IT students,

For international students International student, Media Engineering or IT students there role is to change their data change addresses ,to enroll for the course ,to check the course that they complete ,to check the credit that they accomplish and to know how many is left, it's mandatory to sign there user name and password.

h4. Media Engineering students

1. # of users that occupy this user type: All students participating in programme
\\
2. General responsibilities or activities: search cources, control performance, enrol to cources, check participated and completed courses
\\
3. Computer skills: general computer skills
4. Domain expertise: media engineering
5. Goals: this tool is compulsory to be used. Student can't continue studies without registering as present for period. Also student cannot get grades for course if not enrolled.
6. Pain Points: Main purpose is remote control of studying proces
7. Usage Contexts: Winha can be accessed  from "lobby" area ,"Liberary", and  from  home through internet.
8. Software Ecosystem: Winha is accessible via all major browsers.To communicate with other students or teachers, the students use phones and emails. And to get the course guide the students use study guide which is located in tuubi.( It is coupled {color:#800000}MB: with what other tools, word? Material booklet of the study guide, mobile for text messaging or phoning help(discussion) with friends what courses they are taking, what grade they got, etc??{color})

{color:#008000}Winha is accesed usually from tuubi portal, so in some way it is inside tool of tuubi.{color}
9. Collaborators: teachers, other students, IT support
10.Frequency of Use: around 1-3 times a week

h3. Personal Activities

Name: John Doe

A role or Job Title: Student

     "How can i register for a course?"


John Doe is a third year media engineering student.He lives in Lintuvaara. Over his study years he has used winha to put his personal data, to check all the courses that are offered through out the 4 years, to check the courses offered for the specific period , to check the compulsory and optional courses, to check the grades that he has got from different courses.In winha, which is a frustrating thing for him is that when browsing through it ,it is difficult to find what he wants. For example when he wants to enroll , he has to click ISP in the winhaa page  and then enrollement.But since the term ISP is not self discriptive, he has to  _ask from students how to enroll_ {color:#800000}_(MB so he does use e.g., mobile when using Winha...)._{color}Besides when he clicks the help tab , user help file appears which is written in finnish.

{color:#800000}MB: Please finnish this task ASAP and move to task 2. The Task 1. is missing still the usability criteria for the students users of Winha. These you need for the task2. Finnish both task during this week 47 since next week 48 we should do the pilot testing of your test plan (task2).{color}

h3. Usability Criteria

1. Learnability

     - The system should be easy to learn, so that the student can use it as rapidly as possible.


2. Efficency

    - The system should be efficent to achieve high level of productivity .


3. Memorabilty

    \-  The system should be memorable, so that the student does not have to learn it again after being away for a while.


4. Errors

    - The system should have low error rate, by preventing the student from making errors and recovering from errors made. There should not be catasrophic errors.


5. Satisfaction

   - The system should be satisfactory to the student , inother words it should be likeable.


6. User in control

   - The user should be in control of the system .



----
Task 2
----
h4. Planning Report:

• The goal of the test: what do you want to achieve?

{color:#008000}Goal of the test is to check if the Winha system fits the user requirements.{color}

{color:#800000}MB: What user requirements you mean here? The usability criteria or some other requirememnts?{color}



• Where and when will the test take place?

{color:#008000}The test will take place possibly in one of Usability and Interface design labs.{color}


• How long is each test session expected to take?

{color:#008000}We expect each test to take 30-45 minutes{color}


• What computer support will be needed for the test?

{color:#008000}For the test basic computer configuration is prefered. Winha should be accessible using the most basic configurations computer.{color}

{color:#008000}Network connection is needed.{color}


• What software needs to be ready for the test?

{color:#008000}Any basic operating system (Win XP,  Win 7, Mac OS, or other), Any major browser (Opera, IE, Chrome, Mozilla){color}


• What should the state of the system be at the start of the test?

{color:#008000}User is not logged in.{color}


• What should the system/network load and What should the system/network load and response times be? (not too fast or too slow);

{color:#008000}Response time is not critical, though it should be as fast as possible.{color}


• Who will serve as experimenters for the test?

{color:#008000}We, the members of the group.{color}


• Who are the users going to be and how are we going to get hold of them?

{color:#008000}We will research Winha from the "student user" point of view{color}


• How many users are needed?

{color:#008000}1 - ∞{color}


• What test tasks will the users be asked to perform?

{color:#008000}1) Log in to Winha.{color}

{color:#008000}2) Check enrollments{color}

{color:#008000}3) Enroll to new cource{color}

{color:#008000}4) Check current ECTS amount{color}

{color:#008000}5) Check course details{color}

{color:#008000}Task list can be improved during the test{color}


• What criteria will be used to determine when the users have finished each of the test tasks correctly?

{color:#008000}1) Log in to Winha. -{color} {color:#00ff00}user logged in{color} {color:#ff0000}/ user failed to log in.{color}


{color:#008000}2) Check enrollments -{color} {color:#00ff00}courses the user enrollet to are displayed correctly{color} {color:#ff0000}/ incorrectly.{color}


{color:#008000}3) Enroll to new cource -{color} {color:#00ff00}Enrolled OK{color} {color:#ff0000}/ failed to enroll\-{color}


{color:#008000}4) Check current ECTS amount -{color} {color:#00ff00}Amount of ECTS is correct{color} {color:#008000}/{color} {color:#ff0000}incorrect{color}


{color:#008000}5) Check course details -{color} {color:#00ff00}Course details are correct and meaningful{color} {color:#ff0000}/ wrong or useless course details.{color}


{color:#008000}Task list can be improved during the test{color}

• What user aids will be made available to the test users (manuals, online help, etc)?

{color:#008000}Online help provided by Winha itself{color}


• To what extend will the experimenter be allowed to help the users during the test?

{color:#008000}0 %{color}


• What data is going to be collected and how will it be analysed?

{color:#008000}Result of test (probably measured in %% of comletion) - 100% result OK - 0% failed{color}

{color:#800000}OK go, when you ahve done the pilot test, then amend to what of the task and taks combinations provide information to what of your usability criteria.{color}

<!--table 	{mso-displayed-decimal-separator:"\."; 	mso-displayed-thousand-separator:"\,";} .font5 	{color:windowtext; 	font-size:8.0pt; 	font-weight:400; 	font-style:normal; 	text-decoration:none; 	font-family:Verdana; 	mso-generic-font-family:auto; 	mso-font-charset:0;} td 	{padding-top:1px; 	padding-right:1px; 	padding-left:1px; 	mso-ignore:padding; 	color:windowtext; 	font-size:10.0pt; 	font-weight:400; 	font-style:normal; 	text-decoration:none; 	font-family:Verdana; 	mso-generic-font-family:auto; 	mso-font-charset:0; 	mso-number-format:General; 	text-align:general; 	vertical-align:bottom; 	border:none; 	mso-background-source:auto; 	mso-pattern:auto; 	mso-protection:locked visible; 	white-space:nowrap; 	mso-rotate:0;} .xl24 	{white-space:normal;} .xl25 	{border:.5pt solid windowtext;} .xl26 	{text-align:right;} .xl27 	{text-align:center; 	border-top:.5pt solid windowtext; 	border-right:none; 	border-bottom:.5pt solid windowtext; 	border-left:.5pt solid windowtext;} .xl28 	{border-top:.5pt solid windowtext; 	border-right:.5pt solid windowtext; 	border-bottom:.5pt solid windowtext; 	border-left:none;} .xl29 	{font-size:12.0pt; 	font-weight:700; 	text-align:center;} .xl30 	{border-top:none; 	border-right:none; 	border-bottom:.5pt solid windowtext; 	border-left:none;} .xl31 	{border-top:.5pt solid windowtext; 	border-right:none; 	border-bottom:.5pt solid windowtext; 	border-left:none;} .xl32 	{text-align:left; 	white-space:normal;} ruby 	{ruby-align:left;} rt 	{color:windowtext; 	font-size:8.0pt; 	font-weight:400; 	font-style:normal; 	text-decoration:none; 	font-family:Verdana; 	mso-generic-font-family:auto; 	mso-font-charset:0; 	mso-char-type:none; 	display:none;} -->| Winha system testing |
| Pilot test |
| | | | |
| Final goal of testing is to   evaluate basic usability of Winha system. To find possible ways for   improvement of system. |
| The goal of this pilot testing   is define apropriate questions for final questionarie |
| This test is to be perforemed   inside testing group. Person performing the test is entitled to add any   coments during testing process. According to results of test, more precise   questions will be added. |
| | | | |
| date: | | |
| place: | | |
| name of tester: | | |
| | | | |
| | yes | yes, with difficulties | no |
| Were you able to log in with your standard credentials? | | | |
| Were you able to check courses you are enrolled in? | | | |
| Were you able to find apropriate course? | | | |
| Were you able enroll to desired course? | | | |
| Were you able to check your ECTS amount? | | | |
| Were you able to check details of specific cource? | | | |
| Were you able to distinguish obligatory & optional cources? | | | |
| | | | |
| Any other questions you consider might be relevant: | | | |
| | | | |
| | | | |
| | | | |
| | | | |