Use case Tables :

3.1.1 Use case:1

Use Case-01: Login

Use Case ID UC-01

Use Case Name Login

Actors Voter/Candidates/Voter

Description: Voter and Candidate are two actors who can logged in by
their existing CNIC and Gmail verification pin on the device.

Pre-Conditions: 1. Working Internet.

2. User must open the E-Vote website.

Post conditions: User was logged in.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1. User clicks on the ”Login with Existing Google Account”
button to
2. User click on login with existing CNIC and verification pin
3. User successfully logged in

Exceptions: 1. Invalid Pin

2. Unstable Internet
3. Device Damaged
4. System under maintenance

Alternate Flow: There would be no alternative flow one user may have one
and only one account.

Secondary Actor: Admin

TABLE 3.1: Use Case-01: Login

Use Case-02: Cast Vote

Use Case ID UC-02

Use Case Name Cast Vote

Actors Voter

Description: Voter is actor who can cast vote once after logged in and after
selecting candidates.

Pre-Conditions: 1 User is eligible

2 User must log in

Post conditions: User selected the candidate to cast vote.

Priority: Essential

Frequency of Use: Very High

Basic Flow: 1 User check its information either it is correct or not

2 User check it UC and respective candidates
3 User Cast Vote according to his/her choice

Exceptions: 1 The information is wrong of the user

2 All relevant candidates do not exist
3 Due to internet connection candidates doesn’t selected

Alternate Flow: The user send mail with its official email address registered
in election commission and ask them to cast his vote.

Secondary Actor: None

TABLE 3.2: Use Case-02: Cast Vote

Use Case-03: Check Results

Use Case ID UC-03

Use Case Name Check Results

Actors Voter/candidate/Admin

Description: Voter, Candidate and Admin are actors who can check results
once after result declared after ending time of the voting.

Pre-Conditions: 1 User is eligible

2 User must log in

Post conditions: User selected the result button to check results.

Priority: Essential

Frequency of Use: Very High

Basic Flow: 1 User login into the website

2 Click the result button
3 After viewing the result get log out

Exceptions: 1 The Results are late

2 Election should be conducted again for particular UC
3 Result would not be displayed for particular user due to
some security reasons

Alternate Flow: The user asks verbally other users of same UC’s to ask the
final result after announcement.

Secondary Actor: Admin

TABLE 3.3: Use Case-03: Check Results

Use Case-04: Manage Notification

Use Case ID UC-04

Use Case Name Manage Notification

Actors Admin

Description: Admin is actor who can notify the new important

notifications
time to time for inconvenience of user.
Pre-Conditions: 1 The admin has new information relevant to user interest.
which was not shared until now with user 2 Information should
not cause of squabble

Post conditions: The nonfictions.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 Admin issues the notifications.

2 Admin verify is nonfictions is issued?
3 Updated notification if there is ambiguity found later on.

Exceptions: 1 The admin Issued notifications but not uploaded due to

server site maintenance.
2 Bad quality of internet
3 Heavy traffic on website

Alternate Flow: The admin notifies the public and nominates by using public
resources(means) like media or newspapers.

Secondary Actor: None

TABLE 3.4: Use Case-04:Manage Notification

Use Case-05: View Candidate

Use Case ID UC-05

Use Case Name View Candidate

Actors Voter

Description: Voter is actor who can confirm that has applicable candidate
for his UC. By seeing complete information of candidate.

Pre-Conditions: 1 Login into website.

2 Click on Candidate.

Post conditions: User selected the candidate to cast vote and check status after
casting the vote.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 Evenhanded login to the website.

2 Examine candidate and its status.

Exceptions: 1 The candidate doesn’t exist.

2 Irrelevant candidate is showing to the voter.

Alternate Flow: The user send mail with its official email address registered
in election commission and ask them to cast his vote.

Secondary Actor: None

TABLE 3.5: Use Case-05: View Candidate

Use Case-06: Check Vote

Use Case ID UC-06

Use Case Name Check Vote

Actors Voter, Candidates

Description: Voter is actor who can cast vote once after logged in and after
selecting candidates.

Pre-Conditions: 1 User is logged in1 User is eligible.

2 User must log in.

Post conditions: Check either vote is casted successfully with in the time or
not.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 User cast the vote.

2 Check the status.
3 Logout.

Exceptions: 1 User cast the vote but not submitted at server end.
2 Candidate is removed after vote casted due to some reasons.

Alternate Flow: The user asks Management to verify either vote is casted or
not.

Secondary Actor: Admin

TABLE 3.6: Use Case-06:Check Vote

Use Case-07: Manage Voters

Use Case ID UC-07

Use Case Name Manage Voters

Actors Admin

Description: Admin is actor who can add or remove the voters from the
data base..

Pre-Conditions: 1 Admin must login.

2 Admin checks the details of the voter before doing any op-
eration on it.

Post conditions: Must verify the work had done which want to be done.

Priority: Essential

Frequency of Use: High

Basic Flow: 1 The admin checks the credentials of the voters or not.
2 If exist what would be done? And if does not exist what
should be do?
3 Fixes the operation and verify that work is done or not still?

Exceptions: 1 The system is crash.

2 The Admin forgot the actual operation and did the wrong
work.
3 The information is understandable of the user.

Alternate Flow: The admin puts request user to send his / her information
and
manage again if to be added and just deleted after matching
the credentials whatever the data is saved against that voter.
Secondary Actor: None

TABLE 3.7: Use Case-07: Manage Voters

Use Case-08: Manage Candidates

Use Case ID UC-08

Use Case Name Manage Candidates

Actors Admin

