3. Non-Functional Requirements

3.1. Performance

All score entering and editing, calculations, administrative commands, and options commands must execute instantaneously, except for the following:

In general, the performance of the Grader Tool commands that must access data across a network is subject to potential network delays. The Grader Tool must transmit data as fast as is possible on any given network, but delays due to external network circumstances are beyond the control of the Grader Tool.

There are no specific requirements for the allowable size of a grade spreadsheet in terms of the number of students or graded items. A grade spreadsheet on the order of thousands of items is the maximum expected size during normal use.

The maximum expected sizes of the Grader Tool databases are the following:

The Grader Tool must be able to operate with grader spreadsheets and databases of sizes larger than these normal maximums. However, the tool need not the meet the previously-enumerated time performance requirements for grader spreadsheets or databases larger than normal maximum sizes.

3.2. General Characteristics

3.2.1. Security and Privacy

Students viewing class data must be able to only know what their data is. Professor and TA accounts must be the only accounts able to publish grades to the server, and professor accounts must be the only accounts able to submit grades to the SIS server. Professor accounts must also be the only accounts able to import rosters from the SIS server. Passwords used for the central server must be kept secure from viewing or modification by any other Grader Tool user, and from any user at all on the central server.

3.2.2. Simplicity versus Power

On a spectrum of simple-to-use versus powerful, the Grader Tool is heavily on the side of powerful. Users are assumed to be fully computer literate and knowledgeable on the use of computer networks consisting of local computers and central data servers.




Prev: functional | Next: developer-overview | Up: index | Top: index