Written Status Reports

This page of the Wiki contains written status reports for CMSI 402.

Written Status Report 1

General Information

• Name: Edward Bramanti
• Project Name: Ricetta
• Date: March 4, 2015
• Period Covered: 2/25-3/4

##Accomplishments Since Last Report

• Fixed problems with unit testing suite, now able to make API calls to verify the API is validating input properly
• Cleanup of database after each unit test now occurs (thanks to node-neo4j)
• Implemented more validation checks into user accounts
• Added database initialization to prepare for future Recipe Curator
• Added functionality to Makefile to create ease of workflow

##Scheduled Tasks to be Done

• Finish up validation for signup and login
• Start setting up service and query layer for recipe CRUD operations
• Fix Frisby async issues
• Set up remote database server for Neo4j testing

##Risks/Concerns/Problems

• Frisby async issues may be unavoidable, and may force me to switch to a different framework
• Have a lot of interviews for jobs and a test on Monday, may not be able to meet signup/login completion goal in SDP
• Need to continue upgrading data models that I've made so that it creates less problems when implementing in the query layer

Written Status Report 2

General Information

• Name: Edward Bramanti
• Project Name: Ricetta
• Date: March 18, 2015
• Period Covered: 3/11-3/18

##Accomplishments Since Last Report

• Implemented API layer for the login route
• Added validation for Recipes in Go structs
• Improved function names for service layer

##Scheduled Tasks to be Done

• Complete service and query logic for login (JSON Web Tokens vs. UUID token)
• Implement recipe creation service and query logic
• Implement editing of recipes

##Risks/Concerns/Problems

• Recipe CRUD operations
  • Validation (requires a lot of unit testing)
  • Service layer logic (what queries to call depending on recipe attributes)
  • Query layer logic (making sure Neo4j queries connect nodes with proper relationships)
• Authentication decisions
  • Adding new JSON web tokens vs. using UUID tokens stored in HTTP header

Written Status Report 3

General Information

• Name: Edward Bramanti
• Project Name: Ricetta
• Date: April 1, 2015
• Period Covered: 3/25-4/1

##Accomplishments Since Last Report

• Implemented a majority of the validation for recipes
• Stubbed out creation function for CreateRecipe route
• Added validation for tags

##Scheduled Tasks to be Done

• Complete service and query logic for recipe creation
• Implement recipe retrieval for users
• Stub out Ricetta Curator endpoints

##Risks/Concerns/Problems

• No front-end implemented yet
  • Nothing for poster review next week
• CSS difficulties
  • No decisions made on framework or style

Written Status Report 4

General Information

• Name: Edward Bramanti
• Project Name: Ricetta
• Date: April 15, 2015
• Period Covered: 4/8-4/15

##Accomplishments Since Last Report

• Laid Marionette foundation
• Implemented models for login and signup
• Continued work on returning recipes to users

##Scheduled Tasks to be Done

• Finish GetRecipe
• Begin implementation of EditRecipe

##Risks/Concerns/Problems

• CORS issues
• Deleting recipes may not be implemented
• Conflicts with handles in database
• Front-end CSS
  • No concrete decision on framework (Bootstrap vs. Skeleton)