Trecx:FunctionalRequirements

From Bodington Wiki

Jump to: navigation, search

Back to TReCX

Contents

Introduction

As mentioned elsewhere, there are two primary actors in the tracking context. The trackee who is the some what unwitting participant (even if their consent has been given!) who is participating indirectly by virtue of using e-Learning applications that happen to implement tracking. The second actor type is the tracker who is concerned with analyzing and reviewing tracking information. Therefore, this page is split into two main sections; one concerned with the trackee (events generated) and the other with the tracker (report generation).

Trackee-oriented: (event generation)

What events should we be storing? We looked at the following e-learning applications and noted what we would like to track.

Wiki

We should record:

  • user X creates wiki area Z in wiki at <date+time>
  • user X registered with wiki at <date+time>
  • user X logged in to wiki at <date+time>
  • user X created page Y in wiki area Z at <date+time>
  • user X modified page Y in wiki area Z at <date+time>
  • user X accessed (read) page Y in wiki area Z at <date+time>
  • user X logs out of wiki at <date+time>

And the summaries we would like:

  • list of users who have looked at some part of wiki Z
  • list of users who have read page Y on wiki Z
  • list of users who have contributed to page Y on wiki Z
  • list of pages (with dates and times) in wiki area Z that user X has accessed
  • list of areas and pages (with dates and times) in whole wiki that user X has accessed
  • list of pages (with dates and times) in wiki area Z that users X1, X2, X3, .., Xn have accessed
  • list of areas and pages (with dates and times) in whole wiki that users X1, X2, X3, .., Xn have accessed
  • number of distinct accesses to wiki Z (so we can do a popularity rating)

Course Booking system

We should record:

  • user X registered at <date+time>
  • user X logged in at <date+time>
  • user X accesses (reads) page about course Y at <date+time>
  • user X registers for course Y <date+time>
  • user X un-registers for course Y <date+time>
  • user X adds new course Y at <date+time>
  • user X modifies course Y at <date+time>
  • user X deletes course Y at <date+time>
  • user X makes a comment (ie, reviews) course Y at <date+time>
  • user X logs out at <date+time>

Forum

We should record:

  • user X registered at <date+time>
  • user X logged in at <date+time>
  • user X creates new forum instance Y at <date+time>
  • user X creates new forum thread T
  • user X posted message Z to thread T on forum Y at <date+time>
  • user X read message Z posted to thread T in forum Y at <date+time>
  • user X modifies message Z posted in forum Y at <date+time>
  • user X locks forum at <date+time>
  • user X unlocks forum at <date+time>
  • user X deletes forum Y at <date+time>
  • user X logs out at <date+time>

And the summaries we would like:

  • list of users who have read message X
  • list of users who have posted to forum Y
  • list of users who have accessed forum Y
  • list of forums that user X has acessed
  • list of forums that user X has posted to
  • list of messages in forum Y that user X has read
  • list of forums that users X1, X2, X3, .., Xn have acessed
  • list of forums that users X1, X2, X3, .., Xn have posted to
  • list of messages in forum Y that users X1, X2, X3, .., Xn have read
  • number of distinct accesses to forum Y (so we can do a popularity rating)
  • number of distinct accesses to application (so we can do a popularity rating)

Chat

We should record:

  • user X registered at <date+time>
  • user X logged in at <date+time>
  • user X creates chat room Y at <date+time>
  • user X entered chat room Y at <date+time>
  • user X posted a message in chat room Y at <date+time>
  • user X leaves chat room Y at <date+time>
  • user X logs out at <date+time>

And the summaries we would like:

  • list of users who have visited chat room Y
  • list of users who have posted a message in chat room Y
  • list of chat rooms that user X has visited
  • list of chat rooms that user X has posted to
  • length of time that user X has been in chat room Y
  • number of distinct accesses to chat room Y (so we can do a popularity rating)
  • number of distinct accesses to chat application

Assessment

