כמה כלים
זה פחות קשןר לנושא הפורום, אך מכיוון שמצאתי שמנהלי QA רבים (כולל אני) נאלצו לנהל בקרת תצורה ארשה לעצמי לענות. ישנם כמה כלים מובילים בתחום שידועים לי: 1. Rational Clear Case 2. Microsoft Source Safe 3. Borland Star Team 4. Eclipse (Open Code Project) כמה מילים על בקרת תצורה (אתר אוניברסיטה לונד) Configuration management is one of the key techniques for coordinating people working together in software projects. This is commonly understood and most Software Development Environments offers support for CM. In Eclipse this is trough Stellation and the CVS technology. When using a CM tool one quickly realize that there are operations that are less well supported. Structural changes, often called refactorings, such as renaming modules or moving them between directories are typically problematic, not supported by the CM tool. As a result such operations has to be performed outside of the tool, and the tool cheated by performing the operations as a Delete and a Create and thus loosing historical data as well as risking manual mistakes. When merging parallel work in systems that have undergone such changes the situation gets even worse. The importance of the problem sketched above depends on how often such changes might occur. In a traditional situation, with considerable upfront design and careful structuring before coding, the need for refactorings might be smaller. With the current growing interest for eXtreme Programming with its focus on simplicity and refactorings the problem gets much worse since structural changes is a frequent activity. Eclipse include support to perform refactorings, but the CM support for refactorings is much less developed
