erasEwaste Use Cases

Volunteer Use Cases

1. Login_Layout

Identification: A volunteer logs into the system with his name and his ID given to him by his manager. He then clicks ‘Login’.

Primary Actors: The user (volunteer) and the manager are the primary actors. The manager sets up the volunteer’s account and the volunteer signs in.

Stakeholders: The stakeholders include the volunteer, the manager, and Property Control. The manager can track his volunteers, the volunteers can log their work, and Property Control can have records for itself and recipients.

Preconditions and Main Success Scenario: Having the manager set up the volunteer’s account is the first precondition and making the volunteer aware of his login information is the second.

2. Title_Layout

Identification: This screen welcomes the volunteer after logging in and gives them the option to ‘Enter New Record’, click ‘Find Mode”, or ‘Administration’. ‘New Record’ allows a user to register a product that came in to Property Control. ‘Find Mode’ allows the user to search through products that were already registered. ‘Administration’ allows a logged in manager to perform administrative actions. The user also has the option to ‘Logout’ in the top right corner of the page.

Primary Actors: The volunteer and manager are the primary actors. The volunteer can access ‘Enter New Record’ and ‘Find Mode’ and the manager can access ‘Enter New Record’, ‘Find Mode’ and ‘Administration’.

Stakeholders: The stakeholders here are the volunteers, manager and Property Control.

Preconditions and Main Success Scenario: The volunteers and manager must be have an account and be logged in to get to this screen.

3. Products_Layout

Identification: On this screen the volunteer is welcomed and he can register a product into the database. He first chooses a ‘Product Type’ from a dropdown list, then determines the ‘Product Quality’ and selects the appropriate radio button, then determines whether or not the product passed ‘Final Inspection’ and selects the appropriate radio button. The volunteer then may add any ‘Additional Notes’ in a comment box. The final step here is to provide the volunteer’s ‘Signature’ with his finger on the tablet itself. After all of this information is input, a QR code will be generated on the right side of the screen unique to that product. The volunteer may go back by clicking ‘Home’. The volunteer can also ‘Create New Record’ or ‘Delete Record’. Clicking the ‘Next’ button takes the volunteer to the next screen. The user may also ‘Logout’ in the top right corner.

Primary Actors: The volunteer is the primary actor who determines the data on this screen.

Stakeholders: The stakeholders are the volunteer and Property Control.

Preconditions and Main Success Scenario: The preconditions are that the volunteer received a product. If the product received is a computer, then the volunteer must do a hardware test and a software update.

4. QR_Code

Identification: After the volunteer or manager clicks ‘Next’ on the Products_Layout screen, they are taken to this page that thanks them for registering the product information. They are shown the product’s unique QR code and are given the option to click ‘Finish’, which takes them back to the Home page, or click ‘Logout’.

Primary Actors: The primary actors are the volunteer and the manager.

Stakeholders: The stakeholders are the volunteers, the managers and Property Control. The volunteers and managers can print the QR code and place it on each product to allow for easier tracking for all of Property Control.

Preconditions and Main Success Scenario: The preconditions are that either the volunteer or manager filled out the Products_Layout form and clicked ‘Next’ on the bottom right of that screen.

5. Find_Products_Volunteer_User

Identification: This table allows a volunteer to view products registered in the database. The volunteer may also click ‘Home’ or ‘Logout’ at any time.

Primary Actors: The primary actor is the volunteer user.

Stakeholders: The stakeholders are the volunteer, the manager and Property Control.

Preconditions and Main Success Scenario: The preconditions are that the volunteer is logged into the database, and that there are products that have already been registered before they search for a product.

_________________________________________________________________

Manager Use Cases

1. Login_Layout

Identification: A volunteer logs into the system with his name and his ID given to him by his manager. He then clicks ‘Login’.

Primary Actors: The user (volunteer) and the manager are the primary actors. The manager sets up the volunteer’s account and the volunteer signs in.

Stakeholders: The stakeholders include the volunteer, the manager, and Property Control. The manager can track his volunteers, the volunteers can log their work, and Property Control can have records for itself and recipients.

