3. Non-Functional Requirements

There are a few requirements that while not part of the tool are important to the operation of the tool

3.1. System Performance

The majority of the operations should be very fast. Many database operations should operate on the order of minutes regardless of the size of the database all of which should be instantaneous to the user. The schedule operation on the other hand is much more complex and may take on the order of hours. This however is completely acceptable because doing this by hand takes on the order of weeks so this new system will be much more efficient. The size constraints should not be extreme. On a standard desktop, there should be enough storage space to save all of the system information, including the multiple databases.

3.2. Qualitative System Characteristics

This program is able to run on any current computer. We had a Pentium 2 or 3 in mind with a clock speed of around 400MHz. This program will not require an exorbitant amount of RAM or hard disk space however there should be sufficient amounts of both. There should be an Internet connection to some central place where the databases are located and in designing this system we had a LAN server in mind; however, this is not necessary. The schedule operation will take a few hours to complete and the faster the system the less amount of time this will take, but this program should run on any current computer.


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