Usage Scenario: Title

This is a template for recording a "usage scenario", which may involve one or more "use cases". This template has been adopted for use in collecting scenarios and use cases for Semantic Web Services. It was developed initially by members of the DAML-S Coalition, and then further refined by the architecture and language committees of the Semantic Web Services Initiative (SWSI). It draws on work by Derek Coleman of HP.

The purpose of this template is simply to facilitate the collection of usage scenarios, and to provide some structure for browsing and comparing them. In adopting this template, we particularly do not want to impede the contribution of scenarios. Therefore, all fields may be regarded as optional, and they made be filled in as (in)formally as you wish.

Please feel free to embed or link to other forms of documentation (e.g. UML diagrams), publications, code samples, etc. The objective is just to get in the most relevant and useful information for consideration in the design of architecture and languages for Semantic Web Services.



Domain: [Application domain; e.g. selling books.]


[Brief, high-level overview of the scenario.]


[Overview/describe/discuss issues relevant to this scenario. Why is the scenario of interest?]

Actors & Goals

[Enumerate entities that play a role in the scenario, and their goals. These can include human users and organizations as well as software agents. Specify types of actors (e.g. user, software client, service provider, middle agent) with distinguishing names for each.]

Stakeholders & Interests

[Enumerate stakeholders and their interests in the scenario (humans/organizations/agents not mentioned above).]

URL(s) or Other References

[For further information.]

Modification History

Use Case: Title

[There may be any number of use cases in a usage scenario.]


[List/describe/discuss the particular issues illustrated by this use case.]


[Such things as performance requirements, e.g. fault tolerance, frequency, reliability.]


[Specific actors used in this use case (should be a subset of  Scenario Actors).


[Goals of actors initiating processes; knowledge required to specify process inputs.]


[Conditions that must be true for successful use case execution and termination.]


[Describe the steps of this use case, and specifying the actors/roles responsible for invoking and executing each step. Include, if relevant,information about process flows, protocols, messages, pre-conditions, post-conditions, errors, etc. associated with the steps. Describe interesting variants, where possible.]


[Known issues not explicitly covered above (e.g., error handling).]

Ontologies and Semantic Descriptions

[Describe the kinds of  ontologies and semantic descriptions that are required, rather than specific implementations.]

Reasoning Techniques Required

[Specific kinds of  reasoning required, where known (e.g., planning, data collection or analysis, classification, similarity matching, rule-based inference).]