Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Deep history and shallow history
Topic Summary:
Created On: 30-Nov-2006 15:03
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.
 30-Nov-2006 15:03
User is offline View Users Profile Print this message


Ignacio González

Posts: 1
Joined: 23-Nov-2006

Hello together.

From the description given in Rhapsody's help, and from a simulation I run a couple of days ago, it seems to me that the history connector (H) corresponds to deep history, not to shallow history. But the standard notation in UML for deep history is (H*), not (H).

1) Am I right?

2) How can I model shallow history in Rhpasody?

Thanks in advance.
Report this to a Moderator Report this to a Moderator
 8-Dec-2006 09:05
User is offline View Users Profile Print this message


Jens Steiner

Posts: 9
Joined: 21-Nov-2006

The Rhapsody history connector is a deep history one. With the semantics of Rhapsody statecharts where inner transitions have priority over outer ones, you should alway know what state your system is in when leaving a hierarchic level and can reenter when done on the outer level. I never missed shallow history in this context.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 1 users logged in.
You have posted 0 messages to this forum. 0 overall.

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