WebSphere and .Net Interoperability Using Web Services

230 WebSphere and .Net Interoperability Using Web Services

11.1 Mergers and Acquisitions scenario

The first step in the solution building process is the use case definition. In this

redbook, we decided to design and implement only those use cases that are

most useful in looking at interoperability between the WebSphere and Microsoft

.Net implementations of Web services technology.

Furthermore, we decided to select use cases having different levels of

complexity. The aim is to give the correct answer to designers and developers in

the following two cases:

򐂰 When the interoperability is very simple to achieve and detail is needed only

at development time. In this case, a typical problem is the use of a specific

SOAP format or a certain

type for an input/output variable because of the

different programming languages supported by WebSphere and Microsoft

.Net.

򐂰 When some decisions and design choices have an impact across the

application environment and decisions must be taken earlier during the

design phase.

This can happen when more complex specifications are used, for example

WS-Security. When using more complex specifications, it is necessary to

verify that they can be considered interoperable or whether there are some

limits in the interoperability which may impact the application design.

11.1.1 Use cases overview

For the Mergers and Acquisitions scenario, as part of the ClaimProcess

application, we identify the following actors:

򐂰 Customer - The insurance policy owner

򐂰 Customer service - An LGI employee who works in the contact center and

gives remote assistance to customers by phone

򐂰 Agent - An LGI employee who works in a generic LGI branch office and gives

assistance to local customers

We also identify a use case:

򐂰 Register claim - All actors listed above can register a claim using an Internet

form provided on the LGI Internet site. The difference between the three

actors is that, while the customer executes the claim registration by himself,

the customer service or agent executes the claim registration on behalf of a

customer but using their own authentication on the system.

Using the Rational XDE tool, which is a plug-in of WebSphere Studio Application

Developer, we design the use case model as shown in Figure 11-1 on page 231.

Chapter 11. Designing the scenarios 231

Figure 11-1 Mergers and Acquisitions scenario use case model

11.1.2 Actors

Table 11-1 provides details about the customer actor.

Table 11-1 Customer actor details

Table 11-2 on page 232 provides details about the customer service actor.

Note: Explaining how to use WebSphere Studio Application Developer and

Rational XDE plug-in to design and implement scenarios’ use cases is beyond

the scope of this publication. More information can be found in WebSphere

Version 5 Application Development Handbook, SG24-6993-00

Re

g

ister Clai

m

Ag

ent

Customer

Customer service

Actor name Customer

Brief description Customer: a person who has signed a policy with LGI

or DCI.

Status Primary

Relationships

Associations to use cases Use case 001: Register claim

232 WebSphere and .Net Interoperability Using Web Services

Table 11-2 Customer service actor details

Table 11-3 provides details about the agent actor.

Table 11-3 Agent actor details

11.1.3 Use case 001: Register claim

Table 11-4 provides details about the register claim use case.

Table 11-4 Use case 001: Claim registration

Actor name Customer service

Brief description An LGI or DCI employee who works in the customer

service department answering to customers phone

calls and providing them remote assistance

Status Primary

Relationships

Associations to use cases Use case 001: Register claim

Actor name Agent

Brief description An LGI or DCI employee who is responsible to contact

customers, propose and sign policies, and provide

local assistance to the customer during all policy

validation time

Status Primary

Relationships

Associations to use cases Use case 001: Register claim

Use case name Use case 001: Register claim

Subject area Claim system

Business event A claim is submitted following up a car accident

occurred to a LGI or DCI customer.

Actors 򐂰 Customer

򐂰 Customer service

򐂰 Agent