360 likes | 371 Views
This presentation outlines the transition readiness review team's plan for implementing a farmworker safety system. It covers operational concept design, system demo, quality assurance, metrics, technical debt, transition plan, and Q&A.
E N D
Farmworkers Safety System Presentation 3: Transition Readiness Review Team 9
Outline • Introduction • Operational Concept Design • System Demo • Quality Assurance • Metrics • Technical Debt • Transition Plan • Q&A
$47 Billion Amount California farms and ranches made in 2015 for their output
#1 California remains the leading US state in cash farm receipts.
90,000 Number of farms in the California
$11,000 Farmworker’s Average Yearly Salary
Project mission: “Change work or health to work and health” Improve the health and quality of life of farmworkers
Corecapabilities Step 1 Step 2 Step 3 Register farmworker with basic profile - contact details, farm location, etc Send periodic weather notifications to the registered contact number Provide articles, videos, etc to educate the farmworker
Operational Concept Design In the OCD, we describe the the system, discuss core capabilities, and list our constraints and goals
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 conditions3) Notify farmers and farmworkers about work conditions
Demo Phone Number: (210)961-8835
Quality Assurance How will we test the system to make sure it functions as expected and as designed?
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
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
Technical Debt Solved 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.
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.
Strategy Cal/OSHA Presentation Preparation. Prototype Tuning through testing, evaluation & bug fixes. Upgrade to Premium Plan once budget is approved.
Deliverables Full Functioning Prototype User & Maintainer Manual Source Code
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.