|
A good way I found is to make a base class named "BaseThread"
and all threads inherits from that base class. The base class have functions
like Start(), Stop() and Run(). When you see a class named "AcquisitionThread"
or "AnalyzerThread" you know what it does. In the process View, it's easy to see
what threads do what with neightbourhood and you can also insert in the
processor object of the deployment View, the name of the classes for that node
and specifying stereotype <<process>> or <<thread>> for
each thread.
Jean-Yves Garneau
Analyste-programmeur Centre de Recherche Industrielle du Qu�bec T�l.: (418) 659-1550 Poste 2903 >>> Hurley Randal-rhurle01 <[EMAIL PROTECTED]> 07/17 6:12 am >>> Hi, I am currently trying to come up with a good way of modelling threading in Rose2000, but am having difficulty finding a good way. Does anybody have any suggestions? Thanks in advance, Randal Hurley. ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * ************************************************************************* |
