Projekt 1 - Database. Indholdsfortegnelse. Intro...4 Indledning...5 Projektbeskrivelse...5 Problem felt...6 Problem formulering...

Transkript

1 1

2 Projekt 1 - Database Fakatark Indholdsfortegnelse Faktaark...3 Intro...4 Indledning...5 Projektbeskrivelse...5 Problem felt...6 Problem formulering...6 Projekt title Database projekt 1 Klasse CLmul-b12e Gruppe nummer 1 Gruppe medlemmer: Peter, Mathias, Søren, Baris Navn Skole mail Underskrift Mathias Andreas Svensson cph-ms23@cphbusiness.dk Rinnin.dk Planlægning...7 Estimering...8 PBS/WBS...9 Gantt-kort...11 Ressourcer...12 Dokumentering...13 Entity relation diagram...14 Use-case...15 CRUD Matrix...21 Kode...22 Peter Geoffrey Johansson geofdesign.dk Søren Van Gaever Skøtt sgraphics.dk Baris Yüksel byüksel.dk cph-pj8@cphbusiness.dk cph-ss16@cphbusiness.dk cph-by@cphbusiness.dk Afslutning...23 Konklusion...24 Perspektivering

3 Intro...4 Indledning...5 Projektbeskrivelse...5 Problem felt...6 Problem formulering...6 Indledning I den bredeste forstand, er en database noget, der gemmer data. I en verden af computere og brug af web-applikationer en database henviser sædvanligvis til en samling af relaterede stykker af information Det lagres eksempelvis på en server. udover muligheden for at lagre data, giver en database også muligheden for andre programmer til hurtigt at hente og opdatere ønskede stykker af information. typisk, for en given database, er der en strukturel beskrivelse af den type af data, der ligger i denne database. Denne beskrivelse er kendt som et schema eller skemaet på dansk. Skemaet beskriver de objekter der er repræsenteret i databasen, og forholdet mellem dem. Der er en række forskellige måder at organisere et skema, der er, at modellere den database struktur: disse er kendt som database modeller (eller datamodeller). Den mest almindelige model for en database er en relationel model. Disse databaser er organiseret efter felter (eller attributter), records og tables. Et field/attributter er et enkelt stykke information; en rekord er et komplet sæt felter, og en tabel er en samling af records. Opgavebeskrivelse Opgaven går ud på at skabe en database og anvende datamodeling til at hjælpe med processen. Entitets relations modellen (EER) vil blive anvendt til at hjælpe med at strukturere databasen. Udover det vil en CRUD matrix vil udarbejdet sammen med USE-cases eller User stories. Der vil desuden være eksempler af kode for yderligere at dokumentere. Opgaven indeholder: - EER model - Use cases/user story - CRUD - Database Opgavens formål er at: 1. Documentere arbejdsprocessen samt analysere, for at kunne forstå produktets udvikling og vedligeholdelse. 2. At kunne skabe en database til opgavens formål. Produkt Opgavens produkt er en butik der ønsker at oprette en database med deres produkter. Butikken og kunder skal analyseres ved hjælp af use cases/user stories, for at kunne dokumentere interaktionen mellem sælgeren og køberen og derved hjælpe fremtidig udvikling og implementering af databasen. Ting af interesse under projektet er: kunden, indkøbskurv, produkt og bestillinger. 4 5

4 Problemfelt Nutidens handel bliver stadigvæk udført ansigt til ansigt, men med digitaliseringen af verden anvender flere mennesker at handle og internettet. Dette gør det nemmere at handle for mange mennesker, samt kan skabe flere kunder for online butikker der ønsker at række ud til et bredere publikum. For at kunne se på butikkens varer kræver det en hjemmeside, men databaser er også et krav da man som butiksejer skal kunne oprette nye varer, tilbud og kunne redigere i eksisterende varer i butikken. Brugere og kunder skal også kunne oprette sig som en bruger, hvis databasen skal f.eks. gemme deres hjemmeadresse eller hvis de vil subscribe til fremtidige tilbud fra butikken. Kunden skal også kunne tilføje varer de ønsker at købe til en indkøbskurv. Der skal desuden være forskel på når butiks-ejeren logger ind på databasen som Admin og når kunder logger ind, da der er forskellige rettigheder. F.eks. kunder skal ikke kunne logge ind som admin. Planlægning...7 Estimering...8 PBS/WBS...9 Gantt-kort...11 Ressourcer...12 Problemformulering Hvordan laver vi en database der indeholder butikkens produkter, med tilhørende ID er? Hvordan laver vi en table der indeholder kundernes informationer samt ID? Hvordan skaber vi en indkøbskurv, der kan indeholde varer og varernes information til checkout? 6 7

