Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Target releaseSept-16 (prefereably June-16)
User Story SWIK-191 Deck editor
Document status

Status
titleDRAFT

Date
Document owner
Designer
Developers
QA
Work Package deliverable

D4.3: First stable version of SlideWiki usable, accessible and ubiquitous user interface

WP 2, 3, 4

Related tasks in JIRA:

Task - A task that needs to be done. SWIK-78 Discuss how to handle presentation themes & transitions

Task - A task that needs to be done. SWIK-103 Create a prototype for DeckView and DeckEdit components

Task - A task that needs to be done. SWIK-104 Create Deck/Slide Service

Task - A task that needs to be done.Image Added SWIK-344 Accessible tag list edit for React


 

Summary

  • As a user I want to edit the structure and properties of a presentation deck.

...

Source material for user/stakeholder feedback

Discussion during SemWeb meeting 31-05-2016 at VU Amsterdam:

Hide decktree structure? - is advanced option. Many users want simple structure.

 

Requirements (/user stories) from pilot roadmap:

 

  •  As a content producer, I need the platform to be easy to handle, e.g. through clear and simple structures, and fast to access.  (IKH BIZ)

  • As a content producer, I would like to have a wizard that guide me to the creation of a content that follow the guidelines for UPV MOOCs.(UPV)

...

Evaluation/improvements by Farid Hasanov master thesis :

Issue5 - Adding slides. Users were complaining that adding a new slide is time-consuming to find and perform. It takes time to guess that a right click on the slides hierarchy could be performed.

 

Source. Two users raised this issue, as they experienced slight delays while attempting to increase the number of slides.

 

 

Figure 5.13: Slide adding original.[51].

 

 

 

 

 

Metrics violated: Ease of use, Friendliness.

 

Here, the first user made 3 mistakes and carried out a task within 47 seconds. The ease of use is 25%. The second user spent more time and made more errors. The result is only 14%. For the third user it was 34%.

 

Possible Solution. Since not everyone guesses to right click over the slides, perhaps some note explaining this possibility should be added to the website. However, the best way to solve the slide-adding problem is to provide two small buttons for slide and deck adding. The overall picture looks something like this:


 

 

 

 

 

 

Figure 5.14: Slide adding mockup.

 

 

 

Of course these two buttons will move down each time the amount of slides or decks is increased. This will raise the speed of the user’s interaction with the product since it takes less time than right clicking.

 

 

 

 

Evaluation at UniBonn :