marcodlk / ics491_timesheet Goto Github PK

May be a cleaner/better design approach. The class would also be able to handle all validation and sanitation of requests.

This class should at least contain a function that calculates total hours a given user has worked. It will request the necessary rows from the database given an id/username in order to gather all relevant timed sessions and make necessary calculations.

Self-explanatory... I made a Token class that holds username, id, and privilegeLevel variables. The login class should create a Token with the given variables and pass it along to the UserInterface class which will then operate according to the variables in the Token, most importantly the privilegeLevel.
That's my take on it anyway... let me know if you don't like the idea or have a better suggestion.

The class must implement functions that add/delete/modify user records to the database. These records include information such as username, id, real name, hourly salary, social security number (irrelevant but sensitive information to make a point about security).

The PunchClock class handles the checking in and out of the user. It will get the checkin/checkout times and date via some trigger and send to the database to be recorded.
I think the best way to approach this is to use the Observer design pattern. This class would be the observer and the UserInterface class would be the subject. Read more here: http://www.journaldev.com/1739/observer-design-pattern-in-java