DRAFT: This module has unpublished changes.

Feature List:

  1. How to register to vote and when are the deadlines
  2. What documentation needs to be brought with the student to the ballot box
  3. Where the student can vote (if on campus or in another location)
  4. Directions showing the student how to get to the voting booth
  5. Information on the candidates running for office such as what they stand for, what they are against, and links to further information
  6. Information on any referendums and what they mean

 

Identification: This use case covers the entire feature list because very little changes between the seven features in terms of Primary Actor, Stakeholders/Interests, Pre/Post conditions.

 

Primary Actor: The primary actor is the college student using our application.

 

Stakeholders and Interests: The primary stakeholder in the use of all of our features is the College Student because they are the ones that will use the app to vote. Candidates running for office and society in general are also stakeholders. Candidates might be dependent on students voting for them, or counting on students not voting in order to get into office. Thus, candidates might have either be interested in students not voting and for this application to not succeed, or the other way around. In addition, general society is a stakeholder because whether more students vote or not will impact the types of politicians in government and thereby future policy. So general society, just like candidates running for office, will have a mixed interest in whether students vote or not.

 

Preconditions:

Use Case 1,2,3,5,6: The user will need to input into the application the state and county where he/she is trying vote.

Use Case 4: The user will need to have used feature #3 / completed Use Case 3 before finding directions to where he can vote.

 

Postconditions:

Use Case 1-6: The user see’s the information described in the feature list. The state of the system has not changed.

 

Main Success Scenario:

     Use Cases 1-6:

  1. Upon opening the application, the user inputs the state and county where he wants to vote.
  2. He then taps on the button on the next (home/menu) page entitled “why vote” to read about the benefits of voting.
  3. Back on the home page, the user can click on the "How to Vote" button and find out what is required to vote.
  4. When the user is ready to find out what they cab vote on, the user can click othe "Who/What I Can Vote On" button and from there the user can look through the different candidates. After the user is done looking at the candidates from that same page he can click on the "refferendum" button to seee the different refferendums up in that election.
  5. After the user has determined what they want to vote on, they can now find out when to vote by  clicking the button "When To Vote" which is on the main menu/home page.
  6. Finally when the user is completely prepared to vote, the user can find out the location of his polling place by clicking on the "Where to vote" button and following the instructions posted.

Extensions and Alternative Flows:

1-3.  This information will be hardcoded into the app so if something goes wrong here, it means that the app is not installed correctly and nothing else will work.

4.     The database will be updated in the case of any changes in candidates or their information

5. This infromation is also hardcoded.

6.  The user's phone might not allow applications to access GPS data. We cannot do anything about that but atleast the user will have the address of their voting location.

 

Open Issues:

Some counties might not allow people to find out the location of their polling places online. Also, some counties might use other voting systems than the ones listed in our app.

DRAFT: This module has unpublished changes.