Functional

[Howie3426]

FR1. A-Z Search Bar
Goal: To provide the user with easier traversal of the website.
Stakeholders: Users
Description: After the user selects the category of their choice, the user will be sent to the organizations page. From here, the user will use the A-Z search bar to locate what organization they want to donate to. A failure case that might occur for this function is that the bar does not send the user to the right page regarding the letter they selected.
Origin: Meeting 2: Assessing how to make donating easier.
Version: 1.0
Date: 01/25/2020
Priority: 1

[Howie3426]

FR2. Contact Page
Goal: Enable the user to contact CharityBox
Stakeholders: Users and Organizations
Description: Users and organizations on CharityBox will have the resources provided to them in order to contact CharityBox if they have any problems. A failure case that might occur is that CharityBox contact information is wrong or is not in the right spot.
Origin: Meeting 2: Assessing the ability for customers to contact owners.
Version: 1.0
Date: 01/25/2020
Priority: 2

[Howie3426]

FR3. Verification Email
Goal: To provide the user with verification of their donation.
Stakeholders: Users
Description: Once the user donates and fills out the information form, the user will get emailed a verification message describing the products they have donated and to what company. A failure case that could occur is that the user never receives the email or gets a wrong email.
Origin: Meeting 2: Assessment of customer service.
Version: 1.0
Date: 01/25/2020
Priority: 2

[Howie3426]

FR4. Navigation from 'Categories' to 'Organization'
Goal: To provide easier navigation of the website.
Stakeholders: Users
Description: In order for the user to have ease when navigating and using the website, categories were implemented for donation. When attempting to donate, the user will go through a step-by-step process. The first step is to select a category (food, clothes, hygiene products, ...etc). Once completed, the user will be redirected to a new page with organizations listed. A failure case that might occur with this feature that might occur is that the navigation page takes the user to a different page then the organization page.
Origin: Meeting 2: Assessment on streamlining donations.
Version: 1.0
Date: 01/25/2020
Priority: 1

[Howie3426]

FR5. Navigation from ‘Donation’ to ‘Form’
Goal: To provide easier navigation of the website.
Stakeholders: Users
Description: Once the user has gone through the final step of the donation process, the user will be redirected to a new page where they can fill out their personal information. The form will require their personal information which includes: the user’s first and last name, email, and phone number. A failure case that might occur with this feature that might occur is that the donation page takes the user to a different page then the form.
Version: 1.0
Date: 01/25/2020
Priority: 1

[Howie3426]

FR6. News Page Redirect
Goal: To provide the user with news and information.
Stakeholders: Users
Description: When browsing the main page of the website, the aesthetically pleasing and relevant images contained within the image slideshow will offer the user the ability to directly access the news page. This would provide the user with more information about some of the current events that might be in desperate need of donations. A failure case that may arise is that the link provided to redirect to the news page breaks.
Origin: Meeting 2: Assessment of user’s ease of access when locating current events through the website.
Version: 1.0
Date: 01/26/2020
Priority: 3

[Howie3426]

FR7. List of Donation Items Needed By Organization
Goal: To provide the user with a more full donation experience.
Stakeholders: Users and Organization
Description: Provides the user with a comprehensive list of items that each organization is accepting donations for. After selecting a specific organization, the user will be redirected to a subpage that contains a list of organization-specific subcategories that the user can choose from, to continue on with their donation. A failure case that may arise is that the images of the donation items break or does not appear.
Origin: Meeting 2: Assessment of the donation system.
Version: 1.0
Date: 01/26/2020
Priority: 1

[Howie3426]

FR8. Ability To Share Donation Via Social Media
Goal: To increase user interaction and tie-in with the system.
Stakeholders: Users
Description: After completing a donation, we wish to provide the user with the ability to share their donation via one of our supported social media sites. We believe that this would help create a more interactive community within CharityBox and improve user retention for our service, while also simultaneously spreading the word about our system and its uses. A failure case that may arise is that the social media links break on the website.
Origin: Meeting 2: Assessment of user interaction with the system.
Version: 1.0
Date: 01/26/2020
Priority: 3

