€¦ · Web viewWorking Draft 02, 23 December 2004. Document identifier:...

Web Service Implementation Methodology – Rational Unified Process (Example)Working Draft 02, 23 December 2004Document identifier:

document.doc

Location:http://www.oasis-open.org/committees/documents.php?wg_abbrev=fwsi

Editors:Lai Peng CHAN, Singapore Institute of Manufacturing Technology <[email protected]>Chai Hong ANG, Singapore Institute of Manufacturing Technology <[email protected]>

Contributors:Eng Wah LEE, Singapore Institute of Manufacturing Technology<[email protected]>Puay Siew TAN, Singapore Institute of Manufacturing Technology<[email protected]>Yushi CHENG, Singapore Institute of Manufacturing Technology <[email protected]>Xingjian XU, Singapore Institute of Manufacturing Technology <[email protected]>Zun Liang YIN, Singapore Institute of Manufacturing Technology <[email protected]>Andy TAN, individual, <[email protected]>Roberto PASCUAL, The Infocomm Development Authority of Singapore <[email protected]>JAGDIP Talla, CrimsonLogic Pte Ltd <[email protected]>RAVI SHANKAR Narayanan Nair, CrimsonLogic Pte Ltd <[email protected]>Marc HAINES, individual <[email protected]>

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 [email protected] list. Others should subscribe to and send comments to the [email protected] list. To subscribe, send an email message to

document.doc 20 September 2004Copyright © OASIS Open 2004. All Rights Reserved. of 37

1

2

3

4

5

67

89

1011121314151617181920212223242526272829303132333435363738

394041424344

12

mailto:[email protected]






mailto:%[email protected]








http://www.oasis-open.org/committees/documents.php?wg_abbrev=fwsi/

[email protected] 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/).


454647484950

34

http://www.oasis-open.org/committees/fwsi/


Table of Contents1 Case Example(s) of Applying the Implementation Methodology......................................9

1.1 Rational Unified Process (Example)...............................................................................91.1.1 Overview................................................................................................................. 91.1.2 Approach...............................................................................................................11

1.1.2.1 Discipline: Requirements...............................................................................................121.1.2.1.1 Workflow Detail: Analyze the Problem...................................................................12

1.1.2.1.1.1 Activity: Capture a Common Vocabulary....................................................121.1.2.1.1.1.1 Role....................................................................................................12

1.1.2.1.1.1.2 Artifact.................................................................................................13

1.1.2.1.1.2 Activity: Develop Vision (across all Web services).....................................131.1.2.1.1.2.1 Role....................................................................................................13

1.1.2.1.1.2.2 Artifact.................................................................................................13

1.1.2.1.2 Workflow Detail: Understand Stakeholder Needs..................................................131.1.2.1.2.1 Activity: Elicit Needs...................................................................................13

1.1.2.1.2.1.1 Role....................................................................................................13

1.1.2.1.2.1.2 Artifact.................................................................................................13

1.1.2.1.2.2 Activity: Develop Vision..............................................................................131.1.2.1.2.2.1 Role....................................................................................................13

1.1.2.1.2.2.2 Artifact.................................................................................................13

1.1.2.1.2.3 Activity: Manage Dependencies.................................................................131.1.2.1.2.3.1 Role....................................................................................................14

1.1.2.1.2.3.2 Artifact.................................................................................................14

1.1.2.1.2.4 Activity: Find Actors and Use Cases (per Web service).............................141.1.2.1.2.4.1 Role....................................................................................................14

1.1.2.1.2.4.2 Artifact.................................................................................................14

1.1.2.1.3 Workflow Detail: Define the System.......................................................................141.1.2.1.3.1 Activity: Find Actors and Use Cases (per Web service).............................14

1.1.2.1.3.1.1 Role....................................................................................................14

1.1.2.1.3.1.2 Artifact.................................................................................................14

1.1.2.1.4 Workflow Detail: Manage the Scope of the System...............................................141.1.2.1.4.1 Activity: Prioritise the Use Cases (per Web service)..................................14

1.1.2.1.4.1.1 Role....................................................................................................14

1.1.2.1.4.1.2 Artifact.................................................................................................14

1.1.2.1.5 Workflow Detail: Refine the System Definition.......................................................151.1.2.1.5.1 Activity: Detail a Use Case.........................................................................15

1.1.2.1.5.1.1 Role....................................................................................................15

1.1.2.1.5.1.2 Artifact.................................................................................................15

1.1.2.1.5.2 Activity: Detail the Software Requirements................................................151.1.2.1.5.2.1 Role....................................................................................................15

1.1.2.1.5.2.2 Artifact.................................................................................................15

1.1.2.2 Discipline: Analysis and Design.....................................................................................161.1.2.2.1 Workflow Detail: Define a Candidate Architecture (for each Web service)............16


51

525354555657

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

9293

56

1.1.2.2.1.1 Activity: Architectural Analysis....................................................................161.1.2.2.1.1.1 Role....................................................................................................16

1.1.2.2.1.1.2 Artifact.................................................................................................16

1.1.2.2.2 Workflow Detail: Analyse Behaviour (for each use case)......................................161.1.2.2.2.1 Activity: Use Case Analysis........................................................................16

1.1.2.2.2.1.1 Role....................................................................................................17

1.1.2.2.2.1.2 Artifact.................................................................................................17

1.1.2.2.3 Workflow Detail: Refine the Architecture (for each Web service)..........................171.1.2.2.3.1 Activity: Identify Design Elements..............................................................17

1.1.2.2.3.1.1 Role....................................................................................................17

1.1.2.2.3.1.2 Artifact.................................................................................................17

1.1.2.2.3.2 Activity: Identify Design Mechanisms.........................................................171.1.2.2.3.2.1 Role....................................................................................................17

1.1.2.2.3.2.2 Artifact.................................................................................................17

1.1.2.2.4 Workflow Detail: Design Components....................................................................171.1.2.2.4.1 Activity: Use Case Design..........................................................................17

1.1.2.2.4.1.1 Role....................................................................................................18

1.1.2.2.4.1.2 Artifact.................................................................................................18

