|
Difference between
current version
and
current version:
| At line 0 added 11 lines. |
| + !Summary |
| + *A common analysis asked of the database will be to return longitudinal data. Many faculty and administrators are interested in tracking student progress over time. |
| + |
| + !Preconditions |
| + *The database must store data from multiple courses over time. |
| + *The database must link student data over time. |
| + |
| + !Basic Course of Events |
| + *A faculty member will query for student data (course, assessment or assessment item) across multiple semesters. |
| + *The database will return ALL data for that student (or multiple students) -- i.e., each semesters worth of data will be returned. |
| + *Should a faculty member want to add additional data in subsequent semesters or years, they will have to perform the search again and repeat their analysis - there will be no way to match students across queries. |
Back to Use Case 10,
or to the Page History.
|
