Kristaps Babris

Introduction: Automated generation of executable user interfaces from domain models remains a challenging problem in model-driven software engineering, particularly when both application behavior and domain structure must be preserved in the resulting interface. Existing model-based approaches often remain at the level of abstract interface specifications, whereas AI-assisted generation provides flexible code synthesis but offers limited deterministic traceability to formal domain models. This study proposes a model-driven framework for automatically generating executable web user interface prototypes from the two-hemisphere model, which integrates process and concept representations of a problem domain. Methods: The proposed transformation pipeline maps processes to application states and navigation structures, concepts and their attributes to data-oriented interface elements, and process semantics to reusable user interface patterns selected through a deterministic scoring mechanism. A proof-of-concept implementation generates React.js/Material-UI prototypes incorporating routing, state management, CRUD structures, and automatically generated demonstration data. The framework was evaluated using an e-commerce case study through three complementary methods: static source-code analysis, ISO/IEC/IEEE 29119-based functional acceptance testing, and a pilot expert heuristic evaluation based on Nielsen's usability heuristics. Results: The generated prototype passed all 25 functional acceptance-test scenarios, required no post-generation source-code modification, and was generated in approximately 12 seconds. Static analysis identified no JSLint or ESLint issues and only two minor JSHint warnings. Three independent usability evaluators produced 22 individual observations, which were consolidated into nine unique usability problems: three cosmetic, five minor, one major, and no critical violations. The major issue concerned the absence of a clearly visible order summary in the generated shopping-cart interface. Discussion: The results provide preliminary evidence that the two-hemisphere model can serve as a viable source representation for generating executable user interface prototypes while preserving traceability between behavioral and structural domain information and the resulting implementation. The heuristic findings also identify concrete opportunities for improving transformation rules and the user interface pattern library. However, broader generalisability, comparative efficiency, accessibility, and end-user usability remain to be established through multi-case and user-centred evaluation.

The paper emphasizes the critical importance of the initial phase in IT project development to avoid implementation errors. It argues that minimizing these errors can be achieved by developing project artifacts at the early stage using a model-driven engineering-based approach. Model transformation plays a basic role in that context. The goal of this paper is to survey publications in which the authors propose generating initial project elements through model-driven engineering and to analyze the level of model transformations offered in their solutions. As a result, the authors would highlight the necessity of understanding which elements of a project can be obtained through automatic transformations and which still require manual manipulation. This distinction is crucial, as it can significantly influence the efficiency and accuracy of the project’s early phases. In general, identifying the project components that can be reliably generated through model transformations helps streamline the project inception and elaboration process performed before IT product implementation.

The PhD Thesis proposes a solution for generating a source code of a Web application user interface prototype from a two-hemisphere model using model-driven software engineering principles. The development of a set of model transformation rules is based on the metamodel of the two-hemisphere model as a source model and the metamodel of the expected elements defined for the user interface, which include all user interface layers: concept, navigation, and presentation.

Promocijas darbā piedāvāts risinājums tīmekļa lietotnes lietotāja saskarnes prototipa pirmkoda ģenerēšanai no divpusložu modeļa, izmantojot modeļvadāmas programmatūras inženierijas principus. Modeļu transformācijas likumu kopas izstrāde balstās divpusložu modeļa kā avota modeļa metamodelī un lietotāja saskarnei definētajā sagaidāmo elementu kopas metamodelī, kas ietver visus lietotāja saskarnes slāņus – konceptu, navigāciju un prezentāciju.

UML diagrams are a base for the planning of development in most software projects. It is used for representing different artefacts during software development and project structure. The use case is one of the diagrams in Unified Modelling Language (UML), which allows describing the dynamic flow of the system. There are a lot of tools that are used for creating this diagram before starting the actual coding process, and the diagram needs to be specific and easily understandable. Meantime, the creation of a UML use case diagram from scratch for complex systems can be time-consuming and confusing for people, which needs to be optimised. The authors of the paper attempt to solve the addressed problem. Therefore, in this research paper a new definition for UML use case diagrams will be introduced, where the main question will be whether it is possible to formalise use case modelling by introducing pre-defined use case patterns. This is academic research and discussion, which is based on the analysis of advanced UML tools, which use case diagram templates contain. The solution to this research question contains an initial set of UML use case patterns, created by analysing of the existing use case diagram templates. Moreover, in order to validate work, the pre-defined patterns were demonstrated on a developed prototype. The operation principle of the prototype focused on giving the ability to the user to construct a use case diagram by the combination of pre-defined patterns. The prototype can be useful for the development/management process in case of correct implementation. It will allow decreasing spent time on the use case diagram creation as well as avoid creating anti-patterns.

Day-to-day working activities have been heavily altered by COVID-19 pandemic, forcing a transition from traditional on-site work to on-line telework across the whole world. It has become much harder to efficiently organise, guide and evaluate employee’s work. There are different factors that can influence “work from home” quality, and many of these affect such work negatively. A set of relevant methods and tools should be developed which could improve this situation. The goal of the study is to summarise related background of this problem and to propose an approach to overcoming this problem. To achieve the goal, design engineer’s work is evaluated in an appropriate environment (e.g., AutoCAD, etc.) using automated analysis and visualization of IS auditing data.

Every software development company makes software development based on a specific approach. There are a number of approaches to software development, both disciplined and agile. Each approach includes a set of different activities. Sometimes, the specific nature of a company’s work requires a specific approach, but the need to make work more efficient, faster and better requires implementing activities of other approaches. Then hybrid software development approaches come in. The paper presents an expert survey to examine the most important software development activities, the combinations of development approaches that are used in software development processes and the way of upgrading existing approaches. The evaluated activities of software development process are classified according to their nature – whether they correspond with a team, organisation, documentation, development, and testing. The conclusions are also made on the practices that are required most – disciplined, Agile or hybrid.