1.1.2.2.4.2 Activity: Subsystem Design........................................................................181.1.2.2.4.2.1 Role....................................................................................................18

1.1.2.2.4.2.2 Artifact.................................................................................................18

1.1.2.2.4.3 Activity: Class Design.................................................................................181.1.2.2.4.3.1 Role....................................................................................................18

1.1.2.2.4.3.2 Artifact.................................................................................................18

1.1.2.3 Discipline: Implementation.............................................................................................191.1.2.3.1 Workflow Detail: Structure the Implementation Model...........................................19

1.1.2.3.1.1 Activity: Structure the Implementation Model.............................................191.1.2.3.1.1.1 Role....................................................................................................19

1.1.2.3.1.1.2 Artifact.................................................................................................19

1.1.2.3.2 Workflow Detail: Implement Components..............................................................191.1.2.3.2.1 Activity: Implement Design Elements.........................................................19

1.1.2.3.2.1.1 Role....................................................................................................20

1.1.2.3.2.1.2 Artifact.................................................................................................20

1.1.2.3.3 Workflow Detail: Integrate Each Web Service.......................................................201.1.2.3.3.1 Activity: Integrate Subsystem.....................................................................20

1.1.2.3.3.1.1 Role....................................................................................................20

1.1.2.3.3.1.2 Artifact.................................................................................................20

1.1.2.3.4 Workflow Detail: Manage the Scope of the System...............................................201.1.2.3.4.1 Activity: Prioritise the Use Cases (per Web service)..................................20

1.1.2.3.4.1.1 Role....................................................................................................20

1.1.2.3.4.1.2 Artifact.................................................................................................20

1.1.2.3.5 Workflow Detail: Refine the System Definition.......................................................201.1.2.3.5.1 Activity: Detail a Use Case.........................................................................20

1.1.2.3.5.1.1 Role....................................................................................................20

1.1.2.3.5.1.2 Artifact.................................................................................................20


94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

78

1.1.2.3.5.2 Activity: Detail the Software Requirements................................................211.1.2.3.5.2.1 Role....................................................................................................21

1.1.2.3.5.2.2 Artifact.................................................................................................21

1.1.2.4 Discipline: Testing..........................................................................................................221.1.2.4.1 Workflow Detail: Define Mission.............................................................................22

1.1.2.4.1.1 Activity: Identify Test Motivators.................................................................221.1.2.4.1.1.1 Role....................................................................................................23

1.1.2.4.1.1.2 Artifact.................................................................................................23

1.1.2.4.1.2 Activity: Agree on the Mission....................................................................231.1.2.4.1.2.1 Role....................................................................................................24

1.1.2.4.1.2.2 Artifact.................................................................................................24

1.1.2.4.1.3 Activity: Define Assessment and Traceability Needs.................................241.1.2.4.1.3.1 Role....................................................................................................24

1.1.2.4.1.3.2 Artifact.................................................................................................24

1.1.2.4.1.4 Activity: Define Test Approach...................................................................251.1.2.4.1.4.1 Role....................................................................................................25

1.1.2.4.1.4.2 Artifact.................................................................................................25

1.1.2.4.1.5 Activity: Identify Test Ideas.........................................................................251.1.2.4.1.5.1 Role....................................................................................................26

1.1.2.4.1.5.2 Artifact.................................................................................................26

1.1.2.4.2 Workflow Detail: Define Test Bed..........................................................................261.1.2.4.2.1 Activity: Identify Test Environment.............................................................26

1.1.2.4.2.1.1 Role....................................................................................................26

1.1.2.4.2.1.2 Artifact.................................................................................................26

1.1.2.4.2.2 Activity: Prepare H/W & S/W Infrastructure................................................261.1.2.4.2.2.1 Role....................................................................................................27

1.1.2.4.2.2.2 Artifact.................................................................................................27

1.1.2.4.2.3 Activity: Prepare Test Data Sets.................................................................271.1.2.4.2.3.1 Role....................................................................................................27

1.1.2.4.2.3.2 Artifact.................................................................................................27

1.1.2.4.3 Workflow Detail: Develop, Test and Evaluate........................................................271.1.2.4.3.1 Activity: Define Test Details........................................................................27

1.1.2.4.3.1.1 Role....................................................................................................27

1.1.2.4.3.1.2 Artifact.................................................................................................27

1.1.2.4.3.2 Activity: Implement Test.............................................................................281.1.2.4.3.2.1 Role....................................................................................................28

1.1.2.4.3.2.2 Artifact.................................................................................................28

1.1.2.4.3.3 Activity: Implement Test Suite....................................................................281.1.2.4.3.3.1 Role....................................................................................................28

1.1.2.4.3.3.2 Artifact.................................................................................................28

1.1.2.4.3.4 Activity: Execute Test Suite........................................................................281.1.2.4.3.4.1 Role....................................................................................................29

1.1.2.4.3.4.2 Artifact.................................................................................................29

1.1.2.4.3.5 Activity: Analyse Test Failures....................................................................291.1.2.4.3.5.1 Role....................................................................................................29


139

140

141

142143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

910

1.1.2.4.3.5.2 Artifact.................................................................................................29

1.1.2.4.3.6 Activity: Determine Test Results.................................................................291.1.2.4.3.6.1 Role....................................................................................................29

1.1.2.4.3.6.2 Artifact.................................................................................................29

1.1.2.4.4 Workflow Detail: Improve Test Assets...................................................................291.1.2.4.4.1 Activity: Define Test Approach (Refinement)..............................................29

1.1.2.4.4.1.1 Role....................................................................................................30

1.1.2.4.4.1.2 Artifact.................................................................................................30

1.1.2.4.4.2 Activity: Identify Test Ideas (Refinement)...................................................301.1.2.4.4.2.1 Role....................................................................................................30

1.1.2.4.4.2.2 Artifact.................................................................................................30

1.1.2.4.4.3 Activity: Prepare Guidelines for the Project................................................301.1.2.4.4.3.1 Role....................................................................................................30

1.1.2.4.4.3.2 Artifact.................................................................................................30

1.1.2.5 Discipline: Deployment..................................................................................................311.1.2.5.1 Workflow Detail: Plan Deployment.........................................................................31

