Successfully reported this slideshow.

A2 unit 7 june2007

577 views

Published on

Published in: Business, Economy & Finance
  • Be the first to comment

  • Be the first to like this

A2 unit 7 june2007

  1. 1. June 2007 exam paper Employee number Employee name Rate category Project number Employee number Project number Project name Rate category Hourly rate entity1 entity2 link e.g. Street, Town, City are dependent on Postcode (and not on the table’s PRIMARY KEY) CustomerID HouseNum Street Town City Postcode dependent  not dependent 3NF
  2. 2. Branches Suppliers Denim Daze warehouse A2 Applied ICT Unit 7 Database Exam June 2007 order
  3. 3. Branches Orders Pending Orders Processed Pending Delivery Suppliers Denim Daze warehouse In stock? ‘ cages’ yes no A2 Applied ICT Unit 7 Database Exam June 2007 Despatch order stock received
  4. 4. ( ) ( ) ( ) ( ) ( ) ( ) stock items orders suppliers stock items orders branches ONE supplier(s) can supply ONE stock item(s) MANY MANY ONE order(s) can be for ONE stock item(s) MANY MANY ONE branch(es) can put in ONE order(s) MANY MANY check order files to confirm this one
  5. 5. stock items orders suppliers stock items orders branches branches suppliers stock items orders
  6. 6. ‘ Stock’ data file Stock ID Description Colour Gender Style Size Code Size Description Stock Level Re-Order Level Re-Order Quantity Order Outstanding Buying Price Supplier ID Supplier Name Supplier Address 1 Supplier Address 2 Supplier Town Supplier County Supplier Post Code Supplier Country Contact Name E-Mail Telephone ‘ NewOrder’ data file Order Number Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager ‘ OrdersPendingDelivery’ data file - Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager ‘ OrdersCaged’ data file - Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager branches suppliers stock items orders
  7. 7. ‘ Stock’ data file Stock ID Description Colour Gender Style Size Code Size Description Stock Level Re-Order Level Re-Order Quantity Order Outstanding Buying Price Supplier ID Supplier Name Supplier Address 1 Supplier Address 2 Supplier Town Supplier County Supplier Post Code Supplier Country Contact Name E-Mail Telephone ‘ NewOrder’ data file Order Number Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager Branch ID (PK) Branch Name Address L1 Address L2 Town County Post Code Telephone Manager Supplier ID (PK) Supplier Name Supplier Address 1 Supplier Address 2 Supplier Town Supplier County Supplier Post Code Supplier Country Contact Name E-Mail Telephone Order Number (PK) Status Stock ID (FK) Quantity Date of Order Branch ID (FK) Stock ID (PK) Description Colour Gender Style Size Code Size Description Stock Level Re-Order Level Re-Order Quantity Order Outstanding Buying Price Supplier ID (FK) ‘ OrdersPendingDelivery’ data file - Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager ‘ OrdersCaged’ data file - Stock ID Quantity Date of Order Branch ID Branch Name Address L1 Address L2 Town County Post Code Telephone Manager <ul><li>Create a new attribute called ‘Status’ to allow each of these order files to be combined into a </li></ul><ul><li>(much more efficient) single entity </li></ul><ul><li>Use a ‘make table query’ to create the Orders table from one of the datafiles. Add the Status field </li></ul><ul><li>(Status: “xxxxxx”). Do NOT include Order Number at this stage. </li></ul><ul><li>Use ‘append queries’ to add the data from the other two order files. Don’t forget to change what </li></ul><ul><li>the Status field says. Still do NOT include Order Number at this stage. </li></ul><ul><li>In the table design view, add the ‘Order Number’ field and give it the data type AutoNumber to </li></ul><ul><li>automatically generate an Order Number for all orders. Choose a number to begin this at (enter </li></ul><ul><li>into ‘Format’ in design view – must end in zero, e.g. 40000) </li></ul><ul><li>Use a ‘make table query’ to create these tables </li></ul>branches suppliers stock items orders
  8. 8. <ul><li>From the scenario… </li></ul><ul><li>There will be a computer in the warehouse which will display the next order in the ‘Order Pending’ state. </li></ul><ul><ul><li>How will you see only the orders that are ‘Order Pending’? </li></ul></ul><ul><ul><li>What fields need to be shown? </li></ul></ul><ul><li>If stock is available the Warehouse Operator will process the order as normal. The Warehouse Operator will need to be able to tell the system that the order has been filled and the items are in the relevant cage. </li></ul><ul><ul><li>What needs to be changed to do this? </li></ul></ul><ul><li>After each order has been processed the next in the list will be displayed . </li></ul><ul><ul><li>How are we going to do this automatically? </li></ul></ul><ul><li>If there is not enough stock in the warehouse this should be shown on the form to save the Warehouse Operator looking for stock that is not there. </li></ul><ul><ul><li>Which 2 fields do we need to compare? </li></ul></ul><ul><ul><li>What message(s) do you want to display? </li></ul></ul><ul><ul><li>Plan it out as an IF function: IIF ([condition], true response, false response ) </li></ul></ul><ul><li>In this situation the Warehouse Operator will print off an ‘Out of Stock’ form to put in the cage. </li></ul><ul><ul><li>What needs to be created? </li></ul></ul><ul><ul><li>What details need to be on it? </li></ul></ul><ul><li>If there are no more orders the screen will remain blank until the next order comes in. </li></ul><ul><li>This order will automatically be displayed. </li></ul><ul><ul><li>How could we do this? </li></ul></ul>Pending Processed Pending Delivery

×