1 / 51

Database Systems

Database Systems. Information Systems Intermediate 2. Data and Information. Data is raw, unprocessed facts and figures. Data is collected, stored and processed by computers. Examples: 368 HR101FE 010468 Baker 25168. Data and Information.

maxwell-allen
Télécharger la présentation

Database Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Database Systems Information Systems Intermediate 2

  2. Data and Information • Data is raw, unprocessed facts and figures. • Data is collected, stored and processed by computers. • Examples: • 368 • HR101FE • 010468 • Baker • 25168

  3. Data and Information • Information is processed data with structure or meaning. • Information is useful to humans. • Examples: • Age: 36 years 8 months • Post Code: HR10 1FE • Date of Birth: 01/04/68 • Occupation: Baker • Total Spent: £251.68

  4. What is a database? • A database is a collection of related information about a set of persons or objects. • Traditionally, databases have been manual paper based systems. • Example: the “Yellow Pages”

  5. What is a database management system? • A database management system (DBMS) is a software package which is used to create, manipulate and present data from electronic databases. • Example of DBMSs include Microsoft Access and Filemaker Pro.

  6. Traditional databases • storage of paper records was very bulky • easy to mis-file a record, or records to be lost or damaged • data often duplicated in several records • keeping records up-to-date was difficult and time consuming, and often resulted in data inconsistency, where duplicated values were updated in one record but not in others • many people employed to maintain the records, which was costly • searching for records was time consuming • producing reports, such as sorted lists or data collated from several sources, was extremely time consuming, if not impossible

  7. Case Study: DVD Rentals Member Number Title Forename Surname Telephone No. 1012 Miss Isobel Ringer 293847 1034 Mr John Silver 142536 1056 Mr Fred Flintstone 817263 1097 Mrs Annette Kirton 384756

  8. Case Study: DVD Rentals DVD Code Title Cost Date Out Date Due Member Number Name 002 Finding Nemo £2.50 03/09/04 04/09/04 1034 John Silver 003 American Pie £2.50 27/08/04 28/08/04 1056 F Flintstone 01/09/04 02/09/04 Isobel Ringer 008 The Pianist £2.50 04/09/04 06/09/04 1097 Annette Kirton 011 Notting Hill £2.50 27/08/04 28/08/04 1012 I Ringer 04/09/04 06/09/04 1086 F Flintstone 014 Prime Suspect £2.00 27/08/04 28/08/04 Annette Kirton 015 Shrek £1.50 10/09/04 11/09/04 1034 Joan Silver

  9. Benefits of computerised databases • Searching, sorting and calculating operations can be performed much more quickly and easily. • Information is more easily available to users, due to improved methods of data retrieval. • Data integrity is improved resulting in more accurate information.

  10. Types of computerised database • Flat file • Relational

  11. Flat file databases

  12. Limitations of flat file databases • Data is very likely to be duplicated. • The duplication of data leads to the possibility of data inconsistency. • It is not possible to store information about a member without entering details of a DVD. This is called an insertion anomaly. • Removing a DVD from the database may remove the only record which stores details of a Member. This is called a deletion anomaly.

  13. Relational databases • A relational database stores data in more than one table. • The idea is to ensure that data is only entered and stored once, so removing the possibility of data duplication and inconsistency.

  14. Entities and Data Relationships • An entity represents a person or object. • e.g. Member, DVD Rental • Each entity has a set of attributes which describe examples or instances of that entity. • The attributes of the DVD Rental entity are code, title, cost, date out, date due and member number • The attributes of the Member entity are member number, name and telephone number.

  15. Entities, Attributes and Instances

  16. Entities, Attributes and Instances The Member entity is the whole table

  17. Entities, Attributes and Instances Each column stores one attribute, e.g. Member Name The Member entity is the whole table

  18. Entities, Attributes and Instances Each column stores one attribute, e.g. Member Name The Member entity is the whole table Each row stores one instance, e.g. Member 1034

  19. Entities, Attributes and Instances • An entity represents a person or object. • e.g. Member, DVD Rental • Each entity has a set of attributes which describe examples or instances of that entity. • The attributes of the DVD Rental entity are code, title, cost, date out, date due and member number • The attributes of the Member entity are member number, name and telephone number.

  20. Data Relationships • Three types of relationship: • One-to-one • One-to-many • Many-to-many

  21. Data Relationships • One-to-one

  22. Data Relationships • One-to-one • One-to-many

  23. Data Relationships • One-to-one • One-to-many • Many-to-many

  24. but there’s a problem… More than one table

  25. More than one table

  26. More than one table

  27. Keys • A key is a field, or set of fields, whose values uniquely identify a record. • In any table, there may be more than one field, or set of fields, which can uniquely identify each record—these are called candidate keys. • The candidate key which is chosen to be used is called the primary key.

  28. Keys • Member Number is a candidate key for the Member entity • MEMBER(Member Number, Name, Telephone Number)

  29. Keys • DVD Code is a candidate key for the DVD Rental entity • DVD RENTAL(DVD Code, Title, Cost, Date Out, Date Due, *Member Number) • Member Number is called a foreign key.

  30. Keys • DVD Code is a candidate key for the DVD Rental entity • DVD RENTAL(DVD Code, Title, Cost, Date Out, Date Due, *Member Number) • Member Number is called a foreign key.

  31. Keys • A foreign keyis a field which is not a primary key in its own table, but is a primary key in another table. • Member Number is a foreign key in the DVD table, because it is the primary key in the Member table. • Here is the data model: MEMBER(Member Number, Name, Telephone Number) DVD RENTAL(DVD Code, Title, Cost, Date Out, Date Due, *Member Number)

  32. Implementation • 3 steps: • Set-up the tables • Populate the tables • Manipulate and present the data

  33. Setting up the tables • Which tables are required? • Which fields are required? • What are the properties of each field?

  34. Setting up the tables • Which tables are required? • The tables correspond directly to the entities in the data model. • In this case, there will be two tables, Member and DVD Rental.

  35. Setting up the tables • Which fields are required? • The fields in each table are the attributes in each entity in the data model.

  36. Setting up the tables • What are the properties of each field? • Its name • be consistent!

  37. Setting up the tables • What are the properties of each field? • Its name • Its data type • text • numeric (integer, real, currency) • date or time • Boolean (yes or no) • link • object

  38. Setting up the tables • What are the properties of each field? • Its name • Its data type • Validation: • Presence check • Restricted Choice check • Range check

  39. Populating the tables • Take care to be accurate • Validation: make sure the data is sensible • Verification: make sure the date is correct • Verification methods: • Bar codes, OCR

  40. Manipulating the Data • Searching records • Sorting records • Calculating values • Presenting results

  41. Searching • Which fields will be used to identify the records required? • What are the search conditions for identifying the records required? • Which fields will be displayed? • E.g. Search for Test 3 = 10 • “Test 3 = 10” is called the search condition

  42. Searching: Boolean operators

  43. Searching: wildcard characters

  44. Searching: wildcard characters

  45. Wildcard Searches • Search for Surname = “*son”

  46. Complex Searches • A complex search involves more than one search condition (and usually more than one field) • Search for Test 3 = 10 AND Average > 6 • Search for Test 3 = 10 OR Average > 6 • Search for Test 3 > 5 AND Test 3 < 8 • Search for Test 3 < 2 OR Test 3 >9

  47. Sorting • Which field will be used to decide the order of records? This is called the sort key. • For the sort key, will the order of sorting be ascending or descending?

  48. Sorting • For a list of people with the tallest first • sort in descending order of height • For a list of people with youngest first • sort in ascending order of age • For alphabetical order • sort in ascendingorder of surname • “ascendingorder of surname” is called the sort condition

  49. Complex Sorting • A complex sort involves more than one sort condition involving two or more fields. • The main sort key is called the primary sort key, and the second one is called the secondary sort key. • “Telephone book” order: • Ascending order of Surname, then Ascending order of Forename

  50. Calculating • Use formulas or expressions to calculate a value for a record based on other values in the record

More Related