Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships l Define cardinality, cardinality notation, and crow’s foot notation l Demonstrate the use of structured English, decision tables, and decision trees to develop information system process descriptions l Explain the relationships among data flow diagrams, the data dictionary, and process descriptions

Lecture 92 l Data terminology and concepts l Relationships among data objects l Entity-relationship diagrams (ERDs) Data Analysis - Introduction

Lecture 93 l Data design includes –Entities –Fields –Records –Files –Keys Data Terminology and Concepts

Lecture 94 l Definition –Entity: a person, place, thing, or event for which data is collected and maintained –Entity-relationship diagrams (ERDs): an ERD is a graphical model that shows relationships among system entities Data Terminology and Concepts

Lecture 95

6 l Entity-relationship diagrams (ERDs) –Each entity is a rectangle, labeled with a noun –Each relationship is a diamond, labeled with a verb –Types of relationships l One-to-one (1:1) l One-to-many (1:M) l Many-to-many (M:N) –A full ERD shows all system relationships Data Relationships and Entity- Relationship Diagrams

Lecture 97

8 l One-to-one (1:1) relationship –Exists when exactly one of the second entity occurs for each instance of the first entity –Examples l One office manager heads one office l One vehicle ID number is assigned to one vehicle l One driver drives one delivery truck l One faculty member is chairperson of one department Data Relationships and Entity- Relationship Diagrams

Lecture 99

10 l One-to-many (1:M) relationship –Exists when one occurrence of the first entity can be related to many occurrences of the second entity, but each occurrence of the second entity can be associated with only one occurrence of the first entity –Examples l One individual owns many automobiles l One customer places many orders l One department employs many employees l One faculty advisor advises many students Data Relationships and Entity- Relationship Diagrams

Lecture 911

Lecture 912 l Many-to-many (M:N) relationship –Exists when one instance of the first entity can be related to many instances of the second entity, and one instance of the second entity can be related to many instances of the first –Examples l A student enrolls in one or more classes, and each class has one or more students registered l A passenger buys tickets for one or more flights, and each flight has one or more passengers l An order lists one or more products, and each product is listed on one or more orders Data Relationships and Entity- Relationship Diagrams

Lecture 913

Lecture 914 l A full ERD shows all system relationships –Examples l A sales rep serves one or more customers, but each customer has only one sales rep l A customer places one or more orders, but each order has only one customer l An order lists one or more products, and each product can be listed in one or more orders l A warehouse stores one or more products, and each product can be stored in one or more warehouses Data Relationships and Entity- Relationship Diagrams

Lecture 915

Lecture 916 l Cardinality –Describes how instances of one entity relate to another –Mandatory vs. optional relationships –Crow’s foot notation is one method of showing cardinality –Most CASE products support the drawing of ERDs Data Relationships and Entity- Relationship Diagrams

Lecture 917

Lecture 918 l Creating an ERD 1. Identify the entities 2. Determine all significant events or activities for two or more entities 3. Analyze the nature of the interaction 4. Draw the ERD Data Relationships and Entity- Relationship Diagrams

Lecture 919 Process Description Tools l Structured English –Subset of standard English –Describes process logic l Use only standard sequence, selection, and iteration structures l Use indentation for readability l Use a limited vocabulary

Lecture 920

Lecture 921 Process Description Tools l Decision tables –Show a logical structure that describes process logic –Every logical combination is shown initially –Results then can be combined and simplified –Programmers can use decision tables in developing code

Lecture 922

Lecture 923 Process Description Tools l Decision tables

Lecture 924 Process Description Tools l Steps of constructing a Decision tables –Step 1. Analyze the procedure l Identity conditions and actions –Step 2. Calculate the number of rules l number of rules = 2 n where n = the number of conditions –Step 3. Evaluate the number of outcomes l Analyze the combination of condition to see what outcome should be undertaken –Step 4. Draw up the decision table

Lecture 925

Lecture 926

Lecture 927 Process Description Tools l Decision trees –Graphical representation that shows a decision table’s conditions, actions, and rules –Logic structure is shown horizontally –Easy to construct and understand –Decision table is better in complex situations

Lecture 928