Business Requirements

Functional Requirements

 

1. Web based interface (M):

BRD ID

Requirement

Category

 1.1

Web interface to allow users

1.1.1 to search for and

1.1.2 then select the releavnt courses to create

Must Have

 1.2

Web interface must be secured behind EASE (single sign on)

Must Have

 1.3

Method to allow users access to web interface

Users are defined as LTW - Moodle Service Team who will provide ADMIN access rights and IS Helpline.

Level of Authorisation to be considered.

Must Have

2. Creation of courses (M) - *please note there is no flag to show a course as Moodle enabled within EUCLID

BRD ID

Requirement

Category

 2.1

Data feed from EUCLID to allow user to search and then select course

Must Have

 2.2

Data feed from EUCLID to have a list of enrolled students

Must Have

 2.3

Data feed from EUCLID to get course organise / secretary

Must Have

2.4

3 parameters within Moodle need set:

  • Course Name
  • Course Short Name
  • Course ID (system primary key)

Must Have

2.5

Additional parameters needed:

  • Course ID number (ID from EUCLID plus potentially the academic year and semester information - similar to LEARN) - must allow for matching to Talis Resource Lists
  • Course Category
  • All current defaults applied
Must Have

3. Creation of Accounts (M) - please note the business partner does not want all user accounts being created in Moodle, it has to be on a selection basis

BRD ID

Requirement

Category

3.1

Some method to link to IDM (or alternative system) to get user details

Must Have

3.2

The fields within Moodle to be populated are as follows:

  • Username - '@ed.ac.uk' added to username
  • Authentication method - Shibboleth
  • First Name (perferred name if possible)
  • Surname
  • Email Address

Must Have

4. Create Enrolments (M)

BRD ID

Requirement

Category

4.1

If a user does not exist in Moodle then create user

Must Have

4.2

If a user does exist in Moodle then enrol on course

Must Have

4.3Roles to be created in Moodle at the same point as courses e.g. Student on XXX course, Teacher on XXX course

Must Have

4.4Add user on to Moodle Staff/ Student Help course as appropriate

Must Have

5. Update enrolments (M)

BRD ID

Requirement

Category

5.1

As enrolments change up to and after start date we need the web interface to allow updates of enrolments

Must Have

5.2

Students will also need to be able to be removed from courses where appropriate

*please note EUCLID remains the golden copy for this, all removals and updates must be done within EUCLID first

Must Have

5.3This update should not remove any staff manually added to courses - these are added as Ad hoc changes

Must Have

Please note if there is any prioritisation of development work then this area would be the preferred area to be completed first.

6. Update courses (S)

BRD ID

Requirement

Category

6.1

If information changed in EUCLID

Should Have

7. Category Structure (M)

BRD ID

Requirement

Category

7.1

The courses need to be created in a category structure within Moodle, current category structure to be documented

Must Have

8. Courses (S)

BRD ID

Requirement

Category

8.1

Courses should be able to be selected and their enrolments fed into a manualy created parent course to allow hubs to be created for various programmes.

 

The child course must still be visible and accessible on Moodle

Should Have

9. Integration (C)

BRD ID

Requirement

Category

9.1

The web interface should be able to be integrated as an iframe into Moodle admin screens

Could Have

10. Users (S)

BRD ID

Requirement

Category

10.1

Users will be updated if their details change in IDM unless manual changes have been made in Moodle

Should Have

Non-Functional Requirements

 

The frequency of the data feed from EUCLID (or other system) should be minimum once a day (time can be confirmed at design / build stage).