3. Non-Functional Requirements

3.1. Performance

 

All Grader tool functionalities must execute instantaneously except for the following:

 

  • The hand-in functionality must be in matter of seconds.
  • The synchronize functionality must be in matter of minutes.
  • The submit grades functionality must be in matter of minutes.

 

The above listed exceptions may delay for an extended amount of time due to network delays.

 

The maximum expected size of the Grader tool data is as follows:

 

  • Classes: up to tens of classes.
  • Students: up to hundreds of students per class.
  • Item: up to hundreds of items per class.

 

The Grader tool must be able to operate with Classes containing more Item and Students entry than expected.  However, the grader tool need not meet the previously stated speed performance requirements.

 

 

3.2. Operational Environment

 

The Grader tool need only to function as specified in a California Polytechnic State University: San Luis Obispo academia environment.

 

 

3.3. General Characteristics

 

3.3.1. Security and Privacy

 

Only instructors, teacher’s assistants, and the current student may view the student ID and the name of the current student.  No user may view or alter the login or password for another user.

 

3.3.2 Simplicity versus Power

 

On a spectrum of simple-to-use versus powerful, the Grader Tool is slighty on the side of simplicity.  Users are assumed to be capable of opening, managing, and editing office documents such as Microsoft Excel and Word.

 

 

3.4. Process-Related Non-Functional Requirements

 

3.4.1 System Delivery and Installation

 

The Grader tool will be delivered as a downloadable executable which will install the program onto the user’s computer.

 

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