Install Planner
Task 2: Choose a Task
Tracking Scenario
Note: Before you proceed, you
should already have completed
Task 1: Establish the LANSA Master System.
LANSA's Task Tracking facilities are
designed to:
- Track the application changes that
developers make
- Prevent developers from accidentally
interfering with each others work.
Select from one of the following 3
scenarios (they are named N, U or T).
Choice 1 – Highly Disciplined
Developer Approach
|
|
On some small projects involving
highly disciplined developers the
administration cost of establishing
and maintaining a task tracking and
object locking regime may be
minimized by effectively turning it
off. |
Choice 2 Task Tracking – Object
Locking Only
|
|
On some small to medium projects
involving disciplined developers the
administration cost of establishing
and maintaining a task tracking
regime may be minimized by limiting
its usage to object locking only.
In this scenario developers are
exclusively assigned a task
identifier that they use for life of
a project (or some other unit of
work). At any point in time this
task identifies the objects they
currently have locked and prevents
other developers on the same (or
different) projects from
accidentally interfering with them
while they are locked. |
Choice 3 Task Tracking – Fully Enabled
|
|
On medium to large projects
involving multiple developers this
is the recommended task tracking
scenario that you should use.
Projects (or some other unit of
work) are assigned a short task
identifier (eg: PPPP). No one but
the project manager/administrator is
authorized to use the PPPP task.
This task is called the parent or
owner task.
Developers working on project
PPPP are each exclusively assigned a
child or sub task named PPPPXXX
where XXX identifies the developer
and PPPP identifies the parent or
owner project.
As each developer works, their
work is locked under their exclusive
task PPPPXXX. This prevents objects
they are working on from being
altered by other developers working
on the same or different projects.
When developers complete a unit
of work within a project, the
project manager/administrator
transfers the completed objects from
task PPPPXXX back to the parent
project task PPPP.
The parent project PPPP retains
the complete task tracking history
of the project and continues to
prevent the project object(s) from
being accidentally altered by other
developers (even those working on
project PPPP). |
When you have selected the scenario that
suits your situation, please download a PDF
with the steps to configure the chosen
scenario.
- To view on-line, click the link
below
- To save a copy to your PC, click the
link with the right mouse button and
choose the "save target as" option.
When you have completed configuring task
tracking, please proceed to
Task 3: Choose a Development Scenario.
|