1.1.2.5.1.1 Activity: Develop Deployment Plan.............................................................311.1.2.5.1.1.1 Role....................................................................................................31

1.1.2.5.1.1.2 Artifact.................................................................................................31

1.1.2.5.2 Workflow Detail: Develop Support Material............................................................321.1.2.5.2.1 Activity: Develop Training Material.............................................................32

1.1.2.5.2.1.1 Role....................................................................................................32

1.1.2.5.2.1.2 Artifact.................................................................................................32

1.1.2.5.2.2 Activity: Develop Support Material..............................................................321.1.2.5.2.2.1 Role....................................................................................................32

1.1.2.5.2.2.2 Artifact.................................................................................................32

1.1.2.5.3 Workflow Detail: Produce Deployment Unit (Web service)....................................321.1.2.5.3.1 Activity: Write Release Notes.....................................................................32

1.1.2.5.3.1.1 Role....................................................................................................32

1.1.2.5.3.1.2 Artifact.................................................................................................32

1.1.2.5.3.2 Activity: Develop Installation Artifacts.........................................................321.1.2.5.3.2.1 Role....................................................................................................32

1.1.2.5.3.2.2 Artifact.................................................................................................32

1.1.2.5.3.3 Activity: Create Deployment Unit (Web service).........................................331.1.2.5.3.3.1 Role....................................................................................................33

1.1.2.5.3.3.2 Artifact.................................................................................................33

1.1.2.5.3.4 Activity: Deploy Web Service to identified app servers..............................331.1.2.5.3.4.1 Role....................................................................................................33

1.1.2.5.3.4.2 Artifact.................................................................................................33

1.1.2.5.3.5 Activity: Publish Web service [optional]......................................................331.1.2.5.3.5.1 Role....................................................................................................33

1.1.2.5.3.5.2 Artifact.................................................................................................33

2 References..................................................................................................................... 342.1 Normative..................................................................................................................... 342.2 Non-Normative.............................................................................................................34


184

185

186

187

188

189

190

191

192

193

194

195

196

197

198199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226227228

1112

Appendix A. Acknowledgments...............................................................................................35Appendix B. Revision History..................................................................................................36Appendix C. Notices...............................................................................................................37


229230231

232

1314

List of FiguresFigure 3: The Rational Unified Process..................................................................................13Figure 4: The RUP development disciplines...........................................................................15Figure 5: Requirements Workflow...........................................................................................15Figure 6: Analysis and Design Workflow.................................................................................19Figure 7: Implementation Workflow.........................................................................................22Figure 8: Testing Workflow.....................................................................................................25Figure 9: Deployment Workflow..............................................................................................34


233

234235236237238239240

241

1516

1 Case Example(s) of Applying the Implementation Methodology

The case example(s) aims to illustrate how an agile software methodology could be adapted to incorporate the Web services-specific activities described in the previous chapters.

It is not the intention of this Technical Committee to recommend any of the following case example(s) as the recommended agile software methodology to be used for Web services implementation. The Web service implementation methodology is intended to be generic and should be able to incorporate to any agile software methodology.

1.1 Rational Unified Process (Example)In this section, the Rational Unified Process (RUP) is illustrated as an example of how the Web service implementation methodology can be incorporated into RUP. Although the example tries to be as complete as possible, it is foreseeable that different projects set-up may be different in nature and would need to further customise this case example according to their needs.

1.1.1 Overview

The Rational Unified Process® is a software engineering process. It provides a disciplined approach to assigning tasks and responsibilities within a development organization. Its goal is to ensure the production of high quality software that meets the needs of its end users within a predictable schedule and budget.

As illustrated in Source: IBM-Rational Software, the overall architecture of RUP has two dimensions: the horizontal axis represents time and shows the lifecycle aspects of the process as it unfolds. This dimension is expressed in terms of phases, iterations and

milestones. The vertical axis represents disciplines that logically group activities by nature. This second dimension portrays the static aspect of the process and is described in terms of

process components, disciplines, activities, workflows, artifacts, and roles.

The “humps” in the graph illustrate the relative emphases of the disciplines change over the life of the project. For example, in early iterations more time is spent on Requirements, and in later iterations more time is spent on implementation.


242

243

244245246247248249250251252

253254255256257258259

260

261262263264265266267268269270271272273274275276277278

1718

Source: IBM-Rational Software

Figure 1: The Rational Unified Process

As the terms used in RUP are different from the terms used in Web Service Implementation Methodology, Table 1 maps the terms used between the two software methodologies.

RUP Web Service Implementation MethodologyPhases LifecycleDisciplines PhasesRoles Roles

Analyst System AnalystsRequirements Specifier

Analyst ArchitectRequirements Analyst

Developer Software ArchitectDesignerImplementerIntegrator

Developer DesignerDeveloperDeployer

Tester Test ManagerTest AnalystTest DesignerTesterTest System Administrator

Tester Test ManagerTest DesignerTesterTest System Administrator

Production & Support

Deployment ManagerDBAProcess Engineer

Others UserSystem EngineerProject ManagerStakeholder

Artifacts ArtifactsGlossaryVision

Business Requirement Specifications

Stakeholder RequestsRequirements AttributesRequirements Management PlanSoftware RequirementSoftware Requirements SpecificationsUse Case Model

Requirement Specifications


279280

281

282283284285286287

1920

Supplementary SpecificationsSoftware Architecture Document Software Architecture SpecificationsDesign ModelAnalysis ModelUse Case Realization

Web Service Signature SpecificationsXML SchemaDesign Specifications

Test PlanTest Environment ConfigurationTest Strategy

Test Plan – UAT and System TestTest Plan – Performance TestTest Plan – Integration / Interoperability TestTest Plan – Functional Test

Test-Ideas ListTest CaseTest DataTest Suite

Test Plan – Testbed

Test Script Test ScriptsUnit Test ScriptsClient Test Code

Test LogTest Results

Test Results

Implementation ModelImplementation ElementBuild

Implementation CodesWeb Service Client Codes

Deployment Unit Release NotesDeployment ScriptsWSDL File

