IS 421 Information Systems Analysis James Nowotarski 7 October 2002.
-
date post
19-Dec-2015 -
Category
Documents
-
view
216 -
download
0
Transcript of IS 421 Information Systems Analysis James Nowotarski 7 October 2002.
![Page 1: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/1.jpg)
IS 421Information Systems Analysis
James Nowotarski
7 October 2002
![Page 2: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/2.jpg)
• Understand basics of data modeling:– Defining entities
– Defining attributes
– Defining relationships
– Drawing entity-relationship diagrams (ERDs)
Today’s Objectives
![Page 3: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/3.jpg)
Course Map
Contents
1. Introduction
Planning Phase2. Project Initiation3. Project Management
Analysis Phase4. Systems Analysis5. Gathering Information6. Process Modeling7. Data Modeling
1 2 3 4 6 7 8 9 10 115
Assignments
QuizzesFinal
Week
CoreExamReview
![Page 4: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/4.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 5: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/5.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion45 minutes
*** Bears vs. Packers begins
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 6: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/6.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 7: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/7.jpg)
SDLC
The systems development life cycle (SDLC) is a description of the phases of an information system
Planning Analysis Design Implementation
![Page 8: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/8.jpg)
Key Definitions
• The As-Is system is the current system and may or may not be computerized
• The To-Be system is the new system that is based on updated requirements
![Page 9: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/9.jpg)
Analysis Phase
![Page 10: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/10.jpg)
Analysis Phase
FromPlanningPhase:
System requestFeasibility analysisWorkplan . . .
DevAnalysisPlan
Examine-As-is
IdentifyImprove-ments
DevelopBasicSystemConcepts
DevelopDataModel
DevelopProcessModel
PrepareProposal
ToDesignPhase:
Deliverables:
Analysis Plan Functional Requirements
Quality Requirements
SystemConcept
Data Model
Process Model
System Proposal
Develop Conceptfor To-Be System
![Page 11: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/11.jpg)
Analysis Phase
FromPlanningPhase:
System requestFeasibility analysisWorkplan . . .
DevAnalysisPlan
Examine-As-is
IdentifyImprove-ments
DevelopBasicSystemConcepts
DevelopDataModel
DevelopProcessModel
PrepareProposal
ToDesignPhase:
Develop Conceptfor To-Be System
Gather Analyze Specify
![Page 12: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/12.jpg)
Three Fundamental Analysis Strategies
• Business process Automation (BPA)• Business Process Improvement (BPI)• Business Process Reengineering (BPR)
![Page 13: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/13.jpg)
High-Level Work Plan for Analysis
Step Deliverable Technique
Planning PhaseAnalysis Phase
Examine As-Is System Information SummariesUse CasesProcess ModelData Model
Gather Information
Develop Process ModelDevelop Data Model
Identify Improvements Ideas for System Problem AnalysisRoot Cause AnalysisDuration AnalysisActivity-based CostingInformal BenchmarkingFormal BenchmarkingOutcome AnalysisBreaking AssumptionsTechnology AnalysisActivity EliminationProxy BenchmarkingProcess Simplification
Develop Concept for To-Be System
System ConceptUse CasesProcess ModelData Model
Gather Information
Develop Process ModelDevelop Data Model
![Page 14: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/14.jpg)
Begin with the End in Mind
• Table of contents• Executive summary• System request• Work plan• Analysis strategy• Recommended
system• Feasibility analysis
• Process model• Data model• Appendices
System Proposal Outline
![Page 15: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/15.jpg)
Information Gathering Techniques
• Interviewing• Joint application design• Questionnaires• Document Analysis• Observation
![Page 16: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/16.jpg)
Interviews -- Five Basic Steps
• Selecting Interviewees• Designing Interview Questions• Preparing for the Interview• Conducting the Interview• Post-Interview Follow-up
![Page 17: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/17.jpg)
Types of Questions
Types of Questions Examples
Closed-Ended Questions * How many telephone orders are received per day?
* How do customers place orders?* What additional information would you like the new system to provide?
Open-Ended Questions * What do you think about the current system?* What are some of the problems you face on a daily basis?* How do you decide what types of marketing campaign to run?
Probing Questions * Why?* Can you give me an example?* Can you explain that in a bit more detail?
![Page 18: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/18.jpg)
Interview Report
INTERVIEW REPORT
Interview notes approved by: ____________
Person interviewed ______________Interviewer _______________Date _______________Primary Purpose:
Summary of Interview:
Open Items:
Detailed Notes:
![Page 19: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/19.jpg)
JAD Key Ideas
• Allows project managers, users, and developers to work together
• May reduce scope creep by 50%• Avoids requirements being too specific or too
vague
![Page 20: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/20.jpg)
Joint Application Design (JAD) Important Roles
• Facilitator• Scribe
![Page 21: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/21.jpg)
JAD Meeting Room
JPEG Figure 5-5 Goes Here
![Page 22: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/22.jpg)
Questionnaire Steps
• Selecting participants
– Using samples of the population• Designing the questionnaire
– Careful question selection• Administering the questionnaire
– Working to get good response rate• Questionnaire follow-up
– Send results to participants
![Page 23: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/23.jpg)
Document Analysis
• Provides clues about existing “as-is” system• Typical documents
– Forms
– Reports
– Policy manuals• Look for user additions to forms• Look for unused form elements
![Page 24: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/24.jpg)
Observation
• Users/managers often don’t remember everything they do• Checks validity of information gathered other ways• Behaviors change when people are watched• Careful not to ignore periodic activities
– Weekly … Monthly … Annual
![Page 25: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/25.jpg)
Selecting the Appropriate Techniques
Interviews JAD Questionnaires Document Observation Analysis
Type of As-Is As-Is As-Is As-Is As-IsInformation Improve. Improve. Improve. To-Be To-Be
Depth of High High Medium Low LowInformation
Breadth of Low Medium High High LowInformation
Integration Low High Low Low Lowof Info.
User Medium High Low Low LowInvolvement
Cost Medium Low- Low Low Low- Medium Medium
![Page 26: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/26.jpg)
Summary
• There are five major information gathering techniques that all systems analysts must be able to use: Interviews, JAD, Questionnaires, Document Analysis, and Observation.
• Systems analysts must also know how and when to use each as well as how to combine methods.
![Page 27: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/27.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 28: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/28.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 29: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/29.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 30: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/30.jpg)
Data Modeling in the Analysis Phase
FromPlanningPhase:
System requestFeasibility analysisWorkplan . . .
DevAnalysisPlan
Examine-As-is
IdentifyImprove-ments
DevelopBasicSystemConcepts
DevelopDataModel
DevelopProcessModel
PrepareProposal
ToDesignPhase:
Deliverables:
Analysis Plan Functional Requirements
Quality Requirements
SystemConcept
Data Model
Process Model
System Proposal
Develop Conceptfor To-Be System
![Page 31: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/31.jpg)
Key Definitions
• A data model is a– Formal representation of the data to be used
for a business system.
• A data model should illustrate:– The people, places and things about which
data is collected,
– And how they are related to each other
![Page 32: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/32.jpg)
Key Definitions
• A logical data model shows the logical organization of data– Without regard for how data gets stored,
created or manipulated• A physical data model shows how the data
will physically be stored in the database (secondary memory).– E.g. Oracle may store a customer table in
several files (cust1.dbf, cust2.dbf…) that span several hard drives.
![Page 33: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/33.jpg)
Key Definitions
• Logical data model (Wixom and Dennis)• Data model• Conceptual data model• Entity model• Entity-relationship model• Entity-attribute-relationship model• Information model• Semantic data model
The collective output from logical data modeling is called various names
![Page 34: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/34.jpg)
Data Modeling
• Entity-relationship diagram (ERD)• Entity descriptions• Attribute descriptions• Relationship descriptions• Domain descriptions (not covered here)
A logical data model deliverable includes an ERD and descriptions of entities, attributes, and relationships
Components of a Logical Data Model
![Page 35: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/35.jpg)
An ERD Example
![Page 36: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/36.jpg)
• Entities generally represent people, places, and things of interest to the organization (about which we would like to collect data).
• Represented as rectangle on the ERD
• Named with a singular noun (e.g., Patient)
What Is an Entity?
![Page 37: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/37.jpg)
Entities and Instances
Instances are occurrences of an entity
![Page 38: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/38.jpg)
What is an Attribute?
• An attribute is a characteristic or property of an entity.
• Attributes contain information that describes an entity.
• Attribute names are nouns (e.g, “name”).• Sometimes entity name is added at the
beginning of the attribute name (e.g., “vendor_name”).
![Page 39: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/39.jpg)
Examples of Attributes
• Entity: Person– Attributes:
• first_name• last_name• eye_color• date_of_birth• address
• Entity: Classroom– Attributes:
• room_no• max_capacity
![Page 40: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/40.jpg)
An ERD Example
![Page 41: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/41.jpg)
Identifiers
• An identifier uniquely identifies each instance of the entity. It may consist of one or more attributes.
• Identifiers are also known generically as keys– Candidate keys = all identifiers for an entity
– Primary key = candidate key designated as “official” identifier
![Page 42: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/42.jpg)
Examples of Identifiers
• What attribute uniquely identifies every instance of these entities?– Student
– Classroom
– Vehicle
![Page 43: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/43.jpg)
Depicting Entities, Attributes and Identifiers
Entity name
Attributes
Identifier
Or, usecd_id (PK)
![Page 44: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/44.jpg)
An ERD Example
![Page 45: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/45.jpg)
Relationships
• Relationships represent connections, links, or associations between entities
• e.g., Patient-Appointment
• Relationships have some important properties:
1. Names, that should be active verbs– (A patient schedules appointments)
2. Cardinality
3. Modality.
![Page 46: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/46.jpg)
Cardinality
• Cardinality refers to the number of times instances in one entity can be related to instances in another entity– One instance in an entity refers to one and only one
instance in the related entity (1:1)
– One instance in an entity refers to one or more instances in the related entity (1:M)
– One or more instances in an entity refer to one or more instances in the related entity (M:M)
![Page 47: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/47.jpg)
Modality
• Modality refers to the minimum number of times that an instance in one entity can be related to an instance in another entity– One means that an instance in the related entity must
exist for an instance in another entity to be valid
– Zero means that no instance in the related entity is necessary for an instance in another entity to be valid
![Page 48: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/48.jpg)
Some Ways to Depict Relationships
Patient Appointment
Patient Appointment
Patient Appointment
Patient Appointment
1 M
schedules
schedules
Is scheduled by
Same
e.g., A patient may have zero to
many appointments
![Page 49: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/49.jpg)
Meanings of the Crow’s Feet
Min MaxCardinality
0 1
1 1
0 M[any]
1 M[any]
![Page 50: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/50.jpg)
The Entity-Relationship Diagram (ERD)
![Page 51: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/51.jpg)
An ERD Example
![Page 52: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/52.jpg)
What Is an ERD?
• A picture of the logical data model, – i.e., an ERD shows the information created,
stored, and used by a business system.
![Page 53: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/53.jpg)
An ERD ExampleA patient must have at least 1 appointment
![Page 54: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/54.jpg)
Topic Duration
• Recap Last Week 20 minutes
• Recap Assignments 1-2 10 minutes
• Quiz 45 minutes
*** Break 15 minutes
• Data Modeling: Lecture/Discussion 45 minutes
• Data Modeling: Group Exercises 45 minutes
• Assignment 3 Intro 10 minutes
Today’s agenda
![Page 55: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/55.jpg)
Exercise• SkyHigh Airlines has three major resources: airplanes, pilots, and crew members. Pilots and crew members have home bases, which they return at the end of an assigned flight. A flight must have exactly one pilot and one or more additional crew members along with an airplane. Each
airplane has a maintenance base.
• Draw an ERD showing:• Entities• Relationships
• Cardinality• Modality
• 10 minutes
![Page 56: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/56.jpg)
Group Exercise
• Textbook, p.209, Exercise D-1• Show:
• Entities• Attributes• Identifier(s)• Relationships
• Cardinality• Modality
• 15 minutes
![Page 57: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/57.jpg)
Still More Definitions
• A foreign key is all of these things:• a primary key of one entity (sometimes called parent
entity),
• duplicated in another entity (child entity)
• provides a common linkage between the two entities
![Page 58: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/58.jpg)
Foreign Key Example
• Customer(cust_id (PK), cust_name)• Order (ord_no (PK), cust_id (FK), ord_date)
Customers(Parent)
cust_id cust_name
100 Slick Willy, Inc.
200 George_W, Co.
300 Gore, Ltd.…
ord no cust_id ord_date
2100 200 13-Sep-2000
2101 100 14-Nov-20002102 100 23-Dec-20002103 100 24-Dec-2000…
Orders(Child)
A foreign key is a primary key of one entity that is duplicated in another entity to provide a common linkage between entities. Why use them?
PKFKCust_id
![Page 59: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/59.jpg)
Entity Types1. Independent2. Dependent3. Intersection
![Page 60: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/60.jpg)
Independent Entities
• An independent entity exists without the help of another entity– Common entities such as student, professors,
customers, products
– The identifier is created by the entity’s own attributes
– Usually on the “1” side of a relationship
– a.k.a. fundamental entity (in Visual Analyst, e.g.) or strong entity
![Page 61: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/61.jpg)
Dependent Entities
• Alternatively, a dependent entity cannot exist without the help of another entity– Special entities such as emp_dependent
(needs an employee to exist)
– The identifier is usually based on another entity’s attributes (emp_ssn & dep_ssn)
– Usually on the “M” side of a relationship
– a.k.a. attributive entity (in Visual Analyst, e.g.) or weak entity
![Page 62: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/62.jpg)
Intersection entities
• An intersection entity exists based on the relationship between two entities.– They have attributes that are peculiar to the
relationship between those entity instances, not the individual entities themselves
– They are created to store information about two entities sharing an M:M relationship
– a.k.a. associative entities, gerunds
![Page 63: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/63.jpg)
Intersection Entity Example
A student may take many classes.A class may have many students.Where are grades stored?
Student Class
An instance in the student entity is related to _____instances in the class entity.
An instance in the class entity is related to _____instances in the student entity.
RosterStudent Class
![Page 64: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/64.jpg)
An ERD Example: CD’s Relationships Expanded
![Page 65: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/65.jpg)
An Intersection Entity Example
A CD may be a part of many orders.
An order may contain many CDs.
The CD-order relationship is M:M.
Where do you store quantity of CD’s on an
order?
![Page 66: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/66.jpg)
Adding Intersection Entities
1. Create an intersection entity
(line item).
3. The “1” side goes
on the original
entities.
2. Move the “M’s” are adjacent to
the intersection entity.
![Page 67: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/67.jpg)
M:N to 1:Ms
• Rule: The M always go to the intersection entity. Why?
Orders
CD_No CD_Title Order_No CD_No Qty Order_No234 Best of Lawrence Welk 100101 234 12 100101235 Living Daylights Soundtrack 100101 236 3 100102236 Moody Blues Greatest Hits 100102 234 5 100108
100102 235 2100102 236 6100108 236 1
CD Line Items
![Page 68: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/68.jpg)
Creating An Entity-Relationship Diagram
![Page 69: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/69.jpg)
Steps in Building Data Models1. Review existing data models2. Define entities
a. Independentb. Dependent, including Intersection entities
3. Define attributes and keys (primary, foreign)4. Define relationships5. Finalize ERD6. Normalize7. Integrate data models as required8. Verify completeness of the data model9. Validate the data model
a. With usersb. With the enterprise’s data administrator
![Page 70: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/70.jpg)
Design Guidelines
• Best practices rather than rigid rules• Entities should have many instances (don’t include
fixed items such as stationery headings)• Avoid unnecessary attributes (outside the scope of
your system)• Apply correct cardinality and modality• Labels reflect common business terms• Assumptions should be clearly stated
![Page 71: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/71.jpg)
Summary
• The ERD is the most common technique for drawing data models. The building blocks of the ERD are:– Entities (nouns), describe people, places, or
things– Attributes (nouns), capture information about
the entity– Relationships (active verb sentences)
associate data across entities; they have cardinality and modality
![Page 72: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/72.jpg)
End of Slides - Extra slides follow
![Page 73: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/73.jpg)
Metaphors
ER Model Relational Model
Database Spreadsheet
Entity Relation Table, File Table
Instance Tuple Record Row
Attribute Attribute Field Column
Identifier Key Key Key
![Page 74: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/74.jpg)
Identifiers
• An identifier should have the following characteristics:– Its value should not change over the life of
each instance
– Its value should never be “null” or empty
– It should be composed of the minimal number (preferably one) of attributes required to ensure uniqueness
![Page 75: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/75.jpg)
Some Ways to Depict Relationships
Entity 1 Entity 2
Entity 1 Entity 2
Entity 1 Entity 2
1:1
1:M
1:0 or M
![Page 76: IS 421 Information Systems Analysis James Nowotarski 7 October 2002.](https://reader036.fdocuments.net/reader036/viewer/2022062516/56649d365503460f94a0dbec/html5/thumbnails/76.jpg)
Data Modeling
To identify entity types, look for nouns in the requirements
Customers will access the Internet sales system to look for CDs of interest. Some customers will search for specific CDs or CDs by specific artists, whereas other customers want to browse for interesting CDs in certain categories (e.g., rock, jazz, classical). When the customer has found all the CDs he or she wants, the customer will check out by providing personal information regarding the order (e.g., the CDs to purchase and quantity for each item). The system will verify the customer’s credit card information with an on-line credit card clearance center and either accept the order or reject it.
- Dennis & Wixom, p.159