![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Baseline Topic Summary: How often Created On: 25-Apr-2006 19:33 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
Telelogic DOORS
» Administration
»
Baseline
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.