This document describes several use cases for a social networking application for insurance agents: 1) Authentication - Allows users to log in by checking username and password against a database. 2) Registering Agents - Administrator registers new users by assigning them a username and randomly generated password. 3) Banning Posts - Administrator can remove irrelevant or obscene posts from the portal. 4) Most Valuable Agent - Administrator determines the highest rated agent based on ratings of their posts. 5) Checking Inactive Agents - Administrator can identify and notify agents who have not posted for a certain time period (e.g. 30 days) and remove their account details from the database.

1. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
DOCUMENTATION FOR USE-CASE DIAGRAM

2. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-AUTHENTICATION
BREIF DESCRIPTION:-
This use case is to provide a secure mechanism of users logging in into the portal; it will
allow only the registered users to sign in into the portal by checking in their details with
the requisite database.
ACTORS INVOLVED:-
1. Questioner
2. Answerer
3. Administrator
PRE CONDITION:-
1. The particular ACTOR must have a user name and password.
BASIC FLOW OF EVENTS:-
1. The use case begins when the actor selects the login screen from the home page.
2. The actor enters the details i.e. username and password.
3. The application checks for the correctness of username and password from the
requisite database.
4. The use case ends.
ALTERNATE FLOW OF EVENTS:-
1. If in step3 of the basic flow the application confirms a valid actor.
Then allows the actor to navigate to the next page.
Or
The application responds with a error message to the actor.
PRE CONDITION:-

3. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-REGISTRING AGENTS
BREIF DESCRIPTION:-
This use case is to provide a mechanism for the administrator to provide authentication
for new users who wants to register to the web portal. Administrator provides a password
with a particular username the new user has desired.
ACTORS INVOLVED:-
1. New User
2. Administrator
PRE CONDITION:-
1. The Administrator must be complete the authentication use case.
2. The new user must provide all the details
BASIC FLOW OF EVENTS:-
1. The use case begins when the new user selects the register button from the login
screen.
2. The new user fills in all the details.
3. The application checks in all the details
4. The use case ends.
ALTERNATE FLOW OF EVENTS:-
1. If in step3 of the basic flow the application checks all the details of the New user
if found valid then.
Application generates a password and the new user is alerted with the
confirmation through the administrator.
Or
The application responds with a error message to the administrator and
new user is not registered.
POST CONDITION:-
1. The application adds a new user to the portal

4. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-BANNING POST
BREIF DESCRIPTION:-
This use case is to provide a mechanism for the administrator to remove a particular
irrelevant or obscene post(question or answers) from the poartal
ACTORS INVOLVED:-
2. Administrator
PRE CONDITION:-
1. The Administrator must be complete the authentication use case.
2. There must be an actor completing the post use case
BASIC FLOW OF EVENTS:-
1. The use case begins when the administrator checking for the relevance of the post
manually.
2. If found irrelevant the administrator select the BAN option along the post.
3. The particular post is removed
4. The use case ends
ALTERNATE FLOW OF EVENTS:-
Not Applicable
POST CONDITION:-
1. The application generates a warning to the initiator of the post.

5. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-MOST VALUABLE AGENT
BREIF DESCRIPTION:-
This use case is to provide a mechanism for the administrator to judge the most valuable
agent among all the registered agents. The process is carried forward on the basis of the
ratings of post given to the all the agent’s posts.
ACTORS INVOLVED:-
1. Administrator
PRE CONDITION:-
1. The Administrator must be complete the authentication use case.
BASIC FLOW OF EVENTS:-
2. The use case begins when the administrator selects the option for the best agent.
3. The application sums up the rating of all the posts for all the agents
4. The application selects the agents with the highest rating value.
5. The particular agent is addressed by the administrator.
ALTERNATE FLOW OF EVENTS:-
NOT APPLICABLE
POST CONDITION:-
1. The application generates congratulatory message to the best agent adjudjed.

6. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-CHECK FOR INACTIVE AGENTS
BREIF DESCRIPTION:-
This use case is to provide a mechanism for the administrator to check for agents who
have not posted anything for particular time span and disallow them from taking any
further part in the portal activity.
ACTORS INVOLVED:-
1. Administrator
PRE CONDITION:-
1. The Administrator must be complete the authentication use case.
2. The agents in check should be at least 30 days old subscriber.
BASIC FLOW OF EVENTS:-
1. The use case begins when the new administrator selects the inactive agent button
2. The application checks the last posted dated for all the registered users who are 30
days old subscriber.
3. The application generates the list of all the users who have not posted for the
particular time span.
4. The particular agents are notified by the administrator.
5. The use case ends.
ALTERNATE FLOW OF EVENTS:-
NOT APPLICABLE
POST CONDITION:-
1. The application removes all the details of the inactive agents from the database.
2. The agents creditability as a valid user is removed.

7. SOCIAL NETWORKING APPLICATION FOR
INSURANCE AGENTS
USE CASE:-CHECK FOR INACTIVE AGENTS
BREIF DESCRIPTION:-
This use case is to provide a mechanism for the administrator to check for agents who
have not posted anything for particular time span and disallow them from taking any
further part in the portal activity.
ACTORS INVOLVED:-
1. Administrator
PRE CONDITION:-
1. The Administrator must be complete the authentication use case.
2. The agents in check should be at least 30 days old subscriber.
BASIC FLOW OF EVENTS:-
1. The use case begins when the new administrator selects the inactive agent button
2. The application checks the last posted dated for all the registered users who are 30
days old subscriber.
3. The application generates the list of all the users who have not posted for the
particular time span.
4. The particular agents are notified by the administrator.
5. The use case ends.
ALTERNATE FLOW OF EVENTS:-
NOT APPLICABLE
POST CONDITION:-
1. The application removes all the details of the inactive agents from the database.
2. The agents creditability as a valid user is removed.