Structured methodology and design patterns for web services
First Claim
1. A Web Service system, comprising:
- a service provider configured to provide one or more services on the Web Service system;
one or more service requesters configured to access the one or more services from the service provider via a network;
wherein the Web Service system is configured according to a vendor-independent architecture framework for designing Web Services comprising a plurality of heterogeneous components in accordance with a structured methodology and one or more design patterns.
2 Assignments
0 Petitions
Accused Products
Abstract
System and method for designing and implementing Web Services according to a structured methodology and design patterns. Embodiments may incorporate a structured methodology, best practices and design patterns that address reliability, availability and scalability of Web Services architecture. Embodiments may provide mechanisms for integrating heterogeneous technology components into Web Services. Embodiments may provide a vendor-independent Web Services architecture framework and reusable Web Services design patterns, which may be used in creating end-to-end solutions based on past experience and best practices. Embodiments may include design patterns and best practices for delivering Web Services solutions with Quality of Services. One embodiment may provide a Business-to-Business Integration (B2Bi) integration framework for Web Services. Embodiments may provide a Web Security framework and design patterns for designing end-to-end Web Services security.
1324 Citations
80 Claims
-
1. A Web Service system, comprising:
-
a service provider configured to provide one or more services on the Web Service system;
one or more service requesters configured to access the one or more services from the service provider via a network;
wherein the Web Service system is configured according to a vendor-independent architecture framework for designing Web Services comprising a plurality of heterogeneous components in accordance with a structured methodology and one or more design patterns. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A system for generating a vendor-independent Web Service architecture comprising a plurality of heterogeneous components, comprising:
-
means for generating one or more Use Cases for the Web Service in accordance with one or more design patterns;
means for generating a high-level architecture for the Web Service and in accordance with the one or more design patterns, wherein the high-level architecture identifies two or more entities of the Web Service and the relationships and interactions among the entities; and
means for generating a logical architecture for the Web Service according to the use case scenarios and in accordance with the one or more design patterns, wherein the logical architecture identifies two or more logical components of the Web Service and the relationship among the logical components, and wherein the logical architecture comprises two or more layers. - View Dependent Claims (19)
-
-
20. A method, comprising:
-
generating a vendor-independent Web Service architecture comprising a plurality of heterogeneous components in accordance with one or more design patterns, wherein said generating a vendor-independent Web Services architecture comprises;
generating one or more Use Cases for the Web Service;
generating a high-level architecture for the Web Service, wherein the high-level architecture identifies two or more entities of the Web Service and the relationships and interactions among the entities;
generating a logical architecture for the Web Service according to the use case scenarios, wherein the logical architecture identifies two or more logical components of the Web Service and the relationship among the logical components, and wherein the logical architecture comprises two or more layers; and
implementing the Web Service according to the Web Service architecture. - View Dependent Claims (21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37)
-
-
38. A computer-accessible medium comprising program instructions, wherein the program instructions are configured to implement:
-
generating a vendor-independent Web Service architecture comprising a plurality of heterogeneous components in accordance with one or more design patterns, wherein said generating a vendor-independent Web Services architecture comprises;
generating one or more Use Cases for the Web Service;
generating a high-level architecture for the Web Service, wherein the high-level architecture identifies two or more entities of the Web Service and the relationships and interactions among the entities;
generating a logical architecture for the Web Service according to the use case scenarios, wherein the logical architecture identifies two or more logical components of the Web Service and the relationship among the logical components, and wherein the logical architecture comprises two or more layers; and
implementing the Web Service according to the Web Service architecture. - View Dependent Claims (39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55)
-
-
56. A method for designing and implementing a vendor-independent Web Service architecture, comprising:
-
identifying one or more logical components of the Web Service architecture according to one or more Use Case requirements for a Web Service;
translating the one or more use case requirements and one or more technical constraints to determine a plurality of heterogeneous Web Service components;
categorizing the Web Service components according to a Web Service architecture framework;
organizing the Web Service components according to two or more tiers and two or more layers of the Web Service architecture;
modifying one or more software components according to one or more architecture principles for each of the one or more tiers and the one or more layers;
applying one or more Web Services design patterns to the Web Service architecture where appropriate;
implementing a Web Service according to the Web Service architecture; and
assessing the quality of services of the Web Service after said implementing. - View Dependent Claims (57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69)
-
-
70. A method for designing and implementing a vendor-independent Web Service architecture, comprising:
-
identifying and building one or more security components according to one or more Use Case requirements for a Web Service;
identifying one or more Web Service objects of the Web Service architecture to be protected;
defining an object relationship for security protection in the Web Service architecture;
identifying one or more associated trust domains, security policy and strategy, and one or more threat profiles for the Web Service architecture;
determining one or more protection schemes and measures for the Web Services objects;
applying one or more Web Services design patterns to the Web Service architecture where appropriate;
implementing a Web Service according to the Web Service architecture; and
assessing security levels of the Web Service according to two or more tiers of the Web Service architecture after said implementing. - View Dependent Claims (71, 72, 73, 74, 75, 76, 77, 78, 79, 80)
-
Specification