End-User Support Material Interoperability GuideUser GuideOn-line HelpTutorials

Training Materials Training MaterialsChange Request Not ApplicableDeployment Plan Not ApplicableInstallation Artifacts Not ApplicableProject Specific Guidelines Not ApplicableRelease Notes Not ApplicableTest Environment Summary Not Applicable

Table 1: Mapping of the terms used by both the RUP and the Web Service Implementation Methodology

1.1.2 Approach

In RUP, there are 9 disciplines altogether namely, Business Modeling, Requirements, Analysis & Design, Implementation, Test, Deployment, Configuration & Change Management, Project Management and Environment. However, as the focus of this Web service implementation methodology is on the implementation aspects only, the discplines Business Modeling, Configuration & Change Management, Project Management and Environment are beyond the scope of this document and will not be discussed here. The following disciplines as shown in Figure 2, are of interest and will be illustrated in detail in the subsequent sections.


288

289

290

291292293294295296297298299300

2122

Requirements Analysis and Design Implementation Testing DeploymentRequirements Analysis and Design Implementation Testing Deployment

Figure 2: The RUP development disciplines

For each of these disciplines, the relevant workflow details will be described and are extracted directly from RUP. Most of the activities in these workflow do not need special customisation. However, in areas where the activities are specific to Web services, these will be highlighted in bold1.

1.1.2.1 Discipline: Requirements

Requirements

•Analyze Problem•Capture a Common Vocabulary•Develop Vision (across all WS)

•Understand Stakeholder Needs•Elicit Needs

•Categorise needs into respective WSs•Identify potential WS

•Develop Vision•Refine the Categorisation Based on Features

•Manage Dependencies•Prioritise the WS

•Find Actors & UCs (per WS)•Define System

•Find Actors & UCs (per WS)•Manage Scope Of System

•Prioritise the UCs (per WS)•Refine System Definition

•Detail a UC•Detail the Software Requirements

Requirements

•Analyze Problem•Capture a Common Vocabulary•Develop Vision (across all WS)

•Understand Stakeholder Needs•Elicit Needs

•Categorise needs into respective WSs•Identify potential WS

•Develop Vision•Refine the Categorisation Based on Features

•Manage Dependencies•Prioritise the WS

•Find Actors & UCs (per WS)•Define System

•Find Actors & UCs (per WS)•Manage Scope Of System

•Prioritise the UCs (per WS)•Refine System Definition

•Detail a UC•Detail the Software Requirements


Figure 3: Requirements Workflow

1.1.2.1.1 Workflow Detail: Analyze the Problem

1.1.2.1.1.1 Activity: Capture a Common Vocabulary- Find Common Terms

1.1.2.1.1.1.1 RoleSystem Analyst

1 The activities in italics represent refinement of an activity previously defined.


301

302303

304305306307308309

310

311312

313

314

315

316

317318

319320

23

2425

1.1.2.1.1.1.2 ArtifactThe results should be recorded in Glossary.

1.1.2.1.1.2 Activity: Develop Vision (across all Web services)- Gain agreement on the some problems faced- Identify stakeholders of the Web services- Define boundaries of Web services- Identify (initial) constraints to be imposed on the Web services- Formulate Problem Statement (positioning why the need to develop Web services)


1.1.2.1.1.2.2 ArtifactThe results should be recorded in Requirements Attributes and Vision.

1.1.2.1.2 Workflow Detail: Understand Stakeholder Needs

1.1.2.1.2.1 Activity: Elicit Needs- Determine sources for requirements (who and where can you gather the

requirements of Web services)- Gather information (based on stakeholders identified)- Conduct brainstorming session- Categorise the needs into respective Web services- Identify the Web services


1.1.2.1.2.1.2 ArtifactThe results should be recorded in Stakeholder Requests.

1.1.2.1.2.2 Activity: Develop Vision- Gain agreement on the some problems faced- Identify stakeholders of the Web services- Refine boundaries of Web services- Identify the new constraints (or refine on existing constraints)- Formulate Problem Statement (positioning why the need to develop Web services)- Define features of the Web services based on the needs list- Refine the categorisation of the Web services based on the features


1.1.2.1.2.2.2 ArtifactThe results should be recorded in Requirements Attributes and Vision.

1.1.2.1.2.3 Activity: Manage Dependencies- Assign attributes to the features of the Web services


321322323

324325326327328329

330331

332333334

335

336337338339340341342

343344

345346347

348349350351352353354355

356357

358359360

361362

2627

- Prioritise the Web services- Establish and verify traceability (what requirement types to be traced)- Manage changing requirements


1.1.2.1.2.3.2 ArtifactThe results should be recorded in Requirements Attributes, Requirements Management Plan and Vision.

1.1.2.1.2.4 Activity: Find Actors and Use Cases (per Web service)- Find Actors- Find Use Cases- Create use case model


1.1.2.1.2.4.2 ArtifactThe results should be recorded in Use Case Model and Supplementary Specifications.

1.1.2.1.3 Workflow Detail: Define the System

1.1.2.1.3.1 Activity: Find Actors and Use Cases (per Web service)- Find Actors- Find Use Cases- Refine use case model to include outlined use cases



1.1.2.1.4 Workflow Detail: Manage the Scope of the System

1.1.2.1.4.1 Activity: Prioritise the Use Cases (per Web service)- Prioritise Use Cases and Scenarios

1.1.2.1.4.1.1 RoleSoftware Architect

1.1.2.1.4.1.2 ArtifactThe results should be recorded in Software Architecture Document and Software Requirement.


363364365

366367

368369370371

372373374375

376377

378379380

381

382383384385

386387

388389390

391

392393

394395

396397398399

2829

1.1.2.1.5 Workflow Detail: Refine the System Definition

1.1.2.1.5.1 Activity: Detail a Use Case- Review and Refine the Scenarios- Detail the Flow of Events- Structure the Flow of Events- Describe any Special Requirements

1.1.2.1.5.1.1 RoleRequirements Specifier

1.1.2.1.5.1.2 ArtifactThe results should be recorded in Use Case Model, Supplementary Specifications.

