Difference between revisions of "Notice time"
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
!Sub-attribute!!Camel Code Identifier!!multiplicity!!sequential | !Sub-attribute!!Camel Code Identifier!!multiplicity!!sequential | ||
|- | |- | ||
− | |[[NTCHRS]]||noticeTimeHours||0.. | + | |[[NTCHRS]]||noticeTimeHours||0..*||1 |
|- | |- | ||
− | |[[NTCTXT]]||noticeTimeText||0.. | + | |[[NTCTXT]]||noticeTimeText||0..*||1 |
|- | |- | ||
− | |[[OPERAT]]||operation||0.. | + | |[[OPERAT]]||operation||0..*||1 |
|} | |} | ||
That enabled us to model constructions like:<br> | That enabled us to model constructions like:<br> | ||
Notice is required 24 hrs in advance or when leaving the previous port if closer. | Notice is required 24 hrs in advance or when leaving the previous port if closer. |
Revision as of 06:31, 29 October 2009
jens 09:54, 25 October 2009 (UTC) Notice time can become a complex attribute using the operation idea Raphael proposed and which is been used at Under Keel clearance. The construction can be like to following
Sub-attribute | Camel Code Identifier | multiplicity | sequential |
---|---|---|---|
NTCHRS | noticeTimeHours | 0..* | 1 |
NTCTXT | noticeTimeText | 0..* | 1 |
OPERAT | operation | 0..* | 1 |
That enabled us to model constructions like:
Notice is required 24 hrs in advance or when leaving the previous port if closer.