MetaData “Data about Data” College of Alameda Copyright © 1999 Patrick McDermott I never met a data I didn’t like. —PMcD “Data.

Slides:



Advertisements
Similar presentations
UML: The Unified Modeling Language Excertos do livro: The Unified Modelling Language User Guide by Grady Booch, James Rumbaugh and Ivar Jacobson.
Advertisements

College of Alameda Copyright © 2007 Patrick McDermott Vincent van Gogh ( ) The Langlois Bridge March 1888.
7M701 1 Information Systems Modelling and Design with.
Zen & The Art of Oriented / Objects College of Alameda Copyright © 2006 Patrick McDermott With a tip of the hat to: Herrigel, Eugen,
Accounting System Design
Maintenance Modifying the data –Add records –Delete records –Update records Modifying the design –Add fields into tables –Remove fields from a table –Change.
Chapter 7 UNDERSTANDING AND DESIGNING FORMS. Input Forms: Content and Organization Need for forms Event analysis and forms Relationship between input.
Data Quality Class 3. Goals Dimensions of Data Quality Enterprise Reference Data Data Parsing.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Principles of Object-Oriented Software Development Unified Modeling Language.
COMPREHENSIVE Access Tutorial 2 Building a Database and Defining Table Relationships.
Tony Hoare ¢ Turing Award 1980 ¢ Program Verification ¢ Algol 60 ¢ Axiomatic Semantics ¢ Floyd-Hoare Logic ¢ Concurrent Programs ¢ Communicating Sequential.
Itntroduction to UML, page 1 Introduction to UML.
FIRST COURSE Access Tutorial 2 Building a Database and Defining Table Relationships.
Database – Part 2a Dr. V.T. Raja Oregon State University.
Data Modeling 101 UC Berkeley Extension Copyright © 2000 Patrick McDermott
An Introduction to Models & The UML The Unified Modeling Language Copyright © 2007 Patrick McDermott College of Alameda Not really.
Use Cases College of Alameda Copyright © 2007 Patrick McDermott.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Entity Life Cycle College of Alameda Copyright © 2008 Patrick McDermott Caspar David Friedrich ( ) The Stages of Life, c.
Object Oriented Design and Programming Alan Goude Room: Sheaf 9323.
Cycles & Life Cycles College of Alameda Copyright © 2007 Patrick McDermott.
A Z Approach in Validating ORA-SS Data Models Scott Uk-Jin Lee Jing Sun Gillian Dobbie Yuan Fang Li.
Unified Modeling Language, Version 2.0
Data Types Copyright © 2006 Patrick McDermott College of Alameda
The Relational Model UC Berkeley Extension Copyright © 2008 Patrick McDermott.
Which ERAT? Entity Relationship Attribute Trigger Copyright © 1999 Patrick McDermott.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Access Project 3 Notes. Introduction Maintaining the Database  Modifying the data to keep it up-to-date Restructure the Database  To change the database.
CS-2852 Data Structures LECTURE 3B Andrew J. Wozniewicz Image copyright © 2010 andyjphoto.com.
Quick Draw Copyright © 2007 Patrick McDermott College of Alameda M.C. Escher ( ) Drawing Hands 1948.
Objects and Classes Abstract Classes and Interface Sanjaya Karunasena
Object-Oriented Paradigm and UML1 Introduction to the Object- Oriented Paradigm.
Database Goodness College of Alameda Copyright © 2008 Patrick McDermott Berthe Morisot (1841–95) The Cradle, 1872.
Use Cases -Use Case Diagram Chapter 3 1. Where are we? 2 Analysis Chapters Ch 2Investigating System Requirements Ch 3Use Cases Ch 4Domain Modeling Ch.
CRAM/ERAT Babel College of Alameda Copyright © 2000 Patrick McDermott CRAM: Class-Relationship-Attribute-Method ERAT: Entity-Relationship-Attribute-Trigger.
+ Information Systems and Databases 2.2 Organisation.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Which CRAM? College of Alameda Copyright © 1999 Patrick McDermott Class Relationship Attribute Method cf.: Entity-Relationship-Attribute-Trigger.
Subtypes Copyright © 1999 Patrick McDermott UC Berkeley Extension
The Unified Modeling Language (UML)
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
MADALINA CROITORU Software Engineering week 4 Practical Madalina Croitoru IUT Montpellier.
1 Unified Modeling Language, Version 2.0 Chapter 2.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
Unified OO becomes commonly used in the late 1980s Various analysis and design methods The “three amigos” join forces in Rational Software Also include.
Slide 1 Objectives Understand the basic characteristics of object-oriented systems. Be familiar with the Unified Modeling Language (UML),V.2.0.
SEMI-STRUCTURED DATA (XML) 1. SEMI-STRUCTURED DATA ER, Relational, ODL data models are all based on schema Structure of data is rigid and known is advance.
Unified Process Software Development Darren Roback/Ravali Kallem CMIS Fall 2009.
Distributed Java Programming Distributed Java Programming Class #1 August 20, 2002.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Modeling with UML – Class Diagrams
Introduction to UML.
Use Cases -Use Case Diagram
Creating a database table
Systems Analysis and Design With UML 2
Introduction to Unified Modeling Language (UML)
James Miller, Julia John
University of Central Florida COP 3330 Object Oriented Programming
UML Class Diagrams: Basic Concepts
Accounting System Design
Introduction to UML.
Use Cases & Use Case Diagrams
Accounting System Design
Database Design and Development
G061 - Data Dictionary.
Login Main Functions Via SAS Information Delivery Portal
Presentation transcript:

MetaData “Data about Data” College of Alameda Copyright © 1999 Patrick McDermott I never met a data I didn’t like. —PMcD “Data is, Data are.” In human language, “One word can mean more than one thing. This flexibility provides a deep well of nuance and beauty; it is a foundation of poetry. But it leads only to trouble when you are trying to build software.” —Scott Rosenberg, Dreaming in Code

One cannot give what one does not have One cannot have what one has no place to keep Nēmō dat qua nōn habet.

The Sour of Babel Illustrates the Metadata obstacle to the Semantic Web: We need to call the Same thing by the Same name, Different things by Different names Pietr Brueg(h)el (the Elder) The Tower of Babel, 1563

Attribute or Entity? Jean Tinguely Self-Propelled Meta-Mechanical Machine 1954

Object An object (business object) is a thing the business needs to know about. Classes are groups (classifications) of objects. In most discussions, “class”, “object” and “entity” can be used interchangeably. In addition to business objects, there are infrastructure objects. During analysis, you should only discuss business (entity) objects.

Attribute An attribute is a piece of information about an object needed in your business. CRUD: Create, Read, Update, Delete An attribute or variable is a fact about an object. It can hold only one value at a time. Attributes and relationships do not have attributes; if there is a fact to be kept, it is an object in its own right, not an attribute.

Attribute (Field) Properties IDentifier (Name and Primary Key) Data Type –Min, Max or other range –Default Value or Algorithm –Validation Rule –Select Values (Lookup) Format –Length –Decimal Places Required or Optional? Marcel Marien That which Cannot be Found, 1937

Class in UML CLASS Attribute1 Attribute2 Attribute3 Method1() Method2() Associated with “The Three Amigos” (Spanish: “Los Tres Buddies”) Grady Booch James Rumbaugh & Ivar Jacobson