FW: SEDS on ISO 10303-1262

["Rob Bodington" <rob.bodington@eurostep.com>]

This Seds impacts on Task

Regards
Rob

-------------------------------------------   
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1452 810 960
Mobile: +44 (0)7796 176 401


-----Original Message-----
From: Lothar Klein [mailto:lothar.klein@lksoft.com] 
Sent: 15 June 2006 07:55
To: Ron Kolakowski
Cc: Eva Miliuniene; Giedrius Liutkus; Keith A Hunten; Nigel Shaw;
rob.bodington@eurostep.com; sean.barker@baesystems.com; Thomas E Hendrix
Subject: SEDS on ISO 10303-1262

Ron,
Please find below a new SEDS on module 1262.

All others,
Because the addressed content is currently split out into a new module
we should discuss this at the upcomming SC4 meeting in Toulouse.

Lothar

-- 
// Lothar Klein, LKSoftWare GmbH
// Steinweg 1, 36093 Kuenzell, Germany
// +49 661 933933-0, Fax: -2
// url: http://www.lksoft.com

Section 1.  GENERAL INFORMATION (completed by SC4 Secretariat/WG Convener):

SEDS Report Number:
Date Submitted: 2004-09-15
Status:
Assigned WG: 3
SEDS Team Leader: 
SEDS Team Members: 


Section 2.  ENHANCEMENT AND DISCREPANCY INFORMATION (completed by Author of
SEDS Report):

Author: Eva Miliuniene
Email Address: Eva.Miliuniene@lksoft.lt
Part and Clause where Issue Originates:
 ISO 10303-1262 Task Specification, clause 4 and 5
Other Parts Affected by the Issue: 
Related Issues:
Summary/Abstract/Keywords:
 Task_element specialisations
Problem Description:
This is a summary of several partial issues to the same module:

1) The arm.exp file has for entity Task_element an attribute
  notes : OPTIONAL LIST[1:?] OF Advisory_task_step;
which is not visible in clause 4 of the module (arm.xml) or in the
mappings nor in the ARM E-G diagrams.

2) The current data model allows a single instance of Task_element to
be used by more than one Structured_task_element; e.g.
two instances of Task_element_sequence may refer a single task_step as
elements. Many systems do not allow such kinds of
graphs - they can support only clean tree-structures.
Also it is not clear if this is really in mind of this module.

3) For good reasons ISO 10303-49 introduces serial_action_method and its
specialization sequential_method. Both functionalities should also be
available on the ARM level.

4) The mapping of Decision_point to action_method_to_select_from is
wrong. Because Decision_point is a sub-sub-type of Task_element which
maps to task_element also Decision_point has to include task_element
in its mapping somehow.

5) The mapping of Task_element_sequence to Task_element (as elements)
does only establish a SET but not a LIST as required by the ARM. The
order of the elements (needed for LIST) is not clear when reading this
mapping.   

Conditions Under Which the Issue Was Discovered:
  Implementing this module as part of the EUCAM project

Proposed Solution (Optional):
1) Remove attributes notes from Task_element

2) Add a constraint to ensure that a Task_element can only be used by
at least either one of
  Task_element_sequence.elements;
  Concurrent_elements.elements;
  Descision_point.true_case-element, .false_case_element,
   and .unknown_case_element;
  Looping_element.repeated_element.
 ENTITY Task_element ....
 WHERE
   wr1: (SIZEOF USEDIN(SELF, 'xxx.TASK_ELEMENT_SEQUENCE.ELEMENTS')
       + SIZEOF USEDIN(SELF, 'xxx.CONCURRENT_ELEMENTS.ELEMENTS')
       + SIZEOF USEDIN(SELF, 'xxx.DECISION_POINT.TRUE_CASE_ELEMENT')
       + SIZEOF USEDIN(SELF, 'xxx.DECISION_POINT.FALSE_CASE_ELEMENT')
       + SIZEOF USEDIN(SELF, 'xxx.DECISION_POINT.UNKNOWN_CASE_ELEMENT')
       + SIZEOF USEDIN(SELF, 'xxx.LOOPING_ELEMENT.REPEATED_ELEMENT')
     ) <= 1;
 END_ENTITY;

3) Add a new AO:
  ENTITY Task_element_serial
    SUBTYPE OF (Structured_task_element);
    elements : SET [2:?] OF Task_element;
  END_ENTITY;
and provide a mapping similar to Task_element_sequence but without the
constraint for sequential_method.

4) Add a further subtype in the MIM
  ENTITY decision_point
    SUBTYPE OF (action_method_to_select_from, task_element);
  END_ENTITY;
and map the ARM entity Decision_point to it.

5) Add a comment in the mapping to say that the order in the resulting
SET is given by sequential_method.sequence_position

Section 3.  RESPONSE INFORMATION (completed by SEDS Resolution Team Leader):


If Accepted, Resolution:


Section 4.  FOLLOW-UP INFORMATION (completed by WG Convener):

Class:
Priority:
Impact of Change: 
Further Action Required:
Action Required by SEDS Coordinator/WG Conveners/QC/SC4: