The non-functional requirements for the TestTool are organized into the following categories:
3.1 System-Related Non-Functional Requirements
The TestTool system needs to conform to the following non-functional requirements:
a. Performance:
Time: All of our procedures will happen instantly except for the test generation. Test generation can occur on the order of minutes. Also, the time it takes to hand in the tests is subject to network delays.
Space: Tests generated should be about the size of the raw text that they hold, plus the size of any pictures. The database will have no limits on the size that it can grow to, though extremely large databases could slow down the system.
b. Operational Environment:
The TestTool system is multi-platform. It covers all the basic three operating systems: Linux, Windows, and Mac OS X.
c. General Characteristics:
Security: Version 1.0 of the TestTool has a login screen only for the student home version. The instructor and proctor have no log in. This isn’t too much of a concern because all saved tests will be stored either on a local disk, or on the instructor's network drive; both of which it is the owner’s job to keep secure.
Privacy: The TestTool system does not specify any privacy. Again, it is the instructor’s job to keep the files stored on their computer private.
Reliability: The TestTool must be reliable for it to be useful.
3.2 Process-Related Non-Functional Requirements
a. Development Time:
Development of the functional prototype will take eleven weeks, and will take place during Winter Quarter 2007.
b. Development Cost:
We do not project any costs for the development of this software.
c. System Delivery:
The system will be delivered on a CD when it is complete. This will allow the user to install the software on their workstation or home computer.
d. Installation:
The delivered CD will run an installation wizard to install the software onto Windows. Linux and Mac OS versions will be installed as executable files.
e. Marketing:
As this software is being developed by students for the Computer Science Department, it will be provided for free to anyone in the department who wishes to use it.
3.3 Personnel-Related Non-Functional Requirements
Developers of the TestTool system should be relatively skilled programmers. They are not required to have any credentials, but they should be hard workers and good problem solvers.
On the student end of the functionality, the software should be basic enough for users of any skill level. The teacher interface is slightly more complex, but still should be usable for users of relatively low skill levels.