We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byHayden Powell
Modified over 2 years ago
© 2005 by Prentice Hall Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich
© 2005 by Prentice Hall 9-2 Learning Objectives Define key data modeling terms. Draw entity-relationship (E-R) and class diagrams to represent common business situations. Explain the role of conceptual data modeling in IS analysis and design. Distinguish between unary, binary, and ternary relationships. Define four types of business rules. Compare the capabilities of class diagrams vs. E-R diagrams. Relate data modeling to process and logic modeling.
© 2005 by Prentice Hall 9-3
© 2005 by Prentice Hall 9-4
© 2005 by Prentice Hall 9-5 Conceptual Data Modeling A detailed model that captures the overall structure of data in an organization Independent of any database management system (DBMS) or other implementation considerations
© 2005 by Prentice Hall 9-6 Process of Conceptual Data Modeling Develop a data model for the current system Develop a new conceptual data model that includes all requirements of the new system In the design stage, the conceptual data model is translated into a physical design Project repository links all design and data modeling steps performed during SDLC
© 2005 by Prentice Hall 9-7 Deliverables and Outcome Primary deliverable is an entity-relationship (E-R) diagram or class diagram As many as 4 E-R or class diagrams are produced and analyzed E-R diagram that covers data needed in the projects application E-R diagram for the application being replaced E-R diagram for the whole database from which the new applications data are extracted E-R diagram for the whole database from which data for the application system being replaced is drawn
© 2005 by Prentice Hall 9-8 Deliverables and Outcome (cont.) Second deliverable is a set of entries about data objects to be stored in repository or project dictionary. Repository links data, process, and logic models of an information system. Data elements included in the DFD must appear in the data model and vice versa. Each data store in a process model must relate to business objects represented in the data model.
© 2005 by Prentice Hall 9-9
© 2005 by Prentice Hall 9-10 Gathering Information for Conceptual Data Modeling Two perspectives Top-down Data model is derived from an intimate understanding of the business. Bottom-up Data model is derived by reviewing specifications and business documents.
© 2005 by Prentice Hall 9-11 Requirements Determination Questions for Data Modeling What are subjects/objects of the business? Data entities and descriptions What unique characteristics distinguish between subjects/objects of the same type? Primary keys What characteristics describe each subject/object? Attributes and secondary keys How do you use the data? Security controls and user access privileges
© 2005 by Prentice Hall 9-12 Requirements Determination Questions for Data Modeling (cont.) Over what period of time are you interested in the data? Cardinality and time dimensions Are all instances of each object the same? Supertypes, subtypes, and aggregations What events occur that imply associations between objects? Relationships and cardinalities Are there special circumstances that affect the way events are handled? Integrity rules, cardinalities, time dimensions
© 2005 by Prentice Hall 9-13 Introduction to Entity- Relationship (E-R) Modeling Entity-Relationship (E-R) Diagram A detailed, logical representation of the entities, associations and data elements for an organization or business Notation uses three main constructs Data entities Relationships Attributes
© 2005 by Prentice Hall 9-14 Person, place, object, event or concept about which data is to be maintained Entity type: collection of entities with common characteristics Entity instance: single entity named property or characteristic of an entity Association between the instances of one or more entity types
© 2005 by Prentice Hall 9-15 Identifier Attributes Candidate key Attribute (or combination of attributes) that uniquely identifies each instance of an entity type Identifier A candidate key that has been selected as the unique identifying characteristic for an entity type
© 2005 by Prentice Hall 9-16 Identifier Attributes (cont.) Selection rules for an identifier 1.Choose a candidate key that will not change its value. 2.Choose a candidate key that will never be null. 3.Avoid using intelligent keys. 4.Consider substituting single value surrogate keys for large composite keys.
© 2005 by Prentice Hall 9-17 Multivalued Attributes An attribute that may take on more than one value for each entity instance Represented on E-R Diagram in two ways: double-lined ellipse weak entity
© 2005 by Prentice Hall 9-18 Entity and Attribute Example Simple attributes Identifier attribute… each employee has a unique ID. Multivalued attribute… an employee may have more than one skill.
© 2005 by Prentice Hall 9-19 Degree of Relationship Degree: number of entity types that participate in a relationship Three cases Unary: between two instances of one entity type Binary: between the instances of two entity types Ternary: among the instances of three entity types
© 2005 by Prentice Hall 9-20
© 2005 by Prentice Hall 9-21 Cardinality The number of instances of entity B that can or must be associated with each instance of entity A Minimum Cardinality The minimum number of instances of entity B that may be associated with each instance of entity A Maximum Cardinality The maximum number of instances of entity B that may be associated with each instance of entity A Mandatory vs. Optional Cardinalities Specifies whether an instance must exist or can be absent in the relationship
© 2005 by Prentice Hall 9-22 Cardinality Symbols
© 2005 by Prentice Hall 9-23 Unary Relationship Example
© 2005 by Prentice Hall 9-24 Binary Relationship Examples
© 2005 by Prentice Hall 9-25 Associative Entities An entity type that associates the instances of one or more entity types and contains attributes that are peculiar to the relationship between those entity instances An associative entity is: An entity A relationship This is the preferred way of illustrating a relationship with attributes
© 2005 by Prentice Hall 9-26 A relationship with an attribute …as an associative entity
© 2005 by Prentice Hall 9-27 Ternary relationship …as an associative entity
© 2005 by Prentice Hall 9-28 A relationship that itself is related to other entities via another relationship must be represented as an associative entity.
© 2005 by Prentice Hall 9-29 Supertypes and Subtypes Subtype: a subrouping of the entities in an entity type that shares common attributes or relationships distinct from other subtypes Supertype: a generic entity type that has a relationship with one or more subtype
© 2005 by Prentice Hall 9-30 Rules for Supertype/Subtypes Relationships Total specialization: an entity instance of the supertype must be an instance of one of the subtypes Partial specialization: an entity instance of the supertype may or may not be an instance of one of the subtypes Disjoint: an entity instance of the supertype can be an instance of only one subtype Overlap: an entity instance of the supertype may be an instance of multiple subtypes
© 2005 by Prentice Hall 9-31
© 2005 by Prentice Hall 9-32 Business Rules Specifications that preserve the integrity of the logical data model Four types Entity integrity: unique, non-null identifiers Referential integrity constraints: rules governing relationships Domains: valid values for attributes Triggering operations: other business rules regarding attribute values
© 2005 by Prentice Hall 9-33 Domains The set of all data types and ranges of values that an attribute can assume Several advantages 1.Verify that the values for an attribute are valid 2.Ensure that various data manipulation operations are logical 3.Help conserve effort in describing attribute characteristics
© 2005 by Prentice Hall 9-34 Triggering Operations An assertion or rule that governs the validity of data manipulation operations such as insert, update and delete Components: User rule: statement of the business rule to be enforced by the trigger Event: data manipulation operation that initiates the operation Entity Name: name of entity being accessed or modified Condition: condition that causes the operation to be triggered Action: action taken when the operation is triggered
© 2005 by Prentice Hall 9-35
© 2005 by Prentice Hall 9-36 Packaged Data Models Generic data models that can be applied and modified for an organization Two categories Universal Industry-specific Benefits Reduced implementation time and cost High-quality modeling
© 2005 by Prentice Hall 9-37 Packaged data models provide generic models that can be customized for a particular organizations business rules
© 2005 by Prentice Hall 9-38 Object Modeling Using Class Diagrams Object-oriented approach Based on Unified Modeling Language (UML) Features Objects and classes Encapsulation of attributes and operations Polymorphism Inheritance
© 2005 by Prentice Hall 9-39 Objects Object: an entity with a well-defined role in an application Each object has: State: encompasses the attributes, their values, and relationships of an object Behavior: represents how an object acts and reacts Identity: uniqueness, no two objects are the same
© 2005 by Prentice Hall 9-40 Classes Class: a logical grouping of objects with similar attributes and behaviors Operation: a function or service provided by all instances of a class Encapsulation: the technique of hiding internal implementation details of an object from external view
© 2005 by Prentice Hall 9-41 Class Diagram A diagram showing the static structure of an object-oriented model UML classes are analogous to E-R entities
© 2005 by Prentice Hall 9-42 Types of Operations Constructor Creates a new instance of a class Query Accesses the state of an object Update Alters the state of an object Scope Applies to a full class rather than an individual instance
© 2005 by Prentice Hall 9-43 Representing Associations Association: a relationship among instances of object classes Association role: the end of an association where it connects to a class Multiplicity: indicates how many objects participate in a give relationship
© 2005 by Prentice Hall 9-44 UML associations are analogous to E-R relationships. UML multiplicities are analogous to E-R cardinalities.
© 2005 by Prentice Hall 9-45 Multiplicity notation: means minimum of 0 and maximum of 10 1, 2 means can be either 1 or 2 * means any number roles multiplicities
© 2005 by Prentice Hall 9-46 Association Class An association with its own attributes, operations, or relationships UML association classes are analogous to E-R associative entities.
© 2005 by Prentice Hall 9-47 Derived Attributes, Associations, and Roles Derived items are represented with a slash (/). Derived attributes are calculated based on other attributes
© 2005 by Prentice Hall 9-48 Generalization Superclass-subclass relationships Subclass inherits attributes, operations, and associations of the superclass Types of superclasses Abstract: cannot have any direct instances Concrete: can have direct instances
© 2005 by Prentice Hall 9-49 Generalization and inheritance implemented via superclass/subclasses in UML, supertypes/subtypes in E-R
© 2005 by Prentice Hall 9-50 Polymorphic Operations The same operation may apply to two or more classes in different ways Abstract operations defined in abstract classes defined the protocol, but not the implementation of an operation Methods the implementation of an operation
© 2005 by Prentice Hall 9-51 Polymorphism: Here, each type of student has its own version of calc-tuition() Abstraction: Student is an abstract class and calc- tuition() is an abstract operation (italicized) Class scope: tuitionPerCred is a class-wide attribute
© 2005 by Prentice Hall 9-52 Aggregation and Composition Aggregation A part-of relationship between a component and an aggregate object Composition An aggregation in which the part object belongs to only one aggregate object and lives and dies with the aggregate object
© 2005 by Prentice Hall 9-53 Aggregation is represented with open diamonds Composition is represented with filled diamonds
© 2005 by Prentice Hall 9-54 Summary In this chapter you learned how to: Define key data modeling terms. Draw entity-relationship (E-R) and class diagrams to represent common business situations. Explain the role of conceptual data modeling in IS analysis and design. Distinguish between unary, binary, and ternary relationships. Define four types of business rules. Compare the capabilities of class diagrams vs. E- R diagrams. Relate data modeling to process and logic modeling.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 10 Object-Oriented Analysis and Modeling Using the UML.
Entity Relationship (ER) Modeling The ER Model Developing and ER Diagram Extended ER Model Entity Integrity : Selecting Primary Key Chapter 4.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 6: Entity-Relationship.
1 Notes content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. System Models IS301 – Software.
Monica Farrow EM G30 Material on Vision Er 1 F28DM: Database Management Systems The Entity Relationship Model.
Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an.
Entity/Relationship Modelling. Topics To Be Covered In This Lecture Entity/Relationship models Entities and Attributes Relationships Attributes E/R Diagrams.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Chapter 12 Object-Oriented Design.
ITS232 Introduction To Database Management Systems Siti Nurbaya Ismail Faculty of Computer Science & Mathematics, Universiti Teknologi MARA (UiTM), Kedah.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Software Re-use IS301 – Software.
1 Data Modeling : ER Model N. L. Sarda I.I.T. Bombay.
Database Application Lifecycle Lecture Lectures Objectives Put all the previous lectures into context (Conceptual and Logical Design, Normalisation.
Architectural Design IS301 – Software Engineering Lecture # 14 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
Chapter 6 Architectural Design Slide 1 Chapter 6 Architectural Design.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Object- Oriented Design IS301 –
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
ISBN Prentice-Hall, 2006 Chapter 5 Designing the System Copyright 2006 Pearson/Prentice Hall. All rights reserved.
©Silberschatz, Korth and Sudarshan8.1Database System Concepts Chapter 8: Object-Oriented Databases Need for Complex Data Types The Object-Oriented Data.
Conceptual / semantic modelling 1. 2 Overview design; conceptual design; ER model concepts; semantic aspects; problems; Enhanced ER (EER) modelling; transforming.
1 © 2014 by McGraw-Hill Education. This is proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Chapter 14 Design with Reuse.
3 Entity Relationship (E-R) Modeling. 3 2 In this lecture, you will learn: What a conceptual model is and what its purpose is The difference between internal.
Database Design: ER Modelling (Continued) Reading: C&B, Chaps 11,12&16.
9/2/2014 1Yan Huang - ER Chapter 6: ER – Entity Relationship Diagram Major components of ER diagram Major components of ER diagram Practices Practices.
CII Saxion Hogeschool Enschede 1 Object georiënteerd Ontwerpen met UML Saxion Hogeschool Enschede, januari 2005.
© 2016 SlidePlayer.com Inc. All rights reserved.