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: Baseline
Topic Summary: How often
Created On: 25-Apr-2006 19:33
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.
 25-Apr-2006 19:33
User is offline View Users Profile Print this message


Matthew Herald

Posts: 14
Joined: 19-Apr-2006

Hello,

I am new to DOORS and new to my job.  I still have a learning curve ahead of me, but I am catching on pretty quickly.

My question is, how often do you baseline you modules and/or projects?  As the new DOORS admin. it will be my job to set this standard, but I have no idea exactly when to do it, so I thought I would ask all of you for pointers.  Anything that I should take into consideration will be appreciated.

Thanks.

-------------------------
Matt Herald
Systems Engineering Tools Administrator
ITT Corporation - Communications Systems
Fort Wayne, IN
Report this to a Moderator Report this to a Moderator
 25-Apr-2006 20:23
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

You certainly want to baseline, probably a major, when you reach a deliverable milestone in the project. If there are some minor milestones in the project then I'd tend to do minor baselines to coincide. You should lock down the project, do all the baselines, then unlock it.

Be advised that performance drops as modules get bigger, and they get bigger as History builds up. I'd baseline sluggish modules with some sort of minor+suffix in order to simply attempt to improve performance. I'd be tempted to baseline when the number of History reaches near 10,000; less if its a lot of Text history.

You could archive the module and restore it elsewhere; test load times; then baseline and test again. If there's a drastic improvement then baseline the original.

- Louie
Report this to a Moderator Report this to a Moderator
 26-Apr-2006 09:29
User is offline View Users Profile Print this message


Hazel Woodcock

Posts: 78
Joined: 6-May-2005

I agree with Louie, but this is a slightly different 'focus' on the problem.

Some things to consider:
- Baseline when you are at a point you might want to get back to in the future (hence the milestone advice).
- Baselining has the effect of wrapping up the history and storing it away and so improves module load times.
- Baselining has the effect of wrapping up the history and storing it away, so if you do it too often you get a very fragmented history and it is difficult to find what you are looking for in the audit trail.
- Baselining takes a copy of the module and stores it in the database, so the size of the database increases. This should not affect when you baseline, but may affect how you specify your server.

Hazel
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.