Multi-Layer Software Framework for Group System Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current approaches for configuration and release management of group application systems software, such as those in large banking entities like HSBC, face challenges in efficiently deploying and managing software changes across multiple strategic business units (SBUs) due to the complexity and overhead of maintaining a complete copy of the software system, with much of the software being common across units requiring only minor customization.
Innovation Solution
A framework that provides a global structure and set of tools and processes allowing a single base of program code and related components to be managed and modified, enabling flexible incorporation of software changes while maintaining consistent code release versions across all business units, utilizing a multi-layer architecture with global, base, regional, custom, environment, and local layers to segregate globally-applicable and SBU-specific software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a complete copy of the software system is deployed for each SBU, then each business unit can operate independently with full functionality, but the overhead and complexity of managing and deploying software changes increases significantly
Solution Approach 1:
The software system is segmented into a common core component and SBU-specific customization layers. The framework divides the software architecture into shared infrastructure (handled globally) and localizable components (handled locally), allowing independent deployment of each segment without requiring complete system copies for each SBU.
Solution Approach 2:
The framework creates a universal software core that serves multiple SBUs simultaneously. This common platform provides base functionality for all business units while allowing customization through configuration files and localized components, eliminating the need for separate complete system deployments.
2Stability of the object's composition
If software changes are deployed globally to all SBUs, then consistency across the organization is maintained, but the time required to implement changes and the speed-to-market decreases
Solution Approach 1:
The framework enables selective application of software changes with different update strategies for different SBUs. Critical security patches can be deployed globally immediately, while non-critical enhancements can be rolled out selectively to specific SBUs based on their readiness, allowing parallel deployment at different paces.
Solution Approach 2:
The deployment framework provides dynamic control over software update propagation. Administrators can configure update policies that automatically adjust the scope and timing of deployments based on SBU-specific factors, enabling flexible rollback capabilities and staged rollouts without compromising overall system consistency.
3Adaptability or versatility
If extensive customization is allowed for each SBU, then local needs are met, but the difficulty of maintaining and updating the software system increases
Solution Approach 1:
The framework extracts customization capabilities from the core software and places them in separate configuration files and localized components. This separation allows SBUs to customize their local copies without modifying the protected core code, making maintenance and updates to the core system straightforward while preserving local adaptations.
Solution Approach 2:
The framework uses template-based copying where a standardized software core is replicated across SBUs with automated configuration of local parameters. This copying approach ensures that all SBUs start with a maintained, tested base while local customizations are applied through configuration rather than code modification, simplifying future updates.
4Adaptability or versatility
If manual processes are used for software configuration and deployment, then flexibility in handling complex scenarios is maintained, but productivity and efficiency decrease
Solution Approach 1:
The framework introduces an automated intermediary layer that sits between the software core and SBU deployments. This intermediary handles configuration management, dependency resolution, and deployment orchestration automatically, reducing the need for manual intervention while maintaining the ability to handle complex deployment scenarios through scripted policies.
Data Source
AI summary
A global framework multi-layer computer based architecture is provided. The global framework may include a single set of libraries that contains common source code applicable to substantially all business processing systems using the global framework. The global framework may include individual source code libraries that contain modifications specific to a business processing system to meet the local needs of that business processing system. The business processing systems may execute the custom and base libraries through concatenation of the libraries.