Checking system

Today, we discuss DDL, storyboard and DFD. We need to modify certain part of our proposal because the changes of our database.


After that,  we check our web page, there have some error that we need to correct.

Today finished uploading the website onto a web hosting server, has to make a few modification to the software and the database because it turns out the the web hosting is case sensitive, and since previously i used dreamweaver which wasnt case sensitive, had to correct all the file name, page redirection and links.

Today i also successfully created the triggers which i previously had much problem with. The triggers can update the product every time an order is made. Also  added a last minute feature which is the insert delivery information for admin and users can now view the delivery information of their order after the admin has posted their orders.Today, i also started correction and modification on all the previous documentation to prepare for the final report submission during presentation.

Today, finished polishing the manage customer page for admin and repaired some errors with the customer.At the same time, i spotted an error in the generate sales order interface, that display the total amount that is expected to be paid to the admin wrongly, fixed it realizing that the value keeps increasing even after an order is paid.

 Other than that, also added in search product functionality for users with or without login.
Before this, i mentioned having a hard time with trigger because of not being able to create a trigger that  updates stock quantity when an order is confirmed.Today though, found a convincing lead on how to create the mentioned trigger, although i presume it involves some concept changes to the system, will work on it tomorrow.

Whereelse, in the morning, met with my fellow group members to show them to progress of the system and did a little demonstration of the nearly complete prototype.

Teh

Today, i met with puan without making any prior appointment to inquire more about the ERD, as i am not sure whether to create a table for cart, or to just use a view to display cart, or neither at all. Puan said that it is up to us, and at the end of the day, i decide that creating a view is the most convenient way to manage to database.

Completed the cart interface for the user, and the cart are now able to view their status in their cart, however, i have encountered some problems with the concept of the cart of the website. Firstly, how do i allow user to add items to cart, without confirming the order, and deleting the entries in the cart after the user logs out. In the end i decided to place the delete query at the log out.php to delete all items from the cart for that particular user where the product order are still not confirmed. Even so, i am still having some issues regarding the database for the cart,as it is hard to mange the datas in the cart involving multiple tables. Not to mention, as puan said, the stock quantity in the product have to be updated everytime an order is placed. Puan suggested for us to use trigger to maintain that stock quantity, i shall stick to that idea for now.

Teh

Spent the whole day completing the functionality for the project. What was done today are namely, the functions of the website for the outer layer, where users can see and interact with without logging in, and also sign in and sign up. Changed most of the file formats to .php because most of the pages requires interaction with the database as the website is dynamic.

Other than that, the interface for users who have logged in are completed partially, users are now able to add products to their cart, and the product items are displayed dynamically. The cart for the user where the user can see their order have yet to be completed.

Teh

Met with Puan hidayah today in the morning at 9 am at her office to get clarifications regarding the part 1 part 2 and part 3 of the documentations. Also , we discussed about issues regarding our ERD like whether to put admin in its own table using a view for displaying cart.

Other than that, we have brought up that the table order could not be created with order as a singular, puan suggested us to use other words that could replace the word order. After multiple trial and error and googling, we have concluded and realized that order is actually a reserved word mysql database, hence it is impossible for us to create a table with the table name as order. As a temporary resort, we created the table as orders.

For our database, we start to configure and create table using Appserv base on our ERD .

For interface, we continue to design the other pages that haven done such as individual product description, cart, sign in, sign up, logo of our page, order list, and so on.

after these,we start to do the functionality.

Today we discuss about the storyboard whether if we need to add interface to our P3.
We get to the library discussion room for our discussion at 11am.
At the discussion room, we start doing...
- storyboard
- interface
- researching product description
- design banner

Workshop team member

Date 29.2.2015

First meeting

In the first meeting we had assign each member's responsibility within the group and understand about our job scope .

Beside, during the meeting we set our title,that is Natural Plant Products Online System.

Task complete:

1.Discuss topic of project
2.Create Blog
3.Discuss about the project flow

DATE:20 APRIL 2015

Today we start to create a local host for our database. Using Appserv packages which is My Sql.
First we use the Data Definition Language (DDL) command to create the database table.
Then, we insert our data into the database.

Carolyn

DATE:30.3.2015
4th Meeting

our proposal>.<

After we get back our proposal, we found that that we miss two part that is module of the system and appendix.
btw,we need to rush bcs we need to submit context diagram and storyboard plus need to repair our proposal.

We decide to settle the module and appendix first,after that just carry on the storyboard and context diagram.

DATE:21.3.2015
3rd Meeting

During this meeting,we focus on our user view , data requirement and transaction requirement and ERD.

we face problem when doing ERD ,because have a few confusing about order .

Task complete

1.user view , data requirement and transaction requirement.

2.ERD

DATE 13.3.2015
2nd Meeting 

We list down all software and hardware we need for the project
like
Oracle 9, My SQL
Adobe Dreamweaver
Microsoft office

We dun have client for this project so we do as document analysis
we compare two website 
1. The Body Shop- http://www.thebodyshop.co.uk/index.aspx
2.  Hermo- http://www.hermo.my/mall/64-nature-republic-soothing-n-moisture-aloe-vera-92-soothing-gel-300ml.html

we analysis the inadequate of these two website ,and want to make our system become more easy to use.

Task complete

1.list down the software and hardware we need.

2.document analysis.