Systems Analysis and Design in a Changing World, 6th Edition

Slides:



Advertisements
Similar presentations
Chapter 6: Entity-Relationship Model (part I)
Advertisements

Concepts of Database Management Seventh Edition Chapter 6 Database Design : ERD Model.
Entity Relationship (ER) Modeling
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Modeling the Data: Conceptual and Logical Data Modeling
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain how.
ISMT221 Information Systems Analysis and Design Entity-Relationship Diagram Lab 4 Tony Tam.
System Analysis - Data Modeling
Agenda for Week 1/31 & 2/2 Learn about database design
Overview Objective: refine information gathered
2Object-Oriented Analysis and Design with the Unified Process Events and Use Cases  Use case  Activity the system carries out  Entry point into the.
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Systems Analysis and Design in a Changing World, 6th Edition
Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,
Chapter 5: Modeling Systems Requirements: Events and Things
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
Modeling System Requirements:
SA Capstone Requirements and Design Week 5 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso Some slides adapted from: Systems Analysis.
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis and Design in a Changing World, Thursday, Feb 22
Module Title? Data Base Design 30/6/2007 Entity Relationship Diagrams (ERDs)
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
IS 325 Notes for Wednesday September 4, Syllabus Change I eliminated quizzes I increased the points allocated to homework assignments.
Copyright (c) 2014 Pearson Education, Inc. Introduction to Databases.
SA Capstone Requirements and Design Week 5 SYST Winter 2014
Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
R McFadyen Chapter 7 Conceptual Data Modeling.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Domain Modeling Part1: Entity Relationship Diagram Chapter 4 pp part 1 1.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
7-1 © Prentice Hall, 2004 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH SATZINGER.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
7-1 © Prentice Hall, 2007 Week 5: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Data Modeling IST210 Class Lecture.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain.
CS 370 Database Systems Lecture 9 The Relational model.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Modeling System Requirements: Events and Things. Objectives Explain the many reasons for creating information system models Describe three types of models.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
Chapter 7 Data Modeling with Entity Relationship Diagrams
Systems Analysis and Design in a Changing World, 6th Edition
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
advanced data modeling
CIS 321—IS Analysis & Design Chapter 5: Modeling System Requirements—Events and Things.
Chapter 8 Entity-Relationship Modeling Pearson Education © 2009.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Data Modeling and Entity-Relationship Model I
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
Database Design Chapters 17 and 18.
Business System Development
DATA REQIREMENT ANALYSIS
Domain Class Diagram Chapter 4 Part 2 pp
Database Systems: Design, Implementation, and Management Tenth Edition
MIS2502: Data Analytics Relational Data Modeling
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Chapter 7: Entity-Relationship Model
MIS2502: Data Analytics Relational Data Modeling 2
Presentation transcript:

Systems Analysis and Design in a Changing World, 6th Edition Chapter 4 Systems Analysis and Design in a Changing World, 6th Edition

Domain Classes Systems Analysis and Design in a Changing World 6th Ed Chapter 4 Systems Analysis and Design in a Changing World 6th Ed Satzinger, Jackson & Burd

Systems Analysis and Design in a Changing World, 6th Edition Chapter 4 Outline “Things” in the Problem Domain Data entities Domain classes The Domain Model Class Diagram The Entity-Relationship Diagram Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Overview Chapter 3 Functional Requirements Events Cases Chapter 4 Data entities / Classes Attributes Systems Analysis and Design in a Changing World, 6th Edition

“Things” in the Problem Domain The specific area (or domain) of the users’ business Scope of the system What “things” does the business need to track info? Examples of “Things” products, sales, shippers, customers, invoices, payments, etc. Called “classes” (UML) or “entities” “Things” eventually modelled If you don’t care about the “thing”, don’t model it! Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Types of Things Are there any tangible things? Are there any organizational units? Sites/locations? Are there incidents or events that need to be recorded? Systems Analysis and Design in a Changing World, 6th Edition

Details about Entities/Classes Attribute describes one piece of information about each instance of the class Customer has first name, last name, phone number Identifier or key One attribute uniquely identifies an instance of the class. Required for data entities, optional for domain classes. Customer ID identifies a customer Compound attribute Two or more attributes combined into one structure to simplify the model. (E.g., address rather than including number, street, city, state, zip separately). Sometimes an identifier or key is a compound attribute. Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Attributes and Values Class is a type of thing. Object is a specific instance of the class. Each instance has its own values for an attribute Systems Analysis and Design in a Changing World, 6th Edition

Associations Among Things Association— a naturally occurring relationship between classes (UML term) Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Just to Clarify… Called association on class diagram in UML Multiplicity is term for the number of associations between classes: 1 to 1 or 1 to many We are emphasizing UML in this text Called relationship on ERD in database class Cardinality is term for number of relationships in entity relationship diagrams: 1 to 1 or 1 to many Associations and Relationships apply in two directions Read them separately each way A customer places an order An order is placed by a customer Systems Analysis and Design in a Changing World, 6th Edition

Minimum and Maximum Multiplicity Associations have minimum and maximum constraints Minimum: Zero or one Maximum: one or many Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Types of Associations Binary Association Unary Association (recursive) Ternary Association (three) Systems Analysis and Design in a Changing World, 6th Edition

A Simple Domain Model Class Diagram Note: This diagram matches the semantic net shown previously A customer places zero or more orders An order is placed by exactly one customer An order consists of one or more order items An order item is part of exactly one order Systems Analysis and Design in a Changing World, 6th Edition

UML Notation for Multiplicity Systems Analysis and Design in a Changing World, 6th Edition

Domain Model Class Diagram for course enrollment at a university Where is each student’s grade remembered in this model? Each section has many grades and each grade is association with a student Each student has many grades and each grade is association with a section Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Refined Course Enrollment Model with an Association Class CourseEnrollment Association class— an association that is treated as a class in a many to many association because it has attributes that need to be remembered, such as grade Systems Analysis and Design in a Changing World, 6th Edition

Generalization/Specialization Inheritance for RMO Three Types of Sales Abstract class— a class that allow subclasses to inherit characteristics but never gets instantiated. In Italics (Sale above) Concrete class— a class that can have instances Systems Analysis and Design in a Changing World, 6th Edition

Whole Part Relationships Computer and its Parts Note: this is composition, with diamond symbol. Whole part can have multiplicity symbols, too (not shown) Systems Analysis and Design in a Changing World, 6th Edition

RMO CSMS Project Complete Domain Model Class Diagram Systems Analysis and Design in a Changing World, 6th Edition

Example of ERD Notation A simple ERD without showing attributes Systems Analysis and Design in a Changing World, 6th Edition

ERD Cardinality Symbols often called the crows feet notation Systems Analysis and Design in a Changing World, 6th Edition

Expanded ERD with Attributes Note: This diagram matches the semantic net shown previously Also matches a domain model class diagram shown previously Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition At the end of the day… Determine entities (things in the domain) Attributes (of entities) Keys (Primary, Foreign) Data types (integer, string, etc) Relationships (which entities are related) Cardinality (how are entities related) Systems Analysis and Design in a Changing World, 6th Edition

Systems Analysis and Design in a Changing World, 6th Edition Running Case Studies SBRU – Domain Class Model (example 4.14). Just brainstorm OTSC – Domain Class Model (example 4.14). Just brainstorm SMD – Draw out the diagram, walk us through the changes. Systems Analysis and Design in a Changing World, 6th Edition