Change Management for Software Structure Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional change management systems fail to track, request, approve, or decline changes to structure objects in previously completed phases of a software life cycle, leading to scope and budget inaccuracies during project progression.
Innovation Solution
A process that locks structure objects against changes in completed phases, allowing for change requests to be approved or denied, and tracks changes through a change document, enabling modifications only via approved requests, ensuring that changes are integrated into previous phases and documented.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If structure objects are locked after a phase is completed, then historical integrity and scope accuracy are maintained, but flexibility to make necessary changes is reduced
Solution Approach 1:
The system performs preliminary action by opening a change request file before allowing modifications to locked structure objects. This preliminary step establishes a formal change management process that enables future modifications while maintaining historical integrity through structured approval workflows.
Solution Approach 2:
The system applies dynamics by transitioning structure objects from a static locked state to a dynamic changeable state through the change request mechanism. Once a change request is approved, the locked structure object becomes temporarily editable, allowing the system to adapt between rigidity and flexibility as needed.
2Adaptability or versatility
If changes to structure objects are allowed in previous phases, then adaptability is improved, but scope and budget accuracy deteriorate
Solution Approach 1:
The system implements feedback by tracking all changes to structure objects through change request files and change documents. This feedback mechanism records what changes were made, when they were approved, and their impact, enabling the system to maintain accurate scope and budget information while allowing necessary modifications.
Solution Approach 2:
The change request file acts as an intermediary between the desire to modify structure objects and the need to maintain scope accuracy. This intermediary document captures and manages changes formally, ensuring that scope and budget calculations remain accurate by tracking the impact of each approved modification.
3Device complexity
If traditional change management systems are used, then simplicity is maintained, but tracking and managing changes in completed phases becomes impossible
Solution Approach 1:
The system creates a copy of the change management process for completed phases by opening change request files that replicate the same approval and tracking mechanisms used during active phases. This copying approach extends change management capability to historical phases without fundamentally redesigning the entire system.
Solution Approach 2:
The system segments the change management process into distinct components: change request files for initiating changes, change documents for tracking modifications, and approval workflows for managing modifications. This segmentation allows the system to handle changes in completed phases through a modular approach that builds on existing simple structures.
Data Source
AI summary
A structure object is locked to prevent changes to the structure object in previous phases of a software life cycle. When a request to change the structure object in a previous phase is received, a change request file is opened. The changed request is approved or denied based at least in part on the previous phase. If the changes request is approved, a document is generated for the change request. Any changes made to the structure object are integrated into the previous phase of the structure object and are also stored in the document. If the change request is denied, the change request file is closed.