...CIV E 603: Information Modeling and Database Systems Lecture 1 1 What to Study? Introduction to Data base Relational Model Database design Structured Query Language (SQL) 22 Let’s begin the journey !! …. in to fascinating world of databases 23 Today’s outline Database Management System (DBMS) Entity-Relationship (ER) Model 24 What is a database? Many people would like to call it organization… 25 What is a database? Database is a structured collection of related data. Many name it efficiency… 26 A database is A home for data – since that is where data stay… A manager for data – since data are organized neatly… A GOOGLE for data – since a particular record can be found in a snap… A guardian for data – since a database rejects malicious accesses… … 27 What is a Database? Database: is a collection of related data Data: known facts that can be recorded and that have implicit meaning Properties of database: • represents some aspect of the real world (mini-world -UoD) • logically coherent collection of data with some inherent meaning. A random assortment of data cannot correctly be referred to as a database. • designed, built, and populated with data for a specific purpose. It has an intended groups of users. 28 What is a Database? A database can be of any size and of varying complexity. • For example, the list of...
Words: 2400 - Pages: 10
...CECS 6605 Advanced Database Systems Assignment 1 Deadline: September 8, 2013 Part I. Entity Relationship Diagrams (ERD) Database Design Using Entity-Relationship Diagrams (2003) by Sikha Bagui and Richard Earp Auerbach Publications ISBN:0849315484 Chapter 1 (Database Design Using Entity-Relationship Diagrams) * Checkpoint 1.1, Problem 1; pp. 13-14 * Checkpoint 1.3, Problem 1, 3; pp. 25 Chapter 2 (Database Design Using Entity-Relationship Diagrams) * Checkpoint 2.1, Problems 1, 3, 5, 7; pp. 39 * Checkpoint 2.3, Problems 1, 3; pp. 61 Chapter 3 (Database Design Using Entity-Relationship Diagrams) * Checkpoint 3.1, Problems 1, 3, 5; pp. 78 Chapter 4 (Database Design Using Entity-Relationship Diagrams) * Checkpoint 4.1, Problems 1, 3, 5; pp. 99 * Checkpoint 4.3, Problems 1, 3; pp. 117 Part II. SQL A Guide to SQL (2008) by Philip J. Pratt and Mary Z. Last Use only Oracle for this part. Please show the complete question, query used, and print the query results. Do the exercises from the Henry Books Database. Chapter 1 (A Guide to SQL, Henry Books) * Exercises - odd numbers Chapter 2 (A Guide to SQL, Henry Books) * Exercises - odd numbers Chapter 3 (A Guide to SQL, Henry Books) * Exercises - odd numbers Chapter 4 (A Guide to SQL, Henry Books) * Exercises - odd numbers Part III. Database System Fundamentals Fundamentals of Database Systems (2011) by Ramez Elmasri; Shamkant B. Navathe ...
Words: 352 - Pages: 2
...OBJECT-RELATIONAL DATABASE MODELING USING UML Table of Contents Introduction……………………………………………………………………………………..4 Overview of ER Modeling and UML…………………………………………………………...4 UML Meta-model……………………………………………………………………………… 6 UML Components………………………………………………………………………………7 UML Data Profile……………………………………………………………………………….9 UML Diagrams……………………………………………………………………………….....10 UML Diagram Classification – Static, Dynamic, and Implementation…....................................12 4+1 View of UML Diagrams……………………………………………………………………13 Object-oriented Class Model and Relational Database Model..............................................…...14 Use of UML to develop Ontologies…………………………………………………………..…17 References……………………………………………………………………………………….19 Abstract The Unified Modeling Language (UML) is being used as the de-facto standard in the software industry. With the adoption of UML 2.0, the new enhancements allow this version to describe many of the elements found in today's software technology as well as Model Driven Architecture and Service-Oriented Architecture. Many existing software applications involve complex application layer implemented in object-oriented programming languages and at the same time use relational database systems as the back-end data store. Modeling the whole system in a consistent manner will help developers and end users better understand the application. The Unified Modeling Language (UML) is a standard language for modeling software and database systems. Data...
Words: 3708 - Pages: 15
...Logical Design, Part I Wayne Murphy Strayer University Introduction to Relational Database Management System CIS111019VA016-1132-001 Jean-Robert Bokino January 11, 2013 Logical Design, Part I In this assignment, I will write a two to three page paper titled “Logical Design, Part 1” whereas I am a recently hired consultant for ACME Global Consulting to procure requirements for a large database. In this scenario, “Logical Design, Part 1”, I will develop a database management systems to convince a set of clients of the benefits of using the Entity–Relationship model (E-R) in developing a database. In addition, my management would like the following points addressed in my design: (1). List the advantages of a relational model specific to ACME Global Consulting. (2). Summarize the purpose of an Entity–Relationship Model (E-R) specific to ACME Global Consulting. (3). List and describe essential components of the model such as entities, attributes, keys, relationships, roles, and dependencies specific to ACME Global Consulting. (4). Describe the need for the enhanced E-R model and how we can create sophisticated models to help us in complex environments. (5). Outline and describe the advantage of using the relational model. (6). Create an E-R diagram using graphical depicting software that could theoretically be used in a restaurant application. Now that you know the purpose of this assignment, I will define three key terms that will be discussed in this assignment. The first term...
Words: 1493 - Pages: 6
...Introduction: The importance of conceptual models same: understand the problem before you start constructing a solution. There are two important things to keep in mind when learning about and doing data modeling: 1. Data modeling is first and foremost a tool for communication.Their is no single “right” model. Instead, a valuable model highlights tricky issues, allows users, designers, and implementors to discuss the issues using the same vocabulary, and leads to better design decisions. 2. The modeling process is inherently iterative: you create a model, check its assumptions with users, make the necessary changes, and repeat the cycle until you are sure you understand the critical issues. In this background lesson, you are going to use a data modeling technique—specifically, EntityRelationship Diagrams (ERDs)—to model the business scenario from Lesson 2. The data model you create in this lesson will form the foundation of the database that you use throughout the remaining lessons. Before you sit down in front of the keyboard and start creating a database application, it is critical that you take a step back and consider your business problem—in this case, the kitchen supply scenario presented in Lesson 2— from a conceptual point of view. To facilitate this process, a number of conceptual modeling techniques have been developed by computer scientists, psychologists, and consultants. ? For our purposes, we can think of a conceptual model as a picture of the information...
Words: 7007 - Pages: 29
... | | |College of Information Systems & Technology | | |DBM/380 Version 9 | | |Database Concepts | | |July 16, 2012 to August 13, 2012 | | |Group KM11BIT13 | Copyright © 2012, 2010, 2008, 2007, 2006, 2005, 2003 by University of Phoenix. All rights reserved. Course Description This course covers database concepts. Topics include data analysis, the principal data models with emphasis on the relational model, entity-relationship diagrams, database design, normalization, and database administration. Policies Faculty and students will be held responsible for understanding and adhering to all policies contained within the following two documents: • University policies: You must be logged into the student website to view this document. • Instructor policies: This document is posted in the Course Materials forum. University policies are subject to change. Be...
Words: 3236 - Pages: 13
...Chen’s: The Entity Relationship Model 1106IFSM4106382 Professor Joseph Walker Understanding Peter Chen’s: The Entity Relationship Model In a database, there is a starting point in making your database perform correctly. An Entity-Relationship Model is an actual illustration of structured data from a top-down approach to the database. The end product of the modeling process is an entity-relationship diagram. In the first stage of information system design you use a model during the precondition study to describe information needs or the type of information that is stored in the database. The data model can be used to describe any overview of used terms and their relationship in a certain area of interest like in a database. Dr. Chen introduced this model to show the semantic information of the real world. Many alternatives have appeared since his original model. The goal of this paper is to look at the Chen’s Entity Relationship Model and the current Object–Oriented data Model and compare them. Entity Relationship Data Modeling (ERDM) had been around, Dr. Peter Chen adopted the entity relationship model and brought it to the front and expanded its use. Dr. Chen added a more natural view that the real world consists of entities and relationships like mothers and daughters or fathers and sons and branch off from their like a family tree. Entity relationship modeling try’s to show data objects and data relationships in two components on a single page by using a language...
Words: 631 - Pages: 3
...DATABASE MODELING AND DESIGN The Morgan Kaufmann Series in Data Management Systems (Selected Titles) Joe Celko’s Data, Measurements and Standards in SQL Joe Celko Information Modeling and Relational Databases, 2nd Edition Terry Halpin, Tony Morgan Joe Celko’s Thinking in Sets Joe Celko Business Metadata Bill Inmon, Bonnie O’Neil, Lowell Fryman Unleashing Web 2.0 Gottfried Vossen, Stephan Hagemann Enterprise Knowledge Management David Loshin Business Process Change, 2nd Edition Paul Harmon IT Manager’s Handbook, 2nd Edition Bill Holtsnider & Brian Jaffe Joe Celko’s Puzzles and Answers, 2 Joe Celko nd Location-Based Services ` Jochen Schiller and Agnes Voisard Managing Time in Relational Databases: How to Design, Update and Query Temporal Data Tom Johnston and Randall Weis Database Modeling with MicrosoftW Visio for Enterprise Architects Terry Halpin, Ken Evans, Patrick Hallock, Bill Maclean Designing Data-Intensive Web Applications Stephano Ceri, Piero Fraternali, Aldo Bongio, Marco Brambilla, Sara Comai, Maristella Matera Mining the Web: Discovering Knowledge from Hypertext Data Soumen Chakrabarti Advanced SQL: 1999—Understanding Object-Relational and Other Advanced Features Jim Melton Database Tuning: Principles, Experiments, and Troubleshooting Techniques Dennis Shasha, Philippe Bonnet SQL: 1999—Understanding Relational Language Components Jim Melton, Alan R. Simon Information Visualization in Data Mining and Knowledge Discovery Edited by Usama Fayyad, Georges G. Grinstein...
Words: 89336 - Pages: 358
...CS251-1301B-03 Fundamentals of Database Systems Phase 1 -5 Individual Project Robert March 24th, 2013 Table of Contents Project Outline 3 Description of the Database Design Life Cycle 4 The Entity Relationship Diagram 7 The Logical Model and Normalization 9 The Microsoft Access Database 11 The Microsoft Access Database Application 14 References: 18 Project Outline My idea for a project concept is for a granite fabrication and installation company called MasterStoneWorks. We will perform counter sales, contractor and walk-in customer kitchen and bath design, templates, fabrication, installation, and follow-up. To run efficiently (or at all) we must have a centralized DBMS with access for all employees in order to keep track of the progress of the workload and get the products delivered and installed on time. Issues with the process must be immediately known and corrected as this is a high value product with a small profit margin at this point in our economy. Any miscommunication can be disastrous. The MasterStoneWorks database will have the following tables: * Customers * Sales * Installs * Product choices * Costs (wholesale and retail) * Sales people * Project Managers * Templates * Follow-up * Customer support Description of the Database Design Life Cycle The seven steps of the SDLC/DBDSL: 1. Concept Planning – This first step is where the need to develop, or improve a system is ascertained...
Words: 1691 - Pages: 7
...entry forms The _____ data model is a tool for constructing data models. entityrelationship A _____ is a self-describing collection of integrated records. database 21. _____ is an example of a personal DBMS. access 22. _____ is the process of converting a data model into tables, relationships, and data constraints. database design 23. The _____ problem is unique to a multiuser database environment. lost-update _____ show data in a structured context. reports A ______ is a collection of forms, reports, queries, and programs that process a database. database application ______ is a popular enterprise DBMS. DB2 ______ is the most popular diagramming tool for database applications. E-R 27. ______ is the process of converting a poorly structured table into two or more well-structured tables. normalization 28. ______ process logic that is specific to a given business record. application programs ______ softwares assist in creating, maintaining, and manipulating databases. DBMS A(n) _____ DBMS is designed to process large organizational and workgroup databases. enterprise A(n) _____ is a column or group of columns that identifies a unique row in a table. key All the following steps involved in transforming a data model into a relational database design except _____. each attribute of the entity becomes a row of the table Applications use DBMS for all of the following operations except _____ data. exchange 20. 24. 25. 26. 29. 30. 31. 32. Brenda...
Words: 1054 - Pages: 5
...Chapter 5 Normalization of Database Tables Discussion Focus Why are some table structures considered to be bad and others good and how do you recognize the difference between good and bad structures? From an information management point of view, possibly the most vexing and destructive problems are created through uncontrolled data redundancies. Such redundancies produce update and delete anomalies that create data integrity problems. The loss of data integrity can destroy the usefulness of the data within the database. (If necessary, review Chapter 1, Section 1.4.4, “Data Redundancy”, to make sure that your students understand the terminology and that they appreciate the dangers of data redundancy.) Table structures are poor whenever they promote uncontrolled data redundancy. For example, the table structure shown in Figure IM5.1 is poor because it stores redundant data. In this example, the AC_MODEL, AC_RENT_CHG, and AC_SEATS attributes are redundant. (For example, note that the hourly rental charge of $58.50 is stored four times, once for each of the four Cessna C-172 Skyhawk aircraft – check records 1, 2, 4, and 9.) Figure IM5.1 A Poor Table Structure [pic] |[pic] The figures shown in this discussion show the contents of the IM_Discussion database. This database is located on the teacher’s CD. The | |Student Online Companion also includes SQL script files (Oracle and SQLServer) for all of the data sets used throughout the book. ...
Words: 9797 - Pages: 40
...The Entity-Relationship Unified View of Data PETER PIN-SHAN Massachusetts Model-Toward a CHEN Institute of Technology A data model, called the entity-relationship model, is proposed. This model incorporates some of the important semantic information about the real world. A special diagrammatic technique is introduced as a tool for database design. An example of database design and description using the model and the diagrammatic technique is given. Some implications for data integrity, information retrieval, and data manipulation are discussed. The entity-relationship model can be used as a basis for unification of different views of data: t,he network model, the relational model, and the entity set model. Semantic ambiguities in these models are analyzed. Possible ways to derive their views of data from the entity-relationship model are presented. Key Words and Phrases: database design, logical view of data, semantics of data, data models, entity-relationship model, relational model, Data Base Task Group, network model, entity set model, data definition and manipulation, data integrity and consistency CR Categories: 3.50, 3.70, 4.33, 4.34 1. INTRODUCTION The logical view of data has been an important issue in recent years. Three major data models have been proposed: the network model [2, 3, 71, the relational model [S), and the entity set model [25]. These models have their own strengths and weaknesses. The network model provides a more natural...
Words: 9678 - Pages: 39
...Week One: Database Architecture | | Details | Due | Points | Objectives | 1.1 Explain database architectures. 1.2 Define database systems. 1.3 Define relational database architecture. | | | Reading | Read Ch. 1, “Database Systems,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Read Ch. 2, “Data Models,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Read Ch. 3, “The Relational Database Model,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Reference Ch. 1, “Getting Started,” of Database Concepts as a supplemental reading. | 9/24 | | Reading | Read Ch. 1, “Introduction to Access,” of Exploring Microsoft® Office Access 2010 Comprehensive. | 9/24 | | Reading | Read this week’s Electronic Reserve Readings. | 9/24 | | Participation | Participate in class discussion. | All week | 2 | Nongraded Activities and Preparation SkillSoft® Registration | The first time you access SkillSoft®, you need to register.Do the following to register for SkillSoft®: Go to https://uopx.skillport.com Register by clicking on Register. The Register button is in the lower right corner, below the login boxes.Leave the Organization Code field blank.Use your phoenix.edu e-mail address.Use your student website login name as your user ID (the name before the @email.phoenix.edu).Click Submit. | 9/24 | ...
Words: 2242 - Pages: 9
...Relational database Relational databases are the standard when creating industrial standard efficient and scalable databases. They are based on a structure of tables which are logically connected to each other and can be queried in complex way to extract relevant and meaningful information. The querying of a relational database is done using a high level language called SQL which stands for structured query language. SQL is very easy to understand and unlike traditional programming languages does not rely on arcane syntax, rather structured query language uses English like meaningful syntax in its operations. As opposed to flat file databases this logical organization of data across tables in the form of columns greatly simplifies the organization and retrieval of highly complex data. As the business needs of the client rises so will the size and complexity of data, on of the biggest advantages of relational databases is the scalability associated with them, so as the company grows expanding the database will not be a problem and making sense of the data and extracting meaningful information from it will only get slightly harder. Relational databases come with a plethora of security options and views can be enforced to ensure that unauthorized access to the sensitive information in the database is not allowed. Relational databases also avoid redundancy of information and such databases can be highly optimized by methods such as normalization and good database design to ensure...
Words: 652 - Pages: 3
...is Database Normalization? Database normalization is the process of organizing the columns (attributes) and tables (relations) of a relational database to minimize data redundancy. Normalization involves decomposing a table into less redundant (and smaller) tables without losing information; defining foreign keys in the old table referencing the primary keysof the new ones. The objective is to isolate data so that additions, deletions, and modifications of an attribute can be made in just one table and then propagated through the rest of the database using the defined foreign keys. The relational model separates the logical design from the physical design: DBMS performance is a matter of physical designer using indexes, view materialization, big buffers, etc. It is not a matter of changing the logical design. A typical example of normalization is that an entity's unique ID is stored everywhere in the system but its name is held in only one table. The name can be updated more easily in one row of one table. A typical update in such an example would be the RIM company changing its name to BlackBerry. That update would be done in one place and immediately the correct "BlackBerry" name would be displayed throughout the system. Example Querying and manipulating the data within a data structure that is not normalized, such as the following non-1NF representation of customers' credit card transactions, involves more complexity than is really necessary: 2. What us Entity Relationship...
Words: 527 - Pages: 3