5 Estimering PBS/WBS PBS Dokumentation Database SQL Workbench 8 9

6 WBS Gantt-kort Database + kommentarer CRUD matrix ER model Sammensætning af rapport Userstory Dokumentation Attributtabel Rapport Planlægning 10 11

7 Ressourcer Dokumentering...13 Entity relation diagram...14 Use-case...15 CRUD Matrix...21 Kode

8 Entity Relation Diagram Use-case Use Case Name: Customer registration and confirmation Identifier: UC1 Description: This use case will describe how customers can purchase items, register an account and send their order. Preconditions. 1. It is required that the customers create an account. 2. Customers need to be logged in before executing an order. Assumptions 1. Access to internet and all required login details are in order. Frequency Depending on the size of the production company, new members and new instruments, it could be anything from once a day to multiple times a day. Basic Course 1. The use case begins when the user/customer have made their choice of which products he/she/they want to buy and put in the cart. 2. When the user has pressed the buy button, he/she/they have to sign in/create account. 3. Now the user is told to confirm their account from a link that has been sent to their mail. 4. After the confirmation the user is ready to choose payment method. Either Master Card, Visa or faktura for example. Alternate Course A: Description of the alternate course Condition: If the user wants to purchase more items than the stock has, then an error message will occur and notify the customer. 1. The user wants buy 3 guitar strings and press Put in cart. 2. Error message occurs and says, that there is only 2 left in stock. 3. The customer is given 2 options in the error message. 1st option is to wait until the stock get filled up and then send the package(s). 2nd option would be to only get send the 2 of the strings and then pay for 2 shipments. Post conditions 1. If everything has gone right, payment details accepted the package is on its way. The purchase was succesfull. 14 Actors: Local guitar shop Notes: One concern could be that the website isn t secure enough to handle database injections from hackers. 15

9 Use Case Name: Administrator add/remove/edit products Identifier: UC2 Description: This Use case describes how the administrator may edit in the database. IE. remove or add, goods in the Database. Preconditions It is required that the admin has the relevant logon informations The admin must be logged on, in order to edit information in the database Assumptions. Access to the internet and administrator rights / login, plus product information are in order. Frequency. Depending on how often new products need to be ordered, the frequency can vary from multiple times a day to once a week or month. It would usualy be once every few weeks in this case. Basic Course: 1. The use case begins when the admin types in the admin address in the URL; 2. The admin logs in with the necessary information and gains access to the admin site. 3. Table with the shops items are located in the database. 4. The admin can now edit the products (add new ones, delete existing or edit existing) 5. New products get a unique ID, old products keep their existing ID and deleted products ID s are removed. Alternate Course A: Description of the alternate course Condition: In order to create a new item which is included in an offer (2 for 1 price) along with a pre-existing item of the same type, the database must be able to identify both old and new item and add a rebate. 1. The administrator will create a new item in the databse whoch has been ordered, it must be included in an offer and therefore the ID of the new product will be identified with the old. 2. The offer for the two products separate ID will be registered whether there are bought 2 pieces of the old, two of the new, or one of each products. 3. The database knows when 2 items of the same ID are purchased, or when 2 seperate item ID s have a rebate. The rebate will automatically be deducted from the price. Post conditions Use Case Name: Customer purchase/checkout Identifier: UC3 Description: This use case will describe how a potential customer can complete and pay for a purchase. Preconditions 1. It is required that the customer has a payment method, like a credit card. 2. Customers need to be logged in before executing an order, and finishing off by paying. Assumptions Access to internet and all required login details plus payment details are in order. Frequency The customer can place as many orders and pay as many times as needed. There is no limit to the number of transactions. Basic Course 1. The use case begins when the customer is logged in and has a full shopping cart, the customer is ready to checkout and pay. 2. The customer fills in his/her shipping details 3. Payment options are given, before the checkout is complete. The customer types in their payment details. 4. When the purchase is complete, a success notification will appear on screen and a confirmation mail will be sent to the customers mail. Alternate Course A: Description of the alternate course Condition: The user has a full cart but is not logged in to complete the purchase. 1. When the customer wants to pay for the items, but is not logged in, a message will appear on screen asking the customer to log in to proceed. 2. When the customer has completed their login, the purchase can be completed as described in the aforementioned. Post conditions 1. If all has gone according to plan, the purchase should be a success, and a confirmation message will be prompted on screen for the customer. Actors: Local guitar shop 1. If the aforementioned steps were made, the specified items will be edited in the database. Actors: Local guitar shop. Notes: The reason why the admin must initiate the search in the URL: Is to make hacker attempts harder

