Thank you Roberto for helping a newbie... I'm used to work on uml models for many years with differents tools such as Rose, Bouml, Paradigm... and I confess that I feel very uncomfortable with Topcased. I try to work on myself, and many features are very difficult to do. For example, in an internal block diagram, I can't display an item flow on a connector between 2 flowports. In the help content, it said :
- "To define the name and the type of the ItemFlow, double-click on the connector" -> *Nothing happen* - "So, to show the item flow on your connector, open the graphics tab of the connector properties and show the ConnectorItemFlowIconEdgeObject to see the arrow and ConnectorItemFlowNameEdgeObject to see the label associated. " -> *Those properties doesn't exist in the graphical tab*. I thougth I had a bad specification of my flowports, so I tried to do it in the watch example, and I have the same situation. Thank you again for your help. -- *Pascal PISZYNA* * * * * 2011/4/21 Topcased user list where issues are discussed < [email protected]> > Hello community, > > when we look at the questions in this mailing list and if we also have the > opportunity to see someone who is starting with SysML and chooses to use > Topcased, we can clearly see that the learning curve involved is very steep. > The Watch example is already a very good start, and of course, the > documentation available regarding the editor, the document generator, etc. > is very, very useful. But I think we need something to guide new Topcased > users. When someone decides to use Rhapsody, they have Harmony. When someone > decides to use MagicDraw, they have the SE2 Cookbook. When someone decides > to use Topcased, they don't have a complete example, they don't have a > process description/cookbook, they don't even know what aspects of the SysML > specification are supported. Not knowing what is supported and what not > makes it impossible to assess for what sort of projects Topcased is > adequate. Not having a complete example makes it difficult to find out how > to proceed with Topcased. And then the user has to reverto to the general > SysML documentation. But trying to follow the SUV example from the SysML > specification or the telescope example from the INCOSE MBSE Challenge can be > very frustrating for newbies in Topcased. > > If we really want a greater user base, we need to change this. > > Therefore my question to the main developers who have the project overview: > is there already any subproject dealing with this issue? (like Topcased > Process Engineering, maybe?). If yes, how can we get involved? > > If there is no such subproject, I would like to propose to start one! The > project could start by replicating the SUV example from the SysML > Specification as closely as possible, describing what is possible and what > not, and what are the work arounds. I would really like to participate in > such a project, but would certainly require the assistance of someone with > much more solid knowledge of the capabilities of the tool. If we want to > start real soon, we could work on nightly builds or something that already > incorporate the new editor from the Papyrus project, since this will clearly > affect the workflow. > > So, community, what do you think? > > Rodrigo > > _______________________________________________ > Topcased-users mailing list > [email protected] > http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users >
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
