Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under.

Slides:



Advertisements
Similar presentations
Entity-Relationship (ER) Modeling
Advertisements

Data Flow Diagramming Rules Processes –a process must have at least one input –a process must have at least one output –a process name (except for the.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Chapter 4 Enterprise Modeling.
Chapter 4.
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Systems Analysis and Design 9th Edition
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
MIS 210 Fall 2004Sylnovie Merchant, Ph. D. Lecture 4: Data Modeling Process Modeling MIS 210 Information Systems I.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Conceptual Models Agenda - Steps in the design of a DB - Need for conceptual models - The Entity-Relationship Model (ER-Model)
Data Flow Diagramming. Data Flow Diagrams Data Flow Diagrams are a means to represent data transformation processes within an information system.
Entity Relationship Diagrams
Structuring System Requirements: Process Modeling
Data and Process Modeling
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
© Copyright 2011 John Wiley & Sons, Inc.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 4.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Systems Analysis and Design in a Changing World, Fifth Edition
The Traditional Approach to Requirements
Chapter 6 The Traditional Approach to Requirements
Data flow diagrams.
ระบบฐานข้อมูลขั้นสูง (Advanced Database Systems) Lecturer AJ. Suwan Janin Phone:
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved..
Data and Process Modeling
Systems Analysis and Design in a Changing World, Fifth Edition
IS 320 Notes for Chapter 8. ClassX Problems: Low-Tech Fix Use last year's videos on ClassX  Select "Semesters" tab  Select IS 320  Select the week/lecture.
Entity-Relationship Model
Phase 2: Systems Analysis
The Structured Specification. Why a Structured Specification? System analyst communicates the user requirements to the designer with a document called.
CST203-2 Database Management Systems Lecture 2. One Tier Architecture Eg: In this scenario, a workgroup database is stored in a shared location on a single.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Concepts and Terminology Introduction to Database.
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
5-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Chapter 2 : Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of.
Chapter 4 enterprise modeling
CHAPTER 5 1 DATA AND PROCESS ANALYSIS. Chapter Objectives Describe data and process modeling concepts and tools, including data flow diagrams, a data.
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Database Design – Lecture 6 Moving to a Logical Model.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
Systems Analysis and Design 8th Edition
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
Systems Analysis and Design 8th Edition
6 Systems Analysis and Design in a Changing World, Fourth Edition.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
6 - 1 Systems Analysis and Design, 2 nd Edition Alan Dennis and Barbara Haley Wixom John Wiley & Sons, Inc. Slides by Roberta M. Roth University of Northern.
Database Designsemester Slide 1 Database Design Lecture 7 Entity-relationship modeling Text , 7.1.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
Structured Analysis Methods and Tools
Business System Development
Entity-Relationship Model
Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under.
Chapter 11 Describing Process Specifications and Structured Decisions
Presentation transcript:

Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under what conditions Logic is modeled per process Types of logic: sequence, conditions, iteration

Structured English Uses a subset of English Uses indentation similar to programming Uses process-type verbs like READ, WRITE, GENERATE, CHECK, PRINT Verbs and control words in CAPS Refers to the data coming in and out of the process No specific syntax rules

READ Inventory records WHILE NOT End-of-file DO BEGIN IF IF Quantity-in-stock is less than Minimum-order-quantity THEN GENERATE new order ELSE DO nothing END IF END DO Structured English Examples READ next prescription SELECT CASE CASE (prescription for formulated drug) DO send to lab station CASE (prescription for off-the-shelf drug) DO send to shelving station CASE (prescription for narcotic drug) DO send to secure station END CASE

Decision Tables

1 2 Pay base salary Calculate hourly wage; Produce absence report Calculate hourly wage Calculate hourly wage; Calculate overtime wage Salaried Hourly <40 40 >40 Legend 1) Type of employee 2) Hours worked Decision Trees

Network Models Network Decomposition Diagram –hubs - places where data is stored or processing is done for users at some other location –workstations - places where a user physically sits and can access the system remotely Hub Connectivity Diagrams –simply says what hubs and external networks have to exchange data