Preconditions and Main Success Scenario: Having the manager set up the volunteer’s account is the first precondition and making the volunteer aware of his login information is the second.

2. Title_Manager

Identification: This screen is for a manager only, and allows him to ‘Enter New Record’, ‘Find Products’, ‘Create New User’, and ‘Find Volunteers’. The manager may also click the ‘Logout’ button.

Primary Actors: The primary actor is the manager, who can take these administrative actions.

Stakeholders: The manager, volunteers and Property Control are stakeholders since the manager can create records and users. The volunteers depend on the manager to have accounts and Property Control relies on volunteer and product records for their operations.

Preconditions and Main Success Scenario: The precondition is that the manager logged in.

3. Create_New_Volunteer

Identification: This screen allows the manager to add a volunteer to the database. The manager inserts the volunteer’s name into a text-field and determines whether or not to give them administrative permissions by checking off the checkbox labeled ‘IsManager’. After inputting this information, the manager clicks the ‘Create User’ button. The manager has the option to return home by clicking the ‘Home’ button, or logging out by clicking the ‘Logout’ button.

Primary Actors: The manager is the primary actor here.

Stakeholders: The stakeholders are the manager, volunteers, and Property Control. The manager creates the main record for his volunteer and determines whether or not that person is a manager as well. Managers have greater permissions than regular volunteers.

Preconditions and Main Success Scenario: The preconditions are that the manager is logged in and clicked ‘Create New User’ on the Title_Manager screen. The manager must also have a volunteer to add to the system.

4. Products_Layout

Identification: On this screen the volunteer is welcomed and he can register a product into the database. He first chooses a ‘Product Type’ from a dropdown list, then determines the ‘Product Quality’ and selects the appropriate radio button, then determines whether or not the product passed ‘Final Inspection’ and selects the appropriate radio button. The volunteer then may add any ‘Additional Notes’ in a comment box. The final step here is to provide the volunteer’s ‘Signature’ with his finger on the tablet itself. After all of this information is input, a QR code will be generated on the right side of the screen unique to that product. The volunteer may go back by clicking ‘Home’. The volunteer can also ‘Create New Record’ or ‘Delete Record’. Clicking the ‘Next’ button takes the volunteer to the next screen. The user may also ‘Logout’ in the top right corner.

Primary Actors: The volunteer is the primary actor who determines the data on this screen.

Stakeholders: The stakeholders are the volunteer and Property Control.

Preconditions and Main Success Scenario: The preconditions are that the volunteer received a product. If the product received is a computer, then the volunteer must do a hardware test and a software update.

5. QR_Code

Identification: After the volunteer or manager clicks ‘Next’ on the Products_Layout screen, they are taken to this page that thanks them for registering the product information. They are shown the product’s unique QR code and are given the option to click ‘Finish’, which takes them back to the Home page, or click ‘Logout’.

Primary Actors: The primary actors are the volunteer and the manager.

Stakeholders: The stakeholders are the volunteers, the managers and Property Control. The volunteers and managers can print the QR code and place it on each product to allow for easier tracking for all of Property Control.

 
Preconditions and Main Success Scenario: The preconditions are that either the volunteer or manager filled out the Products_Layout form and clicked ‘Next’ on the bottom right of that screen.

6. Find_Volunteers

Identification: This screen allows a manager to view Volunteers in the database.

Primary Actors: The manager is the primary actor.

Stakeholders: The stakeholder is the manager and the volunteer.

Preconditions and Main Success Scenario: The manager must have first logged in and gone to the Title_Manager screen and clicked ‘Find Volunteers’. The volunteers must have an account in the database.

7. Find_Products_Manager_User

Identification: This table allows a manager to find all products registered in the database along with the volunteers and their ID's. The manager may also click ‘Home’ or ‘Logout’ at any time.

Primary Actors: The primary actor is the manager who searches for this information and indirectly the volunteers who create most of these records.

Stakeholders: The stakeholders are the volunteer, the manager and Property Control.

Preconditions and Main Success Scenario: The preconditions are that the volunteer is logged into the database, and that there are products that have already been registered before they search for a product.