The National Transport University Bulletin

Abstract

Every system can be described from various perspectives using different models, each being a semantically closed abstraction. A model may emphasize the structure of the system (structural model) or focus on its dynamics (behavioral model). Consequently, modeling forms the foundation for developing high-quality software. An analytical model must not include implementation details. The choice of architecture depends on multiple factors: the project scale, number of users, scalability and extensibility needs, and even the technological capabilities of the team. Each architectural type has its pros and cons; therefore, the best architecture is the one that meets the specific needs of your system. There are no generally accepted specific metrics to determine when it is time to end a process. So far, nothing better than “should be enough” has been invented. Depending on the field of knowledge as a whole, the number of entities and the level of detail will vary. Event processing architecture focuses on responding to events, rather than on the constant exchange of data between parts of the system. This paper proposes a software modeling process using visual schemes. The development process starts with the concept, often built using pre-defined architectural templates. As a result, the most adaptable architectural software patterns are presented. The results of the article can be used during software development and implementation. Also, the results of the work can be introduced into the educational process during the teaching of educational disciplines of the cycle of professional training of software engineering

Keywords: