![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: CM process improvements Topic Summary: Created On: 12-Apr-2005 15:23 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
The improvements in SYNERGY/CM 6.4 and SYNERGY/Change 4.4 deliver the following benefits: 1) The overall usability improvement will facilitate teams still working with an object based CM process to evolve and to use Task Based CM 2) The deeper integration of SYNERGY/Change with CM java client will facilitate SYNERGY/Change usage 3) The baseline administration improvements (mark for deletion, intermediate status) will encourage the usage of baseline in your development projects 4) Baseline compare improvements at the CR level and the deeper integration of SYNERGY/Change will encourage the implementation of a CR based process 5) Baseline compare improvements will facilitate the use of best development practices support by DOORS-SYNERGY/Change and TestDirector-SYNERGY/Change integrations (in allowing to understand which DOORS requirements implementation and which TestDirector Defects fix belongs a baseline) Do you agree? Please let us know your feedback and comments. |
|
![]() |
|
![]() |
|
Jean-Louis, I will attempt to respond to each of your points:
> 1) The overall usability improvement will facilitate teams still working with an object based CM process to evolve and to use Task Based CM We do not have any teams using an object based process so I cannot speak directly to this. I will say that the teams that have been tempted to use an object based method were so because of the lack of direct support for the easy reuse of object (accros active projects). I don't see this issue being addressed in this release. > 2) The deeper integration of SYNERGY/Change with CM java client will facilitate SYNERGY/Change usage Time will tell. The integration that has been introduced is certainly a step in the right direction. > 3) The baseline administration improvements (mark for deletion, intermediate status) will encourage the usage of baseline in your development projects The mark for deletion is a nice addition, but will not by itself be a hugh encouragement. (One consideration that seems to have been missed is how to handle mark for deletion in a DCM environment). The intermediate status is a nice concept, but w/o the ability to control the default behaviour when a baseline is created, this feature may actually dis-courage the use of the baseline feature. Other missing features for baselines include: 1) Not able to compare project hierarchies of projects included in the baseline (this would be a nice feature, but does not prevent people from using baselines). 2) There is still no improvements on the ability to use baselines in a cross site (DCM) development environement. This our biggest hinderence to having all programs use baselines. (Many program could work around this limitation, IF remote build management was usable [e.g. did not DCM ALL releases when releases are included in a DCM.]). > 4) Baseline compare improvements at the CR level and the deeper integration of SYNERGY/Change will encourage the implementation of a CR based process Again, a step in the right direction. The ability to do a true CR based configuration management would be good. (Can you, today in 6.4, see "CR conflicts"? That is, see which CRs are only partially included in a build? ... I appoligize, haven't had time to test for this feature.) > 5) Baseline compare improvements will facilitate the use of best development practices support by DOORS-SYNERGY/Change and TestDirector-SYNERGY/Change integrations (in allowing to understand which DOORS requirements implementation and which TestDirector Defects fix belongs a baseline) I don't have enough experience with the intergrations to be able to answer this question. Todd Alden |
|
![]() |
Telelogic SYNERGY
» SYNERGY BETA Forum
»
CM process improvements
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.