R. Adler, `Emerging Standards for Component Software,' IEEE Computer, Vol. 28, No. 3, March 1995, pp. 68-77.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the assembled systems in their target environments. 1.1.1 Integrators view From an integrator s point of view, a component is a blackbox with a very well defined interface. Components are a unit of composition of software architectures. There is a widespread variety of composition of components [2, 3]. For example, with CORBA and JavaBeans the components interface is a list of functions. Other more demanding component models, such as the Catalysis [4] advocate the existence of plug points or standardized connectors between components [5] 1.1.2 Producers view When designing reusable ....

R. M. Adler, "Emerging Standards for Component Software," IEEE Computer, vol. 28, pp. 68-77, 1995.

....has to effectively provide support for mobility of application components, users, and devices. 3. 1 Document Centric Middleware With the beginning of the 90ies, several companies tried to establish standards for middleware architectures supporting active documents and their coordination [1]. These middleware architectures grounded in the works of distributed object applications and middleware, like CORBA established notions of documents into which components or objects were included. The components contained data or software to manipulate the data in other components. They ....

Richard M. Adler. Emerging standards for component software. IEEE Computer, 28(3):68--77, March 1995.

....Keywords: design component, design constraints, design pattern, software architecture, role model, software reuse 1. INTRODUCTION Component based software development stands for software construction by assembly of prefabricated, configurable, and independently evolving building blocks [1, 6, 30]. Emerging software component models, such as the Component Object Model [4] and JavaBeans [28] prescribe standards for the collaboration of independent components and are aimed at improved development productivity and at more resilience of software to changing requirements [15] Current ....

Richard M. Adler. Emerging standards for component software. IEEE Computer, 28(3):68--77, March 1995.

....In addition, modem middleware has to support mobility of application components, users, and devices. 3. 1 Document centric Middleware With the beginning of the 90ies, several companies tried to establish standards for middleware architectures supporting active documents and their coordination ([1]) These middleware architectures grounded in the works of distributed object applications and middleware, like CORBA estab L Object ntered J Binary, closed J OpenDoc ] OLE others ts ] Figure 1: Document centric Middleware lished a notion of documents into which components or objects ....

Richard M. Adler. Emerging standards for component software. IEEE Computer, 28(3):677, March 1995.

....by software developers as they should be. One reason is the fact that the user s perception of an IPSE is not as homogeneous as it should be, because there are many aspects of tool integration. Emerging Component Ware Software component technology will change the way software is produced [1]. A set of heterogeneous interoperating components will replace a monolithic application. Different component producers need to cooperate in order to develop properly interoperating components. Producers weaken their enterprise boundaries by sharing and linking their development processes ....

Adler, R. M. Emerging Standards for Component Software. 1EEE Computer (March 1995), 68-77.

....Software Component based software allows the assembly of independently developed components. This approach addresses the general problem of designing an application from software components that were constructed independently by different developers with different languages and tools [6]. 2.4.8.1 OLE 2.0 OLE 2.0 (Object Linking and Embedding) of Microsoft is a set of standard specifications and implementations for component based software [13] OLE 2.0 is based on Component Object Model (COM) which ensures binary level interoperability across application components written in ....

Richard M. Adler. "Emerging Standards for Component Software". IEEE Computer, pages 68--76, March 1995.

....editing functionality with the ability to edit contents of di#erent media types. A similar approach has already been used in some single user editors #e.g. Quill #Chamberlin, 1990##. We are currently working on extending that approach to a full compound document editor #see OpenDoc standard #Adler, 1995; Nelson, 1995##. As stated in Section 2 functionality for tightly coupled cooperation, direct communication, work#ow management, brainstorming or group decision support is not in: Computer Supported Cooperative Work An International Journal, 3#3 4#, 1995, p.359 378 16 Michael Koch ....

Adler, R. M. #1995#: Emerging Standards for Component Software. IEEE Computer, 28#3#, March 1995, pp. 68#77.

....by software developers as they should be. One reason is the fact that the user s perception of an IPSE is not as homogeneous as it should be, because there are many aspects of tool integration. Emerging Component Ware Software component technology will change the way software is produced [1]. A set of heterogeneous interoperating components will replace a monolithic application. Different component producers need to cooperate in order to develop properly interoperating components. Producers weaken their enter prise boundaries by sharing and linking their development processes ....

Adler, R. M. Emerging Standards for Component Software. IEEE Computer (March 1995), 68-77.

.... reasons: CORBA implementations provide efficient interoperability across heterogeneous software platforms; being a software development platform it has an application viewpoint; CORBA deployment is rather fast in the direction for a cross compatibility with ODP (TINA) 12] OpenDoc, OLE [13] and CAD s Portable Common Tool Environment [14] adopted UNO approach [2] enables flexible distributed systems architecture. The current approach was elaborated within the STEP group of GMD FOKUS [15] as a preproject proposal aiming at highly scalable and reliable mechanism for application ....

Adler R.M., Emerging Standards for Component Software. - In Computer, March, 1995, vol.28, No. 3, p. 68-77

....the integration of heterogeneous, multilanguage, and possibly incompatible software components. It will be interesting to see how good ideas from various software design assistants can be constructively combined. 4.4 Component Frameworks Component frameworks such as OLE, CORBA, OpenDoc, etc. [1] and our coordination perspective were both motivated by the complexity of managing component interdependencies. However, the two approaches represent very different philosophies. Component frameworks enable the interoperation of independently developed components by limiting the kinds of allowed ....

Richard M. Adler. Emerging Standards for Component Software. IEEE Computer, March 1995, pp. 68-77.

.... reasons: CORBA implementations provide efficient interoperability across heterogeneous software platforms; being a software development platform CORBA has an application viewpoint; CORBA deployment is rather fast in the direction for a cross compatibility with ODP (TINA) 18] OpenDoc, OLE [19] and CAD s Portable Common Tool Environment [20] adopted UNO approach [17] enables flexible distributed systems architecture. Contract Service Remote ORB proxy Externalization Service Replication service Contract MCA Copy String IOR ObjRef Internalization Service ORB2 ORB1 Fig. 7 MCA ....

Adler R.M., Emerging Standards for Component Software. - In Computer, March, 1995, vol.28, No. 3, p. 68-77

....heterogeneous software components have existed for quite some time, but these mainly have been isolated connections between two languages, e.g. interfaces for C and FORTRAN. Recently, there has been a trend towards a more general form of interoperability, e.g. Microsoft s OLE and CI Labs OpenDoc [1]. The MOOSE project at the University of Tulsa continues this trend, espousing that interface and behavior, and not language be the primary basis for software component interoperability. This is achieved by mapping component definitions to a common substrate, allowing heterogeneous components with ....

....the related work spans many subjects: component software, distributed objects, security, and formal methods. These are described briefly in the following subsections. 3. 1 Component Software Component software technology strives to facilitate interoperability between independent software components [1]. Independent software components are those that reside on heterogeneous distributed platforms or are constructed from different tools and languages. Component software and object oriented software are very similar in that they rely on well defined interfaces to achieve interoperability. The ....

[Article contains additional citation context not shown here]

R. Adler. Emerging standards for component software. Computer, 28(3):68--77, March 1995.

....In other words, we unbundle active functionality from the DBMS. Thus, we follow a general direction that database research is currently about to take, namely to provide individual database management services that can be used and combined in a variety of ways and in a variety of environments [1, 2, 4, 11, 24]. We first discuss the advantages of unbundling active functionality. We then show how the unbundling process may take place. We start with a domain analysis of active DBMS style active functionality. The main task is the identification of components and the cooperation between them. This leads to ....

....and the cooperation between the units is not hidden within the system but can clearly be identified from outside. Considering database management systems as a form of traditionally large and monolithic software system, it makes sense to build them out from a number of cooperating components [1, 2, 4, 11, 24]. The major motivation for unbundling DBMS comes from the ever increasing demands on the functionality of DBMS because of (new) application areas (like data warehousing) new architectural forms (like distribution and heterogeneity) and technical innovations (like middleware) If one augments the ....

M. Adler. Emerging Standards for Component Software. IEEE Computer, March 2, 1995.

....time, but these mainly have been isolated connections between two languages, e.g. interfaces for C and FORTRAN. Recently, there has been a trend towards a more general form of interoperability, e.g. OMG s Common Object Request Broker Architecture (CORBA) 48] Microsoft s OLE and CI Labs OpenDoc [1]. 2.1.2 Transparency While achieving interoperability of heterogeneous software components in distributed systems is a major goal of this work, transparency is equally important. Transparency is a critical issue to developers and users. The developer of the specialist s diagnostic application ....

....which can be used to provide high assurance to a computing enterprise, are used to supply a formal foundation to the architecture and to link the rest of the layers. 2.2. 1 Component Software Component software technology facilitates interoperability between independent software components [1, 52]. Such components commonly reside on heterogeneous distributed platforms and are often designed with different tools and languages. Component software and object oriented software are very similar in that they rely on well defined interfaces to achieve interoperability. The difference between the ....

[Article contains additional citation context not shown here]

R. Adler. Emerging standards for component software. Computer, 28(3):68-- 77, March 1995.

....complete with reusable class libraries and frameworks meant to make programming easier Brad Cox [8] has gone as far as to propose that almost all programming should be based on reusable object oriented components. Is component software to be restricted to user level components, as in OpenDoc [2], or is Cox right Could the problem be in the difficulty in unlearning previously taught non reuse strategies If so, shound t reuse be the starting point for learning programming concepts, rather than an afterthought at best: something learnt in the workplace, or possibly relegated to a software ....

R M Adler. `Emerging Standards for Component Software', Computer, 28(3):68--76 March 1995.

