Unified SOA Repository Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current management of web services in Service-Oriented Architecture (SOA) is disjointed across development, testing, and production stages, failing to integrate functional and non-functional requirements effectively, leading to inconsistent enforcement of policies and requirements throughout the lifecycle.
Innovation Solution
An integrated SOA repository is implemented to store and manage both functional and non-functional requirements across the lifecycle stages, enabling enforcement of policies and ensuring compliance through development, testing, and production run-time stages by using a unified database system that captures and enforces artifacts like policies, usage plans, and standards compliance rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web services are developed by different teams at different times, then service reusability and flexibility are improved, but management consistency and control are worsened
Solution Approach 1:
The patent segments the service lifecycle management into distinct phases (development, testing, production) with stage-specific policies and artifacts. Each phase has its own management controls and approval processes, allowing different teams to work independently while maintaining overall consistency through stage-gate transitions governed by a process manager.
Solution Approach 2:
The process manager acts as an intermediary between multiple development teams and the central repository. This intermediary enforces lifecycle policies, validates artifacts before stage transitions, and ensures that services meet organizational standards before deployment, thereby maintaining management consistency without restricting team autonomy.
2Productivity
If management is separated across development-testing and production stages, then specialization and efficiency are improved, but integration and consistency are worsened
Solution Approach 1:
The patent implements a universal lifecycle management framework that applies the same policy enforcement mechanisms and validation rules across all stages (development, testing, production). The process manager and repository structure remain consistent throughout, ensuring that the same reliability controls are applied universally regardless of the development phase, thereby maintaining policy enforcement consistency while allowing stage-specific optimizations.
3Loss of information
If a unified repository stores all lifecycle artifacts, then information integration and traceability are improved, but system complexity and implementation difficulty are worsened
Solution Approach 1:
The repository is segmented into stage-specific storage areas (development artifacts, testing artifacts, production artifacts) with distinct schemas and access controls. Each stage has its own artifact types and validation rules, reducing the complexity of managing a unified repository by organizing information hierarchically while maintaining traceability through the lifecycle.
Solution Approach 2:
The patent adds a temporal dimension to the repository structure by organizing artifacts according to lifecycle stages. This dimensional organization allows the system to maintain comprehensive information integration across all stages while managing complexity through stage-based abstraction, where each stage presents a simplified view of the artifacts relevant to that phase.
Data Source
AI summary
A method and appertaining system provide that an integrated Service Oriented Architecture (SOA) repository stores functional and non-functional requirements and associated data and results of associated with software services across the software lifecycle, thereby permitting access at a common point or in a common way by a user to all relevant information about the software service at least during the development, testing, and run-time stages of the software service. Thus, all design documents, testing requirements and results, and run-time policies and contracts can be provided in a common location to facilitate development in the service oriented architecture.