A situated evaluation of the Object Management Group's (OMG) Object Management Architecture (OMA)

Authors:
Evan Wallace;Kurt C. Wallnau
Affiliations:
National Institute of Standards and Technology, Manufacturing Engineering Laboratory, Gaithersburg, MD;Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA
Venue:
Proceedings of the 11th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Year:
1996

Citing 8
Cited 2

Tool integration in software engineering environments

Proceedings of the international workshop on environments on Software engineering environments
PCTE: the standard for open repositories

PCTE: the standard for open repositories
SAAM: a method for analyzing the properties of software architectures

ICSE '94 Proceedings of the 16th international conference on Software engineering
Definitions of Tool Integration for Environments

IEEE Software
Architectural Mismatch: Why Reuse Is So Hard

IEEE Software
Architectural Mismatch: Why Reuse Is So Hard

IEEE Software
A Framework for Evaluating Software Technology

IEEE Software
ORBs In the Midst: Studying a New Species of CASE Integration Mechanism

CASE '95 Proceedings of the Seventh International Workshop on Computer-Aided Software Engineering

Encapsulation of legacy software: A technique for reusing legacy software components

Annals of Software Engineering
A Framework for Evaluating Software Technology

IEEE Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

It has been difficult to objectively assess the real value or maturity of the Object Management Group's Object Management Architecture (OMA). While experience reports have appeared in the literature, these have focused more on the functionality of the end-system than on systematically exploring the strengths and weaknesses of the OMA, and providing practical guidelines on the effective use of the OMA for specific software-engineering problems. In this paper we describe a case study in the use of the OMA to integrate legacy software components into a distributed object system. We assess the OMA in this problem context, and indicate strengths and weaknesses of the specification and current implementations. We extrapolate our experience to a broader class of component-based software systems, and recommend an architectural strategy for the effective use of the OMA to this class of systems.