rizowski / compulock Goto Github PK

Records the processes for the current user.

This was a question the instructor ended up asking and I didn't have an answer. This would be a good time to really understand how I am going to test Process, Program and History recording.

Answer:

Records programs running for the current user

The unit tests that are currently written don't actually test much. They need to be rewritten to better represent a Mock unit test:
http://msdn.microsoft.com/en-us/magazine/cc163904.aspx

Proper error handling for the requirements due for week 2

Can change the users password

Password changes and master passwords.

Proper error handling for Process, Program and history information gathering.

Database needs to be created for Project

The Gui doesn't update the changes to the account if it has been locked. This is essential because if the computer is left on and the account is available at the time. If time passes and the computer enters a time for the account not to be available this becomes problematic because now they can still login. The account is still there and the interface has not been disabled.

I have been going through a lot of my code. It needs some refactoring so that I can use it better when I get to passing around objects to and from the web service. Currently is is thrown together so that I have a bases of getting things to work.

I need to know the following things before my next check up:

• I need to know how REST works
• What kind of information and data models are needed for REST to work
• What kind of protocol REST uses.
  This list may increase as time goes past, as of right now, this is acceptable to learn.

http://msdn.microsoft.com/en-us/library/microsoft.win32.systemevents(v=vs.100).aspx
This should help with that

Database needs to have services created so that I can store information.

Unit Testing for Recording processes, programs and browser history.

Records history for
Chrome, Firefox and Internet Explorer
Preferably for the current user.

Have a TCP Proxy listener that handles all requests. This would secure that I know exactly what each browser visits. I wouldn't have to search for each history db either.

After a certain amount of time is passed the users password is changed to something else.