1.1.2.1.5.2 Activity: Detail the Software Requirements- Detail the Software Requirements- Generate Supporting Reports (Use Case Model and Supplementary Specs)

1.1.2.1.5.2.1 RoleRequirements Specifier

1.1.2.1.5.2.2 ArtifactThe results should be recorded in Software Requirement and Software Requirements Specifications.


400

401402403404405

406407

408409410

411412413

414415

416417418419

3031

1.1.2.2 Discipline: Analysis and Design

Analysis and Design

•Define a Candidate Architecture (for each WS)

•Architectural Analysis•Identify WS Signatures•Identify possible 3rd party WS

•Analyse Behaviour (for each UC)•UC Analysis

•Refine the Architecture (for each WS)•Identify Design Elements

•Signature Mapping Translation•Confirm reuse of 3rd party WS•Identify WS to be built

•Identify Design Mechanisms•Design Components

•UC Design•Subsystem Design

•WS Signature Design•Class Design

Analysis and Design

•Define a Candidate Architecture (for each WS)

•Architectural Analysis•Identify WS Signatures•Identify possible 3rd party WS

•Analyse Behaviour (for each UC)•UC Analysis

•Refine the Architecture (for each WS)•Identify Design Elements

•Signature Mapping Translation•Confirm reuse of 3rd party WS•Identify WS to be built

•Identify Design Mechanisms•Design Components

•UC Design•Subsystem Design

•WS Signature Design•Class Design


Figure 4: Analysis and Design Workflow

1.1.2.2.1 Workflow Detail: Define a Candidate Architecture (for each Web service)

1.1.2.2.1.1 Activity: Architectural Analysis- Define the high-level organization- Identify key abstractions- Identify analysis mechanisms- Identify the use case realization for the current iteration- Identify the Web Service signatures- Identify the possible 3rd party Web Service reuse


1.1.2.2.1.1.2 ArtifactThe results should be recorded in Software Architecture Document and Design Model.

1.1.2.2.2 Workflow Detail: Analyse Behaviour (for each use case)

1.1.2.2.2.1 Activity: Use Case Analysis- Find analysis classes from Use Case Behaviour


420

421

422423

424

425

426427

428429430431432433434

435436

437438439

440

441442

3233

- Distribute behaviour to analysis classes- Describe responsibilities- Reconcile the use case realization- Qualify analysis mechanisms

1.1.2.2.2.1.1 RoleDesigner

1.1.2.2.2.1.2 ArtifactThe results should be recorded in Analysis Model and Use Case Realization.

1.1.2.2.3 Workflow Detail: Refine the Architecture (for each Web service)

1.1.2.2.3.1 Activity: Identify Design Elements- Signature mapping translation- Confirm reuse of 3rd party Web Services- Identify Web Services to be built- Identify classes and subsystems based on the activity Use Case Analysis- Identify subsystem interfaces

o Identify candidate interfaces (from internal or external source)o Look for similarities between interfaces

- Identify reuse opportunitieso Look for existing subsystems with similar interfaceso Modify the newly identified interfaces to improve the fit

- Update the organization of the design model


1.1.2.2.3.1.2 ArtifactThe results should be recorded in Design Model.

1.1.2.2.3.2 Activity: Identify Design Mechanisms- Inventory the implementation mechanisms- Map design mechanisms to implementation mechanisms- Document architectural mechanisms (in terms of patterns)


1.1.2.2.3.2.2 ArtifactThe results should be recorded in Software Architecture Document and Design Model.

1.1.2.2.4 Workflow Detail: Design Components

1.1.2.2.4.1 Activity: Use Case Design- Describe Interactions between design objects (refine interaction diagrams)- Simplify sequence diagrams with interfaces of subsystems (if any subsystems found)- Unify design classes and subsystems


443444445446

447448

449450451

452

453454455456457458459460461462463464

465466

467468469

470471472473

474475

476477478

479

480481482483

3435


1.1.2.2.4.1.2 ArtifactThe results should be recorded in Design Model and Use Case Realization.

1.1.2.2.4.2 Activity: Subsystem Design- Interface realization (Web service signature design)- Distribute subsystem behaviour to subsystem elements (design the Web service)- Document subsystem elements (internal structure of the Web service)- Describe subsystem dependencies



1.1.2.2.4.3 Activity: Class Design- Create initial design classes- Define class visibility- Define operations- Define attributes- Define dependencies- Define associations- Define generalizations- Handle non-function requirements




484485

486487488

489490491492493

494495

496497498

499500501502503504505506507

508509

510511512

3637

1.1.2.3 Discipline: Implementation

Implementation

•Structure the Implementation Model


•Implement Components•Implement Design Elements

•Wrapping into WS•Integrate Each WS

•Integrate Subsystem•Aggregate WS for Application Development

•Manage Scope Of System•Prioritise the UCs (per WS)

•Refine System Definition•Detail a UC•Detail the Software Requirements

Implementation



•Implement Components•Implement Design Elements

•Wrapping into WS•Integrate Each WS

•Integrate Subsystem•Aggregate WS for Application Development

•Manage Scope Of System•Prioritise the UCs (per WS)

•Refine System Definition•Detail a UC•Detail the Software Requirements


Figure 5: Implementation Workflow

1.1.2.3.1 Workflow Detail: Structure the Implementation Model

1.1.2.3.1.1 Activity: Structure the Implementation Model- Establish the implementation model structure- Define imports for each implementation components- Decide how to treat executables (and other derived objects)


1.1.2.3.1.1.2 ArtifactThe results should be recorded in Software Architecture Document and Implementation Model.

1.1.2.3.2 Workflow Detail: Implement Components

1.1.2.3.2.1 Activity: Implement Design Elements- Implement operations- Implement associations- Implement attributes- Provide feedback to design


513

514

515516

517

518

519

520521522523

524525

526527528529

530

531532533534535

3839

- Wrapping into Web Service

1.1.2.3.2.1.1 RoleImplementer

1.1.2.3.2.1.2 ArtifactThe results should be recorded in Implementation Element.

1.1.2.3.3 Workflow Detail: Integrate Each Web Service

1.1.2.3.3.1 Activity: Integrate Subsystem- Integrate implementation elements- Aggregate Web Service for application development

