Application Lifecycle Template Artifact Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, managing dependencies across different stages of the software development lifecycle is complex, making it challenging to accurately and efficiently manage application lifecycle operations.

Innovation Solution

Assigning workload templates to each phase of the application lifecycle with pointers to previous templates and artifacts, and propagating changes between phases to automatically manage lifecycle operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If templates are assigned to each phase of the application lifecycle with pointers to artifacts, then the accuracy of dependency management is improved, but the device complexity increases

Engineering Contradiction:
Improveaccuracy of dependency managementVSAvoidcomplexity of template management system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent divides the application lifecycle into distinct phases (development, testing, deployment, maintenance) with separate templates for each phase. Each template is segmented to contain specific artifact pointers relevant to that phase, making the overall complex system manageable through modular organization. This segmentation allows accurate tracking of dependencies without requiring a monolithic complex structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces templates as intermediary objects that mediate between artifacts and phases. Templates act as intermediaries containing pointers to artifacts, enabling indirect management and tracking of dependencies. This intermediary layer simplifies the relationship management between phases and artifacts while maintaining accuracy in dependency tracking.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If changes in artifacts are propagated to corresponding templates automatically, then the productivity of lifecycle operations is improved, but the device complexity increases

Engineering Contradiction:
Improveefficiency of lifecycle operationsVSAvoidcomplexity of change propagation mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements automatic change propagation as a feedback mechanism where changes in artifacts trigger automatic updates to corresponding templates. This feedback loop ensures that template definitions remain synchronized with actual artifact states without manual intervention, improving productivity while the automation handles the complexity of tracking and propagating changes across the lifecycle.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service through automatic change propagation where the template management system automatically detects, tracks, and propagates changes without requiring external intervention. This self-service capability improves operational efficiency by eliminating manual update processes while the system's internal mechanisms manage the complexity of change propagation.

Inventive Principle:
Principle #25Self-service

3Reliability

If references to previous templates are provided in each template, then the reliability of lifecycle management is improved, but the loss of information increases

Engineering Contradiction:
Improvereliability of lifecycle managementVSAvoidinformation loss in template references
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent uses copying by providing references/pointers to previous templates rather than duplicating their entire content. Each template contains references to artifacts and previous templates, creating a linked structure that maintains reliability through traceability while avoiding information redundancy. This copying approach preserves essential reference information without duplicating unnecessary data.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8843889B2Managing application template artifacts in a networked computing environment
Publication Date: 2014.09.23 KYNDRYL INC
  • US8843889B2 patent drawing
  • US8843889B2 patent drawing
  • US8843889B2 patent drawing

AI summary

Embodiments of the present invention provide an approach for managing application template artifacts throughout an application's lifecycle in a networked computing environment (e.g., a cloud computing environment). In a typical embodiment, a workload template is assigned to each phase of a set of successive phases of the application's lifecycle. Each template typically refers to a template in a preceding phase of the lifecycle. Moreover, the templates may contain pointers to artifacts used in the phases assigned thereto. Any changes occurring in the artifacts/phases are propagated to the corresponding templates so as to automatically manage application lifecycle operations.