wiki:FunctionalDescription

Version 6 (modified by mschenk, 11 years ago) (diff)

Functional Description

The colored items are the ones that need to be filled in by our project:

1. Learning mall actions

1.1. A1. Find courses by criteria

1.1.1. Facets

The website allows visitors to find courses by a number of criteria. The user can filter the search by applying filters on a number of facets. The facets are:

  • startDate
  • duration
  • estimatedEffort
  • language (QUESTION do we want to show this when there is only one language?)
  • delivery
  • certifyingBody
  • creditType
  • credits

TODO What is the order of the facets on the page

1.1.2. Free text search

Visitors can enter search criteria on the website. This is free text. The text will be searched in the following fields of the course objects:

  • code
  • title
  • briefDescription
  • fullDescription
  • startDate (QUESTION really?)
  • duration
  • estimatedEffort
  • language
  • delivery
  • certifyingBody
  • creditType
  • credits

1.2. A2. Display CPCC’s within criteria

A part of the page is filled with the search result from the faceted search described above. The results are limited to a specific number (depends on graphics design). At the end of the result there will be a button 'more courses' that will retrieve the next 'page' of the results. These results will be added to the current page through an ajax call. See http://online-learning.harvard.edu for an example that closely resembles what we want.

1.3. A3. Admission type for CPCC

The 'enroll' option for a course will make a distinction between cpcc's with a 'pre' enrollment strategy and cpcc's with a 'post' of 'self' enrollment strategy. The first case will direct the user to action A4, the other case will lead to action A5

1.4. A4

This is a branching action resulting in three outcomes:

  • The course registration for the current user is registered in the learner registration system with a status of 'pending pre admission'
  • The subprocess 'Manually handle pre-admission' is started for this learner/cpcc (TODO specify how this is done)
  • The learner is presented with a page telling him this process has been started and he will now need to be patient. The same information is sent to him through e-mail.

1.5. A5. Forward to payment system

This action is responsible for forwarding the learner to the payment provider. The action will need to create an identification of the current transaction, holding at least the id of the learner, and the id of the ccpc that is being payed, handing of this data to the payment provider.

Information pertaining to meta-data on the ccpc and/or learner may need to be attached (TODO which information is this?)

1.6. A6. Admission type for CPCC

This action does the selection prior to giving the signal "go ahead and start learning" to the learner. It will check on the admission-type for the given cpcc and display an informational page for the learner on how to proceed now if the admission-type is 'self' or 'pre'. If the admission-type is 'post', some extra handling is necessary and action A7 is started.

1.7. A7

This action is a gather and fork action. First it makes sure that actions A6 and E2 have been done.

1.8. B10

1.9. B2. Register course payment

1.10. B3

1.11. B4. Update learner account status

1.12. B5

1.13. B6. Register course admission status

1.14. B7. Register course denial status

1.15. B8

1.16. B9. Register learner-course performance

1.17. C1

1.18. C2. Yield CPCC information

1.19. D1. Create a netid + password

1.20. E1. Provision a new user

1.21. E2. Enroll user in course

1.22. F1. Handle course / program payment

Attachments (2)

Download all attachments as: .zip