1 / 21

Database Design Concepts Info1408

Database Design Concepts Info1408. Week 5 Database Components. Objectives. Two basic concepts to explore: Conceptual Design Components Logical/Physical Design Components. Conceptual Design. Technology independent- ie will work on any database software An activity carried out by a.

natane
Download Presentation

Database Design Concepts Info1408

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 Design ConceptsInfo1408 Week 5 Database Components

  2. Objectives • Two basic concepts to explore: • Conceptual Design Components • Logical/Physical Design Components

  3. Conceptual Design • Technology independent- ie will work on any database software • An activity carried out by a

  4. Logical Design • Process of translating (mapping) the conceptual design to fit the chosen database model (relational, object oriented etc.) • An activity carried out by a

  5. Physical Design • Mapping the logical design to one or more physical designs • Tailored to the particular DBMS being used and the computer system on which the database will run. • An activity usually performed by a

  6. Entities • Something of interest to the activity we are trying to model • Could be a person, place, thing, concept about which data is collected • Just about anything that can be named with a noun can be an entity …we should restrict ourselves to things of interest to the users of our database.

  7. A very common entity that is found in many business oriented databases is the Conceptually this represents all the customers in the database ……… an individual customer is known as an of the entity CUSTOMER

  8. Attributes • ‘An attribute is a unit fact that characterises or describes an entity in some way’ In other words properties • Attributes can not be broken down into smaller units in any meaningful way … they are the smallest unit of information that is stored within the database • Examples could be name, address, telephone number of the customer

  9. Unique identifiers • An entity will be described using the attributes. For example a student could have name and results. • The problem is we need to be identify one student from another. • Most students can be identified form one another by their name however sometimes two students can have the same name. • How do I make sure I don’t award marks to the wrong student?

  10. I do this by adding an extra attribute known as the key field. • This is a unique identifier • Each student will have a different value for this attribute ie it is unique • What is your unique identifier ? • Remember these unique identifiers are often invented so are often not a property the subject would recognise.

  11. Examples of unique identifiers • National insurance number • Passport number • Membership number • Order number • Vehicle registration number • Bank account number • Remember that only one instance of the entity will have each individual value ie it is unique.

  12. CUSTOMER_ID COMPANY_NAME COMPANY_NAME ADDRESS CITY COUNTRY PHONE An entity is composed of an example: the customer entity can be represented as …. Entity CUSTOMER Unique identifier attributes

  13. Relationships • Relationships are the among entities • Relationships are represented at the conceptual level by lines joining entities together. • Each end of the relationship line shows the maximum cardinality of the relationship (maximum number of instances of one entity that can be associated with the entity at the other end of the relationship line)

  14. Entity-Relationship modelling • It is important to realise that there are a number of different ways of representing the details of relationships and cardinality • For the purposes of this module we want to explore the underpinning concepts involved … we will use one notational style …. You will come across different styles as you refer to different text books. • We will cover this later in the course

  15. Business Rules • Very important …… a policy, procedure or standard that an organisation has adopted. • These business practices must be reflected in the construction and functioning of the database • They may impose on the database design

  16. Business Rules • It is important to identify business rules during investigation of the data requirements. • Business rules will vary from organisation to organisation. It is important to identify the business rules for each relationship.

  17. Examples of Business Rules • A student can be enrolled on one course only- may be appropriate at a university • A student can be enrolled on more than one course – May be appropriate in a college. • A customer can place many orders. • An order is for one customer

  18. Logical Physical (1)Tables • Primary unit of storage in the relational model is the table • A two dimensional structure composed of rows and columns • Each row represents one occurrence (instance) of the entity ( or record) • Each column represents one attribute for that entity.

  19. For each attribute you must identify it’s properties. • Type- this can be • TEXT • NUMBER • DATE/TIME • CURENCY • Size- how big • Is it mandatory or optional

  20. Summary • You should be able to define the following terms • Entities • Attributes • Relationships • Business rules • Tables • Columns • Data types • Constraints

  21. References • Database Demystified by Andy Oppel

More Related