Comments (4)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 F-Skier commented Permalink

My organization is probably one of those that have lots of traceability, a lot of DO-178 type projects. <div>&nbsp;</div> We have been using DOORS from over 10 years now. When we first started using DOORS we were instructed to segregate our traceability using different link sets. Typically we have two or more linksets, one for say requirements and another for test. This was done to allow us to easily have different "traceability columns" so we could separate out the requriements traceabilty from test traceabilty, for example. <div>&nbsp;</div> As a rule we also trace from lower level (source) to higher level (target). This works well for hierarchic traceabilty, but often we need same level traceability. <div>&nbsp;</div> A few problems that occur with this. It is difficult to enforce correct traceability rules. Especially having the need to change around linksets based on what you want to do. And making sure the current direction of linking is performed. <div>&nbsp;</div> Generating traceabilty reports works fine as long as you want to go down one direction and along a common linkset. Wiith complex traceability, the need fo follow "wandering" paths is often required "go down 2 levels of requirements and then switch to test paths" for example. There is certainly no easy way to automate the generation of these types of traceability routes. <div>&nbsp;</div> An easy way of generating a traceabilty route for matrix generation would be very helpful. Of course anything that could be done to improve the speed and efficiency of this report generation would be greatly appreciated. <div>&nbsp;</div> Another issue is the use of surrogates. We use Matlab a lot. There is a method that employees surrogates objects is special modules. There are "add-in" tools that help manage this, however, these integrations are very fragile going from one version of tool to another. If we go to a new version of Matlab or DOORS, do these integrations still work?

2 AndyGurd commented Permalink

Before I went on vacation, I posted this blog post link to several LinkedIn Groups which prompted some great responses and lively discussion (particularly from the INCOSE group). See links below to each of the discussion threads (note: some of the groups require you to request to join and need approval from the group moderator): <div>&nbsp;</div> INCOSE:;discussionID=121720598&amp;gid=1218517 <div>&nbsp;</div> Systems Engineering:;discussionID=121720588&amp;gid=6722 <div>&nbsp;</div> SYSTEM ENGINEERS: <div>&nbsp;</div> Requirements Engineering:;gid=157594&amp;type=member&amp;item=121720587&amp;qid=a6cfdd8d-1b58-4d16-b190-171511373701 <div>&nbsp;</div> IBM Rational DOORS:;gid=769057&amp;type=member&amp;item=121720576&amp;qid=14cd219b-7a20-489c-b748-7951c9b535e7

3 gsiampos commented Permalink

Regarding the comment by F-Skier: <div>&nbsp;</div> The link topology should be enforceable even for data at the same level of decomposition although I can imagine a situation where that would not be true. I'd like to hear more specifics about the types of data involved. <div>&nbsp;</div> On the point about generating traceability columns, the Layout DXL generated by the Analysis Wizard can be modified to include links of different types and non-system attributes. <div>&nbsp;</div> When a recursive analysis is performed using the Analysis Wizard, there may be several columns created showing the traceability. Don't forget that although it is one analysis each of the Layout DXL columns contain separate DXL scripts. The content for one column is not a function of the content in the others. These columns can be modified to include information at the various levels of decomposition. I described an approach for adding non-system attributes in a recent instalment of the DOORS Enlightenment Series. Similarly, a modification can be made to include different link modules.

4 Ben_Sharples commented Permalink

Noticed some of the comments on generating traceability reports from within DOORS and the difficulties faced using the analysis wizard especially where link directions change and diferent linksets used at different levels. <div>&nbsp;</div> I have found that using DXL to generate traceability reports that output directly to excel can get round a lot of these problems as you have the ability to define which linksets, linkmodules or formal modules are used at each level of traceability. <div>&nbsp;</div> Also an added benefit of using an OLE embedded output to excel is it is possible to define the cells and columns data is outputted to, hence also making it simpler to interpret the results where there are multiple links out from a singular object (everything gets ;lined up more neatly) <div>&nbsp;</div> There are a number of posts with sample scripts on the DXL Developer Works forum on how to do this