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
EDUNERARequirementsSpecificationDocument  

RSDVersion1
Updated Mar 17, 2013 by k.oznuri...@gmail.com

#EDUNERA Project Requirements Specification Document.

Table of Contents

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 to do mainly the following:

  1. Users shall browse for online courses
  2. Users shall display vote results about courses
  3. Users shall register to the system

  1. Registered users shall display/update their profile information
  2. Registered users shall vote for courses they enrolled
  3. Registered users shall join or start a discussion in forums
  4. Registered users shall add semantic tag for courses
  5. Registered users shall make their own courses list

  1. The System shall make recommendations for users by using semantic tag.
  2. General users shall send complaints to admin if there is any harmful content
  3. Admin shall display/update/delete user profile.
  4. Admin shall delete comments or discussions if the content is harmful.
  5. Admin shall send mails to all registered users.

  1. Super Admin shall add/update/delete admin information.
  2. 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:Users shall browse for online courses

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.

2.2.Requirement 2:Users shall display vote results 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: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: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.5.Requirement 5:Registered users shall vote for courses they enrolled

Course voting system is accessible for only registered users. User should enter his/her email and password to enter the system. Anyone can vote for course but should enter some additional information about himself/herself for more reliable results. Additional information can be as below list.

  • Were you enrolled the course? Yes/No
  • If the first questions answer is No, the system asks "Do you think to enroll to the course? Yes/No".
  • If the first questions answer is Yes, the system asks "How many weeks did you participate the course?".

2.6.Requirement 6:Registered users shall join or start a discussion in forums

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.7.Requirement 7: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.8.Requirement 8:Registered users shall make their own course list

Users can create a list for courses they are enrolled or wanted to enroll.

2.9.Requirement 9:The System shall make recommendations for users by using semantic tag

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.10.Requirement 10: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.

ID of harmful content : Complaint Message Body:

BUTTONS: SEND MESSAGE, CLEAR, BACK TO MAIN MENU

2.11.Requirement 11:Admin shall display/update/delete 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.12.Requirement 12:Admin shall delete added comments or discussions 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.13.Requirement 13: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.14.Requirement 14: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.15.Requirement 15:All Admins' and Super Admin actions shall logged by the system.

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

2.16 Requirement 16: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.17 Requirement 17: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