Object Oriented Analysis -- A Historical View “Data Processing” Era: Processes Stored in Programs Data in Associated Files Payroll Payroll Data Purchasing.

Slides:



Advertisements
Similar presentations
Chapter Information Systems Database Management.
Advertisements

First Normal Form Second Normal Form Third Normal Form
Entity-Relationship Modeling (ER-M)
When is Orientated Programming NOT? Mike Fitzpatrick.
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.
Chapter 7 Understanding More Complex Requirements Models Using Generalization / Specialization and Whole-Part Hierarchies.
Chapter Information Systems Database Management.
Introduction To System Analysis and Design
Accounting 6500 Relational Databases: Accounting Applications Introduction to Normalization.
7M701 1 Class Diagram advanced concepts. 7M701 2 Characteristics of Object Oriented Design (OOD) objectData and operations (functions) are combined 
Further Data Modelling …and the effect of time. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis –Further.
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Case study Lisa’s Bookstore IST210.
CSCI 242 Relational Data Modeling Copyright 2011, David C. Roberts, all rights reserved.
MS Access 2007 IT User Services - University of Delaware.
CPT 140 Programming Constructs1 OBJECT ORIENTED TECHNOLOGY Terminology and Basic Concepts.
1 INTRODUCTION TO OOP Objective: Know the difference between functional programming and OOP Know basic terminology in OOP Know the importance of OOP Know.
Data Modeling using Entity Relationship Diagramming (ERD)
Advanced Entity Relationship Concepts. Advanced Concepts UIDs Intersection Entities Recursive Relationships Roles Subtypes Exclusivity Historical Fan.
Object Orientation An Object oriented approach views systems and programs as a collection of interacting objects. An object is a thing in a computer system.
CREATE THE DIFFERENCE Normalisation (special thanks to Janet Francis for this presentation)
11 1 Object oriented DB (not in book) Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Learning objectives: What.
CHAPTER 2. FUNDAMENTAL OF ENTITY RELATIONSHIP (ER)
Practice of ER modeling
Introduction to Objects Adapted from “TEN STEPS TO OBJECT-SPEAK” a CPT Tech Talk by Joy Starks September 17, 1999.
Database Design Sections 6 & 7 Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies and Recursive relationships.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Chapter 7: Database Systems Succeeding with Technology: Second Edition.
Recap (önemli noktaları yinelemek) from last week Paradigm Kay’s Description Intro to Objects Messages / Interconnections Information Hiding Classes Inheritance.
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
BIS Database Systems School of Management, Business Information Systems, Assumption University A.Thanop Somprasong Chapter # 5 Normalization of Database.
Database Design Sections 9 & 10 Modeling Historical Data, conditional nontranferability, time-related constraints 1.
Tutorial DFD Cap I. Najwa AlGhamdi. context diagram  Why context diagram ?  To know Who will interact with system. What's the main input and output.
Organizing Data Revision: pages 8-10, 31 Chapter 3.
Customer Order Order Number Date Cust ID Last Name First Name State Amount Tax Rate Product 1 ID Product 1 Description Product 1 Quantity Product 2 ID.
Class Diagrams In UML class diagrams are used to represent classes and relationships between classes. Each class is represented as a box divided into three.
MS Access. Access is a DBMS/RDMS DBMS = Database Management System RDMS = Relational Database Management System.
Database Design 3: Advanced Data Modeling Concepts CS 320.
Chapter 7 Data Modeling with Entity Relationship Diagrams
ITEC 3220A Using and Designing Database Systems Instructor: Prof Z. Yang Course Website: 3220a.htm
ITEC 3220A Using and Designing Database Systems Instructor: Gordon Turpin Course Website: Office: CSEB3020.
Learners Support Publications Object Oriented Programming.
Copyright Ó Oracle Corporation, All rights reserved. Assign Unique Identifiers A Unique Identifier (UID) is any combination of attributes and/or.
Chapter 4 Basic Object-Oriented Concepts. Chapter 4 Objectives Class vs. Object Attributes of a class Object relationships Class Methods (Operations)
1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.
Data modeling Process. Copyright © CIST 2 Definition What is data modeling? –Identify the real world data that must be stored on the database –Design.
Database Design Sections 8 & 12 Modeling Historical Data, conditional nontranferability, time-related constraints.
Lecture 8&9 11/2/16 Introduction to OO Concepts 1.
Howard Paul. Sequential Access Index Files and Data File Random Access.
DBS201: Data Modeling. Agenda Data Modeling Types of Models Entity Relationship Model.
DATA SCIENCE MIS0855 | Spring 2016 Designing Data
DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.
1 Database Design Sections 6 & 7 First Normal Form (1NF), Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies.
Entity/Relationship Modelling
Let try to identify the conectivity of these entity relationship
Information System & Database Design
Implementing an REA Model in a Relational Database
Database Requirements and Design
Information Systems Database Management
Object Oriented Concepts
The Object Oriented Approach to Design
MIS2502: Data Analytics Relational Data Modeling
ITEC 3220A Using and Designing Database Systems
MIS2502: Data Analytics Relational Data Modeling 2
Database Management system
Agenda Software development (SD) & Software development methodologies (SDM) Orthogonal views of the software OOSD Methodology Why an Object Orientation?
Presentation transcript:

