Non-critical user stories (TODO after september 2016) :
- Abi James
This is a copy of the information listed in the Google Doc Requirements SlideWiki 2.0.
Semantification |
E-learning - non-question & test related (i.e., "the rest") |
Export - non-PDF |
Import - non-powerpoint PPTX formats |
New page lay-out |
New theme (colors, logo,..) |
SEO |
UI internationalisation |
Content recommendation
|
Requirements for year 1 - User Stories from pilot roadmap:
I need to include consultation and peer evaluation methods and also learning analytics. (EKDDA)
This User Story is motivated by PUPIN Institute as publisher of training materials. In order to be used for delivering trainings related to proprietary software (e.g. different PUPIN products), (PUPIN)
besides standard features (import / export, collaborative editing) (PUPIN)
I would like to be able to integrate SlideWiki with Moodle and Openedx. (GFOSS)
I would like Slidewiki to offer a tool similar to MediaWiki's Data Transfer (https://www.mediawiki.org/wiki/Extension:Data_Transfer) that will allow user users to both export and import data from and to the wiki(GFOSS)
As a trainer, I want my material to be connected to the CloudRoom environment (http://beta.cloudroom.es/#/course/UPMSWLD) and to OpenEdX (UPM)
As a content producer, I would like SlideWiki to be connected to source code repositories like GitHub, so as to connect my lecturing material with the software releases/virtual machines/etc., required for running examples (UPM)
As an instructor, I need SlideWiki to be integrated with eCampus (ILIAS), which I'm using for managing everything about my class except the lecture notes.(UBO)
As a provider of e-learning courses, instructors from the Metropolitan University will need the SlideWiki to be integrated with the existing eLearning system. (PUPIN)
As a content producer I would like to integrate slidewiki with a Moodle platform. (UFRJ)
2.1 SWIK-??? - About
2.1.1 User Story:
2.1.2 Coordinator/Lead:
2.1.3 JIRA priority:
2.1.4 Related tasks in JIRA:
2.1.5 Identified requirements (e.g., in existing system):
Requirements for year 1 - User Stories from pilot roadmap:
Evaluation/improvements by Farid Hasanov master thesis :
Issues of informative character. Here, flaws concerning the ’about’ page and other informative links will be demonstrated.
Issue1 - wrong displacement of license page. A link to a page about license information opens only on the edit page and has misled the users.
Current state:
Figure 5.26: License information of Slidewiki.[51].
During the test, the user stated that he wanted to press this button, because he thought that this was also a tool for slide editing.
Metric violated: Organization.
Source. One user mentioned this drawback.
Possible Solution. Taking into an account this remark, the decision was made to remove that icon totally, thereby clearing some space. License information can be placed into the “About” tab of the header panel. Creator information can also be placed below the presentation. As well as freeing space for editing, this will also guarantee that, while changing slides when the transition type “Cube” is selected, the edges of the presenta- tion will not be cut.
Issue2 - Contact information. Users met some complications searching for a contract person. They were either going to the footer or scrolling the upper navigation bar of the website.
Metrics violated: Organization, Web-related criteria such as finding contact information. For the first user it took 1 minute and 3 seconds to correctly find the owners information. 3 wrong pages were visited and scrolled in order to achieve the goal. Exactly a minute was spent by the second user on the same task. However, the number of wrong clicks was 0, due to the fact that he searched the main page, or more precisely it’s footer, for the contacts. The third user was more successful, achieving his goal within 34 seconds.
Source. Two users stated that this was an issue.
Possible Solution. The proposal is to add a separate line in the “About” menu, named “Contact us”. This link will open as a page in the website itself with all the contact information, or direct a user to the site of the research group.
2.1.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.1.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.1.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
2.2.1 User Story:
2.2.2 Coordinator/Lead:
2.2.3 JIRA priority:
2.2.4 Related tasks in JIRA:
2.2.5 Identified requirements (e.g., in existing system):
Requirements for year 1 - User Stories from pilot roadmap:
Evaluation/improvements by Farid Hasanov master thesis :
Footer issue. Several testers mentioned that the footer of the website has a flaw. Issue - organization of the footer. The footer is organized in a confusing and unappeal- ing manner, with the section titled “About” creating particular frustration. Users noted that it isn’t aesthetically pleasing that the aforementioned page is located between the presentations and the footer. Metrics violated: Organization, Color and Style.
Source. Two users found the style of the footer unappealing.
Current state. The image below indicates the original state of the footer:
Figure 5.27: Original footer.[51].
Possible Solution. The decision was made to remove the “About” section and to feature it on a separate page. The rest of the links are to be arranged in more visually appealing way, according to the design rules.
Figure 5.28: New footer mockup.
2.2.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.2.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.2.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
2.3.1 User Story:
As a user I want to import SlideWiki content from standard file formats so that I can
use my existing presentations on SlideWiki
2.3.2 Coordinator/Lead:
2.3.3 JIRA priority:
major = can be done after September 2016
2.3.4 Related tasks in JIRA:
2.3.5 Identified requirements (e.g., in existing system):
Requirement (proposed by Abi and Ali) = support presenter notes
Requirements for year 1 - User Stories from pilot roadmap:
As a content producer and training provider, I need to import and export different types of materials((e.g. presentations, SCORM packages, HTML, ePUB, Word files, pdf files etc. ) (EKDDA)
As a content producer I would like to import existing educational material (from different sources) to SlideWiki and export it to various formats (e.g. presentations, SCORM packages, HTML, odp files, pdf files etc.) (GFOSS)
I think a powerpoint.openoffice.appleslides import export is critical (VUA).
As a content producer, I need to import different types of existing materials (e.g. presentations, SCORM packages, HTML, ePUB, Word files) in order to reuse and repurpose them. I also need to export my OERs in the aforementioned formats. (OU)
Evaluation/improvements by Farid Hasanov master thesis :
<none>
2.3.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.3.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.3.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
2.4.1 User Story:
User Story
As a user I want to export SlideWiki content to standard file formats so that I can
use content I created on SlideWiki in other applications
2.4.2 Coordinator/Lead:
2.4.3 JIRA priority:
major = can be done after September 2016
2.4.4 Related tasks in JIRA:
(SUBTASK) 1. Document how deck structure alignes to ePub3 standard
2.4.5 Identified requirements (e.g., in existing system):
Requirements for year 1 - User Stories from pilot roadmap:
As a content producer, I want the EPUB export format to be of version 3.0.(ACC)
As a content producer and training provider, I need to import and export different types of materials((e.g. presentations, SCORM packages, HTML, ePUB, Word files, pdf files etc. ) (EKDDA)
As a content producer I would like to import existing educational material (from different sources) to SlideWiki and export it to various formats (e.g. presentations, SCORM packages, HTML, odp files, pdf files etc.) (GFOSS)
I think a powerpoint.openoffice.appleslides import export is critical. (VUA)
As a content producer, I need to import different types of existing materials (e.g. presentations, SCORM packages, HTML, ePUB, Word files) in order to reuse and repurpose them. I also need to export my OERs in the aforementioned formats. (OU)
As a content producer, I want SlideWiki to create accessible HTML5 content which can be easily exported into the FutureLearn platform (SOTON)
As a content producer I would like to embeed slide wiki presentations on wordpress posts. (UFRJ)
Evaluation/improvements by Farid Hasanov master thesis :
<none>
Performance (of export)
2.4.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.4.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.4.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
2.5.1 User Story:
2.5.2 Coordinator/Lead:
2.5.3 JIRA priority:
2.5.4 Related tasks in JIRA:
2.5.5 Identified requirements (e.g., in existing system):
Requirements for year 1 - User Stories from pilot roadmap:
Evaluation/improvements by Farid Hasanov master thesis :
Motivated by existing research in the field of e-learning [15], [17],the decision to create a multimedia communication system for the website was taken. This will ease user interaction and eliminate the necessity to rely on e-mails. The button for checking the messages will be located near the “Edit Profile” button. When the user navigates onto it without clicking, a pop up window will appear, showing recent messages and basic options. This can be clearly seen in the following image:
Figure 5.30: Messages without clicking on the button.
As mentioned before, this window opens directly over the user page window. Messages are separated with different colors in order to clearly distinguish between them. In the case of a message button being clicked, the following page will be opened in a new window:
2.5.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.5.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.5.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
2.6.1 User Story:
2.6.2 Coordinator/Lead:
2.6.3 JIRA priority:
2.6.4 Related tasks in JIRA:
2.6.5 Identified requirements (e.g., in existing system):
Requirements for year 1 - User Stories from pilot roadmap:
create learning paths from different modules.(EKDDA)
Evaluation/improvements by Farid Hasanov master thesis :<none>
2.6.6 Existing SlideWiki 1.0 lay-out - screenshot(s):
2.6.7 New SlideWiki 2.0 lay-out - mock-up(s):
2.6.8 Description of fields/input/elements + validation + test scenarios:
[example] Clickable link “Upload your presentation” in Header. Onclick go to upload page.. [/example]
[example]Input text field name = validation of special characters and SQL/code insertion[/example]
3 Non functional requirements
NFR1 - Performance
NFR2 - Reliability
NFR3 - Scalability
NFR4 - Usability
Etc…
ALso see technical problem, solution, decisions, and traceability in software architecture document