702 See also section 3.7, the Annotated Bibliography, and appendix d. The

1136 polymorphic type system [Wikstrom 87]. Russell (see Appendix E) is a more

1200 Owl, an experimental C++ extension (See Appendix E,

1235 forthcoming, however see APPENDIX E).

1333 Appendix B also contains references for object-oriented interfaces to

1334 relational databases and see APPENDIX E, Papers, Persistent Operating Systems.

1355 Refs to be included in future FAQs. See also Appendix E.

1364 Apertos (Meta-Object-based Mikro-Kernel. See Appendix E, Papers:28)

1365 Chorus Micro-kernel (written in C++, COOL, See Appendix E, Papers:63)

1366 Choices (research OS, UofI, C++, supports SVR4, See Appendix E, Papers)

1372 Peace (OO family-based parallel OS, See Appendix E, General)

1382 See also APPENDIX E, PAPERS, Persistent Operating Systems entry.

1424 See APPENDIX D for CASE systems supporting these methodologies (several from

1668 > ILU (free, see APPENDIX E entry 59)

1684 consider making other platforms available if enough interest. See Appendix E.

1925 See Appendix E:65 for a complete description and anon FTP info.

2337 gcsurvey.ps. [See APPENDIX E]

2348 and Appendix G.

application

120 Application Objects - In the Object Model

302 The Meta-Class can also provide services to application programs, such as

725 "An investigation of a specific application area that seeks to identify the

958 application of that function.

1083 handles the message in its own way (OO). If an (application) object can cut

1513 object-oriented languages, systems, databases and application

1520 handling distribution of messages between application objects in

1528 many application domains and which will be made available through OMA

1543 application request handling software "bus."

1760 designed to let developers write one application and then deploy it --

1763 can concentrate on the application itself without needing to know multiple

1764 operating systems, networking protocols or where application objects are

1832 combined into one application. The Developer's Kit is scheduled to be

1888 DOME is non-intrusive, meaning that the application development

1890 distributed object management; this allows the application to

2132 application program and the operating system and that, in a

2146 application in the enterprise, accessing virtually any data.

2644 (bruce@utafll.uta.edu). It is a general superclass for application

behavior

8 Object-oriented programming has roots that can be traced to the 1960s. As hardware and software became increasingly complex, manageability often became a concern. Researchers studied ways to maintain software quality and developed object-oriented programming in part to address common problems by strongly emphasizing discrete, reusable units of programming logic[citation needed]. The technology focuses on data rather than processes, with programs composed of self-sufficient modules ("classes"), each instance of which ("objects") contains all the information needed to manipulate its own data structure ("members"). This is in contrast to the existing modular programming that had been dominant for many years that focused on the function of a module, rather than specifically the data, but equally provided for code reuse, and self-sufficient reusable units of programming logic, enabling collaboration through the use of linked modules (subroutines). This more conventional approach, which still persists, tends to consider data and behavior separately.

84 "An object has state, behavior, and identity; the structure and behavior of

213 window and icon objects display different behavior (although cognitive

270 of structure (instance variables), behavior (methods), and inheritance

271 (parents, or recursive structure and behavior) for objects. As pointed out

286 behavior." "A single object is simply an instance of a class."

534 specialized behavior. All routines in Smalltalk are overridable and non-

593 A method implements behavior, which is defined by [Booch 91, p80]:

594 Behavior is how an object acts and reacts, in terms of its state changes

708 abstractions and mechanisms that provide the behavior that this model

714 of externally observable behavior; a complete, consistent, and feasible

718 behavior and adding details needed for actual computer system implementation,

914 specifies slightly different or additional structure or behavior for an object,

995 more than required. Since derived classes can inherit structure and behavior

1057 overrode the virtual method from its base class, providing specialized behavior

1096 simple call. It also allows small packages of behavior, improving coherence

1190 behavior. [Liskov 93] provides a recent exposition.

email

129 a review of their last conference is available by email thanks to Adam

131 **There is a patterns mailing list, email: patterns-request@cs.uiuc.edu,

867 the CMM. To join the ami mailing list email to:

1350 ODMG, send an email message to info@odmg.org and you will receive an

1499 Feel free to call, fax or email for more information.

1974 8-34 Percy Place, email: pth@iona.ie

2110 Email: Randy.Volters@ColumbiaSC.NCR.COM

2443 Programming that have been mentioned to me over the net, in email,

2455 email: dshaker@qualix.com

2511 J. Vol 11, No 3. One author's email address is

2519 Conference, October 1993, Toronto. Email addresses for authors

2529 email address is "ac690@cleveland.freenet.edu".

2541 Copies of the postscript file can be obtained by sending email

2557 via email. The author can be reached at info@testing.com.

2675 email: shaun@iplbath.demon.co.uk

2693 voice: 1-415-957-1441, email: info@soft.com) has a coverage tool for C++

2701 Test Environment Toolkit). To join the group of volunteers, send email to

2708 other FTP sites - sned email to the above address if you can provide

examples

2 In the domain of object-oriented programming an object is usually taken to mean an ephemeral compilation of attributes (object elements) and behaviors (methods or subroutines) encapsulating an entity. In this way, while primitive or simple data types are still just single pieces of information, object-oriented objects are complex types that have multiple pieces of information and specific properties (or attributes). Instead of merely being assigned a value, (like int =10), objects have to be "constructed". In the real world, if a Ford Focus is an "object" - an instance of the car class, its physical properties and its function to drive would have been individually specified. Once the properties of the Ford Focus "object" had been specified into the form of the car class, it can be endlessly copied to create identical objects that look and function in just the same way. As an alternative example, animal is a superclass of primate and primate is a superclass of human. Individuals such as Joe Bloggs or John Doe would be particular examples or 'objects' of the human class, and consequently possess all the characteristics of the human class (and of the primate and animal superclasses as well).

12 In the 1970s, Kay's Smalltalk work had influenced the Lisp community to incorporate object- based techniques that were introduced to developers via the Lisp machine. Experimentation with various extensions to Lisp (like LOOPS and Flavors introducing multiple inheritance and mixins), eventually led to the Common Lisp Object System (CLOS, a part of the first standardized object-oriented programming language, ANSI Common Lisp), which integrates functional programming and object-oriented programming and allows extension via a Meta- object protocol. In the 1980s, there were a few attempts to design processor architectures that included hardware support for objects in memory but these were not successful. Examples include the Intel iAPX 432 and the Linn Smart Rekursiv.

46 Languages called "pure" OO languages, because everything in them is treated consistently as an object, from primitives such as characters and punctuation, all the way up to whole classes, prototypes, blocks, modules, etc. They were designed specifically to facilitate, even enforce, OO methods. Examples: Scala, Smalltalk, Eiffel, JADE, Emerald.

47 Languages designed mainly for OO programming, but with some procedural elements. Examples: C++, C#, VB.NET, Java, Python.

48 Languages that are historically procedural languages, but have been extended with some OO features. Examples: Visual Basic (derived from BASIC), Fortran 2003, Perl, COBOL 2002, PHP, ABAP.

49 Languages with most of the features of objects (classes, methods, inheritance, reusability), but in a distinctly original form. Examples: Oberon (Oberon-1 or Oberon-2) and Common Lisp.

50 Languages with abstract data type support, but not all features of object-orientation, sometimes called object-based languages. Examples: Modula-2 (with excellent encapsulation and information hiding), Pliant, CLU.

223 values view taken by [Cardelli 85]. [Martin 92] provides some examples of

539 not have to be declared. Eiffel and BETA are examples of languages allowing

606 Selector would be another good choice for message_name in the above examples,

764 models, and even DFD's. Booch, Jacobson, and Wirfs-Brock are examples of OO

1079 programming and user interaction (e.g. GUIs). Examples can be found in

1202 [Jones 92] are all examples of OO systems providing subtype polymorphism.

1222 See [Booch 87b] for several examples in Ada and [Stroustrup xx] and [Murray

1223 93] for examples in C++.

1465 [Wilkie 93] summarizes, compares, and provides examples of Booch, Wirfs-Brock,

1937 approach to filtering, and more code examples to guide programmers.

1957 code examples it ships with the product to help developers learning how to use

oma

1494 OMA

1512 (OMA) Guide document. This document outlines a single terminology for

1528 many application domains and which will be made available through OMA

1564 OMA

1602 > Object Management Architecture Guide (OMA)

1610 supports their goals. The OMA publication outlines the

1631 Architecture (OMA) Guide for $50 each.

1636 OMA

1701 OMA

1722 OMA

1735 OMA

1843 OMA

1864 OMA

1916 OMA

1927 OMA

2006 OMA

2118 OMA

2266 OMA

ood