10 Use Case Name: Administrator site traffic Identifier: UC4 Description: The use case will describe how the admin can track and follow the websites traffic, and hotspots. Preconditions 1. A Google account must be made and the shop website must be linked with it. Assumptions 1. Access to internet and all required login details for Google account and the shop are in order. Frequency Measuring the sites traffic can be done as many times as wished. It is advised to do it on a weekly or monthly interval, so an indication of trends can be measured more precisely and correctly. Basic Course 1. A Google account must already exist. 2. The shop website will be linked to one of Google s functions called Google analytics. 3. The Admin can now log on to their Google account whenever required, and view the site s traffic. 4. This can be used to determine hot trends on the website. Alternate Course A: Description of the alternate course Condition: The shop owners don t have an existing Google account to link to the site. 1. Create a new Google account on google.com. 2. Link the site to Google analytics as described in the aforementioned course. Post conditions 1. The owners of the shop should now be able to locate and see all incoming traffic, and the source of the traffic to the site. Actors: Local guitar shop Use Case Name: Users/customers search Identifier: UC5 Description: In this use case we explain how the users discover and search for products. Preconditions 1. Be on the website else no preconditions. Assumptions 1. Access to internet, is interrested in buying for example a guitar, strings and so no. Basic Course 1. Use case begins when the customer arrives to the website and uses the seach bar. 2. The user clicks search and is given examples of products, that the is has typed in. For example: user writes stratocaster in the search bar and the users now sees all stratocasters. 3. The users can now put it in the cart. Alternate Course A: Description of the alternate course Condition: 1. If the user have problems finding the desired product in the search bar, they can use the menu to get closer to what they are looking for. 2. Presses Brands in the menu bar, then is giving af list of diffrent brands. 3. Now the user can find the brand and model of the desired product. Post conditions 1. If the user(s) have found what he/she/they want, they are able to put it in the cart and go to check if logged in. Actors: Local guitar shop 18 19

11 Use Case CRUD Matrix Name: Seller package process. Identifier: UC6 Description: In this use case we will explain about the seller sending customers package. Preconditions 1. Customer has placed an order. Assumptions 1. Access to internet, the customer has placed an order and paid for the ordered products. Basic Course 1. Use case begins there is an order from a customer. 2. Then the seller checks if the products are in stock. 3. Seller the goes down to the local postal service, depending on which shipment method, the customer have chosen. 4. Then sends a mail to the customer that their order now has been shipped. Alternate Course A: Description of the alternate course Customer Product Cart/Order Zip Customer registration C C Admin add/remove U products Customer purchase R C U Admin site traffic R R R R Seller packaging R R R process Customer search R Condition: If the customer choses to have 2 shipments because one/some the products is out of stock. Then the seller must send the items over multiple shipments. 1. The user wants to have their ordered send by multiple shipments. 2. The seller must send the first package as usual. 3. First order is shipped and a shipment mail has been mailed to the customer. 4. The seller requests the product that is out of stock from the product supplier. 5. When the products are in stock again, the second package will now be shipped and a second order mail will be mailed to the customer. Post conditions 1. When everything has gone right, the customer have received the package and the money is received from customer

