Voters application

UC1: Make a vote

• Primary Actor: Voter
• Stakeholders:
  • Organizer wish to have smooth voting process
  • Instructor wish to encourage participation
• Precondition: Voter has identified
• Postcondition: Vote is saved in the system
• Main Scenario:
  1. Voter see a list of groups
  2. Voter select a group
  3. Voter see project description and voting categories
  4. Voter enter their vote
  5. System save the vote and indicate success
• Alternate flow:
  • When vote cannot be saved (eg. due to internet failure) system show failure message and remove vote.

UC2: Edit a vote

Voter open the application, select a group they wish to change the vote and go to the voting form. They see their latest scores. They make their adjustments and system will show that the voting has been registered.

UC3: View vote time left

Voter open application. In addition to the list of groups they will see a message indicating the vote closing time.

UC4: Scan from booth

Voter visits the group's booth. They use their device to detect from a physical object located at the booth and the application will show up with that group's information same as when they have manually select that group.

UC5: View list of groups that have been voted

Voter open application. In the list of groups there will be a visual indicator that that group has been voted. If a group is partially voted (the vote was filled in but not for all categories) it is displayed same as non-voted group.

UC6: Vote closed

Voter open application after system administrator has closed voting. They will see a list of groups and they can select a group to view the group's information but there is no voting form.

UC7: Installing a product

Voter open application and select a group from the list of group. The group information shows and user can opt to install that product. If that product is not supported on their device (for example, if they use an iPhone and the product is an Android application, or if their phone runs an ancient version of Android) there should be a visual indicator telling them that installation is not supported on their device and the reason why.

UC8: Authentication by KU student/staff

Voter who has a KU account opens the application and verify their KU account. Application checks with the KU system and logs the user in with access permissions set according to their status in KU. The application should greets the voter by his name.

UC9: Authentication by non-KU student

Voter who are student but aren't KU student opens the application and choose voting for non-KU student. Voter enters login details given by the system administrator. Application logs them in.

UC10: Authentication by guest

Guest opens the application. Application presents a number. Guest tells the number to the system administrator. The system administrator links the number and the guest's name and organization. Guest select the number and the application logs them in. The application should greets them by their name.

Group

UC1: Enter group information

Group member receive login information from the system administrator. He uses that information and is presented by a form. He enters his data into the form and save it. The system updates that information and next time voter open the group's page they will see the new data.

Backoffice

Assume that the administrator is authenticated

UC1: Configuration

Administrator indicates the intention to configure the system. System presents a list of configurable parameters. Administrator makes some adjustments and indicate the system to save.

UC2: Add project

Administrator indicates the intention to setup projects. System presents a list of projects. Administrator choose add project and enter the project name, the account of the project members. Administrator then tell the group to enter the website and enter their information. (See Group UC1)

UC3: Edit project

Administrator indicates the intention to setup projects. System presents a list of projects. Administrator chooses one and the system present similar form to group's editing form but it also can add/remove project members. Administrator make changes and indicate system to save.

UC4: View vote result

• Primary Actor: Organizer and Instructor ("Administrator")
• Stakeholders:
  • Voter wish to see the result quickly after voting time has ended
• Precondition: Organizer has identified
• Main Scenario:
  1. Administrator view voting result
  2. System present list of projects and their score in every categories.

UC5: Close voting

Administrator indicates the intention to configure the system. System presents a list of configurable parameters. Administrator unset voting allowed and save.