Software Deployment Risk Assessment Method

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large software deployments, such as enterprise resource planning (ERP) systems, often fail due to unaddressed risks during the planning and launch phases, leading to increased costs and loss of goodwill for both customers and providers.

Innovation Solution

A method for deploying software based on a calculated deployment risk level, which assesses configuration parameters like IT personnel credentials, hardware specifications, and estimated load to determine if the deployment risk is below a threshold, authorizing deployment only when risks are mitigated, and enabling features incrementally as risks are reduced.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If software deployment proceeds without rigorous risk assessment, then deployment speed is improved, but deployment reliability deteriorates

Engineering Contradiction:
Improvedeployment speedVSAvoiddeployment reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system performs preliminary risk assessment and validation checks before deployment authorization is granted. Configuration parameters are evaluated upfront to identify potential risks, and the system determines whether risks are acceptable before allowing deployment to proceed, thus ensuring reliability without sacrificing deployment speed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback on deployment risk levels by analyzing configuration parameters and comparing them against predefined risk criteria. This feedback mechanism allows organizations to understand their risk profile and make informed decisions about whether to proceed with deployment or address identified risks first

Inventive Principle:
Principle #23Feedback

2Reliability

If deployment risk assessment is implemented, then deployment reliability is improved, but deployment complexity increases

Engineering Contradiction:
Improvedeployment reliabilityVSAvoiddeployment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically assesses deployment risks by analyzing configuration parameters provided by the organization. Rather than requiring manual risk assessment by consultants or technical staff, the system performs self-service evaluation, reducing the complexity burden on users while maintaining high deployment reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system evaluates deployment risks by analyzing changes in configuration parameters against predefined risk criteria. By focusing on parameter analysis rather than comprehensive system inspection, the approach manages complexity while maintaining reliable risk assessment

Inventive Principle:
Principle #35Parameter changes

3Loss of energy

If deployment risks are not addressed, then deployment cost is reduced, but loss increases

Engineering Contradiction:
Improvedeployment costVSAvoiddeployment loss
Core Design Contradiction:
Loss of energyVSObject-generated harmful factors

Solution Approach 1:

The system takes preliminary anti-action by identifying and flagging deployment risks before they can cause harm. By detecting potential issues in advance through configuration parameter analysis and providing feedback on risk levels, the system prevents costly deployment failures and associated losses while managing costs through targeted rather than comprehensive risk mitigation

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS8046755B2Deploying software based on a calculated deployment risk level
Publication Date: 2011.10.25 SAP SE
  • US8046755B2 patent drawing
  • US8046755B2 patent drawing
  • US8046755B2 patent drawing

AI summary

A computer-implemented method may include receiving first data that includes one or more configuration parameters that characterize an intended deployment of software and a target computer system on which the software is to be deployed. The computer-implemented method may further include calculating a deployment risk level based on the first data, determining whether the calculated deployment risk level is less than a threshold risk level, and transmitting second data to target computer system authorizing deployment of the software if the deployment risk level is less than the threshold risk level. In some implementations, the software is enterprise software. The one or more configuration parameters may include hardware specifications of the target computer system, and the calculated deployment risk level may be based on threshold recommended hardware specifications of the target computer for running the software to be deployed.