....object editor application in another window. One possible future extension would be to extend that application by editing functionality for other object types (see EZ for an example) We are further planning to apply the compound document editor concept presented in the OPENDOC and OLE standards [Adler95, Nelso95]. That means that we will have different part editors for all possible medium types and a combi editor shell that integrates these part editors in one display window. 4.4 Standard editor shells One requirement for multi user editors was that the users want to use their favorite interfaces in the ....

R. M. Adler. Emerging Standards for Component Software. IEEE Computer, 28(3):68--77, March 1995.

....Real Time Application Figure 1. The Realize system provides object replication, fault recovery and real time scheduling, using the reliable ordered multicasts of the Totem system. covery, and for scheduling operations to meet real time constraints. The Realize system uses a CORBA based approach [1, 5] in which calls on objects are replaced by calls on stubs and skeletons. In the terminology of CORBA, Realize is an ORB of a specialized nature that must accommodate object replication, fault detection and recovery, and real time scheduling. Realize services include the ability to encapsulate ....

R. M. Adler, "Emerging standards for component software," Computer, vol. 28, no. 3, March 1995, pp. 68-77.

.... and change its mind about which results to focus resources on and which to discontinue interest in (cancel) Second, Petra Flow generalizes to applications that consist of multiple (distributed) processes that are cooperating either in a nested application model, such as OLE [61] and OpenDoc [3], or in a client server relationship via sockets or remote procedure calls [13] In such a scenario, the Petra Flow graph spans multiple processes with dependence arcs along the communication channels. The implementation would require a parallel channel to communicate at the meta level, i.e. ....

