Marshaling and unmarshaling models using the entity-relationship model

Authors:
Fei Cao;Barrett R. Bryant;Wei Zhao;Carol C. Burt;Rajeev R. Raje;Andrew M. Olson;Mikhail Auguston
Affiliations:
University of Alabama at Birmingham, Birmingham, AL;University of Alabama at Birmingham, Birmingham, AL;University of Alabama at Birmingham, Birmingham, AL;University of Alabama at Birmingham, Birmingham, AL;Indiana University-Purdue University-Indianapolis, Indianapolis, IN;Indiana University-Purdue University-Indianapolis, Indianapolis, IN;Naval Postgraduate School, Monterey, CA
Venue:
Proceedings of the 2005 ACM symposium on Applied computing
Year:
2005

Citing 6
Cited 1

The Unified Modeling Language user guide

The Unified Modeling Language user guide
The entity-relationship model—toward a unified view of data

ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Building Web Services with Java: Making Sense of Xml, Soap, Wsdl, and Uddi

Building Web Services with Java: Making Sense of Xml, Soap, Wsdl, and Uddi
Model Driven Architecture: Applying MDA to Enterprise Computing

Model Driven Architecture: Applying MDA to Enterprise Computing
Composing Domain-Specific Design Environments

Computer
E-R modeler: a database modeling toolkit for Eclipse

ACM-SE 42 Proceedings of the 42nd annual Southeast regional conference

Supporting transparent model update in distributed CASE tool integration

Proceedings of the 2006 ACM symposium on Applied computing

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software systems are usually designed and documented with the aid of visual modeling notations. Visual modeling notations keep evolving over the years in tandem with visual modeling tools, and the tight binding in between impedes the exchanging of modeling assets, which causes a spatial isolation of the models. Another problem with legacy software models is that they are isolated temporally in the early phases of the software engineering life cycle without reaching out to the later phases. This paper presents an approach for breaking both spatial and temporal isolation of software models by marshaling and unmarshaling models using the Entity-Relationship (ER) model, thus providing a promising way for evolving model-driven software development.