Email Marketing Modeling Session Results. Agenda from first session Purpose To produce a Business Function Model (BFM) and a Conceptual Data Model (CDM)

Slides:



Advertisements
Similar presentations
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.
Advertisements

© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
ISMT221 Information Systems Analysis and Design Entity-Relationship Diagram Lab 4 Tony Tam.
1 Class Agenda – 09/20/2011  Answer questions about exam  Evaluate database design homework  Review database design homework for syntax and logic 
Entity Relationship Diagrams Basic Elements and Rules.
Modern Systems Analysis and Design
A Quick Review of Analysis Stages of the Systems Development Life Cycle Planning Analysis Design Construction.
1 Classification: Genpact Internal.  Tool From Oracle  Works with Oracle Database  PL/SQL Based  Widely Used with Oracle Applications  Can be Used.
Chapter 3: Data Modeling
Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.
Database Design Concepts Info1408
July 14, 2015ICS 424: recap1 Relational Database Design: Recap of ICS 324.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Bite sized training sessions: Process Modelling – Part 1 of 2 Process Model Diagrams.
WJEC Applied ICT Databases – Attributes & Entities Entities A database contains one or more related tables. Each table holds all of the information.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Business Rules: The Promise of Data Warehousing. In the Beginning: Formulating Business Rules The Business Objectives The Promise (Data Warehousing) –
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
Database and Direct Response Advertising MKTG 340 Maureen O’Connor.
Entity Relationship 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.
The Software Development Life Cycle: An Overview
Bite sized training sessions: Data Modelling – Part 1 of 2 Data Model Diagrams Feb 2011 Prepared by Guy Beauchamp Group Projects & IT.
Entity Relationship Diagrams
1 DATABASE TECHNOLOGIES BUS Abdou Illia, Fall 2007 (Week 3, Tuesday 9/4/2007)
Overview of Database Development
Database Design Concepts With Access. Learning Outcomes  Identify and define the information that is needed to design a database  Create conceptual.
Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under.
ITEC224 Database Programming
Conceptual Design versus Logical Design. Conceptual Data Design Prepared at beginning of project High level view of how the client sees the data Top down.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 3/1 Copyright © 2004 Please……. No Food Or Drink in the class.
McGraw-Hill/Irwin © 2013 The McGraw-Hill Companies, Inc., All Rights Reserved. Chapter 7 Data Flow Diagramming.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Information Systems Today (©2006 Prentice Hall) 3-1 CS3754 Class Note 12 Summery of Relational Database.
Bite sized training sessions: Data Modelling – Part 2 of 2 Data Definitions.
10-1 Chapter 10 Direct Marketing.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
Introduction to Databases Trisha Cummings. What is a database? A database is a tool for collecting and organizing information. Databases can store information.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Marketing – Think Inside the Box By Francis Jones.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Chapter 4 Marketing Intelligence and Database Research.
Database Design – Lecture 4 Conceptual Data Modeling.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Entity-Relationship Diagram Presentation Gianna-lee Williams 6AQ Ms. Anderson.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
3 1 Database Systems The Relational Database Model.
Subscribers – DatA Extensions
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
TRANSACTIONAL DATA. TRANSACTION DATA THE COLLECTED INFORMATION ABOUT THE SELL AND PURCHASE TRANSACTION IS THE ACTIVITIES THAT OCCUR EVERY TIME YOU BUY.
1 CS 430 Database Theory Winter 2005 Lecture 3: A Fifty Minute Introduction to Data Modeling.
Data Modeling AND ER MODELS.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
TOPIC 5 Search For a New Venture Building a Powerful Marketing Plan.
Principles of Marketing - UNBSJ
10-1 Chapter 10 Direct Marketing.
Process Modeling Graphically represent the processes that capture, manipulate, store, and distribute data between a system and its environment Models DFDs.
Classes, Sequence Diagrams and Triangulation
Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under.
Sales & Marketing Sales and Marketing 14 April 2019
Information Systems in Organizations 2. 1
Database Design Chapter 7.
Presentation transcript:

Marketing Modeling Session Results

Agenda from first session Purpose To produce a Business Function Model (BFM) and a Conceptual Data Model (CDM) for the Marketing Project Today’s Agenda Explain the rules for Business Function Modeling Build a BFM Future Modeling Sessions Finish/refine the BFM as necessary Ask the question “What data do I need to perform this function?” for each of the lowest-level functions in the BFM Build a CDM –this will look like an entity-relationship diagram without any keys or attributes Ultimate outcome of these meetings A CDM to serve as the basis of Logical Data Modeling for the project A prototype process to determine the extent that a facilitated modeling session can reduce or eliminate the need for a formal BRD document

Rules for Business Function Modeling Functions define WHAT, not HOW Functions start with a precise verb Functions are stated in plain English—no jargon Functions deliver something Order of functions is not important Functions may be optional Functions usually break down into 4 to 8 sub-functions Sub-functions must completely define the parent function

Marketing Business Function Model Optimize at the customer level by modifying programs based on results Target campaigns Identify campaign activity Identify response curves –the time lag between receipt and purchase Build predictive models Modify future campaigns

BFM Detail Target campaigns Identify What to test Identify to Whom to send Identify When to send Identify What to send

BFM Detail Identify campaign activity Identify delivery activity –Bounce –Fail –Frequency –Suppress –Exclude –Delivered Identify response activity –Opens –Clicks –Purchases –Search –Shop –Save –Opt Out –None –Flagged as SPAM –Complained –Called

BFM Detail Identify response curves Identify delivery response curves Plot Clicks over time Plot Opens over time Plot Opt Outs over time Plot Complaints over time Plot Flagged as SPAM over time Plot Delivery over time Identify transaction response curves Plot Purchase over time Plot Cancel over time Plot Search over time Plot Shopping over time Plot Save over time

BFM Detail Build predictive models Run test campaign Collect all response data Select other available attributes Select an algorithm Run it Identify predictive variables Build Model Validate Model

BFM Detail Modify future campaigns Apply what we have learned from past campaigns Identify opportunities for new campaigns Terminate ineffective campaigns

Conceptual Data Modeling Agenda Today we ask this question for each of the lowest level functions in the business model: “What data do I need to perform this function?” We answer the question in terms of entities, attributes, and relationships Entity: Something (a noun) the business has the will and the means to keep information about Attribute: A single piece of information about an entity Relationship: An association between two entities for a business purpose We are still looking at: Future-State Perfect-World What, not How

Conceptual Data Modeling Today we are not doing Defining scope Source system analysis Attribute definitions and data types Primary and foreign keys We need to leave some work for the project managers, logical data modelers, and database developers

Conceptual Data Model

CDM Notes Account Attributes –Demographic –Psychographics –Preferences –Hardware/Network/Browser –Everything else you could imagine Content –A unique asset sent to a unique address at a point in time

CDM Event Notes Account EventContent EventLink Event BounceX FailX FrequencyX SuppressX ExcludeX DeliveredX OpenX ClickX PurchaseXXX SearchXXX ShopXXX SaveXXX Opt OutXXX NoneXXX Flagged as SpamX ComplainedXX CalledXX