OMG OVERVIEW: CORBA and the OMA in Enterprise Computing.
Saved in:
| Title: | OMG OVERVIEW: CORBA and the OMA in Enterprise Computing. |
|---|---|
| Authors: | Siegel, Jon1 |
| Source: | Communications of the ACM. Oct98, Vol. 41 Issue 10, p37-43. 7p. |
| Subjects: | Object Management Group Inc., Programming languages, CORBA (Computer architecture), Corporations, Markets, Telecommunication, Research |
| Abstract: | When Object Management Group Inc. (OMG) was formed in 1989, interoperability was its founders primary and almost sole objective, a vision of software components working smoothly together, without regard to details of any component's location, platform, operating system, programming language or network hardware and software. When this interoperability goal was realized in 1996 with the issuance of the Common Object Request Broker Architecture 2.0 (CORBA 2.0) specification, two notable things happened, first, the infrastructure-oriented OMG members who had been concentrating on CORBA and basic services were suddenly free to expand their horizons to include extended features, as a result, the basic CORBA object model is being extended to include multiple interfaces per object, objects passable by value, a beans-like component model and support for realtime, fault-tolerant and embedded CORBA. A second result was that companies and organizations working in vertical markets started to use the 0MG Interface Definition Language to specify standard objects that all could share. This led 0MG to expand its scope through a major reorganization in early 1996, creating its Domain Technology Committee that has grown to include subgroups in Finance/Insurance, Electronic Commerce, Healthcare, Manufacturing,Telecommunications, Transportation, Life Science Research and Business Objects. Nearly simultaneous with this expansion was the formation of OMG's Analysis and Design Task Force, which adopts specifications supporting software analysis and design. INSET: Architectural Overview.. |
| Database: | Engineering Source |
| FullText | Links: – Type: pdflink Text: Availability: 0 |
|---|---|
| Header | DbId: egs DbLabel: Engineering Source An: 11872524 AccessLevel: 6 PubType: Periodical PubTypeId: serialPeriodical PreciseRelevancyScore: 0 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: OMG OVERVIEW: CORBA and the OMA in Enterprise Computing. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22Siegel%2C+Jon%22">Siegel, Jon</searchLink><relatesTo>1</relatesTo> – Name: TitleSource Label: Source Group: Src Data: <searchLink fieldCode="JN" term="%22Communications+of+the+ACM%22">Communications of the ACM</searchLink>. Oct98, Vol. 41 Issue 10, p37-43. 7p. – Name: Subject Label: Subjects Group: Su Data: <searchLink fieldCode="DE" term="%22Object+Management+Group+Inc%2E%22">Object Management Group Inc.</searchLink><br /><searchLink fieldCode="DE" term="%22Programming+languages%22">Programming languages</searchLink><br /><searchLink fieldCode="DE" term="%22CORBA+%28Computer+architecture%29%22">CORBA (Computer architecture)</searchLink><br /><searchLink fieldCode="DE" term="%22Corporations%22">Corporations</searchLink><br /><searchLink fieldCode="DE" term="%22Markets%22">Markets</searchLink><br /><searchLink fieldCode="DE" term="%22Telecommunication%22">Telecommunication</searchLink><br /><searchLink fieldCode="DE" term="%22Research%22">Research</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: When Object Management Group Inc. (OMG) was formed in 1989, interoperability was its founders primary and almost sole objective, a vision of software components working smoothly together, without regard to details of any component's location, platform, operating system, programming language or network hardware and software. When this interoperability goal was realized in 1996 with the issuance of the Common Object Request Broker Architecture 2.0 (CORBA 2.0) specification, two notable things happened, first, the infrastructure-oriented OMG members who had been concentrating on CORBA and basic services were suddenly free to expand their horizons to include extended features, as a result, the basic CORBA object model is being extended to include multiple interfaces per object, objects passable by value, a beans-like component model and support for realtime, fault-tolerant and embedded CORBA. A second result was that companies and organizations working in vertical markets started to use the 0MG Interface Definition Language to specify standard objects that all could share. This led 0MG to expand its scope through a major reorganization in early 1996, creating its Domain Technology Committee that has grown to include subgroups in Finance/Insurance, Electronic Commerce, Healthcare, Manufacturing,Telecommunications, Transportation, Life Science Research and Business Objects. Nearly simultaneous with this expansion was the formation of OMG's Analysis and Design Task Force, which adopts specifications supporting software analysis and design. INSET: Architectural Overview.. |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=11872524 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1145/286238.286246 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 7 StartPage: 37 Subjects: – SubjectFull: Object Management Group Inc. Type: general – SubjectFull: Programming languages Type: general – SubjectFull: CORBA (Computer architecture) Type: general – SubjectFull: Corporations Type: general – SubjectFull: Markets Type: general – SubjectFull: Telecommunication Type: general – SubjectFull: Research Type: general Titles: – TitleFull: OMG OVERVIEW: CORBA and the OMA in Enterprise Computing. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: Siegel, Jon IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 10 Text: Oct98 Type: published Y: 1998 Identifiers: – Type: issn-print Value: 00010782 Numbering: – Type: volume Value: 41 – Type: issue Value: 10 Titles: – TitleFull: Communications of the ACM Type: main |
| ResultId | 1 |
