My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
EDUNERARequirementsSpecificationDocumentRev2  

#Edunera Requirements Specification Document Revision 2

Table of Contents

Changes List

  1. Requirement 1 changed as "General users shall browse for online courses with names and categories".
    • Suggest tags while typing
    • Enable browse for instructors, institutions
  2. Requirement 5 changed as "General users shall report bugs to admin".
    • If a general user found a bug, user shall be able to report bug.
  3. Requirement 7 changed as "Registered users shall add/update/delete courses to a list".
    • Registered user shall create a courses list. Enable to vote user should add a course to the list.
  4. Requirement 8 updated according current changes of related requirements.
  5. Requirement 9 changed as "Registered users shall vote for courses they enrolled and courses' lectures".
    • Registered users can vote for courses's lectures and instructor in addition to course itself.
  6. Requirement 10 changed as "Registered users shall add/edit comment and review of courses they enrolled".
    • Also comments for instructors should be available.
  7. Requirement 15 changed as "Admin shall delete comments or reviews if the content is harmful".
    • Delete option should not allowed for admin.
  8. Requirement 16 changed as "Admin shall display list of complaints and bug reports".
    • Bug reports and complaints should be listed in admin's page.
  9. Use Cases were also updated.

Additional Changes on 02.04.2013:

  1. Requirement 13 is newly added as "Registered users shall add/edit courses, lectures and instructors information".

1.Introduction

The purpose of the software project is to develop a web application and a mobile evaluation application for a better MOOC (Massive Open Online Course)systems for a better future education system. Users of this application can be divided into three groups namely general users, registered users and admins. Users can use Edunera application requirements as in the following:

  1. General users shall browse for online courses with names and categories
  2. General users shall display votes and votes' statistics about courses
  3. General users shall register to the system
  4. General users shall send complaints to admin if there is any harmful content
  5. General users shall report bugs to admin

  1. Registered users shall display/update their profile information
  2. Registered users shall add/update/delete courses to a list
  3. Registered users shall display their courses list
  4. Registered users shall vote for courses they enrolled and courses' lectures
  5. Registered users shall add/edit comment and review of courses they enrolled
  6. Registered users shall add semantic tag for courses
  7. The System shall make recommendations for users by using semantic tags
  8. Registered users shall add/edit courses, lectures and instructors information

  1. Admin shall display/update user profile
  2. Admin shall delete comments or reviews if the content is harmful
  3. Admin shall display list of complaints and bug reports
  4. Admin shall send mails to all registered users
  5. Super Admin shall add/update/delete admin information
  6. All Admins' and Super Admin actions shall logged by the system

The web application functions and user interface details are given in the following sections of this document.

2.Requirements

2.1.Requirement 1:General users shall browse for online courses with names and categories

General users can browse for courses of MOOC applications with a keyword. Keyword can be searched through semantic tags of MOOCs via dbpedia. Users enter the keyword to a textbox and then click search button. If system founds related courses and lists them from highly voted to non-voted courses. If there is not any related course, the system displays an appropriate message to user. Also instructors and institutions can be browsed.

When user browses courses, system should suggest more semantic tags to the user. Therefore, user may be find more easily what he is looking for.

2.2.Requirement 2:General users shall display votes and votes' statistics about courses

When user open a course, the system display the course's vote statistics. Those statistic results are calculated from voting and answers of questions results. Those statistic results can be like as the below list.

  • How many user were voted?
  • What is the average voting result?
  • How many voted user were enrolled the course?
  • How many voted user who are not enrolled the course does think about enrolling?
  • What is the average weekly attendance rate of the voted person who were enrolled the course?

2.3.Requirement 3:General users shall register to the system

Registration process requires at least name, surname, password and email information of prospected user. After a successful submit operation, an activation email containing a validation link to complete activation is sent to to the given email address. Upon validation, user is able to list his/her courses and able to fill evaluation forms for the course, also able to use other registered user functions. Main page for the application welcomes users with course categories and links to pages to search courses and log in to the system. Course categories are determined by admin.

Log in page requires user email address and password used in registration, also gives links standard registration page and forgot my password pages.

List of registration information:

  • Name,
  • Surname,
  • Email,
  • Password

2.4.Requirement 4:General users shall send complaints to admin if there is any harmful content

General users can send the complaint message to the admins if the content is harmful. For sending a complaint user can use below interface.

User Name: User E-Mail: ID of harmful content : Complaint Message Body:

BUTTONS: SEND MESSAGE, CLEAR, BACK TO MAIN MENU

2.5.Requirement 5:General users shall report bugs to admin

General users can send bug report to the admins if the user found a bug in the system. For sending a complaint user can use below interface.

User Name: User E-Mail: Bug Name : Bug Message Body:

BUTTONS: SEND MESSAGE, CLEAR, BACK TO MAIN MENU

2.6.Requirement 6:Registered users shall display/update their profile information

In the profile page of users, they can display their all personal information. They can update their password. There are also some optional information fields for user to fill. User can fill the fields he/she wants and be able to update his/her personal information. These fields can be like in the below list.

  • Education,
  • Occupation,
  • Interested Fields,
  • Birth date,
  • Upload Picture,
  • Location,
  • Gender,
  • Web Site

