Simple Fun Modeling with SQL Server

Slides:



Advertisements
Similar presentations
Database Planning, Design, and Administration
Advertisements

1 1 File Systems and Databases. 1 1 Introducing the Database 4Major Database Concepts u Data and information l Data - Raw facts l Information - Processed.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
1 SWE Introduction to Software Engineering Lecture 13 – System Modeling.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
7M701 1 Software Engineering Systems Models Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 7 (some items)
Ch1: File Systems and Databases Hachim Haddouti
SLIDE 1IS Fall 2002 Database Management: Discussion Session University of California, Berkeley School of Information Management and.
Restaurant Dining System Donald Kaulukukui. Introduction ► Team manager = ME ► Secretary = ME ► President = ME ► R & D = ME ► Tester = ME.
7M822 Software Engineering: System Models 14 September 2009.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
Chapter 7: System models
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
Best Practices for Data Warehousing. 2 Agenda – Best Practices for DW-BI Best Practices in Data Modeling Best Practices in ETL Best Practices in Reporting.
INTRODUCTION TO DATABASES Chapter 1. What is a Database?  Forget the glossary! (see pages 11-12)  The purpose of a database is to help people track.
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
ENTERPRISE APPLICATION INTEGRATION
MIS 673: Database Analysis and Design u Objectives: u Know how to analyze an environment and draw its semantic data model u Understand data analysis and.
L8 - March 28, 2006copyright Thomas Pole , all rights reserved 1 Lecture 8: Software Asset Management and Text Ch. 5: Software Factories, (Review)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Prepared By Prepared By : VINAY ALEXANDER ( विनय अलेक्सजेंड़र ) PGT(CS),KV JHAGRAKHAND.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Database Development Data Analysis: The Entity Relationship Powered by DeSiaMore1.
Week 4-5 DBMS Database Design. Database design process can be divided into 6 major steps: 1.Requirements Analysis 2.Conceptual Database Design 3.Logical.
Understanding Data Intensive Systems Using Dynamic Analysis and Visualization Nesrine NOUGHI.
Lecture 15: Query Optimization. Very Big Picture Usually, there are many possible query execution plans. The optimizer is trying to chose a good one.
MBI 630: Week 9 Conceptual Data Modeling and Designing Database 6/10/2016.
Impact and Influence of Educators in Game Design.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Chapter 5 – System Modeling
Analysis Services in times of Continuous Integration
Building Enterprise Applications Using Visual Studio®
Logical Database Design and the Rational Model
Understanding Data Storage
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Object-oriented and Structured System Models
Object Management Group Information Management Metamodel
Kevin C. Chang University of Illinois, Urbana-Champaign
Week 02 - Introduction to Data Modelling
Fundamentals of Information Systems, Sixth Edition
DATA MODELS.
mysql and mysql workbench
Abstract descriptions of systems whose requirements are being analysed
CO6025 Advanced Programming
Views Defining and Using Views.
Tools for Memory: Database Management Systems
 DATAABSTRACTION  INSTANCES& SCHEMAS  DATA MODELS.
Entity-Relationship Model and Diagrams (continued)
Data Base System Lecture : Database Environment
Four Levels of Data from Ricardo’s Database Illuminated
Simplifying Integration - the art of iWay Software
الفصل الخامس قواعد البيانات Databases
Data Modeling Concepts
IST 318 Database Administration
Database Management Systems
Software Design Lecture : 15.
Database Management Systems CSE594
Data modelling and why it matters
AppointmentmentPeach Appointment Manager
Data Modeling Concepts
Office: ENGR 530 Phone: Emai:
Chapter 5 Architectural Design.
MIS2502: Data Analytics MySQL and MySQL Workbench
Databases 1.
CS 505: Intermediate Topics to Database Systems
Rapid Service Composition
Database Dr. Roueida Mohammed.
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Simple Fun Modeling with SQL Server

Dane Schilling Father Husband Headspringer

Agenda What Why How Demo

What Defined Entity-relationship modeling is a relational schema database modeling method, used in software engineering to produce a type of conceptual data model (or semantic data model) of a system, often a relational database, and its requirements in a top-down fashion.

The Real What Data isn’t always fancy. In its infancy a data model should be simple, but done correctly it should age like a fine wine.

The Why Data modeling is what sets the stage for any application or report. With the right model in place we ensure we are on course for success.

How Defined Two standard approaches. Top-Down Bottom-Up

Top-Down Top-down logical data models are created in an abstract way by getting information from people who know the subject area. A system may not implement all the entities in a logical model, but the model serves as a reference point or template.

Bottom-Up Bottom-up models or View Integration models are often the result of a reengineering effort. They usually start with existing data structures forms, fields on application screens, or reports. These models are usually physical, application-specific, and incomplete from an enterprise perspective. They may not promote data sharing, especially if they are built without reference to other parts of the organization.

The Real How For me data modeling is a hands on process. You will get your hands dirty and you will get it wrong at times. In my opinion, getting things wrong is the best way to learn.

Context

Demo

Link to repo: https://github Link to repo: https://github.com/daneSchilling/TheWorld Applications/Nuget mentioned: - Highcharts - RoundhousE - StructureMap - Mediatr