![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Baselining a new module Topic Summary: New module already has a version Created On: 30-May-2007 11:12 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Using DOORS v7.1.... |
|
![]() |
|
![]() |
|
Hi Alan,
this can happen, when the module was copied from another module or restored from an archive without baselines. Another option is, that someone has deleted the baseline, if that option is enabled in your database.... ![]() Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Really?
I'm shocked. I can't envisage a time when you would want to copy a module and keep the version information. Well, I suppose I can, but not as a default option (and I don't remember being asked the question for any of the modules I've created through copying an existing module as a template). I would be embarrassed if I were the softie that coded that. They should be hung drawn and quartered. Incidentally, baseline deletion is only enabled for a couple of us with administrative rights, and we didn't. So there's no way around it then? Edited: 30-May-2007 at 11:50 by Alan Gooch |
|
![]() |
|
![]() |
|
Hi Alan,
DOORS users manual says: <cite> Note: Copying a module does not copy the baselines associated with the module. Copying a project containing modules that have baselines does not retain those baselines. </cite> I can not find any option to copy baselines to?! Sorry for that bad news, but I'm only the messenger, not the responsible ![]() Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Reik is correct in stating that when you copy a module, the new module has it's version set to the current version of the original, but with no previous baselines.
If you want to copy a module without this happening then use the clone option instead. Note that if you clone a module the object identifiers are not preserved in the copy. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Hmm.
How annoying. Thanks anway. |
|
![]() |
|
![]() |
|
I'd archive then restore the module. That allows preserving the baselines and prevents a bunch of links getting created.
I wonder what would happen if the current user has no R access ..err.. had no read access to the module at the time it was baselined? Would they see the baseline's existence but couldn't load it? - Louie |
|
![]() |
|
![]() |
|
This is one of those many endearing little nuances of DOORS that has been around since the tools inception but I can't understand why they don't fix it. If you copy a module, I reckon the default user expectation is that the baseline labels are reset to version 0.0 and no outgoing links are included in the copy either (any exceptions to this should be provided as options).
------------------------- 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 |
|
![]() |
Telelogic DOORS
» General Discussion
»
Baselining a new module
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.