![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Using 'Overridable' link parings Topic Summary: What are the possible benefits? Created On: 12-Feb-2007 15:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I've been scratching my head.... Has anyone ever used 'Overridable' link parings?
DOORs help states: Select the Link Module options you wish to use for this linkset: If you select Mandatory, link information for this linkset can only be stored in the specified link module. If you select Overridable, a user's personal default link module will be used to store information about their links. Seems like you would give up control over where the links are stored. I must be missing something. Does anyone allow 'Overridable' linking in their schema? What are the possible benifits? Thanks, Dan |
|
![]() |
|
![]() |
|
I don't allow it.
I recommend a proper data model with all relationships defined using mandatory link pairings. I also create and soft-delete a DOORS Links module in every folder in the project, thus preventing accidental link creation. There may be advantages to allowing users to override the linkset pairings, but in my experience users just get themselves in a pickle and I end up having to move links around - not fun. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Same here - I don't allow overridable links either.
When it comes to a link schema for a DOORS project, the rules should be black and white for each module - you can either link from it or you can't. I would prefer users to come and argue the point that a link rule should be implemented than having to fix up link spaghetti later. I make sure that all template modules have the "Only allow outgoing links as specified in the above list" checkbox checked so that from a standing start, new modules can't link anywhere and the author will need to seek assistance with someone who has Administrator access rights and can put the rule in (Usually done by the people who have been assigned a Requirements Management role and can keep an eye on the integrity of the schema). ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Absolutely, don't allow it, as Paul says, black and white rules when it comes to where the links live else you can forget doaing any useful analysis later on.
In our db we have gone one step further, and removed the standard link routines completely, then replaced them with a custom routine that consults a 'rule table' before making the links using DXL. This was done before I 'inherited' the db, but apparently there was another problem that lead tothis solution, in that using the standard method (defining rules in the module properties of each module) caused the database to slow right down (lots and lots of modules). Apparently it was taking up to a few minutes per link to create new links.( doors v 5.2) The tricky part was to remove the standard link options from the standard menu and mouse menu on each and every client machine, since these menu's are defined in 'formal.dxl' on the user side. Eventually got around that one by creating a custom 'formal.dxl' file on the network, then using a customised user log in icon. The icon redirects to a custom batch file on the network ( a windows .bat file). This file, among other things does a simple replace of the 'formal.dxl' file every time a user fires off the launch icon. As I mentioned, this was largely in place when I stepped into the Administrator shoes, but I can dig out more info if anyone is interested. Rgds Andrew. ------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Linking is pretty hopeless. You lose links when you archive modules and its a hassle all the way around.
We'll adopt Raytheon's policy where users specify their desired link target partners in special Link_ xxx text attributes. A nightly script reads the attributes and creates or deletes links as specified. This allows us to have more than one kind of link between two modules; in our case we can say a test event is relative to a requirement for 'Verification' purposes and can also link the same req with the same event for 'Certification' purposes. Well, we will as soon as I shake loose from this project and can focus on DB administration and Project policies and procedures, and of course write the clever link script. In the Req decomposition world a child req can 'satisfy' a parent req but you can also have a child req 'reference' some data in the parent module. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Using 'Overridable' link parings
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.