Methods, computer program products, and/or systems are provided that perform the following operations: identifying an application marker for a source application; mapping the application marker to a set of micro-patterns provided in a micro-pattern repository, wherein a micro-pattern defines a set of actions to be performed to modernize a source application component for a target platform; generating a set of potential modernization pathways for the source application, wherein a potential modernization pathway is based, at least in part, on an aggregation of one or more micro-patterns included in the set of micro-patterns mapped to the application marker; determining a recommended modernization pathway from the set of potential modernization pathways based, at least in part, on micro-pattern optimization; and providing the recommended modernization pathway for source application modernization execution, wherein the source application modernization execution includes executing each micro-pattern included in the recommended modernization pathway.

Methods, computer program products, and/or systems are provided that perform the following operations: identifying an application marker for a source application; mapping the application marker to a set of micro-patterns provided in a micro-pattern repository, wherein a micro-pattern defines a set of actions to be performed to modernize a source application component for a target platform; generating a set of potential modernization pathways for the source application, wherein a potential modernization pathway is based, at least in part, on an aggregation of one or more micro-patterns included in the set of micro-patterns mapped to the application marker; determining a recommended modernization pathway from the set of potential modernization pathways based, at least in part, on micro-pattern optimization; and providing the recommended modernization pathway for source application modernization execution, wherein the source application modernization execution includes executing each micro-pattern included in the recommended modernization pathway.

Disclosed embodiments relate to adjusting vehicle Electronic Control Unit (ECU) software versions. Operations may include receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software; configuring, in response to the prompt and based on a delta file corresponding to the second version of ECU software, the second version of ECU software on the ECU in the vehicle for execution; and configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable.

Disclosed embodiments relate to adjusting vehicle Electronic Control Unit (ECU) software versions. Operations may include receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software; configuring, in response to the prompt and based on a delta file corresponding to the second version of ECU software, the second version of ECU software on the ECU in the vehicle for execution; and configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable.

Methods are described herein for creating and installing software updates which may be rolled back, without requiring large processing capabilities and/or large storage capacity at a device. Delta software updates are determined comprising differences, on a bit-level, between a first version of the software and a second, updated, version of the software, and metadata defining how to apply the differences. Methods of performing a rollback-capable update at a device are also described herein.

A method includes inputting at least one compressed image in a computing system. The method also includes an inplace patching process. Another image is decompressed over the compressed image by a processor. Local variables are stored periodically, receiving restored power after an interruption to the inplace patching, wherein an execution of the inplace patching is resumed at a later time interval by the processor by restoring the local variables. The method also includes completing the inplace patching process of decompressing the image over the inputted compressed image after restoring the local variables.

When configuration information regarding configurations of respective devices are received from electronic control units, the in-vehicle device generates a hash value based on data values of the configuration information, and transmits the hash value to a center device. The center device compares the hash value received from the in-vehicle device with a hash value of configuration information of the vehicle stored in a vehicle-side configuration information storage unit of the center device, and notifies the in-vehicle device of a full data transmission request for transmitting all data values of the configuration information when both of the hash values do not match each other. When the in-vehicle device is notified of the full data transmission request, the in-vehicle device transmits all of the data values of the configuration information to the center device.

When configuration information regarding configurations of respective devices are received from electronic control units, the in-vehicle device generates a hash value based on data values of the configuration information, and transmits the hash value to a center device. The center device compares the hash value received from the in-vehicle device with a hash value of configuration information of the vehicle stored in a vehicle-side configuration information storage unit of the center device, and notifies the in-vehicle device of a full data transmission request for transmitting all data values of the configuration information when both of the hash values do not match each other. When the in-vehicle device is notified of the full data transmission request, the in-vehicle device transmits all of the data values of the configuration information to the center device.

A Smart Products Lifecycle Management (sPLM) system that is built upon the smart component data model and the NPD.sup.3 process model, is enabling engineers, data scientists, and other stakeholders to collaborate on a common platform to develop smart products. The sPLM system is validated by applying it to unmanned aircraft systems (UAS) development and operations, referred to as UsPLM. The UsPLM has shared lifecycle management functions that are provided as web services and can be applied to all digital models of UAS devices, software, autonomy functions, and missions. The individual models can be versioned, tracked, and be composed with other compatible models, if needed. The rule and scoring engines embedded in the UsPLM allow building and executing configuration rules, regulation rules, and various machine-learning models. This facilitates modular UAS architecture design so that the UAS has the flexibility to be reconfigured for various mission applications.

A Smart Products Lifecycle Management (sPLM) system that is built upon the smart component data model and the NPD.sup.3 process model, is enabling engineers, data scientists, and other stakeholders to collaborate on a common platform to develop smart products. The sPLM system is validated by applying it to unmanned aircraft systems (UAS) development and operations, referred to as UsPLM. The UsPLM has shared lifecycle management functions that are provided as web services and can be applied to all digital models of UAS devices, software, autonomy functions, and missions. The individual models can be versioned, tracked, and be composed with other compatible models, if needed. The rule and scoring engines embedded in the UsPLM allow building and executing configuration rules, regulation rules, and various machine-learning models. This facilitates modular UAS architecture design so that the UAS has the flexibility to be reconfigured for various mission applications.