Template:— representing_breakdown_structure (rep_bkdn_struct)
Capability:representing_breakdown_structure		 Date: 2009/04/06 15:58:01
Revision: 1.23
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssuesin situ

Issue raised against: representing_breakdown_structure

GENERAL issues

Closed issue Issue: RBN-1 by Rob Bodington (07-02-21) minor_technical issue
Resolution: Accept. Status: closed

Breakdown_element_usage has an attribute name. This is missing from Figure 1 and the instantiation path
Comment: (Rob Bodington 07-04-23)
Corrected

Closed issue Issue: TR-1 by Trisha Rollo (07-06-06) minor_technical issue
Resolution: Accept. Status: closed

The short name does not comply with validation requirements
Comment: (Trisha Rollo 07-06-06)
Short name changed to comply with validation rules.

Closed issue Issue: TR-2 by Trisha Rollo (07-06-06) minor_technical issue
Resolution: Accept. Status: closed

Figure one shows characterizations therefore does not comply with validation rules
Comment: (Trisha Rollo 07-06-06)
Characterizations removed from figure 1

Closed issue Issue: TR-3 by Trisha Rollo (07-06-06) editorial issue
Resolution: Accept. Status: closed

Diagrams showing characterizations would help understanding.
Comment: (Trisha Rollo 07-06-06)
Characterization diagram added

Closed issue Issue: DNV-11 by Tore Hartvigsen, DNV (2007-8-6) editorial issue
Resolution: Accept. Status: closed

Issue file: TORHAR_template_issues.xls Template: representing_breakdown_structure Check list clause: 20 "in model review"
Comment: (Tim Turner 2008-2-29)
Fixed

Closed issue Issue: DNV-12 by Tore Hartvigsen, DNV (2007-8-6) editorial issue
Resolution: Accept. Status: closed

Issue file: TORHAR_template_issues.xls Template: representing_breakdown_structure Check list clause: 19 'Organization' name not name of 'person'.
Comment: (Tim Turner 2008-2-29)
Fixed

Closed issue Issue: DNV-13 by Tore Hartvigsen, DNV (2007-8-6) editorial issue
Resolution: Accept. Status: closed

Issue file: TORHAR_template_issues.xls Template: representing_breakdown_structure Check list clause: 9 Fig 1: "View_definition_realtionship"
Comment: (Tim Turner 2008-2-29)
Fixed

Closed issue Issue: DNV-14 by Tore Hartvigsen, DNV (2007-8-6) editorial issue
Resolution: Accept. Status: closed

Issue file: TORHAR_template_issues.xls Template: representing_breakdown_structure Check list clause: 24 More text would be appreciated
Comment: (Tim Turner 2008-2-29)
Minor elaboration added.

Closed issue Issue: TJT-1 by Tim Turner, LSC (2007-12-6) minor_technical issue
Resolution: Accept. Status: closed

It should NOT be allowed to instantiate multiple breakdown_element_usage(s) between the same parent and child breakdown_elements! Consider if each breakdown_element_definition in the breakdown should be unique? Should the breakdown_element_usage(s) also be unique (in terms of the elements that they relate)?
Comment: (Tim Turner 2008-2-29)
The template does not instantiate the element definitions. However, this may be an issue for the AP239 ARM.