Bug 468459 - EAST-ADL metamodel followed only partially in EATOP?
Summary: EAST-ADL metamodel followed only partially in EATOP?
Status: UNCONFIRMED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EATop (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 8
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Voget CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-27 07:13 EDT by Janne Luoma CLA
Modified: 2021-03-03 17:21 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Janne Luoma CLA 2015-05-27 07:13:30 EDT 
EAST-ADL metamodel (version 2.1.12) defines a set of rules and constraints in relation to the definition of the elements. Can EATOP also follow these rules and constraints as now it is possible to specify incorrect and inconsistent models. 

For example, VariableElement in EATOP may have as 'Optional Element' reference to itself, other VariableElement, Requirement, Package etc. whereas the metamodel explicitly specifies that the 'Optional Element' reference link should be: ”one FunctionPrototype or one FunctionPort or one FunctionConnector or one HardwareComponentPrototype or one HardwarePin or one ClampConnector”.

As there are many other similar constraints in EAST-ADL, am I missing something or how to activate those validity & consistency checks in EATOP?

Or is there a newer version providing functionality for complete metamodel covering also the constraints and rules like the one mentioned above?