R. Soley and C. Stone. (eds.). Object Management Architecture Guide. Third edition. John Wiley & Sons, Framingham MA, 164 pp., 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and distributed computing resources. The use of the object abstraction in integrating such resources is also characteristic of recent developments in application integration architectures, in particular, architectures of heterogeneous interoperable information resource environments (HIRE) [21, 24]. The HIRE architectures are built around a concept of a global object space and based on the idea of complete separation of resource specifications and encapsulated implementations. Among different attempts to support such environments is the promising activity of the Object Management Group ....

....and encapsulated implementations. Among different attempts to support such environments is the promising activity of the Object Management Group (OMG) on specifying Common Object Request Broker Architecture (CORBA) 3] which is the key piece of the OMG Object Management Architecture (OMA) [24]. The main goal of CORBA is to facilitate the development of distributed applications whose components collaborate efficiently, reliably and transparently. It defines the communication infrastructure of the object oriented software framework and provides a mechanism by which objects transparently ....

R. Soley (Ed.). Object Management Architecture Guide. Revision 2.0, OMG TC Document, September 1, 1992

....the hardest problems in modern software engineering. Among different attempts to address this problem, is the promising activity of Object Management Group (OMG) on specifying Common Object Request Broker Architecture (CORBA) 4] CORBA is the key piece of OMG Object Management Architecture (OMA) [20]. It defines the communication infrastructure of the object oriented software framework and provides mechanisms by which objects transparently make requests and receive responses. Object Request Broker (ORB) supports interoperability between applications on different machines in heterogeneous ....

R. Soley (Ed.). Object Management Architecture Guide. Revision 2.0, OMG TC Document, September 1, 1992.

....and start up time changes, the environment allows dynamic changes. We have argued for a flexible operating system architecture. p assures flexibility by incorporating three features. Unlike classical objects where an event generator must specify the handling object, the generalized object model [19] permits the environment to make the decision dynamically. Meta computing [13] 8] allows the manipulation of the reified aspects of a subsystem. As a subsystem is modified, the evolution of related interfaces can be handled through version set interfaces [18] 4.7: Generalized objects The ....

....aspects of reflection. Emerald [4] has shown the importance of type conformity in distributed systems. Even industrial projects are paying increasing attention to flexible interaction between objects and facilities for dynamic modifications. One of the most important is CORBA by OMG [15] [19]. CORBA is a software platform for cooperation between objects in a heterogeneous distributed environment. It is based on the classical object model and uses a subset of C for interface specification. A second project viz. IBM s DSOM [9] aims at inter language interoperability and provides basic ....

R. Soley (ed), Object Management Architecture Guide, OMG TC Document 90.9.1: Object Management Group, 1990.

.... have attempted to employ the Web in increasingly sophisticated applications, these applications have begun to overlap in complexity the sorts of distributed applications for which distributed object architectures such as OMG s CORBA, and its surrounding Object Management Architecture (OMA) [Sol95] were originally developed. Since the Web was not originally designed to support such applications, Web application development efforts increasingly run into limitations of the basic Web infrastructure. If the Web is to be used as the basis of complex enterprise applications, it must provide ....

R. Soley (ed.), Object Management Architecture Guide, Third Edition, Wiley, June 1995 <ftp://ftp.omg.org/pub/docs/ab/95-05-05.ps>.

.... (EC DTF) It provides a high level object oriented framework for specification of requirements for electronic commerce systems, designed in accordance with OMG s Object Management Architecture a generic set of components, interfaces, and protocols for distributed object oriented applications [13]. The OMG architecture is broadly based on the eCo System framework, and it provides a similar multi layer interoperability framework. Related functional requirements are grouped into a number of containers called facilities. Facilities are, in turn, categorized into market infrastructure services ....

R. M. Soley, editor. Object Management Architecture Guide , Revision 3.0. John Wiley and Sons, New York, 3rd edition, June 1995.

....years which ensure interoperability among heterogeneous hardware platforms and software packages from different vendors. Object technology has been used to describe interfaces and interaction patterns for such distributed applications. The Common Object Request Broker Architecture (CORBA) OMG 95, Soley 95] is the most successful representative of an object based distributed computing infrastructure. There are a number of commercially available implementations of CORBA, which we refer to as object request brokers (ORBs 1 ) as a shorthand. 1. Throughout this report the term ORB will be used to ....

....specification for object based interprocess communication in distributed, heterogeneous environments. CORBA has been standardized by the Object Management Group (OMG) an industry group of over 600 computer manufacturers and independent software vendors. The current version of CORBA, version 2. 0 [Soley 95] was specified in 1995. There are many COTS implementations of CORBA available in the marketplace; we refer to such implementations as object request brokers (ORBs) and are careful to distinguish between CORBA (a specification) and ORB (an implementation) CORBA provides transparent ....

Soley, R. M., ed. Object Management Architecture Guide, 3rd ed. New York, NY: John Wiley & Sons, 1995.

....computing platform yields a framework in which objects are distributed across the system. Objects invoke other objects, or are themselves invoked, to provide services to the application. The Object Management Group (OMG) has established the Common Object Request Broker Architecture (CORBA) [12, 14, 15, 17, 18], which is a standard for communications middleware that defines interfaces to distributed objects and that provides mechanisms for communicating operations to objects by means of messages. The key component of this architecture is the Object Request Broker (ORB) which handles requests to, and ....

R. M. Soley, Object Management Architecture Guide, Object Management Group, OMG Document 92-11-1.

....Workflow systems are expected to work in distributed heterogeneous environments which are very common in enterprises of even moderate complexity. CORBA is one of the major standardization initiatives of the computer industry for handling heterogeneity in distributed environments (OMG 1991, Soley and Stone 1995). CORBA provides a standard communication mechanism which enables distributed objects to operate on each other. In CORBA only the ORB (Object Request Broker) knows the implementation details and actual locations of the components (objects) in the system. Clients and servers only know the ....

Soley, R. M., and Stone, C. M., "Object Management Architecture Guide", Third Edition, John Wiley & Sons, 1995.

....distributed across a healthcare enterprise. Since all clinical and some business services are eventually expected to be integrated into the CPR infrastructure, it is considered as an enterprise itself. CPR architecture is being constructed utilizing the Object Management Architecture described in [Soley 1996]. CORBA compliant ORBs constitute a distribution backbone for CPR components. All deployed application systems are selected according to the criteria of the best fit for a particular business process they serve and according to the mandatory requirement to comply with CPR architecture. ....

R. M. Soley and C. M. Stone, Object Management Architecture Guide, 3 ed. John Wiley & Sons, 1996.

.... The most important distributed object architectures today are: f OMG CORBA (Object Management Group Common Object Request Broker Architecture) f Microsoft DCOM (Distributed Component Object Model) and f Java RMI (Remote Method Invocation) All architectures share the same basic concepts [11, 14], although they differ in details. It is important to understand, that CORBA is not a product. It is a specification which is used by several software vendors to deliver their CORBA compliant products. Different CORBA implementations are Iona Orbix, Inprise Visibroker, BEA ObjectBroker, Expersoft ....

Soley R. M., Ph.D. (1995), Object Management Architecture Guide, OMG, John Wiley & Sons, Inc., Revision 3.0, Third Edition

....no requirement for centralized services in this specification, so there are no inherent restrictions on scalability. 1. 5 Relationship to Existing OMG Specifications The Activity Service specification is directly based upon the following OMG technology: OMG CORBA Object Request Broker (ORB) [1]. OMG Interface Definition Language (IDL) 2] OMG Object Transaction Service (OTS) It is anticipated that the Activity Service will aid, if desired, the deployment of the following OMG technologies: OMG Workflow Management Facility. The Activity Service specification requires the ....

R. Soley (ed.), Object Management Architecture Guide, Third Edition, Wiley, June 1995.

....developers can be served by a centralised ASG database server. Therefore, distributed ASG servers are needed for different viewpoint subgraphs to overcome this performance bottleneck. An architecture that has faced the challenge to support distributed and heterogeneous computation is OMG s CORBA [Sol92] Its specification defines a common interface definition language (IDL) an object oriented language to define classes, inheritance relationships, attributes and operations. Modules can be used to group a set of related classes. Grouping classes into a module restricts the the visibility of ....

R. M Soley, editor. Object Management Architecture Guide. Technical report, Object Management Group, 492 Old Connecticut Path, Framingham, MA 01701, USA, 1992.

