1. Farmworkers Safety System
Presentation 3:
Transition Readiness Review
Team 9
JUAN

2. Outline Introduction Operational Concept Design System Demo
Quality Assurance
Metrics
Technical Debt
Transition Plan
Q&A
JUAN

3. Agriculture Statistics
JUAN

4. Amount California farms and ranches made in 2015 for their output
$47 Billion
Amount California farms and ranches made in 2015 for their output
JUAN

5. California remains the leading US state in cash farm receipts.#1
California remains the leading US state in cash farm receipts.
JUAN

6. Number of farms in the California
90,000
Number of farms in the California
JUAN

7. Farmworker’s Average Yearly Salary
$11,000
Farmworker’s Average Yearly Salary
JUAN

8. “Change work or health to work and health”
Project mission:
“Change work or health to work and health”
Improve the health and quality of life of farmworkers
JUAN

9. Core capabilities Step 3 Step 2 Step 1
Provide articles, videos, etc to educate the farmworker
Step 1
Send periodic weather notifications to the registered contact number
Register farmworker with basic profile - contact details, farm location, etc
JUAN

10. Operational Concept Design
In the OCD, we describe the the system, discuss core capabilities, and list our constraints and goals
VAHAG

11. System Purpose
Claim:
Heat and environmental conditions jeopardize the safety of millions of laborers in CA. Farmworkers are among those affected.
Current Situation: No standardized systems exist.
At best: Information is shared at the beginning of the workday. Communication happens through cell-phones and through in-person check-ins.
At worst: Workers work in isolation of each other and are unaware of environmental conditions. Sometimes, can have no interaction with management.
Goals: (in order of clients’ prioritization) 1) Improve farmworkers quality of life. 2) Educate farmworkers about the risks from environmental conditions 3) Notify farmers and farmworkers about work conditions
VAHAG

12. System Boundary Diagram
JUAN, Fix

13. System Demonstration
JUAN & THEERAPAT

14. Demo
Phone Number: (210)
JUAN

15. Quality Assurance
How will we test the system to make sure it functions as expected and as designed?
DAVID

16. Testing Overview
Focus shifted from unit testing to quality testing, making sure core aspects functioned as expected
Tested the quality of both aspects of our project: the Web Application and the SMS Notifications
JUAN

17. Test Suites Requirement ID Verification Type
Test Case ID (if applicable)
CR-1: Temperature-based notification system
Testing
Inspection
TC-01 Send SMS notifications
TC-02 Fetch temperature based on user’s location
CR-2: Educational content system
TC-03 Upload new educational content
TC-04 View educational content
TC-05 Create a quiz
TC-06 Take a quiz on educational content
CR-3: Accurate farmworker location
TC-07 Update farmworker location via SMS
TC-08 Farmworker self-update of location
TC-09 Contractor/Farmer update of farmworker location
CR-4: Profile system
TC-10 Create user profile
TC-11 Edit/Update user profile
TC-12 Delete user profile
TC-13 Register Farm
TC-14 Login/ Logout
Needs update from DAVID / FERESHTEH

18. Test Results (Web Application)
Number of Test Cases: 30
Passed 25
Failed 3
N/A 2
** The N/A result is those which are not implemented
JUAN

19. Failed Test Cases (Web Application)
Reason
TC-05-04: The farmworker is able to search for educational content
Unable to search quizzes
TC-07-02: System saves progress and completion of quiz and shows grade
Status of quiz is not saved
TC-14-03: Forgot password
Unable to recover password
JUAN

20. Discarded Test Cases (Web Application)
Reason
TC-12-01: Successfully delete the profile
Currently not deleting profiles, only disabling
TC-12-02: The delete function deletes only the suspected profile
JUAN

21. Test Results (SMS Notification)
Number of Test Cases: 22
Passed 21
Failed
N/A 1
** The N/A result is those which are not implemented
JUAN

22. Discarded Test Cases (SMS Notification)
Reason
TC-09-03: Farmworker receives text message after farm owner/contractor updates location
Currently don’t send notifications from changes made on the web application
JUAN

