Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 30-May-2007 11:12
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Using DOORS v7.1....

I've been asked to baseline a module which has never before been baselined.

Modules I have created have automatically been v0.0 when created, therefore when I create a baseline of it I get offered the option to set it to v0.0, v0.1, v1.0. Generally I will baseline it at v1.0, the first 'formal' baseline.

I have now come across a module created by someone else which appears to be defaulting to v1.1 (the title bar of the module says "Formal module '<module full name>' current 1.1 - DOORS"

When I use File|Baseline|New, I get offered v1.1, v1.2 or v2.0. Yet this module has no previous baseline. How can this be, and can I change it, as I wish to baseline it a v1.0.

TIA

Report this to a Moderator Report this to a Moderator
 30-May-2007 11:24
User is offline View Users Profile Print this message


Reik Schroeder

Posts: 361
Joined: 28-Jul-2003

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
Report this to a Moderator Report this to a Moderator
 30-May-2007 11:36
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

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
Report this to a Moderator Report this to a Moderator
 30-May-2007 11:58
User is offline View Users Profile Print this message


Reik Schroeder

Posts: 361
Joined: 28-Jul-2003

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
Report this to a Moderator Report this to a Moderator
 30-May-2007 14:25
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
 30-May-2007 14:32
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Hmm.

How annoying.

Thanks anway.
Report this to a Moderator Report this to a Moderator
 30-May-2007 18:33
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
 31-May-2007 00:33
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.