<<XSDcomplexType>> Contact {Analysis}

Documentation
Notes: 3/3/03
We are assuming that the usage of the contact is going to be much greater in the exchange of business documents than in the maintenance of an address book.
If this is the case, the more structured representation of Person Name that exists within the Person component is felt to be unlikely to be useful. Recommendation is to keep the Name construct simple for higher reuse where the need for the structure is less apparrent.



Parent PackageContactAbstractNo
Export ControlPublicAccessLink Class forNone
Class KindNormalClassCardinalityn
Space ConcurrencySequential
PersistenceNo  


Nested ClassesNewClass


Operations
NameSignature
RegisterContactInformation RegisterContactInformation ()
provideDepartment provideDepartment ()
provideJobTitle provideJobTitle ()
provideContactInformation provideContactInformation ()


Attributes
NameTypeInitial Value
IdIdentifierType 
NameNameType 
Job TitleTextType 
DepartmentTextType 


Associations
NameMy RoleMy ClassOther RoleOther Element
Telephone--Not Named--Contact--Not Named--ContactTelephoneNumber
Pager--Not Named--Contact--Not Named--ContactTelephoneNumber
MobilePhone--Not Named--Contact--Not Named--ContactTelephoneNumber
Fax--Not Named--Contact--Not Named--ContactTelephoneNumber
PostalAddress--Not Named--Contact--Not Named--PostalAddress
Email--Not Named--Contact--Not Named--ContactEmailAddress
InstantMessengerId--Not Named--Contact--Not Named--ContactInstantMessengerId
URI--Not Named--Contact--Not Named--ContactURI
--Not Named----Not Named--Contact--Not Named--ContactTelephoneNumber
--Not Named----Not Named--Contact--Not Named--ContactMethods
--Not Named----Not Named--Contact--Not Named--Party


Dependencies
NameClassSupplier
Provide Contact InformationContactOrder Entry Clerk
Review Supplier Contact InformationContactAR Clerk