23. Traceability Matrix OCD Requirements Win-Win SSAD TPC OC1
Temperature Based Notification
WC_4153, WC_4156, WC_4170, WC_4172, WC_4182
UC-14
TC-01, TC-02
OC2
Educational Content
WC_4159, WC_ , WC_4179
UC-12, UC-13
TC-03, TC-04, TC-05, TC-06
OC3
Profile System
WC_4175, WC_4177, WC_4178, WC_4180, WC_4181, WC_4184
UC-1, UC-2, UC-3, UC-4, UC-6, UC-7, UC-8, UC-9, UC-10, UC-11
TC-10, TC-11, TC-12, TC-13, TC-14
OC4
Accurate Farmworker Location
WC_4157, WC_4171,
UC-5
TC-07, TC-08, TC-09
Needs to be fixed/ David, Fereshteh

24. Definition of Done Code Completed
Code is according the defined standards
Code is Commented Appropriately
Code is Reviewed by Second Developer (Different that the one who coded the segment in question)
Unit Testing.
New Code Integration with the Existing Code on GitHub (Without Submitting to GitHub)
Integrated Code is Tested on Local Machine (Project’s Features are tested to determine if the code that has been added is working properly and there is no integration issues).
Code Submission to GitHub
Code is Submitted to Production Server (MS Azure)
Project’s Features are tested while running on Production Server
JUAN

25. Progress Burndown Metric
BASIR

26. Effort Metric
BASIR

27. Technical Debt Solved Remaining
Lots of new team members needing to get acclimated to the project
User Interface Approved by the Client.
A Quiz Module Full Implementation was decided to be done.
Remaining
Awaiting input from Cal/OSHA and/or possible investors that could affect the system’s functionalities.
BASIR

28. Transition Plan
JUAN

29. Roles JUAN Team Member Role Construction Transition Juan Andrade
Project Manager, Life Cycle Planner, Developer
Project Management, Develop Back-End, LCP
Manage Project Transition, Fix/Build Software,, Code/Design Review, Provide Client training
Basir Navab
Developer, Life Cycle planner
Develop UI, Develop Front- End, LCP
Fix/Build Software, Code/Design Review, Provide client Training
David Tasky
Tester
Create Test Cases, Unit Testing Front-End/Back-End
Test Software, Code/Design review,
Provide Client Training
Vahagen Sinanian
Developer, Operational Concept
Develop UI, Develop Front- End
Fix/Build Software,, Code/Design Review, Provide client Training
Theerapat Chawannakul
Developer, System Architect
Build software, Code/Design Review, Provide Client Training
Fereshteh Khorzani
Create Test Cases, Unit Testing Front-End/Back-End
Code/Design Review, Test software, Provide Client Training
JUAN

30. Objectives Client Training. Hand Over Source Code and Documentation.
Prototype deployment on a participating farm.
Adapt and Optimize System’s Performance according to the expected load.
Implement Possible New Features proposed by Cal/OSHA and/or Investors.
JUAN

31. Strategy Cal/OSHA Presentation Preparation.
Prototype Tuning through testing, evaluation & bug fixes.
Upgrade to Premium Plan once budget is approved.
JUAN

32. Deliverables Full Functioning Prototype User & Maintainer Manual
Source Code
JUAN

33. Risks Uncertainty on the expected changes from Cal/OSHA
Uncertainty on the results from the Prototype Deployment under real time load.
Creation of a Future Maintenance Plan after deployment.
JUAN

34. Schedule Date Role Activity April 22nd to April 27th
Developers/Testers
Acceptance Testing of the System and Bug Fixes
April 28th
Team
Delivery of: Source Code, Documentation and Training Material
May 2017
Team / Client
Meeting with Cal/OSHA.
May July 2017
Develop and Adjust the remainder of the Project and Enhance existing features after Cal/OSHA's Meeting.
TBD
Client
Budget for Development and Technology Assets Approval.
Prototype Deployment on Participating Farm
JUAN

35. Q&A
JUAN

36. Thank you
JUAN