Sriram Srinivasen wrote:
>I once did a project for a large shipping company a couple of years
>back where I was tasked with coming up with a common object model
>across the company. This is obvious in hindsight, but I learnt the
>hard way that no two departments had a common understanding of a
>simple object like an aircraft. For a long-range planner, the average
>speed and the containing capacity in gross terms is all that
>matters. The short-range planner had to worry about the tail number,
>flight and maintenance hours, breakdown of capacity by freight type,
>taxiing speeds vs. cruising speeds etc. The accounting department
>couldn't be bothered with any of these details. Their focus was on gas
>consumption, depreciation etc. Neither the schema nor the
>functionality was reusable across departments. The only thing we could
>possibly conclude was that where there was an overlap (aircraft tail
>number, for example), the data should be kept in one consistent
>format. Reuse of business components is a myth. It is not something
>that can be helped by EJB or MTS.
I couldn't disagree more. I see lots of customers who reuse business
components all the time. Not only that but the components they are reusing
were built using CICS COBOL 10 or 20 years ago.
Developing from an enterprise wide common object model and developing
reusable business components are COMPLETELY different things.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
