Architecture - CDM Design Draft by Warren for ST

1      Schema Design

1.1         Overview

This section includes the background of writing this document and some basic introduction of TIBCO software stack structure.

1.2         CDM Design Principle

1.2.1       Naming

1.2.1.1      Upper Camel Case Rule

All the element name and attribute naming are following Upper Camel Case standard.

1.2.1.2      Abbreviations

Abbreviation will not apply on any of the element name to give designer the better understanding of the entity meaning.

Following abbreviations has been applied on the attribute naming for each element/complexType in the XSD schema:

Note: Abbreviation will only be applied on the attribute with multiple words. In another words, abbreviation will NOT apply on single word.

e.g.  Original words: individualAddress

                                After applying abbreviation: indivAddr

Original Name	Abbreviation
address	addr
individual	indiv
number	num
description	desc
value	val
code	cd
service	serv
class	clas
count	cnt
measure	meas
amount	amt
text	txt
quantity	qty
original/origin	orig
destination	dest
delivery	dlvr
display	disp
sequence	seq
event	evnt
acknowledge /acknowledging/ acknowledgement	ack
geographic / geography	geog
Special / specialty	spcl
Request	req
instruction / instructor / instructional	inst

1.2.1.2.1   ID vs. reference ID

Id attribute for each entity will be named as ID rather than entityID

1.2.1.3      Target name space

[Company] would follow the following naming pattern for naming target name space:

a.       XSD:

http://[Company].com.au/<FunctionalArea>/CHECKDOC/<EntityName>/<VersionNo.>

b.       WSDL (Abstract):

http://[Company].com.au/<FunctionalArea>/Services/<ServiceName>/Abstract/<VersionNo.>

c.       WSDL (Concrete):

http://[Company].com.au/<FunctionalArea>/Services/<ServiceName>/Concrete/<VersionNo.>

1.3         CDM Design

1.3.1       Overview

Following schema has been designed as the CDM in the TIBCO layer to facilitate the further SOA integration and mediation needs in the ESB layer.

-          Account

-          Address

-          commodity

-          Common

-          Item

-          Location

-          Party

-          Piece

-          Relationship

-          Shipment

-          ShippingEvent

-          State

-          Trip

1.3.2       Design Details

Entitiy Name	Account
SchemaName	Account_v1
Prefix	account
TN	http://[Company].com.au/LDM/Entities/[BusinessContext]/v1