Difference between revisions of "Notice time"
Jump to navigation
Jump to search
m |
m |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
Notice time can become a complex attribute using the operation idea Raphael proposed and which is been used at Under Keel clearance. | 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 | The construction can be like to following | ||
| Line 6: | Line 5: | ||
!Sub-attribute!!Camel Code Identifier!!multiplicity!!sequential | !Sub-attribute!!Camel Code Identifier!!multiplicity!!sequential | ||
|- | |- | ||
| − | |[[NTCHRS]]||noticeTimeHours||0.. | + | |[[NTCHRS]]||noticeTimeHours||0..*||1 |
|- | |- | ||
|[[NTCTXT]]||noticeTimeText||0..1||n/a | |[[NTCTXT]]||noticeTimeText||0..1||n/a | ||
| Line 14: | Line 13: | ||
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 | + | Notice is required 48, 24, 6 hrs in advance or when leaving the previous port whichever is less.<br> |
| + | A further instance can be: Confirmation 2 hrs before arriving the xx-position.<br> | ||
| + | |||
| + | |||
| + | Remark: Product specifications which allow multiplicity > 1 for this attribute should state whether the order of values has any significance and explain the significance. | ||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | |||
| + | {| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left" | ||
| + | !David!!Raphael!!others!!Jens | ||
| + | |- style="background:white; color:black" | ||
| + | |DA Y/N | ||
| + | |RMM Y/N | ||
| + | |others Y/N | ||
| + | |Y | ||
| + | |} | ||
| + | |||
| + | |||
| + | Jens (BSH); I agree with that proposal. Looks pretty much better than our initial ideal of notice time (refer to the attribute section) | ||
Latest revision as of 10:34, 5 January 2010
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 | n/a |
| OPERAT | operation | 0..1 | n/a |
That enabled us to model constructions like:
Notice is required 48, 24, 6 hrs in advance or when leaving the previous port whichever is less.
A further instance can be: Confirmation 2 hrs before arriving the xx-position.
Remark: Product specifications which allow multiplicity > 1 for this attribute should state whether the order of values has any significance and explain the significance.
| David | Raphael | others | Jens |
|---|---|---|---|
| DA Y/N | RMM Y/N | others Y/N | Y |
Jens (BSH); I agree with that proposal. Looks pretty much better than our initial ideal of notice time (refer to the attribute section)