The consideration of semantic gap between design and code

Herald of Kazakh-British technical university, 2023

Full text Open access: Gold Metadata (CSL-JSON)
DOI 10.55452/1998-6688-2023-20-4-48-54
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

In project management on creation of program application, specialists from different subject areas are involved, who include their contributions, for instance, UI/UX designers who create mock-ups of the future application or developers who write the code according to the prototype. The design conception may go beyond the possibilities of interpreting it from a technical point of view of implementation. The realization of such idea could not to be able to collect on only one defined program platform or language, and accordingly the problem is appeared. To eliminate semantic gap between the designers’ concepts and opportunity of program developers in technical affordance, released methodology, Model Driven Architecture (MDA), which is, on the one hand, a concept for implementation of software, on the other hand a standard. In paper, considerate the MDA and its transformation levels with determine a pragmatical semantics of mapping, reasons of chosen a class diagram as model of transformation and Java language for code generation.