November Production to January 2017 Beta traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
|
November Production to January 2017 Alpha traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
AssociationReference files (full, delta and snapshot) | 1 | ||
| AttributeValue (full, delta and snapshot) | 344 | ||
| Description-DA (full, delta and snapshot) | 695 | DK do not keep records of the number of components they have updated. According to the traceability service, between December and March (their editing cycle for this release) they changed approx 350 concepts - HOWEVER in almost every concept they inactivated the old Description and created a new Description, so multiple changes per concept. The good news is that this matches the diff report, which shows 349 active record changes (i.e.) new description records, and 346 inactivation records. | |
| Language-DA (full, delta and snapshot) | 693 | ????????? Why 2 less than Description records??????? | |
| ModuleDependency (full, delta and snapshot) | 2 | 2 new March 2017 records added as expected | |
| Relationship (full, delta and snapshot) | 25 | No new stated relationships were changed as part of the DK editing cycle, and no concepts were updated. These changes are therefore unexpected. Looking into them they appear to be partially a result of role group churn (due to the known issue in the classifier wrapper), but I've also found several which are new to the March release, and also some that were in the November release as inactive yet have now been activated (with all identical fields including the Role group) in the March release. Some have even been born inactive in this release... Further investigation therefore in progress... We discovered that the differences are due to the following:
|