This can be useful when
service speci?¬?cations are needed to be made before they can be applied.
On the code generation side this case was very clear-cut. This was mainly because
the language concepts are already de?¬?ned as elements in XML, and the property
values of the modeling constructs are attributes of the XML elements. CPL servers
already provided an interface speci?¬?cation and thus showed the expected input.
SUMMARY 119
CHAPTER 6
INSURANCE PRODUCTS
In this chapter we describe the speci?¬?cation of ?¬?nancial and insurance products for a
web portal. Unlike the other cases presented in this book, we focus here on modeling
only static structures: The platform already provided the implementation for the
behavior. The allocation of the speci?¬?cation work is interesting in this case. The
modeling language is used by insurance experts, and thus by non-programmers, to
specify various insurance products. The same people then use a generator to produce
the required implementation as Java code for a J2EE web portal.
6.1 INTRODUCTION AND OBJECTIVES
The starting point for this case was a business decision: A company acting as an
information provider and broker was building a portal for handling various ?¬?nancial
products and insurance products. The portal aimed to compare information about
insurance products from different providers and share the data with insurance
companies and other ?¬?nancial service providers.
Pages:
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243