Integrated Software Delivery System for Lifecycle Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software delivery methods are limited to specific sub-processes and fail to manage the entire life cycle of software products from development to production, leading to poor quality products, delays, and cost overruns due to the lack of an end-to-end integrated management system that can handle the evolution of software components and their dependencies across multiple platforms and environments.

Innovation Solution

An integrated data processing system that includes a central repository for storing software components, sub-systems for identifying, creating, and distributing software packages, and managing changes, along with a tracking sub-system to capture and integrate information across the software delivery process, ensuring the integrity and consistency of software products throughout their life cycle.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software delivery management is implemented to control evolution and implementation of changes, then reliability of software deployment is improved, but device complexity increases due to the need for integrated management systems

Engineering Contradiction:
Improvesoftware deployment reliabilityVSAvoidmanagement system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the software delivery process into distinct functional modules: configuration management module, change management module, problem management module, and deployment module. Each module handles specific aspects of software delivery independently, reducing overall system complexity while maintaining comprehensive control through their coordinated interaction.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a centralized software library as an intermediary component that stores and manages software components, configurations, and metadata. This intermediary serves as a common interface between different management modules and target systems, simplifying the complexity of direct interactions between multiple management functions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If comprehensive end-to-end software delivery process is implemented, then manufacturing precision of software products is improved, but loss of time increases due to the extensive management process

Engineering Contradiction:
Improvesoftware product qualityVSAvoiddelivery process time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring software components, dependencies, and deployment parameters in the software library before actual deployment. Configuration files and metadata are prepared in advance, allowing rapid deployment execution without time-consuming setup during the actual delivery process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The deployment system implements self-service capabilities through automated configuration generation, dependency resolution, and deployment execution. The system automatically retrieves required components from the software library, resolves dependencies, and executes deployments without requiring extensive manual intervention, thereby reducing delivery time while maintaining precision.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If centralized management of software components is implemented, then ease of operation is improved, but device complexity increases due to integration requirements

Engineering Contradiction:
Improvesoftware delivery operationVSAvoidintegrated system integration
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The software library serves as a universal platform that handles multiple functions: storing software components, managing configurations, tracking versions, resolving dependencies, and facilitating deployments. This multi-functional design consolidates what would otherwise require separate systems, improving ease of operation while managing integration complexity through a single unified interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7735080B2Integrated system and method for the management of a complete end-to-end software delivery process
Publication Date: 2010.06.08 SERVICENOW INC
  • US7735080B2 patent drawing
  • US7735080B2 patent drawing
  • US7735080B2 patent drawing

AI summary

A software delivery process including sub-processes of configuration management and version control, change and problem management, building, packaging, and distribution and installation. The process is implemented by an integrated management system that includes a configuration management sub-system, a change and problem management sub-system, a building sub-system, a packaging sub-system, a distribution sub-system, and a tracking sub-system. The subsystems are integrated in order to manage the software along its whole life cycle, from development to installation in production. The tracking sub-system captures and integrates information about the status of the delivery from the other sub-systems along all steps of the process.