Main

 
Object Oriented Technology
Object Oriented
Technology

Links: Resume | Papers | Courses | Consulting | ContEd | HW/SW | Tech Interests
Terminology | Organizations ▼ | Certifications | Standards ▼ | Methods | Companies | Tools | Schools | Conferences
Macintosh | EVB Software Engineering

OO Methods, see: Development Methods and SemanticNets
OO-related: CASE/SEE Tools | Reuse Libraries | OO & Ada Conferences
Links Below: Orgs | Languages | Patterns | References | Standards

Organizations:

Orgs | Languages | Patterns | References | Standards

Object-Oriented, Object-Based, &
Encapsulation Languages:

Orgs | Languages | Patterns | References | Standards

Orgs | Languages | Patterns | References | Standards

References:

Orgs | Languages | Patterns | References | Standards

OO Standards: see also Engineering Standards

  • OO notation -- There are two major "contenders" remaining for the industry de facto standard:
  • Unified Modeling Language (UML
    • )
    • Rational recruited some "heavy hitters" in the OO word to standardize on a OO Notation [to allow Rational Rose to support multiple methods]
    • They attempted to separate the notation from the methods, which were many (see OO Methods)
    • See also: SysML and Enterprise Architecture Methods/Notations
    • The leads for developing UML were the "tres amigos" -- each had developed different approaches to object-oriented development, and were in fairly wide use in the industry:
      1. E. Grady Booch
        • The "Booch Method" was introduced when Grady was at the Air Force Academy:
          • Object Oriented Design, USAF Academy, Colo, 1980, republished in Ada Letters, Vol. 1, No. 3, March/April 1982
          • Software Engineering with Ada textbook, Benjamin/Cummings, 1983
          • The industry starting referring to the package notation "Booch-O-Grams"
        • This "Booch Notation" was one of the first to be applied in commercial/defense applications, evolving out of the Ada community.
        • Grady later went to work for Rational Software
          • Rational (at that time) not only produced a Ada compilation system, they created a proprietary hardware system, the R1000, with firmware extensions, and the operating system was written entirely in Ada for Ada [see Tools and HW-SW].
          • Rational invented the "subsystem" construct to help deal with complexity
          • Rational implemented their Rational Environment using Subsystems, and also provided it to developers [a "unit" above the Ada package construct, essentially a library with information hiding and a generic instantiation capability]
          • That concept was included in Grady's text: Software Components with Ada -- Structures, Tools, and Subsystems, Benjamin/Cummings, 1987
      2. Ivar Jacobson
      3. Jim Rumbaugh
        • Rumbaugh, et al developed the OMT: Object Modeling Technique
        • He also joined Rational
    • Together they defined, not only the notation...
      • The public Unified Modeling Language (UML), which they submitted to OMG for industry "buy-in" and adoption, but also
      • Initially market the Rational Objectory Process®, which eventually evolves into
      • The Rational Unified Process®, an integrated combination of the best of their three methods  
  • OPEN (Object-oriented Process, Environment and Notation)
    • Notation is called OML, or the OPEN Modeling Language
      • The other proposed industry standard (compare with UML)
      • The lead team is Brian Henderson-Sellers (MOSES), Ian Graham (SOMA) and Don Firesmith (ADM3). Other consortium members include Ed Yourdon and Meiler Page-Jones.
    • OPEN Process Framework (OPF), a public-domain object-oriented framework of free, open source, reusable method components (i.e., classes of process components).
    • See US mirror site: http://www.markv.com/OPEN
    • BOM (Business Object Model)
  • "Vender-Neutral"
    • See Languages above
    • CORBA (Common Object Request Broker Architecture)
      • CORBA is an evolving standard for object-oriented event system architectures. It defines an interface definition language, an object request broker, and object adaptors.
      • Vendor-supplied objects must comply to the framework
      • Schmidt's CORBA page http://www.cs.wustl.edu/~schmidt/corba.html 
      • IONA Technologies http://www.iona.com/
  • Non-Portable:
    • Microsoft COM (Component Object Model) works only on the Microsoft Windows-family of Operating Systems using Windows services. The family of COM technologies includes COM+, Distributed COM (DCOM) and ActiveX® Controls Microsoft's Object Linking and Embedding that users see on their display, COM provides the underlying services of interface negotiation, life cycle management (determining when an object can be removed from a system), licensing, and event services (putting one object into service as the result of an event that has happened to another object).
    • Microsoft OLE (Object Linking and Embedding) provides services for the compound document (includes different data types, such as text, audio files, and motion video files)
    • IBM SOM (System Object Model) is an object-oriented shared library system. SOM is much more robust in terms of fully supporting a wide variety of OO languages. Whereas basic COM essentially defines a cut-down version of C++ to program to, SOM supports almost all common features and even some more esoteric ones. For instance SOM supports multiple inheritance, metaclasses and dynamic dispatching.
    • IBM DSOM is a distributed version of SOM, based on CORBA, allows objects on different computers to communicate.

Links: Resume | Papers | Courses | Consulting | ContEd | HW/SW | Tech Interests
For OO Tools, see: CASE/SEE Tools, and Reuse Libraries | For OO Methods, see: Development Methods
For other OO-Related content, also see: Conferences | Methods | Engineering Standards | Macintosh | EVB Software Engineering

Links Above: Top | Orgs | Languages | Patterns | References | Standards

 ©1994-2007 Gregory M. Bowen, CSDP