A code tracking system monitors usage of application code executed by one or more computing devices. Characteristics of the usage of the application code are determined. Using the characteristics of the usage of the application code, a modification to an entry of application code executed by the one or more computing devices is detected. The detected modification to the entry of application code is communicated to a code management system. The code management system presents the modification to the entry of the application code to a user of the code management system.

A code tracking system monitors usage of application code executed by one or more computing devices. Characteristics of the usage of the application code are determined. Using the characteristics of the usage of the application code, a modification to an entry of application code executed by the one or more computing devices is detected. The detected modification to the entry of application code is communicated to a code management system. The code management system presents the modification to the entry of the application code to a user of the code management system.

A system may include a historical managed software system data store that contains electronic records associated with controllers and deployed workloads (each electronic record may include time series data representing performance metrics). An entropy calculation system, coupled to the historical managed software system data store, may calculate at least one historical entropy value based on information in the historical managed software system data store. A detection engine, coupled to a monitored system currently executing a deployed workload in the cloud computing environment, may collect time series data representing current performance metrics associated with the monitored system. The detection engine may then calculate a current monitored entropy value (based on the collected time series data representing current performance metrics) and (iii) compare the current monitored entropy value with a threshold value (based on the historical entropy value). Based on the comparison, a corrective action for the monitored system may be triggered.

A system may include a historical managed software system data store that contains electronic records associated with controllers and deployed workloads (each electronic record may include time series data representing performance metrics). An entropy calculation system, coupled to the historical managed software system data store, may calculate at least one historical entropy value based on information in the historical managed software system data store. A detection engine, coupled to a monitored system currently executing a deployed workload in the cloud computing environment, may collect time series data representing current performance metrics associated with the monitored system. The detection engine may then calculate a current monitored entropy value (based on the collected time series data representing current performance metrics) and (iii) compare the current monitored entropy value with a threshold value (based on the historical entropy value). Based on the comparison, a corrective action for the monitored system may be triggered.

A CI/CD assist device accepts configuration data and test data collectively from a terminal (a vendor terminal) of a provider that provides a network service to a customer. The configuration data specifies a functional unit required to provide the network service, and the test data specifies test content for the network service or the functional unit. Each of an NOS, an NOS, and an NOS automatically builds the functional unit specified by the configuration data that is accepted by the CI/CD assist device. Each of a test device, a test device, and a test device automatically conducts a test on the network service or the functional unit based on the test data. The network service and the functional unit are built in each environment.

A CI/CD assist device accepts configuration data and test data collectively from a terminal (a vendor terminal) of a provider that provides a network service to a customer. The configuration data specifies a functional unit required to provide the network service, and the test data specifies test content for the network service or the functional unit. Each of an NOS, an NOS, and an NOS automatically builds the functional unit specified by the configuration data that is accepted by the CI/CD assist device. Each of a test device, a test device, and a test device automatically conducts a test on the network service or the functional unit based on the test data. The network service and the functional unit are built in each environment.

Performing usage-based software library decomposition is disclosed herein. In some examples, a processor device generates a first library graph representing a first software library including multiple functions. The first library graph comprises a plurality of nodes that each correspond to a function of the first software library. The processor device identifies a function within the first software library (“invoked function”) that is directly invoked by an application that depends on the first software library, then generates a call graph including nodes within the first library graph (“dependency nodes”) corresponding to either the invoked function or another function invoked by the invoked function during application execution. Using the call graph, the processor device generates a second software library including only functions of the first software library corresponding to dependency nodes of the call graph.

Performing usage-based software library decomposition is disclosed herein. In some examples, a processor device generates a first library graph representing a first software library including multiple functions. The first library graph comprises a plurality of nodes that each correspond to a function of the first software library. The processor device identifies a function within the first software library (“invoked function”) that is directly invoked by an application that depends on the first software library, then generates a call graph including nodes within the first library graph (“dependency nodes”) corresponding to either the invoked function or another function invoked by the invoked function during application execution. Using the call graph, the processor device generates a second software library including only functions of the first software library corresponding to dependency nodes of the call graph.

Disclosed are methods, systems, devices, apparatus, media, design structures, platforms, and other implementations, including a method that includes receiving, by a processor-based device, configuration data representative of an initial arrangement of interlinked components forming a data application, and determining based on the configuration data, by the processor-based device, one or more complexity scores indicative of levels of complexities for one or more portions of the initial arrangement of interlinked components forming the data application. The method further includes automatically reconfiguring, by the processor-based device, the initial arrangement of interlinked components based on the computed one or more complexity scores to produce a resultant arrangement of interlinked components forming the data application.

In one implementation, systems and methods are provided for developing a computer-implemented digital experience application having a first and a second micro-application. Each micro-application includes a front end interface configured to receive and display information. The first micro-application includes a first event manager configured to detect an application event belonging to a category, and a first state manager configured to detect an application state belonging to the category. The digital experience application further includes a driver application configured to host the first and second micro-applications, an event hub configured to receive the detected application event from the first micro-application, and a state store configured to store the detected application state received from the first micro-application. The second micro-application includes a second event manager configured to receive the detected application event from the event hub, and a second state manager configured to receive the detected application state from the state store.