1.1.2.3.3.1.1 RoleIntegrator

1.1.2.3.3.1.2 ArtifactThe results should be recorded in Build and Implementation Model.

1.1.2.3.4 Workflow Detail: Manage the Scope of the System

1.1.2.3.4.1 Activity: Prioritise the Use Cases (per Web service)- Prioritise Use Cases and Scenarios


1.1.2.3.4.1.2 ArtifactThe results should be recorded in Software Architecture Document and Software Requirement.

1.1.2.3.5 Workflow Detail: Refine the System Definition

1.1.2.3.5.1 Activity: Detail a Use Case- Review and Refine the Scenarios- Detail the Flow of Events- Structure the Flow of Events- Describe any Special Requirements

1.1.2.3.5.1.1 RoleRequirement Specifier



536

537538

539540541

542

543544545

546547

548549550

551

552553

554555

556557558559

560

561562563564565

566567

568569570

4041

1.1.2.3.5.2 Activity: Detail the Software Requirements- Detail the Software Requirements- Generate Supporting Reports (Use Case Model and Supplementary Specs)

1.1.2.3.5.2.1 RoleRequirement Specifier

1.1.2.3.5.2.2 ArtifactThe results should be recorded in Software Requirement and Software Requirements Specifications.


571572573

574575

576577578579

4243

1.1.2.4 Discipline: Testing


Figure 6: Testing Workflow

1.1.2.4.1 Workflow Detail: Define Mission

1.1.2.4.1.1 Activity: Identify Test Motivators- Identify iteration target items

o Web serviceso configuration (deployment platform)

- Gather and examine related informationo dependencies of services to be tested

other services configuration (deployment platform)

- Identify candidate motivatorso Web services

functionality usability


Testing

•Define Mission• Identify Test Motivators

•Functionality•Reliability•Performance•interoperability

• Agree on Mission• Define Assessment &

Traceability Needs• Define Test Approach

•API Level•SOAP Level

• Identify Test ideas•Define Test Bed

• Identify Test Environment• Prepare H/W & S/W Infrastructure• Prepare Test Data Sets

•Develop, Test & Evaluate• Define Test Details• Implement Test

•Generate WS Client• Implement Test Suite• Execute Test Suite• Analyse Test Failures• Determine Test Results

•Improve Test Assets• Define Test Approach• Identify Test Ideas• Prepare Guidelines for Project

Testing

•Define Mission• Identify Test Motivators

•Functionality•Reliability•Performance•interoperability

• Agree on Mission• Define Assessment &

Traceability Needs• Define Test Approach

•API Level•SOAP Level

• Identify Test ideas•Define Test Bed

• Identify Test Environment• Prepare H/W & S/W Infrastructure• Prepare Test Data Sets

•Develop, Test & Evaluate• Define Test Details• Implement Test

•Generate WS Client• Implement Test Suite• Execute Test Suite• Analyse Test Failures• Determine Test Results

•Improve Test Assets• Define Test Approach• Identify Test Ideas• Prepare Guidelines for Project

580

581

583

584

585

586

587588589590591592593594595596597598

4445

reliability performance supportability

- Determine quality riskso prioritise the tests requirements

architecture significant value of service stability

o define the acceptable quality level- Define motivator list

o define the specific Web services ready to be tested- Maintain traceability relationships

o manage the test requirements to the other requirements impact analysis

- Evaluate and verify your resultso verify with team members on the objectives of this activity

1.1.2.4.1.1.1 RoleTest Manager

1.1.2.4.1.1.2 ArtifactThe results should be recorded in Test Plan.

1.1.2.4.1.2 Activity: Agree on the Mission- Investigate options for the scope of the assessment effort

o determine the resources needed to achieve the testingo scope the test based on existing resources

- Formulate mission statemento determine a balance between the need for:

Test for correctness Test for completeness

o determine Test Coverage Code Test requirements Defect Test Result

o determine the necessary stages of testing Unit (Formal/Informal) Integration (Formal/Informal) System (Formal) UAT (Formal)

- Identify test deliverableso Test Plan (based on type of tests)

Test Cases (high-level) Test Scenarios (test case)

o Explanationo Deriving Test Cases from Use Caseso Deriving Test Cases from Supplementary

Specifications Deriving Test Cases for Performance Tests Deriving Test Cases for Security / Access

Tests Deriving Test Cases for Configuration Tests Deriving Test Cases for Installation Tests Deriving Test Cases for other Non

Functional Tests


599600601602603604605606607608609610611612613614

615616

617618619

620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652

4647

o Deriving Test Cases for Product Acceptance Testso Build Verification Test Cases for Regression Testso Defining Test Data for Test Caseso use the existing test ideas as a mean to identify

possible scenarioso verify all extension points where not explicitly defined

Test Procedures/Steps Test Scripts

Test Result- Evaluate and verify your results

o verify with team members and stakeholder on the objectives of this activity

1.1.2.4.1.2.1 RoleTest Manager


1.1.2.4.1.3 Activity: Define Assessment and Traceability Needs- Identify assessment and traceability requirements

o how to assess formal and informal testing- Consider constraints

o limitation that prohibits the testing effort existing skills set availability of resources

tools information process skills set

- Consider possible strategieso acquire required skills

vendor training

o outsource- Define and agree on the assessment strategy

o define checkpoint to assess the strategy (verify test approach)- Define tool requirements

o Use existing tool Good match Workaround solution Acquire new technology

o Increase productivity Regression testing

- Evaluate and verify your resultso verify with team members and stakeholder on the objectives of this activity

1.1.2.4.1.3.1 RoleTest Analyst



653654655656657658659660661662663

664665

666667668

669670671672673674675676677678679680681682683684685686687688689690691692693694695

696697

698699700

4849

1.1.2.4.1.4 Activity: Define Test Approach- Examine test motivators and target test items

o test requirements - FURPS- Examine the software architecture

o understand how the target is deployed select the appropriate test point

- Consider the appropriate breadth and depth of the test approacho determine strategy for the test points

API level SOAP Client level

Atomic / Collaboration- Identify existing test techniques for reuse

o gather experience from team members identify the possible technique for use

