Please enable JavaScript.
Coggle requires JavaScript to display documents.
Introduction (Why Model (conceptual, visual representation, communication,…
Introduction
Why Model
conceptual
visual representation
communication
understanding
Data Model
WHAT
Completed by BA
Rules
Relationships
Thing of Interest
HOW
Developer
Desinger
WHY
reduce Duplication
Reduce Ambiguity
Business Needs
Shared Data
Business Decision
GOOD MODEL
Keep it simple
Completeness
Avoid Redundancy/Duplication
Address update to multiple entities
Enforce Business Rules
Re-Usability
Sharing with other departments
Stablity + Flexibility
Communiation
Back to business
Forward to developer
Integration
Enterprise Architecture
Data Architecture
Conflicting Objectives
Completeness vs. Simplicity
Approach
Top Down
Gap Analysis
Start with Stakeholders
Blank sheet
Bottom Up
Existing Sources
Databases
Procedural Guides
Spreadsheets
user Interfaces
Apply
Business Modelling
System Modelling
Impact Analysis
Communcation
Training
Business System
Components
Input
Output
Process
Rules
Data
without context
030618
Information
data with context
date 03/06/18
employee # 030-618
Money £30,618