2.3.3. Add/Edit + First Time

This section references material covered in the User Interface Overview which provides the "building blocks" the user needs to create a test in the Test Generation Interface. It also uses terminology described in the Glossary.

For this use case, the user has just run the program for the first time and therefore has no questions in the database. The user would like to generate a short, 3 question quiz on inheritance.

From the main interface, the user gestures to generate a test by clicking on the New Test button on the Tests pallette. This brings up the New Test Dialog as seen below in Fiugre ?. As this is the first run of the program, the user sees no entries in the Courses list and sees the following entries in the Type drop-down list: "Exam", "Midterm", "Final", "Quiz". Since the system has no knowledge of the current term from other tests, it guesses based on the current date, that the term is Winter 2008.


yay
Figure 1 - New Test Dialog.

Although this is a good guess, it is actually the Spring term of 2008. Thus, the user clicks the term drop down and selects Spring from the list.   The user then clicks the "Show/Hide Details" toggle, revealing the Test Creation details.  Since the user hasn't created any questions or added any additioinal databases, only the main database is shown (Note: the program requires one database at all times, named "Main Database" by default).  The user leaves all the information blank because he plans on only using one section and presses OK.

yay
Figure 2 - New Test Dialog.
The program displays the main generation panel, shown below.  The user notices that the Main Database appears under databases but no questions are displayed in the database view.  Note that if the user tries to filter a filled database and there are no questions that match the filter, the below also applies.   Since there are no question in the database view, the auto-generate and generator buttons are greyed out.  The user clicks on the "Add Question" at the bottom of the test view.  This launches a test creation window and, as detailed in Section 2.2, creates a simple multiple choice question.  The question now shows up in the test view.  The user likes the question and wants it available for future use, so he right clicks on the file and selects "Add to Database" then "All".  The question now appears in the database view.
yay
Figure 3 - Main view with empty database

The user then adds two more questions, adding only the first to the database.  The summary now lists 3 questions and a total length of 35 minutes (the sum of the lengths or the questions created), which seems too long--the user notices he made a typo on the length of question 2.  The user selects question 2 and clicks the edit button which again brings up the question creation screen where he edits the erroneous value of 20 to 10.  Since the user wants the edit to appear in the database, he again right clicks and saves the question back to the database.

Now that his questions are created, the user wants to add a bit of text to the first question to reference an in-class joke but doesn't want the text saved back into the database.  The user selects question one, clicks edit and makes the change.  He does NOT save the change back to the database.


yay
Figure 4 - Main view with empty database

The test meets the expectations of the user so he/she saves the test by clicking the Save to File button. This click brings up the user's standard save dialog as provided by the operating system. They navigate to their desired save folder and enter a filename for the test "test5". They then click save which performs the save to the file and closes the Save to File dialog. The user now closes the test generation interface by selecting the X in the upper right hand corner.

 

Prev: database change/printing | Next: impossible condition | Up: test generation | Top: index