Integration Environment Generator for Automated Build Script Creation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual process of determining dependencies between software modules and creating build scripts for deployment packages is labor-intensive, complex, and prone to errors, especially for large applications with many components, during the application development phase.

Innovation Solution

An integration environment generator that converts input files into a unified markup language, validates them against specified rules, identifies dependencies and scheduling information, and generates build scripts, scheduling scripts, and test case scripts using pre-defined templates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual process is used to determine dependencies and create build scripts, then flexibility and control are maintained, but labor intensity and error rate increase

Engineering Contradiction:
Improveerror rateVSAvoidmanual process
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system automatically generates build scripts by traversing the dependency graph and selecting appropriate templates, enabling the system to serve itself without manual intervention. The build script generation process is self-driven through automated dependency analysis and template selection based on module characteristics.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of writing build scripts is replaced by an automated computational system that analyzes dependencies, selects templates, and generates scripts algorithmically. This substitution eliminates human error while maintaining the functional output of build scripts.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If manual build script creation is used, then adaptability to changes is maintained, but time consumption and complexity increase

Engineering Contradiction:
Improvetime consumptionVSAvoidprocess complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The build script generation process is segmented into distinct modular steps: dependency graph construction, module identification, template selection, and script generation. Each step handles a specific aspect of the process, making the overall complex task manageable and automated through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system adapts to changes by dynamically adjusting parameters such as template selection based on module type, dependency relationships, and build configuration. When application components change, the dependency graph is re-traversed and appropriate templates are selected, automatically adapting the build script without manual reconfiguration.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If automated generation is implemented, then efficiency and error reduction are achieved, but system complexity increases

Engineering Contradiction:
ImproveefficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The build script generation system serves multiple functions: it analyzes dependencies, generates build scripts, creates scheduling scripts, and produces test case scripts. This multi-functional approach consolidates several manual processes into a single automated system, improving efficiency while the modular architecture manages the inherent complexity.

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

Solution Approach 2:

The dependency graph serves as an intermediary data structure that bridges the input application components and the output build scripts. This intermediary representation simplifies the transformation process by providing a standardized intermediate form that can be systematically processed through template selection and script generation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8689177B2Integration environment generator
Publication Date: 2014.04.01 ACCENTURE GLOBAL SERVICES LTD
  • US8689177B2 patent drawing
  • US8689177B2 patent drawing
  • US8689177B2 patent drawing

AI summary

An integration environment generator receives an input file and converts the input file into a markup language file. The input file identifies modules for an application to be deployed, dependencies among the modules, test cases for testing the modules, and scheduling information. The integration environment generator receives rules and validates the markup language file against the rules. The rules specify a unified format for including the dependencies of the modules in the input file. The integration environment generator identifies the modules, the dependencies among the modules, and the scheduling information and the test cases from the validated markup language file. The integration environment generator selects a build script template for the identified dependencies, a scheduling script template for the identified scheduling information and a test case script template for the identified test cases and generates a build script, a scheduling script and a test case script from the templates.