CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Chapter 9 Structuring System Data Requirements
Chapters 7 & 9 System Scope
Modern Systems Analysis and Design Third Edition
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
System Analysis - Data Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Entity Relationship Diagrams Basic Elements and Rules.
Chapter 14 (Web): Object-Oriented Data Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 10 Structuring System Requirements: Conceptual Data Modeling.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Data Modeling Advanced Concepts.
Entity Relationship Diagrams
Chapter 3: Modeling Data in the Organization
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 8 Structuring System Data Requirements
Data Modeling Introduction. Learning Objectives Define key data modeling terms –Entity type –Attribute –Multivalued attribute –Relationship –Degree –Cardinality.
CHAPTER 9: Structuring System Requirements: Conceptual Data Modeling Conceptual Data Modeling 1.1 MSIS 5653 Advanced Systems Development Dursun Delen,
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 3 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Importance of data modeling Importance of data modeling Write good.
Chapter 14: Object-Oriented Data Modeling
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
 Keys are special fields that serve two main purposes: ◦ Primary keys are unique identifiers of the relation in question. Examples include employee numbers,
Entity-Relationship modeling Transparencies
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
1 Web-Enabled Decision Support Systems Entity-Relationship Modeling Prof. Name Position (123) University Name.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Segment 5 Database Review International Islamic University Chittagong Campus.
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
Chapter 8 Structuring System Data Requirements
Chapter 8 Structuring System Data Requirements
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 8 Structuring System Data Requirements
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Structuring System Requirements: Conceptual Data Modeling 7.1.
ER to Relational Translation COMSATS INSTITUTE OF INFORMATION TECHNOLOGY, VEHARI.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Chapter 9 Structuring System Data Requirements. Objectives:  Define key data modeling terms.  Draw entity-relationship (E-R) and class diagrams to represent.
Chapter 11 & 12 Entity-Relationship (E-R) Model Characteristics of E-R Model Components of E-R Model Example of E-R Model Enhanced E-R Model.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Object-Oriented Data Modeling
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Modern Systems Analysis and Design Third Edition
Logical Database Design Transparencies 1. ©Pearson Education 2009 Objectives How to create a set of tables from an ER model. How to check that the tables.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Business System Development
Modern Systems Analysis and Design Third Edition
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Chapter 9 Structuring System Data Requirements
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Modern Systems Analysis and Design Third Edition
Chapter 1: The Database Environment
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
CS4222 Principles of Database System
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,

Objectives Upon completion of part I you will be able to: –Understand and be able to explain the concepts related to data modeling terms –Understand and be able to draw entity relationship diagrams –Understand and be able to explain the concepts related to conceptual data modeling –Understand and be able to explain the concepts related to distinguish between unary, binary, and ternary relationships –Understand and be able to explain the concepts related to defining rules for business use in E-R diagrams

Overview Data Modeling: Why is it Important? –Characteristics of data are crucial –Data are most complex aspects of information systems –Data characteristics reasonably permanent E-R Diagramming / Class Diagramming –Explain structure of data –Mastery is crucial to success

Conceptual Data Modeling What is a Conceptual Data Model –Representation of organizational data –Rules and meaning of data Conceptual Data Modeling Process –Develop model for existing system –Develop model for new system –Encapsulates all SDLC phases Deliverables –E-R diagram –Entries in data dictionary

Gathering Information Top-Down Approach –Understanding of the nature of the business –No specific information requirements Bottom-Up Approach –Specific business documents Computer displays Reports Business forms

Introduction to E-R Modeling Overview –E-R model –E-R Diagram Entities –Entity type –Entity instance –Naming and defining types –Attributes Naming and defining attributes Multi-valued attributes –Candidate keys and identifiers Relationships –Associations

Conceptual Data Modeling and the ER Model Degree of Relationship –Unary –Binary –Ternary Cardinalities in Relationships –Minimum –Maximum Naming and Defining Relationships –Naming guidelines –Guidelines for defining Associative Entities

Representing Supertypes & Subtypes Subtype –Sub grouping of entities Supertype –Generic entity type Relationship Rules –Total specialization –Partial specialization –Disjoint rule –Overlap rule

Business Rules Types of Business Rules –Entity integrity –Referential integrity constraints –Domains Domain definitions –Triggering operations Components –User rule –Event –Entity name –Condition –Action

Packaged Conceptual Data Models Overview –Comparatively low cost –Generic data models –Developed by specialists Types of Packaged Data Models –Universal –Industry specific Benefits –Time –Cost –Quality

Object Modeling Representing Objects and Classes –Object –State –Behavior –Object class –Class diagram –Operation Types of operations –Constructor –Query –Update –Scope Representing –Associations –Association Classes –Derived Attributes, Associations, and Roles –Generalization

Summary Conceptual Data Modeling Gathering Information E-R Modeling Supertypes and Subtypes Business Rules The Role of Packaged Conceptual Data Models Object Modeling