System Requirements Presentation Luke Skon, Trenton Fitzgerald Printer Control System Requirements Presentation Luke Skon, Trenton Fitzgerald

Functional Requirements It must contain a database that keeps track of the resources the users print The database should be integrated into the current one It should include two new tables, Student and Printer The database should use SQL

Database Diagram

Functional Requirements It must not let users print more resources than they've been allocated. If the database reads that they've gone over their paper quota, don't print Should notify user that their printing attempt failed, and why For security reasons, this requirement should take precedence.

Functional Requirements It must let users print resources that they have been allocated, if possible. If a user's database entry does not state that they used too much resources, let them print “Not possible” when the user queues up a job that goes over their limit. If the server is down and the reason is unknown, then do not print, so that the system cannot be taken advantage of.

Functional Requirements It should be possible to view database information at any given time. Database viewing software, already implemented Create new accounts for printing admins, give them permissions over the resource columns and the printer job and printer tables. Server should be left running It must be possible to view the printers' operational status.

Operational Requirements Ought to accommodate the entirety of Sacred Heart High school students Teachers College students System Administrators Other stadd

Operational Requirements Ought to be nearing completion before the end of the semester System should be mostly implemented by then Server up and running Database modifications should be complete Alberto will take over after Luke's departure