Structured methodology and design patterns for web services

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, wherein each Use Case models a particular business scenario for the Web Service, and wherein each design pattern models a structure that is applicable under certain conditions;
• means for generating a high-level architecture for the Web Service in accordance with the one or more design patterns, wherein said means for generating the high-level architecture identifies two or more entities of the Web Service and relationships and interactions among the two or more entities;
• and
• means for generating a logical architecture for the Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more design patterns, wherein said means for generating the logical architecture identifies two or more logical components of the Web Service and relationships among the two or more logical components according to two or more tiers, and wherein the generated logical architecture comprises two or more layers.

A method, comprising:

• performing by one or more computers:
• generating a vendor-independent Web Service architecture comprising a plurality of heterogeneous components in accordance with one or more design patterns, wherein each design pattern models a particular structure that is applicable in a Web Service under certain conditions, and wherein said generating a vendor-independent Web Services architecture comprises:
• generating one or more Use Cases for the Web Service in accordance with the one or more design patterns, wherein each Use Case models a particular business scenario for the Web Service, and wherein said generating one or more Use Cases comprises:
• obtaining requirements, including user requirements and technical requirements, for the Web Service;
• and
• encapsulating the obtained requirements for the Web Service into the one or more Use Cases for the Web Service;
• generating a high-level architecture for the Web Service in accordance with the one or more design patterns, wherein said generating the high-level architecture comprises identifying two or more entities of the Web Service and relationships and interactions among the two or more entities;
• and
• generating a logical architecture for the Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more design patterns, wherein said generating the logical architecture comprises identifying two or more logical components of the Web Service and relationships among the two or more logical components according to two or more tiers, and wherein the logical architecture comprises two or more layers;
• and
• implementing the Web Service according to the generated Web Service architecture.

A non-transitory computer-accessible storage medium storing program instructions, wherein the program instructions are computer-executable to implement:

• generating a vendor-independent Web Service architecture for implementing a Web Service, wherein the Web Service architecture comprises a plurality of heterogeneous components in accordance with one or more design patterns, wherein each design pattern models a particular structure that is applicable in a Web Service under certain conditions, and wherein, in said generating a vendor-independent Web Services architecture, the program instructions are computer-executable to implement:
• generating one or more Use Cases for the Web Service in accordance with the one or more design patterns, wherein each Use Case models a particular business scenario for the Web Service, and wherein, in said generating one or more Use Cases, the program instructions are computer-executable to implement:
• obtaining requirements, including user requirements and technical requirements, for the Web Service;
• and
• encapsulating the obtained requirements for the Web Service into the one or more Use Cases for the Web Service;
• generating a high-level architecture for the Web Service in accordance with the one or more design patterns, wherein, in said generating the high-level architecture, the program instructions are computer-executable to implement identifying two or more entities of the Web Service and relationships and interactions among the two or more entities;
• generating a logical architecture for the Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more design patterns, wherein, in said generating the logical architecture, the program instructions are computer-executable to implement identifying two or more logical components of the Web Service and relationships among the two or more logical components according to two or more tiers, and wherein the logical architecture comprises two or more layers.

A method for designing and implementing a vendor-independent Web Service architecture, comprising:

• performing by one or more computers:
• identifying one or more logical components of the Web Service architecture according to one or more use case requirements for a Web Service, wherein each use case requirement specifies a particular business scenario for the Web Service;
• translating the one or more use case requirements and one or more technical requirements for the Web Service to determine a plurality of heterogeneous Web Service components for the Web Service architecture;
• 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 for the Web Service architecture according to one or more architecture principles for each of the one or more tiers and the one or more layers of the Web Service architecture;
• applying one or more Web Services design patterns to the Web Service architecture, wherein each design pattern models a particular structure that is applicable to the Web Service;
• implementing a Web Service according to the Web Service architecture;
• and
• assessing quality of services provided by the Web Service after said implementing the Web Service.

A method for designing and implementing a vendor-independent Web Service architecture, comprising:

• performing by one or more computers:
• identifying and building one or more security components according to one or more use case requirements for a Web Service, wherein each use case requirement specifies a particular business scenario for the 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 for the Web Service architecture, security policy and strategy for the Web Service architecture, 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, wherein each design pattern models a particular structure that is applicable to the Web Service;
• 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 the Web Service.