Full text
© The Author(s) of individual chapters, 2025 DOI: 10.21303/978-9908-9706-8-4.ch1 Abstract The object of the study is the processes of functioning and maintenance, which together determine the stage of operation of a web-based information system for managing an enterprise or organization. During the study, the problem of developing elements of the methodology for lifecycle management of a web-based information system was solved. Modern research in this area is mainly aimed at analyzing and developing individual aspects of managing the operation of complex systems. The main attention is paid to solving individual tasks of managing the operation of systems based on IoT or DevOps. General issues of creating and improving the System Lifecycle Management approach remain little studied. During the study, the main provisions of the effective management concept of the life cycle of a web-based information system were proposed. This concept is based on a multi-level representation of the information system and the possibility of effective management of the system according to its properties. For further formal description of the proposed concept, the main concepts were defined and the ontology of this concept was developed. Based on this ontology, a generalized model of effective management of the operation of a web-based information system and aset of theoretical and categorical models that detail the description of the elements of this model were developed. The resulting generalized model was taken as a basis for developing a formal problem statement of effective life cycle management of an operated information system as an IT service system. A formal description of the objective function and constraints of the problem of classical (permanent) life cycle management of an Viktor Levykin Maksym Yevlanov Oleksandr Petrychenko Olga Neumyvakina CHAPTER 1 Basics of the effective management methodology of web-based information systems
5 Basics of the effective management methodology of web-based information systems Chapter 1 operated information system was proposed. On its basis, a formal description of the objective function and constraints of the problem of effective life cycle management of an operated web-based information system was proposed. It was determined that the problem of classical (permanent) life cycle management of an operated information system is a special case of the proposed problem of effective management. The practical application of the obtained research results allows improving systems for life cycle management of an operated information system without global reengineering of existing systems and technologies for data storage and processing. Keywords Web-based information system, system property, operation management, ontology of effective management, theoretical-categorical model, attributive model. 1.1 Introduction The first quarter of the 21st century is characterized by the rapid development of web-based information systems (IS) for managing enterprises and organizations. The term "web-based IS" will be used here and further to refer to IS that uses web technologies to provide information and services to users or other information systems/applications[1]. One of the most important consequences of this definition is the perception of web-based IS as systems, which functions can be accessed from anywhere in the world (provided there is a working Internet connection) via a browser. The modern view of the architecture of web-based IS recognizes the existence of several different approaches to describing this architecture. However, to reflect the above-mentioned perception of web-based IS, it is best to use the description of the architecture of such a system proposed in[2] (Fig.1.1). In Fig.1.1, the following designations are adopted for the elements of the description of the architecture of web-based IS: DNS– Domaine Name System, a domain name system that ensures the operation of the Internet; CDN– Content Delivery System, a content delivery system that provides acceleration of the delivery of static HNML, CSS, JavaScript files and images (dotted lines separate the elements of the web-based system that are located on the system's web servers and can be located practically anywhere on the globe). Detailed descriptions of these elements are given in[2]. Creation, support and development of web-based IS with the architecture described in Fig.1.1 significantly complicates the solution of the problem of managing such IS within their life cycle (LC). Such management is necessary for any IT company that promotes web-based IS of its own production on the market of IT products
6 Management of a modern IT company: theoretical and technological aspects intended for the management of enterprises and organizations. The goal of such management in general should be to increase the competitiveness of web-based IS by maintaining the characteristics of efficiency and quality of this system at the level most desirable for all stakeholders. DNS Load Balancer CDN User's browser Cloud storage Copy of data Database Web app servers Data warehouse Data "firehose" Caching service Job Queue Services Job servers Full text search service 1 11 210 9b 9a 9c 3 4 56a 6b 8 7 Fig. 1.1 Description of the architecture of a web-based system Source:[2] The modern approach to the creation and functioning of IS management of enterprises and organizations conceptually considers such systems as a type of system for providing IT services to operators and users[3]. Here and further, the term "service" will be understood as the performance of actions, work or duties, which is self-sufficient, consistent, discrete and can be composed of other services[4]. Based on this definition, the term "IT service" was proposed to be used to refer to an independent functional task in IS, the use of which is economically and technically feasible for performing a separate activity of the process of an enterprise or organization or for managing this activity[5]. The results of implementing this approach in the IT industry are[6]: –the concept of an IT service management system as a system for managing and controlling the activities of managing IT objects of an IT company;
7 Basics of the effective management methodology of web-based information systems Chapter 1 –an approach "Product Lifecycle Management" (PLM); –an approach "Application Lifecycle Management" (ALM). The term "PLM" will be understood as an approach to managing processes and methods that are used or created during the LC of products or systems. Its scope mainly covers the hardware parts of the system[7]. The term "ALM" will be understood as an approach focused on the software LC. It is designed to monitor, control and manage artifacts and processes that arise during the program LC. These processes include requirements development, source code management, test management, release management, etc.[8]. To solve the problem of managing services during their LC, a separate type of management system was created– service management systems. According to the modern understanding, such systems should be perceived as systems for managing and controlling the activities of the service provider from the point of view of service management[3]. However, although the PLM and ALM approaches arose on the basis of the same concept of an IT service management system, the ISs created within these approaches developed in different ways. In order to eliminate the difference between these ISs, a new approach was developed, the main difference of which is the integration of PLM and ALM into the interdisciplinary management of the system's LC (SLM)[9]. Unfortunately, the creation and development of the SLM approach occurs mainly at the conceptual level. The reasons for this should be considered different approaches to the structuring of hardware and software, as well as to the integration of elements of this software into systems. In addition, the phases of the software and hardware LCs also differ, even if there are similarities[10]. Therefore, conducting theoretical and theoretical-applied research devoted to the development of methodological foundations of the SLM approach at the conceptual and formal levels is relevant. 1.2 Analysis of modern research in the field of effective management ofweb-based information systems Modern information technologies (IT) and IS based on PLM are aimed at managing large amounts of information and artifacts that arise and accumulate during the product LC[7]. Such PLM-IT and PLM-IS are considered as a center that ensures the existence of compatible data flows (for example, data from CAD products, modeling or architecture data, etc.) and solving the problems of managing these data flows. This is due to the fact that PLM grew out of CAD (Computer Aided Design) and PDM(Product Data Management). For this reason, PLM-IT and PLM-IS are only limitedly suitable for displaying and supporting the software LC[9].
8 Management of a modern IT company: theoretical and technological aspects The use of PLM-IT and PLM-IS for managing the IS LC in enterprises and organizations is complicated by the need to manage changes that arise during the creation and operation of such IS. Thus, in[11] the reasons for these complications are the lack of compatibility of product change notifications, low data quality, and the lack of direct traceability and tracking of changes to the final product. To eliminate these complications,[11] proposes to integrate PLM-IS and IT asset administration(Asset Administration Shell). Such integration should improve cooperation between PLM-IS and IS of enterprise and organization management, improve data quality, ensure traceability and increase efficiency within engineering processes. However, this approach is not very suitable for LC management, because it focuses mainly on hardware management. Unlike PLM, ALM was originally considered as an approach that can theoretically be used without the use of appropriate tools. ALM was mainly proposed to be used to integrate all processes, methods and data used and generated within software development[8]. The modern vision distinguishes three main aspects within ALM: governance, development and operations[9]. The governance aspect considers the tasks of conducting software business analysis, project portfolio management and program portfolio management. The development aspect considers the tasks of software generation (from requirements definition through design and source code development to testing and release). The operation aspect considers the tasks of software monitoring and management[12]. Modern research suggests understanding SLM as a technical and organizational basis for LC management of all system artifacts that are created or improved during the existence of this system, and the tools used to work with these artifacts. This basis provides clear tracking of all system elements. Thus, interdisciplinary SLM is considered the basis for complex digital engineering[13]. But IT products that are the results of this complex digital engineering differ significantly from each other. Examples of such IT products include: –Microsoft products (Microsoft System Center 2016, Microsoft Azure Automation & Control in Microsoft Operations Management Suite); –specialized products of individual IT companies (Cortex, ActiveBatch Workload Automation, Ignio, VMware Vrealize Orchestrator, etc.); –products that are descendants of CASE systems and visual modeling environments (CA Process Automation). As can be seen, the main difference between IT products designed to implement the SLM approach is caused mainly by the features and requirements of specific IT companies, on which orders these products were created. It should be noted that there is no fixed classification of IT products that can be used to implement the SLMapproach.
9 Basics of the effective management methodology of web-based information systems Chapter 1 But it should be recognized that these and similar IT products generally meet the requirements for service management systems defined in[3]. In general, the set of functions of such products is aimed at achieving the following goals: – increasing the efficiency of the functioning of IT processes of the enterprise-consumer of IT services (technical and economic goal); –reducing the operational risks of the enterprise-consumer of IT services (technical and economic goal); –reducing the costs of IT processes of the enterprise-consumer of IT services throughout the entire LC (economic goal); –compensation for the negative consequences of the complexity of managing the IT services system of the consumer enterprise, in particular, eliminating the effect of "IT blindness" (economic goal); –increasing the level of compliance with standards, including to facilitate further certification (economic and organizational and methodological goal). Unlike applied developments, most theoretical research in the field of PLM, ALM and SML is aimed at developing individual aspects of IT service management of large industrial systems based on the Internet of Things. For example, in[14] a description of the information layer of the reference architectural model RAMI 4.0 is proposed, which is supported by the Zachman Framework concept. The proposed description, according to the authors, should ensure the practical use of RAMI4.0, allowing stakeholders to use model-based systems engineering, on the one hand, and include information engineering, on the other. However, the description proposed in[14] can be used to develop only individual aspects of industrial systems and does not cover the task of industrial IS management as a whole. Similar research is being conducted in the IT industry. Thus, in[15] the results of mixed modeling and modeling of continuous service delivery pipeline scenarios as a separate aspect of DevOps are described. But these studies also do not cover the overall task of managing IS and IT, which an IT company uses in its activities. The formation of integral assessments of the progress and results of the functioning of individual IS services currently does not involve the use of formal models[16]. At the same time, studies have shown that the success of projects aimed at improving individual processes is not a coincidence, but a predictable result with clearly defined and measurable characteristics[17]. To solve various IT service management problems, approaches based on solving multi-criteria optimization problems are proposed in[18]. However, the difficulties of applying such approaches in managing real webbased IS force to look for other options for solving such problems. Thus, in[19] it is proposed to consider an approach to web service management based on knowledge. However, this approach is not yet fully developed and requires additional research.
10 Management of a modern IT company: theoretical and technological aspects A significant number of studies consider the problem of managing the IS LC mainly through the prism of tools for its solution. In this case, the multi-criteria decision-making process is usually proposed as the main tool. To implement this process, decision support systems based on multidimensional data warehouses are proposed. An example of such a platform designed to automate the management of the stages of the LC describing the development of modern software is considered in[20]. Asignificant part of the publications is devoted to describing the results of research into problems that arise when using tools for solving such multi-criteria optimization problems. Algorithms[21] and tools[22] for analyzing and optimizing hyperparameters are considered as similar tools in modern research. Studies devoted to the use of simulation modeling tools for LC management of individual aspects of IS[23] are not left without attention. The following directions for further research on the development of SLM are indicated in[9]: –improving the implementation of the knowledge management process in the business (in particular, ensuring the interconnection of business goals and indicators with current processes to identify awareness of complaints and the potential for business improvement[24]); –developing an integrated or common ALM-PLM data model (in particular, to identify and minimize differences between the descriptions of the hardware and software development processes[25]); –extending the requirements and use cases of the ALM-PLM system to other stages of the Life Cycle; –urther detailing and refining the SLM, PLM and ALM approaches, developing these approaches through new methods, ideas and processes to support the development of software and hardware; –defining KPIs for ALM-PLM integration (in particular, to further evaluate and control the use of these approaches to assess their success or potential for improvement[26]). But the SLM development is impossible without eliminating an important contradiction in the field of IT service management. The essence of this contradiction is as follows. A typical IT service management system, defined in[1], recognizes the goal of management as maintaining user satisfaction with existing IT services at the level desired by the Provider and Consumer of IT services. At the same time, the main quantitative criterion by which it is possible to determine the degree of achievement of this goal is the indicator of the number of incident reports that remain unresolved. But these incident reports arise as a result of the interaction of operators and users with existing IT services and the IT infrastructure that ensures the operation of these
11 Basics of the effective management methodology of web-based information systems Chapter 1 IT services. Thus, the IT service management system defined in[3] and the IT products that are created on the basis of the requirements for this system are aimed at maintaining stable and time-invariant states of the software and hardware of the ITservice system. Therefore, compliance with the requirements for a typical service management system defined in[3] does not allow optimizing the set of IT services taking into account the technical and economic features of changing business processes of individual consumers of IT services. Therefore, the study of the general formal formulation of the problem of managing the IS LC is relevant both from a theoretical and practical point of view. The aim of the study is to develop the foundations of a methodology for effective management of the LC of an operated web-based IS as an IT service system taking into account the technical and economic features of business processes subject to automation. This will allow automating the solution of the tasks of managing the IS LC for enterprises and organizations, taking into account the features of SLM and ALM-PLM integration. To achieve this aim, it is proposed to solve the following objectives: –develop a concept for effective operation management of web-based IS; –develop a set of models for effective operation of web-based IS; –develop a formal statement of the problem of effective operation management of web-based IS; –develop a model of the properties of the operated web-based IS. 1.3 Research concepts and assumptions By analogy with the modern vision of ALM, the SLM approach in this study is proposed to be considered as a set of three main aspects: system governance, system development, and system operations. However, unlike the tasks considered in[9] and[12], which comprise the ALM aspects, it is proposed to present each SLM aspect as a set of typical processes of the system's LC, defined in[4]. Such a representation is shown in Fig.1.2. The use of typical processes allowed, instead of defining individual management tasks characteristic of each individual aspect of the approach, to establish a set of works and activities, the implementation of which is most important for a specific aspect. Based on the proposed aspect-process representation of the SLM approach, a conclusion was made about the significant differences in the methodologies for managing web-based IS under development and web-based IS under operation. Based on this conclusion, a decision was made on the feasibility of conducting research in
12 Management of a modern IT company: theoretical and technological aspects the field of developing the main elements of the methodology for managing the operation of web-based IS. This decision was also a consequence of the following reasons: –the minimum (compared to other aspects) number of typical LC processes of the system, which in this aspect are the most important; –recognition by modern IT companies of LC processes, which describe the operation of IT products, as critical business processes, the activities of which bring the main percentage of the IT company's profit; –unlike the aspects of system management and development, the aspect of system operation remains the least studied from a theoretical and applied point of view. SLM Approach System Governance Aspect Organizational project-enabling processes Technical management processes System Development Aspect System Operations Aspect – system analysis process; – operation process; – maintenance process; – disposal process – business or mission analysis process; – stakeholder needs and requirements definition process; – system requirements definition process; – system architecture definition process; – design definition process; – system analysis process; – implementation process; – integration process; – verification process; – transition process; – validation process; – disposal process – life cycle model management process; – infrastructure management process; – portfolio management process; – human resource management process; – quality management process; – knowledge management process – project planning process; – project assessment and control process; – decision management process; – risk management process; – configuration management process; – information management process; – measurement process; – quality assurance process Fig. 1.2 Aspect-process representation of the System Lifecycle Management approach
19 Basics of the effective management methodology of web-based information systems Chapter 1 –"Provider of IS" concept; –"Customer of IS" concept; –"Requirement of IS" concept; –"RFC IS" concept; –"Configuration of IS" concept; –"Presentation Layer" concept; –"Configuration Item" concept; –"Transaction" concept. These concepts define the main points of view that should be taken into account during a detailed formalized description of the operated IS at different levels of representation as a set of individual CIs and transactions created to meet the requirements of the IS Supplier and Consumer. The description of the states of the operated IS will consist of the following concepts, shown in Fig.1.1[27]: –"Configuration of IS" concept; –"Presentation Layer" concept; –"Configuration Item" concept; –"Transaction" concept; –"State of IS" concept; –"Planned state" concept; –"Current state" concept. These concepts define the main points of view that should be taken into account during a detailed formalized description of the operated IS at different levels of representation of both planned and current states of individual CIs and transactions. The description of indicators that characterize the operated IS and its CIs will consist of the following concepts, shown in Fig.1.3[27]: –"State of IS" concept; –"Indicator" concept; –"Library of Indicators" concept. These concepts define the main points of view that should be taken into account during a detailed formalized description of the operated IS by a set of individual indicators based on a specific library of indicators. The description of the efficiency of the IS operation by its individual properties and as a whole will consist of the following concepts shown in Fig.1.3[27]: –"State of IS" concept; –"Planned state" concept; –"Current state" concept; –"Indicator" concept;
20 Management of a modern IT company: theoretical and technological aspects –"Presentation Layer" concept; –"Property" concept; –"Efficiency" concept; –"RFC IS" concept. These concepts define the main points of view that should be taken into account during a detailed formalized description of the efficiency of the operated IS at different levels of representation. Partial duplication of concepts in different descriptions is necessary to ensure the connections of these descriptions with each other. 1.4.2 Results of development of a set of theoretical and categorical models of effective operation of a web-based information system Based on the groups of concepts of the subject area identified in Subsection1.4.1, it becomes possible to develop generalized mathematical models of effective management of the operation of web-based IS. Since these descriptions are sets of individual concepts defined in a different way, they can be formally represented in the form of the following categories[27]: –description of the operated IS at different levels of representation will be represented by the LIS category; –description of the states of the operated IS will be represented by the LSt category; –description of indicators characterizing the operated IS and its CIs will be represented by the Lind category; –description of the efficiency of the IS operation by its individual properties and in general will be represented by the LEff category. The LI category, taking into account the concepts of the ontology of web-based IS service management and the connections between these concepts, has the form L Ob Ob Ob Ob Ob Ob Ob Ob Ob H IS IS Cust recRFC Conf PL CI Tr O ,, ,, ,,,,, _Pr bb Ob Ob Ob Ob Ob Ob Ob Ob Ob Ob IS Cust IS rec IS recIS Cust H HHH H Pr ,, ,, , Pr CConf rec Conf PL Conf CI Conf Tr Tr CI Ob Ob Ob Ob Ob Ob Ob Ob Ob HHHH,,,,, _HHHH Ob Ob Ob Ob RFCRFC Cust Ob Pr ,, , 1 (1.1) where ObIS– a subset of LIS category objects that describes the "Information System"concept; ObPr– a subset of LIS category objects that describes the "Provider of IS" concept; ObCust– a subset of LIS category objects that describes the "Customer of IS"concept; Obrec– a subset of LIS category objects that describes the "Requirement of IS" concept; ObRFC– a subset of LIS category objects that describes the "RFC IS" concept; ObConf– a subset of LIS category objects that describes the "Configuration of IS"
21 Basics of the effective management methodology of web-based information systems Chapter 1 concept; ObP_L– a subset of LIS category objects that describes the "Presentation Layer" concept; ObCI– a subset of LIS category objects that describes the "Configuration Item" concept; ObTr– a subset of LIS category objects that describes the "Transaction" concept; HOb Ob IS Pr – a subset of LIS category morphisms defined between subsets ObPr and ObIS; HOb Ob Cust IS – a subset of LIS category morphisms defined between subsetsObIS and ObCust; HOb Ob rec IS – a subset of LIS category morphisms defined between subsetsObIS and Obrec; HOb Ob rec Pr – a subset of LIS category morphisms defined between subsets ObPr and Obrec; HOb Ob IS Cust – subset of LIS category morphisms defined between subsets ObCust and ObIS; H Ob Ob Conf rec– subset of LIS category morphisms defined between subsets Obrec and ObConf; H Ob Ob Conf PL _ – subset of LIS category morphisms defined between subsets ObP_L and ObConf; H Ob Ob Conf CI – subset of LIS category morphisms definedbetween subsets ObCI and ObConf; H Ob Ob Conf Tr – subset of LIS category morphisms defined between subsets ObTr and ObConf; HOb Ob Tr CI – subset LIS category morphisms defined between subsets ObCI and ObTr; HOb Ob RFC Pr – a subset of morphisms of the LIS category defined between the subsets ObPr and ObRFC; HOb Ob RFC Cust – a subset of morphisms of the LIS category defined between the subsets ObCust and ObRFC; HOb 1– a subset of single morphisms defined on selected subsets of objects of the LIS category. The LSt category, taking into account the concepts of the web-based IS service management ontology identified in[27] and the relationships between these concepts, has the form L Ob Ob Ob Ob Ob Ob Ob H St Conf PL CI Tr St Pl St CStOb Ob Conf P ,,,,,,, ___ _LL Conf CI Conf Tr Tr CI St Conf Pl St H HHHH Ob Ob Ob Ob Ob Ob Ob Ob Ob O ,, ,, ,_ bb Ob Ob St CSt St Ob HH,, , _1 (1.2) where ObSt– a subset of objects of the LSt category, which describes the concept of "State of IS" concept; ObPl_St – a subset of objects of the LSt category, which describes the concept of "Planned State" concept; ObC_St– a subset of objects of the LSt category, which describes the concept of "Current State" concept; HOb Ob St Conf – a subset of morphisms of the LSt category, defined between subsets ObCont and ObSt; H Ob Ob Pl St St _–asubset of morphisms of the LSt category, defined between subsets ObSt and ObPl_St; H Ob Ob CSt St _– a subset of morphisms of the LSt category, defined between subsets ObSt and ObC_St; HOb 1– a subset of single morphisms, defined on selected subsets of objects of the LSt category. The LInd category, taking into account the concepts of the web-based IS service management ontology highlighted in[27] and the connections between these concepts, has the form LO bObOb HHH IndStInd LibOb Ob Ob Ob St Ind Lib Ind Ob ,,,,, , 1 (1.3)
22 Management of a modern IT company: theoretical and technological aspects where ObInd– a subset of objects of the LInd category, which describes the "Indicator" concept; ObLib– a subset of objects of the LInd category, which describes the "Library of Indicators" concept; HOb Ob St Ind– a subset of morphisms of the LInd category, defined between the ObInd and ObSt subsets; HOb Ob Lib Ind– a subset of morphisms of the LInd category, defined between the ObInd and ObLib subsets; HOb 1– a subset of single morphisms, defined on selected subsets of objects of the LInd ategory. The LEff category, taking into account the concepts of the web-based IS service management ontology highlighted in[27] and the connections between these concepts, has the form L Ob Ob Ob Ob Ob Ob Ob Ob H Eff St Pl St CStInd PL op EffRFC O ,,,, ,,,, __ _Prbb Ob Ob Ob Ob Ob Ob Ob Ob Ob Pl St St CSt St St Ind op St op P H HH H __ Pr Pr _ ,, ,, LL op Eff Pl St Eff CSt Eff RFC St Ob HHHHH Ob Ob Ob Ob Ob Ob Ob Ob ,,,,, Pr __ 1 , (1.4) where ObProp– a subset of objects of the LEff category that describes the "Property" concept; ObEff– a subset of objects of the LEff category that describes the "Effi ciency" concept; H Ob Ob op St Pr – a subset of morphisms of the LEff category defined between the ObSt and ObProp subsets; H Ob Ob op PL Pr _– a subset of morphisms of the LEff category defined between the ObP_L and ObProp subsets; H Ob Ob Pl St Eff _– a subset of morphisms of the LEff category defined between the ObEff and ObPl_St; subsets H Ob Ob CSt Eff _– a subset of morphisms of the LEff category defined between the ObEff and ObPl_St subsets; HOb Ob RFC St – a subset of morphisms of the LEff category defined between the ObSt and ObRFC subsets; HOb 1– a subset of unit morphisms defined on selected subsets of objects of the LEff category. According to the provisions of[3], the management of effective operation of web-based IS is based on the cycle "Plan– Do– Check– Act" (PDCA). In this management cycle: –at the "Plan" stage, the development of web-based IS operation plans is carried out; –at the "Do" stage, work is carried out to implement web-based IS operation plans; –at the "Check" stage, work is carried out to verify the results of the implementation of web-based IS operation plans; –at the "Act" stage, work is carried out to correct web-based IS operation plans. Then the generalized model of effective management of web-based IS operation can be represented as a supercategory of the following form[27] ML LL LF FFFF OPDChAL L L L L L L L L L D P Ch D D Ch A Ch P A ,, ,, ,,,, , (1.5) where LP– a supercategory that formally descries the "Plan" stage; LD– a supercategory that formally describes the "Do" stage; LCh – a supercategory that formally describes the "Check" stage; LA– a supercategory that formally describes the
23 Basics of the effective management methodology of web-based information systems Chapter 1 "Act"stage; FL L D P– a single covariant functor that establishes a connection between the LP and LD supercategories; FL L Ch D– a single covariant functor that establishes a connection between the LD and LCh supercategories; FL L D Ch – a single covariant functor that establishes a connection between the LCh and LD supercategories; FL L A Ch – a single covariant functor that establishes a connection between the LCh and LA supercategories; FL L P A– a single covariant functor that establishes a connection between the LA and LP supercategories. The functors FL L D P, FL L Ch D, FL L A Ch and FL L P A connect the supercategories LP, LD, LCh and LA according to the control cycle of the operated web-based IS. The functor FL L D Ch establishes a connection between the supercategories LCh and LD to describe situations when the operation of the web-based IS is carried out according to the developed plans and there is no need to adjust these plans. To detail the formal description of the supercategories LP, LD, LCh and LA, the category of description of the states of the operated IS LSt (1.2) was divided into two subcategories: the subcategory of description of the planned state of the operated IS LSt P and the subcategory of description of the current state of the operated IS LSt C . The LSt P subcategory has the form[6, 27] L Ob Ob Ob Ob Ob Ob HH St PConf PL CI Tr St Pl St Ob Ob Ob Conf PL C ,,,,,,, __ _ oonf CI Conf Tr Tr CI St Conf Pl St St Ob Ob Ob Ob Ob Ob Ob Ob Ob HHHHH , ,, ,, _ 1 OOb , (1.6) and the subcategory LSt C has the form[6, 27] L Ob Ob Ob Ob Ob Ob HH St CConf PL CI Tr St CStOb Ob Ob Conf PL Co ,,,,,,, __ _ nnf CI Conf Tr Tr CI St Conf CSt St Ob Ob Ob Ob Ob Ob Ob Ob Ob Ob HHHHH , ,, ,, _1 . (1.7) Then, taking into account the previously developed categorical descriptions of the exploited ISs, the LP supercategory is proposed to be described as follows[6, 27] LL LL FF PISSt P IndL L L L St P IS Ind St P ,, ,, , (1.8) where F L L St P IS – a single covariant functor that establishes a connection between the LIS categories LIS and LSt P ; FL L Ind St P – a single covariant functor that establishes a connection between the categories LSt P and LInd. The LD supercategory is proposed to be described as follows[6, 27] LL LL FF DISSt C IndL L L L St C IS Ind St C ,, ,, , (1.9)
24 Management of a modern IT company: theoretical and technological aspects where F L L St C IS – a single covariant functor that establishes a connection between the LIS categories LIS and LSt P ; FL L Ind St P – a single covariant functor that establishes a connection between the supercategories and LInd. The LCh supercategory is proposed to be described as follows[6, 27] LL LLL FFFF Ch IS St P St C IndL L L L L L L L St P IS St C IS Ind St P Ind S ,,, ,,,,tt C . (1.10) The LA supercategory is proposed to be described as follows[27] LL LF AISEff L L Eff IS ,, , (1.11) where F L L Eff IS – a single covariant functor that establishes a connection between the supercategories LIS and LEff. The diagram of the relationships between the elements of the generalized model of effective management of the operation of web-based IS (1.5) is shown in Fig.1.4[6]. Fig. 1.4 Diagram of relationships between elements of a generalized model of effective management of the operation of a web-based information system LP LDLCh LA P D L L F A P L L F Ch A L L F D Ch L L F Ch D L L F This diagram establishes transitions between the main states of the cycle "Plan– Do– Check– Act" of effective management of the operation of a web-based IS. In this diagram, states are defined as supercategories LP, LD, LCh and LA, which describe the corresponding stages of the mentioned cycle. Transitions between these
25 Basics of the effective management methodology of web-based information systems Chapter 1 states are shown as functors FL L D P, FL L Ch D, FL L D Ch , FL L A Ch and FL L P A. Thus, model (1.5) can be represented as a finite state machine, transitions between the states of which are associated with changing the alphabets of the description of these states, although they retain their structural features. 1.4.3 Results of the development of a formal statement of the problem ofeffective management of the operation of a web-based information system The use of the developed set of theoretical and categorical models (1.1)–(1.11) allowed to formally describe the global problem of managing the operation of a webbased IS as an IT service system. In doing so, it is possible to proceed from the following assumption. Assumption5: the main approach to managing an IT service system is the "Plan– Do– Check– Act" cycle. As noted above, classical management of the operation of an IT service system is management aimed at minimizing the number of incident reports that remain unresolved. Therefore, it is proposed to consider the target state of the operated IT service system as a state in which the number of incident reports and RFC of the managed IT service system tends to 0. Let's call such a state of the operated IS as an IT service system stable. The aspiration of the operated web-based IS to a stable state is proposed to be described by an objective function, which has the form[6] () () , ,, Tr RFC ii njjm 11 0 (1.12) where Tri– the transaction, the execution of which generates the i-th incident; n is the number of incidents that occur during the operation of the web-based IS; RFCj– the j-th RFC; m – the number of RFCs that occur during the operation of the web-based IS. The objective function (1.12) of the classical (permanent) LC management r of the operation of a web-based IS is limited by the following conditions[6]: –for each incident during its elimination, the planned and current states in which the operated IS may be during the control of its operation must be determined Tr Ob LL LLLL iTrISD St P Ch St C Ch ,; (1.13)
26 Management of a modern IT company: theoretical and technological aspects –for each RFC during its implementation, the planned and current states in which the operated IS may be during the control of its operation must be determined RFCObLLLLL L iRFC IS DSt P Ch St C Ch ,; (1.14) –the current state of the IS in the process of controlling its operation must fully correspond to its planned state (based on the features of the "Plan– Do– Check– Act" cycle and model (1.5)) ()().LLLL LLLL St P Ch St C Ch St C Ch St P Ch 0 (1.15) Such a formulation of the task of managing the operation of a web-based IS will allow obtaining an IS that will be best adapted to the requirements of its users. But such adaptability does not guarantee effective operation of the IS, because the set of requirements and RFC itself may not be aimed at achieving effective planned and current states of the operated IS. Therefore, an attempt to achieve goal (1.12) may lead to an increase in RFC. This increase is due to the fact that the number of RFCs that will arise during the operation of the IS can increase only because previous solutions to the management task will not give the desired coincidence of planned and current states. This situation will be especially pronounced in cases where the business processes of the automation object, the IS itself and the IT infrastructure in which the IS is operated are in a state of constant change. Unlike the considered concept of classical (constant) management, the proposed concept of effective management of the operation of web-based IS uses an additional concept of "system property"[31]. At the same time, the interest for the Consumer and the Supplier of IS is only those properties of the system that characterize the manifestations of individual qualities of the web-based IS. The qualities of the web-based IS, in turn, are determined by a set of requirements (functional and non-functional) that are imposed on the IS before the start of its operation, as well as a set of RFCs of the IS and its individual CIs formed during the operation of the IS. In this case, effective management of the operation of the web-based IS will be defined as actions to achieve the planned results for each individual property of the IS and its CIs. Then the task of achieving the global goal of effective management of the operation of the web-based IS will be considered as the task of achieving optimal characteristics of this IS for each of its specific properties and the minimum probability of the existence of unsolved incidents and RFCs during the operation stage of this IS. The formal description of the objective function of this task will be as follows[6]
27 Basics of the effective management methodology of web-based information systems Chapter 1 fObLOb Lo pt fObLOb EffEff EffEff EffEff E 11 1 22 (, ), (, Prop Prop fff Eff Eff zz EffEff Eff Lo pt fObLOb L ), (, 2 Prop ) ), () ()min, opt PTrPRFC z i i n j j m 11 (1.16) where 1,2,…,z– identifiers of individual properties of the operated IS; P(Tri)– probability of no beneficial exchange between the operated IS and its environment as a result of transaction Tri; P(RFCj)– probability of no beneficial exchange between the operated IS and its environment as a result of RFC RFCj implementation. The objective function of effective management of web-based IS operation (1.16) is limited by the following conditions[6]: –for any specified k-th property of the operated IS, there must be a set of states of this IS, being in which the operated IS will be considered effective for this property ob Ob LL optObLLObLL Eff k EffEff A k St IS DInd IS D ,, (1.17) where Ob LL IndISD ∈∈ – a set of indicators by which the fact of this IS being in an effective state is established during the operation of the web-based IS; –for each incident during its elimination, planned and current states must be determined, being in which the operated IS can be considered effective Tr Ob LL LLLLLL iTrISD St P Ch St C Ch Ef fA ,, ; (1.18) – for each RFC during its implementation, planned and current states must be determined, being in which, the operated web-based IS can be considered effective RFCObLLLLL LL L jRFC IS DSt P Ch St C Ch Ef fA ,, ; (1.19) –the current state of the web-based IS in the process of controlling its operation must approach its planned state (based on the features of the "Plan– Do– Check– Act" cycle and model (1.5)) with some permissible small deviation ()().LLLL LLLL St P Ch St C Ch St C Ch St P Ch (1.20)
28 Management of a modern IT company: theoretical and technological aspects The developed formulation of the problem of effective management of the operation of web-based IS allows to consider the problem of classical (permanent) management of the operation of web-based IS as a separate case of problem (1.16)–(1.20). For this case, the objective function (1.16) will have the form: fObLOb Lo pt fObLOb EffEff EffEff EffEff E 11 1 22 (, ), (, Prop Prop fff Eff Eff zz EffEff Eff Lo pt fObLOb L ), (,) 2 Prop opt PTrPRFC z i i n j j m , () (). 11 0 (1.21) The proposed formal description of the task of effective management of the operation of a web-based IS will allow obtaining an IS that will be during its operation: –best adapted to the requirements of its users and the features of the IT infrastructure and business processes of the automation object existing during operation; –be in those states that will be recognized as effective by both the Consumer and the Supplier (including, based on their strategies and goals within the IS LC[5]). 1.5 Results of the development of a theoretical and categorical model ofthe property of an information system The proposed formal statement of the problem of effective management of the operation of web-based IS requires specifying the formal description of the concept "Property" and its possible connections with the "State of IS", "Indicator", "Presentation Layer" and "Efficiency" concepts. Based on the formal description of the objective function (1.16), effective management of the operation of web-based IS requires the use of sets of parameters (or estimates of their values), which are elements of sets of objects of the categorical models of the concepts "Property" and "Efficiency". Therefore, to specify the formal model of the property of IS, it is proposed to use the following assumption. Assumption6: the main principles of effective management at individual stages of web-based IS LC should be identical to each other. Using this assumption allows to formulate the main principle of effective management of the operation of web-based IS by analogy with the main principle of managing IS requirements described in[5]. This principle consists in the gradual
35 Basics of the effective management methodology of web-based information systems Chapter 1 HRS AbL – a morphism that defines the hierarchy of subordination of descriptions of the rating scale to descriptions of the corresponding capability level. HPAM morphisms subset in the general case consists of the following morphisms HHH PAMTr PAM Ind PAM , , (1.37) where HTr PAM – a morphism that defines the hierarchy of subordination of descriptions of transactions as IS CIs, the state of which is measured, to descriptions of process attributes used during measurement; HInd PAM – a morphism that defines the hierarchy of subordination of descriptions of indicators used to measure the state of a transaction as IS CI descriptions of process attributes used during measurement. HAM PMF morphisms subset in the general case consists of a HPAM PA morphism that defines the subordination of descriptions of process attributes used during measurement to descriptions of process attributes of the measurement scheme. A diagram of the structure of the category-theoretic model LProp, which describes the "Property" concept, is shown in Fig.1.5. Fig. 1.5 Structure diagram of the theoretical-categorical model LProp, which describes the concept of "Property" ObAbL ObPA ObPMF ObP_G ObAM ObPAM LProp ObRS As Tr Ob As Ind Ob PAM Tr H PAM Ind H _ P G PMF H _ P G AM H AbL PA H AbL RS H PA PAM H Modern standards and IT are focused on solving the problem of classical (permanent) management of IS operations, in which deviations between the planned and
36 Management of a modern IT company: theoretical and technological aspects current values of state indicators of individual IS CIs are measured. The application of the LProp model in the process of solving the problem of effective management of the operation of web-based IS made it possible to formulate and formally solve the following variants of this problem: –the problem of minimizing deviations in the values of the levels of capabilities of IS transactions at any of the levels of representation of this IS (the problem of optimizing the levels of maturity of IS and its elements); –the problem of minimizing deviations in the values of the attributes of IS transaction processes at any of the levels of capabilities and levels of representation of this IS (the problem of optimizing the states of IS and its elements within the selected maturity levels); –the task of minimizing deviations in the values of IS transaction indicators and their CI within individual process attributes at any of the levels of capabilities and levels of representation of this IS (the task of classical (constant) IS operation management). 1.6 Discussion of the research results In the process of the research, a concept of effective management of the LC of an operated web-based IS was proposed. The proposed concept consists in a multi-level representation of a web-based IS as a product with a set of individual properties. In this case, each property of the IS is considered as a manifestation of the individual qualities of this system. Each quality, in turn, is proposed to be considered as the result of fulfilling a set of requirements and RFCs of the IS and its SI. This concept allows to formally describe the task of effective management of the LC of an operated IS as a task of achieving optimal characteristics of this IS for each of its specific properties and the minimum probability of the existence of unresolved incidents and RFCs during the operation stage of this IS. For a formal description of the proposed concept, a generalized model of effective management of the operation of web-based IS (1.5)–(1.11) and a complex of theoretical and categorical models (1.1)–(1.4) were developed, which detail the description of the elements of this model. The use of the apparatus of category theory allows to further present the generalized model (1.5)–(1.11) as a finite state machine, the transitions between the states of which are associated with the change of the alphabets of the description of these states, although they retain their structural features. Such a representation allows to consider the developed models (1.1)–(1.11) in further studies as the basis for a formal description of the
37 Basics of the effective management methodology of web-based information systems Chapter 1 automated effective management of the operation of web-based IS based on the "Plan– Do– Check– Act" cycle. This description can exist provided that it is possible to prove the possibility of transforming the corresponding finite state machine into a consistent set of simpler finite state machines that describe IT processing of data structures at each stage of the cycle[6]. Based on the developed generalized model (1.5)–(1.11), a formal description (1.12) of the purpose of classical (permanent) LC management of the operated IS and limitations (1.13)–(1.15) was developed. Taking into account these formal descriptions and the results of the development of the concept of effective LC management of an operated web-based IS, a formal description of the objective function of effective management of the LC of an operated IS (1.16) and systems of constraints (1.17)–(1.20) was developed. The obtained results allow to define the problem of classical (permanent) LC management of an operated IS (1.21) as a special case of the problem of effective management. To clarify the formal statement of the problem of effective LC management of an operated web-based IS, a theoretical-categorical model of the properties of an operated web-based IS (1.22)–(1.37) was developed. The use of the developed theoretical-categorical model LProp allowed to significantly change the features of the statement and solution of the problem of effective management of the operation of a web-based IS. Solving this problem using the developed model (1.22)–(1.37) will allow not only to maintain the operated IS in a stable state, but also to determine the optimal levels of maturity of the IS and its individual transactions from the point of view of the Consumer and the Provider of IT services. This allows stakeholders to plan and manage the recognition of the feasibility and implementation of the following measures during the operation of a web-based IS: –standardization (typification) of individual IS transactions and IS as a whole at any of the representation levels; –to ensure the manageability of individual transactions of the IS and the IS as awhole (in real time or time close to real); –to ensure the optimal operation of individual transactions of the IS and the IS as a whole. It should be noted that a significant number of modern studies in the field of PLM, ALM and SLM use the mathematical apparatus of graph theory for the formal description of the tasks to be solved. Examples of such studies are[40,41]. Incontrast, in this study, the mathematical apparatus of category theory was used for the formal description of the tasks of LC management of the operated IS. The theoretical and categorical models of the operated IS and the tasks of LC management of this IS used and developed in this study are based on the ontology of web-based
38 Management of a modern IT company: theoretical and technological aspects IS services management proposed by one of the authors of the study in[27] and allow to establish: –the boundaries of domains and data structures used to describe individual concepts of the ontology; –the rules for transforming domains and data structures when creating connections between different concepts of the ontology. The applied application of the models developed in this study makes it possible to transition to effective LC management of an operated IS without global reengineering of systems and technologies for data storage and processing. The vast majority of IT products for LC management of an operated IS are highly specialized and relatively new products that occupy a small market segment. Therefore, systems for LC management of an operated IS are most often the result of integrating a large number of such highly specialized products. The proposed theoretical and categorical models allow in such cases[6]: –to determine domains and data structures for technologies for integrating heterogeneous IT products into a single system; –to ensure the transition from classical to effective LC management of an ITservice system without serious changes in the list of highly specialized products inoperation. Also important from an applied point of view is the proposed presentation of the existing problem of classical (permanent) LC management of an operated IS as a separate case of the problem of effective management. This representation allows to consider the design and implementation of an effective LC management system of operated IS as a gradual evolutionary development of the previously created and already operating system for the classical LC management of IT services. The main limitation of this study is the need to use complete descriptions of all elements of this IS to solve the problem of effective LC management of an operatedIS. This means that during at least one iteration of the "Plan– Do– Check– Act" cycle, IS administrators must interact with a complete digital model of this IS at all levels of representation to solve individual tasks of LC management. The development and maintenance of such a model is a complex and costly task. But this limitation is methodological in nature and is valid for any work in the field of change management of developed or operated IS (which is confirmed, for example, by studies[42,43]). Another feature of the obtained results is their orientation on the LC management of the operated IS in conditions of constant changes in business processes, functions and elements of IT infrastructure. This feature is a consequence of the generalization of applied experience in supporting and ensuring the functioning of IS management of enterprises and organizations in conditions of martial law, which is in force in Ukraine[6].
39 Basics of the effective management methodology of web-based information systems Chapter 1 Although the obtained research results are methodological in nature, they should be recognized as important for further theoretical and applied research in the field of creating PLM-, ALMand SLM-IS and IT. The main further directions of development of this research are[6]: –determination of the set of properties of the operated IS and efficiency indicators for these properties; –development of new and improvement of existing models, detailing the formal description of the task of effective management; –development and implementation of methods and algorithms for solving problems of effective management of various IS and IT options. 1.7 Conclusions The concept of the task of effective LC management of an operated IS as an IT service system is formulated. The formulated concept allows to formally describe the task of effective LC management of an operated IS as the task of achieving optimal characteristics of this IS for each of its specific properties and the minimum probability of the existence of unresolved incidents and RFCs during the operation stage of this IS. The result obtained takes into account the points of view of the Supplier and Consumer of IT services as the main stakeholders of web-based IS. During further research, the main attention was paid to the development of elements of the methodology for effective management of the operation of webbased IS precisely from the point of view of the Supplier as an IT company that provides (sells or leases) its own web-based IS for operation by enterprises or organizations acting as Consumers. A generalized model of effective management of web-based IS operation (1.5)–(1.11) and a set of theoretical and categorical models (1.1)–(1.4) that detail the description of the elements of this model have been developed. The developed models are a formal basis for creating IS and IT for effective management of webbased IS operation without global reengineering of systems and technologies for data storage and processing. Unlike existing models of a similar purpose, the developed models allow establishing the boundaries of domains and data structures used to describe the elements of the generalized model (1.5)–(1.11), as well as the rules for transforming domains and data structures when creating connections between different elements of this model. A formal statement of the problem of classical (permanent) LC management of operated IS as an IT service system has been developed. A formal description of
40 Management of a modern IT company: theoretical and technological aspects the objective function (1.12) and constraints (1.13)–(1.15) of this problem is proposed using the apparatus of category theory and set theory. The developed formal formulation is based on the existing definition of the goal of such management as maximizing the satisfaction of IS users based on the results of each iteration of the "Plan– Do– Check– Act" cycle of LC management of the operated IS. It is proposed to consider the IS state as a formal sign of such satisfaction as the number of incident reports and RFCs of the operated IS tending to 0. The results obtained allow to formally describe the task of LC management of the operated IS in conditions of stable(unchangeable) business processes and IT infrastructure of enterprises and organizations as objects of automation. A formal description of the objective function (1.16) and constraints (1.17)–(1.20) of the task of effective LC management of the operated IS is proposed using the apparatus of category theory, set theory and elements of probability theory. It is determined that the task of classical (permanent) LC management of the operated IS is a special case of the proposed task of effective management. Practical application of the proposed formal description of the task of effective LC management of an operated IS allows improving SLM-systems for LC management of an operated IS without global reengineering of existing systems and technologies for data storage and processing. A theoretical and categorical model of the IS property (1.22)–(1.37) has been developed. This model allows formally describing any IS property taking into account the current requirements set by modern standards for the implementation of the processes of assessing the LC of the system. Using the developed model (1.22)–(1.37) allows solving tasks for automating effective planning and management of the operation of web-based IS. Conflict of interest statement The authors declare that there is no conflict of interest in relation to this paper, as well as the published research results, including the financial aspects of conducting the research, obtaining and using its results, as well as any non-financial personal relationships. Use of artificial intelligence statement The authors declare that they did not use artificial intelligence tools in preparing this manuscript.
41 Basics of the effective management methodology of web-based information systems Chapter 1 References 1. What is Web (Based) Information System. IGI Global. Available at: https:// www.igi-global.com/dictionary/web-based-information-system/32189#:~: text=An%20information%20system%20that%20utilizes,or%20other%20information%20systems%2Fapplications 2. Fulton, J. (2017). Web Architecture 101. Medium. Available at: https://medium. com/storyblocks-engineering/web-architecture-101-a3224e126947 3. ISO/IEC 20000-1. Information technology – Service management – Part 1: Service management system requirements (2018). Geneva: ISO Copyright Office, 96. 4. ISO/IEC/IEEE Standard No 15288:2015 (2015). Systems and software engineering – System life cycle processes. ISO/IEC/IEEE International Standard. https://doi.org/10.1109/IEEESTD.2015.7106435 5. Levykin, V. M., Evlanov, M. V., Kernosov, M. A. (2014). Patterny proektirovaniia trebovanii k informatcionnym sistemam: modelirovanie i primenenie. Kharkiv: OOO "Kompaniia "Smit", 320. 6. Levykin, V., Ievlanov, M., Levykin, I., Petrychenko, O. (2025). Development of a concept for the task of life cycle effective management of an operated information system. Technology Audit and Production Reserves, 2 (2 (82)), 66–73. https://doi.org/10.15587/2706-5448.2025.326479 7. Stark, J. (2020). Product Lifecycle Management (Vol.1). Cham: Springer International. https://doi.org/10.1007/978-3-030-28864-8 8. Schwaber, C. (2006). The Changing Face of Application Life-Cycle Management. Forrester Research Inc. Available at: https://www.yumpu.com/en/document/ view/13866040/download-the-changing-face-of-application-life-cycle-mks 9. Wyrwich, F., Kharatyan, A., Dumitrescu, R. (2024). Interdisciplinary system lifecycle management – a systematic literature review. Proceedings of the Design Society, 4, 2765–2774. https://doi.org/10.1017/pds.2024.280 10. Rizzo, S. (2016). Why ALM and PLM need each other. Siemens Whitepaper. Available at: https://polarion.plm.automation.siemens.com/hubfs/Docs/Whitepapers/why-alm-and-plm-need-each-other-whitepaper.pdf 11. Liepert, C., Stary, C., Lamprecht, A., Zügn, D.; Elstermann, M., Lederer, M. (Eds.) (2025). Interoperable Product Change Management Within Engineering: A Digital Twin Approach. Subject-Oriented Business Process Management. Models for Designing Digital Transformations. S-BPM ONE 2024. Communications in Computer and Information Science. Vol. 2206. Cham: Springer. https:// doi.org/10.1007/978-3-031-72041-3_17
42 Management of a modern IT company: theoretical and technological aspects 12. Chappell, D. (2010). What is Application Lifecycle Management? David Chappell and Associates. Available at: http://davidchappell.com/writing/white_papers/ What_is_ALM_v2.0--Chappell.pdf 13. Eigner, M. (2021). System Lifecycle Management: Digitalisierung des Engineering. Berlin, Heidelberg: Springer Vieweg. https://doi.org/10.1007/978-3-66262183-7 14. Binder, C., Neureiter, C., Lüder, A. (2022). Towards a domain-specific information architecture enabling the investigation and optimization of flexible production systems by utilizing artificial intelligence. The International Journal of Advanced Manufacturing Technology, 123 (1-2), 49–81. https://doi.org/10.1007/s00170022-10141-2 15. Colantoni, A., Berardinelli, L., Garmendia, A., Bräuer, J. (2022). Towards Blended Modeling and Simulation of DevOps Processes: the Keptn Case Study. MODELS'22: Proceedings of the 25th International Conference on Model Driven Engineering Languages and Systems: Companion Proceedings, Association for Computing Machinery. New York, 784–792. https://doi.org/10.1145/3550356.3561597 16. Gulzar, K., Ruusu, R., Sierla, S., Aarnio, P., Karhela, T., Vyatkin, V. (2018). Automatic Generation of a Lifecycle Analysis Model from a First Principles Industrial Process Simulation Model. 2018 IEEE 16th International Conference on Industrial Informatics (INDIN). Danvers, 741–746. https://doi.org/10.1109/ indin.2018.8471980 17. Calderon, N. N., Kajko-Mattsson, M., Nolan, A. J. (2015). Successful process improvement projects are no accidents. Journal of Software: Evolution and Process, 27 (11), 896–911. https://doi.org/10.1002/smr.1738 18. Reiff-Marganiec, S., Tilly, M. (Eds.) (2012). Handbook of Research on Service-Oriented Systems and Non-Functional Properties: Future Directions. IGI Global. https://doi.org/10.4018/978-1-61350-432-1 19. Driss, M., Aljehani, A., Boulila, W., Ghandorh, H., Al-Sarem, M. (2020). Servicing Your Requirements: An FCA and RCA-Driven Approach for Semantic Web Services Composition. IEEE Access, 8, 59326–59339. https://doi.org/10.1109/ access.2020.2982592 20. Kienzle, J., Combemale, B., Mussbacher, G., Alam, O., Bordeleau, F., Burgueno, L. et al. (2022). Global Decision Making Over Deep Variability in Feedback-Driven Software Development. Proceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering. New York. https://doi.org/ 10.1145/3551349.3559551 21. Moosbauer, J., Binder, M., Schneider, L., Pfisterer, F., Becker, M., Lang, M. et al. (2022). Automated Benchmark-Driven Design and Explanation of
43 Basics of the effective management methodology of web-based information systems Chapter 1 Hyperparameter Optimizers. IEEE Transactions on Evolutionary Computation, 26 (6), 1336–1350. https://doi.org/10.1109/tevc.2022.3211336 22. Garouani, M., Ahmad, A., Bouneffa, M., Hamlich, M., Bourguin, G., Lewandowski,A. (2022). Using meta-learning for automated algorithms selection and configuration: an experimental framework for industrial big data. Journal of Big Data, 9 (1). https://doi.org/10.1186/s40537-022-00612-4 23. Bush, B., Stright, D., Huggins, J., Newes, E. (2022). Simulation process and data flow for a large system dynamics model. Simulation, 98 (9), 823–833. https:// doi.org/10.1177/00375497221093381 24. Ebert, C. (2013). Improving engineering efficiency with PLM/ALM. Software&Systems Modeling, 12 (3), 443–449. https://doi.org/10.1007/s10270013-0347-3 25. Deuter, A., Imort, S. (2020). PLM/ALM Integration With The Asset Administration Shell. Procedia Manufacturing, 52, 234–240. https://doi.org/10.1016/ j.promfg.2020.11.040 26. Deuter, A., Otte, A., Höllisch, D. (2017). Methodisches Vorgehen zur Entwicklung und Evaluierung von Anwendungsfällen für die PLM/ALM-Integration. Wissenschaftsforum Intelligente Technische Systeme (WInTeSys). Paderborn, 211–222. https://doi.org/10.17619/UNIPB/1-93 27. Petrichenko, O. V. (2021). Improving enterprise IT-service management methodology. Management Information System and Devises, 177, 4–12. https://doi.org/ 10.30837/0135-1710.2021.177.004 28. Date, C. J. (2003). Introduction to Database Systems. Pearson, 1040. 29. Dilovi tranzaktsii. Microsoft Build. Available at: https://docs.microsoft.com/ uk-ua/dynamics365/project-operations/psa/basic-business-transactions 30. Tanenbaum, A., Wetherall, D. (2010). Computer Networks. Pearson, 960. 31. Fleishman, B.; Patten, B., Jorgenson, S. (Eds). (1995). Stochastic Theory of Complex Ecological Systems. Complex Ecology. New Jersey: Prentice Hall PTP, Prentice Hall Inc, 166–224. 32. Kanaga Priya, P., Reethika, A.; Mishra, A., El Barachi, M., Kumar, M. (Eds.) (2024). A Review of Digital Twin Applications in Various Sectors. Transforming Industry using Digital Twin Technology. Cham: Springer, 239–258. https://doi.org/ 10.1007/978-3-031-58523-4_12 33. Guinea-Cabrera, M. A., Holgado-Terriza, J. A. (2024). Digital Twins in Software Engineering – A Systematic Literature Review and Vision. Applied Sciences, 14(3), 977. https://doi.org/10.3390/app14030977 34. Ievlanov, M. V., Neumyvakina, O. E., Karamysheva, A. Iu. (2012). Global goals of IT-services supplier and consumer. Eastern-European Journal of Enterprise
44 Management of a modern IT company: theoretical and technological aspects Technologies, 5 (2 (59)), 12–17. Available at: https://journals.uran.ua/eejet/ article/view/4137 35. ISO/IEC/IEEE Standard No 15504-5 (2012). Information technology – Process assessment – An exemplar software life cycle process assessment model ISO/IEC/IEEE International Standard. 36. ISO/IEC/IEEE Standard No 33061 (2021). Information technology – Process assessment – Process assessment model for software life cycle processes. ISO/IEC/IEEE International Standard. 37. Mesquida, A. L., Mas, A.; O'Connor, R. V., Pries-Heje, J., Messnarz, R. (Eds.) (2011). ISO/IEC 15504-5 Best Practices for IT Service Management. Systems, Software and Service Process Improvement. Springer 14–24. https://doi.org/ 10.1007/978-3-642-22206-1_2 38. Jung, H.-W., Ting, K.-F. (2017). An empirical evaluation of ISO/IEC 15504-5 capability measures: Reflective or formative. Computer Standards & Interfaces, 53, 123–130. https://doi.org/10.1016/j.csi.2017.03.002 39. Monla, Z., Assila, A., Beladjine, D., Zghal, M.; De Paolis, L. T., Arpaia, P., Sacco, M. (Eds.) (2023). A Conceptual Framework for Maturity Evaluation of BIM-Based AR/VR Systems Based on ISO Standards. Extended Reality. Springer, 139–156. https://doi.org/10.1007/978-3-031-43401-3_9 40. Zimmermann, T. C., Konietzko, E., Lindow, K. (2024). Graph-based Parameter Management for Configuration Controlled Multi-level Modeling of Cyber-physical Systems. 2024 19th Annual System of Systems Engineering Conference (SoSE). Tacoma, 270–274. https://doi.org/10.1109/sose62659. 2024.10620964 41. Katzung, S., Cinkaya, H., Kizgin, U. V., Savinov, A., Baschin, J., Vietor, T. (2024). AI-based analysis and linking of technical and organisational data using graph models as a basis for decision-making in systems engineering. Proceedings of the Design Society, 4, 2625–2634. https://doi.org/10.1017/pds.2024.265 42. Rostami, K., Stammel, J., Heinrich, R., Reussner, R. (2017). Change Impact Analysis by Architecture-based Assessment and Planning. Lecture Notes in Informatics, Proceedings – Series of the Gesellschaft fur Informatik. Hannover, 267, 69–70. 43. Rostami, K., Heinrich, R., Busch, A., Reussner, R. (2017). Architecture-Based Change Impact Analysis in Information Systems and Business Processes. 2017 IEEE International Conference on Software Architecture (ICSA). Gothenburg, 179–188. https://doi.org/10.1109/icsa.2017.17