swimEC swimEC StandardsStandards Structure
Standards Structure
A specification, or standard, is referred to as a Message Implementation Guideline (MIG). A MIG defines a logical (implementation independent) and physical description of a message standard.
Each MIG contains all of the information required by a participant to enable a swimEC transaction to be completed, including:
- standards for a specific transaction (eg rollover, registration & contribution, unit trust distributions)
- financial EDI standards eg direct credit
- workflow
- business rules
- codes
- protocols
- processing rules.
Each swimEC message standard is produced in the same manner and specification format - by using eBOM. The eBOM artifacts which comprise a MIG are as follows:
- Industry Model - and specific messages of interest
- Roles and Responsibilities of key Stakeholders
- Data Model
- Business Scenarios
- Field Specifications
- Integrity Constraints
- Payment Linkage
- Payment Message
- Workflow (ACK) Message
- Work practices - eg. SLA's, error handling
- Message Processing Guidelines & Protocols
- Examples
The representation of each artifact above is based on widely adopted representations. The representations are shown below:
MIGS Artifact |
Representation |
Industry Model – and specific messages of interest |
UML Collaboration diagram |
Roles and Responsibilities of key Stakeholders |
UML Role Hierarchy |
Data Model |
UML Class Models |
Business Scenarios |
Industry Sector / Business Line variation |
Field Specifications |
UML Class Attributes (Formatting, Types, Lengths, mandatory constraints) |
Integrity Constraints |
Business Rule Specification Language |
Payment Linkage |
Linkage to Payment type and consideration – eg. BECS & BPAY |
Payment Message |
Payment System format rules + Reconciliation usage. |
Workflow (ACK) Message |
UML Class Models
UML Sequence Diagrams |
Work practices (eg. SLAs) |
Business Rule Specification Language |
Message Processing Guidelines & Protocols |
File naming conventions
Physical flows and processing |
Message Dictionary
All the fields and individual message elements that comprise each swimEC message standard are constructed from the same dictionary. This ensures that all swimEC message standards are built from the same message components – and that consistency is maintained between the message standards. For instance, all message standards are based on the same address message elements and fields. top
Page Last Modified: 8 March 2004
| © Copyright 2004 swimEC Council |
|
 |
Disclaimer
Subject to any statutory provisions which may not be excluded by law, the swimEC Council will not be held liable for any damages whatsoever resulting from any action arising in connection with the use of any content of this site or its publication, including any action for copyright infringement or defamation. |
|
