Dev-Maintain Landscape Preview Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software release management systems face synchronization challenges between development and production computing systems, leading to software failures, inefficiencies, and increased costs due to version mismatches and incompatible changes.
Innovation Solution
A three-tier computing system landscape is introduced, comprising a development maintenance system, a development preview system, and a production system, where the development preview system is upgraded one release cycle earlier than the others, enabling early validation and maintenance, and a Preview and Maintenance Controller optimizes the upgrade, merge, and transport sequence to synchronize changes effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the development computing system is upgraded to a new release version before the production computing system, then early validation and feature creation for future versions is enabled, but synchronization failures and software failures occur due to version mismatches
Solution Approach 1:
The development computing system is segmented into two separate systems: a first development computing system that runs on the current release version and a second development computing system that runs on the new release version. This segmentation allows each system to operate independently at different versions, enabling early validation in the second system while maintaining stability in the first system and production system.
Solution Approach 2:
The first development computing system acts as an intermediary between the production computing system and the second development computing system. It receives and validates changes from the second system before transporting them to production, serving as a buffer that prevents direct version mismatches and synchronization failures.
2Reliability
If the development computing system and production computing system are upgraded to the same release version simultaneously, then synchronization is maintained, but early validation and maintenance of new features is not possible
Solution Approach 1:
The development computing system is divided into two separate systems operating at different release versions. The second development computing system runs on the new release version to enable early feature validation, while the first development computing system and production system remain synchronized on the current release version.
Solution Approach 2:
The second development computing system performs preliminary validation and testing of changes on the new release version before those changes are transported to the first development computing system and subsequently to production. This preliminary action enables early feature validation while maintaining production stability.
3Device complexity
If a single development computing system is used, then system complexity is reduced, but the ability to perform early validation and maintenance across different release versions is limited
Solution Approach 1:
The single development computing system is segmented into two separate development computing systems, each specialized for different purposes: one for current version maintenance and one for future version development. This segmentation enables multi-version development capability while keeping each individual system relatively simple.
Solution Approach 2:
The two development computing systems together provide universal functionality for both current version maintenance and future version development. Each system has a specific function, but collectively they enable versatile multi-version development and validation capabilities.
Data Source
AI summary
A development maintenance (Dev-Maintain) computing system is upgraded from a release version n to a release version n+1, where a production (Prod) computing system is on the release version n, and a development preview (Dev-Preview) computing system is on the release version n+1. Changes are transported from the Dev-Preview computing system to the Dev-Maintain computing system. Inactive changes transported from the Dev-Preview computing system into the Dev-Maintain computing system are merged to generate merged changes. The merged changes are transported to the Dev-Preview computing system. A release version upgrade is performed to the Prod computing system and to the Dev-Preview computing system. Active changes are transported from the Dev-Maintain computing system to the Prod computing system.