Your
 work journal is great until mid June when it stops.



The
 whole point of using Trello is that we can generate evidence that you used an iterative process and purposeful / efficient use of time. This is an NCEA expectation for Merit.



Your
 data dictionary is too simple. I provided a template that contained all the info needed such as length, foreign key, etc .  You’ve reduced it to three columns which doesn’t show much in the way of planning for NCEA.



Create
 your schema in that web
 app I shared or use
 the relationship feature in phpmyadmin and you can include a screenshot for a visual representation in your planning which would suffice for an entity relationship model. At present you only have a thumbnail in your journal which isn’t large enough to be read.
 Make it big and give it its own section.



No
 UI mockup.



Flowchart
 is nice for a procedural style project. No information on classes is described though.



No
 pseudocode exists. You need to describe what each class is, what properties and methods it contains and describe the procedures within each method.



Interesting
 API calls in your js.js file



It
 seems you’ve used a single class for your whole project in the trade.php
 file. This is ok,  but your planning needs to have a pseudocode description of what’s happening inside of it, when it is instantiated and how it’s used.



include("inject.html");
 is happening twice in the home.php file, jquery is included twice too



Your
 code comments are a bit thin in most files. You should make note of any interesting bits and justify your decisions in the comments.
(Hint: Your pseudocode,
 when completed, could serve as code comments if they’re written clearly enough.)



Running
 your program, it’s not clear exactly what it’s meant to do. What is the user expected to enter? I entered some integers and nothing happened, no error message either.



Login
 and logout work fine. These features could be encapsulated in a class though which would strengthen the programming side of the assessment.



Make
 sure that your app can allow the user to complete a CRUD cycle. I didn’t see any obvious way that an entry could be edited and updated in your code.



Your
 data structure has only two tables with a single one-to-many relationship.  As it is lacking sufficient complexity for the database standard at NCEA level 3, it can get you an achieved at best provided that all of the above points are addressed.