Object Oriented Analysis -- A Historical View “Data Processing” Era: Processes Stored in Programs Data in Associated Files Payroll Payroll Data Purchasing Purchasing Data Budgeting Budgeting Data Retirement Retirement Data --Data files designed for use with particular Programs --Data shared with some difficulty since when the original program changed, the data usually changed too. --Programs and their data were “silos” not understood except by their own programmers.

Object Oriented Analysis -- A Historical View “Data Independence” Era: Processes Stored in Programs A Single Source of Data in a Shared DataBase Payroll Purchasing Budgeting Retirement --Data designed separately from programs, with eye to meeting whole organization needs. --Data easily shared between programs --Data understood by all. -- Programs could be easily changed, as long as they didn’t change the data. -- Programs could be insulated from changes to data that didn’t affect them. One Shared Database for All Processes

Object Oriented Analysis -- A Historical View “Object Oriented” Era: Objects, each with its own processes and its own data Vendor --processes --data --Each Object “knows” the things about itself that it has to. It “knows” how to do the things it has to do. -- Communication by Messages to and between Objects --Everyone knows what things each object can do, and what the message should look like to request a particular service from an object. --Data and processes are “encapsulated” protected from changes from the outside, and available only from the object itself through some message. So Object processes and data are not understood except by their own programmers. Invent.Item --processes --data Cust Order --processes --data Employee --processes --data Message

Historical Rental Date Customer Cust ID Name Mem Stat Late Fees Current Rental Date Out Due Date Check Out Movie Check In Movie Movie Movie ID Title Get Price Price Cat Price code Description M-Price N-Price Content Cat Category code Description 1.Ask for Name, Late Fees (CustID). 2.Do “Get Price” (CustID, MovieID) 3.Ask for M-Price, N-Price (PriceCode) 6.Update LateFees (CustID) 4.Ask for MemStat (CustID) 5. Ask for Title (MovieID)

Benefits of Object Oriented Analysis and Programming Reuse (?) Encapsulation Inheritance Greater programmer efficiency (?) Easier to build and modify systems (?) –Travelers Insurance “Trend” 1st -- $7M and 80 person/years 2nd -- $1.5M and 18 person/years 3rd -- $.5M and 6 person/years

Object Oriented Systems: Key Terms Classes versus Objects Attributes of a Class Inheritance Association Relationships Whole-part Relationships Method or Service (and Inheritance) Message Sending Encapsulation or information hiding Polymorphism Reuse

Class Object Data Entity Instance Relational Table Row of Table Objects Vs. Classes Specific Instance of the Category

Faculty Faculty ID Office Specialty Offer a course Method 2 Person Name Home Address Phone Change Address Change Phone Student Student ID Major Grade Point Register for Course Change Major Administrator Staff ID Title Organization Est. New Org Method 2 Classification Hierarchies and Inheritance

Class Name Attribute 1 Attribute 2 Attribute 3 Method 1 Method 2 Class Name Attribute 1 Attribute 2 Attribute 3 Method 1 Method 2 Class without Objects Class with Objects

Faculty Faculty ID Office Specialty Offer a course Method 2 Person Name Home Address Phone Change Address Change Phone Student Student ID Major Grade Point Register for Course Change Major Administrator Staff ID Title Organization Est. New Org Method 2 Class. Hierarchies and Inheritance– A Class with no Objects

Class Exercise: Draw the diagram for the Object Model for the following WCV objects. Use at least one Classification hierarchy and appropriate relationship associations. (Ignore Services for now.) Movie (MovieID, Title, PriceCat) Customer (Name, Address, Phone, CustID, MemStat, LateFees) Copy (MovieID, Copy#, #Times viewed) Employee (Name, Address, Phone, EmplID, Location, PayRate) CurrentRental (MovieID, Copy#, CustID, EmplID, Due Date) Prices (PriceCat, M-Price, N-Price)