Welcome to the jude_morera_P1 wiki!

First day (6/23)

Yesterday: Sketching out preliminary database design.

Today: (hopefully) finishing database and designing the POJO.

Roadblocks: Figure out how this 'grading scheme' thing is going to work within 3NF.

Day 2 (6/24)

Yesterday: getting database up to par and interesting these long requirements; creating the POJO represnatives

Today: Probably making html pages; makes most sense to create the fields we need then the code to read/write to it

Roadblocks: the size of this project, plus I'm a bit rusty in html

Day 3 (6/27)

'Yesterday'(weekend): worked on the account DAO and such, to pull the Request info in the app.

Today: hoping to figure out to have an actual 'log in' instead of just a gated page change. Cookies, Queries, Session/Tokens all possible routes.

Roadblocks: persisting the "login", so that after moving to the 'homepage', the user 'stays logged in'.

Day 4 (6/28)

Yesterday: Implemented a persistent login with automatic pulling of all an employee's requests on their login.

Today: Next step is a form for submitting a new request; implemented via a navbar taking to another page (the new page is made, just need to finish up the form).

Roadblocks: So far, dates. Might need to get creative to have html/bootstraps handle date+time; also, oddities in GET method not working so POST has to be used.

Day 5 (6/29)

Yesterday: finished the ability to post new requests, started working on Manager login.

Today:

• Make the manager page actually have content; It will need to be able to see all requests from all users, and modify+update the status code (accept/deny).
• Should add ability to Employee-Request page to update a grade on a request with status code awaiting grade, and update the status to graded, awaiting manager review.
• next steps:
  1. Instead of the primary-key ints for users/types/etc. should actually pull the respective names; this will require more endpoints and json sending I guess.
  2. Along with that, the derived info such as showing the calculated expected reimbursement = cost * type's percent, except I also need to implement that business rule of $1000 - 'Pending'(whatever that means) - 'Awarded'; guess this means a new html field to display the available as well.
  3. Give manager screen ability to mark urgent anything less than 2 weeks from starting; cannot submit a new request less than a week prior to event;

Roadblocks: there's a lot of stuff to do, especially when my html isn't up to par. Still haven't started on any test automation because I'm implementing "basic infrastructure".

Day 6 (6/30)

Yesterday: 1. Manager login that can see all requests 2. Employee can submit a grade and change status Today: 1. Manager ability to change status (i.e. approve/deny) 2. Include the display for available balance; this will require minor refactoring of java request object. Roadblocks: the great unknown, encroaching ever closer...

#Day 7 (7/1) Yesterday: I think I finished the necessary endpoints for an MVP, at least the the point I can reasonably begin testing; got the prereqs for the test automation up (Selenium, Cucumber, Junit Suite).

Today: In order of priority: Testing, cobbling whatever I missed, stretch goals + appearances. (Still need add the calculating for available 'balance').

Roadblocks: A bit vague on what needs to be tested; junit for each service method? DAO method? Controllers?