Software Architecture
Requirements Analysis
Remote Service Call
  Contents

PDF version   PostScript version

Mapping to an Object Model

An important aspect of the use case model presented above is the predominance of a few use cases, common to both the client and the server subsystems. This commonality is expressed with both the inclusion and extension semantics. As a consequence, the class models (Figure B.1) for both modules share most of their elements.
Two classes are however noticeably different: the HTTP networking class, and the SOAP message representation and generation class. As discussed in Section 2.1.2, the client module only requires a lightweight implementation of HTTP POST. On the other hand, the server must provide a full implementation of the protocol--and support concurrent connections.
The class Message encapsulates the representation and creation process of the generic elements of a SOAP message. Two subclasses--ReqMsg and RespMsg--complement it with the elements specific to request and response messages.