1. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT related and supported tools Sebastian Scholze, ATB - Institute for Applied System Technology Bremen GmbH 01.07.2003, Sofia

2. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Agenda The presentation is structured in the following chapters: –Introduction –Refactoring Overview / Tools –Common development platform Overview / Tools –Unit Testing Overview / Tools –Continuous Integration Overview / Tools –Putting all together –Planning and Tracking Overview / Tools

3. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Introduction We want to set up an development environment during this course, with which you are able to do/support the following: –IDE with refactoring support –IDE with Unit-Testing support –Automatic build-system Automatic creation of Test-Cases (skeletons) and Test-Suites Automatic maintenance of Test-Cases Automatic execution of the Unit-Tests Automatic / Continuous integration –Planning and Tracking of a project

4. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Introduction How to do Tool-Supported Refactoring? –with Eclipse How to do Tool-Supported Unit-Testing? –with Eclipse and Junit How to create Unit-Tests and Test-Suites? –with JUnit and JunitDoclet How to automate Unit-Testing and Unit-Test creation? –with Ant How to establish continuous integration with tools? –with Ant and CruiseControl How to plan XP? –with XPlanner How to set up a common development platform

5. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Common development platform Source-Code –Code conventions (e.g. SUNs Java Code Conventions) –Documentation conventions (e.g. JavaDoc for API- Documentation) Infrastructure –Common directory structure To ensure each team member has the same “environment” –Common build system To ensure each team member is able to compile the sources also they are using different tools –Unit-Testing (at least for the interfaces) To ensure that at least the interfaces are implemented correctly (which helps while integrating) –Common source repository

6. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Common development platform - Tools Common source repository (e.g. CVS, VSS) –To ensure that the team is always working on the same sources Continuous integration –The source code is build automatically in defined intervals –The source code is automatically tested against the developed unit tests –The source code is automatically deployed as an integrated version –Automatic notification system Common Planning system (e.g. XPlanner) Common Bug-Tracking system (e.g. Bugzilla, Mantis)

7. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Questionnaire What do you expect from the tools? What do you think is missing in „your“ tools? Where is tool support helpful? Can you plan & track your projects in your environment?

8. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Preparation What tools we/you need: –Sun JDK 1.4 –Eclipse 2.1 –JUnit 3.7 –JunitDoclet 1.02 –Ant 1.52 –CruiseControl 2.02 –XPlanner 0.4 –Servlet Container (e.g. Tomcat) –Source Code Control System (e.g. CVS, VSS) –Bug-Tracking System (e.g. Bugzilla, Mantis) –Mailserver (e.g. sendmail, James)

9. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Refactoring - Overview Advantages of Refactoring –Supports the discipline in the teams –Refactoring keeps the code simple –Simple design/code increases the maintainability Challenges of Refactoring –Refactoring “by hand” is slow –Refactoring “by hand” is error-prone –Sometimes only practicable by “experts” Why using tools to refactor? –Less erroneous than refactoring by hand –Much faster than refactoring by hand –Easier than refactoring by hand

10. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Refactoring with Eclipse Why Eclipse? –Eclipse is free (CPL) –Open plug-in architecture –Java & C++ support –Platform independant

11. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Refactoring with Eclipse Supported refactoring pratices in Eclipse –Rename class / field / method / package –Move class / field / method –Change method signature –Convert anonymous class to nested class –Convert nested type to top level –Pull up constructor / field / method –Push down field / method –Extract interface –Inline –Extract constant / local variable / method –Convert local variable to field –Encapsulate field Other helpful features in Eclipse –“Automatic” creation of “getter / setter” methods –“Automatic” Test-Case generation

12. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Refactoring with Eclipse Refactoring – Example –Demonstration of the Refactoring practises provided in Eclipse

13. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Collective Code Ownership

14. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Common Source Repository - CVS What is CVS (the concurrent versions system)? –CVS is a centralized file storage system, which maintains a history of changes to each file Any version of the file can be easily recovered, as well as a complete set of activity history and commentary. –CVS is Open-Source –CVS supports Distributed development –CVS is platform independent CVS key features –Revisions –Tagging –Branching –Merging –Recovering

15. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Common Source Repository - CVS Advantages –Decentralised –Concurrent editing –Open standard –Integration-support in many IDEs Challenges –Developer has to learn another tool –Discipline is required

16. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Automation / Common build system - Overview Why using an automation tool? –To ensure that every team member is building the same system Why use ant? –XML buildfiles –Platform independent –Extensible –Integration –Because of continuous integration with cruisecontrol

17. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Automation with Ant – Directory structure A generic directory structure is required –to support team development on each computer you have the same directory environment –to support different IDEs you can use ant although you are using different IDEs in your teams –to support “real” automation automatic “continuous integration”

18. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Automation with Ant – build.xml Ant is a Java-based build tool –Ant is a utility using xml that was developed in response to frustration with makefiles. –In a nutshell, you write an xml document, 'build.xml' which builds your programs and checks for what depends on what. –Ant is platform independent –Ant can be integrated into many IDEs –Ant can be use for automation

19. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Automation with Ant – Running ant Preparation –The following environment variables have to be set $JAVA_HOME has to point to the home directory of your java installation $ANT_HOM has to point to the home directory of your ant installation Running –Running from the shell “ant build.xml ” –Running from Eclipse “Run ant” command in Eclipse Result –Completed target –Output from Ant over success or failure of the chosen target

20. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Unit Testing with tools - Overview Advantages of Unit-Testing –Software is always developed against the Unit-Test –Higher correctness of the software –Easier to distribute work, because everybody is coding against the Unit-Tests –Easier integration, because of tested interfaces –Easier maintainability of the source code Challenges of Unit-Testing –Really covered all “public” methods? –Creation of test-skeletons is time consuming and annoying work –While refactoring the software, you have to refactor the Unit-Tests also Why using Tools for Unit-Testing? –Less erroneous creation of Test-Cases –Time consuming and annoying work – creation of test stub’s and test suites – is done automatically

21. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Unit Testing with tools - Eclipse Tool supported test-generation –Test-Cases and Test-Suites can be created with an Eclipse wizard Advantages –The wizard creates test stubs for selected methods Disadvantages –The wizard must be used for all classes –Cannot update Test-Cases for edited or refactored classes

22. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Unit Testing with tools - Eclipse Test Execution –Junit in Eclipse Advantages –Integrated into IDE –Directly navigate to an occurred error Disadvantages –Testing must be started manually

23. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Unit Testing with tools – What is missing How to create Test-Case skeletons automatically? –with the help of JUnitDoclet How to create easy Test-Cases automatically? –with the help of JUnitDoclet How to keep the Test-Cases actual while refactoring the source? –with the help of JUnitDoclet How to integrate JUnitDoclet into “your” IDE? –with the help of Ant How to automate the process of Test-Case creation, compilation and testing? –with the help of Ant together with JUnitDoclet

24. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Unit Testing with tools - JUnitDoclet JUnitDoclet –JUnitDoclet works as a plug-in for SUN’s JavaDoc tool but instead of generating HTML documentation it generates test classes and methods. –For every public method of every class in the application a JUnit Test- Case is created. –In addition all Test-Cases of a package and its subpackages are added to a JUnit Test-Suite. Key Benefits –Independence of IDEs and capability for automation, –generation of test classes and methods for complete package hierarchies (including Test-Suites), –incremental generation through merging with existing tests and updating after simple refactorings, –adaptability according to users needs through templates

25. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Example Proposed directory structure Required tools –Ant –JUnit –JUnitDoclet

26. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Application classes

27. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Compiled Application classes Preparation –The application classes are compilable. –This is necessary for javadoc to be able to parse the source code of them. Compile –“ant compile” or –“Run Ant” command in Eclipse Choose target “compile” Result –Compiled application classes

28. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet – Generating Test-Cases Preparation –Javadoc is parsing the source code of the application classes –From the collected information, JUnitDoclet writes TestCases and TestSuites (preferably) to a different directory –For each package there is a TestSuite. For each public, non-abstract class there is a TestCase For each public method there is a test method. In case of accessor tests, set and get are tested together Generate –“ant junitdoclet” or –“Run Ant” command in Eclipse Choose target “junitdoclet” Result –Generated TestCases and TestSuites

29. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Generated Test- Case/Suite

30. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Compiled Tests Preparation –The TestCases are compilable. Compile –“ant junitcompile” or –“Run Ant” command in Eclipse Choose target “junitcompile” Result –Compiled application classes

31. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools JUnitDoclet - Running the Tests Preparation –Compiled TestCases Testing –“ant junittest” or –“Run Ant” command in Eclipse Choose target “junittest” Results –Do your tests pass? You will see the result in the testresult.txt –If the tests fail, go back to step 2.

32. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Continuous Integration with Cruisecontrol - Overview What is Continuous Integration? –Continuous Integration by Martin Fowler and Matthew Foemmel: „An important part of any software development process is getting reliable builds of the software. Despite it's importance, we are often surprised when this isn't done. We stress a fully automated and reproducible build, including testing, that runs many times a day. This allows each developer to integrate daily thus reducing integration problems.“ What is CruiseControl? –CruiseControl is a framework for a continuous build process. –It includes, but is not limited to, plugins for email notification, Ant, and various source control tools. –A web interface is provided to view the details of the current and previous builds.

33. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Continuous Integration with Cruisecontrol - Overview What we want to achieve with CruiseControl? –Defined build loops –Automatic integration of the latest sources –Automatic test of the compiled application classes –Automatic notification To achieve this, CruiseControl has to do the following: –Get the latest version of the application classes from the source repository –Build the latest sources –Get the latest version of the Test-Cases and Test-Suites from the source repository –Build the latest Test-Cases –Run the Test-Cases against the Application-Classes –Notify the users about build/test success or failures

34. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools CruiseControl - Configuration of the build loop

35. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools CruiseControl – Configuration of the buildfile

36. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools CruiseControl – Web Interface The web-interface presents the results of the build loops. –Links to current & previous builds The right side of the page presents the results of the build, including –compilation errors, –test results, –and details about what files have changed since the last build. How does it work? –The web-interface uses Stylesheets to transform the XML- output from CruiseControl

37. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Putting all together Real-Life example –Create Code –Create Test-Cases –Run Test-Cases –Refactor Code –Recreate Test-Cases –Re-Run Test-Cases –Integrate project into CruiseControl

38. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Planning and Tracking with Tools - Overview

39. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Planning and Tracking with Tools - Overview

40. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Tracking with Tools - Bugzilla Bugzilla is one example of a "Defect Tracking Systems„ –A defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Key features: –integrated, product-based granular security schema –inter-bug dependencies and dependency graphing –advanced reporting capabilities –a robust, stable RDBMS back-end –extensive configurability –a very well-understood and well-thought-out natural bug resolution protocol –email, XML, console, and HTTP APIs –available integration with automated software configuration management systems, including CVS (through the Bugzilla email interface and checkin/checkout scripts)

41. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Tracking with Tools - Bugzilla But why should you use Bugzilla? –Bugzilla is very adaptable to various situations. Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to configuration management and replication problems –Bugzilla can dramatically increase the productivity and accountability of individual employees by providing a documented workflow and positive feedback for good performance. Bugzilla puts the power in your hands to improve your value to your employer or business while providing a usable framework for your natural attention to detail and knowledge store to flourish.

42. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Bugzilla – Bug-List

43. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Bugzilla – Enter New Bug

44. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Bugzilla – Query Page

45. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Bugzilla – Statistics

46. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Bugzilla – Product page?

47. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Planning and Tracking with Tools - XPlanner XPlanner –XPlanner is a project planning and tracking tool for eXtreme Programming (XP) teams. –Key Features Simple planning model Virtual note cards Support for recording and tracking projects, iterations, user stories, and tasks Online time tracking Metrics generation (team velocity, individual hours,...) SOAP interfaces for advanced XPlanner integration and extension.

48. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner Planning and tracking in XPlanner –Customer and developers define a release plan Allows the definition of future iterations –Customer defines user stories to be implemented next User-Stories can be assigned to iterations and prioritized –Developers estimated the effort required to implement the stories A story can be estimated before tasks for a story are defined Define tasks required to implement the story –Implement the stories –Track progress The time, worked on a task is tracked in the form of a progress bar

49. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner Planning and tracking in XPlanner –Customer and developers define a release plan Allows the definition of future iterations –Customer defines user stories to be implemented next User-Stories can be assigned to iterations and prioritized –Developers estimated the effort required to implement the stories A story can be estimated before tasks for a story are defined Define tasks required to implement the story –Implement the stories –Track progress The time, worked on a task is tracked in the form of a progress bar

50. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Overview Overview of all projects Functions to –create /edit projects –select a project –add / edit people

51. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Project view Overview of a selected project Overview of all iterations for the selected project Functions to –edit the selected project –create / edit iterations –select an iteration

52. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Iteration view Overview of a selected iteration Overview of all user stories for the selected iteration –completed tasks –open tasks –estimated effort Functions to –edit the selected iteration –create / edit user-stories –select an user story

53. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Iteration view

54. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – User-Story view Overview of a selected user story Overview of all tasks for the selected user story –completed tasks –open tasks –responsability Functions to –edit the selected user story –Add comments for a user story –create / edit tasks –select a task

55. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner –Task view Overview of a selected task Overview of all tasks for the selected user story –completed tasks –open tasks Functions to –edit the selected task –add working time to tasks –complete / reopen a task

56. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Metrics per Iteration Metrics-Overview of a selected iteration

57. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools XPlanner – Integration view Metrics-Overview of a selected iteration

58. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Summary It was demonstrate how the incremental development can be kept executable by tool support The demonstrated tools Ant, Bugzilla, Eclipse, CruiseControl, JUnit, JUnitDoclet and XPlanner showed that the development speed and quality is increasing It was shown how to setup and use the advantages of a powerfully built verification and integration system With the help of planning and tracking tools it is possible to measure the increase of development speed and software quality.

59. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Resources Tools –Anthttp://ant.apache.org –CVShttp://www.cvshome.org –Bugzillahttp://www.bugzilla.org –CruiseControlhttp://cruisecontrol.sourceforge.net –Eclipsehttp://www.eclipse.org –JUnithttp://www.junit.org –JUnitDoclethttp://www.junitdoclet.org –WinCVShttp://www.wincvs.org –XPlannerhttp://www.xplanner.org

60. Sofia Bulgaria Summer School IST-2001-34488 eXPERT: Best Practice on e-Project Development http://www.esi.es/Expert 30 June - 2 July 2003 eXPERT Related and Supported Tools Resources Articles & Links –eXtreme Programming http://www.extremeprogramming.org/lessons.html –Lessons Learned http://www.extremeprogramming.org/lessons.html –Project Velocity http://c2.com/cgi/wiki?ProjectVelocity –Refactoring practises http://www.refactoring.com/catalog/index.html http://www.refactoring.com/catalog/index.html –Unit Testing http://www.junit.org