Automated Software Transport Task Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for servicing complex software systems like SAP R/3 are time-consuming and prone to errors, particularly in planning and executing changes across multiple interconnected logical systems, which can lead to costly workflow disruptions and data corruption.
Innovation Solution
An automated method for generating low-level operational tasks from high-level operational tasks in a software development system, using system roles and transport tracks to define routes through the system landscape, thereby streamlining the process of routing software changes across interconnected logical systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual methods are used for planning and executing software changes across multiple interconnected logical systems, then operators can control and approve each change, but the process becomes time-consuming and prone to errors
Solution Approach 1:
The system performs self-service by automatically analyzing the system landscape, determining transport paths, and generating low-level operational tasks without requiring manual operator intervention for each step. The automated system serves itself by routing software services through the appropriate logical systems based on pre-defined transport tracks and system roles.
Solution Approach 2:
The patent replaces the mechanical manual process of analyzing system landscapes and creating operational tasks with an automated computer-based system. The mechanical analysis and task generation performed by operators is substituted with automated software that analyzes transport tracks, system roles, and dependencies to generate operational tasks.
2Manufacturing precision
If detailed manual analysis of system landscape and transport paths is performed, then accurate routing of software services is achieved, but the complexity and time required for operation increases
Solution Approach 1:
The system performs preliminary action by pre-defining transport tracks that specify source systems, adjacent interconnected systems, and target systems in a particular order. These transport tracks are established in advance, so when software services need to be transported, the routing path is already determined and does not require complex real-time analysis.
Solution Approach 2:
The patent changes parameters by introducing system roles and system role types as standardized parameters for categorizing logical systems. Instead of analyzing each system's individual characteristics, the automated system uses these role parameters to quickly determine appropriate transport paths and operational tasks.
3Reliability
If multiple logical systems are used for software development, testing, and production, then service integration and error prevention are improved, but the complexity of managing transport across systems increases
Solution Approach 1:
The patent applies universality by creating a standardized transport management system that works across multiple different logical systems (development, quality assurance, productive systems). The same transport tracks, system roles, and automated task generation mechanisms are universally applied regardless of the specific system type, simplifying management across the diverse system landscape.
Solution Approach 2:
The automated operational task generation system acts as an intermediary between the high-level transport requirements and the low-level system-specific operations. It mediates by analyzing transport tracks and system roles to generate appropriate operational tasks for each logical system, reducing the complexity of direct system-to-system management.
Data Source
AI summary
A method for effecting changes in a software system landscape with a plurality of logical software systems that are interconnected by logical transport paths, comprises: providing system role types, each system role being associated with one of a plurality of system role types; providing low level operational tasks associated to system role types; providing a transport track that defines a route through logical systems in a particular order and that specifies one source system, adjacent interconnected systems, and at least one target system; providing high level operational tasks in a software development system that define software changes; generating transport requests for transporting the software changes; and generating a low level operational task list for the logical systems affected by the changes to the software by: analyzing the transport track(s) and the system role types and selecting low level operational tasks associated with the system role types according to the high level operational tasks.