Zen & The Art of Oriented / Objects College of Alameda Copyright © 2006 Patrick McDermott With a tip of the hat to: Herrigel, Eugen,

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

Object Oriented Programming. Object Oriented Data and operations are grouped together Account Withdraw Deposit Transfer Interface: Set of available operations.
System definition and boundaries Subsystems, environment, connections, dependencies Payroll Rules, contracts Working time Reductions, tax Accounting and.
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426/CPE 426 Senior Projects University of Nevada, Reno.
Chapter Object-Oriented Practices. Agenda Object-Oriented Concepts Terminology Object-Oriented Modeling Tips Object-Oriented Data Models and DBMSs.
Object Oriented System Development with VB .NET
Requirements Analysis 1 Use Cases -> Class Diagrams Moving from the user towards the system.
From Class Diagrams to Databases. So far we have considered “objects” Objects have attributes Objects have operations Attributes are the things you record.
Lecturer: Dr. AJ Bieszczad Chapter 66-1 Object-Oriented analysis and design Special nature of OO development Use cases Design with UML OO system design.
Database Design Concepts Lecture 7 Introduction to E:R Modelling Identifying Entities.
Chapter 16: Customizing Forms Copyright © 2014 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
CPT 140 Programming Constructs1 OBJECT ORIENTED TECHNOLOGY Terminology and Basic Concepts.
CRC Cards C lass  R esponsibility  C ollaborator Copyright © 1999 Patrick McDermott UC Berkeley Extension Although not strictly part.
Data Modeling 101 UC Berkeley Extension Copyright © 2000 Patrick McDermott
Chapter 13 (Online): Object-Oriented Databases
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of.
Use Cases College of Alameda Copyright © 2007 Patrick McDermott.
1 Advanced Computer Programming Databases. Overview What is a database? Database Basics Database Components Data Models Normalization Database Design.
OBJECT AND CLASES: THE BASIC CONCEPTS Pertemuan 8 Matakuliah: Konsep object-oriented Tahun: 2009.
Module 7: Object-Oriented Programming in Visual Basic .NET
Two Approaches to System Development
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.
1 Object-Oriented Systems Development Bahrami © Irwin/ McGraw-Hill Chapter 2: Object Basics Object-Oriented Systems Development Using the Unified Modeling.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
7-1 © Prentice Hall, 2004 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Database Design – Lecture 3 Conceptual Database Design.
Quick Draw Copyright © 2007 Patrick McDermott College of Alameda M.C. Escher ( ) Drawing Hands 1948.
MSF Design Example Conceptual Design Logical Design Physical Design.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
CRAM/ERAT Babel College of Alameda Copyright © 2000 Patrick McDermott CRAM: Class-Relationship-Attribute-Method ERAT: Entity-Relationship-Attribute-Trigger.
Kal Bugrara, Ph.DSoftware Engineering Northeastern University Fundamentals Of Software Engineering Lecture V.
2007ACS-3913 Ron McFadyen1 Class Diagram See Schaum’s UML Outline, especially chapters 4, 5, 6, 7.
Finding Classes Copyright © 1999 Patrick McDermott College of Alameda A Quest: David, Earl of Huntingdon, 1120 from A Critical Inquiry.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
Object-Oriented Data Modeling
Which CRAM? College of Alameda Copyright © 1999 Patrick McDermott Class Relationship Attribute Method cf.: Entity-Relationship-Attribute-Trigger.
Banking Example College of Alameda Copyright © 1998 Patrick McDermott.
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.
Design CIS 4800 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College Copyright © 2009 John Wiley & Sons, Inc. Copyright © 2008 Course.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
1 CMT2050: Object Oriented Programming and Design Dr. Xiaohong Gao Room 2C23 Ext ( Seminar Week 1) The.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
12 OBJECT-ORIENTED DESIGN CHAPTER
INFSY 535.  Small systems  Larger systems 1.Understand the program requirement- what 3. Write and test each part (unit testing) 4. Maintenance 2. Specify.
Lecture 8&9 11/2/16 Introduction to OO Concepts 1.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Chapter 6: The Analysis Workflow Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes [Arlow and Neustadt, 2005] CS 426 Senior Projects in.
UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.
Chapter 16: Customizing Forms Copyright ©2013 by The McGraw-Hill Companies, Inc. All rights reserved.
Database (Microsoft Access). Database A database is an organized collection of related data about a specific topic or purpose. Examples of databases include:
DOMAIN CLASSES – PART 1 BTS430 Systems Analysis and Design using UML.
Object-Oriented Modeling
Systems Analysis and Design
Chapter 8 Analysis & Modeling
Chapter 16: Customizing Forms
Object Oriented Concepts
Lec 3: Object-Oriented Data Modeling
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes
Chapter 7: Classes and Objects Chapter 8: Finding Analysis Classes
Object Oriented Programming
ITEC 3220A Using and Designing Database Systems
Software Analysis.
The Object Paradigm Classes – Templates for creating objects
Presentation transcript:

Zen & The Art of Oriented / Objects College of Alameda Copyright © 2006 Patrick McDermott With a tip of the hat to: Herrigel, Eugen, R.F.C. Hull (translator from German), Zen in the Art of Archery, New York: Vintage Books ( ), 1953, 1989 (Zen in der Kunst des Bogenschiessens, 1948) René Magritte ( ) The Prince of Objects Le Prince des objets 1927

Data Processing Process Data Tear down this Wall!!! Name is “Pat” Balance is $110 Payment is $50 Take Pat’s Balance; Subtract the Payment; Make that the Balance;

Classes & Objects OBJECT: A discrete entity with a well-defined boundary and identity that encapsulates state and behavior; an instance of a class. Rumbaugh [3 Amigos], Reference, p CLASS: The descriptor for a set of objects that share the same attributes, operations, methods, relationships and behavior. A class represents a concept within the system being Modeled. Rumbaugh [3 Amigos], Reference, p Separate the Essence from the Instance.

Class A class is a category of Things. An object is one of those things. A instantiation of a class. Encapsulation Inheritance $$ Poly m o r p h i s m Name Address Telephone CreditRating Taxonomy is a taxing task: Is a Grad student an employee? Is Pluto a Planet? Is Bill Gates human?

“Class” is perhaps Best defined by Examples… Tangible Intangible Conceptual –Cost Center, Account People Places Things Events Roles Organizations Collections of Objects Interface –Form or Dialog Infrastructure –Date, Money, Address Persistence: Database Control Reference Lists Other Systems Process –Currency Format?

They’re Everywhere! There must be a Class if … there’s a form … there’s a file … there’s a number … there are multiple copies … It’s Important NOTE-- –Sections and boxes on Forms –The name might not be obvious Responsibilities Obligation or Contract Personification Helps Know Things –Invoice: Know the Customer Do Things –Invoice: Compute Total Get Organized –Abstraction