Change Management Framework Using Executable Semantics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current change management approaches fail to systematically address the complex and far-reaching impacts of disruptive technologies like blockchain and artificial intelligence on organizational systems, particularly in ensuring non-functional properties such as security and safety, which are delicate and often lead to avoidance of changes due to the risk of invalidating software functionality.
Innovation Solution
The method involves representing proposed changes in a high-level format using Problem-Oriented Engineering (POE-Δ) notation, mapping them to low-level executable semantic models like Hybrid Communicating Sequential Processes (HCSP) language, and validating these changes through simulation to ensure they meet identified needs without requiring additional changes, with a focus on security and safety aspects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full characterization of external behavior through mathematical modelling and mathematical proof is applied to establish non-functional properties like security and safety, then the reliability and security of the system is improved, but the complexity of change management increases and changes are often avoided
Solution Approach 1:
The patent segments the change management process into distinct phases: identifying unsatisfied needs, representing proposed changes at high level, mapping to low-level executable semantics, validating changes, and handling additional changes. This segmentation reduces the complexity of managing changes by breaking down the overall process into manageable steps, each with specific objectives and deliverables.
Solution Approach 2:
The patent applies preliminary action by validating proposed changes against identified needs and mathematical models before implementing them. The system performs change impact analysis and validation in advance to ensure that changes meet security and safety requirements, preventing problematic changes from being implemented and reducing the need for costly rework.
2Adaptability or versatility
If changes are made to satisfy new needs or requirements, then the adaptability and functionality of the system is improved, but the risk of invalidating existing software functionality increases
Solution Approach 1:
The system performs preliminary validation by mapping proposed changes to low-level executable semantics and validating them against identified needs before implementation. This preliminary action ensures that changes are verified for correctness and do not invalidate existing functionality, allowing the system to adapt to new needs while maintaining reliability.
Solution Approach 2:
The patent implements feedback mechanisms where the validation process provides feedback on whether proposed changes satisfy identified needs and maintain software functionality. The system identifies additional changes required and cascades them through the system, providing continuous feedback to ensure changes are correct and complete before implementation.
3Reliability
If validation processes are performed to ensure changes meet security and safety standards, then the reliability is improved, but the time required for change management increases
Solution Approach 1:
The patent performs validation as a preliminary action before change implementation, using mathematical models and executable semantics to verify changes in advance. This preliminary validation prevents time-consuming rework and ensures changes are correct the first time, actually reducing overall change management time despite the added validation step.
Solution Approach 2:
The patent replaces manual, mechanical change validation processes with automated validation using mathematical models and executable semantics. The system automatically maps high-level change representations to low-level semantics and validates them against identified needs, eliminating time-consuming manual verification and accelerating the change management process.
Data Source
AI summary
A method of managing change in a complex system begins with identifying an unsatisfied need to be met by the system. To satisfy the need a proposed change to the system to satisfy the need is represented a high-level representation of the proposed change. The high-level representation is mapped to a low-level executable semantic model, which is used to validate the proposed change and ensure the proposed change meets the identified and does not require additional changes to the system. On a condition that the validating steps determines that additional changes are required the additional changes are represented in the high-level representation of the system; the high-level change is mapped to the low-level executable semantic model and the additional changes are re-validated.