3.2 General Characteristics

3.2.1. Security and Privacy

All operations check for user's rights to perform the selected action. If a user does not have rights to execute said action, the action should never execute for that user. User rights are initially established by administrators with the rights to adjust other user's rights.

Passwords for users on this system need to be kept secure from viewing or modification by any other user. Personal data kept about users should also remain private from users who do not have the rights to view said information.

3.2.2. Simplicity versus Power

On a spectrum of simple-to-use versus powerful, the Scheduler is medium to high on the side of powerful. Users are checked for improper data entry and the screens are fairly intuitive but there are a fair number of items that are highly dependent on each other, changing one will cascade changes to several other items, possibly causing problems with scheduling.





Prev: Performance | Next: None | Up: Non-Functional Requirements | Top: index