![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Benefits of the java client for the developers Topic Summary: Created On: 12-Apr-2005 15:17 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
The new java client provides the following benefits: 1) The support of daily build management activities in the java client will ease the deployment of the java client in the development teams 2) Developers have a better understanding of their development environment managed by SYNERGY/CM thanks to the usability and the functional completion of the java client Do you agree? Please let us know your feedback and comments on this topic. |
|
![]() |
|
![]() |
|
See my comments below:
>1) The support of daily build management activities in the java client will ease the deployment of the java client in the development teams I assume the implication here is that because the build managers will be using the Java Client more, they will encourage and be able to help the developers use the Java Client more. This is not a bad assumption for at least some teams, but there will still be many build managers that have to use the Classic Client on a regular basis. Because of this, they may also chose to continue to use ONLY the Classic Client (rather than switching back and forth, or running both). The biggest road blocks will the lack of DCM support and the fact that many teams will still not be able to use baselines (and therefore still need to copy tasks). >2) Developers have a better understanding of their development environment managed by SYNERGY/CM thanks to the usability and the functional completion of the java client Yes, they have an easier to use interface, that is more consistent, with access to additional features that they can not access from the Classic Client. I highly recommend to all of my users (even under v6.3) that they use the Java Client when doing developer work (even if they are also a build manager). But, understanding of the tool, and to some extent use of the tool, is still cloaked by terminology and implmentations/concepts that are at times unnecasarily confusing to my users. Todd Alden |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.