Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic TAU (steve huntington)
Decrease font size
Increase font size
Topic Title: Warning TSC0144: Model inconsistency error: The metafeature 'Definition' contains NULL value.
Topic Summary: Warning TSC0144: Model inconsistency error:
Created On: 16-Mar-2005 21:07
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 16-Mar-2005 21:07
User is offline View Users Profile Print this message


Cynthia Smith

Posts: 1
Joined: 20-Nov-2002

I am stumped by the following error messages:

GC Information TSC0173: Checking Package GC...
Actor::CITS Warning TSC0144: Model inconsistency error: The metafeature 'Definition' contains NULL value.
Actor::CITS Warning TSC0144: Model inconsistency error: The metafeature 'Definition' contains NULL value.
Actor::CITS Warning TSC0144: Model inconsistency error: The metafeature 'Definition' contains NULL value.
......
GC Information TSC0174: Package GC - 0 error(s), 11 warning(s)
GC Information TMI0740: Checking Diagrams...
RequirementsAnalysis.ttp Information TMI0762: Check complete.

Other actors in our sequence diagrams are fine. All of the actors were placed on the sequence diagrams by drag and drop from the Actors package. When I look at the properties of the actors they appear to be identical to actors that have no problems. When I drill down through the Applied Stereotypes and Dependencies to look at properties for anything identified as a "metafeature" I can't see anything wrong. However, after navigating through these heirarchies sometimes the number of warning changes to 7 or 8. When I try to repeat the same actions on a different actor the warnings jump back up to 10 or 11 (obviously I am just shooting in the dark at this point).

My experience tells me that it isn't the tool, it is something dumb (and probably obvious) that we are not doing correctly. Does anyone have any ideas?

Thanks,
Cindy Smith
Report this to a Moderator Report this to a Moderator
 17-Mar-2005 07:21
User is offline View Users Profile Print this message


suneel santharam

Posts: 15
Joined: 4-Sep-2003

Hi Cynthia,

This issue was seen in the TAU G2 2.2 version and they have improved this area of the tool in the latest version Tau G2 2.3.

However I would suggest to use TAU G2 2.4 release, which is the latest version.
Take the benefit of the new feature and the improvement done as compare to older version.

If you still see this issue in TAU G2 2.4. Then I would suggest you to contact the Telelogic Support.

Best Regards,
Suneel...
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic TAU forum.
There are currently 1 users logged in.
The most users ever online was 15 on 31-Mar-2008 at 16:22.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.