Week 5 Session 1
During this session we went through Risk Management. In the session we talked about risks that could develop or appear. In the session we also talked about what affect it could have on the project and end project. If risks do arise they need to be handled correctly for example in group project if a person is absent, the team leader can split their tasks to other team members. If they are not dealt with appropriately they can increase costs, delay completion, or may even result in failure.
In this project we will keep a log of all the risks that can occur. The picture of the document is below.
Risk Contingency – If it does happen what are you going to do?
Risk Mitigation – What are you going to do from prevent it from happening?

During this session we had a quick meeting to discuss and talk about how far we have got with the tasks set. Our entire group had the tasks done and were up-to-date. We all uploaded the diagrams on egnyte and also printed a copy out to compare and contrast. Most of our group had very similar entities but the relationships were a bit different. As a group we drew the first draft on paper, the picture of the diagram is below.
First attempt

Second attempt

During this week we had a few meetings. This week we got the Entity Relationship Diagram (ERD) and Table Schema out the way. We gathered around in our group with each of our diagrams and discussed the good and the negative parts. One of the members in the group had separate entities for each member of staff. This would make it very complicated and time consuming if the database was updated in the future. So we discussed that we would have one entity called ‘staff’ and have field name position. This would have all the members of staff in one table.
The Screenshot below shows my second attempt at the ERD. From the previous I have added a delivery entity because this will be important for the supplier. The assumption was that there may be several warehouses over the UK. So the supplier must need the information about delivery to dispatch the products. Once this diagram was created I then created the table schema. The table schema will need improving because the foreign keys aren’t in the tables. Without the foreign keys there will be no links between the tables.


Below is the improved diagram that I have attempted in this week. Firstly I have removed the many to many relationship that existed. This was between the supplier and order entity. In the revised diagram the supplier will be linked to the garden items table and the supplier. The relationship between staff and order was incorrect so this was swapped around because a member of staff can place many order. But before I had many staff can place an order. For order items entity we changed the name because it was getting confusing with similar entity names, so this was changed to ‘basket’.

Also attached is the table schema we attempted as a group. As you can see the correct links have been made, So the Order table will have a foreign key coming from the Staff table.

Week 5 Session 2
After a short break we continued the second session. In this session we discussed if having 30 tables for each category would be efficient. Carrying out some researched showed us that we can separate each category in the same table but as a view. Below is an example of how we created a view and joined the supplier table. I first opening the databases in the schema in the bottom left of the screenshot. Then I right clicked view and clicked create view. It brings up a blank page where you need to add the SQL to create the view. This way it made it more efficient and easy to update in the future.
Below is the screenshot of the SQL to create a view within that table.

Now we have done a SQL query to output the data alongside with the supplier information.
First half table

Second half table

Creating views would be good for the long term because it would be easier to update and also easier to find the data. Before there was just too many tables and it was too confusing. Now we just need to find the items table and click views in the schemas part in workbench.
Change in team leader
During these weeks we had some issues about the tasks given to the individuals. So we decided to change the team leader to see if this would get rid of the issue. So I am the new team leader in this project. So far it is going well because I have given equal tasks to everyone with a date to be completed by. Once they have completed the tasks we will discuss as a group and make a final design for the diagrams, ERD and table schema.
The tasks for this week;
The tasks for this week is to create a final design for the ERD and table schema. The other task is to do a Use case diagram, class diagram, Activity Diagram and sequence diagram.
The kanban board has been updated and the picture is below.
