Trade Agreement.Buyer.Trade Party
From Gs Uno Project
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | '''Trade | + | '''Trade Agreement. Buyer. Trade_ Party''' |
| - | + | == Definition == | |
| + | bla | ||
''Business Requirement'' | ''Business Requirement'' | ||
| Line 7: | Line 8: | ||
ID: ''sequence number within message or group'' | ID: ''sequence number within message or group'' | ||
Short name: ''short term describing the requirement'' | Short name: ''short term describing the requirement'' | ||
| - | |||
== Requirement == | == Requirement == | ||
''Requirement text, see [[BRAD best practices]] for instuctions on how to write a requirement.'' | ''Requirement text, see [[BRAD best practices]] for instuctions on how to write a requirement.'' | ||
Revision as of 14:43, 20 February 2009
Trade Agreement. Buyer. Trade_ Party
Contents |
Definition
bla
Business Requirement
Message: name of message to which requirement applies Group: name of requirements group within message ID: sequence number within message or group Short name: short term describing the requirement
Requirement
Requirement text, see BRAD best practices for instuctions on how to write a requirement.
Rationale
Rationale, see BRAD best practices for instuctions on how to write a rationale.
Business Rules
Example
Example
Sources
list any relevant sources
Realisation Status
status of the requirement, pick on of following: CANDIDATE, APPROVED, SUBMITTED, REALISED
UN/CEFACT mapping
mapping to message or library.
GS1 mapping
ODEN: official dictionary entry name in GDD
BT: default business term in GDD
GDD: [1]