[Howie3426]

FR9. Validation of Participating Organizations
Goal: To provide CharityBox with more credibility.
Stakeholders: Organizations
Description: By providing an organization with an application form to fill out, we are ensuring that only legitimate organizations are participating in CharityBox’s service. This ensures the users of CharityBox that their donations are being received, as well as strengthening the business relationship between the organizations and CharityBox. A failure case that may arise is that the organization may not be able to access is the form on the website due to the link breaking. Also, another failure case may be that the form is unable to store the data.
Origin: Meeting 3: Assessing the legitimacy and security of the program.
Version: 1.0
Date: 01/26/2020
Priority: 2

[Howie3426]

FR10. FAQ Answer Page
Goal: To enhance the user experience and answer frequently asked questions
Stakeholders: Users
Description: By providing answers to users’ frequently asked questions, CharityBox looks to enhance the users’ navigation and experiences on the website, answer their most asked questions to help eliminate confusion, as well as maintain transparency. A failure case that may arise is that the links provided to help answer the user’s questions break.
Origin: Meeting 2: Assessing the user experience.
Version: 1.0
Date: 01/26/2020
Priority: 2

[Howie3426]

FR11: User Information Form
Goal: To obtain user information in order to send a confirmation email to the user
Stakeholders: Users
Description: When the user chooses the item they wish to donate in step 3, the user will be redirected to another page where it will ask the user to fill out a digital form. The form will ask the user to enter their first name, last name, email, phone number and so forth. After the user has entered the required fields in the form, the user will press the submit button which will allow for email verification to the user. A failure case that might arise with this requirement is that the form does not allow the user to enter their inputs or the form does not store the data the user entered into the form.
Origin: Meeting 2: Assessing the user experience.
Version: 1.0
Date: 01/26/2020
Priority: 2

[Howie3426]

FR12. Counter Underneath Donation Items
Goal: To enhance the visual appeal of the website and provide a visual representation of the items donated.
Stakeholders: Users
Description: Located beneath the donation items in step 3, the counter will keep track of the number of times the specific item has been donated. For each donation, the counter will increase by one. For example, let’s say the user donates (one) canned food items, therefore the counter will increase by 1. A failure case that may arise with this requirement is that the counter does not increment after each donation.
Origin: Meeting 1: Team members were brainstorming features for the website, and decided to add this requirement during the meeting.
Version: 1.0
Date: 01/26/2020
Priority: 2

[Howie3426]

FR13. Donation History
Goal: To allow users to track their previous donations made to the site through their account.
Stakeholders: User
Description: After the user submits the form and receives an email verification about the item they will donate, the user’s donated item will be posted under a donation history page under their account in order for the user to track their past donations. A failure of the donation history requirement is that donations do not get added to the user’s account under donation history.
Origin: Meeting 1: Team members were brainstorming features for the website, during meeting.
Version: 1.0
Date: 01/26/2020
Priority: 2

[Howie3426]

FR14. Social Media Redirects
Goal: To provide the user with links to CharityBox’s social media
Stakeholders: Users
Description: At the bottom of the website, the user can click on the social media icon that will redirect the user to CharityBox’s social media accounts. A failure case that may arise is that the link does not redirect to CharityBox’s social media accounts. It may redirect to the social media’s login screen and does not go to CharityBox’s page.
Origin: Meeting 1: Team members were brainstorming features for the website, and decided to add this requirement during meeting.
Version: 1.0
Date: 01/26/2020
Priority: 3

[Howie3426]

FR15. Feedback Form
Goal: To allow users to express their concerns/opinion of CharityBox through the website.
Stakeholders: Users
Description: A link will be provided on the website that will allow users to submit a feedback form which will be sent to CharityBox’s team members. A failure case that may arise with this form is that the user is unable to write their input and that the data from the form does not get sent to CharityBox.
Origin: Meeting 1: Team members were brainstorming features for the website, and decided to add this requirement during meeting.
Version: 1.0
Date: 01/26/2020
Priority: 2