Issue 13031: Section 7.3 hierarchy (almas-ftf) Source: (, ) Nature: Revision Severity: Critical Summary: Section 7.3: The hierarchy is defined in the Receiver Hierarchy Configuration File and is alert independent, so for all templates the same. Therefore RKParentType should be removed from ReceiverKind related to AlertTemplate in order to prevent a lot of redundant information. Solution: Remove RKParentType from ReceiverKind related to AlertTemplate.Instead, introduce a seperate class ReceiverHierarchy. Note that this has quite an impact on the PSMs! Resolution: Revised Text: Actions taken: October 31, 2008: received issue April 30, 2009: Deferred Discussion: This change would have a significant impact upon the PSMs and as such it was deferred. There may be some redundant information as a result of this. Suggest handled in an RTF End of Annotations:===== m: webmaster@omg.org Date: 31 Oct 2008 05:04:40 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: A.G. van der Meer Company: Thales-NL mailFrom: bert.vandermeer@nl.thalesgroup.com Notification: Yes Specification: ALMAS Specification Section: 6.2, 7.3 FormalNumber: dtc/2008-04-01 Version: Beta 1 RevisionDate: 04/01/2008 Page: 13, 40 Nature: Revision Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322) Description Section 7.3: The hierarchy is defined in the Receiver Hierarchy Configuration File and is alert independent, so for all templates the same. Therefore RKParentType should be removed from ReceiverKind related to AlertTemplate in order to prevent a lot of redundant information. Solution: Remove RKParentType from ReceiverKind related to AlertTemplate.Instead, introduce a seperate class ReceiverHierarchy. Note that this has quite an impact on the PSMs!