Software Verification System Using Product Definition Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for verifying software installations on computers are incomplete, failing to provide a thorough verification of software versions and components, leading to potential operational issues.

Innovation Solution

A method and system for thoroughly verifying software installations by generating and storing a detailed product definition that includes file, database, and registry information, allowing for confirmation of proper installation by comparing installation properties against a stored definition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current verification methods (database scripts, file version checks) are used, then the verification process is simple and quick, but the verification is incomplete and does not provide thorough verification of software installations

Engineering Contradiction:
Improveverification completenessVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification system segments the software installation verification into multiple independent components: file verification, registry entry verification, database object verification, and configuration file verification. Each component can be verified separately and contributes to the overall verification completeness without requiring a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The verification system is designed to universally verify multiple types of software installation artifacts through a single integrated platform. It can verify files, registry entries, database objects, and configuration files using common verification logic, eliminating the need for separate verification tools for each artifact type.

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

2Measurement precision

If a detailed product definition including multiple installation properties is created, then the verification accuracy is improved, but the time and resources required to create and store the definition increase

Engineering Contradiction:
Improveinstallation verification accuracyVSAvoiddefinition creation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating the product definition during the software installation process itself. The verification definition is created in advance before verification is needed, capturing all installation properties (files, registry entries, database objects) at the moment of installation, thus eliminating the need for manual definition creation later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification system creates a copy of the installation state by capturing and storing the properties of installed software components. This copy (the product definition) is then used for verification purposes, allowing accurate verification without requiring the original installation process to be repeated or manually documented.

Inventive Principle:
Principle #26Copying

3Difficulty of detecting and measuring

If comprehensive installation properties (files, database objects, registry entries) are verified, then the detection of installation issues is improved, but the complexity of the verification process increases

Engineering Contradiction:
Improveinstallation issue detection capabilityVSAvoidverification process complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The verification process is segmented into distinct verification passes, each targeting specific types of installation artifacts. The system can verify files in one pass, registry entries in another, and database objects in a third, allowing comprehensive detection without requiring all verifications to occur simultaneously in a complex monolithic process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses an intermediary product definition structure that mediates between the complex installation state and the verification process. This definition serves as an intermediate representation that simplifies the verification logic by providing a standardized format for comparing expected versus actual installation states across different artifact types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9891903B2Software verification system and methods
Publication Date: 2018.02.13 ALLSCRIPTS SOFTWARE LLC
  • US9891903B2 patent drawing
  • US9891903B2 patent drawing
  • US9891903B2 patent drawing

AI summary

A method for detecting a confirmation of a properly installed software product on a computing device, determining the software product installation properties of the properly installed software product, and storing information relating to at least one or more software product installation properties of the properly installed software product.