....The most important distributed object architectures today are: OMG CORBA (Object Management Group Common Object Request Broker Architecture) Microsoft DCOM (Distributed Component Object Model) and . Java RMI (Remote Method Invocation) All architectures share the same basic concepts [11, 14], although they differ in details. It is important to understand, that CORBA is not a product. It is a specification which is used by several software vendors to deliver their CORBA compliant products. Different CORBA implementations are Iona Orbix, Inprise Visibroker, BEA ObjectBroker, Expersoft ....

Soley R. M., Ph.D. (1995), Object Management Architecture Guide, OMG, John Wiley & Sons, Inc., Revision 3.0, Third Edition

....but also to the ORB and thus works with standard commercial CORBA ORBs. The difficult issues of replication, consistency, fault detection and recovery are handled by Eternal and are hidden from the application programmer. 1 Introduction The Common Object Request Broker Architecture (CORBA) [10, 12] established by the Object Management Group (OMG) facilitates the development of distributed applications by providing for location transparency, separation between specification and implementation, and interworking of heterogeneous languages, architectures and operating systems. The Eternal ....

R. M. Soley, Object Management Architecture Guide, Object Management Group, OMG Document 92-11-1.

....used in certain decisions regarding the destinations for migrating objects. 2. 2 CORBA Object Management Group (OMG) which is a consortium of several companies including Sun, HP, DEC, and IBM, attempts to define the various facilities that are necessary for distributed object oriented computing [3]. This definition, which is popularly known as the the Object Management Architecture (OMA) Reference Model, is shown in Figure 2.2. The central component of this model is the Object Request Broker (ORB) which is responsible for transparent communication between objects. In other words, it ....

R.M. Soley and C.M. Stone, The Object Management Architecture Guide. John Wiley & Sons, Inc., third ed., July 1995.

....and distributed computing resources. The use of the object abstraction in integrating such resources is also characteristic of recent developments in application integration architectures, in particular, architectures of heterogeneous interoperable information resource 1 environments (HIRE) [21, 24]. The HIRE architectures are built around a concept of a global object space and based on the idea of complete separation of resource specifications and encapsulated implementations. Among different attempts to support such environments is the promising activity of the Object Management Group ....

....and encapsulated implementations. Among different attempts to support such environments is the promising activity of the Object Management Group (OMG) on specifying Common Object Request Broker Architecture (CORBA) 3] which is the key piece of the OMG Object Management Architecture (OMA) [24]. The main goal of CORBA is to facilitate the development of distributed applications whose components collaborate efficiently, reliably and transparently. It defines the communication infrastructure of the object oriented software framework and provides a mechanism by which objects transparently ....

R. Soley (Ed.). Object Management Architecture Guide. Revision 2.0, OMG TC Document, September 1, 1992

....interprocess communication remains the only feasible means of synchronization. We further assume that failures respect the fail stop model [21] which means that objects fail by crashing without the emission of spurious messages. In analogy to the OMG Object Management Architecture (OMA) [23], the Electra object model consists of objects implemented in various programming languages scattered over an arbitrary number of machines. The ORB is the communication heart in the model. It provides an infrastructure allowing objects to communicate, independent of the specific programming ....

Soley, R. M. Object Management Architecture Guide. Object Management Group. OMG Document 92-11-1.

....applications need to accommodate several programming languages and to access legacy information systems. Heterogeneity, interoperability, and extensibility must thus be addressed by the system software used to develop next generation business applications. The Object Management Architecture (OMA) [12], proposed by the Object Management Group (OMG) aims at reducing complexity, lowering development costs, and hasten the introduction of new applications. OMG plans to accomplish this through the introduction of the CORBA architectural framework [10] of a standard interface dec Work supported ....

R. M. Soley. Object Management Architecture Guide. Object Management Group. OMG Document 92-11-1.

....handlers when the agreements are violated. 1. INTRODUCTION In recent years the benefits of object oriented technology have led to its widespread use in all areas of software development. Achieving Interoperability using objects is gaining acceptance with the adoption of the CORBA standard [1,2]. However, the functional interoperability that CORBA offers is only a part of the object oriented support that many distributed applications need, since they must cope with an environment that is dynamic. Most distributed applications, other than multimedia based ones such as video and audio, do ....

Soley, Richard M. ed. Object Management Architecture Guide, Object Management Group, 1993.

....to intercept object base operations and redirect them to OOS, thus providing genuine persistence for Software Refinery. Architecture independent The final development would be to express OOS operations in terms of an architecture independent interface to persistent object bases (e.g. CORBA [20]) so that the UFS prototype implementation could be replaced by whatever industrialstrength object bases are found desirable. Summary The effects of these developments on the capabilities of Software Refinery should be as follows. VHLL Wide spectrum programming is enhanced in two ways. First, ....

