The connection between Doors and SysML models

[Marco Franke]

I have read the above articles/input and I am very interested in the
functionality of the IBM Rational Rhapsody Gateway. The requirements
in Doors are represented in an informal way. These textual
requirements can be linked to SysML. Can some explain me how
requirements can be inserted in SysML as requirements which should be
satisfied by a block of a block diagram?

[GP]

Hi Marco

Rhapsody Gateway can import the requirements defined in DOORS (and in
other sources) in the SysML Model in Rhapsody.

SysML foreseen the existence of requirements in the model ! This is
one of the many interesting new elements introduced by SysML itself.
See the spec @ OMG. There is a new diagram, called Requirement
Diagram, and the requirements themselves are entities of the model.

Once imported, you can drag-n-drop the new model entities in any
diagram and link them to the model via various connection types. In
the case of blocks and sub-blocks in BDD and IBD, you can link the
blocks/ports to the requirements via a "satisfy" relationship (ie.:
the block is there because satisfy the requirement).

The IBM solution is quite poor compared to the solution of ATEGO, that
allows you to

1) roundtrip engineering of the requirements in DOORS and ARTISAN
STUDIO (in the IBM solution the requirements are "owned" by DOORS
only)
2) import in DOORS model elements of STUDIO with custom import mapping
(in the IBM solution the mappings are fixed)

The #2 above is very powerful if coupled with the Requirements
Management Framework add-on of DOORS by IBM, that allows you to export
excellent-quality documents from DOORS.

[Agusti CANALS]

Have a look to the Topcased Sysml, an open source tool !!

Regards
Agusti

----- Message d'origine -----
De : sysml...@googlegroups.com <sysml...@googlegroups.com>
À : SysML Forum <sysml...@googlegroups.com>
Envoyé : Sat Feb 05 16:30:44 2011
Objet : [SysML Forum] Re: The connection between Doors and SysML models

Hi Marco

--
You received this message because you are subscribed to the Google
Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com
To post to this group, send email to sysml...@googlegroups.com
To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en

[Marco Franke]

Thanks a lot,
what is Topcases SYSML?
Is it "only" a graphical modelling tool?

I search an aproach or a programm to
validate requirements against a "SysML" or "UML" model.

Best regards,

Marco

[samuel rochet]

Hi,

TOPCASED is much more than a "graphical" editor. It is a complete
platform including a "real" SysML (and UML) model editor and many
others interesting features (document generation, scripting, OCL
tooling, etc.).

In your specific case it proposes many solutions for requirements
management.

Have a look at http://www.topcased.org/ for a complete overview.


Samuel

> > For more options, visit this group athttp://groups.google.com/group/sysmlforum?hl=en_US?hl=en- Hide quoted text -
>
> - Show quoted text -

[FAUDOU Raphael]

Hi Marco, hi all,

 

TOPCASED is an open source modeling platform that contains model-based graphical editors (UML, SysML, SAM, AUI, AADL...) and other components like "TOPCASED Req" to import and trace/cover requirements from model elements and "TOPCASED gendoc2" to generate documents from models.

 

Once TOPCASED installed, you can create a project and import requirements from DOORS through a CSV, excel file, Word document or open office sheet. TOPCASED req imports the requirements through a wizard that lets you choose the data to import, the requirement attribute identification and the output format you want as a result between 3 possible formats:

• Sysml requirements (a SysML model containing only "Requirement" elements),
• UML requirements (a UML model containing classes stereotyped "Requirement")
• "Requirement" model = model based on a "Requirement" metamodel that is based on the "RIF" requirement format (in progress toward standardization).

 

If you chose the “requirement” format, you will be able to drag and drop your requirements to any model element and it will create a “trace” link.

Please see the “Requirement tutorial” to have a better view of what can be done between upstream textual requirements and model elements here: http://gforge.enseeiht.fr/docman/view.php/112/4346/TPC_4.3_Requirement_tutorial.pdf

(“Requirement management” tutorial).

 

If you chose the “SysML” format, you can create “satisfy” links between your SysML model elements and your SysML requirements.

 

Hope it helps

Regards

raphaël

 

-----Message d'origine-----
De : sysml...@googlegroups.com [mailto:sysml...@googlegroups.com] De la part de Marco Franke
Envoyé : mardi 8 février 2011 15:01
À : SysML Forum

  ________________________________  

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

[Eran Peleg]

Hi Marco Franke

I'm using Rhapsody with GW connection to DOORS.  A bit of background:

a.    Requirements (and even requirement flavors such as Functional, Non-Functional, Performance, etc., can be specified in SysML and therefore Rhapsody.

b.    Requirements can have relations to other requirements and to other model elements (see SysML spec on OMG for more details).  It is also possible to build nested requirements by dragging requirement on another one.

c.    Of course requirements document can be generated from Rhapsody using either ReporterPlus or RPE.

d.    Therefore, why to use DOORS ???  But if DOORS is given …

e.    The GW can build Requirements in Rhapsody from DOORS and then after synchronize changes to both sides.

f.    If Dependency relation (or Anchor) is created, the GW creates the relation in DOORS as a linked table.

g.    It is recommended that not all DOORS info will be considered as Requirements and filter out those that are not really a requirements (you do it in the GW filtering functionality)

h.    If we implement the whole development cycle with UML / SysML, one may consider a very small set of DOORS's requirements.

i.    Other traditionally DOORS artifacts such as Test and testing methods, can be now capture as SysML elements (see SysML spec)

 

If more information is please write and I'll be glad to answer.

Thanks

Eran

PS I have SysML and UML OMG's certification

 

 

======================

Eran Peleg, CEO

Metaphor Vision Ltd.

Phone: +972545346060

Fax: 151545346060

eMail: epe...@metaphor.co.il

Skype: EranPelegMetaphor

======================

--

[GP]

@Eran

How are you able to

" The GW can build Requirements in Rhapsody from DOORS and then after
synchronize changes to both sides"

according to my local IBM support this is not possible: they told me
that a sync means that only new requirements build in RHP will be send
to DOORS (and at each sync these will be rewritten). Moreover, if I
change a DOORS-managed requirement in RHP, with a DOORS sync will be
rewritten .... this is what IBM told me.

On the other way around, Atego Artisan Studio can perform full
roundtrip.

By the way, Topcased can only import from DOORS using Excel as a
bridge.

G.

On 11 Feb, 21:36, Eran Peleg <epe...@metaphor.co.il> wrote:
> Hi Marco Franke
>
> I'm using Rhapsody with GW connection to DOORS.  A bit of background:
>
> a.    Requirements (and even requirement flavors such as Functional,
> Non-Functional, Performance, etc., can be specified in SysML and therefore
> Rhapsody.
>
> b.    Requirements can have relations to other requirements and to other
> model elements (see SysML spec on OMG for more details).  It is also
> possible to build nested requirements by dragging requirement on another
> one.
>
> c.    Of course requirements document can be generated from Rhapsody using
> either ReporterPlus or RPE.
>

> d.    Therefore, why to use DOORS ???  But if DOORS is given .

[Eran Peleg]

Hi GP
So, (as usual) they don't really know how their products work.
It is not a theory; we have implemented the Drs-GW-Rh and it works fine both
ways.
There is a ~250 course slide set about how to implement the GW and both ways
sync. Ask IBMers to provide you the course materials.
IBM Support are able to help you if something is not working properly; they
are very efficient.
Good luck
Eran