1 2 3 4 5 6
Page 4. The Assessment Page
Now that you know what to do, how do you know if you've done it well? Understand that you will be evaluated based on the quality of the database created. If it works correctly, if it looks good and is easy to use, and if it has enough records to be a usable database, you will have created a quality database. I will sit behind your teams' computer and enter data into your form, and evaluate the results in by viewing the report generated. Please take a gander over the assessment rubric below to learn more about what is expected of this project. |
| Best Work |
Good Work |
Acceptable Work |
Unacceptable Work |
Category |
| The form for data entry should be easy to understand at a glance, and should provide clear instructions to guide the user to use it. It should also be graphically balanced and nice to look at. | It may take a moment to understand
what to do with the form at first glance, and you may have to read the whole
set of instructions to know how to use it. Graphically, it may look
disorganized, but everything is there and it works. |
You have to know how the form
will be used before the user starts. Instructions will be confusing.
Graphically, it looks rough, thrown together and not very professional.
It works, though. |
The form doesn't work. There
are either no instructions or the instructions are not helpful. Graphically
it looks amateurish, and thrown together without any thought. |
The Data Entry Form |
| There are three tables, with a
total of 60 cars at minimum. Each table has 6 fields and each has an
a validation rule and validation text that guides the user. All fields
have appropriate data types. |
There are three tables, but maybe
not the full 60 cars. There may be a field missing, or one that has
an inappropriate data type. One or two validation rules or texts may
be missing. |
Fewer than three tables, definitely
less than the necessary 60 cars. Missing or incomplete fields, with
inconsistencies between the tables. Validation rules are incorrect,
texts are not helpful and data types inconsistent. |
Only one table, with less than
60 cars. Fields are missing, and data incomplete. Validation rules are
missing, as are texts. Data types default to text. |
The
Tables of Data |
| Returns all field values as specified
by the user. The values returned are consistent with what the user wanted.
No error messages or blank fields from Access. |
Returns some field values, but
some may be missing. Values returned are generally consistent with what
the user had in mind. There may a an error message or a blank field. |
Field values are mostly not
returned. Values returned sometimes don't have anything to do with the
criteria the user entered. Error messages and blank fields are common. |
Field values are not returned,
or if so, none have any relevance to the user's criteria. Error messages
or blank fields are more common than not. |
The
Query |
| The report has a graphically pleasing
look in terms of balance, design and color. It explains to the user
the recommended vehicle and gives the criteria used to support its recommendation. |
The report has a mostly pleasing
look but may be unbalanced or use contrasting colors. The data returned
to the user may be incomplete or difficult to understand. |
The report looks amateurish, exhibiting
poor design. The criteria returned and the explanation written to the
user are largely incomplete and difficult to understand. |
The report has serious errors
in design, and returns no usable information to the user. |
The
Report |
Click Here to go to the Next Page!