The easiest way to give an overview of the functionality of TaskJuggler is with an example.
Refer to section The Example: Accounting Software for a printout of the example.
In this project, we plan to create an accounting program. The project starts on January 16, 2002, and its end is planned for June 30, 2002. The project will consist of the following tasks:
The developers set up the specification for the software and documentation.
This is the whole process of coding the software. It includes the following subtasks:
Connection procedures to the database.
Creating the user interface.
Creating the calucation and computing routines for the data.
Testing the software. There are two stages of software testing:
Test the software in alpha stage.
Test the software in beta stage. The customer normally takes part in this beta test phase.
Creating the printed user manual
This task includes all steps necessary to communicate to the customer. This is an important task, as it defines the basic milestones of the project. For example, we cannot start the project before the contract is signed. It is also important to check the planned date of shipping the software to the customer.
This process consist of the following subtasks:
This milestone defines the start of the project.
This marks the start of the beta test. Normally, the customer wants to see a beta version, so this is also a milestone.
This is the date when the project has ended. Software is in final stage, the manual is ready and printed, and everything is shipped to the customer.