Release Notes for Industry Models BFMDW/BDW/FMDW for m1

Transcription

1 Release Notes for Industry Models BFMDW/BDW/FMDW for m1

2 Table of Contents Release Notes for BFMDW/BDW/FMDW for m1...3 Information...3 Features and Fixes since last release...3 Feature Enhancements Added (8.5.0)...3 Fixes/Defects Resolved (8.5.0)...3 Known Model Issues / Limitations...4 Known IDA Issues / Limitations...5

3 Release Notes for BFMDW/BDW/FMDW for m1 Version: Date: 30 August 2012 Information Following are the release notes for version of BFMDW/BDW/FMDW for m1. This offering includes: An m1 Model containing: the FSDM Analytical Requirements Application Solution Templates An Atomic Warehouse Model, including System of Record, Summary and Feedback entities A Dimensional Warehouse Model, including Transactional, Aggregate and Dimensional entities Note: IDA and ERwin equivalents of the Atomic Warehouse Model and Dimensional Warehouse Model are also included For instructions on the usage of the Industry Models BFMDW/BDW/FMDW for m1, please refer to the Information Center. Note: The following list of issues pertains to the BFMDW model. The BDW and FMDW models may have a subset of these issues. Features and Fixes since last release Feature Enhancements Added (8.5.0) 6824 Provide the Dimensional Model in m1 Note: For a detailed description of Banking and Financial Markets content coverage added in version 8.5.0, please see the What s New section of the Information Center. Fixes/Defects Resolved (8.5.0) MD00033 Mappings missing from FSDM to LDM objects MD00038 FK Physical Name for Classification Values are incorrect in some cases MD00044 Product Asset Type should be moved under Product Classification in the LDM MD00050 Instrument Price Quotation should be a subtype of condition MD00053 Involved Party Credit Risk Profile missing Involved Party Id MD00054 Definition misleading for "Software" as a Resource Item Type In FSDM, Time Band Group has two parents 7537 Security Arrangement has extra link to PEWUIDC 8866 Involved Party Lifecycle Status Id missing on Involved Party entity

4 Known Model Issues / Limitations 9467 In the IDA model, the labels on relationship lines from fact entities to dimensions are overlapping when there are multiple roles. Work-around: the user can rearrange the diagrams so that labels are no longer overlapping 8572 Coexisting super / sub type dimensions There are Dimensions in the Dimensional Model which are in effect subtypes of each other, for example Arrangement' and 'Loan Arrangement'. The main consideration here is that these 2 entities for example could both contain what is in effect the same instance of a Loan, but 'Loan Arrangement' would carry a greater level of detail via the more descriptive attributes on this entity. The super / sub type Dimensional entities need to be rationalised Dimensional entities inheriting attributes that do not necessarily apply. For example Web Page has Eligible IRB Collateral Flag and Eligible Standardized Collateral Flag. This issue occurred due to the requirement to ensure that dimensions in the DWM directly reflect the full inheritance hierarchy in the AWM. A workaround is to remove those attributes that do not apply to the conformed dimension Credit Risk Analysis has multiple relationships with Currency that should be reduced to one such relationship. The intention was to allow the measures to be shown in multiple currencies, but for this to work there would need to be a duplication of the facts in the fact table - one for each currency. A workaround is to remove one of the relationships with Currency duplicate foreign keys in AWM model DDL when generated for DB2 The default rollup strategy for the AWM is to roll all subtypes into the entity that is at the top of the inheritance hierarchy. In the case of 3 foreign key attributes on subtypes of Arrangement, rolling the subtypes results in duplicate foreign key constraints, as different subtypes have the same named attribute. In most cases, the physical rollup / rolldown strategy will be reviewed for all entities that are to be implemented. If separate tables are used for subtypes, this DDL error will not occur. Alternatively, if the user wants to roll up all subtype entities, they can ignore this error, as in effect the requirement would be to only have one such attribute physical columns contain carriage return characters that cause errors in running the generated DDL. These errors are due to a different character code being used for carriage returns. A workaround is to edit the DDL and reformat the comment text Operational Risk Assessment is called Operational Risk Assessment(42984) in the m1 model. This is caused because of the existence of a non-fact table in the model, (which is a subtype of Assessment) and the decision that a fact table should always have the same name as the Analytical Requirement it supports.

5 A workaround is to rename either the AWM entity or the Fact entity. Known IDA Issues / Limitations Invalid line feed character after transformation to physical data model Relationship names not transformed when transforming from LDM to PDM Note: All of these IDA issues are resolved by JR43428patch.zip.