2.7.Requirement 7:Registered users shall add/update/delete courses to a list

Users can add a courses to his/her course list. Following are the information that can be taken from the user when he/she add a course to the list.

  • Status;
    • Currently taking,
    • Completed,
    • Plan to Enroll,
    • On-hold,
    • Dropped.
  • Lectures Taken, (for currently taking or dropped course)
  • Score; (For Voting)
  • Add Favorite Courses,
  • Comment.

All these information can be added while adding a new course and also updated. User may delete his/her course from the list. User can add a course from his/her profile my courses page by selecting from a dropdown list or from the course page from add to list link.

Updating added course information have a several scenarios. For Example;

  1. User may want to see currently taking courses progress by updating,
    • Lectures Taken. (can be increased or decreased)
  2. User may want to update course status.
  3. User may want to update overall score of the course.
  4. User may want to add additional comment for course and update it.
  5. User may want to add course to my favorite list.
  6. User may want to delete the course.

2.8.Requirement 8:Registered users shall display their courses list

User can display all his/her courses from my course list or user page also lead to my courses page. Course lists are categorized according to course's status. User can display courses lists with;

  • Categorized version, (Currently taking, Plan to Enroll, etc.)
  • List courses by their overall score from user itself.
  • List courses by their Lectures Taken field,
  • List courses by their general vote statistics.

In addition from this page user can go to voting window for each course.

2.9.Requirement 9:Registered users shall vote for courses they enrolled and courses' lectures

Course voting system is accessible for only registered users who are added the course in their list. User should enter his/her email and password to enter the system. Voting can be categorized as overall score and some specific voting cases such as,

  • instructor:
    • Teaching skills: Not Good - Awesome
  • course materials:
    • Insufficient-Very Sufficient
  • learning:
    • Time wasting - Very useful
  • difficulty:
    • Easy-Difficult

Those can be voted according to likert scale by giving a rate number from 1-10. According to voting cases each lectures can be also voted.

2.10.Requirement 10:Registered users shall add/edit comment and review of courses they enrolled

Users can discuss and comment issues about lecture assignments, course subjects and expected questions, refer further information related online courses. Discussion forms can have ranking system for problem discussions to reduce searching also.Further details of the operation should be decided upon during the design.

2.11.Requirement 11:Registered users shall add semantic tag for courses

User can add semantic tags for a course from a dropdownlist that is bind with the system database.

2.12.Requirement 12:The System shall make recommendations for users by using semantic tags

System can recommend further courses to users by using course list, voting results and some machine learning techniques like dimension reduction. Since it is supervised system, at the beginning, recommendation may not be satisfactory but with further data and user contribution, recommendation results can be more acceptable.Further details of the operation should be decided upon during the design.

2.13.Requirement 13:Admin shall display/update user profile

The admin authentication is through the entry of correct the admin name and password. After the admin entered the system can manage have the authority to manipulate all users data.

2.14.Requirement 14:Admin shall display list of complaints and bug reports

2.15.Requirement 15:Admin shall delete comments or reviews if the content is harmful

Admin can display complaint messages and if the content is really harmful then he/she can send a message to the content owner and delete the content.

2.16.Requirement 16:Admin shall send mails to all registered users

Admin can send mail to all users with the below interface example.

All Users: Yes/No (menu selection)

Subject : Email Message Body: Any File to Attach:

BUTTONS: SEND EMAIL, CLEAR, BACK TO MAIN MENU

Entered email message subject, body and its attached file, if any, will be sent to all users one by one, that is destination field of the sent email will not contain all email addresses seperated by comma. Any File to Attach menu item may include a browse function, which will allow the administrator to browse directories and select a file to attach.

2.17.Requirement 17:Super Admin shall add/update/delete admin information.

Any admin profile should be created by a super admin in the system by filling out a form containing the following information. All fields are mandatory, unless marked as not mandatory (there should be a message about this to the super admin).

  • Lastname
  • Name
  • Email
  • Password
  • Contact Phone
  • Address Line 1
  • Address Line 2
  • Address City
  • Address Country (select from a menu of all countries)
  • Further Comments (A free info field) (not mandatory)

Reasonable lengths for all data fields are to be assumed. All data fields are free format. Super admin can also update and delete any admin information.

2.18.Requirement 18:All Admins' and Super Admin actions shall logged by the system.

Actions of all system administrators aimed to be logged to database.

2.19 Requirement 19:Development Environment

The software will be developed in an object oriented programming language Java with play framework. The development and operation environment is Windows. Details will be decided.

2.20 Requirement 20:Security

All client-server operations through the Internet will be through SSL to provide security.

3. Mobile Client Capabilities

Mobile Clients can display courses information and if they are registered users, they can display their profile and courses information. Also all voting and tagging functions will be available by mobile. We also aim to add mobile discussion forms and announcements access for our mobile clients.

4.Testing

Unit tests will be done by each writer of the codes and further testing details will be decided in design.

Powered by Google Project Hosting