We should record:

  • user X registered with assessment system at <date+time>
  • user X logged in at <date+time>
  • user X visited assessment Y at <date+time>
  • user X submitted answers for assessment Y at <date+time>

And the summaries we would like:

  • list of users who have visited assessment Y
  • list of users who have submitted answers for assessment Y
  • number of distinct accesses to assessment Y (so we can do a popularity rating)
  • number of distinct accesses to assessment application

The following is out of scope:

  • How many questions the student got right, ie, score.
  • Which questions the student got wrong
  • What was the average score for the class for each question

PDP

We should record:

  • user X registered with system at <date+time>
  • user X logged in at <date+time>
  • user X visited page Y at <date+time>
  • user X created a new PDR at <date+time>
  • user X shared (granted access to) PDR P with user Y
  • user logs out at <date+time>

Repository

How much do we track about document? We need a title I guess. We should record:

  • user X registered with system at <date+time>
  • user X uploaded document Y at <date+time>
  • user X modifed document Y at <date+time>
  • user X reviewed document Y at <date+time>

And the summaries we would like:

  • list of users that accessed document Y
  • list of documents access by user X
  • list of documents modified by user X

Annotation (Digital Repositories)

We should record:

  • user X commented on resource Y at <date+time>

And the summaries we would like:

  • list of users that have commented on resource Y

Reading list

We should record:

  • user X registered with system at <date+time>
  • user X accessed reading list Y at <date+time>
  • reading list Y created at <date+time>
  • reading list Y modified at <date+time>

And the summaries we would like:

  • list of users that accessed reading list Y between <date> and <date>
  • summary: list of additions between <date> and <date>
  • summary: number of distinct accesses to reading list Y (popularity rating)

VLE

We should record:

  • user X registered with system at <date+time>
  • user X logs in at <date+time>
  • user X creates resource Y at <date+time>
  • user X reads resource Y at <date+time>
  • user X updates resource Y at <date+time>
  • user X deletes resource Y at <date+time>
  • system reveals resource Y at <date+time>
  • system hides resource Y available at <date+time>
  • user X logs out at <date+time>

Tracker-oriented: (report generation)

Authorisation

The same search interface is applied to both the Trecx tracking store and to a tool with its own store. For reasons of security, this interface must have a place for the queryer's identity, it will be up to the target system to decide whether to autorise the request or not. For the purposes of Trecx, we will always assume that authorisation is given; in reality, the traget application will be obliged to contact a group membership service to confirm.

[This process is actually quite complex for Bods - it's not a case of authorised / not authorise - there's different levels of authorisation: See, View etc]

Queries

We's like to search across the following:

  • group of users: What did Dozy, Dave Dee, Dozy, Beaky, Mick and Titch 'do'. Here we will supply a list, in the future we'd like to browse and either select users or slect a group name (or list of groups).
  • date range: What happened between Date 1 and Date 2, (and the open ended: between Date 1 and today, and before Date 1).
  • list of resources: Details about all resources in the following list, (the list will be a set of URLs). Could be 1 item in list, could be many.

What other issues are there

  • results ordering (chronological, reverse chronological, alphabetical, any others?)
  • what are the top 10 most accessed resources

It is felt that http://www.w3.org/TR/xquery/ would be a suitable query language.

Results

In the fullness of time, we would like a nice graphical presentation of the search results, for this project we would expect the following

  • plain text list (in a browser)
  • CSV file export
  • iCal format

with the latter being 'icing on the cake'

Meta data

It would be desirable (but out of scope here) to fetch meta data about each event from the host system.

Visual Displays of Data

We need to ensure that we collect the raw data which when processed can be used to produce a similar sort of visual display produced by Blackboard. This means:

  • number of accesses per area
  • number of accesses over time
  • number of accesses per hour of the day
  • number of access per day of the week
  • number of accesses per user

We will collect the data to enable this to be done in a system such as Excel, but will not perform the processing as part of Trecx.

Flashy reporting

Allow stats to be displayed using Crystal Reports etc.

We will have collected this data but will not implement this functionality in this project.


Back to TReCX