Web Services Implementation Methodology - Guide for ...
[pic]
Web Services Implementation Methodology – Guide for submitting Case Example
Working Draft 03, 14 August 2005
Document identifier:
fwsi-im-1 0-ExampleGuide-doc-wd-03.doc
Location:
Editor:
Eng Wah LEE, Singapore Institute of Manufacturing Technology
Andy TAN, individual
Contributors:
Andy TAN, individual
Chai Hong ANG, Singapore Institute of Manufacturing Technology
Marc HAINES, individual
Abstract:
This document provides a guideline to prepare a case example to be included in the Implementation Methodology Guideline.
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 imsc@lists.oasis- list. Others should subscribe to and send comments to the fwsi-comment@lists.oasis- list. To subscribe, send an email message to fwsi-comment-request@lists.oasis- 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 ().
Table of Contents
1 Introduction 3
1.1 Purpose of this document 3
1.2 Terminology 3
2 Case Example Submission Process 4
2.1 Proposal 4
2.2 Review 4
2.3 Adoption 4
3 Template for Case Example Submission 5
3.1.1 Section 1: Overview 5
3.1.2 Section 2: Terminology Mapping 5
3.1.3 Section 2.1: Implementation Lifecycle 5
3.1.4 Section 2.2: Project Team Roles 5
3.1.5 Section 2.3: Artifact Cross Reference 5
3.1.6 Section 3: Implementation Phases 6
Appendix A. Acknowledgments 7
Appendix B. Revision History 8
Appendix C. Notices 9
Introduction
1 Purpose of this document
The purpose of this document is to provide a template to prepare a case example of using agile software methodology to be included in the Web Service Implementation Methodology (WSIM) guideline.
2 Terminology
The Web Services Implementation Methodology defines a systematic approach to Web Services development, which define a set of generic and method-independent steps. This methodology can be applied by most software developer teams to develop Web Services applications.
Software practitioners can adopt any agile software development methodology for Web Services application development. Practitioners can contribute their experience by including the process as a case example to be included in the WSIM guideline.
This document intends to provide a guide to prepare the documentation and serve as a checklist. This is to provide easy reference by the reader.
Case Example Submission Process
This section describes the process of preparing the case examples for submission.
1 Proposal
Any member (refer to as proposer) can propose any agile software methodology by provide an overview of the methodology and explain how it can be adopted for Web Services Implementation.
The sub-committee will review the material and give feedback. When found suitable, the sub-committee will asked the proposer to prepare the documentation base on this template.
2 Review
The proposer posted the document on the OASIS portal and inform the chair or secretary of the sub-committee. The chair or the secretary will convene a meeting as soon as possible to review the document and provide feedback to the proposer.
The proposer will edit any changes requested or provide alternative recommendation and update the document for further review.
3 Adoption
The WSIM Sub-committee will review the case example submitted by members and voted to be accepted as case example. The voting process adheres to the same requirement as the committee draft.
Template for Case Example Submission
This section describes the template for the case example.
1 Section 1: Overview
This section provides an introduction to the agile software methodology. It aims to provide background information about the methodology using the vocabulary or terminology of the agile software methodology.
2 Section 2: Terminology Mapping
This sections explains the terminology used with respect to the agile software methodology and how it is related to the generic terminology used in the WSIM guideline. The aim is to provide a quick reference to help reader to cross reference the terminology used in the agile software methodology to that used in the WSIM guideline.
3 Section 2.1: Implementation Lifecycle
This section explains the implementation phases with respect to the agile software methodology. It maps the phases to the phases defined in the WSIM guideline.
If there is no direct mapping, a note is provided to explain why it is not needed or suggest additional phases typically not found in the standard agile software methodology doctrine. The same apply to cases where the phases required in the agile software methodology are not defined in the WSIM guideline. The purpose of this note is to enable the reader to understand the needs for inclusion.
4 Section 2.2: Project Team Roles
This section explains the project team members and their roles with respect to the agile software methodology. It provides a map to the project teams’ roles that is recommended in the WSIM guideline.
If there is no direct mapping, a note is provided to explain why it is not needed or suggest additional roles typically not found in the standard agile software methodology doctrine. A note is provided to highlight the adaptation recommended. The same apply to team roles found in the agile software methodology but not defined in the WSIM guideline. The purpose of this note is to enable the reader to understand the needs for the inclusion
5 Section 2.3: Artifact Cross Reference
This section provides a cross reference of the terminology describing artifacts produced at each phase with respect to the agile software methodology. It maps the artifacts to the artifacts defined in the WSIM guideline.
If there is no direct mapping, a note is provided to explain why it is not needed or suggest additional artifacts typically not found in the standard agile software methodology doctrine.
If there are additional artifacts required in the software agile methodology but not required in the IM guideline, a note is included to explain the inclusion.
6 Section 3: Implementation Phases
This section provides detail description of the implementation phases describe in Section 2.1. The terminology use is with respect to the agile software methodology and not the IM guideline. This guideline recommended the following sub-sections:
1 Activities
This section provides a detail description of the activities carried out using the terminology of the agile software methodology. The activities of a particular case example should be clearly linked to the activities listed in the generic implementation methodology document. This should include the use of or reference to the number associated with an activity (example [3.3.4] is a cross reference number referring to Activity: Identify reusable Web Services).
Activities from the generic implementation methodology document that do not apply to the particular agile methodology used in the case example do not have to be listed.
If there are activities specific to the agile methodology that do not have equivalent activities in the generic implementation methodology these activities heading will not have a cross reference number.
2 Roles
This section lists the members of the team participating in this activity using the terminology used for the agile software methodology.
3 Artifacts
This section listed the artifacts produced for this phase using the terminology used for the agile software methodology.
4 Section 4: References
This section lists any references used to prepare this document as well as materials to assist reader to understand the subject matters.
A. Acknowledgments
The following individuals were members of the committee during the development of this specification.
Andy TAN, Individual
Chai Hong ANG, Singapore Institute of Manufacturing Technology
Eng Wah LEE, Singapore Institute of Manufacturing Technology
Puay Siew TAN, Singapore Institute of Manufacturing Technology
Yushi CHENG, Singapore Institute of Manufacturing Technology
Xingjian XU, Singapore Institute of Manufacturing Technology
Zun Liang YIN, Singapore Institute of Manufacturing Technology
Roberto PASCUAL, The Infocomm Development Authority of Singapore
JAGDIP Talla, CrimsonLogic Pte Ltd
RAVI SHANKAR Narayanan Nair, CrimsonLogic Pte Ltd ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
Related searches
- amazon web services revenue
- amazon web services revenue 2018
- amazon web services profitability 2018
- amazon web services revenue history
- amazon web services financials
- amazon web services annual report
- amazon web services revenue 2019
- amazon web services strategic plan
- amazon web services cloud
- amazon web services growth
- amazon web services history
- amazon web services cloud platform