Soley, R.M. (ed.), "Object Management Architecture Guide", Object Managament Group (1992).

....the first step in achieving a flexible realization. Next, we must determine which objects have reified aspects and how the effects of changes are propagated and controlled. 4. 4 Event Management Flexible event management is provided in the Pi architecture through the generalized object model [Soley, 1990] and metacomputation [Maes, 1987b] The generalized object model capitalizes on the decoupling of event generation and handling. One problem with conventional operating system design is that an object that is not a part of the operating system has no way of knowing when certain events occur. ....

R. Soley (ed) (1990) Object Management Architecture Guide, OMG TC Document 90.9.1: Object Management Group, Framingham, MA.

....The query processing approach presented in this paper is implemented in the MIND (METU Interoperable DBMS) project (Dogac, A. et al 1995b; Dogac, A. et al 1995c; Dogac, A. et al 1996; Kilic, E. et al. 1995) MIND architecture is based on OMG s 1 distributed object management architecture (Soley, 1992). The infrastructure of the system is build on a CORBA implementation, namely DEC s ObjectBroker 2 (DEC, 1994) An interface of a generic Database Object through CORBA IDL has been defined and multiple implementations of this interface for Sybase 3 , Oracle7 4 , Adabas D 5 and MOOD (METU ....

Soley, R. M. (1992). Object Management Architecture Guide.

....immediately. Finally, message based integration frameworks do not support concurrency control and also do not remove the performance bottleneck of a central database server. 3. 3 OMG CORBA These problems are reasonably well solved in OMG s common object request broker architecture (CORBA) [10]. Figure 1 displays an overview. The core component of this architecture is an object request broker (ORB) which is specified in detail in [11] An ORB delivers a client s request for invoking an operation to a server object, which will execute the operation and then the ORB will deliver the ....

R. M Soley, editor. Object Management Architecture Guide. Technical report, Object Management Group, 492 Old Connecticut Path, Framingham, MA 01701, USA, 1992.

.... over a period of hours or days in the case of computationally intensive algorithms such as finite element analysis, is queued to an event channel, of which many varieties with alternative coordination models are defined by the Object Management Group s (OMG) Object Management Architecture (OMA) [5]. This pattern is quite general, and can be used to encapsulate any component ComponentB ExternalState( Status ( Consistent ( various types of OMA ComponentA ExternalState( Status ( Consistent ( event channel execute operation write output to channel Consistency ExternalState( ....

Soley, R. (ed.): Object Management Architecture Guide, John Wiley and Sons, Inc. (1995)S

.... is influenced by the existing work in the literature in the following respects: ffl The query processing architecture suggested in [19] affected the design of the system described in [16] 5] 6] 21] and [22] Yet, our architecture is based on OMG s distributed object management architecture [30], as explained in Section 3. ffl In this paper, the work presented in [7] is used in estimating the time taken by global subqueries. In [7] it is assumed that participating DBMSs are autonomous and may not be able, even if they are willing, to provide the cost model parameters. The strategy in ....

....3. An Environment for Multidatabase Query Processing The query optimization approach presented in this paper is being implemented in the MIND (METU INteroperable DBMS) project described in [5, 6, 8, 16, 21, 22] MIND architecture is based on OMG s 1 distributed object management architecture [30]. The infrastructure of the system is built on a CORBA implementation, namely DEC s ObjectBroker 2 [16] We have defined an interface of a generic Database Object through CORBA IDL and developed multiple implementations of this interface for Sybase 3 , Oracle7 4 , Adabas D 5 and MOOD (METU ....

R. M. Soley. Object Management Architecture Guide, OMG, Second Edition, 1992.

....decisions and tradeoffs in keeping the framework simple yet flexible. We also outline the interface of the main components of the framework in IDL, as well as the major algorithms that govern the operation of the framework. Section 4 describes the prototyping of our proposed framework in the CORBA [11] distributed object computing environment to provide optimized data streaming support. We take advantage of CORBA to simplify the channel configuration process, and use Java as a safe and platform independent language to allow a senderside stack layer implementation to be supplied by the ....

R. M. Soley, editor. Object Management Architecture Guide (2nd Edition). Object Management Group, 1992.

....spatial data repositories. GeoPOM is developed as part of the Open Architecture Scientific Information System (OASIS) project [21, 20] OASIS provides an extensible, seamless environment for scientific data analysis, knowledge discovery, visualization, and collaboration based on CORBA [27]. In OASIS, we use geoPOM to implement the persistent state of geoscientific CORBA objects in a data repository independent way. GeoPOM facilitates access to data in repositories while maintaining their autonomy, and keeping the data in the repositories. GeoPOM provides an object oriented data ....

R. M. Soley, editor. Object Management Architecture Guide (2nd Edition). Object Management Group, 1992.

.... has been used, an alternative option would be to use the high level and persistence features of AprilQ to enhance the expresiveness and declarativenes of the system An alternatice software platform that has been used for the development of Cooperative systems is the OMA (CORBA) architecture ([4]) This architecture offers the middleware, which distributed objects can use to exchange messages transparently. Part of this architecture is the Object Request Broker (ORB) which allows the transparent exchange of requests and responses between objects. CORBA is a generic architecture intended ....

R. Soley (ed.). Object Management Architecture Guide, Third Edition. Wille, June 1995.

....The system interface may allow changes to the constructor and the destructor, the resources used during the lifetime and response to generated and notified events for an object. 5. 4 Event Management Flexible event management is provided in the p architecture through generalized object model [Soley, 1990] and metacomputation [Maes, 1987b] The generalized object model capitalizes on the decoupling of the generator and the handler(s) of an event. On the other hand, the classical object model requires a client object to know the server object for invocation of a method. By eliminating this ....

R. Soley (ed) (1990) Object Management Architecture Guide, OMG TC Document 90.9.1: Object Management Group.

....objects. Object Model: A single design portability abstract model. Object Services: Provide the main functions for realizing basic object functionality. Common Facilities: Comprise facilities which are useful in many application domains. The main reference on the activities of the OMG is [Sole 92a]. Standardization Efforts of the ODMG The ODMG was formed in the summer of 1991 out of six representatives of companies developing object oriented database systems. The companies are: Versant, Object Technology, Object Design, SunSoft, ONTOS, O2 Technology, and Objectivity. Firstly they ....

....with four design dimensions in Chapter 5. Card 85a] Definition of object oriented languages on p 481ff. Catt 94a] Detailed description of the ODMG efforts. Loom 93b] Introduction of the ODMG efforts on standardization. Nier 89a] He gives a very general definition of object orientation. [Sole 92a]: Reference Manual concerning the OMG efforts. Wegn 90a] Definition of object oriented languages on p 26ff, p 44ff. X3 S 91a] Final report of the OODBTG. Describes also shortly efforts of the OMG. 49 ....

Soley R. M. (ed.), "Object Management Architecture Guide", OMG, 1992.

.... namely object oriented analysis and design (OOA OOD) Formal Description Techniques (FDTs) and object based distributed architectures, in our case, the Object Managment Group (OMG) Common Object Request Broker Architecture (CORBA) specification [22] of their Object Management Architecture (OMA) [23]. Each of these technologies covers some of the requirements on distributed application software development so that a development process in which they can all be integrated would be a significant advance. However, although in isolation each of them is sufficiently mature for industrial usage, ....

R. M. Soley (ed.). "Object Management Architecture Guide." Working Paper OMG TC Document 92.11.1, Object Management Group, Framingham, MA (USA), Sept. 1992.

....yet meaningless, information and can remain focused on the task at hand. To meet OASIS design goals, we are exploiting the emerging distributed object management system (DOMS) technology as promoted by the Object Management Group s (OMG) Common Object Request Broker Architecture (CORBA) standard [3]. CORBAcompliant software is now available from many vendors and, now that a on the wire protocol standard for inter ORB communication has been adopted (CORBA 2.0) interoperability between different vendors implementation of CORBA on heterogeneous platforms will be supported. The basic idea ....

R. M. Soley, editor. Object Management Architecture Guide (2nd Edition). Object Management Group, 1992.

....to a great extent. Common Object Request Broker Architecture (CORBA) is a well established DOM technology which has been used successfully for the implementation of complex systems including multi databases [2, 3] CORBA is the communication mechanism of the Object Management Architecture (OMA) [6] proposed by Object Management Group (OMG) It provides a virtually local and homogeneous environment over the actual distributed, heterogeneous environment. Changes in object implementations, or object relocations are transparent to the client. Object interfaces are defined using Interface ....

