Lecture 4 Logic Modeling

Slides:



Advertisements
Similar presentations
Database Design Process
Advertisements

Chapter 6: Entity-Relationship Model (part I)
Alternative Approach to Systems Analysis Structured analysis
Chapter 4 Enterprise Modeling.
Systems Development Life Cycle
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
System Analysis - Data Modeling
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Data Flow Diagramming. Data Flow Diagrams Data Flow Diagrams are a means to represent data transformation processes within an information system.
Entity-Relationship Model and Diagrams (continued)
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Jump to first page Chapter 2c System Analysis - Logic Modeling.
Process Descriptions: Logic Modeling
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 4.
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition.
Chapter 2: Entity-Relationship Model (Continued)
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
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 7 Logical Database Design
Logic Modeling MIS 322. Why do we need Logic Modeling? Lets look at the following DFD.
Chapter 9 Structuring System Requirements: Logic Modeling
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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Information Systems System Analysis 421 Class Eight.
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
MBI 630: Class 6 Logic Modeling 9/7/2015. Class 6: Logic Modeling Logic Modeling Broadway Entertainment Co. Inc., Case –Group Discussion (Handout) –Logic.
Chapter 8 Structuring System Requirements: Logic Modeling
© 2008 Prentice Hall, Ovidiu Noran Lecture 7a 1 Modelling Logic Requirements (Textbook Chapter 8)
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Structuring System Requirements: Conceptual Data Modeling 7.1.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 8 Structuring System Logical Requirements.
Chapter 8 Structuring System Logical Requirements.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Description and exemplification of entity-relationship modelling.
Chapter 9 Logical Database Design : Mapping ER Model To Tables.
CHAPTER 5 1 DATA AND PROCESS ANALYSIS. Chapter Objectives Describe data and process modeling concepts and tools, including data flow diagrams, a data.
Cis339 Modern Systems Analysis and Design Fifth Edition Chapter 8 Structuring System Logic Requirements: 8.1.
Systems Analysis and Design 8th Edition
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
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 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Normalization. Overview Earliest  formalized database design technique and at one time was the starting point for logical database design. Today  is.
Modern Systems Analysis and Design Fourth Edition Chapter 8 Structuring System Logical Requirements (process description)
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 9 Structuring.
IS 4420 Database Fundamentals Chapter 3: Modeling Data in the Organization Leon Chen.
Let try to identify the conectivity of these entity relationship
Business System Development
Chapter 8 Structuring System Logical Requirements
Business System Development
Chapter 9 Structuring System Requirements: Logic Modeling
Process & Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 8 Structuring System Logical Requirements
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Database Management system
Database Management system
Presentation transcript:

Lecture 4 Logic Modeling

Learning Objectives Ask the right kinds of questions to determine data requirements for an IS Learn to draw entity-relationship (E-R) diagrams Entity type Entity instance Attribute Candidate key Multi-valued attributes Relationship Degree Cardinality Associative entity 6.2

Logic Modeling Although data-flow diagrams are good for identifying processes, they do not show the logic inside the processes. most fundamental processing steps. Just what occurs within a process? How are the input data converted to the output information? Because data-flow diagrams are not really designed to show the detailed logic of processes. you must model process logic using other techniques.

Logic Modeling Logic modeling involves representing the internal structure and functionality of the processes represented on data-flow diagrams. These processes appear on DFDs as little more than black boxes, in that we cannot tell from only their names precisely what they do and how they do it. Yet, the structure and functionality of a system’s processes are a key element of any information system. Processes must be clearly described before they can be translated into a programming language.

Logic Modeling with decision Tables A matrix representation of the logic of a decision, which specifies the possible conditions for the decision and the resulting actions. Condition Stub : That part of a decision table that lists the conditions relevant to the decision. Action stubs: That part of a decision table that lists the actions that result for a given set of conditions. Rules: That part of a decision table that specifies which actions are to be followed for a given set of conditions.

Constructing decision tables Name the conditions and the values each condition can assume. Determine all of the values each condition can take. For some conditions, the values will be simply “yes” or “no” (called a limited entry). For others, the conditions may have more values (called an extended entry). Name all possible actions that can occur. List all possible rules. Determine the number of rules, by multiplying the number of values for each condition by the number of values for every other condition. Define the action for each rule. Simplify the decision table.

Logic Modeling with decision Tables – Example 1 Employee type has two values: “S,” which stands for salaried, and “H,” which stands for hourly. Hours worked has three values: less than 40, exactly 40, and more than 40. Because of the indifferent condition for rules 1, 3, and 5, we can reduce the number of rules by condensing rules 1, 3, and 5 into one rule. We have two conditions, one with two values (S,H) and one with three ( <40 , 40 , >40), so we need 2 X 3, or 6, rules. If we added a third condition with three values, we would need 2 3 3, or 18, rules.

Logic Modeling with decision Tables – Example 1

Logic Modeling with decision Tables – Example 2 In the example from Hoosier Burger ( Reordering Process) how they reorder food and other items they use in the restaurant They reorder depends on whether the item is perishable. Realize the importance of the seasonality of their work.

Logic Modeling with decision Tables – Example 2

Logic Modeling with decision Tables – Example 2

Logic Modeling with decision Tables – Exercise A small company that sells eyeglasses to the public wants to incentivize its sales staff to sell customers higher quality frames, lenses, and options. The company has decided to pay the sales representatives based on a percentage of the profit earned on the glasses. All sales representatives will earn 15% of the profit on the eyeglasses. However, the owners are concerned that the sales staff will fear earning less than they do now. Therefore, those who were already working at the company are grandfathered into an arrangement where the workers are guaranteed to earn at least their base salary. Newly hired employees, however, are guaranteed only minimum wage based on the hours worked. To ensure only productive employees are retained, employees who are underperforming for three months in a row are automatically terminated. For those employees who are grandfathered in, any month where the representative earns only the salary is considered underperforming. For newer employees, the bottom quarter of the employees based on profit earned per hour worked are considered underperforming. Use a decision table to represent the logic in this process. Write down any assumptions you have to make.