R. M. Adler. Emerging standards for component software. Computer, 28(3):68-- 77, March 1995.

....1997 includes the development of design handbooks for activities and dependencies as well as a design process for generating executable systems by successive specializations of their architectural descriptions. 5.3 Component Frameworks Component frameworks such as OLE, CORBA, OpenDoc, etc. [1] facilitate the interoperation of independently developed components by limiting the kinds of allowed interactions and by providing a standardized infrastructure for managing them. Component frameworks and our coordination perspective represent two very different philosophies in component based ....

Richard M. Adler. Emerging Standards for Component Software. IEEE Computer, March 1995, pp. 68-77.

No context found.

R. Adler, `Emerging Standards for Component Software,' IEEE Computer, Vol. 28, No. 3, March 1995, pp. 68-77.

No context found.

R.M. Adler, "Emerging Standards for Component Software", IEEE Computer, March 1995, pp. 68-76.

No context found.

Adler R.: Emerging Standards for Component Software. IEEE Computer Vol. 28 No. 3, March 1995.

No context found.

Adler, R.M.: Emerging Standards for Component Software. IEEE Computer, March 1995, pp. 68-77.

No context found.

Richard M. Adler, "Emerging Standards for Component Software," IEEE Computer, IEEE Computer Society Press, Vol. 28, No. 3, March 1995, pp. 6877.

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