The agile project management approach has been considered to be one of the most popular approaches for developing IT solutions. Use of this approach allows us to change the requirements at any stage of the IT project, and one of the twelve principles of Agile Manifesto, -"Simplicity", -promotes the use of a minimum amount of project documentation. One of the disadvantages limiting the implementation in such resource-intensive projects as Information Systems Projects (ISP) is the risk of exceeding budgets and time limits. Therefore it is highly important to develop such a tool that will contribute in discussion and approval process with the customer before changes are started so as to minimize the possibilities of changes at further stages of the project. This article investigates the possibility of applying holistic methods of the Enterprise Architecture (EA) in order to support solutions design during an Information System Project, in particular, in the form of documentation at the stage before implementation planning. The main aim of our research is to develop a tool that will help the customer to understand the planned changes and will contribute in that their infl uence on the already existing EA is taken into account. This article fi rst reviews standards of IT project management in the context of recommendations for "conceptual project" outcomes. Next, the results of interviews conducted with IT consultants are presented. The proposed Architectural Solution (AS) is a document that completes the stage of design and coordinating IT changes. It is based on the application of methods and models from the fi eld of EA. We believe this solution may be a suffi cient document for coordinating projects that are conducted under agile philosophy.

Реорганизационная деятельность на предприятии требует системного подхода к оценке результатов отдельных проектов и к формированию портфеля смежных проектов по внедрению изменений. Системный подход в случае анализа изменений в деятельности компании подразумевает рассмотрение любых организационных изменений в контексте архитектуры предприятия: необходимо учитывать взаимосвязь и взаимозависимость бизнес-процессов, организационной структуры, информационных систем, информационно-технологической инфраструктуры и других компонентов архитектуры предприятия. Сегодня в целях повышения конкурентоспособности и необходимости соответствовать меняющимся бизнес-условиям все больше компаний реализуют проекты внедрения или изменения тех или иных архитектурных решений: проекты реинжиниринга бизнес-процессов, реформирования организационной структуры, внедрения информационных систем и др. При этом часто проблема решается изолированно от связанных компонентов архитектуры предприятия, что ведет к неудовлетворительным результатам подобных проектов. Эффективное внедрение архитектурных решений требует проведения комплексного анализа предлагаемых изменений, поскольку реорганизация одного из слоев или отдельных элементов архитектуры предприятия влечет за собой изменение требований к элементам других слоев. Ценность компонентов архитектуры предприятия определяется набором сервисов, которые эти компоненты предоставляют друг другу в ответ на предъявляемые требования. Поэтому сервисы являются универсальным инструментом выравнивания архитектурных слоев и создания сбалансированной архитектуры предприятия. Сформулирован алгоритм проведения сервис-ориентированного анализа архитектурных решений, предложены методы определения требований к сервисам различных слоев архитектуры предприятия на основе существующих общепризнанных моделей и продемонстрировано использование сервис-ориентированного анализа в проекте аудита бизнес-процессов.

This article lists a part of a study of possibilities of using and integrating digital twins of the existing high-tech enterprise processes on the examples of a high-pressure gas compressor station and a gas treatment plant using low-temperature separation of an oil and gas enterprise using an architectural approach. The need for the use of digital twins (DT) in the high-tech industry is due to the inability to effectively conduct full-scale tests to select the necessary operating modes in the implementation framework of technological processes with varying parameters (high cost and increased resource consumption compared to the creation of a DT). The main difference between DT and conventional models is the three-dimensional matrix of input variable parameters that can be given to DT for processing in order to obtain the most correct output data when performing simulations. At the same time, millions of operational cycles can be generated in real time, which allows us to most effectively solve various business problems. For example, the task of finding optimal solutions and prototype configurations under study.

The agile project management approach has been considered to be one of the most popular approaches for developing IT solutions. Use of this approach allows us to change the requirements at any stage of the IT project, and one of the twelve principles of Agile Manifesto,-"Simplicity",-promotes the use of a minimum amount of project documentation. One of the disadvantages limiting the implementation in such resource-intensive projects as Information Systems Projects (ISP) is the risk of exceeding budgets and time limits. Therefore it is highly important to develop such a tool that will contribute in discussion and approval process with the customer before changes are started so as to minimize the possibilities of changes at further stages of the project. This article investigates the possibility of applying holistic methods of the Enterprise Architecture (EA) in order to support solutions design during an Information System Project, in particular, in the form of documentation at the stage before implementation planning. The main aim of our research is to develop a tool that will help the customer to understand the planned changes and will contribute in that their infl uence on the already existing EA is taken into account. This article fi rst reviews standards of IT project management in the context of recommendations for "conceptual project" outcomes. Next, the results of interviews conducted with IT consultants are presented. The proposed Architectural Solution (AS) is a document that completes the stage of design and coordinating IT changes. It is based on the application of methods and models from the fi eld of EA. We believe this solution may be a suffi cient document for coordinating projects that are conducted under agile philosophy.

The paper presents key approaches of development relatively simple software applications which deals with controlling digital devices via JTAG interface.