Enterprise Platform for Parallel Software Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software development, teams face delays and inefficiencies due to dependencies between team members, particularly in understanding the software architecture and relationships between components, leading to idle time and reduced team performance.

Innovation Solution

A common platform that fetches contract information for existing applications, enabling multiple users to work independently by providing this information to developers and testers, allowing them to create test cases and develop source code parallelly, and integrating the new feature into the existing application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software professionals work in sequential phases with dependencies on each other, then each professional can focus on their specific task, but the waiting time increases and team productivity decreases

Engineering Contradiction:
ImproveTask focus and specializationVSAvoidTeam productivity
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system performs preliminary actions by automatically generating contract information, API documentation, and test case templates before developers and testers begin their work. This allows team members to start their tasks immediately without waiting for manual documentation or setup from other team members, thus maintaining task focus while eliminating waiting time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary system that acts as a mediator between different software professionals. This system automatically generates and distributes contract information, API specifications, and test data, eliminating the need for direct handovers and dependencies between developers, testers, and other team members, thereby enabling parallel work while maintaining task specialization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Stability of the object's composition

If software professionals wait for input from other professionals before resuming work, then dependency management is maintained, but the waiting time becomes excessively long and re-collecting project information becomes difficult

Engineering Contradiction:
ImproveDependency managementVSAvoidWaiting time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system enables self-service by automatically generating and providing contract information, API documentation, and test case templates to developers and testers without requiring them to wait for or request information from other team members. The system serves itself by maintaining up-to-date project information and making it readily available, thus managing dependencies while eliminating waiting time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-generating and storing contract information, API specifications, and test data before team members need them. This ensures that when developers or testers resume work, all necessary information is already prepared and available, maintaining dependency management while eliminating the need to wait or re-collect information.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If software professionals are experts in specific technologies, then they can write high-quality code in their specialized areas, but they cannot work on projects using different technologies which reduces team flexibility

Engineering Contradiction:
ImproveCode qualityVSAvoidTeam flexibility
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The system provides universal contract information and API documentation that can be used across different technologies and programming languages. This allows specialists in one technology to work on projects requiring different technologies by providing them with technology-agnostic contract specifications, thereby maintaining code quality through specialized expertise while enabling team flexibility through universal interfaces and documentation.

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

4Reliability

If team members need to understand design patterns and relationships between different modules across different technologies, then system integration is improved, but the time and effort required increases significantly

Engineering Contradiction:
ImproveSystem integrationVSAvoidUnderstanding time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system acts as an intermediary that automatically generates and provides comprehensive contract information, API documentation, and relationship mappings between different modules and technologies. This eliminates the need for team members to manually study and understand complex system relationships, thereby maintaining reliable system integration while significantly reducing the time and effort required to understand design patterns and module relationships.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10204319B2Enterprise system and method for facilitating common platform for multiple-users working parallelly in enterprise environment
Publication Date: 2019.02.12 WIPRO LTD
  • US10204319B2 patent drawing
  • US10204319B2 patent drawing
  • US10204319B2 patent drawing

AI summary

Systems and methods for facilitating a common platform for multiple users working parallelly in an enterprise environment are described. When a request is received along with requirements for adding a new feature in an existing application, the system fetches contract information associated with the existing application. The system further provides the contract information to a first user and a second user. Post receiving the contract information and requirements, the first user creates one or more test cases and the second user develops a source code for the feature to be added into the existing application. The system executes the one or more test cases for testing the validity of the source code and further integrates the source code into the existing application.