Common Use Cases
Requirements Analysis
SOAP RPC
  Contents

PDF version   PostScript version

Requirement Formalisation

A general order consideration is standing out of the diagram in Figure 2.1: the number of use cases (five) is small, but the complexity of each operational use case is high. This is an essential feature of frameworks, which must achieve a substantial amount of processing to handle a complex aspect of the system on behalf of the client application. In the case of middleware frameworks in general--and of XMLbroker in particular, this complexity is defined by the need to provide a suitable level of transparency for remote method calls.

Figure 2.1: Global view of use cases

We will now review each use case in some detail, starting with their three fundamental constituents: SOAP interpretation, SOAP message generation and Java Interpretation.