From (Imperfect) Object Diagrams to (Imperfect) Class Diagrams

Kästner, Andreas; Gogolla, Martin; Selić, Bran

doi:10.1145/3239372.3239381

Cited by 8 publications

(4 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…At the technical level, we plan to integrate TOTEM with model transformation repositories [Di Rocco et al 2016] or general-purpose repositories like GitHub, to allow powerful means to query, discover and chain reusable transformations. Finally, we plan to exploit the notion of DRM as a device to capture meta-model requirements in other applications, like bottom-up and example-based modelling [Kästner et al 2018;López-Fernández et al 2015].…”

Section: Discussionmentioning

confidence: 99%

Automated Reuse of Model Transformations through Typing Requirements Models

Lara

Guerra

Ruscio

et al. 2019

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Model transformations are key elements of model-driven engineering, where they are used to automate the manipulation of models. However, they are typed with respect to concrete source and target meta-models, making their reuse for other (even similar) meta-models challenging. To improve this situation, we propose capturing the typing requirements for reusing a transformation with other meta-models by the notion of a typing requirements model (TRM). A TRM describes the prerequisites that a model transformation imposes on the source and target meta-models to obtain a correct typing. The key observation is that any meta-model pair that satisfies the TRM is a valid reuse context for the transformation at hand. A TRM is made of two domain requirement models (DRMs) describing the requirements for the source and target meta-models, and a compatibility model expressing dependencies between them. We define a notion of refinement between DRMs and see meta-models as a special case of DRM. We provide a catalogue of valid refinements and describe how to automatically extract a TRM from an ATL transformation. The approach is supported by our tool TOTEM. We report on two experiments—based on transformations developed by third parties and meta-model mutation techniques—validating the correctness and completeness of our TRM extraction procedure and confirming the power of TRMs to encode variability and support flexible reuse.

show abstract

Section: Discussionmentioning

confidence: 99%

Automated Reuse of Model Transformations through Typing Requirements Models

Lara

Guerra

Ruscio

et al. 2019

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…The scientific literature delivers numerous reports scoping tools and methods that help the designer to improve particular aspects of the designed model. For example, A. Kästner et al [37] propose a transition to class models starting from object models. V. Besnard et al [47] provide formal verification of some model properties expressed with Linear Temporal Logic.…”

Section: Ar Tool Functionalitymentioning

confidence: 99%

“…As example, it may be mentioned: refactoring of class diagram by O.A. Derjugina [35], validating and optimizing object and class diagrams by K. K. Sergievskiy et al [36], exploration of object and class diagrams by Kästner et al [37], synthesis of State Machine Models N. Kahani [38], insight about class diagram using in the survey of J. Hutchinson [22].…”

mentioning

confidence: 99%

Initial training in design of computer programs using UML

Andreyanov,

Gagarin

2023

P Sci Edu

View full text Add to dashboard Cite

Introduction. Design is commonly acknowledged as a key process in the life cycle of computer programs and softwareintensive systems. The process efficaciously reveals creative capabilities of the author programmer and predetermines the basic advantages as well as shortcomings of the resulting program product, service or system. Design automation and other kinds of its support have been emerged simultaneously with onset of the software industry. From the beginning of the century the MDA (Model Driven Architecture) approach grew famous, offering to comprehend a design of a program as a process of sequential transformation of the program’s models, represented in UML or in other languages related to UML. Without becoming dominant, the MDA approach successfully evolves inside of a broader approach called MDE (Model Driven Engineering). Mastering UML and understanding of its role in MDE appears to be a prerequisite for a seamless entering of a professional programmer into domain of engineering of program systems. This provision justifies an increased attention to methods of UML teaching and to peculiarities of UML learning, and, moreover, to the professional education in the area of programs and program systems design technologies. This paper is aimed to draw attentions to challenges of the initial training in UML and tackle the challenges contributing a methodology and tools for sake of fostering the quality of education in program design. Materials and methods. The research is based on the university syllabi, the author’s lecture notes on software engineering, reports on laboratory works and course papers, protocols of experimental and sample runs of the developed programs, scientific publications, including pedagogical and engineering periodicals, conference materials, Internet resources, such as sites of the ACM, the OMG and others. The following research methods were used: system analysis of the own experience in program design as well as experience remarkable in student’s works; theoretical conceptual modelling of the program design including modelling of design scenarios; a trial implementation of the developed algorithms. Research results. A conceptual cognitive model of design as of a process during program development is proposed, highlighting the designer’s behavior when dealing with project artefacts. Feasible scenarios of analytic and advisory intervention into the design process are specified, using the model. A sample architecture of a program tool suitable for such an intervention is proposed as well as algorithms that enable online critical evaluation of the project’s current state, prompting feasible tracks of the project’s evolvement, revealing designer’s ideas and pointing some UML misuse. The algorithms are built in a program tool named Procrust that implements the proposed architecture. Trials of Procrust show that it basically fits to primary training of software design using UML and, in particular, to a training in the MDA/MDE methodology. Conclusion. The research results enable to set up an environment for comfortable and efficient program design using UML due to employing the proposed analytic and advisory support of the design process. Algorithms of the support and supporting program tools are targeted at initial design training on curricula of higher school and secondary vocational education. The algorithms foster in-depth study of UML and acquiring of advanced software design skills.

show abstract

“…The IMD with the help of IMD dictionary generates a machine interpretable representation of Java code using source code parser. [31]. As described in TABLE 4, declaration blocks, data-members and methods are translated into corresponding UML classes, attributes and operations.…”

Section: A Transformation Rules For Translating Source-code To Intermentioning

confidence: 99%

A Model Driven Reverse Engineering Framework for Generating High Level UML Models From Java Source Code

et al. 2019

View full text Add to dashboard Cite

Legacy systems are large applications which are significant in performing daily organizational operations and cannot be upgraded easily especially in the absence of architectural and design documentation. Software modernization is an emerging field of software engineering, which transforms the legacy systems into new one according to the specified requirements of stakeholders. It mainly deals with improving the architecture, features, rules and data sources of existing system. It always remained a challenging task to achieve high-level representation of legacy systems. In order to achieve this high-level representation, Reverse Engineering (RE) plays an integral role. The issues of traditional RE are overcome with the help of Model Driven Reverse Engineering (MDRE) such as it generates model-based view of the legacy systems, which is comprehensible and easy to understand for practitioners. MDRE is an active research area but it provides limited tool support to extract and model both structural and behavioral aspects of legacy systems. In this paper, a novel MDRE framework named as ''Source to Model Framework (Src2MoF)''is proposed to generate Unified Modeling Language (UML) structural (class) and behavioral (activity) diagrams from the Java source code. Src2MoF is based on the principles of Model Driven Engineering (MDE), which use models as first-class citizens alleviating the complexity of software systems. The contributions of this paper are as follows; first, an Intermediate Model Discoverer (IMD) is developed using source code parser to get the intermediate representation of the system from the existing Java code. Second, an open source transformation engine named ''UML model generator'' is implemented using Java, which takes these intermediate models as input, and produce high-level UML models of the subject legacy system. Finally, the two benchmark case studies are presented to depict the relevance and usability of Src2MoF. INDEX TERMS Model driven reverse engineering, reverse engineering, UML models, legacy systems, java code.

show abstract

From (Imperfect) Object Diagrams to (Imperfect) Class Diagrams

Cited by 8 publications

References 11 publications

Automated Reuse of Model Transformations through Typing Requirements Models

Automated Reuse of Model Transformations through Typing Requirements Models

Initial training in design of computer programs using UML

A Model Driven Reverse Engineering Framework for Generating High Level UML Models From Java Source Code

Contact Info

Product

Resources

About