select appropriate technique the rest as contingency

- Define techniqueso Outline each technique for each type of test

Automated/Manual/semi-automated Require tool

Framework Test Design

o maintenanceo effectivenesso reusableo longevity

Implementation tips and tricks Test bed pre-condition/post-condition

Test data management Test Result logging/reporting

- Define the test asset configuration management strategyo Identify possible test assets management

version control backup

- Survey availability of reusable assetso Identify existing test asset which could be reused

Based on test design- Evaluate and verify your results

o verify with team members and stakeholder on the objectives of this activity

1.1.2.4.1.4.1 RoleTest Designer

1.1.2.4.1.4.2 ArtifactThe results should be recorded in Test Environment Configuration, Test Plan and Test Strategy.

1.1.2.4.1.5 Activity: Identify Test Ideas- Identify relevant Test Motivators and Target Test Items

o Determine level of testing required for specific/partial targets Correctness (must) Completeness (vary)

The test ideas will help you to identify the possible test scenarios you would need to address based on the signature of each method call found in the specific Web service


701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739

740741

742743744745

746747748749750751752753

5051

- Examine relevant available Test-Idea Catalogso Check existing best practices to test specific

- Brainstorm additional Test Ideaso Enhance Test Idea catalogo Examine Web service and analyse every method signature

Valid value Boundary value

o Identify possible values for each parameter. Valid and invalid

Special value Invalid value

Must conform to the syntax of the parameter data structure Guidelines: Test Ideas for Booleans and Boundaries Guidelines: Test Ideas for Method Calls

- Refine the Test-Ideas Listo update existing list

- Evaluate and verify your resultso verify with team members and stakeholder on the objectives of this activity


1.1.2.4.1.5.2 ArtifactThe results should be recorded in Test-Ideas List.

1.1.2.4.2 Workflow Detail: Define Test Bed

1.1.2.4.2.1 Activity: Identify Test Environment- Identify the application architecture and deployment

o Hardware and Software (20% effort) Configurations

o Test Data (80% effort) Explanation Depth Breadth Scope Architecture

- Identify the test facilitieso Tools

Hardware and Software requirementso Roles

Sys Admin, DBA, etco Security


1.1.2.4.2.1.2 ArtifactThe results should be recorded in Test Environment Configuration.

1.1.2.4.2.2 Activity: Prepare H/W & S/W Infrastructure- Select the appropriate technique to control environment- Set up test environment


754755756757758759760761762763764765766767768769770771

772773

774775776

777

778779780781782783784785786787788789790791792793

794795

796797798

799800801

5253

o settings and configuration- Restore test environment

o Logso Temp fileso Software and Hardware settings

1.1.2.4.2.2.1 RoleTest System Administrator, DBA

1.1.2.4.2.2.2 ArtifactThe results should be recorded in Test Environment Configuration.

1.1.2.4.2.3 Activity: Prepare Test Data Sets- Identify the test data to be used

o Deptho Breadtho Scope

- Identify the strategy to restore test datao data refresho data re-initializeo data reseto data roll forward


1.1.2.4.2.3.2 ArtifactThe results should be recorded in Test Data.

1.1.2.4.3 Workflow Detail: Develop, Test and Evaluate

1.1.2.4.3.1 Activity: Define Test Details- Examine the Target Test Item and related Test-Ideas List- Select a subset of the test ideas to detail- For each test idea, design the Test;

o identify input, output and execution conditionso identify candidate points of observationo identify candidate points of controlo Identify appropriate oracles

- Define required data sources, values and ranges- Source sufficient consumable Test Data- Maintain traceability relationships- Evaluate and verify your results


1.1.2.4.3.1.2 ArtifactThe results should be recorded in Test Case, Test Data and Test Script.


802803804805806

807808

809810811

812813814815816817818819820821

822823

824825826

827

828829830831832833834835836837838839

840841

842843844

5455

1.1.2.4.3.2 Activity: Implement Test- Test Design

o Macro-Level Collaboration of high-level test case

o Micro-Level Test script implementation level

Affected by the test data managemento Data partitioning strategyo Data “life-cycle” strategy

- Select appropriate implementation technique- Set up test environment preconditions- Generate Web service client- Implement the test- Establish external data sets- Verify the test implementation- Restore test environment to known state- Maintain traceability relationships- Evaluate and verify your results

1.1.2.4.3.2.1 RoleTester

1.1.2.4.3.2.2 ArtifactThe results should be recorded in Test Script.

1.1.2.4.3.3 Activity: Implement Test Suite- Examine candidate Test Suites- Examine related Tests and Target Test Items- Identify Test dependencies- Identify opportunities for reuse- Apply necessary infrastructure utilities- Determine recovery requirements- Implement recovery requirements- Stabilize the Test Suite- Maintain traceability relationships- Evaluate and verify your results


1.1.2.4.3.3.2 ArtifactThe results should be recorded in Test Suite.

1.1.2.4.3.4 Activity: Execute Test Suite- Setup test environment to known state- Set execution tool options- Schedule Test Suite execution- Execute Test Suite- Evaluate execution of Test Suite- Recover from halted tests- Inspect the Test Logs for completeness and accuracy- Restore test environment to known state- Maintain traceability relationships


845846847848849850851852853854855856857858859860861862

863864

865866867

868869870871872873874875876877878

879880

881882883

884885886887888889890891892893

5657

- Evaluate and verify your results


1.1.2.4.3.4.2 ArtifactThe results should be recorded in Test Log.

1.1.2.4.3.5 Activity: Analyse Test Failures- Examine the Test Logs- Capture nontrivial incident data- Identify procedural errors in the test- Locate and isolate failures- Diagnose failure symptoms and characteristics- Identify candidate solutions- Document you findings appropriately- Evaluate and verify your results


1.1.2.4.3.5.2 ArtifactThe results should be recorded in Change Request.

1.1.2.4.3.6 Activity: Determine Test Results- Examine all test incidents and failures- Create and maintain Change Requests- Analyze and evaluate status- Make an assessment of the current quality experience- Make an assessment of outstanding quality risks- Make an assessment of test coverage- Draft the Test Evaluation Summary- Advise stakeholders of key findings- Evaluate and verify your results


