Dummy Service Substitution for Parallel Software Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Service Oriented Architecture (SOA), the development of software modules is often delayed due to the unavailability of the service layer, as complex services require significant time to develop and resource-intensive computation, making the Quality Assurance process less cost-effective and hindering parallel development of software modules and service layers.
Innovation Solution
A computerized apparatus and method that allows for the development of software modules using dummy services, which can be adapted and replaced with actual services, enabling parallel development by providing a dummy service obtainer, adaptation module, and service replacement module to map and replace dummy services with actual or additional dummy services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the service layer is developed completely before software module development, then the quality of software module can be examined properly, but the development time is significantly extended
Solution Approach 1:
The patent creates dummy services in advance that mimic the interface and behavior of actual services. These dummy services are prepared beforehand to allow software module development to proceed without waiting for the complete service layer, thus performing the necessary service preparation action in advance rather than blocking the entire development process.
Solution Approach 2:
The patent introduces dummy services as intermediary components between the software module and the actual service layer. These dummy services act as mediators that provide the necessary interface compatibility and basic functionality during development, allowing parallel development while maintaining the ability to examine software quality through controlled interactions.
2Adaptability or versatility
If generic services with many fields are used to fit various entities, then service reusability is improved, but the complexity of field mapping increases
Solution Approach 1:
The patent applies local quality by allowing different software modules to use only the specific fields and capabilities they need from the generic service, rather than requiring all fields. Each module can selectively access relevant portions of the service interface, reducing the perceived complexity while maintaining overall service reusability.
Solution Approach 2:
The patent performs field mapping in advance during the service definition phase, creating a predefined mapping between generic service fields and specific entity requirements. This preliminary action eliminates the need for developers to perform complex field mapping during implementation, as the mappings are already established and documented.
3Reliability
If complex services are operated multiple times for Quality Assurance, then thorough testing is achieved, but resource consumption and computation time increase
Solution Approach 1:
The patent creates dummy services that are simplified copies of the actual complex services. These copies replicate the essential interface and behavior needed for testing purposes but with reduced computational complexity and resource requirements, allowing multiple QA operations without the high cost of operating full complex services.
Solution Approach 2:
The patent employs dummy services as lightweight, disposable testing artifacts that can be created and discarded easily. These services require minimal resources to operate and can be rapidly instantiated for testing scenarios, making the QA process more cost-effective compared to using full complex services for every test operation.
Data Source
AI summary
A method and apparatus for developing a computer program utilizing services that may not be available during development. A dummy service providing a naïve implementation of the service that is to be provided by the services is obtained or created. The computer program is modified such that it utilizes the dummy service. After an actual service is available, the computer program is modified once more to utilize the actual service instead of the dummy service.