
Web Service Implementation Methodology
Public Review Draft, 6 July 2005
Document
identifier:
fwsi-im-1.0-guidelines-doc-wd-01b.doc
Location:
http://www.oasis-open.org/committees/documents.php?wg_abbrev=fwsi
Editors:
Eng Wah LEE, Singapore Institute of Manufacturing Technology
Contributors:
Marc HAINES, individual <mhaines@uwm.edu>
Lai Peng CHAN, Singapore Institute of Manufacturing Technology
<lpchan@SIMTech.a-star.edu.sg>
Chai Hong ANG, Singapore Institute of Manufacturing Technology
Puay Siew TAN, Singapore Institute of Manufacturing Technology
Han Boon LEE, Singapore Institute of Manufacturing Technology
Yushi CHENG, Singapore Institute of Manufacturing Technology
<ycheng@SIMTech.a-star.edu.sg>
Xingjian XU, Singapore Institute of Manufacturing Technology
Zunliang YIN, Singapore Institute of Manufacturing Technology
Abstract:
This document specifies Web Service specific activities in a Web Service Implementation Methodology and illustrates the approach to incorporate these activities into an existing agile software development methodology.
Status:
This document is updated periodically on no
particular schedule. Send comments to
the editor.
Committee members should send comments on this specification to the fwsi-imsc@lists.oasis-open.org list. Others should subscribe to and send comments to the fwsi-comment@lists.oasis-open.org list. To subscribe, send an email message to fwsi-comment-request@lists.oasis-open.org with the word "subscribe" as the body of the message.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the FWSI TC web page (http://www.oasis-open.org/committees/fwsi/).
Table of Contents
2 Implementation
Methodology Overview
2.2
Web Service Implementation Lifecycle
3 Web Service
Implementation Methodology
3.2.1
Activity: Determine the need for Web Service
3.2.2
Activity: Elicit Web Service requirements
3.2.3
Activity: Manage the Web Service requirements
3.2.4
Activity: Model the usage scenarios
3.2.5
Activity: Prepare Test Cases for User Acceptance Test (UAT) and System Test