![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Baseline a project's modules Topic Summary: Created On: 24-Sep-2002 15:08 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I am trying to do the following: At some moments in time we need to make sure that all the formal modules within a project belong together. To do so, I want to make sure that all modules will get the same baseline (major.minor). I want to choose either the next minor baseline or the next major baseline. Here "next" means one higher then the highest baseline value currently in use by any of the modules in the project hierarchy. Because DOORS won't let me do this, I am writing a DXL script for it. Having found out what the highest baseline in use is, is not a problem. From that I create a baseline : // the following contain the highest found values int l_major int l_minor // create a new baseline int l_new_major = l_major int l_new_minor = l_minor + 1 // example! string l_new_suffix = null Baseline r_baseline = baseline (l_new_major, l_new_minor, l_new_suffix) ... But when I use this in the following call: //open the module for editing, like you have to when baselining from DOORS's menu r_module = edit (r_full_name, false) if r_module == null { b_can_open_modules = false } else { // create the module baseline create (r_module, r_baseline, t_annotation) close r_module } then the create call gives the following error: -R-E- DXL: <Line:205> cannot create specific baseline -I- DXL: <Line:285> execution halted Does this mean that the create actually only allows the nextMajor or nextMinor functions as the second argument?? This is what I find as examples in the Reference Manual, but the create call description does not say anything like that? Or am I doing something else wrong? Regards, Jan Willem |
|
![]() |
|
![]() |
|
[1] Rather than letting your DXL die at the error you can probably trap it via:
// See noError and lastError in the DXL manual string ErrMess noError() create(...) ErrMess = lastErr() if (!null ErrMess) { print "Error creating baseline for module " Name ":\nErrMess "" } [2] I believe you cannot skip major or minor designations: you cannot create baseline 5.2 unless there exists some 5.1 baseline; and you cannot create a 5.0 baseline unless there exists some 4.x baseline. You can check this using the above Trap handling. Let it run for all modules expecting that the module with the highest designations will NOT fail, whereas all others will fail. [3] The long term solution will probably be either to [3a] Artificially and manually do a bunch of baselines for each module making them all the same; then delete the intermediate (and useless) baselines. [3b] Maintain a "System Baseline Version Description Document" (VDD) outside of DOORs that shows which modules (their names respective baseline designations) are all in "sync" with each other at some specific point in time. When baselining, insert some VDD designation in the baseline "description" field. - Louie |
|
![]() |
Telelogic DOORS
» Change Management
»
Baseline a project's modules
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.