Network Decomposition Diagram Set of Workstations System Hub Workstation External Network

Hub Connectivity Diagram Hub 50 feet 35 miles External Network 3000 miles

Simple Example Customer Ordering System Server System Administrator Credit Verification Service Order Takers Server Credit Verification Service 200 miles

Data Dictionary -Includes: -descriptions of all pieces of data -relationships between pieces of data -Purposes -eliminate ambiguities -identify links between DFDs and ERD -clarify how different pieces of data are related -serves as a standard reference throughout the project -specify what is contained in data stores and flows

What needs to be defined Data flows Data stores Data elements Entities Relationships Attributes are collections of are collections of correspond to

Basic parts of a definition Name (that appears on the diagram) Type (data flow, data store, entity, etc.) Description (text) Synonyms (other names used for same thing) What it contains What it is contained in Constraints/data type

Data Flow Definition Name (that appears on the diagram) Type = data flow Description (text) Synonyms What it contains - list of data elements; lower- level data flows What it is contained in - data flow in higher-level diagram Constraints - source and destination

Example Data Flow Definition Name: Customer Record Type: data flow Description: The customer information that needs to be stored in the customer DB Synonyms: none What it contains: data elements: customer ID customer name customer address customer phone lower-level data flows: none What it is contained in: none Constraints: Source: Process 5, Create Customer Record Destination: Data Store D3, Customer Master

Data Store Definition Name (that appears on the diagram, including ID) Type = data store Description (text) Synonyms What it contains - list of data elements What it is contained in - n/a Constraints - physical form, if known

Example Data Store Definition Name: Customer Master Type: data store Description: Information on all customers who have provided this information when placing an order Synonyms: none What it contains: data elements: customer ID customer name customer address customer phone What it is contained in: n/a Constraints: form is a database table

Data Element Definition Name (does not appear on the diagram) Type = data element Description (text) Synonyms (other data elements and attributes) What it contains - n/a What it is contained in (data stores and data flows) Constraints (format, length, valid values)

Example Data Element Definition Name: customer name Type: data element Description: The last name of a customer who has at one time placed an order Synonyms: attribute Customer.name What it contains: n/a What it is contained in: data flow Customer Record; data store Customer Master Constraints: must be a character string with maximum length 15

Entity Definition Name (that appears on the diagram) Type = entity Description (text) Synonyms What it contains (attributes) What it is contained in - n/a Constraints (identifier)

Example Entity Definition Name: Customer Type: entity Description: Any individual who has at one time placed an order and purchased goods Synonyms: none What it contains: attributes Customer_ID, Name, Address, Phone What it is contained in: n/a Constraints: Customer_ID must be unique

Relationship Definition Name (that appears on the diagram) Type = relationship Description (text) Synonyms What it contains (attributes, including key attributes of participating entities) What it is contained in - n/a Constraints (cardinality, degree, operational constraints)

Example Relationship ACCOUNT account number balance owner type Has CUSTOMER Name Address Customer_IDPhone 8 Charge Customer Purchase D5Customer Accounts Purchase Information ERDDFD Customer Information Account Information

Example Relationship Definition Name: Has Type: relationship Description: Associates individual customers with the credit accounts they have with this business, that they can use to purchase goods Synonyms: data store D5, Customer Accounts What it contains: attributes Customer.Customer_ID, Account.account_number, owner_type What it is contained in: n/a Constraints: binary; many-to-one; mandatory for accounts, but not customers

Attribute Definition Name (that appears on the diagram) Type = attribute Description (text) Synonyms (other attributes and data elements ) What it contains - n/a What it is contained in (entities and relationships) Constraints (format, length, valid values)

Example Attribute Definition Name: Name Type: attribute Description: The last name of a customer who has at one time placed an order Synonyms: data element customer_name What it contains: none What it is contained in: entity Customer Constraints: must be a character string with maximum length 15