Generating DEX long forms

Leif and Tim asked me about some EXPRESS errors they had when generating a DEX long form.

I thought it would be useful to copy the response to all modellers.

1) Make sure that you have done a CVS update on stepmod. There were some errors in the PLCS long form caused by the SHTOLO. These were corrected last week and the AP has been submitted to the convener for publication.

2) When the DEX long form is generated, there may be some SUPERTPYE OF statements that are referring to entities that are not in the long form i.e. have been deliberately excluded. E.g.

ENTITY Class

SUPERTYPE OF (ONEOF(Class_by_extension, Class_by_intension));

id : STRING;

name : STRING;

description : OPTIONAL STRING;

END_ENTITY;

It would be possible to prune these in the XSL for the long form generator, but to do it properly will take some time. So for now, the long form express file should be manually edited. i.e. dex_lf.exp

3)       There may be some expressions (where rules etc) that have 'AP239_PRODUCT_LIFE_CYCLE_SUPPORT_ARM_LF as a string. E.g.
ENTITY Component_upper_level_identification
  SUBTYPE OF (Assembly_component_relationship);
  upper_assembly_relationship : Assembly_component_relationship;
  sub_assembly_relationship : Next_assembly_usage;
UNIQUE
  UR1: upper_assembly_relationship, sub_assembly_relationship;
WHERE
  WR1: SELF :<>: upper_assembly_relationship;
  WR2: SELF\View_definition_relationship.relating_view :=: upper_assembly_relationship\View_definition_relationship.relating_view;
  WR3: SELF\View_definition_relationship.related_view :=: sub_assembly_relationship\View_definition_relationship.related_view;
  WR4: (upper_assembly_relationship\View_definition_relationship.related_view :=: sub_assembly_relationship\View_definition_relationship.relating_view) OR (SIZEOF(QUERY(pdr <* USEDIN(upper_assembly_relationship\View_definition_relationship.related_view, 'AP239_PRODUCT_LIFE_CYCLE_SUPPORT_ARM_LF.VIEW_DEFINITION_RELATIONSHIP.RELATED_VIEW') | pdr.relating_view :=: sub_assembly_relationship\View_definition_relationship.relating_view)) = 1);
  WR5: SIZEOF(['AP239_PRODUCT_LIFE_CYCLE_SUPPORT_ARM_LF.NEXT_ASSEMBLY_USAGE', 'AP239_PRODUCT_LIFE_CYCLE_SUPPORT_ARM_LF.COMPONENT_UPPER_LEVEL_IDENTIFICATION'] * TYPEOF(upper_assembly_relationship)) = 1;
END_ENTITY;.

Again – this could be fixed in the XSL, but in the short term, these should be manually replaced with the name of the dex schema

4) If there are still errors, it is likely that these are caused by super/sub type entities not being present in the long form, or by attributes referencing entities that are not present in the long form. This is caused by the capabilities not including the necessary entities. So check the capabilities.

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)1454 270030
Mobile: +44 (0)7796 176 401
Fax: +44 (0)1454 270031

plcs-dex message