Hello Tristan, Patrick, I would not like to post further on this discussion here, as this is not an appropriate platform, so please check your official mail.
Thanks. Best Regards, Gajendra > Today's Topics: > > 1. Re: Topcased-users Digest, Vol 70, Issue 1 > (Topcased user list where issues are discussed) > 2. TOPCASED requirement facilities > (Topcased user list where issues are discussed) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Jul 2011 13:02:53 +0000 > From: Topcased user list where issues are discussed > <[email protected]> > To: "[email protected]" > <[email protected]>, > "[email protected]" > <[email protected]> > Subject: Re: [Topcased-users] Topcased-users Digest, Vol 70, Issue 1 > Message-ID: > <mailman.9.1309784595.31947.topcased-us...@lists.gforge.enseeiht.fr > > > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > I am not sure you took enough time to really know the tool. > > my answers bellow : > > > De : [email protected] [mailto: > [email protected]] De la part de Topcased user > list where issues are discussed > Envoy? : vendredi 1 juillet 2011 18:40 > ? : [email protected] > Objet : Re: [Topcased-users] Topcased-users Digest, Vol 70, Issue 1 > > Hi Benoit, > > If you create requirements in the outline view by dragging and dropping > imported requirements as is the process in Topcased, you don't have the > possibility to create requirements diagram. I've tested this and this is a > major drawback of the tool. > [Tristan FAURE] The requirement Diagram exists for SysML files, drag and > dropping requirement on diagram is possible if you use TOPCASED Requirement > tool. This tool is derived from ReqIF OMG Specification and will in the > future be totally compatible : http://www.omg.org/spec/ReqIF/ > If you want to use SysML Stand-alone you just have to create a requirement > diagram and create Satisfy, Trace ... relationships. > I remind you that you can create a callout in several diagrams, if you > want to drag and drop a SysML requirement to create a Satisfy relationship > it is possible > [cid:[email protected]] > > > >From the discussion I had with the visionaries of the tool, I concluded > that they don't want to have requirement diagrams at all in this tool. For > them the requirement is just text and that the model created in the outline > view is what they want. > [Tristan FAURE] Requirement is not only a text Requirement. In > TOPCASED-Requirement a requirement is the model representation of textual > requirements defined in documents, in System Engineering the important point > is not the graphical representation but the link between the textual > requirements and the model elements. > > So all possibilities of doing anything within requirement diagrams are > therefore killed !!! > > If you are interested in requirement diagram then there will not be any > possibility to use the tool in the way, I understand, you are using now. > There is no possibility perhaps to use the tool in standard way and then > generate a desired output. > > The visionaries have created this tool and are driving the way of usage in > a particular direction of their personal interest but not as a industry > standard way of using it. Therefore, I always see people asking questions on > this forum, how to do this and how to do that. Unless one receives training > on the tool usage he/she cannot exploit its potential. I don't know how do > you want to respond to this but this is a fact. > [Tristan FAURE] TOPCASED is actually an industrial tool designed by System > Engineers, saying that TOPCASED have some lacks of usability is a fact but > it is widely used in System Engineering community. TOPCASED is a free and > open source software, having some trainings to handle it is just an option > for users and that's why we try to be the most reactive we can to give > answers to community. > And if you download and read the last TOPCASED presentation, you will see > that the roadmap plans to add a lot of connectors to system engineering > world (Scade, DOORS...). > Kind regards > Tristan FAURE > > Gajendra > > Date: Tue, 5 Jul 2011 10:02:52 +0200 > From: Topcased user list where issues are discussed > <[email protected]> > To: <[email protected]> > Subject: [Topcased-users] TOPCASED requirement facilities > Message-ID: > < > mailman.14.1309853004.31947.topcased-us...@lists.gforge.enseeiht.fr> > Content-Type: text/plain; charset="us-ascii" > > Gajendra, > I can't let you say that "The visionaries have created this tool and are > driving the way of usage in a particular direction of their personal > interest but not as an industry standard way of using it". > As Tristan said, if you want to define Requirement facilities using > standard SysML with TOPCASED, the standard is correctly implemented and > you can make it. But, as we are industrial (developing safety critical > embedded systems), we consider it is not a best way to manage textual > requirements in models. In real life we have to manage several hundreds > or thousands of requirements, I am not sure that drawing all of them and > their relationship with use cases or all other features is an industrial > way to work. > Based on our real practice we defined the new plugin TOPCASED/Req and it > satisfies industrial needs. Furthermore and as Tristan said we are not > too far from the ReqIF standard and we will meet this OMG definition. > In conclusion with TOPCASED you can choose 2 ways to manage textual > requirements within models, both are OMG standard compatible and users > are free to use one of these solutions in their own process (but not to > mix them). The main key driver of TOPCASED was to define a toolset to be > most opened possible with regard to industrial process and based on > standard. > If you consider that some feature is missing in order to manage in best > and industrial way requirements & models then you can either raise a > feature request in the forge trackers or propose a new contribution > through a new plug-in or a modification on an existing one. > Best regards > Patrick Farail > > The information in this e-mail is confidential. The contents may not be > disclosed or used by anyone other than the addressee. Access to this e-mail > by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and > delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of > this e-mail as it has been sent over public networks. If you have any > concerns over the content of this message or its Accuracy or Integrity, > please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus > scanning software but you should take whatever measures you deem to be > appropriate to ensure that this message and any attachments are virus free. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.gforge.enseeiht.fr/pipermail/topcased-users/attachments/20110705/c39a9039/attachment-0001.html > > > > ------------------------------ > > _______________________________________________ > Topcased-users mailing list > [email protected] > http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users > > End of Topcased-users Digest, Vol 70, Issue 4 > ********************************************* >
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