Soley R.M. (ed.), Stone C.M. Object Management Architecture Guide, Third Edition, John Wiley & Sons, 1995.

....more than 600 members from industry, research institutions and academia, CORBA promises interoperability between different object systems working on a variety of computer platforms. Actually, the term CORBA refers to the Object Request Broker component of the Object Management Architecture (OMA) [SoSt95] also developed by OMG, and discussed below. Object Management Architecture The basic components of the object management architecture are the object request broker, the application objects, the CORBA facilities [OMG95b] and the CORBA services [OMG96] as shown in Figure 3 5 below. Application ....

Soley, R.M., Stone, C.M. Object Management Architecture Guide. Revision 3.0. New York, USA: John Wiley & Sons, 1995. 164p. ISBN 0471 -14193-3.

....they tend to evolve more easily. The OMG CORBA standard [13] permits the design of open distributed systems in an object oriented fashion by providing an infrastructure that allows objects to communicate independent of the specific programming languages and techniques used to implement the objects [16]. Open systems avoid excessive dependence on a single manufacturer, or on a certain operating system, hardware, or programming language, and thus offer customers freedom of choice. Development risks are reduced, and enterprises can choose the components of a distributed system according to ....

....years we have been designing and implementing CORBA environments for reliable distributed applications. The results of our work are a set of new abstractions as well as Orbix Isis [7] and Electra [10] two object request brokers for reliable distributed systems. We enhanced the OMA Model [16] with object groups and virtually synchronous program execution. The rest of the paper is structured as follows. Section 2 stipulates requirements for a reliable CORBA environment. Section 3 deals with the low level system support necessary to implement the reliable CORBA. In Section 4 and 5 we ....

Soley, R. M. Object Management Architecture Guide. Object Management Group. OMG Document 92-11-1.

.... ability to group as29 sociated entities according to common properties and polymorphism which is the ability of abstractions to overlap and intersect [NWM93] OMG s OMA is a promising attempt for a standard architecture that joins distributed computing and object oriented programming technologies [OHE96a, NWM93, SS95]. 2.3.1 Object Management Architecture OMA defines a Reference Model identifying and characterizing the components, interfaces, and protocols that compose a distributed object architecture. The OMA object model supports encapsulation, abstraction and polymorphism. The reference model has four ....

R.M. Soley (ed.), C.M. Stone, Object Management Architecture Guide, Third Edition, John Wiley & Sons, 1995.

....The system interface may allow changes to the constructor and the destructor, the resources used during the lifetime and response to generated and notified events for an object. 4.3. 4 Event Management Flexible event management is provided in the Pi architecture through generalized object model [Soley, 1990] and metacomputation [Maes, 1987b] The generalized object model capitalizes on the decoupling of the generator and the handler(s) of an event. On the other hand, the classical object model requires a client object to know the server object for invocation of a method. By eliminating this ....

R. Soley (ed) (1990) Object Management Architecture Guide, OMG TC Document 90.9.1: Object Management Group, Framingham, MA.

No context found.

R. Soley and C. Stone. (eds.). Object Management Architecture Guide. Third edition. John Wiley & Sons, Framingham MA, 164 pp., 1995.

No context found.

Soley, Richard Mark (ed.), Object Management Architecture Guide, John Wiley & Sons Inc., 1992,

No context found.

R. Soley (ed.), Object Management Architecture Guide, Third Edition, Wiley, June 1995.

No context found.

R. M. Soley, C. M. Stone, and Object Management Group., Object Management Architecture Guide, Rev. 3.0, 3rd ed. New York, NY: J. Wiley, 1995.

No context found.

R. M Soley, editor. Object Management Architecture Guide. Technical report, Object Management Group, 492 Old Connecticut Path, Framingham, MA 01701, USA, 1992.

No context found.

R. M. Soley. Object Management Architecture Guide. Object Management Group, Inc. (OMG). Revision 1.0, November

No context found.

R. M. Soley (ed.), Stone C.M. Stone, Object Management Architecture Guide, John Wiley & Sons, 1995.

No context found.

Soley, R.; ed. (1993) Object Management Architecture Guide, Second Revision. Object Management Group, Framingham, Mass.

No context found.

Soley R., Stone C. Object Management Architecture Guide. Third edition. John Wiley and Sons, Inc. 1995.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC