Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Outcomes: Difference between revisions

From MoodleDocs
No edit summary
m (cat edit)
Line 17: Line 17:
Some example scenarios: [[Outcomes_examples]]
Some example scenarios: [[Outcomes_examples]]


 
[[Category:Outcomes]]
[[Category:Future]]

Revision as of 09:20, 18 June 2007

Feature description: Build on the keywords in 1.6 to provide metadata/outcomes/competencies/goals for all activities and courses, linkable to standard lists of metadata such as State-based learning outcomes and curricula.

In short it works like this:

  1. The admin for the site imports (or types!) a long list of short text statements (outcomes or metadata). These are like the "official" tags that we have now in blogs. Let's call it list A.
  2. Teachers can choose a subset of list A to apply to their course. The course is now tagged with metadata representing the outcomes of that course (list B)
  3. Teachers can choose a subset of list B for each activity in Moodle (list C, D, E etc).
  4. Teachers can (at course level) generate a report showing the overall coverage of list B among all the activities. This way it's easy to see if a particular outcome has been forgotten or not covered well enough. It also forces the teacher to think hard about course design, which is a good thing.
  5. Teachers grade students either with a single grade
  6. When students complete a given course, the outcomes for that course are recorded against the user's name. This allows:
    1. reporting by student of which outcomes they have completed
    2. reporting for students about which outcomes they are yet to achieve
    3. smart course selection (find me a course to teach me "xxxxx")
    4. reporting for admins about all students on the system and where they are up to.


Some example scenarios: Outcomes_examples