Template:— representing_structured_task_sequential (rep_struct_task_seq) Date: 2009/03/20 15:55:45
Revision: 1.8
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssues

Issue raised against: representing_structured_task_sequential

GENERAL issues

Closed issue Issue: JNN-1 by Johan Nielsen (2008-02-27) editorial issue
Resolution: Accept. Status: closed

Checklist clause 30: In Figure 1 the assigning_identification for task name and task version identification has been mixed.
Comment: (Johan Nielsen 2008-02-27)
Fixed.

Closed issue Issue: JNN-2 by Johan Nielsen (2008-02-27) minor_technical issue
Resolution: Accept. Status: closed

Checklist clause 50: Parameters Task_method_version.of_task_method and Task_method_version.content not set in path.
Comment: (Johan Nielsen 2008-02-27)
Fixed.

Closed issue Issue: JNN-3 by Johan Nielsen (2008-02-27) minor_technical issue
Resolution: Reject. Status: closed

Checklist clause 52: Input paramter @task_step should be a list.
Comment: (Johan Nielsen 2008-02-27)
This is an issue against the path language. Deferred for now.

Closed issue Issue: DNV-1 by Fredrik Lied Larsen, DNV (2008-3-5) minor_technical issue
Resolution: Accept. Status: closed

Issue file: C:\DEXlib\issues\template_issues_rep_struc_task_seq.xls Template: representing_structured_task_sequential Check list clause: 29 Parameter objective relating a task_method to a task_objective is not explicitly shown.
Comment: (Leif Gyllstrom 2008-03-05)
Rejected. Parameter objective relating a task_method to a task_objective is an optional attribute, not instantiated by this template and therefore not part of the input parameters ! Task_objective is just shown in the EXPRESS-G diagram, in order to present an EXPRESS-G diagram that is conformant with the AP239 Long Form.

Closed issue Issue: DNV-2 by Fredrik Lied Larsen, DNV (2008-3-5) major_technical issue
Resolution: Accept. Status: closed

Issue file: C:\DEXlib\issues\template_issues_rep_struc_task_seq.xls Template: representing_structured_task_sequential Check list clause: 30 Parameter task_step relates to Task_element, but input parameter task_step relates to entity Task_step. The latter should be shown in the EXPRESS-G diagram as well, otherwise Task_element_sequence can contain a list of Task_element_sequence. That is not correct functionality for this template.
Comment: (Leif Gyllstrom 2008-03-05)
Rejected. Defining the input parameter task_step to of type Task_step restricts the usage. Making the proposed change to the EXPRESS-G diagram would create an EXPRESS-G diagram that is not conformant with the AP239 Long Form.

Closed issue Issue: DNV-3 by Fredrik Lied Larsen, DNV (2008-3-5) major_technical issue
Resolution: Accept. Status: closed

Issue file: C:\DEXlib\issues\template_issues_rep_struc_task_seq.xls Template: representing_structured_task_sequential Check list clause: 51 Description for task_name_class_name relates task_name to Task_method_version not Task_method. Shall this template have a name or not? This must be harmonized between templates representing_task_simple and this template, and possibly referencing_task.
Comment: (Leif Gyllstrom 2008-03-05)
Accepted. Changed to Task_method.

Closed issue Issue: DNV-4 by Fredrik Lied Larsen, DNV (2008-3-5) minor_technical issue
Resolution: Accept. Status: closed

Issue file: C:\DEXlib\issues\template_issues_rep_struc_task_seq.xls Template: representing_structured_task_sequential Check list clause: 53 Task_id_class_name has entry classes Task_method_identification_code and Task_method_name, should only be Task_method_identification_code if we have task_name as well as task_id.
Comment: (Leif Gyllstrom 2008-03-05)
Accepted. Changed to Task_method.

Closed issue Issue: DNV-5 by Fredrik Lied Larsen, DNV (2008-3-5) minor_technical issue
Resolution: Accept. Status: closed

Issue file: C:\DEXlib\issues\template_issues_rep_struc_task_seq.xls Template: representing_structured_task_sequential Check list clause: 68 The example only displays one instance of entity Task_step but the template defines the list from Task_element_sequence to be [2:?].
Comment: (Leif Gyllstrom 2008-03-05)
Accepted. Added an additional Task_step to the instantiation diagram.

Closed issue Issue: PBM-1 by Peter Bergström (2009-03-17) minor_technical issue
Resolution: Accept. Status: closed

parameter task_step only allows task_steps to be part of the list of task_elements. should be changed to "task_element".
Comment: (Peter Bergström 2009-03-18)
Accepted. Opened up the task_step parameter to allow for any task_element in the list..

Closed issue Issue: PBM-2 by Peter Bergström (2009-03-18) minor_technical issue
Resolution: Accept. Status: closed

The name of the parameter task_step should be changed to become "task_steps", plural, it is not clear now that the template ends in a list of task_steps. This change requires changes at all places where template is used.
Comment: (Tim Turner 2010-03-10)
The cardinality is provided by the EXPRESSG diagram fig 1 and in the instance diagrams fig 3 and 4. Furthmore, the aggregate box appears when the template attribute to Task_step is populated in tools such as GI. Plurals are generally not used when referring to an object in EXPRESS because the cardinality is expressed separately. It means that some template specifications need to be read/reviewed before use.