![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: The problem with filtering and the DOORS tree structure Topic Summary: The filter functionality and the tree structure are incompatible. Created On: 21-Jul-2008 13:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
My company are pushing me to implement filtering, which I have resisted for a long time as I believe it is fundamentally broken in DOORS. Any opinion ?
I will try to explain: We are trying to implement Product Options in DOORS, should be simple enough, just create an enumerated attribute with lets say: Option1 Option2 So the idea now is that requirements can be tagged as either Option1 or Option2, then at publication time we simply filter out one or the other. However, DOORS objects are structured in to a tree, as in the following example: Heading1 | |_Heading2 | |_Requirement | |_Requirement | |_Heading2 | |_Requirement | |_Requirement | You get the idea. Now then, its simple enough to tag the requirements with Option1 or Option2, but what happens when we need 2 variants of the Heading1 object? We would have to add a new Heading 1 object to give 2 variants, but now one of the Heading1 objects 'owns' some requirements, and one of them is an 'orphan' with no requirements as follows: Heading1 Heading1 | |_Heading2 | |_Requirement | |_Requirement | |_Heading2 | |_Requirement | |_Requirement | Of course this is all quite manageable with the simple example above, but lets try with 5 Options, 7 levels of headings, all split across multiple modules (eg, one published document, might consist of 20 modules, one per chapter for the document). How do you ensure that the following scenario's do not eventuate: * Duplicate headings * Requirements with no headings * Dulpicate requirements I have a few ideas of my own, but they all seem complicated, am wondering if anyone has crossed swords with this scenario themselves and what combination of DXL, Process, User Education, has been used to make it work. Thanks, Andrew. ------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Kinds of makes me think you are trying to stretch DOORS to do something that DOORS was not designed for. Is this kind of like using of a saw to drive a nail?
|
|
![]() |
|
![]() |
|
Unfortunately yes. I keep mentioning that at the office.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
I have done a similar thing.
Change all Object Heading to Object Text. Filter OH not empty Export to spreedsheet (Excel export does not include the para no.) Export Abs; OH, Para Style. Change second col title to Object Text; Replace in col 3 'Heading:' with Text:' (so para style is applied properly in Word), Add blank col with title 'Object Heading' Import spreadsheet. This changes all OH to OT but retains the hierarchy. Export to Word will look the same since it uses the correct paragraph style. Now paragraph numbers are text and can be duplicated or annotated with a, b. By creating filterable attributes different documents can be produced from the same DB. I have 15 different documents produced from the same DOORS Module. |
|
![]() |
|
![]() |
|
Andrew, it might be worth your while taking a look at KeyChange from Integrate.
This is a doors addin that support product line requirements. In my opinion it is a very good product. website link Integrate Systems Engineering. ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
Thanks Tony, will check that one out.
I believe the latest version of DOORS TREK also has product line functionality, has anyone used that before? ------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Andrew, it might be worth your while taking a look at KeyChange from Integrate. This is a doors addin that support product line requirements. In my opinion it is a very good product. website link Integrate Systems Engineering. Are they working on KeyChange again. Last I heard they had stopped development on it. That was about 4 or 5 months ago. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Are they working on KeyChange again. Last I heard they had stopped development on it. That was about 4 or 5 months ago. I investigated the status of KeyChange yesterday as I have a project that could do with it. The response from Integrate was: "KeyChange is not yet in full commercial release. It has had a very good reception during Beta testing however we are not currently planning a commercial release because we haven't been able to validate a business plan. Basically we can't see a big enough market at the moment" I can't believe that there is not a "big enough market at the moment" - Telelogic, needs to do the same deal they did with with Integrates "KeyTrace" product (distributed by Telelogic as "TraceLine") and get "KeyChange" into a marketable state or preferably build it into the out-of-the-box DOORS product. ------------------------- Paul Miller Specification Practices Specialist EuroCyber Melbourne, Australia Mobile: + 61 (0) 418 135 103 http://www.eurocyber.biz |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.