Project Roadmap

Project Plan for First Semester

• Week of September 7:
  • Team will be continuing their work on looking into how to make a plugin and thinking about what browser the team should use for the plugin.
• Week of September 14:
  • Decide on rule-based or machine learning approach for the plugin
  • Team member assignment (due by Sept. 17 meeting): make a recommendation of which browser we should go with and why.
  • Decide on the browser for the plugin
• Week of September 21:
  • Project manager check in with Dr. Markham
  • Start working on a plugin tutorial (pick a tutorial as a team)
• Week of September 28:
  • Work on the plugin tutorial
  • Start working on the logo and work on a design (UI, etc.) for the plugin
  • Meet with client to update client on decisions regarding rule based and the browser being used.
    • Gather requirements from the client
• Week of Oct 5:
  • Project manager check in with Dr. Markham
  • Start working on a prototype
• Week of Oct 12:
  • Continue work on the design and work on the prototype
• Week of Oct. 19:
  • Present the design, UI, and the prototype
• Week of Oct. 26:
  • Continue work on the protype and start laying out plans for the implementation stage
• Week of Nov. 2:
  • Project manager check in with Dr. Markham
  • Continue work on the design and implementation plans
• Week of Nov. 9:
  • Work on Lessons learned paper
  • Continue work on the implementation plans
    • Finalize plan for semester 2 implementation
• Week of November 16:
  • Lessons learned paper due and peer evaluations
  • Work on final presentation

Project Plan for Second Semester

• Note: Each iteration is 2 weeks long
• First Iteration
  • Onboard new team members
  • Begin researching and each member work on rules that they think should be used in our system
  • If gmail.js API isn't implemented already, integrate it into our codebase
  • Start looking into the API's documentation to find the useful calls.
  • Finalize the rules and document the rules chosen and the weight of each of the rules
• Second Iteration
  • Start with the backend. Create and test javascript code that will implement the rule-based filter.
    • Use the gmail.js filter to extract the gmail text
  • Begin the front-end and model/improve based on prototype in wiki
    • Leave the percentage static for now until we connect the back-end with the front-end
  • Find a test dataset that we can use to test
• Third Iteration
  • Continue backend and frontend work
  • Decide on manual testing of the plugin using the database or automated testing
• Fourth Iteration
  • Connect the backend with the front end and test the extension
  • Improve the accuracy of the extension by testing the weights
• Fifth Iteration
  • Work on getting the plugin into the extension store IF time permits.
  • Finalize and submit the project