Towards a Metrics Suite for Object-Relational Mappings

Holder, Stefan; Buchan, James; MacDonell, Stephen G.

doi:10.1007/978-3-540-78999-4_6

Cited by 10 publications

(16 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…al. in [13]. Based on the ISO/IEC standard for software quality, they define a mapping between high-level non-functional (quality) software system characteristics (efficiency, usability, maintainability) and O/R mapping layer aspects (object creation, object retrieval, query complexity, etc.).…”

Section: Missing Awarenessmentioning

confidence: 99%

“…Consequently, an engineer needs to understand the impact of a design decision in order to conform to the desired overall system characteristics. Holder et al [13] propose an organization of non-functional characteristics which are influenced by O/R mapping strategies. Their organization is derived from the ISO/IEC standard for software quality, ISO/IEC 9126 [1].…”

Section: Non-functional Characteristicsmentioning

confidence: 99%

“…Figure 5 depicts their organization. We see the definition of quality characteris- Figure 5: O/R Quality Characteristics defined by Holder et al [13] tics as an important step towards measurable aspects of a mapping strategy. However, we propose further refinement of these characteristics to provide measurable metrics.…”

Section: Non-functional Characteristicsmentioning

confidence: 99%

“…Instead, there exist different strategies, which can be used to implement the semantic of an inheritance relationship. These strategies have been defined and documented in a number of publications ( [4,12,15,13]) and are widely accepted. In their essence, they differ in the number, structure, and relationship of tables that are used to store objects of the domain model.…”

Section: Introductionmentioning

confidence: 99%

“…In their essence, they differ in the number, structure, and relationship of tables that are used to store objects of the domain model. Depending on the chosen strategy, an application has varying non-functional system characteristics [13], e.g., efficiency, usability, and maintainability. Today, there is no cost model, method, or tool chain, which helps software engineers to make an informed decision for or against a particular mapping strategy.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Object-Relational Mapping Revisited - A Quantitative Study on the Impact of Database Technology on O/R Mapping Strategies

Lorenz¹,

Rudolph²,

Hesse³

et al. 2017

Proceedings of the 50th Hawaii International Conference on System Sciences (2017)

View full text Add to dashboard Cite

Object-oriented applications often achieve persistence by using relational database systems. In such setup, objectrelational mapping is used to link objects to tables. Due to fundamental differences between object-orientation and relational algebra, the definition of a mapping is a considerably difficult task. Today, there are only informal guidelines that support engineers in choosing the best mapping strategy. However, guidelines do not provide a quantification of actual impact and trade-off between different strategies. Thus, the decision on which mapping strategy should be implemented relies on a large portion of gut feeling.In this paper, we propose a framework and conduct a quantitative study of the impact of object-relational mapping strategies on selected non-functional system characteristics. Our study creates awareness for consequences of using different mapping designs and persistence technologies. This allows developers to make distinctive and informed decisions, based on quantified results rather than gut feeling.

show abstract

Section: Missing Awarenessmentioning

confidence: 99%

Section: Non-functional Characteristicsmentioning

confidence: 99%

Section: Non-functional Characteristicsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations