User Stories
From reCHOIRed software
1. Users can log into the site by type of user. Features of the site will be available based on this type.
Estimated effort: 2 hours Priority Rating: 1 Completion Status: Complete
2. Administrators can set up accounts for participating schools. The system will automatically email the school a temporary password for the account.
Estimated effort: 6 hours Priority Rating: 1 Completion Status: Complete
3. Users can change their password. If they cannot remember their password, they can retrieve it by email.
Estimated effort: 3 hours Priority Rating: 4 Completion Status: Complete
4. A “God-user” account can create new administrator accounts. This will allow new staff members to be added to the system.
Estimated effort: 5 hours Priority Rating: 3 Completion Status: Complete
5. Users can update their profile information. Profiles will contain two email fields. Information in the profile should be based on the type of user.
Estimated effort: 8 hours Priority Rating: 1 Completion Status: Complete
6. Workers can sign up for an account. Required information includes name, email and phone number. There is no verification required.
Estimated effort: 5 hours Priority Rating: 2 Completion Status: Complete
7. Registered workers can sign up for a shift. The shift will then be unavailable for anyone else to choose.
Estimated effort: 7 hours Priority Rating: 1 Completion Status: Complete
8. Schools can submit their repertoire for the festival. Administrators will be notified when a school submits their repertoire.
Estimated effort: 8 hours Priority Rating: 1 Completion Status: Complete
9. Administrators can generate name tags for the workers. A name tag file will be generated from the list of users that have signed up for work. The generated file will then be used in conjunction with Microsoft Office in a merge operation to create these name tag labels.
Estimated effort: 3 hours Priority Rating: 1 Completion Status: Complete
10. Administrators can update available jobs and their associated job descriptions. In the event of a description changing, the administrator can go in and update the information to give users an idea of what they are signing up for.
Estimated effort: 5 hours Priority Rating: 2 Completion Status: Complete
11. Administrators can create new job positions and their associated job descriptions. When a new position opens up, administrators would want users to be able to sign up.
Estimated effort: 5 hours Priority Rating: 2 Completion Status: Complete
12. Administrators can update the festival schedule (school-specific and festival). As school information is received, the schedule may change to accommodate various preferences of performance times. A list of festival functions and school-specific schedules would be available to change.
Estimated effort: 8 hours Priority Rating: 1 Completion Status: Complete
13. A user views a static page, such as “Festival History”. A user is interested in the history of the festival and so he or she views the history page.
Estimated effort: 2 hours Priority Rating: 4 Completion Status: Complete
14. A school preorders shirts. The school selects the quantity and sizes. A message is sent to the administrators notifying them of the preorders.
Estimated effort: 10 hours Priority Rating: 4 Completion Status: Complete
15. Administrator views the details of a school. Needing contact information on a specific school, the administrator views the profile for a school. This page contains all the information needed, at a glance, about the school.
Estimated effort: 3 hours Priority Rating: 1 Completion Status: Complete
16. School views festival schedule. The school may select from either a daily events schedule or a school-specific schedule. The results would be displayed appropriately.
Estimated effort: 6 hours Priority Rating: 3 Completion Status: Complete
17. After receiving an invitation to the choral festival, a school user will need to submit detailed information for their school via the online application. To do this, the user must login with the credentials included in their invitation. If they have not submitted registration details, they will be required to fill out some information to give their account information necessary for their online profile to be useful. After submitting their information, they will have full use of their account.
Estimated effort: 8 hours Priority Rating: 1 Completion Status: Complete
18. An administrator may need to upload pictures that depict any number of aspects of the festival for public viewing on the website. The administrative user must login, and then navigate to the picture uploading section of the website. Once there, the user may browse to the proper file, and upload it. Once uploaded, the photo will be publicly viewable by all users of the website.
Estimated effort: 6 hours Priority Rating: 4 Completion Status: Complete
19. An administrative user may need to generate labels for a CD label for any choir’s performance. The administrative user must login, and then choose to generate an appropriate file for this operation. The generated file will then be used in conjunction with Microsoft Office in a merge operation to create these CD labels.
Estimated effort: 2 hours Priority Rating: 3 Completion Status: Complete
20. An administrative user may need to generate address labels for a mailing needing to be sent to any choir. The administrative user must login, and then choose to generate an appropriate file for this operation. The generated file will then be used in conjunction with Microsoft Office in a merge operation to create these address labels.
Estimated effort: 2 hours Priority Rating: 1 Completion Status: Complete
21. A school user will need to evaluate the choral festival after their attendance, and will be asked to do so within some pre-determined time frame after the festival. To do this, they will need to login to their account, and navigate to the evaluation page. Once there, they will fill out some evaluation information. When they are done, they will submit their evaluation.
Estimated effort: 6 hours Priority Rating: 3 Completion Status: Incomplete
22. An administrative user may need to update the information contained on any of the web application’s pages containing nothing other than a few paragraphs of text that may need to be updated on a yearly basis. The administrative user must login, and then choose the specific page on which they would like to modify information. They are then brought to an edit page where changes can be made. Once finished, the administrative user must save their work.
Estimated effort: 3.5 hours Priority Rating: 1 Completion Status: Complete
23. An administrative user may need to communicate with a school user, or a school user may need to communicate with an administrative user. In this situation, either user type must login, and then navigate to their messages. Once there, they may add a new note that will be visible to the administrator, or the school user, whomever the note is intended for. All previous messages will be visible by both users so the entire context of all communications between the two users will be entirely clear.
Estimated effort: 8 hours Priority Rating: 3 Completion Status: Complete
