I am developing a course in Model-Based Systems Engineering. I have decided to build it on SysML and the Topcased editor. I am not much more than a newbie myself. I will be placing the tutorials in the public domain and want to participate in open-source efforts. From my text in "Getting Design Right: A Systems Approach" I have a worked example for a toy catapult but it is very basic. I agree that the Watch example is good but incomplete. I would like to participate in any group you initiate to create a more complete example.
I am also creating software to read parametric diagrams and generate Modelica scripts. Late, I will adapt the software to read activity diagrams and generate Python scripts. Is there an open source community working on anything similar? Peter L. Jackson Professor School of Operations Research and Information Engineering Rhodes Hall 218 (607) 255-9122 [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Topcased user list where issues are discussed Sent: Thursday, April 21, 2011 7:32 AM To: [email protected] Subject: [Topcased-users] Creating an updated SysML example 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
