%
%   Note that any line beginning with a percentage character is ignored
%   as are blank lines
%

%   Somewhere in the file you should define the four keywords title,
%   planner, version (of the plan) and base (base date: nothing can happen
%   earlier than this).  If you don't define them then UNKNOWN is assumed
%   for title, planner and version and 01/01/80 is assumed for the basedate

title Example Plan for Tutorial Purposes
planner Chris Hobbs
version 1.0
base 11/6/90

holiday 25/12/90
holiday 26/12/90

%
% It is not necessary to specify the types of resources but if you do
% then the program will add their usages up for you.  Resources may
% be people or things ('scopes, ovens, etc) and in the future you will
% be able to associate costs with them

% Here are the resources
% ======================

resource programmers
resource analysts
resource testers

% Activities must be specified (otherwise you've got nothing to schedule).
% With each activity you can associate all or any of the following 
% keywards (in brackets as shewn):
%
%    earliest     (earliest start date: default is basedate)
%    duration     (shortest, probable and maximum durations (days):
%			default is zero)
%    cost         (direct cost associated with the activity:
%			default is zero)
%    needs        (quantity and type of resource needed:
%			default no resources)

% If there is more to come then end the line with a plus sign

% Here are the activities
% =======================

activity start 		           (earliest 12/01/91) +
				   (duration 1,1,1)
activity finish
activity prepare feasibility study (duration 10,10,10) (needs 2 analysts) 
activity write specification       (duration 20,25,40) +
				   (needs 5 analysts) +
				   (cost 100)
activity design system             (duration 20,25,40) +
				   (needs 3 analysts) +
				   (needs 1 programmers) +
				   (cost 230)
activity code system               (duration 10,10,10)
activity test system               (duration 10,10,10)
activity write test specification  (duration 15,20,25) +
				   (needs 2 testers) +
				   (needs 1 programmers) +
				   (needs 1 analysts) +
				   (cost 150)

% Again, there is no need to specify dependencies but they are
% normally needed.  The format is "dependency <percentage> <first> -> <last>
% where the given percentage of the first must be complete before the
% last starts

% Here are the dependencies
% =========================

dependency 100 start                     -> prepare feasibility study
dependency 100 prepare feasibility study -> write specification
dependency 100 write specification       -> design system
dependency 80  design system             -> code system
dependency 100 code system               -> test system
dependency 100 write test specification  -> test system
dependency 100 prepare feasibility study -> write test specification
dependency 100 test system               -> finish
