You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "Lawrence Mandel (JIRA)" <ji...@apache.org> on 2008/05/20 21:11:55 UTC

[jira] Commented: (WODEN-112) Woden Use Cases

    [ https://issues.apache.org/jira/browse/WODEN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598409#action_12598409 ] 

Lawrence Mandel commented on WODEN-112:
---------------------------------------

John, any plan to work on the Woden use cases?

> Woden Use Cases
> ---------------
>
>                 Key: WODEN-112
>                 URL: https://issues.apache.org/jira/browse/WODEN-112
>             Project: Woden
>          Issue Type: Improvement
>            Reporter: John Kaputin
>
> Woden development has been driven by the WSDL 2.0 spec which is basically about a static data model, rather than a dynamic usage model. To ensure we understand the requirements of Woden users correctly it would be helpful to capture the key Use Cases in terms of Actors, what benefits they need to achieve and the interaction required across the system boundary (e.g. the API) to achieve those benefits. 
> Use cases captured in this form describe the external view of how agreed requirements will be supported. Although this is being done somewhat retrospectively, these use cases will provide the Woden user community with some gauge on how well Woden will meet their needs, without them having to become experts on the Woden API.  The use cases may also help facilitate a review of the Woden API before we release a 1.0 version. Such use cases may also be helpful for writing user documentation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org