1.1.2.4.3.6.2 ArtifactThe results should be recorded in Test Evaluation Summary and Test Results.

1.1.2.4.4 Workflow Detail: Improve Test Assets

1.1.2.4.4.1 Activity: Define Test Approach (Refinement)- As in “Define Test Approach” activity found in “Define Mission” Workflow



894

895896

897898899

900901902903904905906907908

909910

911912913

914915916917918919920921922923

924925

926927928

929

930931

932933

5859

1.1.2.4.4.1.2 ArtifactThe results should be recorded in Test Environment Configuration, Test Plan and Test Strategy.

1.1.2.4.4.2 Activity: Identify Test Ideas (Refinement)- As in “Identify Test Ideas” activity found in “Define Mission” Workflow


1.1.2.4.4.2.2 ArtifactThe results should be recorded in Test-Ideas List.

1.1.2.4.4.3 Activity: Prepare Guidelines for the Project- Identify the Project's Needs for Guidelines- Prepare Guidelines for Project Use- Maintain Guidelines

1.1.2.4.4.3.1 RoleProcess Engineer

1.1.2.4.4.3.2 ArtifactThe results should be recorded in Project Specific Guidelines.


934935936937

938939

940941

942943944

945946947948

949950

951952953

6061

1.1.2.5 Discipline: Deployment

Deployment

•Plan Deployment•Develop Deployment Plan

•Develop Support Material•Develop Training Material•Develop Support Material

•Produce Deployment Unit (WS)•Write Release Notes•Develop Installation Artifacts•Create Deployment Unit (WS)•Deploy WS to identified app servers •Publish WS (optional)

Deployment

•Plan Deployment•Develop Deployment Plan

•Develop Support Material•Develop Training Material•Develop Support Material

•Produce Deployment Unit (WS)•Write Release Notes•Develop Installation Artifacts•Create Deployment Unit (WS)•Deploy WS to identified app servers •Publish WS (optional)


Figure 7: Deployment Workflow

1.1.2.5.1 Workflow Detail: Plan Deployment

1.1.2.5.1.1 Activity: Develop Deployment Plan- Plan how to produce the software- Plan how to package the software- Plan how to distribute the software- Plan how to install the software- Migration- Providing help and assistance to the users

1.1.2.5.1.1.1 RoleDeployment Manager

1.1.2.5.1.1.2 ArtifactThe results should be recorded in Deployment Plan.


954

955956

957

958

959960961962963964965

966967

968969970

6263

1.1.2.5.2 Workflow Detail: Develop Support Material

1.1.2.5.2.1 Activity: Develop Training Material- Develop an outline for the training materials- Write the training materials

1.1.2.5.2.1.1 RoleCourse Developer

1.1.2.5.2.1.2 ArtifactThe results should be recorded in Training Materials.

1.1.2.5.2.2 Activity: Develop Support Material- Develop end-user support material

1.1.2.5.2.2.1 RoleTechnical Writer

1.1.2.5.2.2.2 ArtifactThe results should be recorded in End-User Support Material.

1.1.2.5.3 Workflow Detail: Produce Deployment Unit (Web service)

1.1.2.5.3.1 Activity: Write Release Notes- Describe the major new features and changes in the release- Describe any known bugs and limitations or workarounds to using the product

1.1.2.5.3.1.1 RoleDeployment Manager

1.1.2.5.3.1.2 ArtifactThe results should be recorded in Release Notes.

1.1.2.5.3.2 Activity: Develop Installation Artifacts- Produce all the software required to install and uninstall the product quickly, easily

and safely without affecting other applications or system characteristics


1.1.2.5.3.2.2 ArtifactThe results should be recorded in Installation Artifacts.

1.1.2.5.3.3 Activity: Create Deployment Unit (Web service)- Create a deployment unit that is sufficiently complete to be downloadable, installable

and run on a node as a group


971

972973974

975976

977978979

980981

982983

984985986

987

988989990

991992

993994995

996997998

9991000

100110021003

100410051006

6465

- A deployment unit consists of a build (an executable collection of components), documents (end-user support material and release notes) and installation artifacts

1.1.2.5.3.3.1 RoleConfiguration Manager

1.1.2.5.3.3.2 ArtifactThe results should be recorded in Deployment Unit.

1.1.2.5.3.4 Activity: Deploy Web Service to identified app servers- Identify the service end-point- Create the deployment script and configure the deployment parameters- Deploy the Web service- Generate the WSDL



1.1.2.5.3.5 Activity: Publish Web service [optional]- Identify the UDDI registry- Prepare the information needed for publishing- Publish the Web service in the UDDI registry- Perform a find and bind to test




10071008

10091010

101110121013

10141015101610171018

10191020

102110221023

10241025102610271028

10291030

103110321033

6667

2 References2.1 Normative

1.

2.2 Non-Normative1. “Rational Unified Process”, Version 2003.06.00.65, IBM-Rational Software.

2. “Rational Unified Process for Developing Web Services”, Version 1.0, Java Smart Services Laboratory and Rational Software Pte. Ltd., Aug 2003.


1034

10351036

10371038103910401041

6869

Appendix A. AcknowledgmentsThe following individuals were members of the committee during the development of this documentation: Ravi Shankar, CrimsonLogic Pte. Ltd. Jagdip Talla, CrimsonLogic Pte. Ltd. Andy Tan, Individual Roberto Pascual, IDA


1042

104310441045104610471048

1049

7071

Appendix B. Revision HistoryRev Date By Whom Whatwd-01 2004-09-30 Lai Peng CHAN

Chai Hong ANGInitial version

2004-12-23 Chai Hong ANG Split the original document into two


1050

1051

7273

Appendix C. NoticesOASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS Open 2004. All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself does not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


1052

105310541055105610571058105910601061

106210631064

1065

106610671068106910701071107210731074

10751076

10771078107910801081

1082

7475

€¦ · Web viewWorking Draft 02, 23 December 2004. Document identifier:...

Documents

Transcript of €¦ · Web viewWorking Draft 02, 23 December 2004. Document identifier:...