Print this Page

Object Computing Principles
Concepts and Reality Check

Object Computing Principles provides a one-day overview of the Object Oriented approach: What is it?  How does it work?  Why would you do that?  The seminar first employs non-technical business language to define and explain object technology foundation concepts.  The discussion then positions today's reality and tomorrow's promise by exploring the many controversies surrounding object technology.

Object Computing Principles uses examples and case studies to teach the concepts that make the object oriented approach valuable.  Students participate in interactive exercises and discussions to learn how classes, inheritance, encapsulation and polymorphism enhance reuse, quality and Rapid Application Development.

Object Computing Principles looks long and hard at the current state of the art to separate substance from wishful thinking.  What are the important industry groups and which standards will live through commercial implementation?  How important is aggregation and application assembly from pre-existing parts and components?  Who are the vendors?  What are their strategies, architectures and products?  What's the status of object databases?  What about the ongoing convergence of object technology, n-tiered client/server and the web?

What You Will Learn

• Object theory: Why is reuse so important?

• All those weird words: What do they really mean?

• Object methodology: How do requirements analysis & design change?

• Current status: How much OT can you really use today?

• Futures: What happens tomorrow, and how can you prepare?

Who Should Attend

• I/S management, planners and architects

• Application design and development managers and practitioners

• Business analysts

• Business area management and staff involved with requirements analysis & application construction

Seminar Outline

Part 1: Object Concepts

• Introduction: What is it?

  • Why objects?

  • What is an object?

  • Where did they come from?

• OO Analysis and Design: Why would you do that?

  • Reuse: Quality & RAD

  • Domain definition

  • Real-world simulation

  • JAD & modeling methodologies

• Modules and Classes: How does it work?

  • Encapsulation: Combining data & process

  • Specialization: Subclass & Superclass

• Object Concepts & Terminology

  • Abstraction & Type

    • Characteristics

    • Properties vs. values

    • Behavior, actions & methods

    • Identity

    • Encapsulation

  • Messages

  • Type Triad

    • Name

    • Definition

    • Extension

  • Classification

    • Generalization/Specialization

    • Inheritance

    • Substitution

    • Polymorphism

Part 2: Reality Check

• Current state of the art

  • Visual objects

  • Business-logic objects

  • Persistent objects

• Product Positioning & Status

  • Design methodology overview

    • Object Modeling Technique (OMT)

    • Booch (Rational Rose)

    • Objectory (OOSE or Jacobson)

    • Fusion (Coleman)

    • Unified Modeling Language (UML)

  • State of the art

    • Visual Objects vs. Business Logic Objects vs. Persistent Objects

    • Application Creation: Build vs. Buy vs. Buy & Extend

  • Object-Based Aggregation

    • Granularity: Fine-grained vs. large-grained objects

    • Class Libraries

    • Components

    • Frameworks

    • Business Objects

  • Wrapping Legacy Applications

    • Treating Existing Applications as Objects

  • Databases

    • Object data structures

    • Object front-end to RDBMS