12 Kode Afslutning...23 Konklusion...24 Perspektivering...24 CREATE DATABASE eshop; USE eshop; CREATE TABLE zip( zip int PRIMARY KEY UNIQUE, city varchar(45) )engine=innodb; CREATE TABLE customers( cusid int PRIMARY KEY AUTO INCREMENT, cusname varchar(45) NOT NULL, cusadress varchar(45) NOT NULL, country varchar(45) NOT NULL, varchar(45) NOT NULL, password varchar(45) NOT NULL, zip_fkey int FOREIGN KEY (zip_fkey) REFERENCES zip(zip) )engine=innodb; CREATE TABLE products( prodid int PRIMARY KEY AUTO INCREMENT, prodname varchar(45) NOT NULL, price int NOT NULL, placeinstock NOT NULL, numberstock int NOT NULL, minnumberstock int NOT NULL )engine=innodb; CREATE TABLE order_items( orderid int PRIMARY KEY AUTO INCREMENT, orderstatus varchar(45), customer_cusid int FOREIGN KEY (customer_cusid) REFERENCES customer(cusid), )engine=innodb; CREATE TABLE cart_has_products( cart_customer_cusid int PRIMARY KEY AUTO INCREMENT, products_prodid int FOREIGN KEY (products_prodid) REFERENCES products(prodid) quantity int NOT NULL, )engine=innodb; // INSERT INSERT INTO zip (zip, city) VALUES ( 7000, Fredericia ); //INSERT for zip tabel // UPDATE. Her bliver et product opdateret hvor produkt id et er 1. UPDATE products SET prodname=fender Stratocaster, price=5000, placeinstock=hylde2, numberstock=7, minnumber- Stock=1 WHERE prodid=1; // DELETE. Dette sletter et produkt fratabellen products hvor id et er 1. DELETE FROM products WHERE prodid =

13 Konklusion & Refleksion Konklusion Meget af den data der er adgang til online, om det er en butik der sælger en bestemt vare, eller et bibliotek der indeholder information om bøger, anvender databaser. Dette gør det nemmere at holde styr på vigtig information der skal til for holde orden. Databaser kan også blive anvendt til at lagre data om medlemmer eller kunder, for f.eks at gøre det lettere for tilbagevendende kunder. I dette tilfælde skulle der laves en lille database der indeholder data om nogle varer, samt give en potentiel kunde mulighed for at checke ud efter et køb. Vi kan konkludere at vores mål er nået, idet vi har skabt en lille version af en simpel database, der indeholder information om varer og muligheden for at afslutte en handel. Vi har også anvendt use-cases for bedre at forklare og give en bedre forståelse af sammenhængen mellem køber og sælger i dette tilfælde. Refleksion Starten af projektet var følte gruppen sig presset, idet at vi lige havde holdt sommerferie og skulle igang med det samme. Skolen havde også fået nyt adresse og alt var endnu ikke faldt på plads, hvilket ikke gjorde situationen meget bedre. Vi startede ud med at lave en slagplan og lavede et gantt-kort dagen efter opgavens udlevering, for bedre at få et overblik planlægge arbejdsprocessen. Gruppen har haft god dynamik fra starten af, og medlemmerne havde en god sans for hvad der skulle laves og hvordan processen ville være. Arbejdskontrakten blev overholdt, dog var der nogle uheldige sygdage og fraværsdage hos nogle af medlemmerne til slut, hvilket der ikke kunne gøres så meget ved. Det resulterede i et mindre set-back for vores plan, men ikke noget der ikke kunne klares. Planen i en helhed, som vi havde lavet fra starten, blev holdt i god grad. 24