REAP ET/Use Cases/StudentTakesSession

Use Case UC1: Student takes a session

Scope: modular interface of REAP

Primary Actor: Student

Stakeholders and Interests: ...

Preconditions: interface has been set up by the Researcher (option: and by the Teacher)

Postconditions: Student has performed at least one assessment/instruction phase. Student's model has been updated.

Basic Flow:

1. Students logs in.
2. Student chooses a document to read.
3. Student reads a document.
4. Student takes a post-reading test.
5. Student gives his/her opinion.

Alternative Flows:

*a. At any time, Student decides to log out

1. System asks confirmation
2. Student confirms
3. Student's model is updated
4. Student logs out

*b. At any time, Teacher decides to insert a specific document in a system

1. System updates Student's model
2. System goes to reading phase with the specific document.

1a. Student's password is not set up

1. Student sets up password
2. Student logs in

1b. Student's username and password don't match.

1. System notifies Student.
2. Student retries.

2a. Student does not remember password.

1. Teacher resets password

2. Student logs in

2a. Student has not taken any pretest yet

1. Student takes pretest

2b. Reading is not an instructional module at this point

1. Student takes the instructional module (question, example, definition, sound) that has been set up.

3a. Document has poor quality

1. Student notifies System
2. Student chooses Document

3b. Student wants the definition of a word

1. Student looks up the word in the dictionary

3c. Student wants to hear a word

1. Student listens to the word

3d. Student wants an example sentence for a word

1. Student looks up an example sentence for the word

4a. Reading is not the instructional module

1. Student takes a post-instructional module test

Special Requirements:

• decent speed of display
• ...

Technology and Data Variation:
...

Frequency of occurence:

• Could be continuous

Open Issues:

...