Description: Admin is actor who can add, edit or delete particular can-
didates. Check their portfolio and send notification if any
needed. Only Admin can assign parties to candidates.

Pre-Conditions: 1 Admin can access the candidates’ section of the website.

2 Admin check the data of that particular candidate is exist
or not.

Post conditions: Make sure that data is being manipulated if any operation
may do on it.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 Go to the specific section of the website.

2 Consider the particular data of the candidate if is okay check
data already exist if so.
3 Do the operation needed on data.

Exceptions: 1 Website not show data of user although it is present in data

base for certain user.
2 By submission of form, it gives fault of data redundancy
although that would not be acceptable for that user because
that user registering 1st time at that site.

Alternate Flow: Manually add data in the database.

Secondary Actor: None.

TABLE 3.8: Use Case-08: Manage Candidates

Use Case-09: View Candidate Profile

Use Case ID UC-09

Use Case Name View Candidate Profile

Actors Candidate, Voter

Description: The voter and candidate can check their profile(information)

at the 1st page after getting login.

Pre-Conditions: 1 User must register.

2 User login successfully.

Post conditions: If existing data is not accurately asking the admin to correct
it.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 User login.

2 Check his/her portfolio before casting the vote.

Exceptions: 1 Even after getting register user not found his data on that
page.
2 User found data of someone unknow person on his profile.
3 Due to ambiguation system data changed its form.

Alternate Flow: None

Secondary Actor: None

TABLE 3.9: Use Case-09: View Candidate Profile

Use Case-10: Manage Parties

Use Case ID UC-10

Use Case Name Manage Parties

Actors Admin

Description: Only admin can assign the parties according to the candi-
dates. Each candidate must be a member of some party.

Pre-Conditions: 1 Admin has complete details of candidate and clear informa-

tion of candidate with which party he/she want to
contribute. 2 Confirm the party takes part in the election in
that year.
Post conditions: After assigning the party to the candidate. Notify the candi-
date, through any considerable source.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 Choose the candidate party form the drop-down menu while
adding the information of the candidate.
2 If the candidate wants to be elected not through any party
the independent candidate option is to be selected.

Exceptions: 1 Choose the candidate party form the drop-down menu while
adding the information of the candidate. 2 If the candidate
wants to be elected not through any party the independent
candidate option is to be selected.

Alternate Flow: None

Secondary Actor: None

TABLE 3.10: Use Case-10: Manage Parties

Use Case-11: Manage Results

Use Case ID UC-11

Use Case Name Manage Results

Actors Admin

Description: The declaring and showing result privileges are only guaran-
teed to the admin.

Pre-Conditions: 1 The voter cast the vote.

2 There are candidates who can be nominated.
3 The voting time get out.

Post conditions: Result must be shown to all user i.e., Voters and candidates.

Priority: Essential

Frequency of Use: Very High

Basic Flow: 1 Admin determine the highest number of votes in each UC’s
separately.
2 Update result of table of the database.
3 Issues notifications on public side.

Exceptions: The all-vote information lost due to data base crash.

Alternate Flow: The result should announce by notifications and sending

emails to every candidate and announce through electronic
media and print media.

Secondary Actor: None

TABLE 3.11: Use Case-11: Manage Results

Use Case-12: Password Change

Use Case ID UC-12

Use Case Name Password Change

Actors Voter

Description: User change password any time if he/she want to change for
being the security reasons or some other reasons.

Pre-Conditions: 1 The user is register on that website.

2 User know her previous password.
3 User is not restricted by the admin not to change the
password.

Post conditions: User check the new password after logging in again.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 After logged in go to the change password tab.

2 Write old password and then new password after that write
new password again.
3 Click on confirm button.

Exceptions: 1 The admin restricts the user to change password on their

own due to any reasons.
2 Password does not change because user try some wrong
method to do so.

Alternate Flow: The user request to admin to change his password and let
him/her with new password through some secure authenti-
cated source.

Secondary Actor: Admin

TABLE 3.12: Use Case-12: Password Change

Use Case-13: Password Change

Use Case ID UC-13

Use Case Name Add Areas

Actors Admin

Description: Admin can add new area in the website selected by election
commission for the election and if need to remove some area
only admin can do so again.

Pre-Conditions: 1 Go to the add area button.

2 Check the area is already added or not

Post conditions: After adding the area make sure that it is showing to all user
candidates and voter too.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 The admin logged in and go to the new area button to area
comprise section.
2 Add information of that area.
3 Click submit button to add in data base.

Exceptions: 1 The system does not work properly for the time being due
to multiple admin panel using area for the same work.
2 After submission of from the area does not saved.
3 After submission button the whole form data removed im-
mediately due to some errors in form filling.

Alternate Flow: Just put entry directly into the database of the website.

Secondary Actor: None

TABLE 3.13: Use Case-13: Password Change

Use Case-14: Logout

Use Case ID UC-14

Use Case Name Logout

Actors Voter, Candidate, Admin

Description: Voter, Candidate and Admin are actors who can use website
and doing their respective work according to their nature of
work they logged out accounts from site.

Pre-Conditions: 1 Account exists

2 User login

Post conditions: Check also he/she logout or not.

Priority: Essential

Frequency of Use: Normal

Basic Flow: 1 After doing respective work user click logout button
2 Confirm the logout button to logged out.
3 Close the window if user wants.

Exceptions: 1 The account automatically logged out without any warning.

2 After logout he/she can still stay logged in.

Alternate Flow: After the specific time period of logging in the account may
logged out automatically due to no more interacting with of
user with the website.

Secondary Actor: None

TABLE 3.14: Use Case-14: Logout

References 91