Generating Database Access Code From Domain Models

Khelifi, Nassima Yamouni; Śmiałek, Michał; Mekki, Rachida

doi:10.15439/2015f247

Cited by 5 publications

(2 citation statements)

References 13 publications

(16 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In fact, the actual program realization has been at its heart from the beginning [31] and the foundations laid in OOram appear as very relevant for achieving a necessary flexibility in code as demonstrated by the DCI approach (Data, Context and Interaction), in which roles and role binding are used to depart use cases from more stable parts of software systems [10,30,11]. This is of the utmost interest in the broader area of preserving use cases in code [6,18,24].…”

Section: Oorammentioning

confidence: 99%

Aspects and roles in software modeling: A composition based comparison

Vranić

Laslop

2016

COMSIS J

View full text Add to dashboard Cite

It's intriguing how the work on inherent aspect-oriented modeling almost completely ignores the similarity between aspect-oriented and role based decomposition and composition. Ever since the notion of aspect entered the software development arena, it has been compared to the notion of role. Findings range from identifying greater similarities to more cautious observations that albeit aspects and roles are similar, they appear to be more as complimentary with a significant effort needed to really bring them together in programming. Even a cursory comparison of Theme/UML, which represents a design part of Theme, probably the best known and most comprehensive approach to aspect-oriented modeling, to OOram, a prominent representative of approaches to role based modeling that influenced UML, reveals striking similarities in both decomposition and composition. Within a more comprehensive effort of finding the principles of a sustainable approach to aspect-oriented modeling, this paper pursues further this observation by establishing a partially reversible transformation of a Theme/UML model to the corresponding OOram model that proves principal analogy of themes to OOram collaboration view diagrams accompanied by the corresponding scenario view and interface view diagrams. An important implication is that aspects have their counterpart not in roles themselves, but in role collaboration. Based on these results, a possibility of using UML composite structure diagrams for aspect-oriented design is sketched out in the paper.

show abstract

Section: Oorammentioning

confidence: 99%

Aspects and roles in software modeling: A composition based comparison

Vranić

Laslop

2016

COMSIS J

View full text Add to dashboard Cite

show abstract

“…Several techniques have been used for this purpose such that automatic source to source error compensation of floating-point programs [17], generating database access code from domain models [18], and generating pseudo-code from source code [19], etc.…”

Section: Introductionmentioning

confidence: 99%

Feature-Based Comparison of Language Transformation Tools

Ilyas

2020

Research Journal Of Computer Science And Information Technology

View full text Add to dashboard Cite

Code transformation is the best option while switching from farmer to next technology. Our paper presents a comparative analysis of code transformation tools based on 18 different factors. These factors are Classes, pointers, Access Specifiers, Functions and Exceptions, etc. For this purpose, we have selected varyCode, Telerik, Multi-online converter, and InstantVB. Source Language considered for this purpose is C sharp (C#) and the target language is Visual Basics (VB). Results show that VaryCode is best among the four tools as its converted programs throw fewer errors and require minor changes while running the program.

show abstract