@BR-Requirements Template

From Gs Uno Project

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

Contents 1 Requirement 1.1 Rationale 1.2 Business Rules 1.3 Example 1.4 Sources 2 Realisation Status 2.1 UN/CEFACT mapping 2.2 GS1 mapping

[edit] Requirement

Requirement text, see BRAD best practices for instuctions on how to write a requirement.

[edit] Rationale

Rationale, see BRAD best practices for instuctions on how to write a rationale.

[edit] Business Rules

[edit] Example

Example

[edit] Sources

list any relevant sources

[edit] Realisation Status

status of the requirement, pick on of following: CANDIDATE, APPROVED, SUBMITTED, REALISED

[edit] UN/CEFACT mapping

mapping to message or library.

[edit] GS1 mapping

ODEN: official dictionary entry name in GDD

BT: default business term in GDD

GDD: [1]