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: Baselline set script for DOORS 5.2
Topic Summary:
Created On: 4-Feb-2004 08:36
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.
 4-Feb-2004 08:36
User is offline View Users Profile Print this message


Dirk Plaschke

Posts: 103
Joined: 17-Sep-2002

Hi all.

Does anyone has a script that will emulate the DOORS 7 Baseline Set functionality (possibly in simplest form) ?
We now have many modules (25 and more) in one path that will be baselined every week (this is very crude).

Thank you very much and have a nice doorsday ;-)

regards,
Dirk.

-------------------------
Dirk Plaschke
Report this to a Moderator Report this to a Moderator
 4-Feb-2004 13:51
User is offline View Users Profile Print this message


Richard Kilgore

Posts: 12
Joined: 16-Sep-2002

Dirk -
The attached script was used to create a minor baseline for each module in hopes of improving performance in our v6.0 database.
You can modify to create a major baseline.
It works in v5.2.
All mods must already have been baselined at least once.

Hope this helps.

Richard Kilgore
Northrop Grumman Mission Systems
richard.kilgore@ngc.com
Report this to a Moderator Report this to a Moderator
 4-Feb-2004 15:51
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

[A] You need to insert the Basline Suffix in your designation, since there can be two baselines: [1] "4.2" and [2] "4.2 (a)".

After your statement: string bl = (major b) "." (minor b)"", consider adding statement:
if (!null suffix(b)) bl = bl " (" suffix(b) ")"

[ B] Consider using the "version(mod)" command, since that gets the current baseline designation as shown at the top of Module windows: "current 4.2 (a)". This would replace the need for the loop and the BL stuff above your "confirm" statement.

[C] Lots of baselines is also bad. Perhaps you can count the number of History Records (or perhaps even count the number of Bytes in all the "hist.oldValue" and "hist.newValue", and display that to the user. Users could be encouraged to bypass baselining when "few" changes have been made to the current version.

- Louie

Edited: 4-Feb-2004 at 16:42 by Louie Landale
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 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 0 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.