E-Guard Diagrams Project

Use Cases:

This section shows the use cases and scenarios of the user features and system features. For more use cases, please see the documentation, here.

Parent Checks Activity

User and System Requirements:

User requirement:

The E-Guard shall allow parents to check web activity, keystroke, chat, email, IM and launched application.

System requirement:

1. The system shall keep a record of web activity of the child which a parent can access.

2. A report of all keystrokes shall be documented into the database.

3. All chat messages will be recorded and saved in the database for parental viewing.

4. Parents can check all IM a child has sent.

5. Emails will be copied into individuals reports for the parents to check.

6. A list of which application or software is launched will be tracked and listed into a document.

Scenarios:

The system shall keep a record of web activity of the child.

Name: Parent Check Web Activity

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child uses web activity.

Exit condition: Parent checks web activity.

Event Flow:

1. The child goes to website.

2. Recording Agent records the website URL and send it to the Database Management Agent.

3. The recording is saved in the database by the Database Management Agent.

4. The parent checks and view the recorded web activity from the Database Management Agent.

A report of all keystrokes shall be documented into the database.

Name: Parent Checks Keystrokes

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child types on keyboard.

Exit condition: Parent checks the keystrokes activity.

Event Flow:

1. The child types on the keyboard.

2. Recording Agent documents every key pressed and sends it to the Management Agent.

3. The document is stored in the database by the Database Management Agent.

4. The parent checks which keystroke where pressed by the child.

All chat messages will be recorded and saved in the database for parental viewing.

Name: Parent Checks Chat Messages

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child sends chat messages.

Exit condition: Parent view the sent child’s chat messages.

Event Flow:

1. The child sends chat messages.

2. The chat messages are tracked and copied by the Recording Agent and sent to the Management Agent.

3. The Database Management Agent saves the copied chat messages into the database.

4. The parent selects “Check Chat Messages”.

5. The Database Management pulls the requested files and sends it to the parent.

6. The parent views the child’s chat messages.

Parents can check all IM a child has sent.

Name: Parent Views IM.

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child sends an instant message.

Exit condition: Parent checks the instant messenger activity.

Event Flow:

1. The child sends an instant message.

2. Recording Agent identifies the sent instant message and sends a copy of the IM to the Database Manager Agent.

3. The Database Management Agent saves the copy to the database.

4. The parent clicks on “Check IM” and access the saved copy from delivered by the Database Management Agent.

Emails will be copied into individuals reports for the parents to check.

Name: Parent Checks Emails.

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child sends an email.

Exit condition: Parent checks the email activity.

Event Flow:

1. The child sends an email.

2. Recording Agent saves a report of the contents of the email and sends it to the Management Agent.

3. The report is stored in the database by the Database Management Agent.

4. The parent clicks on “Check Email”.

5. The Database Management Agent retrieves the email report and sends it to the parent.

6. The parent checks the email activity.

A list of which application or software is launched will be tracked and listed into a document.

Name: Parent Launched Software.

Participating actor: Recording Agent, Database Management Agent, Parent and Child

Entry condition: Child launch application.

Exit condition: Parent checks launched application.

Event Flow:

1. The child launches application.

2. Recording Agent documents the launched application and sends it to the Management Agent.

3. The document is stored in the database by the Database Management Agent.

4. The parent checks which application was launched by the child.

Class Diagrams

Class diagrams are used to show the different objects, operations, and attributes in a system. This diagram displays the software’s classes. We can see that the child and parent classes are specializations of the class user. Depending on the user, you can either enter websites or check websites and set allowed words. Each time a child is does an activity, their activities are recording and identified to check if the child is doing suspicious activities. If suspicious are identified, the parent will be notified.

Sequence Diagrams

Notify if suspicious website.

This diagram shows what happens if a child goes to an unhealthy website. When a child goes to the suspicious website, the recording agent saves the website URL, and the browser agent identifies the URL. If the URL is unhealthy, a notification is sent to the parent.

Name: Goes to flagged website

Participating actor: Child, Notification Agent, Browser Agent, Database Management Agent

Entry condition: Child goes on flagged website.

Exit condition: Notification Agent alerts parent of the activity.

Event Flow:

1. Child goes to flagged website on their device.

2. Browser agent retrieves the list of unhealthy websites from the Database Management Agent.

3. Recording agent records the activity and sends it to the notification agent.

4. The notification agent sends the activity, screenshot, time, and date to the parent.

Child Class State Diagram

This shows how the behavior of the class Child. The system allows that child to choose several activities. When a child chooses and activity, the events or functions in the class are triggered.

Activity Diagram

Notify if suspicious website.

The diagram below shows various paths that might occur when a process is executing. In this diagram, we require the child to enter an URL. The URL not only is recorded by the recording agent but also is processed by the browser agent. If the browser agent identifies that the URL is unhealthy, then the notification agent will alert the parents.

Video Presentation:

Documentation