Linking Requirements from DOORS to Rhapsody SysML Model

[Seckin Aribal]

Hi,

We are using Rhapsody SysML for modelling our system and
Doors tool for requirement analysis in our company. We are using the Gateway tool for the traceability of the requirements in Doors from Rhapsody.

But we had a problem as following:  In Gateway tool, if we click on " add high level requirements", requirements are added to the SysML
model. However, we have got many requirements and do not prefer
to add all these requirements to the model.  

How can we achieve this without adding the requirements to SysML
model and how can we create the relationship between
requirements and model?

Thanks in advance.

[Ritesh Sugandhi]

Hi,

I have some thought . see if it is useful and add your comments.

1> Door and Rhapsody are seperate products which are inferced through plug-in called Rhapsody Gateway value pack.Doors has many facilitities from reporting point of view where as in Rhapsody reporter plus you have to write scipts.

2> You can directly wite the requirement in Rhapsoy and define the tracability matrix among them.

3> Let suppose you decided to have a repositary of all requirments in Doors(functional and nonfunctional), and all primary requirement to be modeled in SysML project in Rhapsody. You can do this.

4>  now when you define requirements in Door. During fetch of requirement from Door to Rhpsody all the requirements will be transfter ( I don't know if some filtered can be put). You can put into a package c/s MainRequirementInDoor package. A part of the total requirement can be copied (or transfer) into another package (lets say InterestingRequirements or ModelingRequirements).

Please note that functional requirements can be modeled in SysML easily. 

4> if you feel that you have many requirement then try to classify them in packages and you can use the package diagram to represent the classification.

5> You can drag and drop the modeling requirement into diagrams as well as use the hyperlink between diagrams.

As for as I know, It is preferable to have small set of main requirements( 5-10) Under main requirement you can classify secondary requirements.

Best Regards,,

--- RITESH

[ztay...@motorola.com]

Hello,

I am using both Telelogic Tau G2 and DOORs for requirements
management. If there was a convenient way to display, edit, search,
and manage SysML requirements in a rudimentary fashion similar to
DOORs or even Excel, I would certainly drop DOORs and use Tau G2 only
for requirements management. Each of my requirements has dozens of
fields that need to be managed. Even a simple way to display, filter,
and edit SysML requirements in a tabular form would be extremely
useful.

Has anyone come across a method that would help?

Thanks,

Zack

On Jan 5, 12:08 am, "Ritesh Sugandhi" <ritesh.sugan...@gmail.com>
wrote:

> > Thanks in advance.- Hide quoted text -
>
> - Show quoted text -

[ggorman]

I would also suggest you ask this question on the IBM Rational
Rhapsody DeveloperWorks forum, since it is monitored by the product
teams and experts.

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=1501

/Greg


On Jan 4, 11:08 pm, "Ritesh Sugandhi" <ritesh.sugan...@gmail.com>
wrote:

[Amanda]

Hi -

We're using a similar set-up - connecting DOORS and Rhapsody via
Gateway. Probably the easiest way to limit what requirements get into
Rhapsody is to create an attribute in DOORS that flags whether the
requirement should be picked up by Gateway, and then configure your
Gateway's ".types" file to only pull in those objects (requirements)
with the correct setting of the attribute. This changes the set of
requirements that Gateway pulls in from DOORS - I don't know of a way
to limit what gets pushed from Gateway to Rhapsody other than this.
There should be plenty of documentation in the Gateway support
literature to walk you through modifying your .types file - there are
certainly other ways to filter in the .types file than just by a
unique attribute.

Once you get the requirements into Rhapsody, you can add an "anchor"
between the individual requirements and model elements (classes,
diagrams, etc) to establish a relationship - those requirements with
anchors will show up in Gateway as "covered".

- Amanda