Start Verifying and validating requirements

Verifying and validating requirements

While the concepts and relationships represent an enumeration of the architecture, the stakeholders' perspectives approaches from a different viewpoint: how the architecture meets the goals and requirements.

For the purpose of this Working Group and this architecture, and without prejudice toward other definitions, we will use the following definition: [Definition: A Web service is a software system designed to support interoperable machine-to-machine interaction over a network.

It has an interface described in a machine-processable format (specifically WSDL).

To illustrate this distinction, you might implement a particular Web service using one agent one day (perhaps written in one programming language), and a different agent the next day (perhaps written in a different programming language) with the same functionality.

However, since these terms are ambiguous -- sometimes referring to the agent and sometimes to the person or organization that owns the agent -- this document prefers the terms In order for this message exchange to be successful, the requester entity and the provider entity must first agree on both the semantics and the mechanics of the message exchange.

A list of remaining open issues is included in 4 Conclusions.

Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page.

This publication as a Working Group Note coincides with the end of the Working Group's charter period, and represents the culmination of the group's work.