William Shaffer This schema describes the content model for WysDoM use case. Waysys LLC Copyright (c) 2007 Waysys LLC This element is the top level element of the use case document. The Use Case Header contains aboout the project, the status of the use case, and the revision history. Use this element to provide an identifier for the use case that can be used in a termref element. Use this element to list the project to which this use case belongs Use this element to name the package that contains this use case. Use this element to note the level of completion of this use case. Use this element to record the revision history of this use case. This element contains the main text of the use case. This element is the name of the use case. The name can be a short phrase that describes the use case. The phrase should be short enough to make a reasonable entry in a table of contents. This element contains a descripton of the use case. Use this element to explaini important aspects of the use case. This element contains a list of the actors involved in use case. The first actor should be the primary actor. The list must contain at least one actor. This element containis information about a single actor. Set the primary attribute to true if the actor is the primary actor. An actor can be either a person or a system. This element describes the primary deliverable from the use case. This element may contain a reference to an output, report, or other item. This element describes the conditions that come before the execution of the scenarios. Extends are use cases that provide an optional sequence of events to other use cases. If this use case is extended, list the extensions here. This element is optional. If it is present, it must contain at least one extend element. This element provides a list of scenarios. There must be at least one scenario, the primary scenario. This element contains a description of the scenario. A scenaro is a list of numbered steps. The scenario name identifies the scenario. For example, one scenario should be labeled the primary scenario. The optional comment element is used to identify any conditions for invoking the scenario. This optional element can be used to attach additional information aboout the use case. This element describes the conditions that come after the execution of the scenarios.