D.dsgn + dbms


Published on


Published in: Design
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

D.dsgn + dbms

  1. 1. Systems Analysis and Design 8 th Edition Chapter 9 Data Design
  2. 2. Chapter Objectives <ul><li>Explain data design concepts and structures </li></ul><ul><li>Describe file processing systems </li></ul><ul><li>Explain database systems and define the components of a database management system (DBMS) </li></ul><ul><li>Describe Web-based data design </li></ul>
  3. 3. Chapter Objectives <ul><li>Explain data design terminology, including entities, fields, common fields, records, files, tables, and key fields </li></ul><ul><li>Describe data relationships, draw an entity relationship diagram, define cardinality, and use cardinality notation </li></ul><ul><li>Explain the concept of normalization </li></ul><ul><li>Explain the importance of codes and describe various coding schemes </li></ul>
  4. 4. Chapter Objectives <ul><li>Describe relational and object-oriented database models </li></ul><ul><li>Explain data warehousing and data mining </li></ul><ul><li>Differentiate between logical and physical storage and records </li></ul><ul><li>Explain data control measures </li></ul>
  5. 5. Introduction <ul><li>You will develop a physical plan for data organization, storage, and retrieval </li></ul><ul><li>Begins with a review of data design concepts and terminology, then discusses file-based systems and database systems, including Web-based databases </li></ul><ul><li>Concludes with a discussion of data storage and access, including strategic tools such as data warehousing and data mining, physical design issues, logical and physical records, data storage formats, and data controls </li></ul>
  6. 6. Data Design Concepts <ul><li>Data Structures </li></ul><ul><ul><li>Each file or table contains data about people, places, things or events that interact with the information system </li></ul></ul><ul><ul><li>File-oriented system </li></ul></ul><ul><ul><li>File processing system </li></ul></ul><ul><ul><li>Database system </li></ul></ul>
  7. 7. Data Design Concepts <ul><li>Overview of File Processing </li></ul><ul><ul><li>File processing can be efficient and cost-effective in certain situations </li></ul></ul><ul><ul><li>Potential problems </li></ul></ul><ul><ul><ul><li>Data redundancy </li></ul></ul></ul><ul><ul><ul><li>Data integrity </li></ul></ul></ul><ul><ul><ul><li>Rigid data structure </li></ul></ul></ul>
  8. 8. Data Design Concepts <ul><li>Overview of File Processing </li></ul><ul><ul><li>Various types of files </li></ul></ul><ul><ul><ul><li>Master file </li></ul></ul></ul><ul><ul><ul><li>Table file </li></ul></ul></ul><ul><ul><ul><li>Transaction file </li></ul></ul></ul><ul><ul><ul><li>Work file </li></ul></ul></ul><ul><ul><ul><li>Security file </li></ul></ul></ul><ul><ul><ul><li>History file </li></ul></ul></ul>
  9. 9. Data Design Concepts <ul><li>The Evolution from File Systems to Database Systems </li></ul><ul><ul><li>A database management system (DBMS) is a collection of tools, features, and interfaces that enables users to add, update, manage, access, and analyze the contents of a database </li></ul></ul><ul><ul><li>The main advantage of a DBMS is that it offers timely, interactive, and flexible data access </li></ul></ul>
  10. 10. Data Design Concepts <ul><li>The Evolution from File Systems to Database Systems </li></ul><ul><ul><li>Some Advantages </li></ul></ul><ul><ul><ul><li>Scalability </li></ul></ul></ul><ul><ul><ul><li>Economy of scale </li></ul></ul></ul><ul><ul><ul><li>Enterprise-wide application – database administrator (DBA) </li></ul></ul></ul><ul><ul><ul><li>Controlled redundancy </li></ul></ul></ul><ul><ul><ul><li>Data independence </li></ul></ul></ul>
  11. 11. DBMS Components <ul><li>Interfaces for Users, Database Administrators, and Related Systems </li></ul><ul><ul><li>Users </li></ul></ul><ul><ul><ul><li>Query language </li></ul></ul></ul><ul><ul><ul><li>Query by example (QBE) </li></ul></ul></ul><ul><ul><ul><li>SQL (structured query language) </li></ul></ul></ul><ul><ul><li>Database Administrators </li></ul></ul><ul><ul><ul><li>A DBA is responsible for DBMS management and support </li></ul></ul></ul>
  12. 12. DBMS Components <ul><li>Interfaces for Users, Database Administrators, and Related Systems </li></ul><ul><ul><li>Related information systems </li></ul></ul><ul><ul><ul><li>A DBMS can support several related information systems that provide input to, and require specific data from, the DBMS </li></ul></ul></ul><ul><ul><ul><li>No human intervention is required for two-way communication </li></ul></ul></ul>
  13. 13. DBMS Components <ul><li>Data Manipulation Language </li></ul><ul><ul><li>A data manipulation language (DML) controls database operations, including storing, retrieving, updating, and deleting data </li></ul></ul><ul><li>Schema </li></ul><ul><ul><li>The complete definition of a database, including descriptions of all fields, tables, and relationships, is called a schema </li></ul></ul><ul><ul><li>You also can define one or more subschemas </li></ul></ul>
  14. 14. DBMS Components <ul><li>Physical Data Repository </li></ul><ul><ul><li>The data dictionary is transformed into a physical data repository, which also contains the schema and subschemas </li></ul></ul><ul><ul><li>The physical repository might be centralized, or distributed at several locations </li></ul></ul><ul><ul><li>ODBC – open database connectivity </li></ul></ul><ul><ul><li>JDBC – Java database connectivity </li></ul></ul>
  15. 15. Web-Based Database Design <ul><li>Characteristics of Web-Based Design </li></ul>
  16. 16. Web-Based Database Design <ul><li>Internet Terminology </li></ul><ul><ul><li>Web browser </li></ul></ul><ul><ul><li>Web page </li></ul></ul><ul><ul><li>HTML (Hypertext Markup Language) </li></ul></ul><ul><ul><li>Tags </li></ul></ul><ul><ul><li>Web server </li></ul></ul><ul><ul><li>Web site </li></ul></ul>
  17. 17. Web-Based Database Design <ul><li>Internet Terminology </li></ul><ul><ul><li>Intranet </li></ul></ul><ul><ul><li>Extranet </li></ul></ul><ul><ul><li>Protocols </li></ul></ul><ul><ul><li>Web-centric </li></ul></ul><ul><ul><li>Clients </li></ul></ul><ul><ul><li>Servers </li></ul></ul>
  18. 18. Web-Based Database Design <ul><li>Connecting a Database to the Web </li></ul><ul><ul><li>Database must be connected to the Internet or intranet </li></ul></ul><ul><ul><li>Middleware </li></ul></ul><ul><ul><ul><li>Adobe ColdFusion </li></ul></ul></ul><ul><li>Data Security </li></ul><ul><ul><li>Well-designed systems provide security at three levels: the database itself, the Web server, and the telecommunication links that connect the components of the system </li></ul></ul>
  19. 19. Data Design Terminology <ul><li>Definitions </li></ul><ul><ul><li>Entity </li></ul></ul><ul><ul><li>Table or file </li></ul></ul><ul><ul><li>Field </li></ul></ul><ul><ul><li>Record </li></ul></ul>
  20. 20. Data Design Terminology <ul><li>Key Fields </li></ul><ul><ul><li>Primary key </li></ul></ul><ul><ul><li>Candidate key </li></ul></ul><ul><ul><li>Foreign key </li></ul></ul><ul><ul><li>Secondary key </li></ul></ul>
  21. 21. Data Design Terminology <ul><li>Referential Integrity </li></ul><ul><ul><li>Validity checks can help avoid data input errors </li></ul></ul><ul><ul><li>In a relational database, referential integrity means that a foreign key value cannot be entered in one table unless it matches an existing primary key in another table </li></ul></ul><ul><ul><li>Orphan </li></ul></ul>
  22. 22. Entity-Relationship Diagrams <ul><li>Drawing an ERD </li></ul><ul><ul><li>The first step is to list the entities that you identified during the fact-finding process and to consider the nature of the relationships that link them </li></ul></ul><ul><ul><li>A popular method is to represent entities as rectangles and relationships as diamond shapes </li></ul></ul>
  23. 23. Entity-Relationship Diagrams <ul><li>Types of Relationships </li></ul><ul><ul><li>Three types of relationships can exist between entities </li></ul></ul><ul><ul><li>One-to-one relationship (1:1) </li></ul></ul><ul><ul><li>One-to-many relationship (1:M) </li></ul></ul><ul><ul><li>Many-to-many relationship (M:N) </li></ul></ul>
  24. 24. Entity-Relationship Diagrams <ul><li>Cardinality </li></ul><ul><ul><ul><li>Cardinality notation </li></ul></ul></ul><ul><ul><ul><li>Crow’s foot notation </li></ul></ul></ul><ul><ul><ul><li>Unified Modeling Language (UML) </li></ul></ul></ul><ul><ul><ul><li>Now that you understand database elements and their relationships, you can start designing tables </li></ul></ul></ul>
  25. 25. Normalization <ul><li>Standard Notation Format </li></ul><ul><ul><li>Designing tables is easier if you use a standard notation format to show a table’s structure, fields, and primary key </li></ul></ul><ul><ul><li>Example: NAME ( FIELD 1 , FIELD 2, FIELD 3) </li></ul></ul>
  26. 26. Normalization <ul><li>Repeating Groups and Unnormalized Design </li></ul><ul><ul><li>Repeating groups </li></ul></ul><ul><ul><ul><li>Often occur in manual documents prepared by users </li></ul></ul></ul><ul><ul><li>Unnormalized </li></ul></ul><ul><ul><li>Enclose the repeating group of fields within a second set of parentheses </li></ul></ul>
  27. 27. Normalization <ul><li>First Normal Form </li></ul><ul><ul><li>A table is in first normal form (1NF) if it does not contain a repeating group </li></ul></ul><ul><ul><li>To convert, you must expand the table’s primary key to include the primary key of the repeating group </li></ul></ul>
  28. 28. Normalization <ul><li>Second Normal Form </li></ul><ul><ul><li>A table design is in second normal form (2NF) if it is in 1NF and if all fields that are not part of the primary key are functionally dependent on the entire primary key </li></ul></ul><ul><ul><li>A standard process exists for converting a table from 1NF to 2NF </li></ul></ul><ul><ul><li>The objective is to break the original table into two or more new tables and reassign the fields so that each nonkey field will depend on the entire primary key in its table </li></ul></ul>
  29. 29. Normalization <ul><li>Third Normal Form </li></ul><ul><ul><li>3NF design avoids redundancy and data integrity problems that still can exist in 2NF designs </li></ul></ul><ul><ul><li>A table design is in third normal form (3NF) if it is in 2NF and if no nonkey field is dependent on another nonkey field </li></ul></ul><ul><ul><li>To convert the table to 3NF, you must remove all fields from the 2NF table that depend on another nonkey field and place them in a new table that uses the nonkey field as a primary key </li></ul></ul>
  30. 30. Normalization <ul><li>A Normalization Example </li></ul>
  31. 31. Using Codes During Data Design <ul><li>Overview of Codes </li></ul><ul><ul><li>Because codes often are used to represent data, you encounter them constantly in your everyday life </li></ul></ul><ul><ul><li>They save storage space and costs, reduce data transmission time, and decrease data entry time </li></ul></ul><ul><ul><li>Can reduce data input errors </li></ul></ul>
  32. 32. Using Codes During Data Design <ul><li>Types of Codes </li></ul><ul><ul><li>Sequence codes </li></ul></ul><ul><ul><li>Block sequence codes </li></ul></ul><ul><ul><li>Alphabetic codes </li></ul></ul><ul><ul><li>Significant digit codes </li></ul></ul><ul><ul><li>Derivation codes </li></ul></ul><ul><ul><li>Cipher codes </li></ul></ul><ul><ul><li>Action codes </li></ul></ul>
  33. 33. Using Codes During Data Design <ul><li>Developing a Code </li></ul><ul><ul><li>Keep codes concise </li></ul></ul><ul><ul><li>Allow for expansion </li></ul></ul><ul><ul><li>Keep codes stable </li></ul></ul><ul><ul><li>Make codes unique </li></ul></ul><ul><ul><li>Use sortable codes </li></ul></ul>
  34. 34. Using Codes During Data Design <ul><li>Developing a Code </li></ul><ul><ul><li>Avoid confusing codes </li></ul></ul><ul><ul><li>Make codes meaningful </li></ul></ul><ul><ul><li>Use a code for a single purpose </li></ul></ul><ul><ul><li>Keep codes consistent </li></ul></ul>
  35. 35. Steps in Database Design <ul><li>Create the initial ERD </li></ul><ul><li>Assign all data elements to entities </li></ul><ul><li>Create 3NF designs for all tables </li></ul><ul><li>Verify all data dictionary entries </li></ul><ul><ul><li>After creating your final ERD and normalized table designs, you can transform them into a database </li></ul></ul>
  36. 36. Database Models <ul><li>Relational Databases </li></ul><ul><ul><li>The relational model was introduced during the 1970s and became popular because it was flexible and powerful </li></ul></ul><ul><ul><li>Because all the tables are linked, a user can request data that meets specific conditions </li></ul></ul><ul><ul><li>New entities and attributes can be added at any time without restructuring the entire database </li></ul></ul>
  37. 37. Database Models <ul><li>Object-Oriented Databases </li></ul><ul><ul><li>Many systems developers are using object-oriented database (OODB) design </li></ul></ul><ul><ul><ul><li>Object Management Group (OMG) </li></ul></ul></ul><ul><ul><ul><li>Each object has a unique object identifier </li></ul></ul></ul>
  38. 38. Data Storage and Access <ul><li>Data storage and access involve strategic business tools </li></ul><ul><li>Strategic tools for data storage and access </li></ul><ul><ul><li>Data warehouse – dimensions </li></ul></ul><ul><ul><li>Data mart </li></ul></ul><ul><ul><li>Data Mining </li></ul></ul>
  39. 39. Data Storage and Access <ul><li>Logical and Physical Storage </li></ul><ul><ul><li>Logical storage </li></ul></ul><ul><ul><ul><li>Characters </li></ul></ul></ul><ul><ul><ul><li>Data element or data item </li></ul></ul></ul><ul><ul><ul><li>Logical record </li></ul></ul></ul><ul><ul><li>Physical storage </li></ul></ul><ul><ul><ul><li>Physical record or block </li></ul></ul></ul><ul><ul><ul><li>Buffer </li></ul></ul></ul><ul><ul><ul><li>Blocking factor </li></ul></ul></ul>
  40. 40. Data Storage and Access <ul><li>Data Coding and Storage </li></ul><ul><ul><li>Binary digits </li></ul></ul><ul><ul><li>Bit </li></ul></ul><ul><ul><li>Byte </li></ul></ul><ul><ul><li>EBCDIC, ASCII, and Binary </li></ul></ul><ul><ul><li>Unicode </li></ul></ul>
  41. 41. Data Storage and Access <ul><li>Data Coding and Storage </li></ul><ul><ul><li>Storing dates </li></ul></ul><ul><ul><ul><li>Y2K Issue </li></ul></ul></ul><ul><ul><ul><li>Most date formats now are based on the model established by the International Organization for Standardization (ISO) </li></ul></ul></ul><ul><ul><ul><li>Absolute date </li></ul></ul></ul>
  42. 42. Data Control <ul><li>User ID </li></ul><ul><li>Password </li></ul><ul><li>Permissions </li></ul><ul><li>Encryption </li></ul><ul><li>Backup </li></ul><ul><li>Recovery procedures </li></ul><ul><li>Audit log files </li></ul><ul><li>Audit fields </li></ul>
  43. 43. Chapter Summary <ul><li>Files and tables contain data about people, places, things, or events that affect the information system </li></ul><ul><li>DBMS designs are more powerful and flexible than traditional file-oriented systems </li></ul><ul><li>An entity-relationship diagram (ERD) is a graphic representation of all system entities and the relationships among them </li></ul>
  44. 44. Chapter Summary <ul><li>A code is a set of letters or numbers used to represent data in a system </li></ul><ul><li>The most common database models are relational and object-oriented </li></ul><ul><li>Logical storage is information seen through a user’s eyes, regardless of how or where that information actually is organized or stored </li></ul>
  45. 45. Chapter Summary <ul><li>Physical storage is hardware-related and involves reading and writing blocks of binary data to physical media </li></ul><ul><li>File and database control measures include limiting access to the data, data encryption, backup/recovery procedures, audit-trail files, and internal audit fields </li></ul><ul><li>Chapter 9 complete </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.