|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T
Length: 247501 (0x3c6cd)
Types: TextFile
Names: »TRACKER_DOCUMENTATION«
└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
└─⟦5cb1d1d7f⟧ »DATA«
└─⟦3b1ee7bd8⟧
└─⟦this⟧
--::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--uguide.m
--::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
XDJDE FORMAT=P06PDE,DUPLEX=NO,MARGIN=(.75 IN),END;
\f
The software described in this manual was
developed at GTE Western Division on DEC
equipment (VAX 11/780) using the VAX/VMS
Version 4.1 operating system.
Page i
CONTENTS
CHAPTER 1 INTRODUCTION
1.1 OVERVIEW OF TRACKER . . . . . . . . . . . . . . . 1-1
CHAPTER 2 INSTALLING TRACKER
2.1 CHANGING TRACKER PARAMETERS . . . . . . . . . . . 2-1
2.2 COMPILING AND LINKING TRACKER . . . . . . . . . . 2-1
CHAPTER 3 USING TRACKER
3.1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 OPERATION . . . . . . . . . . . . . . . . . . . . 3-3
3.3 CREATING A TRACKER INPUT FILE . . . . . . . . . . 3-3
3.3.1 Entering Global Data . . . . . . . . . . . . . . 3-3
3.3.2 Entering Activity Data . . . . . . . . . . . . . 3-4
3.3.3 Entering Milestone Data . . . . . . . . . . . . 3-5
3.3.4 Entering Personnel Data . . . . . . . . . . . . 3-6
3.3.5 Entering Subsystem Data . . . . . . . . . . . . 3-8
3.3.6 Entering Element Data . . . . . . . . . . . . . 3-9
3.4 MANIPULATING THE TRACKER DATA . . . . . . . . . 3-12
3.4.1 Data Menu . . . . . . . . . . . . . . . . . . 3-12
3.4.1.1 Global Data Operations Menu . . . . . . . . 3-13
3.4.1.2 Activity Operations Menu . . . . . . . . . . 3-14
3.4.1.2.1 Adding An Activity . . . . . . . . . . . . 3-14
3.4.1.2.2 Deleting An Activity . . . . . . . . . . . 3-16
3.4.1.2.3 Modifying An Activity . . . . . . . . . . 3-16
3.4.1.2.3.1 Activity Data Menu . . . . . . . . . . . 3-17
3.4.1.2.4 Displaying An Activity . . . . . . . . . . 3-18
3.4.1.3 Milestone Operations Menu . . . . . . . . . 3-18
3.4.1.3.1 Adding A Milestone . . . . . . . . . . . . 3-19
3.4.1.3.2 Deleting A Milestone . . . . . . . . . . . 3-20
3.4.1.3.3 Modifying A Milestone . . . . . . . . . . 3-20
3.4.1.3.3.1 Milestone Data Menu . . . . . . . . . . 3-21
3.4.1.3.4 Displaying A Milestone . . . . . . . . . . 3-22
3.4.1.4 Personnel Operations Menu . . . . . . . . . 3-22
3.4.1.4.1 Adding A Person . . . . . . . . . . . . . 3-22
3.4.1.4.2 Deleting A Person . . . . . . . . . . . . 3-23
3.4.1.4.3 Modifying A Person . . . . . . . . . . . . 3-25
3.4.1.4.3.1 Personnel Data Menu . . . . . . . . . . 3-25
3.4.1.4.4 Displaying A Person . . . . . . . . . . . 3-26
3.4.1.5 Subsystem Operations Menu . . . . . . . . . 3-27
3.4.1.5.1 Adding A Subsystem . . . . . . . . . . . . 3-27
3.4.1.5.2 Deleting A Subsystem . . . . . . . . . . . 3-28
3.4.1.5.3 Modifying A Subsystem . . . . . . . . . . 3-28
3.4.1.5.3.1 Subsystem Data Menu . . . . . . . . . . 3-29
3.4.1.5.4 Displaying A Subsystem . . . . . . . . . . 3-30
3.4.1.6 Element Data Operations Menu . . . . . . . 3-30
3.4.1.6.1 Adding An Element . . . . . . . . . . . . 3-31
Page ii
3.4.1.6.2 Deleting An Element . . . . . . . . . . . 3-34
3.4.1.6.3 Modifying An Element . . . . . . . . . . . 3-35
3.4.1.6.3.1 Element Data Menu . . . . . . . . . . . 3-35
3.4.1.6.4 Displaying An Element . . . . . . . . . . 3-37
3.4.1.6.5 Quick Update Of The Current Size . . . . 3-37
3.4.1.6.5.1 Element Data Groups Menu . . . . . . . . 3-37
3.4.1.6.6 Quick Update Of The Activity Percent
Complete . . . . . . . . . . . . . . . . . 3-38
3.4.1.6.6.1 Element Data Groups Menu . . . . . . . . 3-39
3.4.1.7 Exiting The Data Menu . . . . . . . . . . . 3-40
CHAPTER 4 NOTES ON THE TRACKER CALCULATIONS
4.1 CALCULATIONS USED IN TRACKER . . . . . . . . . . . 4-1
4.1.1 Sorting The Elements . . . . . . . . . . . . . . 4-1
4.1.2 Man-Hours Remaining . . . . . . . . . . . . . . 4-1
4.1.3 Completion Dates . . . . . . . . . . . . . . . . 4-2
4.1.4 Percent Complete . . . . . . . . . . . . . . . . 4-2
4.1.5 Reset The Data . . . . . . . . . . . . . . . . . 4-3
CHAPTER 5 TRACKER REPORTS
5.1 PRINTING TRACKER REPORTS . . . . . . . . . . . . . 5-1
5.1.1 Report Menu . . . . . . . . . . . . . . . . . . 5-1
5.2 SAMPLE TRACKER REPORTS . . . . . . . . . . . . . . 5-3
5.2.1 Parameter Data Report . . . . . . . . . . . . . 5-4
5.2.2 Comments Report . . . . . . . . . . . . . . . . 5-5
5.2.3 All Element Status Report . . . . . . . . . . . 5-6
5.2.4 List By Subsystem Report . . . . . . . . . . . . 5-9
5.2.5 List By Milestone Report . . . . . . . . . . . 5-10
5.2.6 List By Person Report . . . . . . . . . . . . 5-11
5.2.7 Subsystem Summary Report . . . . . . . . . . . 5-12
5.2.8 Milestone Summary Report . . . . . . . . . . . 5-13
5.2.9 Lines Of Code Per Subsystem Report . . . . . . 5-14
5.2.10 Percent Complete Report . . . . . . . . . . . 5-15
5.2.11 Distribution Of Work Remaining Within Subsystem
Report . . . . . . . . . . . . . . . . . . . . 5-17
5.2.12 Completion Date For Milestones Report . . . . 5-19
5.2.13 Reports Printed List . . . . . . . . . . . . . 5-20
APPENDIX A
A.1 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . A-1
Page 1
XDJDE FORMAT=P06PDE,DUPLEX=YES,END;
\f
CHAPTER 1
INTRODUCTION
TRACKER is an ADA conversion of the original INPREP and
TRACKR programs written in IFTRAN. The Ada version, TRACKER, is
one program that combines the two previous Iftran programs. It
was developed under the VAX/VMS Version 4.0 environment using the
DECAda compiler.
1.1 OVERVIEW OF TRACKER
TRACKER is an interactive, menu driven management tool used
for tracking the progress on a project (mainly software
projects). It will calculate percent complete and dates of
completion. By using the data entered by the user and the
calculations obtained, several different reports can be produced.
A data file must be created for each project being tracked.
Once this file has been initially created through TRACKER
prompting, updating the data is optional before writing the
reports for each run of TRACKER.
The project being tracked is broken down into subsystems.
Each subsystem contains several routines or components that have
a common purpose. For example, one project may have subsystems
for REPORT GENERATION, ANTENNA MANIPULATION, and SIGNAL
PROCESSING.
The project also is broken into phases of development,
otherwise known in TRACKER as activities. Each routine or piece
of the project must go through each phase of development. A
maximum of 10 activities may be defined for a project. For
example, most software projects have activities similar to the
following: HIGH LEVEL DESIGN, DETAIL DESIGN, CODE, UNIT TEST,
and INTEGRATE.
Several people may be assigned to a project at one time.
TRACKER takes into consideration the person's work speed
(measured in units of work produced per hour) and up to three
pairs of start/stop dates for each person.
INTRODUCTION Page 1-2
A maximum of 99 Milestones may be defined in a given
project. Each milestone is assigned a number, description and
due date. A milestone describes a significant point in the
project development. In TRACKER, the milestones are defined
similar to "this group of routines or components is completely
finished", not as "high level design is done" or "Preliminary
Design Review is complete". TRACKER can only determine when a
group of routines is complete, not if a phase of development is
complete.
Each routine or component of the project is entered into
TRACKER as an ELEMENT. The element is given a description, a
unique abbreviation of up to 6 characters in length, and a size
measured in some unit. In software, the unit of measurement for
size is usually SLOC's or Source Lines Of Code. The element is
also assigned to one subsystem and one milestone. One person may
be assigned to work on the entire element or a person could be
assigned to each phase of development in the element, meaning,
more than one person could work on any given element.
Several routines can be produced from this data. These
include:
1. Parameter Data List
2. All Element Status Report
3. List by Subsystem Report
4. List by Milestone Report
5. List by Person Report
6. Subsystem Summary Report
7. Milestone Summary Report
8. Work Units per Subsystem Report
9. Percent Completion of Work within Subsystem Report (This
report shows the percent complete based on the current
size estimate and the original size estimate.)
10. Distribution of Remaining Work within Subsystem Report
(This report shows the percent complete based on the
current size estimate and the original size estimate.)
11. Completion Date by Milestone Report
\f
CHAPTER 2
INSTALLING TRACKER
2.1 CHANGING TRACKER PARAMETERS
There are 3 parameters which may be modified before building
the executable version of TRACKER. These parameters are located
in package DATA_PKG, file DATAPKG.ADA. The parameters describe
the working calendar of the company installing TRACKER and are
used to predict completion dates. The holidays and vacation days
are evenly distributed throughout the calendar year. The
parameters are as follows:
Name of Constant Default Description
---------------- ------ -----------
DAYS_IN_WORK_WEEK 5 number of work days in the 7 day week
HOURS_IN_WORK_DAY 8.0 number of hours worked in 1 work day
WORK_DAYS_OFF_IN_YEAR 10 number of holidays and vacation days
on an average
In order to change the constants, the person installing the
software must edit the file DATA_PKG.ADA. After the parameters
have been changed to the desired values, the TRACKER executable
image is ready to be built.
2.2 COMPILING AND LINKING TRACKER
If TRACKER is being installed on a VAX running VMS, the
files can be compiled by submitting the command file called
COMALL.COM. If some other system is being used, the Ada files
should be compiled in the following order:
CALENDARS.ADA
CALENDARB.ADA
LISTPKGS.ADA
LISTPKGB.ADA
DATAPKG.ADA
VT100S.ADA
VT100B.ADA
PROMPTS.ADA
INSTALLING TRACKER Page 2-2
PROMPTB.ADA
TRACKER.ADA
INITTR.ADA
SETUPTR.ADA
MANDATA.ADA
PRIOR.ADA
CALCTIME.ADA
CHKPCT.ADA
FIXDATA.ADA
FIXRESET.ADA
FIXORIG.ADA
WRDATA.ADA
MENUDR.ADA
GETDATA.ADA
GLOBAL.ADA
AC.ADA
MS.ADA
PR.ADA
SS.ADA
EL.ADA
REPORT.ADA
CALCPCT.ADA
RCOMMENTS.ADA
RDATEDONE.ADA
RLISTEL.ADA
RLISTMS.ADA
RLISTPR.ADA
RLISTSS.ADA
RPAGE.ADA
RPARAM.ADA
RPCTBYSS.ADA
RPRINTED.ADA
RSUMMS.ADA
RSUMSS.ADA
RWORKBYSS.ADA
RWORKDIST.ADA
After all units have been successfully compiled, they can be
linked together, forming the executable version. It may be
desirable to define a system command to invoke TRACKER. On the
vax in would be similar to:
$ TRACKER :== run [some_directory]TRACKER.EXE
\f
CHAPTER 3
USING TRACKER
3.1 OVERVIEW
The TRACKER program is completely prompt and menu driven.
At certain points in the program, the user is not allowed to
continue until proper data is input. The prompting mechanism
works in the following manner: If the data being requested has a
default value, the user may respond with a carriage return. The
default value is displayed to the right of the "<cr>=" symbol.
If the user responds with '?', then the prompt will be expanded
to give the user more information on the type of data to enter.
For data that does not have a default value, a carriage return or
'?' will display the extended prompt. Otherwise, the user should
enter the data as requested after the colon. If the data entered
is invalid, the user will be prompted again until valid data is
received. For the prompt/response examples in this manual, the
user's response will be underlined. "<CR>" stands for carriage
return.
The user is allowed to include an optional comments file
with the TRACKER reports. If all reports are printed, the user
will be prompted for the comments filename. Otherwise, the user
may choose to include a comments file from the report menu. The
comments file must be a text file, which will be copied directly
into the reports. For example, the user might include a runoff
file, diagrams, notes, or tables.
The input file to the TRACKER program is initially created
by running TRACKER. TRACKER requires that there be at least one
activity, one milestone, one person, one subsystem, and one
element at all times. The data that is entered by the user is
stored in a specific order by the TRACKER program, which can then
use this file again for the next run. If the data is modified, a
new version of the file will be generated. Do not attempt to
edit the input file! If you do, and the data is not in the
correct format, TRACKER will not read the input file. No error
correction is provided when reading the input file. The user
will be notified if the input file is not in the correct format.
USING TRACKER Page 3-2
Once the input file is read in, the user is allowed to
manipulate the data and print TRACKER reports. These reports are
put into an output file. The output file will have the same name
as the input file, except that it will have a ".rpt" extension.
USING TRACKER Page 3-3
3.2 OPERATION
If you are using a VAX/VMS system and TRACKER has been
installed, you may run TRACKER by typing the VAX command:
$ RUN TRACKER
You will see the TRACKER introduction displayed on the
terminal screen. After the screen is cleared, the following
question will be asked:
Do you have an existing TRACKER file that you
would like to use for this run?
[Y or N, <cr>=N] :
If you have run TRACKER before and would like to use that same
file either to modify the data or print reports, then type "Y".
Otherwise, you will be creating a new TRACKER file. You want to
type "N" or press carriage return if you are running TRACKER for
the first time, or if you want to track a different project by
creating a new TRACKER data file.
If you answered "yes" to the above question, you will be
prompted for the name of the input file. The data from that file
will then be read in. Refer to the section titled "Manipulating
The Tracker Data" to find out what to do next.
3.3 CREATING A TRACKER INPUT FILE
If you did not have an existing TRACKER file, you will be
prompted for the name of the file to create and forced to enter
at least one record of data for each data type. This is to
insure that TRACKER will have the minimum amount of data to print
complete reports. If you make a mistake or change your mind
about some of the data you have entered, don't worry. You will
be given a chance to add, delete, or modify the data you have
just entered after you have entered the minimum data
requirements. A sample session of the next sequence of questions
you will be asked follows.
3.3.1 Entering Global Data
First, you will be asked to enter the global data. Global
data contains information about the project in general. The
information to the right of the colon is the user's input. Here
is a sample global data input session:
____
Project Name : <CR>
USING TRACKER Page 3-4
What is the name of the project in 30 characters or less?
_______ _
Project Name : PROJECT X
____
Project Number : <CR>
What is the 3 digit project number?
Enter an integer in the range 0 to 999
_
Project Number : ?
What is the 3 digit project number?
Enter an integer in the range 0 to 999
___
Project Number : 800
_
Manager Name : ?
What is the project manager's name in 30 characters or less?
___ _______
Manager Name : MR. MANAGER
The tracker calculations are based on the
last day of a work week.
What is the date for this run?
_
e.g. 12/6/1985 ( <cr> = null date) : ?
Enter month/day/year where the month is 1..12, the day
is 1..31, and the year is 1901..2099
____
e.g. 12/6/1985 ( <cr> = null date) : <CR>
You cannot use a null date. Try Again!
The tracker calculations are based on the
last day of a work week.
What is the date for this run?
________
e.g. 12/6/1985 ( <cr> = null date) : 5/3/1985
3.3.2 Entering Activity Data
Next, you will be prompted to enter an activity. The
activity data describes the different phases of the project, how
important that activity is, and how far along you are. You may
have up to 10 activities. For example, you might have High Level
Design, Detail Design, Coding, Unit Test, and Integration as your
activities. Remember, you must enter one or more of the each of
the data types; activity, milestone, personnel, subsystem and
element. The following is a sample prompting session for
activities:
If you would like more information on the type of data
USING TRACKER Page 3-5
to enter for any of the following questions, enter '?'.
Otherwise, enter the data requested.
_
Activity Name : ?
Enter the name of the activity which is a
string of up to 10 characters.
______
Activity Name : DESIGN
What is this activity's percent of the project?
_
Percent ( <cr> = 0.0) : ?
Enter a number in the range 0.0 .. 100.0
_____
Percent ( <cr> = 0.0) : 100.0
____
Priority : <CR>
Enter the priority of the activity on a scale of 1 to 10.
_
Priority : 1
_
Consider [ y or n <cr>=y ] : ?
Do you want to consider this activity in the
Tracker calculations?
____
Consider [ y or n <cr>=y ] : <CR>
What percentage is available at start?
_
Percent ( <cr> = 0.0) : ?
Enter the a number in the range 0.0 .. 100.0
_____
Percent ( <cr> = 0.0) : 100.0
The number of activities = 1
Would you like to add another activity?
____
[ Y or N, <cr>=N ] : <CR>
3.3.3 Entering Milestone Data
After you have finished adding activities, you will be
prompted for the milestone information. A milestone describes
USING TRACKER Page 3-6
when you expect a group of elements to be completed. Several
elements may belong to a single milestone. You may define up to
99 milestones. The following is a sample session:
If you would like more information on the type of data
to enter for any of the following questions, type a '?'
Otherwise, enter the data requested.
_
Milestone Number : ?
Enter an integer in the range 1..99
_
Milestone Number : 1
Milestone Completion Number
____
( <cr> = milestone number ) : <CR>
What is the due date?
_
e.g. 12/6/1985 ( <cr> = null date) : ?
Enter month/day/year where the month is 1..12, the day
is 1..31, and the year is 1901..2099
________
e.g. 12/6/1985 ( <cr> = null date) : 6/1/1985
Milestone description :
____ __ _ _________ ___________
THIS IS A MILESTONE DESCRIPTION
The number of milestones = 1
Would you like to add another milestone?
_
[ Y or N, <cr>=N ] : ?
Please enter y or n.
Would you like to add another milestone?
____
[ Y or N, <cr>=N ] : <CR>
3.3.4 Entering Personnel Data
After milestone data, you must enter the personnel data.
This information determines who will be working on the project,
how fast he/she works, and for how long. The person is
identified by his/her two letter initials.
If you would like more information on the type of data
to enter for any of the following questions, type a '?'
Otherwise, enter the data requested.
_
Person's Name : ?
USING TRACKER Page 3-7
Enter the name of the person in 20 characters or less.
Anything longer will be truncated.
______ ______
Person's Name : RONALD REAGAN
__
Person's Initials : RR
_
Production Rate ( <cr> = 1.0) : ?
How many units of work can this person complete per hour ?
Enter a float in the range 0.01..99.99
____
Production Rate ( <cr> = 1.0) : <CR>
_
Hours Per Week ( <cr> = 40) : ?
How many hours per week (1..84) does this person work ?
____
Hours Per Week ( <cr> = 40) : <CR>
What is this person's start date?
_
e.g. 12/6/1985 ( <cr> = null date) : ?
Enter month/day/year where the month is 1..12, the day
is 1..31, and the year is 1901..2099
________
e.g. 12/6/1985 ( <cr> = null date) : 2/1/1985
What is this person's stop date?
_________
e.g. 12/6/1985 ( <cr> = null date) : 2/15/1985
Would you like to add another set of start/stop dates?
_
[y or n, <cr>=n] : Y
What is this person's start date?
_________
e.g. 12/6/1985 ( <cr> = null date) : 2/30/1985
That was not a valid date!
_
Month (1..12) : 3
_
Day (1..31) : 1
____
Year (1901..2099) : 1985
What is this person's stop date?
_________
e.g. 12/6/1985 ( <cr> = null date) : 1/15/1985
That is not a valid stop date. The stop date must be
a later date than the start date. TRY AGAIN!
The start date is 3/ 1/1985
What is this person's stop date?
_________
e.g. 12/6/1985 ( <cr> = null date) : 3/15/1985
USING TRACKER Page 3-8
Would you like to add another set of start/stop dates?
_
[y or n, <cr>=n] : Y
What is this person's start date?
_________
e.g. 12/6/1985 ( <cr> = null date) : 3/20/1985
What is this person's stop date?
________
e.g. 12/6/1985 ( <cr> = null date) : 6/1/1985
The number of people = 1
Would you like to add another person?
____
[ Y or N, <cr>=N ] : <CR>
3.3.5 Entering Subsystem Data
Next, you will be prompted for subsystem data. A subsystem
describes a group of routines that perform a common function.
All of the subsystems together comprise the whole project. Here
is a sample of what you will be asked to enter:
If you would like more information on the type of data
to enter for any of the following questions, type a '?'
Otherwise, enter the data requested.
_
Subsystem Name : ?
Enter the name of the subsystem, which is a
string of up to 10 characters.
______ _________
Subsystem Name : REPORT GENERATOR
What percentage of the total subsystem is available at start?
_
Percent ( <cr> = 0.0) : ?
Enter a number in the range 0.0 .. 100.0
____
Percent ( <cr> = 0.0) : <CR>
Enter the new task numbers directly below the old
task numbers. You may enter blanks for the task
numbers that you want to leave the same, so that
you can change one task number at a time.
DO NOT USE TABS! [ <cr> = no change ]
HIGH
----
REPORT GE 0
USING TRACKER Page 3-9
_
REPORT GE : ?
That was not a valid input. Enter the four digit
task number for each activity.
Enter the new task numbers directly below the old
task numbers. You may enter blanks for the task
numbers that you want to leave the same, so that
you can change one task number at a time.
DO NOT USE TABS! [ <cr> = no change ]
HIGH
----
REPORT GE 0
____
REPORT GE : 3000
The number of subsystems = 1
Would you like to add another subsystem?
____
[ Y or N, <cr>=N ] : <CR>
3.3.6 Entering Element Data
The last type of data you will be asked to enter is the
element data. The element data describes a routine or component
of the project. Each routine is entered as an element, which is
given a description, an abbreviation, and a size. The
description abbreviation must be unique since it identifies each
element. The element is assigned to one milestone and one
subsystem. Each element is required to go through all phases
(activities) of development. Therefore, one person may work on
all phases of the element, or each activity(phase)may be assigned
to a person.
An element also contains the percent complete of each
activity for that element. You are to enter the activity
completeness on a single input line with a single character
representing the percent complete for each activity. A '0' or a
' ' represents 0% complete. A '1' represents 10% complete for
that activity. A '2' means that the activity is 20% complete,
and so on up to '9', which means 90% complete. A 'd' or 'D'
indicates that the activity is 100% complete or done. For
example, if you have five activities, you will enter a string of
five characters representing the percent complete for each
activity. If you press the carriage return or enter a blank, all
the activities will be at 0% complete. The following is a sample
of the information you will be asked:
If you would like more information on the type of data
to enter for any of the following questions, enter a '?'.
Otherwise, enter the data requested.
USING TRACKER Page 3-10
______ _______ ___________
Element description : SECOND ELEMENT DESCRIPTION
_
Unique abbreviation : ?
Enter a unique description key of 6 characters or
less that abbreviates the element description.
The existing elements are :
EL1 ELEMENT DESCRIPTION ONE
___
Unique abbreviation : EL2
_
Subsystem Name : ?
Enter the name of the subsystem, which is a
string of up to 10 characters.
The existing subsystems are :
REPORT GE
______ __
Subsystem Name : REPORT GE
Will more than one person be working on this element?
_
[y or n, <cr>=n] : N
Enter the initials of the person assigned to this element
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
RR RONALD REAGAN
NR NANCY REAGAN
MM MICKEY MOUSE
__
Person's Initials : MM
_
Milestone Number : ?
Enter an integer in the range 1..99
The existing milestones are :
1 THIS IS THE FIRST MILESTONE
USING TRACKER Page 3-11
_
Milestone Number : 1
_
Element Priority ( <cr> = milestone number ) : ?
Enter an integer in the range 1..99
_
Element Priority ( <cr> = milestone number ) : 2
_
Current Size : ?
What do you currently estimate the size of the element to be?
Enter an integer in the range 0 to 99999
____
Current Size : 2000
_
Original size ( <cr> = current size) : ?
What do you estimate the original size of the element to be ?
Enter an integer in the range 0 to 99999
____
Original size ( <cr> = current size) : <CR>
_
Complexity [ <cr> = 1.0 ] : ?
Enter a real number in the range 0.01 to 5.00
____
Complexity [ <cr> = 1.0 ] : <CR>
_
Activity Completeness : ?
For each activity, enter one character
(0 through 9 or ' ', or 'd') indicating that
activity's completeness. Put all the data on
one input line.
For Example:
If you have 5 activities: HLD, DD, CD, UT, and I,
and you enter
Activity Completeness : d86 1
HLD is 100% done. DD is 80% done. CD is 60% done.
UT is 0% done. I is 10% done.
Enter '?' if you would still like more help on how to
enter this data. Otherwise, enter the data as described.
_
Activity Completeness : ?
You will be prompted for the completeness of each activity.
Enter a number from 0 to 9, or ' ', or 'd' to indicate
the percent complete.
'd' or 'D' means it is 100% complete or Done.
USING TRACKER Page 3-12
' ' or '0' means it is 0% complete.
'1' means it is 10% complete.
'2' means it is 20% complete. etc.
_
How complete is activity HIGH LEVEL ? 0
Would you like to add another element?
____
[ Y or N, <cr>=N ] : <CR>
3.4 MANIPULATING THE TRACKER DATA
At this point, whether you answered "Y" or "N" to an
existing TRACKER file, you will be asked the following question:
Would you like to make any changes or modifications
to any of the TRACKER data? (Y or N, <cr>=Y)
If you would like to add, modify, or delete any of the data
that you just entered or that was previously entered, then type
"Y" or press the carriage return. If you just want to print the
TRACKER reports with the data you currently have, then type "N"
and refer to the section titled "Printing Tracker Reports."
3.4.1 Data Menu
If you answered "yes," the following menu will appear:
DATA MENU
=======================================================
Choose the number of one of the following data types
that you would like to manipulate:
1) Global
2) Activity
3) Personnel
4) Milestones
5) Subsystem
6) Element
7) Done With Data - EXIT from Data Menu
This menu allows you to choose the type of data you would
like to operate on. Once you choose a data type, the selected
menu will appear.
USING TRACKER Page 3-13
3.4.1.1 Global Data Operations Menu -
If you choose global data (1) from the data menu, the
following submenu will be displayed:
GLOBAL DATA MENU
=======================================================
Choose the number of one of the following global
variables that you would like to modify:
1) Project Name PROJECT X
2) Project Number 800
3) Project Manager's Name MR. MANAGER
4) Date the TRACKER Run is Valid for 5/ 3/1985
5) Done With Data - EXIT from Global Data Menu
The type of data is displayed along with the current value.
Since the only operation you can perform on global data is
modification, you must choose the number of the variable you
would like to change. After modification of a menu selection,
you will be returned to the global data menu with the new data
displayed next to the corresponding selection.
If you choose "1" from the global data menu, you will be
requested to enter the new project name. For example:
The current project name is PROJECT X
What would you like to change the project name to?
____ _______ ____
Project Name : YOUR PROJECT NAME
If you choose "2", you will be prompted for the new project
number:
The current project number is 800
What would you like to change the project number to?
___
Project Number : 500
If you choose "3", you will be asked to enter the new
project manager's name:
The current manager is MR. MANAGER
Who would you like to be the new manager?
____ _________ ____
Manager Name : YOUR MANAGER'S NAME
USING TRACKER Page 3-14
If you choose "4", you will be prompted for the new date for
the TRACKER run:
The current date is 5/ 3/1985
What would you like to change the date to?
_________
e.g. 12/6/1985 ( <cr> = null date) : 5/10/1985
If you are done with the global data or would like to
manipulate a different data type, choose "5" from the global data
menu, and you will be returned to the data menu.
3.4.1.2 Activity Operations Menu -
To manipulate the activity data, choose selection "2" from
the data menu. The operations you choose to perform will only
effect the activity data. When you are through with the activity
data, or if you want to manipulate a different data type, exit
(5) from the operations menu and the data menu will be displayed
again.
The following will be displayed:
OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Done With Data - EXIT from Operations Menu
3.4.1.2.1 Adding An Activity -
If you choose operations menu selection "1" to add an
activity, you will be prompted for the following data:
If you would like more information on the type of data
to enter for any of the following questions, enter '?'.
Otherwise, enter the data requested.
_
Activity Name : ?
Enter the name of the activity which is a
string of up to 10 characters.
USING TRACKER Page 3-15
The existing activities are :
HIGH LEVEL
______ ______
Activity Name : DETAIL DESIGN
What is this activity's percent of the project?
_
Percent ( <cr> = 0.0) : ?
Enter a number in the range 0.0 .. 100.0
What is this activity's percent of the project?
____
Percent ( <cr> = 0.0) : <CR>
_
Priority : ?
Enter the priority of the activity on a scale of 1 to 10.
_
Priority : 1
_
Consider [ y or n <cr>=y ] : ?
Do you want to consider this activity in the Tracker
calculations?
____
Consider [ y or n <cr>=y ] : <CR>
What percentage is available at start?
____
Percent ( <cr> = 0.0) : <CR>
Enter the new task number (range 0 to 9999).
DO NOT USE TABS! [ <cr> = 0 ]
DETA
----
____
SUBSYSTEM : 2000
The number of activities = 2
The activities' percent of the total project must total 100%
for all the activities.
The activity completeness in all the elements for the new
activity is set to 0%. You will be prompted for a task number
for each subsystem you have defined, since every subsystem has a
task number for each activity.
USING TRACKER Page 3-16
3.4.1.2.2 Deleting An Activity -
If you choose menu selection "2" from the operations menu,
you will be prompted for the name of the activity you wish to
delete. You can only delete an existing activity. TRACKER will
let you know if you try to delete an activity that isn't there.
If you enter an incorrect activity, you will be given the option
to abort the procedure or try again. Otherwise, the activity
will be deleted from the list of activities, the activity
completeness in the element data, and the subsystem task numbers,
so that you don't have to worry about deleting the activity
information from the relevant data. If you only have one
activity remaining, you will not be allowed to delete it because
you must have at least one activity at all times. You will be
asked to enter the following data:
Which activity would you like to delete?
_
Activity Name : ?
Enter the name of the activity which is a
string of up to 10 characters.
The existing activities are :
HIGH LEVEL
DETAIL DES
____ ____
Activity Name : UNIT TEST
Sorry, but activity UNIT TEST does not exist.
You must enter an existing activity.
Press the return key to see the list of existing activities.
Enter 'a' to abort this procedure
Enter any other key to continue.
_
A
3.4.1.2.3 Modifying An Activity -
If you want to modify an activity, choose "3" from the
operations menu. You will be asked which activity to modify and
the activity data menu for that activity will be displayed. A
sample session follows:
Which activity would you like to modify?
_
Activity Name : ?
Enter the name of the activity which is a
string of up to 10 characters.
USING TRACKER Page 3-17
The existing activities are :
DET DESIGN
___ ______
Activity Name : DET DESIGN
3.4.1.2.3.1 Activity Data Menu -
The menu for the requested activity, DET DESIGN, will now be
displayed:
ACTIVITY DATA MENU
==========================================================
Choose the number of one of the following activity fields
that you would like to modify:
1) Activity Name DET DESIGN
2) Percentage of the Total Project 0.0%
3) Priority 2
4) Consider In Calculations TRUE
5) Percent At Start 0.0%
6) Done With Data - EXIT from Activity Data Menu
You may now choose the number of the data that you would
like to modify. The prompts for modifying the data types are the
same as for adding an activity, except that the old value of the
data is displayed, and you only have to enter the values of the
fields that you choose to modify rather than a whole record of
data. A sample modification of the percentage of the total
project follows:
___
The current percentage of the total project is : 0.0
What would you like to change the percentage to?
____
Percent ( <cr> = 0.0) : 90.0
USING TRACKER Page 3-18
ACTIVITY DATA MENU
========================================================
Choose the number of one of the following activity fields
that you would like to modify:
1) Activity Name DET DESIGN
2) Percentage of the Total Project 90.0%
3) Priority 2
4) Consider In Calculations TRUE
5) Percent At Start 0.0%
6) Done With Data - EXIT from Activity Data Menu
When you are done modifying the data for this activity,
choose number "6" from the activity data menu and you will be
returned to the operations menu.
3.4.1.2.4 Displaying An Activity -
If you choose menu selection "4" from the operations menu, a
list of the current data will be displayed on the screen. Press
carriage return to go back to the operations menu.
If you want to see the fields for a particular activity
record, choose modify from the operations menu. You will be
asked which activity to modify. When the menu is displayed, the
values of each field of the record will be displayed next to the
menu selections.
3.4.1.3 Milestone Operations Menu -
To manipulate the milestone data, choose selection "4" from
the data menu. The operations you choose to perform will only
effect the milestone data. When you are through with the
milestone data, or if you want to manipulate a different data
type, exit (5) from the operations menu and the data menu will be
displayed again.
The following operations menu will be displayed:
USING TRACKER Page 3-19
OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Done With Data - EXIT from Operations Menu
3.4.1.3.1 Adding A Milestone -
If you choose operations menu selection "1" to add a
milestone, you will be prompted for the following data:
If you would like more information on the type of data
to enter for any of the following questions, press the
return key. Otherwise, enter the data requested.
_
Milestone Number : ?
Enter an integer in the range 1..99
The existing milestones are :
1 SOME LONG MILESTONE NUMBER 1 IS HERE
2 This is the second longest description
99 This should be the last milestone
_
Milestone Number : 3
Milestone Completion Number
_
( <cr> = milestone number ) : ?
Enter an integer in the range 1..99
____
Milestone Completion Number ( <cr> = milestone number ) : <CR>
What is the due date?
____
e.g. 12/6/1985 ( <cr> = null date) : <CR>
Milestone description :
MILESTONE THREE
The number of milestones = 4
USING TRACKER Page 3-20
3.4.1.3.2 Deleting A Milestone -
If you choose menu selection "2" from the operations menu,
you will be prompted for the number of the milestone you wish to
delete. You can only delete an existing milestone. TRACKER will
let you know if you try to delete an milestone that isn't there.
If you enter an incorrect milestone, you will be given the option
to abort the procedure or try again. Otherwise, the milestone
will be deleted from the milestone list. If you only have one
milestone remaining, you will not be allowed to delete it because
you must have at least one milestone at all times.
If an element has been assigned to that milestone, you will
be asked which milestone will replace the old one. You must
enter an existing milestone. This feature prevents you from
having to modify each element that was assigned to the deleted
milestone. You will be asked to enter the following data:
Which milestone would you like to delete?
[ give milestone number]
_
Milestone Number : ?
Enter an integer in the range 1..99
The existing milestones are :
1 SOME LONG MILESTONE NUMBER 1 IS HERE
2 This is the second longest description
99 This should be the last milestone
3 MILESTONE THREE
_
Milestone Number : 3
Number of milestones = 3
3.4.1.3.3 Modifying A Milestone -
If you want to modify a milestone, choose "3" from the
operations menu. You will be asked which milestone to modify,
and the milestone data menu for that milestone will be displayed.
A sample session follows:
What is the number of the milestone you would like to modify?
_
Milestone Number : 1
USING TRACKER Page 3-21
3.4.1.3.3.1 Milestone Data Menu -
The menu for milestone 1, will now be displayed:
MILESTONE DATA MENU
==========================================================
Choose the number of one of the following milestone fields
that you would like to modify:
1) Milestone Number 1
2) Completion Number 1
3) Due Date null date
4) Description SOME LONG MILESTONE NUMBER 1 IS HERE
5) Done With Data - EXIT from Milestone Data Menu
You may now choose the number of the data that you would
like to modify. If you modify the milestone number, it will be
changed in all related data. This service is provided so that
you don't have to worry about an old milestone number being found
in the element data. The prompts for modifying the data types
are the same as for adding a milestone, except that the old value
of the data is displayed, and you only have to enter the values
of the fields that you choose to modify rather than a whole
record of data. A sample modification of the due date follows:
The current due date is a null date.
What would you like to change it to?
________
e.g. 12/6/1985 ( <cr> = null date) : 4/1/1985
The new date will be shown when the menu is displayed again.
MILESTONE DATA MENU
==========================================================
Choose the number of one of the following milestone fields
that you would like to modify:
1) Milestone Number 1
2) Completion Number 1
3) Due Date 4/ 1/1985
4) Description SOME LONG MILESTONE NUMBER 1
5) Done With Data - EXIT from Milestone Data Menu
When you are done modifying the data for this milestone,
choose number "5" from the milestone data menu and you will be
returned to the operations menu.
USING TRACKER Page 3-22
3.4.1.3.4 Displaying A Milestone -
If you choose menu selection "4" from the operations menu, a
list of the current data will be displayed on the screen. Press
carriage return to go back to the operations menu.
If you want to see the fields for a particular milestone
record, choose modify from the operations menu. You will be
asked which milestone to modify. When the menu is displayed, the
values of each field of the record will be displayed next to the
menu selections.
3.4.1.4 Personnel Operations Menu -
To manipulate the personnel data, choose selection "3" from
the data menu. The operations you choose to perform will only
effect the personnel data. When you are through with the
personnel data, or if you want to manipulate a different data
type, exit (5) from the operations menu and the data menu will be
displayed again.
The operations menu looks like this:
OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Done With Data - EXIT from Operations Menu
3.4.1.4.1 Adding A Person -
If you choose operations menu selection 1 to add a person,
you will be prompted for the following data:
___ ____
Person's Name : JOE COOL
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
USING TRACKER Page 3-23
RR RONALD REAGAN
NR NANCY REAGAN
MM MICKEY MOUSE
__
Person's Initials : JC
_
Production Rate ( <cr> = 1.0) : ?
How many units of work can this person complete per hour ?
Enter a float in the range 0.01..99.99
The default is 1.0. Press <cr> for the default value.
____
Production Rate ( <cr> = 1.0) : <CR>
_
Hours Per Week ( <cr> = 40) : ?
How many hours per week (1..84) does this person work ?
The default is 40 hours. Press <cr> for the default.
____
Hours Per Week ( <cr> = 40) : <CR>
What is this person's start date?
_
e.g. 12/6/1985 ( <cr> = null date) : ?
Enter month/day/year where the month is 1..12, the day
is 1..31, and the year is 1901..2099
________
e.g. 12/6/1985 ( <cr> = null date) : 3/5/1985
What is this person's stop date?
________
e.g. 12/6/1985 ( <cr> = null date) : 2/5/1985
That is not a valid stop date. The stop date must be
a later date than the start date. TRY AGAIN!
The start date is 3/ 5/1985
What is this person's stop date?
________
e.g. 12/6/1985 ( <cr> = null date) : 5/1/1985
Would you like to add another set of start/stop dates?
_
[y or n, <cr>=n] : N
The number of people = 4
3.4.1.4.2 Deleting A Person -
If you choose menu selection "2" from the operations menu,
you will be prompted for the initials of the person you wish to
delete. You can only delete an existing person. TRACKER will
let you know if you try to delete an person that isn't there. If
you enter an incorrect person, you will be given the option to
USING TRACKER Page 3-24
abort the procedure or try again. Otherwise, the person will be
deleted from the personnel list. If you only have one person
remaining, you will not be allowed to delete because you must
have at least one person at all times.
If that person has been assigned to an element or to a phase
of an element, you will be asked which existing person should be
assigned to work on that element when the old person is deleted.
At this point, you cannot abort the procedure, but you must enter
an existing person to take the old person's place. This feature
prevents you from having to modify each element assigned to that
person. You will be asked to enter the following data:
Which person would you like to delete?
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
BB BONNIE BURKHARDT
ML MAY LEE
JC JOE COOL
FF Freddy Flinstone
MS MILO SILO
__
Person's Initials : JC
When person JC is deleted,
who would you like to use in his place in the element data?
__
Person's Initials : JJ
Sorry, but no one with those initials exists.
You must enter an existing person.
Press the return key to see the list of defined people
and their initials.
Enter 'a' to abort this procedure.
Enter any other key to continue.
_
A
You cannot abort the procedure at this time.
You must enter valid initials.
__
Person's Initials : FF
Number of people = 4
USING TRACKER Page 3-25
3.4.1.4.3 Modifying A Person -
If you want to modify a person, choose "3" from the
operations menu. You will be asked which person to modify and
the personnel record data menu for that person will be displayed.
A sample session follows:
Which person would you like to modify?
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
RR RONALD REAGAN
NR NANCY REAGAN
MM MICKEY MOUSE
__
Person's Initials : RR
3.4.1.4.3.1 Personnel Data Menu -
The menu for the requested person, RR, will now be
displayed:
PERSONNEL DATA MENU
==========================================================
Choose the number of one of the following personnel fields
that you would like to modify:
1) Person's Name RONALD REAGAN
2) Person's Initials RR
3) Production Rate 1.000
4) Hours Per Week 40
5) First Start/Stop Date null date null date
6) Second Start/Stop Date null date null date
7) Third Start/Stop Date null date null date
8) Done With Data - EXIT from Personnel Data Menu
You may now choose the number of the data that you would
like to modify. If you modify the person's initials, the change
will be reflected in the element data. This service is provided
so that you don't have to worry about old initials being found in
the element data. The prompts for modifying the data types are
the same as for adding a person, except that the old value of the
data is displayed. You only have to enter the values of the
fields that you choose to modify rather than a whole record of
USING TRACKER Page 3-26
data. For example, if you chose to modify the first start/stop
dates (5), you would see the following:
The current start date for this set of dates is a null date.
What would you like to change it to?
_
e.g. 12/6/1985 ( <cr> = null date) : ?
Enter month/day/year where the month is 1..12, the day
is 1..31, and the year is 1901..2099
________
e.g. 12/6/1985 ( <cr> = null date) : 4/1/1985
The current stop date for the second set of dates is a
null date.
What would you like to change it to?
________
e.g. 12/6/1985 ( <cr> = null date) : 5/5/1985
PERSONNEL DATA MENU
==========================================================
Choose the number of one of the following personnel fields
that you would like to modify:
1) Person's Name RONALD REAGAN
2) Person's Initials RR
3) Production Rate 1.000
4) Hours Per Week 40
5) First Start/Stop Date 4/ 1/1985 5/ 5/1985
6) Second Start/Stop Date null date null date
7) Third Start/Stop Date null date null date
8) Done With Data - EXIT from Personnel Data Menu
When you are finished modifying the data for this person,
choose number "8" from the personnel data menu and you will be
returned to the operations menu.
3.4.1.4.4 Displaying A Person -
If you choose menu selection "4" from the operations menu, a
list of the current data will be displayed on the screen. Press
carriage return to go back to the operations menu.
If you want to see the fields for a particular person's
record, choose modify from the operations menu. You will be
asked which person to modify. When the menu is displayed, the
values of each field of the record will be displayed next to the
menu selections.
USING TRACKER Page 3-27
3.4.1.5 Subsystem Operations Menu -
To manipulate the subsystem data, choose selection "5" from
the data menu. The operations you choose to perform will only
effect the subsystem data. When you are through with the
subsystem data, or if you want to manipulate a different data
type, exit (5) from the operations menu and the data menu will be
displayed again.
You will see the following menu displayed:
OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Done With Data - EXIT from Operations Menu
3.4.1.5.1 Adding A Subsystem -
If you choose operations menu selection "1" to add a
subsystem, you will be prompted for the following data:
If you would like more information on the type of data
to enter for any of the following questions, press the
return key. Otherwise, enter the data requested.
Subsystem Name : ?
Enter the name of the subsystem, which is a
string of up to 10 characters.
The existing subsystems are :
SUB1
SUB2
SUB3
Subsystem Name : SUB4
What percentage of the total subsystem is available at start?
Percent ( <cr> = 0.0) :
USING TRACKER Page 3-28
Enter the new task numbers directly below the old task
numbers. You may enter blanks for the task numbers
that you want to leave the same, so that you can change
one task number at a time.
DO NOT USE TABS! [ <cr> = no change ]
HI D DET CODE UNIT INTE
---- ---- ---- ---- ----
SUB4 0 0 0 0 0
____
SUB4 : <CR>
The number of subsystems = 4
3.4.1.5.2 Deleting A Subsystem -
If you choose menu selection "2" from the operations menu,
you will be prompted for the name of the subsystem you wish to
delete. You can only delete an existing subsystem. TRACKER will
let you know if you try to delete a subsystem that isn't there.
If you enter an incorrect subsystem, you will be given the option
to abort the procedure or try again. Otherwise, the subsystem
will be deleted from the subsystem list. If you only have one
subsystem remaining, you will not be allowed to delete it because
you must have at least one subsystem at all times.
If that subsystem has been assigned to an element, you will
be asked which subsystem you want to replace the old subsystem.
You must enter an existing subsystem. At this point, you cannot
abort the procedure, but you must enter an existing subsystem to
take the old subsystem's place. This feature prevents you from
having to modify each element that had that subsystem assigned to
it. You will be asked to enter the following data:
Which subsystem would you like to delete?
____
Subsystem Name : SUB4
Number of subsystems = 3
3.4.1.5.3 Modifying A Subsystem -
If you want to modify a subsystem choose "3" from the
operations menu. You will be asked which subsystem to modify and
the data menu for that subsystem will be displayed. A sample
session follows:
Which subsystem would you like to modify?
_
Subsystem Name : ?
Enter the name of the subsystem, which is a
string of up to 10 characters.
USING TRACKER Page 3-29
The existing subsystems are :
SUB1
SUB2
SUB3
____
Subsystem Name : SUB2
3.4.1.5.3.1 Subsystem Data Menu -
The menu for the requested subsystem, SUB2, will now be
displayed:
SUBSYSTEM DATA MENU
==========================================================
Choose the number of one of the following subsystem fields
that you would like to modify:
1) Subsystem Name SUB2
2) Task Numbers
3) Percent At Start 0.0%
4) Done With Data - EXIT from Subsystem Data Menu
You may now choose the number of the data that you would
like to modify. If you modify the subsystem name, the change
will be reflected in the element data. This service is provided
so that you don't have to worry about an old subsystem name being
found in the element data. The prompts for modifying the data
types are the same as for adding a subsystem, except that the old
value of the data is displayed, and you only have to enter the
values of the fields that you choose to modify rather than a
whole record of data. A sample modification of the task numbers
follows:
Enter the new task numbers directly below the old task
numbers. You may enter blanks for the task numbers
that you want to leave the same, so that you can change
one task number at a time.
DO NOT USE TABS! [ <cr> = no change ]
HI D DET CODE UNIT INTE
---- ---- ---- ---- ----
SUB2 1 2 3 4 5
____ ____ ____ ____ ____
SUB2 : 1000 2000 3000 4000 5000
USING TRACKER Page 3-30
SUBSYSTEM DATA MENU
==========================================================
Choose the number of one of the following subsystem fields
that you would like to modify:
1) Subsystem Name SUB2
2) Task Numbers
3) Percent At Start 0.0%
4) Done With Data - EXIT from Subsystem Data Menu
_
2
Enter the new task numbers directly below the old task
numbers. You may enter blanks for the task numbers
that you want to leave the same, so that you can change
one task number at a time.
DO NOT USE TABS! [ <cr> = no change ]
HI D DET CODE UNIT INTE
---- ---- ---- ---- ----
SUB2 1000 2000 3000 4000 5000
____
SUB2 : <CR>
When you are done modifying the data for this subsystem,
choose number "4" from the subsystem data menu and you will be
returned to the operations menu.
3.4.1.5.4 Displaying A Subsystem -
If you choose menu selection "4" from the operations menu, a
list of the current data will be displayed on the screen. Press
carriage return to go back to the operations menu.
If you want to see the fields for a particular subsystem
record, choose modify from the operations menu. You will be
asked which subsystem to modify. When the menu is displayed, the
values of each field of the record will be displayed next to the
menu selections.
3.4.1.6 Element Data Operations Menu -
To manipulate the element data, choose selection "6" from
the data menu. The operations you choose to perform will only
effect the element data. When you are through with the element
data, or if you want to manipulate a different data type, exit
(7) from the operations menu and the data menu will be displayed
USING TRACKER Page 3-31
again.
The element data operations menu will be displayed:
ELEMENT DATA OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Quick Update of the Current Size
6) Quick Update of the Activity Percent Complete
7) Done With Data - EXIT from Operations Menu
3.4.1.6.1 Adding An Element -
If you choose operations menu selection "1" to add an
element, you will be prompted for the following data:
If you would like more information on the type of data
to enter for any of the following questions, enter a '?'.
Otherwise, enter the data requested.
_
Element description : ?
What is the description of the element in 35 characters
or less?
_______ ______
Element description : ANOTHER ELEMNT
_
Unique abbreviation : ?
Enter a unique description key of 6 characters or
less that abbreviates the element description.
The existing elements are :
EL1 ELEMENT 1
EL2 THE SECOND ELEMENT
EL4 ELEMENT FOUR
EL5 ELEMENT FIVE
EL9 ELEMENT 9
EL10 ELEMENT TEN
EL3 ELEMENT THREE
____
Unique abbreviation : EL14
USING TRACKER Page 3-32
_
Subsystem Name : ?
Enter the name of the subsystem, which is a
string of up to 10 characters.
The existing subsystems are :
SUB1
SUB2
SUB3
____
Subsystem Name : SUB2
Will more than one person be working on this element?
_
[y or n, <cr>=n] : Y
Enter the initials of the person assigned to each activity
of this element...
Who is assigned to HI DESIGN ?
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
BB BONNIE BURKHARDT
ML MAY LEE
FF Freddy Flinstone
MS MILO SILO
__
Person's Initials : FF
Who is assigned to DET DESIGN?
__
Person's Initials : MM
Who is assigned to CODE ?
__
Person's Initials : MS
Who is assigned to UNIT TEST ?
__
Person's Initials : BB
Who is assigned to INTEGRATE ?
__
Person's Initials : ML
_
Milestone Number : ?
Enter an integer in the range 1..99
The existing milestones are :
USING TRACKER Page 3-33
1 SOME LONG MILESTONE NUMBER 1 IS HERE
2 This is the second longest description
99 This should be the last milestone
_
Milestone Number : 2
_
Element Priority ( <cr> = milestone number ) : ?
Enter an integer in the range 1..99
____
Element Priority ( <cr> = milestone number ) : <CR>
_
Current Size : ?
What do you currently estimate the size of the element to be?
Enter an integer in the range 0 to 99999
____
Current Size : 3000
____
Original size ( <cr> = current size) : <CR>
_
Complexity [ <cr> = 1.0 ] : ?
Enter a real number in the range 0.01 to 5.00
____
Complexity [ <cr> = 1.0 ] : <CR>
_
Activity Completeness : ?
For each activity, enter one character
(0 through 9 or ' ', or 'd') indicating that
activity's completeness. Put all the data on
one input line.
For Example:
If you have 5 activities: HLD, DD, CD, UT, and I,
and you enter
Activity Completeness : d86 1
HLD is 100% done. DD is 80% done. CD is 60% done.
UT is 0% done. I is 10% done.
Enter '?' if you would still like more help on how to
enter this data. Otherwise, enter the data as described.
_
Activity Completeness : ?
You will be prompted for the completeness of each activity.
Enter a number from 0 to 9, or ' ', or 'd'
to indicate the percent complete.
'd' or 'D' means it is 100% complete or Done.
' ' or '0' means it is 0% complete.
USING TRACKER Page 3-34
'1' means it is 10% complete.
'2' means it is 20% complete. etc.
_
How complete is activity HI DESIGN : 9
_
How complete is activity DET DESIGN : ?
That was not a valid value. TRY AGAIN!
Enter a number from 0 to 9, or ' ', or 'd'
to indicate the percent complete.
'd' or 'D' means it is 100% complete or Done.
' ' or '0' means it is 0% complete.
'1' means it is 10% complete.
'2' means it is 20% complete. etc.
_
How complete is activity DET DESIGN : 8
_
How complete is activity CODE : 7
_
How complete is activity UNIT TEST : 7
_
How complete is activity INTEGRATE : 0
3.4.1.6.2 Deleting An Element -
If you choose menu selection "2" from the operations menu,
you will be prompted for the abbreviation of the element you wish
to delete. You can only delete an existing element. TRACKER
will let you know if you try to delete an element that isn't
there. If you enter an incorrect element, you will be given the
option to abort the procedure or try again. If you only have one
element remaining, you will not be allowed to delete it because
you must have at least one element at all times. You will be
asked to enter the following data:
Which element would you like to delete?
_
Description Abbreviation : ?
Enter a unique description key of 6 characters or
less that abbreviates an existing element description.
The existing elements are :
EL1 ELEMENT 1
EL2 THE SECOND ELEMENT
EL4 ELEMENT FOUR
EL5 ELEMENT FIVE
EL6 ELEMENT SIX
EL8 ELEMENT 8
EL9 ELEMENT 9
EL10 ELEMENT TEN
USING TRACKER Page 3-35
EL11 ELEMENT ELEVEN
EL12 EL12
EL3 ELEMENT THREE
EL13 THIS IS A NEW ELEMENT
EL14 ANOTHER ELEMNT
____
Description Abbreviation : EL13
Number of elements = 13
3.4.1.6.3 Modifying An Element -
If you want to modify an element, choose "3" from the
operations menu. You will be asked which element to modify and
the element data menu for that element will be displayed. A
sample session follows:
Which element would you like to modify?
___
Description Abbreviation : EL1
3.4.1.6.3.1 Element Data Menu -
The menu for element, EL1, will now be displayed:
ELEMENT DATA MENU
==========================================================
Choose the number of one of the following element fields
that you would like to modify:
1) Element Description ELEMENT 1
2) Description Abbreviation EL1
3) Subsystem Name SUB1
4) Person's Initials ML
5) Milestone Number 1
6) Element Priority 1
7) Current Size 100
8) Complexity 1.50
9) Activity Completeness '1234 '
10) More than one person assigned FALSE
11) Done With Data - EXIT from Element Data Menu
You may now choose the number of the data that you would
like to modify. The prompts for modifying the data types are the
same as for adding an element, except that the old value of the
data is displayed, and you only have to enter the values of the
USING TRACKER Page 3-36
fields that you choose to modify rather than a whole record of
data. A sample modification of multiple people, selection "10",
follows:
The element can now be assigned to several people.
Who is assigned to HI DESIGN ?
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
BB BONNIE BURKHARDT
ML MAY LEE
FF Freddy Flinstone
MS MILO SILO
__
Person's Initials : ML
Who is assigned to DET DESIGN?
__
Person's Initials : FF
Who is assigned to CODE ?
__
Person's Initials : BB
Who is assigned to UNIT TEST ?
__
Person's Initials : MS
Who is assigned to INTEGRATE ?
__
Person's Initials : MS
ELEMENT DATA MENU
==========================================================
Choose the number of one of the following element fields
that you would like to modify:
1) Element Description ELEMENT 1
2) Description Abbreviation EL1
3) Subsystem Name SUB1
4) People's Initials ML,FF,BB,MS,MS
5) Milestone Number 1
6) Element Priority 1
7) Current Size 100
8) Complexity 1.50
9) Activity Completeness '1234 '
10) More than one person assigned TRUE
11) Done With Data - EXIT from Element Data Menu
USING TRACKER Page 3-37
When you are finished modifying the data for this element,
choose number "11" from the element data menu and you will be
returned to the operations menu.
3.4.1.6.4 Displaying An Element -
If you choose menu selection "4" from the operations menu, a
list of the current data will be displayed on the screen. Press
carriage return to go back to the operations menu.
If you want to see the fields for a particular element
record, choose modify from the operations menu. You will be
asked which element to modify. When the menu is displayed, the
values of each field of the record will be displayed next to the
menu selections.
3.4.1.6.5 Quick Update Of The Current Size -
If you choose "5" from the element data operations menu, you
will be allowed to update the current size of a group of
elements. The following submenu containing these groups will be
displayed:
3.4.1.6.5.1 Element Data Groups Menu -
ELEMENT DATA GROUPS MENU
=======================================================
Choose the number of one of the following groups of
element data that you would like do a quick update on :
1) All Elements
2) Elements belonging to a Milestone
3) Elements belonging to a Person
4) Elements belonging to a Subsystem
5) Done With Data - EXIT from Operations Menu
Choose the number of the group of elements you would like to
change. The current size of the elements belonging to that group
will be displayed, and you will be prompted for the new value.
Press carriage return if you would like to keep the current
value. This feature allows you to do your weekly updates more
efficiently. Choose "5" when you are finished updating the
current size and you will be returned to the element data
operations menu. A sample quick update of the current size for
elements belonging to a person follows:
USING TRACKER Page 3-38
_
Person's Initials : ?
Enter a string of up to 2 characters that represents
the initials of the person.
The existing people are :
ML MAY LEE
BB BONNIE BURKHARDT
__
Person's Initials : ML
For LISTPK -- LIST PACKAGE [ <cr> = no change ]
Old current size = 123
___
New current size : 130
For DATAPK -- DATA PACKAGE [ <cr> = no change ]
Old current size = 130
___
New current size : 150
For VT100 -- VT100 AND MENUS [ <cr> = no change ]
Old current size = 503
___
New current size : 550
For PROMPT -- PROMPTS [ <cr> = no change ]
Old current size = 1205
____
New current size : 1250
For INITTR -- INITIALIZE TRACKER [ <cr> = no change ]
Old current size = 14
__
New current size : 25
For SETUP -- SET UP TRACKER [ <cr> = no change ]
Old current size = 34
__
New current size : 40
For MANDAT -- MANIPULATE DATA [ <cr> = no change ]
Old current size = 35
__
New current size : 50
3.4.1.6.6 Quick Update Of The Activity Percent Complete -
If you choose "6" from the element data operations menu, you
will be allowed to update the activity percent complete of each
element by data groups. The following submenu containing these
groups will be displayed:
USING TRACKER Page 3-39
3.4.1.6.6.1 Element Data Groups Menu -
ELEMENT DATA GROUPS MENU
=======================================================
Choose the number of one of the following groups of
element data that you would like do a quick update on :
1) All Elements
2) Elements belonging to a Milestone
3) Elements belonging to a Person
4) Elements belonging to a Subsystem
5) Done With Data - EXIT from Operations Menu
Choose the number of the data group you would like to
change. The activity percent complete of the elements belonging
to that group will be displayed, and you will be prompted for the
new value. Press carriage return if you would like to keep the
current value. This feature allows you to do your weekly updates
more efficiently. Choose "5" when you are done updating the
percent complete and you will be returned to the element data
operations menu. A sample quick update of the percent complete
for elements belonging to a milestone follows:
____
Milestone Number : <CR>
Enter an integer in the range 1..99
The existing milestones are :
1 GENERIC PACKAGES, TRACKER DRIVERS FINISHED
2 MENUS, MENU DRIVER, READ/WRITE TO FILE
3 PROMPTING AND REPORT GENERATION WORKS
_
Milestone Number : 3
For FIXDAT -- GROUP DATA FIXES
[ <cr> = no change ]
Old percent complete = DDD65
_____
New percent complete : ddd75
For RESET -- RESET ENTIRE DATA
[ <cr> = no change ]
Old percent complete = DD74
___
New percent complete : dd8
For RESET -- RESET ENTIRE DATA
[ <cr> = no change ]
Old percent complete = DD74
___ _
New percent complete : dd8 1
For ORIGFX -- UPDATE ORIGINAL TO CURRENT SIZE
[ <cr> = no change ]
USING TRACKER Page 3-40
Old percent complete = DDDDD
____
New percent complete : <CR>
For GLOBAL -- GLOBAL DATA PKG
[ <cr> = no change ]
Old percent complete = DDD95
_____
New percent complete : dddd6
For MS -- MILESTONE PKG
[ <cr> = no change ]
Old percent complete = DD973
_____
New percent complete : dd855
For RDATDN -- REPORT DATE DONE BY MS
[ <cr> = no change ]
Old percent complete = DD74
____
New percent complete : <CR>
3.4.1.7 Exiting The Data Menu -
To exit the data menu, choose number "7". The activities'
percent of the total project will be checked to make sure they
add up to 100%. If it does not, you must go back and modify the
activity data so that they add up to exactly 100%. Since the
activities define the different phases of the project, 100% of
the project must be accounted for by these activities. If the
total does not equal 100%, you can add, delete or modify the
activity data until the total percent complete equals 100%. The
following example shows how you could adjust the total percent of
the project by adding another activity.
The total of each activity's percent of the total project
does not add up to 100.0%.
You must go back and change the activity data.
HI LEVEL D 15.0%
DETAIL DES 20.0%
CODE 25.0%
UNIT TEST 20.0%
-------
Total percent = 80.0
Press <cr> to return to the Data Menu.
____
<CR>
USING TRACKER Page 3-41
DATA MENU
=======================================================
Choose the number of one of the following data types
that you would like to manipulate:
1) Global
2) Activity
3) Personnel
4) Milestones
5) Subsystem
6) Element
7) Done With Data - EXIT from Data Menu
_
2
OPERATIONS MENU
=======================================================
Choose the number of one of the following operations
that you would like to perform:
1) Add
2) Delete
3) Modify
4) Display the Current Data
5) Done With Data - EXIT from Operations Menu
_
1
If you would like more information on the type of data
to enter for any of the following questions, enter '?'.
Otherwise, enter the data requested.
_________
Activity Name : INTEGRATE
What is this activity's percent of the project?
__
Percent ( <cr> = 0.0) : 20
Enter a number in the range 0.0 .. 100.0
____
Percent ( <cr> = 0.0) : 20.0
____
Priority : <CR>
Enter the priority of the activity on a scale of 1 to 10.
_
Priority : 1
____
Consider [ y or n <cr>=y ] : <CR>
What percentage is available at start?
____
Percent ( <cr> = 0.0) : <CR>
USING TRACKER Page 3-42
Enter the new task number (range 0 to 9999).
DO NOT USE TABS! [ <cr> = 0 ]
INTE
----
____
TRACKER : 1000
INTE
----
_
INPREP : ?
Enter the new task number (range 0 to 9999).
DO NOT USE TABS! [ <cr> = 0 ]
INTE
----
____
INPREP : 4000
The number of activities = 5
Once the activity percent of the project equals 100%, you
will be asked the following questions:
Would you like to update the original size estimates for all
the elements to reflect the current size estimate?
_
Y or N ( <cr>=N ) : ?
Tracker will step through each element and assign the
original size to equal the current size.
Would you like to update the original size?
____
[ Y or N <cr>=N ] : <CR>
Do you want to start tracking the project from this point
onwards and use the current percent complete as the
starting point?
_
[ Y or N <cr>=N ] : ?
Tracker will step through each element and compute the
amount of work that is completed on the element. It then
subtracts this amount from the current size to obtain the
EQUIVALENT NEW SIZE estimate. The percent complete for
that element is erased and set to ' '.
Do you want to start tracking the project from this point?
____
[ Y or N <cr>=N ] : <CR>
Writing the data to file....
\f
CHAPTER 4
NOTES ON THE TRACKER CALCULATIONS
4.1 CALCULATIONS USED IN TRACKER
4.1.1 Sorting The Elements
First, the milestones are sorted by the completion number.
Elements belonging to a milestone of a lower completion number
are completed first. Within each milestone, the elements are
sorted by priority number. Elements of priority '1' are
completed before elements of priority '2', etc. If elements
belonging to one milestone have the same priority, they are
completed in the order they were entered into the data file.
4.1.2 Man-Hours Remaining
The calculation of Man-Hours Remaining and the Completion
Dates is based upon those activities considered in the
calculations. An activity is also considered in the calculations
if its priority is less than or equal to any activity that is
considered. This is to prevent the user from skipping a phase of
completion and receiving incorrect data from the reports. For
example, if you wanted to track only Detailed Design, priority =
2, the High Level Design, priority = 1, would also be considered
in the calculations since you can't start Detailed Design until
High Level Design is completed.
The time required for each activity on an element is
calculated as follows:
ELEMENT_SIZE := ELEMENT.current_size - ELEMENT.size_done_at_start;
TIME_FOR_1_ACTIVITY := ELEMENT.complexity * ELEMENT_SIZE
* (PERCENT_OF_TOTAL_PROJECT(this_activity) / 100.0)
* ((100.0 - ELEMENT.percent_complete(this_activity)/100.0)
/ ASSIGNED_PERSONS.production_rate;
The total time remaining on an element is a sum of the time
required for each activity used in the calculations.
NOTES ON THE TRACKER CALCULATIONS Page 4-2
4.1.3 Completion Dates
The activities are completed in increasing order of
priority. This means a person working on a given element, A,
must complete all the activities of priority '1' before moving on
to the next element, B, and working on its activities of priority
'1'. After a person has completed the activities of priority
'1', he starts back at the first element and works on the
activities of priority '2', etc.
For each person, TRACKER walks through his element list and
keeps a running total of the total time needed to complete all
the activities with priority '1', then '2', etc., until the
activity with the highest considered priority is about to be
calculated. On this last pass through his element list, a
completion date is calculated for each element. The amount of
time needed to complete element A's activities of HIGHEST
CONSIDERED PRIORITY is added to the total amount of time
remaining for this person. This grand total time remaining is
then added to the current date to obtain a completion date for
the element. This process is then repeated for every other
element assigned to this person.
A null start date signifies that the person can start work
immediately. A null stop date signifies that the person will
finish working when all his work is completed. 3.p If a person's
start date is later than the current date, his start date is used
to predict a completion date instead of the current date.
TRACKER skips over any time between a stop date and the next
start date. If a person's final stop date comes before the
projected completion date, this implies that the person doesn't
have enough time to finish the element. On the reports, this
underflow-date is shown by the completion date equalling
"99/99/99".
An average number of vacation days and holidays are already
included in the calculations. This number of days off is spread
evenly throughout the year. The default number of days off is
equal to 10, but consult your system manager to see if this
default was changed when TRACKER was installed.
4.1.4 Percent Complete
There are three types of percent complete values that are
calculated, Percent Complete at Start, Percent Complete on the
Contract, and Percent Complete on the Entire Project. The
calculations are as follows:
ELEMENT_SIZE -- size of the element
START -- amount of work done on the element at the start of the
-- contract (if it was bid at 40% complete for 10000 SLOCs,
-- 4000 SLOCs would be completed at start)
EQ_SIZE := ELEMENT_SIZE - START;
NOTES ON THE TRACKER CALCULATIONS Page 4-3
-- the size of an new element requiring the equivalent
-- amount of work, otherwise described as the amount
-- of work left to do at start of the contract
DONE -- amount of work done since the start of the contract
EQ_SIZE_FOR_1_ACTIVITY := ELEMENT.complexity
* (ELEMENT_SIZE - ELEMENT.size_done_at_start)
* ACTIVITY_PERCENT_OF_PROJECT;
START_FOR_1_ACTIVITY := ELEMENT.complexity
* ELEMENT.size_done_at_start * ACTIVITY_PERCENT_OF_PROJECT;
DONE_FOR_1_ACTIVITY := SIZE_FOR_1_ACTIVITY
* PERCENT_DONE_ON_ACTIVITY;
EQ_SIZE := sum_for_all_activities (EQ_SIZE_FOR_1_ACTIVITY);
START := sum_for_all_activities (START_FOR_1_ACTIVITY);
DONE := sum_for_all_activities (DONE_FOR_1_ACTIVITY);
PCT_DONE.CONTRACT := 100.0 * DONE / EQ_SIZE;
PCT_DONE.START := 100.0 * START / (START + EQ_SIZE);
PCT_DONE.ENTIRE := 100.0 * (DONE + START) / (EQ_SIZE + START);
When calculating the percent complete based on the original
size estimate, the element's size and the amount of work done at
start used in the calculations may have to be adjusted. If the
original size estimate is less than or equal to the current size,
no change is made. The size is equal to the original estimate
and the size done at start equals the ELEMENT.size_done_at_start.
If the original size is greater than the current size, the size
done at start must be adjusted so the ratio of work done at start
to the total amount of work is the same. The adjustment is as
follows:
size done at start = ELEMENT.size_done_at_start *
(current_size / original_size);
This value for element size and size done at start are then used
to calculate the percent complete.
4.1.5 Reset The Data
If the user chooses to RESET the data, two calculations are
performed. First, the percent complete on the contract is
calculated by subsystem and activity. The calculations are
described in the previous section. These values are then used to
update the PERCENT AVAILABLE AT START field in both the activity
and subsystem data.
NOTES ON THE TRACKER CALCULATIONS Page 4-4
Second, each element is examined and a new value for the
size_done_at_start field is calculated. The values for PERCENT
COMPLETE BY ACTIVITY are then erased and set equal to zero.
Using the notation of the previous section, the calculation is as
follows:
new_size_done_at_start := old_size_done_at_start + DONE;
\f
CHAPTER 5
TRACKER REPORTS
5.1 PRINTING TRACKER REPORTS
You will be asked the following question before you are
allowed to print reports:
Do you want to update the previous date of completion with
the newly computed date of completion?
_
[Y or N, <cr>=Y] : ?
When the data is written to the file for the next run of
TRACKER, which set of element completion dates would you
like stored in the 'Previous Completion Date' column, the
previous completion date used in this run or the newly
computed completion date?
Do you want to update the previous date of completion with
the newly computed date of completion?
____
[Y or N, <cr>=Y] : <CR>
Now you are ready to generate TRACKER reports.
5.1.1 Report Menu
The report menu containing all the reports you are allowed
to generate will be displayed on the screen. Once you choose a
report to be printed, the output is put into the tracker ".rpt"
file. This file is the same name as the input file with a ".rpt"
extension. A star will appear next to the menu selection to
indicate that you have already generated that report. If you
choose a starred report, a duplicate copy of that report will be
generated and added to the output file. The reports are created
in the order in which you pick them. If you want to print all of
the reports, choose menu selection "13". You will be asked if
you have a comments file that you would like to include in the
report. The comments file can be any text file. If you don't
want to print any reports and would just like to exit TRACKER,
enter "14". An example of a report file that had three reports
TRACKER REPORTS Page 5-2
generated follows:
REPORT MENU
==============================================================
Choose the number of the report that you would like generated.
The star(s) indicate that you have already requested that
report to be generated.
1) Parameter Data List
2) Comments File
3) All Element Status Report
4) List By Subsystem
5) List By Milestone
6) List By Person
* 7) Subsystem Summary
* 8) Milestone Summary
9) Work Units Per Subsystem
* 10) Percent Completion Of Work Within Subsystem
11) Distribution Of Remaining Work Within
Subsystems
12) Completion Date For Milestones
13) All Of The Above and EXIT
14) EXIT FROM TRACKER
TRACKER REPORTS Page 5-3
If you print all reports, the session will look like this:
REPORT MENU
==============================================================
Choose the number of the report that you would like generated.
The star(s) indicate that you have already requested that
report to be generated.
1) Parameter Data List
2) Comments File
3) All Element Status Report
4) List By Subsystem
5) List By Milestone
6) List By Person
7) Subsystem Summary
8) Milestone Summary
9) Work Units Per Subsystem
10) Percent Completion Of Work Within Subsystem
11) Distribution Of Remaining Work Within
Subsystems
12) Completion Date For Milestones
13) All Of The Above and EXIT
14) EXIT FROM TRACKER
__
13
Do you have a comments file that you would
like to include?
_
[Y or N, default=N] : N
XDJDE FORMAT=LNDPDE,DUPLEX=NO,MARGIN=(0 IN),END;
5.2 SAMPLE TRACKER REPORTS
TRACKER REPORTS Page 5-4
5.2.1 Parameter Data Report
Project Name: TRACKER REDESIGN #256 Status Date: 4/12/1985
Project Manager: Sam Harbaugh
NUMBER OF ACTIVITIES : 5
NUMBER OF MILESTONES : 3
NUMBER OF PERSONNEL : 2
NUMBER OF SUBSYSTEMS : 2
NUMBER OF ELEMENTS : 40
SUBSYSTEM % AVAILABLE AT START
--------- --------------------
TRACKER 0.00%
INPREP 0.00%
PERSON'S NAME INITIALS RATE PER HOUR HOURS PER WEEK START DATE STOP DATE
------------- -------- ------------- -------------- ---------- ----------
MAY LEE ML 2.500 40 0/ 0/ 0 99/99/99
BONNIE BURKHARDT BB 2.500 40 0/ 0/ 0 99/99/99
ACTIVITY NAME % TOTAL PROJECT PRIORITY CONSIDERED % AVAILABLE AT START
------------- --------------- -------- ---------- --------------------
HI LEVEL D 15.00% 1 YES 0.00%
DETAIL DES 20.00% 2 YES 0.00%
CODE 25.00% 3 YES 0.00%
UNIT TEST 20.00% 3 YES 0.00%
INTEGRATE 20.00% 3 YES 0.00%
TASK NUMBERS
HI L DETA CODE UNIT INTE
---- ---- ---- ---- ----
3000 3000 3000 3000 3000
3000 3000 3000 3000 3000
MILESTONE DUE DATE DESCRIPTION
--------- ---------- -----------
1 2/19/1985 GENERIC PACKAGES, TRACKER DRIVERS FINISHED
2 3/15/1985 MENUS, MENU DRIVER, READ/WRITE TO FILE
3 5/ 3/1985 PROMPTING AND REPORT GENERATION WORKS
MILESTONE COMPLETION SEQUENCE
1 2 3
TRACKER REPORTS Page 5-5
5.2.2 Comments Report
TRACKER COMMENTS
====================================================================================================================================
A copy of any comments file may be included in this report.
TRACKER REPORTS Page 5-6
5.2.3 All Element Status Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** ALL ELEMENT STATUS REPORT ***
** ACTIVITIES ** ORIGINL CURRENT EQ. NEW SIZE LST
MS PR SUBSYSTEM DESCRIPTION ABREV RP H D C U I SIZE SIZE SIZE VERIFIED COMPXY
-- -- --------- ----------- ------ -- - - - - - ------- ------- ------- -------- ------
1 1 TRACKER CALENDAR PACKAGE CALNDR BB D D D D D 140 140 140 2/22/85 1.000
1 1 INPREP LIST PACKAGE LISTPK ML D D D D D 100 123 123 2/22/85 1.000
1 1 INPREP DATA PACKAGE DATAPK ML D D D D * 100 130 130 2/22/85 1.000
BB * * * * D
1 2 INPREP VT100 AND MENUS VT100 ML D D D D D 400 503 503 2/22/85 1.000
1 2 INPREP PROMPTS PROMPT ML D D D D D 800 1205 1205 2/22/85 1.000
2 1 TRACKER TRACKER TRACKR BB D 9 7 7 4 250 86 86 2/22/85 1.000
2 2 INPREP INITIALIZE TRACKER INITTR ML D D D 9 8 30 14 14 2/22/85 1.000
2 2 INPREP SET UP TRACKER SETUP ML D D D 9 9 30 34 34 2/22/85 1.000
2 2 INPREP MANIPULATE DATA MANDAT ML D D 9 8 8 70 35 35 2/22/85 1.000
2 2 TRACKER PRIORITIZE PRIOR BB D D 9 5 4 150 92 92 2/22/85 1.000
2 3 TRACKER CALCULATE TIME DONE CALCTI BB D D D 9 9 100 111 111 2/22/85 1.000
2 2 INPREP CHECK AC TOTAL PERCENT CHKPCT ML D D D 9 8 30 33 33 2/22/85 1.000
3 3 INPREP GROUP DATA FIXES FIXDAT BB D D D 6 5 70 77 77 4/12/85 1.000
3 3 INPREP RESET ENTIRE DATA RESET BB D D 7 4 30 30 30 4/12/85 1.000
3 3 INPREP UPDATE ORIGINAL TO CURRENT SIZE ORIGFX BB D D D D D 10 10 10 4/12/85 1.000
2 2 INPREP WRITE DATA WRDATA ML D D D D D 20 20 20 4/ 5/85 1.000
1 2 INPREP MENU DRIVER MENUDR ML D D D D D 130 144 144 4/ 5/85 1.000
1 1 INPREP GET DATA FROM FILE GETDAT ML D D D D D 35 29 29 4/ 5/85 1.000
3 3 INPREP GLOBAL DATA PKG GLOBAL ML D D D 9 5 75 48 48 4/12/85 1.000
3 3 INPREP ACTIVITY PKG AC ML D D D 8 7 500 241 241 4/12/85 1.000
3 3 INPREP MILESTONE PKG MS ML D D 9 7 3 450 200 200 4/12/85 1.000
3 3 INPREP PERSONNEL PKG PR ML D D 9 6 5 500 370 370 4/12/85 1.000
3 3 INPREP SUBSYSTEM PKG SS ML D D D 7 4 350 177 177 4/12/85 1.000
3 3 INPREP ELEMENT PKG EL ML D D 8 * * 550 581 581 4/12/85 1.000
BB * * * 7 7
1 1 TRACKER REPORT DRIVER REPORT BB D D D D D 100 121 121 4/ 5/85 1.000
2 2 TRACKER CALC PERCENT DONE CALPCT BB D D 9 8 8 140 120 120 4/ 5/85 1.000
2 2 TRACKER REPORT COMMENTS RCOMMN ML D D D 6 35 34 34 4/ 5/85 1.000
3 3 TRACKER REPORT DATE DONE BY MS RDATDN BB D D 7 4 150 150 150 4/12/85 1.000
2 2 TRACKER REPORT ALL ELEMENTS RLSTEL BB D D D 8 4 150 156 156 4/ 5/85 1.000
2 2 TRACKER REPORT EL BY MILESTONE RLSTMS BB D D D 8 7 175 190 190 4/ 5/85 1.000
2 2 TRACKER REPORT EL BY PERSON RLSTPR BB D D D 9 9 175 171 171 4/ 5/85 1.000
2 2 TRACKER REPORT EL BY SUBSYSTEM RLSTSS BB D D D 9 7 175 179 179 4/ 5/85 1.000
2 1 TRACKER REPORT NEW PAGE RPAGE BB D D D D D 30 30 30 4/ 5/85 1.000
3 3 TRACKER REPORT PARAMETER DATA RPARAM BB D D 7 7 5 250 249 249 4/12/85 1.000
3 3 TRACKER REPORT PCT DONE BY SUBSYSTEM RPCTSS BB D D 8 7 5 150 106 106 4/12/85 1.000
TRACKER REPORTS Page 5-7
3 3 TRACKER LIST OF REPORTS PRINTED RPRINT ML D D D D D 26 26 26 4/12/85 1.000
TRACKER REPORTS Page 5-8
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** ALL ELEMENT STATUS REPORT ***
** ACTIVITIES ** ORIGINL CURRENT EQ. NEW SIZE LST
MS PR SUBSYSTEM DESCRIPTION ABREV RP H D C U I SIZE SIZE SIZE VERIFIED COMPXY
-- -- --------- ----------- ------ -- - - - - - ------- ------- ------- -------- ------
3 3 TRACKER REPORT MILSTONE SUMMARY RSUMMS BB D D D 8 7 125 116 116 4/12/85 1.000
3 3 TRACKER REPORT SUBSYSTEM SUMMARY RSUMSS BB D D D 8 7 125 116 116 4/12/85 1.000
3 3 TRACKER REPORT WORK DISTRIBUTION RDIST BB D D 7 7 6 150 139 139 4/12/85 1.000
3 3 TRACKER REPORT WORK BY SUBSYSTEM RBYSS BB D D 7 6 4 150 120 120 4/12/85 1.000
------- ------- ------- -------- ------
TOTALS 7026 6456 6456 1.000
TRACKER REPORTS Page 5-9
5.2.4 List By Subsystem Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** LIST BY SUBSYSTEM REPORT ***
TRACKER
** ACTIVITIES ** ORIGINL CURRENT EQ. NEW SIZE LST MAN-HRS
MS PR DESCRIPTION ABREV RP H D C U I SIZE SIZE SIZE VERIFIED COMPXY TO COMP
-- -- ----------- ----- -- - - - - - ------- ------- ------- -------- ------ -------
1 1 CALENDAR PACKAGE CALNDR BB D D D D D 140 140 140 2/22/85 1.00 0.0
2 1 TRACKER TRACKR BB D 9 7 7 4 250 86 86 2/22/85 1.00 9.5
2 2 PRIORITIZE PRIOR BB D D 9 5 4 150 92 92 2/22/85 1.00 9.0
2 3 CALCULATE TIME DONE CALCTI BB D D D 9 9 100 111 111 2/22/85 1.00 1.8
1 1 REPORT DRIVER REPORT BB D D D D D 100 121 121 4/ 5/85 1.00 0.0
2 2 CALC PERCENT DONE CALPCT BB D D 9 8 8 140 120 120 4/ 5/85 1.00 5.0
2 2 REPORT COMMENTS RCOMMN ML D D D 6 35 34 34 4/ 5/85 1.00 3.8
3 3 REPORT DATE DONE BY MS RDATDN BB D D 7 4 150 150 150 4/12/85 1.00 23.7
2 2 REPORT ALL ELEMENTS RLSTEL BB D D D 8 4 150 156 156 4/ 5/85 1.00 10.0
2 2 REPORT EL BY MILESTONE RLSTMS BB D D D 8 7 175 190 190 4/ 5/85 1.00 7.6
2 2 REPORT EL BY PERSON RLSTPR BB D D D 9 9 175 171 171 4/ 5/85 1.00 2.7
2 2 REPORT EL BY SUBSYSTEM RLSTSS BB D D D 9 7 175 179 179 4/ 5/85 1.00 5.7
2 1 REPORT NEW PAGE RPAGE BB D D D D D 30 30 30 4/ 5/85 1.00 0.0
3 3 REPORT PARAMETER DATA RPARAM BB D D 7 7 5 250 249 249 4/12/85 1.00 23.4
3 3 REPORT PCT DONE BY SUBSYSTEM RPCTSS BB D D 8 7 5 150 106 106 4/12/85 1.00 8.9
3 3 LIST OF REPORTS PRINTED RPRINT ML D D D D D 26 26 26 4/12/85 1.00 0.0
3 3 REPORT MILSTONE SUMMARY RSUMMS BB D D D 8 7 125 116 116 4/12/85 1.00 4.6
3 3 REPORT SUBSYSTEM SUMMARY RSUMSS BB D D D 8 7 125 116 116 4/12/85 1.00 4.6
3 3 REPORT WORK DISTRIBUTION RDIST BB D D 7 7 6 150 139 139 4/12/85 1.00 12.0
3 3 REPORT WORK BY SUBSYSTEM RBYSS BB D D 7 6 4 150 120 120 4/12/85 1.00 13.2
------- ------- ------- -------- ------ -------
TOTALS 2746 2452 2452 1.00 145.6
TRACKER REPORTS Page 5-10
5.2.5 List By Milestone Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** LIST BY MILESTONE REPORT ***
Milestone # 2 is due 3/15/85 -- MENUS, MENU DRIVER, READ/WRITE TO FILE
** ACTIVITIES ** ORIGINL CURRENT EQ. NEW SIZE LST MAN-HRS
PR SUBSYSTEM DESCRIPTION ABREV RP H D C U I SIZE SIZE SIZE VERIFIED COMPXY TO COMP
-- --------- ----------- ------ -- - - - - - ------- ------- ------- -------- ------ -------
1 TRACKER TRACKER TRACKR BB D 9 7 7 4 250 86 86 2/22/85 1.00 9.5
1 TRACKER REPORT NEW PAGE RPAGE BB D D D D D 30 30 30 4/ 5/85 1.00 0.0
2 INPREP INITIALIZE TRACKER INITTR ML D D D 9 8 30 14 14 2/22/85 1.00 0.3
2 INPREP SET UP TRACKER SETUP ML D D D 9 9 30 34 34 2/22/85 1.00 0.5
2 INPREP MANIPULATE DATA MANDAT ML D D 9 8 8 70 35 35 2/22/85 1.00 1.5
2 TRACKER PRIORITIZE PRIOR BB D D 9 5 4 150 92 92 2/22/85 1.00 9.0
2 INPREP CHECK AC TOTAL PERCENT CHKPCT ML D D D 9 8 30 33 33 2/22/85 1.00 0.8
2 INPREP WRITE DATA WRDATA ML D D D D D 20 20 20 4/ 5/85 1.00 0.0
2 TRACKER CALC PERCENT DONE CALPCT BB D D 9 8 8 140 120 120 4/ 5/85 1.00 5.0
2 TRACKER REPORT COMMENTS RCOMMN ML D D D 6 35 34 34 4/ 5/85 1.00 3.8
2 TRACKER REPORT ALL ELEMENTS RLSTEL BB D D D 8 4 150 156 156 4/ 5/85 1.00 10.0
2 TRACKER REPORT EL BY MILESTONE RLSTMS BB D D D 8 7 175 190 190 4/ 5/85 1.00 7.6
2 TRACKER REPORT EL BY PERSON RLSTPR BB D D D 9 9 175 171 171 4/ 5/85 1.00 2.7
2 TRACKER REPORT EL BY SUBSYSTEM RLSTSS BB D D D 9 7 175 179 179 4/ 5/85 1.00 5.7
3 TRACKER CALCULATE TIME DONE CALCTI BB D D D 9 9 100 111 111 2/22/85 1.00 1.8
------- ------- ------- -------- ------ -------
TOTALS 1560 1305 1305 1.00 58.3
TRACKER REPORTS Page 5-11
5.2.6 List By Person Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** LIST BY PERSON REPORT ***
MAY LEE
** ACTIVITIES ** ORIG CURRNT EQ NEW MAN-HRS FINISH DUE
MS PR SUBSYSTEM DESCRIPTION ABREV H D C U I SIZE SIZE SIZE CPX TO COMP DATE DATE
-- -- --------- ----------- ----- - - - - - ------ ------ ------ --- ------- -------- --------
1 1 INPREP LIST PACKAGE LISTPK D D D D D 100 123 123 1.0 0.0 DONE 2/19/85
1 1 INPREP DATA PACKAGE DATAPK D D D D * 100 130 130 1.0 0.0 DONE 2/19/85
1 1 INPREP GET DATA FROM FILE GETDAT D D D D D 35 29 29 1.0 0.0 DONE 2/19/85
1 2 INPREP VT100 AND MENUS VT100 D D D D D 400 503 503 1.0 0.0 DONE 2/19/85
1 2 INPREP PROMPTS PROMPT D D D D D 800 1205 1205 1.0 0.0 DONE 2/19/85
1 2 INPREP MENU DRIVER MENUDR D D D D D 130 144 144 1.0 0.0 DONE 2/19/85
2 2 INPREP INITIALIZE TRACKER INITTR D D D 9 8 30 14 14 1.0 0.3 4/15/85 3/15/85
2 2 INPREP SET UP TRACKER SETUP D D D 9 9 30 34 34 1.0 0.5 4/15/85 3/15/85
2 2 INPREP MANIPULATE DATA MANDAT D D 9 8 8 70 35 35 1.0 1.5 4/15/85 3/15/85
2 2 INPREP CHECK AC TOTAL PERCENT CHKPCT D D D 9 8 30 33 33 1.0 0.8 4/15/85 3/15/85
2 2 INPREP WRITE DATA WRDATA D D D D D 20 20 20 1.0 0.0 DONE 3/15/85
2 2 TRACKER REPORT COMMENTS RCOMMN D D D 6 35 34 34 1.0 3.8 4/15/85 3/15/85
3 3 INPREP GLOBAL DATA PKG GLOBAL D D D 9 5 75 48 48 1.0 2.3 4/16/85 5/ 3/85
3 3 INPREP ACTIVITY PKG AC D D D 8 7 500 241 241 1.0 9.6 4/17/85 5/ 3/85
3 3 INPREP MILESTONE PKG MS D D 9 7 3 450 200 200 1.0 18.0 4/19/85 5/ 3/85
3 3 INPREP PERSONNEL PKG PR D D 9 6 5 500 370 370 1.0 30.3 4/25/85 5/ 3/85
3 3 INPREP SUBSYSTEM PKG SS D D D 7 4 350 177 177 1.0 12.7 4/29/85 5/ 3/85
3 3 INPREP ELEMENT PKG EL D D 8 * * 550 581 581 1.0 62.7 5/ 3/85 5/ 3/85
3 3 TRACKER LIST OF REPORTS PRINTED RPRINT D D D D D 26 26 26 1.0 0.0 DONE 5/ 3/85
----- ------ ------ --- ------- -------- --------
TOTALS 4231 3947 3947 1.0 142.7
TRACKER REPORTS Page 5-12
5.2.7 Subsystem Summary Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** SUBSYSTEM SUMMARY REPORT ***
MAN-HRS PERCENT
SUBSYSTEM ML BB TO COMP COMPLETE
--------- ------- ------- ------- --------
TRACKER 3.8 141.8 145.6 85.16%
INPREP 115.7 49.8 165.5 92.14%
------- ------- ------- --------
TOTALS: 119.5 191.6 311.1 89.48%
TRACKER REPORTS Page 5-13
5.2.8 Milestone Summary Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** MILESTONE SUMMARY REPORT ***
MAN-HRS PERCENT
MILESTONE ML BB TO COMP COMPLETE
--------- ------- ------- ------- --------
1 0.0 0.0 0.0 100.00%
2 7.0 51.3 58.3 88.83%
3 84.6 128.6 213.3 80.65%
------- ------- ------- --------
TOTALS: 91.6 180.0 271.6 89.48%
TRACKER REPORTS Page 5-14
5.2.9 Lines Of Code Per Subsystem Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** LINES OF CODE PER SUBSYSTEM ***
ORIGINAL CURRENT EQ. NEW OLDEST MOST RECENT
SUBSYSTEM SIZE SIZE SIZE VERIFICATION VERIFICATION
--------- -------- -------- -------- ------------ ------------
TRACKER 2746 2452 2452 2/22/1985 4/12/1985
INPREP 4280 4004 4004 2/22/1985 4/12/1985
-------- -------- -------- ------------ ------------
TOTALS: 7026 6456 6456 2/22/1985 4/12/1985
TRACKER REPORTS Page 5-15
5.2.10 Percent Complete Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** ORIGINAL ESTIMATE OF PERCENT COMPLETE WITHIN SUBSYSTEM ***
% DONE % AVAIL %ENTIRE
SUBSYSTEM HI LEVE DETAIL CODE UNIT TE INTEGRA CONTRACT AT START PROJECT
--------- ------- ------- ------- ------- ------- -------- -------- -------
TRACKER 100.00% 99.09% 87.47% 75.71% 59.92% 83.81% 0.00% 83.81%
INPREP 100.00% 100.00% 94.84% 81.74% 71.46% 89.35% 0.00% 89.35%
--------- ------- ------- ------- ------- ------- -------- -------- -------
TOTALS ON
CONTRACT: 100.00% 99.64% 91.96% 79.38% 66.95% 87.19% 0.00% 87.19%
% AVAIL
START: 0.00% 0.00% 0.00% 0.00% 0.00%
% ENTIRE
PROJECT: 100.00% 99.64% 91.96% 79.38% 66.95%
TRACKER REPORTS Page 5-16
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** CURRENT ESTIMATE OF PERCENT COMPLETE WITHIN SUBSYSTEM ***
% DONE % AVAIL %ENTIRE
SUBSYSTEM HI LEVE DETAIL CODE UNIT TE INTEGRA CONTRACT AT START PROJECT
--------- ------- ------- ------- ------- ------- -------- -------- -------
TRACKER 100.00% 99.65% 89.17% 77.27% 62.40% 85.16% 0.00% 85.16%
INPREP 100.00% 100.00% 95.36% 86.21% 80.27% 92.14% 0.00% 92.14%
--------- ------- ------- ------- ------- ------- -------- -------- -------
TOTALS ON
CONTRACT: 100.00% 99.87% 93.01% 82.81% 73.48% 89.48% 0.00% 89.48%
% AVAIL
START: 0.00% 0.00% 0.00% 0.00% 0.00%
% ENTIRE
PROJECT: 100.00% 99.87% 93.01% 82.81% 73.48%
TRACKER REPORTS Page 5-17
5.2.11 Distribution Of Work Remaining Within Subsystem Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** ORIGINAL DISTRIBUTION OF WORK REMAINING WITHIN SUBSYSTEM ***
(in MAN-HOURS)
TOTAL PERCENT
SUBSYSTEM HI LEVEL DETAIL D CODE UNIT TES INTEGRAT REMAINING COMPLET
--------- -------- -------- -------- -------- -------- --------- -------
TRACKER 0.0 2.0 34.4 53.4 88.0 177.8 83.81%
INPREP 0.0 0.0 22.1 62.5 97.7 182.3 89.35%
-------- -------- -------- -------- -------- --------- -------
TOTALS: 0.0 2.0 56.5 115.9 185.8 360.1 87.19%
% OF TOTAL: 0.00% + 0.56% + 15.69% + 32.18% + 51.58% = 100.00%
TRACKER REPORTS Page 5-18
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** CURRENT DISTRIBUTION OF WORK REMAINING WITHIN SUBSYSTEM ***
(in MAN-HOURS)
TOTAL PERCENT
SUBSYSTEM HI LEVEL DETAIL D CODE UNIT TES INTEGRAT REMAINING COMPLET
--------- -------- -------- -------- -------- -------- --------- -------
TRACKER 0.0 0.7 26.6 44.6 73.8 145.6 85.16%
INPREP 0.0 0.0 18.6 44.2 63.2 126.0 92.14%
-------- -------- -------- -------- -------- --------- -------
TOTALS: 0.0 0.7 45.1 88.8 137.0 271.6 89.48%
% OF TOTAL: 0.00% + 0.25% + 16.62% + 32.69% + 50.44% = 100.00%
TRACKER REPORTS Page 5-19
5.2.12 Completion Date For Milestones Report
Project Name: TRACKER REDESIGN
Project Manager: Sam Harbaugh
Status Date: 4/12/85
*** COMPLETION DATE FOR MILESTONES ***
MILE- PREVIOUS CURRENT DUE
STONE ML BB COMPL DATE COMPL DATE DATE
----- -------- -------- ---------- ---------- --------
1 DONE DONE 4/ 8/85 DONE 2/19/85
2 4/15/85 4/23/85 4/18/85 4/23/85 3/15/85
3 5/ 3/85 5/16/85 5/15/85 5/16/85 5/ 3/85
-------- -------- ---------- ---------- --------
TOTAL: 5/ 3/85 5/16/85 5/16/85
TRACKER REPORTS Page 5-20
5.2.13 Reports Printed List
REPORTS PRINTED
====================================================================================================================================
Parameter Data List
Tracker Comments
All Element Status Report
List By Subsystem
List By Milestone
List By Person
Subsystem Summary
Milestone Summary
Work Units Per Subsystem
Percent Completion Of Work Within Subsystem
Distribution Of Remaining Work Within Subsystems
Completion Date For Milestones
XDJDE FORMAT=P06PDE,MARGIN=(.75 IN),END;
\f
APPENDIX A
A.1 GLOSSARY OF TERMS
________
ACTIVITY
The project is broken into phases of development, otherwise
known in TRACKER as activities. Each routine or piece of the
project must go through each phase of development. A maximum of
10 activities may be defined for a project. For example, most
software projects have activities similar to the following: HIGH
LEVEL DESIGN, DETAIL DESIGN, CODE, UNIT TEST, and INTEGRATE.
_______
ELEMENT
Each routine or component of the project is entered into
TRACKER as an ELEMENT. The element is given a description, a
unique abbreviation of up to 6 characters in length, and a size
measured in some unit. In software, the unit of measurement for
size is usually SLOC's or Source Lines Of Code. The element is
also assigned to one subsystem and one milestone. One person may
be assigned to work on the entire element or a person could be
assigned to each phase of development in the element, meaning,
more than one person could work on any given element.
_________
MILESTONE
A maximum of 99 Milestones may be defined in a given
project. Each milestone is assigned a number, description and
due date. A milestone describes a significant point in the
project development. In TRACKER, the milestones are defined
similar to "this group of routines or components is completely
finished", not as "high level design is done" or "Preliminary
Design Review is complete". TRACKER can only determine when a
group of routines is complete, not if a phase of development is
complete.
_________
PERSONNEL
Several people may be assigned to a project at one time.
TRACKER takes into consideration the person's work speed
(measured in units of work produced per hour) and up to three
Page A-2
pairs of start/stop dates for each person.
_________
SUBSYSTEM
The project being tracked is broken down into subsystems.
Each subsystem contains several routines or components that have
a common purpose. For example, one project may have subsystems
for REPORT GENERATION, ANTENNA MANIPULATION, and SIGNAL
PROCESSING.
_______
TRACKER
TRACKER is an interactive, menu driven management tool used
for tracking the progress on a project (mainly software
projects). It will calculate percent complete and dates of
completion. By using the data entered by the user and the
calculations obtained, several different reports can be produced.
--::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--tracker.m
--::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
CONTENTS
1 WORK_CALENDAR . . . . . . . . . . . . . . . . . . . 4
2 LIST_PKG . . . . . . . . . . . . . . . . . . . . . . 4
2.1 ADD . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 EMPTY_LIST . . . . . . . . . . . . . . . . . . . . 5
2.3 FIND . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 CHANGE_LIST_KEY . . . . . . . . . . . . . . . . . 6
2.5 CHANGE_LIST_DATA . . . . . . . . . . . . . . . . . 6
2.6 DELETE . . . . . . . . . . . . . . . . . . . . . . 6
2.7 START_WALK . . . . . . . . . . . . . . . . . . . . 7
2.8 WALK . . . . . . . . . . . . . . . . . . . . . . . 7
3 DATA_PKG . . . . . . . . . . . . . . . . . . . . . . 8
4 VT100 . . . . . . . . . . . . . . . . . . . . . . . 8
4.1 CLEAR_SCREEN . . . . . . . . . . . . . . . . . . . 9
4.2 PRINT_REPORT_MENU . . . . . . . . . . . . . . . . 9
4.3 PRINT_DATA_MENU . . . . . . . . . . . . . . . . . 9
4.4 PRINT_GLOBAL_MENU . . . . . . . . . . . . . . . 10
4.5 PRINT_OPERATION_MENU . . . . . . . . . . . . . . 10
4.6 PRINT_EL_OPERATION_MENU . . . . . . . . . . . . 10
4.7 PRINT_EL_GROUPS . . . . . . . . . . . . . . . . 11
4.8 PRINT_AC_MENU . . . . . . . . . . . . . . . . . 11
4.9 PRINT_EL_MENU . . . . . . . . . . . . . . . . . 11
4.10 PRINT_MS_MENU . . . . . . . . . . . . . . . . . 12
4.11 PRINT_PR_MENU . . . . . . . . . . . . . . . . . 12
4.12 PRINT_SS_MENU . . . . . . . . . . . . . . . . . 12
4.13 TRACKER_INTRO . . . . . . . . . . . . . . . . . 13
4.14 GOODBYE_MESSAGE . . . . . . . . . . . . . . . . 13
5 PROMPT_PKG . . . . . . . . . . . . . . . . . . . . 13
5.1 DISPLAY_ELEMENT_DATA . . . . . . . . . . . . . . 14
5.2 DISPLAY_SUBSYSTEM_DATA . . . . . . . . . . . . . 14
5.3 DISPLAY_PERSONNEL_DATA . . . . . . . . . . . . . 15
5.4 DISPLAY_MILESTONE_DATA . . . . . . . . . . . . . 15
5.5 DISPLAY_ACTIVITY_DATA . . . . . . . . . . . . . 15
6 TRACKER - MAIN . . . . . . . . . . . . . . . . . . 17
6.1 INITIALIZE_TRACKER_DATA . . . . . . . . . . . . 17
6.2 SET_UP_TRACKER_DATA . . . . . . . . . . . . . . 17
6.3 MANIPULATE_DATA . . . . . . . . . . . . . . . . 18
6.3.1 CHECK_AC_PERCENT . . . . . . . . . . . . . . . 18
6.3.2 PRIORITIZE . . . . . . . . . . . . . . . . . 19
6.3.2.1 SORT_EL_IN_MS . . . . . . . . . . . . . . . 19
6.3.2.2 SORT_EL_IN_PR . . . . . . . . . . . . . . . 19
6.3.3 CALC_TIME_DONE . . . . . . . . . . . . . . . . 20
6.3.3.1 GET_EL_TIME . . . . . . . . . . . . . . . . 20
6.3.4 GROUP_DATA_FIXES . . . . . . . . . . . . . . . 21
6.3.4.1 RESET_DATA . . . . . . . . . . . . . . . . . 21
6.3.4.2 UPDATE_ORIGINAL . . . . . . . . . . . . . . 21
6.4 WRITE_DATA_TO_FILE . . . . . . . . . . . . . . . 22
6.5 DATA_MENU_DRIVER . . . . . . . . . . . . . . . . 22
6.6 GET_DATA . . . . . . . . . . . . . . . . . . . . 23
6.7 GLOBAL_PKG . . . . . . . . . . . . . . . . . . . 23
6.7.1 GL_INITIALIZE . . . . . . . . . . . . . . . . 24
6.7.2 GL_SET_UP . . . . . . . . . . . . . . . . . . 24
6.7.3 GL_SAVE . . . . . . . . . . . . . . . . . . . 24
6.8 ACTIVITY_PKG . . . . . . . . . . . . . . . . . . 25
Page 2
6.8.1 AC_ADD . . . . . . . . . . . . . . . . . . . . 25
6.8.2 AC_INITIALIZE . . . . . . . . . . . . . . . . 26
6.8.3 AC_SET_UP . . . . . . . . . . . . . . . . . . 26
6.8.3.1 AC_READ . . . . . . . . . . . . . . . . . . 27
6.8.4 AC_DELETE . . . . . . . . . . . . . . . . . . 27
6.8.4.1 DELETE_AC_COMPLETENESS . . . . . . . . . . . 28
6.8.4.2 DELETE_SS_TASK_NUM . . . . . . . . . . . . . 28
6.8.4.3 DELETE_MULTIPLE_PEOPLE . . . . . . . . . . 28
6.8.5 AC_MODIFY . . . . . . . . . . . . . . . . . . 29
6.8.5.1 MODIFY_AC_KEY . . . . . . . . . . . . . . . 29
6.8.6 AC_SAVE . . . . . . . . . . . . . . . . . . . 30
6.8.6.1 AC_WRITE . . . . . . . . . . . . . . . . . . 30
6.9 MILESTONE_PKG . . . . . . . . . . . . . . . . . 30
6.9.1 CHANGE_MS_IN_EL . . . . . . . . . . . . . . . 31
6.9.2 MS_ADD . . . . . . . . . . . . . . . . . . . . 31
6.9.3 MS_INITIALIZE . . . . . . . . . . . . . . . . 32
6.9.4 MS_SET_UP . . . . . . . . . . . . . . . . . . 32
6.9.4.1 MS_READ . . . . . . . . . . . . . . . . . . 33
6.9.5 MS_DELETE . . . . . . . . . . . . . . . . . . 33
6.9.6 MS_MODIFY . . . . . . . . . . . . . . . . . . 33
6.9.6.1 MODIFY_MILESTONE_KEY . . . . . . . . . . . . 34
6.9.7 MS_SAVE . . . . . . . . . . . . . . . . . . . 34
6.9.7.1 MS_WRITE . . . . . . . . . . . . . . . . . . 35
6.10 PERSONNEL_PKG . . . . . . . . . . . . . . . . . 35
6.10.1 CHANGE_PR_IN_EL . . . . . . . . . . . . . . . 35
6.10.2 PR_ADD . . . . . . . . . . . . . . . . . . . . 36
6.10.3 PR_INITIALIZE . . . . . . . . . . . . . . . . 36
6.10.4 PR_SET_UP . . . . . . . . . . . . . . . . . . 37
6.10.4.1 PR_READ . . . . . . . . . . . . . . . . . . 37
6.10.5 PR_DELETE . . . . . . . . . . . . . . . . . . 38
6.10.6 PR_MODIFY . . . . . . . . . . . . . . . . . . 38
6.10.6.1 MODIFY_PERSONNEL_KEY . . . . . . . . . . . . 39
6.10.6.2 MODIFY_START_STOP_DATE . . . . . . . . . . 39
6.10.7 PR_SAVE . . . . . . . . . . . . . . . . . . . 39
6.10.7.1 PR_WRITE . . . . . . . . . . . . . . . . . . 40
6.11 SUBSYSTEM_PKG . . . . . . . . . . . . . . . . . 40
6.11.1 SS_ADD . . . . . . . . . . . . . . . . . . . . 41
6.11.2 SS_INITIALIZE . . . . . . . . . . . . . . . . 41
6.11.3 SS_SET_UP . . . . . . . . . . . . . . . . . . 41
6.11.3.1 SS_READ . . . . . . . . . . . . . . . . . . 42
6.11.4 SS_DELETE . . . . . . . . . . . . . . . . . . 42
6.11.5 CHANGE_SS_IN_EL . . . . . . . . . . . . . . . 43
6.11.6 SS_MODIFY . . . . . . . . . . . . . . . . . . 43
6.11.7 SS_SAVE . . . . . . . . . . . . . . . . . . . 44
6.11.7.1 SS_WRITE . . . . . . . . . . . . . . . . . . 44
6.12 ELEMENT_PKG . . . . . . . . . . . . . . . . . . 45
6.12.1 ADD_RECORD_TO_LISTS . . . . . . . . . . . . . 45
6.12.2 EL_ADD . . . . . . . . . . . . . . . . . . . . 45
6.12.3 EL_INITIALIZE . . . . . . . . . . . . . . . . 46
6.12.4 UPDATE_CURRENT . . . . . . . . . . . . . . . . 46
6.12.4.1 FIX_EL_SIZE . . . . . . . . . . . . . . . . 47
6.12.5 UPDATE_PCT_DONE . . . . . . . . . . . . . . . 47
6.12.6 EL_SET_UP . . . . . . . . . . . . . . . . . . 47
6.12.6.1 EL_READ . . . . . . . . . . . . . . . . . . 48
6.12.7 EL_DELETE . . . . . . . . . . . . . . . . . . 48
Page 3
6.12.8 EL_MODIFY . . . . . . . . . . . . . . . . . . 49
6.12.8.1 MODIFY_ELEMENT_KEY . . . . . . . . . . . . . 49
6.12.9 EL_SAVE . . . . . . . . . . . . . . . . . . . 50
6.12.9.1 EL_WRITE . . . . . . . . . . . . . . . . . . 50
6.13 REPORT_GENERATOR . . . . . . . . . . . . . . . 51
6.13.1 CALC_PCT_DONE . . . . . . . . . . . . . . . . 52
6.13.1.1 GET_SS_TOTALS . . . . . . . . . . . . . . . 52
6.13.2 PRINT_COMMENTS . . . . . . . . . . . . . . . . 52
6.13.3 COMPLETION_DATE_FOR_MS . . . . . . . . . . . . 53
6.13.3.1 INIT_DATE_HEADERS . . . . . . . . . . . . . 53
6.13.3.2 CALC_DATE_TOTALS . . . . . . . . . . . . . 54
6.13.3.3 PRINT_A_DATE . . . . . . . . . . . . . . . . 54
6.13.3.4 PRINT_MS_DATES . . . . . . . . . . . . . . . 54
6.13.3.5 PRINT_TOT_MS_DATES . . . . . . . . . . . . . 55
6.13.4 ALL_ELMNT_STATUS_REP . . . . . . . . . . . . . 55
6.13.4.1 INIT_EL_HEADERS . . . . . . . . . . . . . . 55
6.13.4.2 PRINT_EL . . . . . . . . . . . . . . . . . . 56
6.13.5 LIST_BY_MILESTONE . . . . . . . . . . . . . . 56
6.13.5.1 INIT_HEADERS . . . . . . . . . . . . . . . . 57
6.13.5.2 PRINT_AN_ELEMENT . . . . . . . . . . . . . . 57
6.13.5.3 PRINT_MS_TOTAL . . . . . . . . . . . . . . . 57
6.13.6 LIST_BY_PERSON . . . . . . . . . . . . . . . . 58
6.13.6.1 INIT_PR_HEADERS . . . . . . . . . . . . . . 58
6.13.6.2 PRINT_PR_ELEMENT . . . . . . . . . . . . . . 58
6.13.6.3 PRINT_PR_TOTAL . . . . . . . . . . . . . . . 59
6.13.7 LIST_BY_SUBSYSTEM . . . . . . . . . . . . . . 59
6.13.7.1 INIT_SS_HEADERS . . . . . . . . . . . . . . 59
6.13.7.2 PRINT_SS_ELEMENT . . . . . . . . . . . . . . 60
6.13.7.3 PRINT_SS_TOTAL . . . . . . . . . . . . . . . 60
6.13.8 START_PAGE . . . . . . . . . . . . . . . . . . 61
6.13.9 PARAMETER_DATA_LIST . . . . . . . . . . . . . 61
6.13.10 PERCENT_COMPLETION . . . . . . . . . . . . . . 61
6.13.10.1 INIT_PCT_HEADERS . . . . . . . . . . . . . 62
6.13.11 REPORTS_PRINTED_LIST . . . . . . . . . . . . . 62
6.13.12 MILESTONE_SUMMARY . . . . . . . . . . . . . . 62
6.13.12.1 INIT_SUMMS_HEADERS . . . . . . . . . . . . . 63
6.13.12.2 CALC_SUMMS_TOTALS . . . . . . . . . . . . . 63
6.13.12.3 PRINT_SUMMS . . . . . . . . . . . . . . . . 64
6.13.12.4 PRINT_SUMMS_TOTALS . . . . . . . . . . . . 64
6.13.13 SUBSYSTEM_SUMMARY . . . . . . . . . . . . . . 64
6.13.13.1 INIT_SUMSS_HEADERS . . . . . . . . . . . . . 65
6.13.13.2 CALC_SUMSS_TOTALS . . . . . . . . . . . . . 65
6.13.13.3 PRINT_SUMSS . . . . . . . . . . . . . . . . 65
6.13.13.4 PRINT_SUMSS_TOTALS . . . . . . . . . . . . . 66
6.13.14 WORK_UNITS_PER_SS . . . . . . . . . . . . . . 66
6.13.14.1 INIT_SIZE_HEADERS . . . . . . . . . . . . . 66
6.13.14.2 CALC_SIZE . . . . . . . . . . . . . . . . . 67
6.13.15 DISTRIBUTION_OF_WORK . . . . . . . . . . . . . 67
6.13.15.1 INIT_DIST_HEADERS . . . . . . . . . . . . . 68
6.13.15.2 CALC_SS_WORK . . . . . . . . . . . . . . . 68
Page 4
1 WORK_CALENDAR
OVERVIEW:
This package provides functions for manipulating time in a work
week. It assumes that the date entered is the last day of the work
week. This implies that when you are adding hours to a date, time for
the weekend is added before the time for work.
HISTORY:
written by Bonnie Burkhardt March 1985
EXCEPTIONS HANDLED:
none
2 LIST_PKG
OVERVIEW:
This package defines the generic list used for all data types and
the actions that can be performed on them. In TRACKER, each data type
will have its own linked list instantiated in the respective data
package. The rec_data field is a pointer to a record of data.
For the generic case, the resulting data structure looks like
this:
prev_ptr current_ptr
. .
| |
V V
_________ _________ _________ <-- tail
head -->| next +-|--->| next +-|--->| next +-|---> null
|_________| |_________| |_________|
| rec_key | | rec_key | | rec_key |
|_________| |_________| |_________|
| rec_data| | rec_data| | rec_data|
|_________| |_________| |_________|
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
Page 5
2.1 ADD
OVERVIEW:
This procedure adds a new list record onto the end of the linked
list. This feature provides a simple method by which you could sort
the list; DELETE the list elements in the order you want the list to
be sorted. Once you have DELETEd it, ADD it back onto the end of the
list. Loop until the list is sorted.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
2.2 EMPTY_LIST
OVERVIEW:
This function determines if the list is empty by checking the
pointer to the head of the list. If it is null, true is returned.
Otherwise, the list is not empty.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
2.3 FIND
OVERVIEW:
This procedure searches the entire list for a record by the
rec_key and returns the record. Found = true if the record is found
and false otherwise. If the record is found, it is pointed to by
list.current_ptr.
EXCEPTIONS HANDLED:
none
Page 6
HISTORY:
written by May Lee February 1985
2.4 CHANGE_LIST_KEY
OVERVIEW:
This procedure will change the old_key to the new_key for a
list_type. Since this is a generic package, the programmer would
otherwise not be able to access the key directly from the program.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
2.5 CHANGE_LIST_DATA
OVERVIEW:
This procedure will find a record and change the old_data to the
new_data for a list type. Since this is a generic package, the
programmer would otherwise not be able to access the data directly
from the program.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
2.6 DELETE
OVERVIEW:
This procedure deletes a record from the linked list by removing
the links to that record. The record is first found by calling FIND.
If it is found, the record is pointed to by list.current_ptr. The
empty list record is deallocated by calling FREE.
Page 7
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
2.7 START_WALK
OVERVIEW:
Start the pointer at the head of the list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
2.8 WALK
OVERVIEW:
This procedure walks a linked list one link at a time, returning
the contents of that links data in rec_ptr. It can be used to write a
linked list to file or to print the contents of the list's data.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
Page 8
3 DATA_PKG
OVERVIEW:
This package defines the five basic data types used in tracker:
activity, element, milestone, personnel, and subsystem. Each one is a
record with a pointer pointing to that record. The values for the
fields are obtained by prompt/response sessions with the user.
Milestone, personnel, and subsystem data each have as a field of their
record, a pointer to the element list. This field is the list of
elements to which that data belongs. The List_Pkg instantiations for
each data type is also in this package.
In addition to the data types, this package contains the global
variables used in the Global_Package and the counters for each data
type.
Since most of the other packages with this package, instantiation
of the Calendar_Package and other frequently needed packages is done
in the data package to reduce the number of instantiations throughout
the TRACKER modules.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee February 1985
written by Bonnie Burkhardt March 1985
NOTES:
The function CONVERT, which is contained in this package, is only
there to correct a quirk in Ada when dealing with enumeration types
that are single characters. We have declared an enumeration type
act_phase_char_set, which is a subset of the ascii character set.
This enumeration type must appear with quotes around it when getting
it from a file or a user, and will be printed with quotes when put to
the screen. We want to be able to declare 1 as a member of
act_phase_char_set, but it is handled literally as '1' (including the
quotes).
4 VT100
OVERVIEW:
This package maintains actions that affect the screen display.
Various menus can be displayed by passing the appropriate parameter to
the function PRINT. The user's selection from the displayed menu is
returned.
Page 9
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
4.1 CLEAR_SCREEN
OVERVIEW:
This procedure clears the screen on a vt100 using an escape code
sequence.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
4.2 PRINT_REPORT_MENU
OVERVIEW:
The report menu consists of the various reports a user is allowed
to print.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.3 PRINT_DATA_MENU
OVERVIEW:
This procedure displays the different types of data that can be
manipulated.
Page 10
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.4 PRINT_GLOBAL_MENU
OVERVIEW:
This procedure displays the global variables that can be
manipulated.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.5 PRINT_OPERATION_MENU
OVERVIEW:
This procedure displays the operations that can be performed on a
data type.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.6 PRINT_EL_OPERATION_MENU
OVERVIEW:
This procedure displays the operations that can be performed on
an element data type.
Page 11
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.7 PRINT_EL_GROUPS
OVERVIEW:
This procedure displays the different groups of element data that
can be updated with the quick update.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.8 PRINT_AC_MENU
OVERVIEW:
This procedure displays the fields that can be changed on an
activity type.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.9 PRINT_EL_MENU
OVERVIEW:
This procedure displays the fields that can be changed on an
element type.
Page 12
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.10 PRINT_MS_MENU
OVERVIEW:
This procedure displays the fields that can be changed on a
milestone type.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.11 PRINT_PR_MENU
OVERVIEW:
This procedure displays the fields that can be changed on a
personnel type.
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.12 PRINT_SS_MENU
OVERVIEW:
This procedure displays the fields that can be changed on a
subsystem type.
Page 13
EXCEPTIONS HANDLED:
others the user is reprompted
HISTORY:
written by May Lee March 1985
4.13 TRACKER_INTRO
OVERVIEW:
This procedure prints the TRACKER banner introduction on the
terminal screen.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
4.14 GOODBYE_MESSAGE
OVERVIEW:
This procedure prints the TRACKER exit message on the terminal
screen.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
5 PROMPT_PKG
OVERVIEW:
This package contains the user prompt messages that will be
displayed on the screen. The prompts will only return valid data.
The user is trapped until a valid entry is received. If the data
being requested has a default value, the user may respond with a
Page 14
carriage return. If, the user responds with '?' ( or anything else
that causes an exception), then the prompt will be expanded to give
the user more information on the type of data to enter. For data that
does not have a default value, a carriage return or '?' will display
the extended prompt. Otherwise, the data is received from the user
and processed accordingly. If the data is invalid, the user will be
prompted again until valid data can be returned.
EXCEPTIONS HANDLED:
others any illegal input from the user
HISTORY:
written by May Lee March 1985
NOTES:
The search key for each data type has two types of prompts : one
for an existing key, and one for a new key that is not already in the
list.
This package also provides procedures to display the keys of each
data list to the screen.
5.1 DISPLAY_ELEMENT_DATA
OVERVIEW:
This procedure walks the list and prints the name of each element
to the screen.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
5.2 DISPLAY_SUBSYSTEM_DATA
OVERVIEW:
This procedure walks the list and prints the name of each
subsystem to the screen.
Page 15
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
5.3 DISPLAY_PERSONNEL_DATA
OVERVIEW:
This procedure walks the list and prints the name of each person
to the screen.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
5.4 DISPLAY_MILESTONE_DATA
OVERVIEW:
This procedure walks the list and prints the number of each
milestone to the screen.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
5.5 DISPLAY_ACTIVITY_DATA
OVERVIEW:
This procedure walks the list and prints the name of each
activity to the screen.
Page 16
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
Page 17
6 TRACKER - MAIN
OVERVIEW:
TRACKER is an ADA conversion of the original INPREP and TRACKR
programs written in IFTRAN. The Ada version of TRACKER is one program
that combines the two previous Iftran programs. It is written under
the VAX/VMS Version 4.0 environment.
The TRACKER program is a management tool used for estimating
project cost and scheduling requirements, and tracking progress within
projects by calculating dates of completion, amount of time required,
amount of code, and other variable data. Reports can be produced that
will show the status of the project from several different
perspectives.
EXCEPTIONS HANDLED:
name_error error message is printed and program terminates
ERROR_IN_INPUT_FILE error message is printed and program terminates
HISTORY:
written by May Lee March 1985
6.1 INITIALIZE_TRACKER_DATA
OVERVIEW:
This procedure calls the individual data initialize procedures in
a specific order to obtain the tracker information needed to make a
complete tracker file. The internal data structures are created and
the data is written to the tracker file. The name of the output file
is obtained in this procedure, but the file is actually created just
before the write in the procedure WRITE_DATA_TO_FILE.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.2 SET_UP_TRACKER_DATA
Page 18
OVERVIEW:
This procedure opens the tracker input file and calls the
individual data set_up procedures in a specified order to read in the
tracker data from the file and set up the internal data structures.
EXCEPTIONS HANDLED:
name_error if the given file can't be opened
. raised to the calling routine
others ERROR_IN_INPUT_FILE is raised
HISTORY:
Written by May Lee March 1985
6.3 MANIPULATE_DATA
OVERVIEW:
This is the main driver for manipulating and adding data. This
procedure calls the menu driver and the other necessary routines to
validate the data and calculate data needed to print reports before
the data is written to file.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
written by Bonnie Burkhardt March 1985
6.3.1 CHECK_AC_PERCENT -
OVERVIEW:
This procedure checks to see that the activity percent of project
adds up to 100.0%.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
Page 19
6.3.2 PRIORITIZE -
OVERVIEW:
This procedure sorts the element lists according to milestone
completion number and then element priority.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.3.2.1 SORT_EL_IN_MS -
OVERVIEW:
This procedure sorts the elements belonging to a given milestone
by element priority. If all elements have the same priority, no
sorting takes place. Otherwise, sorting is done by deleting the
lowest priority elements and adding them to the end of the element
list.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.3.2.2 SORT_EL_IN_PR -
OVERVIEW:
This procedure sorts the elements belonging to a given person
using the milestones sorted by completion sequence and the milestone's
elements sorted by element priority. Sorting is done by walking down
each milestone's element list and deleting and adding any elements
which belong to this person.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
Page 20
HISTORY:
written by Bonnie Burkhardt March 1985
6.3.3 CALC_TIME_DONE -
OVERVIEW:
This procedure calculates the date each element will be completed
and the total number of hours left to completion.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
NOTES:
The activities used in the calculations include all activities
that were marked as being considered in the calculations and all
activities whose priority is less than or equal to any activity marked
as being considered.
6.3.3.1 GET_EL_TIME -
OVERVIEW:
This procedure computes the total amount of time needed to
complete the activities with TEST_PRIORITY of each element assigned to
the current programmer, PR_PTR. It then adds this time to the total
time the programmer works and to the total number of hours needed to
complete the element, ELE_PTR.hours_to_complete. It also calculates
the date this amount of work will be completed. The completion date
is stored in the element field, DATE_DONE.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
Page 21
6.3.4 GROUP_DATA_FIXES -
OVERVIEW:
This procedure is the driver for making changes to the entire set
of element data. Two types of changes are possible, updating the
original estimate to equal the current estimate or starting the
project at this point and using this run as the starting point for the
project.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.3.4.1 RESET_DATA -
OVERVIEW:
For each element, this procedure calculates the amount of work
completed and stores this value in the SIZE_DONE_AT_START field.
After this calculation, it erases the percent complete field in the
element by setting it equal to " ".
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
NOTES:
The SIZE_DONE_AT_START is equal to the old SIZE_DONE_AT_START
plus any work that has been completed since the start of the project.
This means that the data can be 'reset' or 'restarted' as many times
as necessary with no loss in accuracy.
6.3.4.2 UPDATE_ORIGINAL -
OVERVIEW:
This procedure walks through the element data and for each
element sets the original size estimate equal to the current size
estimate.
Page 22
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.4 WRITE_DATA_TO_FILE
OVERVIEW:
This procedure writes all of the tracker data to a text file by
calling the save procedures of each data type in a specified order.
If the file already exists, then the output text file is a new VAX_VMS
version of any existing tracker input file.
The information is stored in a sequential text file. All of the
data is read in at the beginning of the program, manipulated, and then
written back out to the new file.
The data is stored in the file in the following order:
+-----------------------+
| Global Data |
+-----------------------+
| Activity Data |
+-----------------------+
| Milestone Data |
+-----------------------+
| Personnel Data |
+-----------------------+
| Subsystem Data |
+-----------------------+
| Element Data |
+-----------------------+
EXCEPTIONS HANDLED:
name_error tracker file can't be created, raised to calling
routine
HISTORY:
Written by May Lee March 1985
6.5 DATA_MENU_DRIVER
Page 23
OVERVIEW:
This procedure gets all the TRACKER data by controlling the
printing of the data menus, and resolving the selections to those
menus.
The data menu displays different types of data. When a data type
is chosen, an operations submenu appears, which allows the user to
manipulate the data. Since the only operation that can be performed
on global data is modification, the user is prompted for the new data,
which is assigned directly to the global variable rather than calling
a modify procedure in global_data.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.6 GET_DATA
OVERVIEW:
The user is asked whether or not he has an existing TRACKER file.
This procedure either calls INITIALIZE_TRACKER_DATA if the user does
not have an existing TRACKER file, or calls SET_UP_TRACKER_DATA if the
user does have a file.
EXCEPTIONS HANDLED:
name_error raised to the calling procedure
ERROR_IN_INPUT_FILE raised to the calling procedure
others indicates invalid user response so user reprompted
HISTORY:
written by May Lee March 1985
6.7 GLOBAL_PKG
OVERVIEW:
This package defines the global data and the actions that can be
performed on them.
Page 24
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.7.1 GL_INITIALIZE -
OVERVIEW:
This procedure prompts for global data by calling the Prompt_Pkg
functions, which returns valid data only.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.7.2 GL_SET_UP -
OVERVIEW:
This procedure sets up the global variables read in from an input
file. The global data line is read in from the input file, and broken
down into the respective global variables. The data is read in the
order specified by the GL_SAVE procedure.
EXCEPTIONS HANDLED:
others error reading the global data
. raises ERROR_IN_INPUT_FILE
HISTORY:
written by May Lee March 1985
6.7.3 GL_SAVE -
OVERVIEW:
This procedure will save the global data to an output file. The
global data is composed of different types of variables. The
variables are written to the first line of the output file in the
following format:
Page 25
+--------------+--------+---------------+--+--+----+--+--+--+--+----+
| project_name |proj_num| manager_name |mo|dy| yr |ac|ms|pr|ss| el |
+--------------+--------+---------------+--+--+----+--+--+--+--+----+
See DATA_PKG for the full names and types of each variable.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8 ACTIVITY_PKG
OVERVIEW:
This package defines the actions that can be performed on an
activity (defined in DATA_PKG).
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.1 AC_ADD -
OVERVIEW:
This procedure sets up the record to be added to the list by user
prompt/response. The prompts are called from the Prompt_pkg, which
returns a valid response. The complete record is then added to the
linked list by calling the generic List_pkg procedure ADD.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
Page 26
NOTES:
A check is made to insure that the maximum number of activities
is not exceeded.
The number of activities is incremented in this procedure.
6.8.2 AC_INITIALIZE -
OVERVIEW:
This procedure is called only when a new TRACKER file has to be
created. It is part of a forced user response to fill in the
necessary data to make TRACKER a complete report. The procedure
AC_ADD is called to gather the information and put it into a linked
list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.3 AC_SET_UP -
OVERVIEW:
This procedure is only called if there is an existing input file.
The activity record is read from the input file by calling AC_READ.
Each record is added to the linked list by calling the generic
List_Pkg procedure ADD until there are no more activity records.
EXCEPTIONS HANDLED:
others Error reading the record from the file.
. This exception raises ERROR_IN_INPUT_FILE.
HISTORY:
written by May Lee March 1985
NOTES:
The number of activities records read in is determined by the
global variable num_of_activities.
If an error is detected reading the data, the rest of the input
line is skipped and reading the rest of the data continues. All
errors found are reported. Execution is not terminated until the
Page 27
entire input file has been read.
6.8.3.1 AC_READ -
OVERVIEW:
This procedure reads a record from the file. One line of data is
read at a time and broken down into the fields of the activity record,
which is made visible to the calling routine AC_SET_UP. The data is
read in the format specified by the AC_WRITE procedure.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
Any exceptions raised here are handled by AC_SET_UP.
6.8.4 AC_DELETE -
OVERVIEW:
This procedure is used to delete a record from the list by
calling the generic procedure DELETE. The user is prompted for an
existing activity to delete by a call to Prompt_pkg. When an activity
is deleted, its completeness information, which is stored as a field
in the element record, must also be deleted by calling the procedure
DELETE_AC_COMPLETENESS.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of activities is decremented if the delete is
successful.
A check is made to insure the last activity is not deleted.
There must be at least one activity at all times.
Page 28
6.8.4.1 DELETE_AC_COMPLETENESS -
OVERVIEW:
This procedure is called when an activity is deleted from the
activity list. When an activity is deleted, the element list is
walked and the activity completeness is deleted in each element to
account for the missing activity. Since the activity completeness is
stored as an array in a field of the element, the array cell
corresponding to the number of the activity in the activity list is
deleted. The remaining array cells are moved up one cell space. The
number of the cell to be deleted is ac_number.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.4.2 DELETE_SS_TASK_NUM -
OVERVIEW:
This procedure is called when an activity is deleted from the
activity list. When an activity is deleted, the subsystem list is
walked and the task number associated with that activity is deleted
from each subsystem's task number field array. Since the task number
is stored as an array in a field of the subsystem, the array cell
corresponding to the number of the activity in the activity list is
deleted. The remaining array cells are moved up one cell space. The
number of the cell to be deleted is ac_number.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.4.3 DELETE_MULTIPLE_PEOPLE -
OVERVIEW:
This procedure is called when an activity is deleted from the
activity list. The element list is walked. If it is a multiple
person element, the person's inititals associated with that activity
is deleted from that element record's people_initials variant field.
Since the person's initials are stored as an array, the array cell
Page 29
corresponding to the number of the activity in the activity list is
deleted. The remaining array cells are moved up one cell space. The
number of the cell to be deleted is ac_number.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.5 AC_MODIFY -
OVERVIEW:
This procedure allows the user to modify an existing record. The
user is prompted for an existing activity record by calling the
appropriate Prompt_Pkg function. The generic FIND is used to get the
record. The user is then allowed to change the fields by choosing a
menu selection. The record fields are modified directly. If the
activity name is modified, MODIFY_AC_KEY is called.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.5.1 MODIFY_AC_KEY -
OVERVIEW:
This procedure is called if the activity name is modified. The
name must be changed in the list search key by calling the List_pkg
procedure CHANGE_LIST_KEY, as well as in the record data.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
Page 30
6.8.6 AC_SAVE -
OVERVIEW:
This procedure saves a record to file by calling the AC_WRITE
procedure. The generic procedures START_WALK and WALK are called to
walk the linked list allowing one record at a time to be written.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.8.6.1 AC_WRITE -
OVERVIEW:
This procedure is passed in a record pointer. The record is
written to one line of the output file in the following format:
+----------+-----+--+----+-----+
| name |p_tot|pr|cons|pc_st|
+----------+-----+--+----+-----+
See DATA_PKG for the full names of the fields and their types.
The activity records are the second type of data to be written to the
output file.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.9 MILESTONE_PKG
OVERVIEW:
This package defines the actions that can be performed on
milestone data types (defined in DATA_PKG).
Page 31
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.9.1 CHANGE_MS_IN_EL -
OVERVIEW:
This procedure is called when a milestone is deleted from or
modified in the milestone list. Before either of these actions can be
taken, the element list that contains milestones with the same number
is walked. This list is a field of the milestone data record. The
milestone number field of each element record is reassigned the new
milestone number.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.9.2 MS_ADD -
OVERVIEW:
This procedure sets up the record to be added to the list by user
prompt/response. The function calls to Prompt_Pkg return only valid
existing data. The complete record is then added to the linked list
by calling the generic list procedure ADD.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of milestones is incremented in this procedure.
Page 32
6.9.3 MS_INITIALIZE -
OVERVIEW:
This procedure is called only when a new TRACKER file has to be
created. It is part of a forced user response to fill in the
necessary data to make TRACKER a complete report. The procedure
MS_ADD is called to gather the information and put it into a linked
list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The user is forced to add at least one milestone record and then
is prompted to add another or not.
6.9.4 MS_SET_UP -
OVERVIEW:
This procedure is only called if there is an existing input file.
The milestone list is set up by reading the milestone record from the
input file by calling MS_READ, and adding it to the linked list by
calling the generic procedure ADD until there are no more milestone
records.
EXCEPTIONS HANDLED:
others Error reading the record from the file.
. This exception raises ERROR_IN_INPUT_FILE.
HISTORY:
written by May Lee March 1985
NOTES:
The number of milestone records read in is determined by the
global variable num_of_milestones.
If an error is detected reading the data, the rest of the input
line is skipped and reading of the rest of the data continues. All
errors found are reported. Execution is not terminated until the
entire input file has been read.
Page 33
6.9.4.1 MS_READ -
OVERVIEW:
This procedure reads a record from the file. One line of data is
read at a time and broken down into the fields of the milestone
record, which is made visible to the calling routine MS_SET_UP. The
data is read in the format specified by the MS_WRITE procedure.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
Any exceptions raised here are handled by MS_SET_UP.
6.9.5 MS_DELETE -
OVERVIEW:
This procedure is used to delete a milestone from the list by
calling the List_Pkg procedure DELETE. When a milestone is deleted
from the milestone list, the milestone number must also be changed in
every element to which it belonged by calling the procedure
CHANGE_MS_IN_EL.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of milestones is decremented after the record is
deleted.
A check is made to insure the last milestone is not deleted.
There must be at least one milestone at all times.
6.9.6 MS_MODIFY -
Page 34
OVERVIEW:
This procedure allows the user to modify an existing milestone
record. The user is prompted for an existing milestone record by
calling the appropriate Prompt_Pkg function. The generic FIND is used
to get the record. The user is then allowed to change the fields by
choosing a menu selection. The record fields are modified directly.
When a milestone number is modified in the milestone record, the
milestone number must also be changed in every element to which it
belonged by calling the procedure MODIFY_MILESTONE_KEY.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.9.6.1 MODIFY_MILESTONE_KEY -
OVERVIEW:
This procedure is called when the milestone number is modified.
The user is prompted for a new unique key by calling the Prompt_Pkg
function. The milestone number must be changed in the milestone
record, the search key for the milestone list, and the field of the
element record for each element in the milestone's element list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.9.7 MS_SAVE -
OVERVIEW:
This procedure saves a record to file by calling the MS_WRITE
procedure. The generic procedures START_WALK and WALK are called to
walk the linked list allowing one record at a time to be written.
EXCEPTIONS HANDLED:
none
Page 35
HISTORY:
written by May Lee March 1985
6.9.7.1 MS_WRITE -
OVERVIEW:
This procedure references the current record pointer. The record
is written to one line of the output file in the following format:
+--+--+--+--+----+-------------------------+
|ms|cp|mm|dd|year| description |
+--+--+--+--+----+-------------------------+
See DATA_PKG for the full names of the fields and their types. The
milestone records are the third type of data to be written to the
output file.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.10 PERSONNEL_PKG
OVERVIEW:
This package defines the actions that can be performed on a
personnel type (defined in DATA_PKG).
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.10.1 CHANGE_PR_IN_EL -
OVERVIEW:
Page 36
This procedure is called when a person is deleted from or
modified in the personnel list. Before either of these actions can be
taken, the element list that contains people with the same name is
walked. This list is a field of the personnel data record. The
person's initials field of each element record is reassigned the new
person.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.10.2 PR_ADD -
OVERVIEW:
This procedure sets up the record to be added to the list by user
prompt/response. The function calls to Prompt_Pkg return only valid
existing data. The complete record is then added to the linked list
by calling the generic list procedure ADD.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of people is incremented in this procedure.
6.10.3 PR_INITIALIZE -
OVERVIEW:
This procedure is called only when a new TRACKER file has to be
created. It is part of a forced user response to fill in the
necessary data to make TRACKER a complete report. The procedure
PR_ADD is called to gather the information and put it into a linked
list.
EXCEPTIONS HANDLED:
none
Page 37
HISTORY:
written by May Lee March 1985
NOTES:
The user is forced to add at least one person record and then is
prompted to add another or not.
6.10.4 PR_SET_UP -
OVERVIEW:
This procedure is only called if there is an existing input file.
The people list is set up by reading the personnel record from the
input file by calling PR_READ, and adding it to the linked list by
calling the generic procedure ADD until there are no more people
records.
EXCEPTIONS HANDLED:
others Error reading the record from the file.
. This exception raises ERROR_IN_INPUT_FILE.
HISTORY:
written by May Lee March 1985
NOTES:
The number of people records read in is determined by the global
variable num_of_people.
If an error is detected reading the data, the rest of the input
line is skipped and reading of the rest of the data continues. All
errors found are reported. Execution is not terminated until the
entire input file has been read.
6.10.4.1 PR_READ -
OVERVIEW:
This procedure reads a record from the file. One line of data is
read at a time and broken down into the fields of the personnel
record, which is made visible to the calling routine PR_SET_UP. The
data is read in the format specified by the PR_WRITE procedure.
EXCEPTIONS HANDLED:
none
Page 38
HISTORY:
written by May Lee March 1985
NOTES:
Any exceptions raised here are handled by PR_SET_UP.
6.10.5 PR_DELETE -
OVERVIEW:
This procedure is used to delete a record from the list by
calling the List_Pkg procedure delete. When a person is deleted from
the personnel list, his initials also have to be changed in every
element to which he belonged in the element list by calling the
procedure CHANGE_PR_IN_EL.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of people is decremented after the record is deleted.
A check is made to insure that the last person is not deleted.
There must be at least one person at all times.
6.10.6 PR_MODIFY -
OVERVIEW:
This procedure allows the user to modify an existing person
record. The user is prompted for an existing person record by calling
the appropriate Prompt_Pkg function. The generic FIND is used to get
the record. The user is then allowed to change the fields by choosing
a menu selection. The record fields are modified directly. When a
person's initials are modified in a personnel record, his initials
also have to be changed in every element to which he belonged in the
element list by calling the procedure MODIFY_PERSONNEL_KEY.
EXCEPTIONS HANDLED:
none
Page 39
HISTORY:
written by May Lee March 1985
6.10.6.1 MODIFY_PERSONNEL_KEY -
OVERVIEW:
This procedure is called when the person's initials are modified.
The user is prompted for a new unique key by calling the Prompt_Pkg
function. The person's initials must be changed in the person's
record, the search key for the personnel list, and the field of the
element record for each element in the person's element list.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.10.6.2 MODIFY_START_STOP_DATE -
OVERVIEW:
This procedure is called when a pair of start/stop dates is to be
modified for a person. The user is prompted for a new set of dates by
calling the Prompt_Pkg.date function. The date is then compared to
others start/stop dates to see if it is valid. If not, the user is
reprompted. If any start/stop date is assigned a null value, the
other future start/stop dates will be modified to also be a null date
as needed.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
Written by Bonnie Burkhardt March 1985
6.10.7 PR_SAVE -
OVERVIEW:
Page 40
This procedure saves a record to file by calling the PR_WRITE
procedure. The generic procedures START_WALK and WALK are called to
walk the linked list allowing one record at a time to be written.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.10.7.1 PR_WRITE -
OVERVIEW:
This procedure references the current record pointer. The record
is written to one line of the output file in the following format:
+--------------------+--+-----+--+-----+----+-----+----+-----+----+
| name |in| rate|hr|start|stop|start|stop|start|stop|
+--------------------+--+-----+--+-----+----+-----+----+-----+----+
See DATA_PKG for the full names of the fields and their types. The
personnel records are the fourth type of data to be written to the
output file.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.11 SUBSYSTEM_PKG
OVERVIEW:
This package defines the actions that can be performed on a
subsystem (defined in DATA_PKG).
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
Page 41
6.11.1 SS_ADD -
OVERVIEW:
This procedure sets up the record to be added to the list by user
prompt/response. The function calls to Prompt_Pkg return only valid
existing data. The complete record is then added to the linked list
by calling the generic list procedure ADD.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of subsystems is incremented in this procedure.
6.11.2 SS_INITIALIZE -
OVERVIEW:
This procedure is called only when a new TRACKER file has to be
created. It is part of a forced user response to fill in the
necessary data to make TRACKER a complete report. The procedure
SS_ADD is called to gather the information and put it into a linked
list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The user is forced to add at least one subsystem record and then
is prompted to add another or not.
6.11.3 SS_SET_UP -
OVERVIEW:
This procedure is only called if there is an existing input file.
The subsystem list is set up by reading the subsystem record from the
input file by calling SS_READ, and adding it to the linked list by
Page 42
calling the generic procedure ADD until there are no more subsystem
records.
EXCEPTIONS HANDLED:
others Error reading the record from the file.
. This exception raises ERROR_IN_INPUT_FILE.
HISTORY:
written by May Lee March 1985
NOTES:
The number of subsystem records read in is determined by the
global variable num_of_subsystems.
If an error is detected reading the data, the rest of the input
line is skipped and reading of the rest of the data continues. All
errors found are reported. Execution is not terminated until the
entire input file has been read.
6.11.3.1 SS_READ -
OVERVIEW:
This procedure reads a record from the file. One line of data is
read at a time and broken down into the fields of the subsystem
record, which is made visible to the calling routine SS_SET_UP. The
data is read in the format specified by the SS_WRITE procedure.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
Any exceptions raised here are handled by SS_SET_UP.
6.11.4 SS_DELETE -
OVERVIEW:
OVERVIEW:
Page 43
This procedure is used to delete a subsystem from the list by
calling the List_Pkg procedure DELETE. When a subsystem is deleted
from the subsystem list, the subsystem number must also be changed in
every element to which it belonged by calling the procedure
CHANGE_SS_IN_EL.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of subsystems is decremented after the record is
deleted.
A check is made to insure that the last subsystem is not deleted.
There must be at least one subsystem at all times.
6.11.5 CHANGE_SS_IN_EL -
OVERVIEW:
This procedure is called when a subsystem is deleted from or
modified in the subsystem list. Before either of these actions can be
taken, the element list that contains subsystems with the same name is
walked. This list is a field of the subsystem data record. The
subsystem name field of each element record is reassigned the new
subsystem.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.11.6 SS_MODIFY -
OVERVIEW:
This procedure allows the user to modify an existing record. The
user is prompted for an existing subsystem record by calling the
appropriate Prompt_Pkg function. The generic FIND is used to get the
record. The user is then allowed to change the fields by choosing a
menu selection. The record fields are modified directly. When a
subsystem name is modified in the subsystem record, the subsystem name
Page 44
must also be changed in every element to which it belonged by calling
the procedure CHANGE_SS_IN_EL.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.11.7 SS_SAVE -
OVERVIEW:
This procedure saves a record to file by calling the SS_WRITE
procedure. The generic procedures START_WALK and WALK are called to
walk the linked list allowing one record at a time to be written.
EXCEPTIONS HANDLED:
none
HISTORY:
Written by May Lee March 1985
6.11.7.1 SS_WRITE -
OVERVIEW:
This procedure is passed in a record pointer. The record is
written to one line of the output file in the following format:
+----------+-----+--------------+
| name | prct| task_numbers | ...
+----------+-----+--------------+
^
|___ varies from 1..num_of_activities
See DATA_PKG for the full names of the fields and their types. The
subsystem records are the fifth type of data to be written to the
output file.
EXCEPTIONS HANDLED:
none
Page 45
HISTORY:
Written by May Lee March 1985
6.12 ELEMENT_PKG
OVERVIEW:
This package defines the actions that can be performed on element
data types (defined in data_pkg).
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.12.1 ADD_RECORD_TO_LISTS -
OVERVIEW:
This procedure is called by EL_SET_UP and EL_ADD. It adds the
element record to every data's element list by calling the List_Pkg
procedures FINDto find the record and return the pointer and ADD to
append the record to the list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The pointer to the current element record is passed as a
parameter.
6.12.2 EL_ADD -
OVERVIEW:
This procedure sets up the record to be added to the list by user
prompt/response. The function calls to Prompt_Pkg return only valid
existing data. The complete record is then added to the linked list
Page 46
by calling the procedure ADD_RECORD_TO_LISTS.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The number of elements is incremented if the element has been
successfully added to all the necessary data lists.
6.12.3 EL_INITIALIZE -
OVERVIEW:
This procedure is called only when a new TRACKER file has to be
created. It is part of a forced user response to fill in the
necessary data to make TRACKER a complete report. The procedure
EL_ADD is called to gather the information and put it into a linked
list.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The user is forced to add at least one element record and then is
prompted to add another or not.
6.12.4 UPDATE_CURRENT -
OVERVIEW:
This procedure walks through a group of elements and asks the
user to update the current size estimate. If no change is desired,
the user presses <cr>. Otherwise he enters the new value for current
size.
EXCEPTIONS HANDLED:
none
Page 47
HISTORY:
written by Bonnie Burkhardt March 1985
6.12.4.1 FIX_EL_SIZE -
OVERVIEW:
This procedure updates the element's current size.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.12.5 UPDATE_PCT_DONE -
OVERVIEW:
This procedure steps through a group of elements and updates the
percent complete estimate.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
written by Bonnie Burkhardt March 1985
6.12.6 EL_SET_UP -
OVERVIEW:
This procedure is only called if there is an existing input file.
The element list is set up by reading the element record from the
input file by calling EL_READ, and adding it to the linked list by
calling ADD_RECORD_TO_LISTS until there are no more element records.
EXCEPTIONS HANDLED:
others Error reading the record from the file.
. This exception raises ERROR_IN_INPUT_FILE.
Page 48
HISTORY:
written by May Lee March 1985
NOTES:
The number of element records read in is determined by the global
variable num_of_elements.
If an error is detected reading the data, the rest of the input
line is skipped and reading the rest of the data continues. All
errors found are reported. Execution is not terminated until the
entire input file has been read.
6.12.6.1 EL_READ -
OVERVIEW:
This procedure reads a record from the file. One line of data is
read at a time and broken down into the fields of the element record,
which is made visible to the calling routine EL_SET_UP. The data is
read in the format specified by the EL_WRITE procedure.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
Any exceptions raised here are handled by EL_SET_UP.
6.12.7 EL_DELETE -
OVERVIEW:
This procedure is used to delete an element record. The user is
prompted to enter an existing element by a call to the Prompt_Pkg
function, which returns a valid key. The element is deleted from each
data's element list to which that element belonged. The element is
then deleted from the element list by calling the List_pkg procedure
DELETE.
EXCEPTIONS HANDLED:
none
Page 49
HISTORY:
written by May Lee March 1985
NOTES:
The number of elements is decremented if the delete is
successful.
A check is made to insure the last element is not deleted. There
must be at least one element at all times.
6.12.8 EL_MODIFY -
OVERVIEW:
This procedure allows the user to modify an existing element
record. The user is prompted for an existing element record by
calling the appropriate Prompt_Pkg function. The generic FIND is used
to get the record. The user is then allowed to change the fields by
choosing a menu selection. The record fields are modified directly.
If the element abbreviation is modified, MODIFY_ELEMENT_KEY is called.
If a change is made to a field that affects another data type, then
checks have to be made to insure that the change is valid. For
example, if the person's initials are changed in the element data,
checks have to be made to make sure that the new initials belong to a
valid pre-defined person. This is taken care of by the Prompt_Pkg,
which only returns valid values.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
written by Bonnie Burkhardt March 1985
6.12.8.1 MODIFY_ELEMENT_KEY -
OVERVIEW:
This procedure is called when the element description
abbreviation is modified. The user is prompted for a new unique key
by calling the Prompt_Pkg function. The element key must be changed
in the element record, the search key for the element list, and the
search key for each data type's element list.
Page 50
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
If an error is detected in finding the element in any of the
data's element list, a message is output to the screen only. There is
no data recovery or termination performed.
6.12.9 EL_SAVE -
OVERVIEW:
This procedure saves a record to file by calling the EL_WRITE
procedure. The user is first asked which date of completion to save
to determine which date to write to the file. The generic procedures
START_WALK and WALK are called to walk the linked list allowing one
record at a time to be written.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.12.9.1 EL_WRITE -
OVERVIEW:
This procedure is passed in a record pointer. The record is
written to one line of the output file in the following format:
+--------------+------+----------+--+--+--+-------+-------+
| description | key | ss_name |pr|ms|pi| bs_ln | sz_st | . . .
+--------------+------+----------+--+--+--+-------+-------+
prev_date date_verif
+-------+---+----------+--+--+----+--+--+----+------+
. . . | cur_sz|com| ac_cmpltn|mo|dy|year|mo|dy|year|mul_pr| . . .
+-------+---+----------+--+--+----+--+--+----+------+
^
this field varies from 1..num_of_activities
Since the element record is variant, the remaining data depends on
Page 51
the value of more_than_one_person.
If true : +--+--+--+
|pr|pr|pr|...num_of_activities -- array of initials
+--+--+--+
If false: +--+
|pr| -- only one initial
+--+
The element records are the last type of data to be written to the
output file. There are no extra spaces between the record fields.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
NOTES:
The boolean value more_than_one_person, is read and written to
the file as an integer (1=true, 0=false). This is due to the problems
with the way Ada reads an enumeration type from a file. The default
width cannot be used if additional data follows the boolean value. If
the width is used to allow for a trailing blank, then the boolean
value can be read, but the following value is incorrect (unless you
account for the blank).
6.13 REPORT_GENERATOR
OVERVIEW:
This procedure controls the report menu and resolves the
selections the user makes, allowing the user to print any combination
of reports.
EXCEPTIONS HANDLED:
end_error invalid user menu response
data_error invalid user menu response
HISTORY:
written by May Lee February 1985
written by Bonnie Burkhardt March 1985
Page 52
6.13.1 CALC_PCT_DONE -
OVERVIEW:
This procedure calculates the percent complete by subsystem and
activity, total percent done by subsystem and activity, total percent
available at start by subsystem and activity, and the total percent
complete on the entire project. The grand total percent done, percent
available at start, and percent complete on the entire project are
also calculated.
The percent complete by milestone is also calculated in a similar
manner.
EXCEPTIONS HANDLED:
others an error message is printed and the execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
NOTES:
The percentage calculations are performed one subsystem at a
time. For each subsystem, its element list is walked and the total
size, total size available at start, and total amount done is
tabulated. Grand total accumulators are also updated from the
subsystem totals. From these totals, the percent complete for the
subsystem and for the entire project is calculated.
6.13.1.1 GET_SS_TOTALS -
OVERVIEW:
This procedure computes the total amount of work, the amount
done, and the amount available at start for a subsystem.
EXCEPTIONS HANDLED:
others error message is printed and execution continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.2 PRINT_COMMENTS -
Page 53
OVERVIEW:
This procedure asks for the name of the comments file and copies
the contents of the comments file to the tracker report file.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.13.3 COMPLETION_DATE_FOR_MS -
OVERVIEW:
This report is a matrix showing the finsh date of each person in
relation to each defined milestone. The personnel are represented on
the x-axis and the milestones on the y-axis. There are four possible
values for a date : "...." means the person is not assigned to any
elements with that milestone, "99/99/99" means the person did not have
enough time to finish his work, "DONE" means the person has completed
all work assigned to him on this milestone, otherwise, a calculated
completion date will appear. The data in the report includes the date
each person will complete a milestone, the latest date each person
will finish all work, the latest date each of the milestones will be
finished, and the date that the milestone is due. If more than 10
people are assigned to the project, the Completion Date for Milestone
report is repeated until all people have been included on a report.
EXCEPTIONS HANDLED:
others error message printed and execution continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.3.1 INIT_DATE_HEADERS -
OVERVIEW:
This procedure initializes all the headers of the completion
dates by milestone report.
EXCEPTIONS HANDLED:
none
Page 54
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.3.2 CALC_DATE_TOTALS -
OVERVIEW:
This procedure calculates the total amount of time left by
MILESTONE and by person.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.3.3 PRINT_A_DATE -
OVERVIEW:
This procedure prints a date to the report_file. The string
"...." is printed for a null date and the string "99/99/99" is printed
for an underflow date. If the date is neither an overflow date or a
null date, the ANY_WORK_LEFT flag is checked to see if this entity is
actually completed (ANY_WORK_LEFT = false), and a "DONE" printed
instead of the actual completion date.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.3.4 PRINT_MS_DATES -
OVERVIEW:
This procedure prints a milestone completion date line. This
line includes the date complete for each person in the range
START_PR..STOP_PR. If a person is not assigned to an element, in the
milestone, a "...." is printed. If there is not enough time for the
person to finish working on the milestone, "99/99/99" is printed. If
the person is finished working on the mileston, "DONE" is printed.
Otherwise the completion date is printed.
Page 55
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.3.5 PRINT_TOT_MS_DATES -
OVERVIEW:
This procedure prints the total milestone completion date line.
This line includes the date complete for each person in the range
START_PR..STOP_PR. If a person is not assigned to an element, a
"...." is printed. If there is not enough time to complete the
milestone, "99/99/99" is printed. If the person is finished, "DONE"
is printed, otherwise the completion date is printed.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.4 ALL_ELMNT_STATUS_REP -
OVERVIEW:
This report lists all of the element data, including the total
original size, the total current size, and the average complexity.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.4.1 INIT_EL_HEADERS -
OVERVIEW:
Page 56
This report initializes the headers for the All Element Status
report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.4.2 PRINT_EL -
OVERVIEW:
This report prints out an element to the report file. If the
element has more than one person assigned to it, one additional line
is printed for each extra person. This line lists only the initials
of the person assigned and the percent complete by activity. If the
person is not assigned to a particular activity, a '*' is printed in
that column.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.5 LIST_BY_MILESTONE -
OVERVIEW:
One report is produced for each milestone which lists all the
elements belonging to that milestone. The element data includes the
remaining man-hours of work to complete each entity, the total
original size, the total current size, the average complexity, and the
total remaining man-hours of work to complete each milestone.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
Page 57
6.13.5.1 INIT_HEADERS -
OVERVIEW:
This procedure initializes all the headers of this List by
Milestone Report.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.5.2 PRINT_AN_ELEMENT -
OVERVIEW:
This procedure prints out an element line. This line of data
includes the remaining man-hours of work to complete this element, the
original size, the current size, the complexity, and the remaining
man-hours of work to completion.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.5.3 PRINT_MS_TOTAL -
OVERVIEW:
This procedure prints out the total statics for a milestone.
This includes the total remaining man-hours of work to complete this
milestone, the total original size, the total current size, and the
average complexity.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
Page 58
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.6 LIST_BY_PERSON -
OVERVIEW:
One report is printed for each person on the project. Each
report lists all the elements assigned to that person. The report
includes information listed in the List by Milestone Report and also
the date each element is due (its milestone due date) and the
calculated finish date for each element. The finish date for each
element was computed previously by CALC_TIME_DONE and stored in the
element data.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.6.1 INIT_PR_HEADERS -
OVERVIEW:
This procedure initializes all the headers of this person report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.6.2 PRINT_PR_ELEMENT -
OVERVIEW:
This procedure prints out an element line. This line includes
the element data plus the remaining man-hours of work to complete this
element, the original size, the current size, the complexity, the
remaining man-hours of work to complete this element, the due date and
the projected completion date.
Page 59
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.6.3 PRINT_PR_TOTAL -
OVERVIEW:
This procedure prints out the total statics for the person. This
includes the total remaining man-hours of work to complete this
milestone, the total original size, the total current size, and the
average complexity.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.7 LIST_BY_SUBSYSTEM -
OVERVIEW:
A separate report is printed for each subsystem. All of the
element data for each subsystem is displayed including the remaining
man-hours of work to complete each element, the total original size,
the total current size, the average complexity, and the total
remaining man-hours of work to complete each subsystem.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.7.1 INIT_SS_HEADERS -
Page 60
OVERVIEW:
This procedure initializes all the headers of this subsystem
report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.7.2 PRINT_SS_ELEMENT -
OVERVIEW:
This procedure prints out an element line. This line includes
the element data, the remaining man-hours of work to complete this
element, the original size, the current size, the complexity, and the
remaining man-hours of work until completion.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.7.3 PRINT_SS_TOTAL -
OVERVIEW:
This procedure prints out the total statics for a subsystem.
This includes the total remaining man-hours of work to complete this
subsystem, the total original size, the total current size, and the
average complexity.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
Page 61
6.13.8 START_PAGE -
OVERVIEW:
This routine starts the next report on a new page and prints the
globalproject data on the report. It then centers the title and
subtitle on the page. After leaving two blank lines, it prints the
headers: HEADER1, HEADER2, and HEADER_LINES.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.9 PARAMETER_DATA_LIST -
OVERVIEW:
This report prints all of the parameter data including global
variables, activity data, milestone data, personnel data, subsystem
data, and the milestone completion sequence.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.10 PERCENT_COMPLETION -
OVERVIEW:
This report actually consists of two separate matrix reports. It
shows the percentage complete of each activity in relation to each of
the subsystems. One report is based on the original size and the
other on the current size. The activities are represented on the
x-axis and the subsystems on the y-axis. The data printed includes
the percent completion of work for each activity by subsystem, the
total percent completion on the contract for each activity and for
each subsystem, the percent available at start for each subsystem and
for each activity, and the percent completion of work for the entire
project for each subsystem and activity.
Page 62
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.10.1 INIT_PCT_HEADERS -
OVERVIEW:
This procedure initalizes the headers for the Percent Complete by
Subsystem Report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.11 REPORTS_PRINTED_LIST -
OVERVIEW:
This procedure is not on the report menu, but is always the last
report printed whenever two or more reports are output. The output of
this report is simply a listing of all the reports printed in the
current TRACKER run.
EXCEPTIONS HANDLED:
none
HISTORY:
written by May Lee March 1985
6.13.12 MILESTONE_SUMMARY -
OVERVIEW:
This report is a two dimensional matrix that presents a summary
of the remaining man-hours of work for each person on the project in
relation to each milestone. The personnel are on the x-axis and the
milestones are on the y-axis. Calculations for man-hours are based
Page 63
upon current work units. The data printed includes remaining
man-hours of work for each person by milestone, total remaining work
in man-hours for each person, total remaining work in man-hours for
each milestone, total remaining work for the entire project (sum of
milestone totals), the percent complete for each milestone, and the
percent complete for the entire project. If more than 10 people are
assigned to the project, the Milestone Summary Report is repeated
listin 10 people at a time until all people have been included on the
report.
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.12.1 INIT_SUMMS_HEADERS -
OVERVIEW:
This procedure initializes all the headers of the MILESTONE
summary report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.12.2 CALC_SUMMS_TOTALS -
OVERVIEW:
This procedure calculates the total amount of time left by
MILESTONE and by person.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
Page 64
6.13.12.3 PRINT_SUMMS -
OVERVIEW:
This procedure prints out a milestone line. This line includes
the amount of time needed to complete the milestone by person, the
total time needed for the milestone, and the milestone's percent
complete.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.12.4 PRINT_SUMMS_TOTALS -
OVERVIEW:
This procedure prints out the milestone totals. This data
includes the total number of man-hours needed for each person to
complete the project, the grand total man-hours left on the project,
and the grand total percent complete on the project.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.13 SUBSYSTEM_SUMMARY -
OVERVIEW:
This report is a two dimensional matrix that presents a summary
of the remaining man-hours of work for each person on the project in
relation to each subsystem. The personnel are displayed on the x-axis
and the subsytems on the y-axis. Man-hour calculations are based on
current work units. The data printed includes remaining man-hours of
work for each person by subsystem, the total remaining work in
man-hours for each person, the total remaining work in man-hours to
complete each subsystem, the total remaining work for the entire
project (sum of subsystem totals), the percent complete for each
subsystem, and the percent complete for the entire project. If more
than 10 people are assigned to the project, the subsystem summary
report is repeated listing 10 people at a time until all people have
been included on a report.
Page 65
EXCEPTIONS HANDLED:
others an error message is printed and execution
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.13.1 INIT_SUMSS_HEADERS -
OVERVIEW:
This procedure initializes all the headers of the subsystem
summary report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.13.2 CALC_SUMSS_TOTALS -
OVERVIEW:
This procedure calculates the total amount of time left by
subsystem and by person.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.13.3 PRINT_SUMSS -
OVERVIEW:
This procedure prints out an subsystem line. This line includes
the the remaining man-hours of work to complete this subsystem by
person, the current percent complete, and the total man-hours required
to complete this subsystem.
Page 66
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.13.4 PRINT_SUMSS_TOTALS -
OVERVIEW:
This procedure prints out a subsystem line. This line includes
the the remaining man-hours of work to complete this subsystem by
person, the current percent complete, and the total man-hours required
to complete this subsystem.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.14 WORK_UNITS_PER_SS -
OVERVIEW:
This report displays the total amount of original and current
size units for each defined subsystem in the project. Total original
and current size for the project are given as summary data at the
bottom of the report.
EXCEPTIONS HANDLED:
others an error message is printed and processing
continues
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.14.1 INIT_SIZE_HEADERS -
OVERVIEW:
Page 67
This procedure initalizes the headers for the Percent Complete by
Subsystem Report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.14.2 CALC_SIZE -
OVERVIEW:
This procedure calculates the total size of a given subsystem and
the earliest and most recent verification date.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.15 DISTRIBUTION_OF_WORK -
OVERVIEW:
This report actually consists of two separate matrix reports. It
shows the total man-hours of work remaining for each activity in
relation to each of the subsystems. One report is based on the
original size and the other on the current size. The activities are
represented on the x-axis and the subsystems on the y-axis. The data
printed includes remaining man-hours of work for each activity by
subsystem, the total remaining work in man-hours for each activity and
for each subsystem, the percent complete for each subsystem, the grand
total remaining work, the grand total percent complete, and the
percentage of the total work remaining on the entire project by
activity.
EXCEPTIONS HANDLED:
others an error message is printed and processing
continues
HISTORY:
written by Bonnie Burkhardt March 1985
Page 68
6.13.15.1 INIT_DIST_HEADERS -
OVERVIEW:
This procedure initalizes the headers for the Percent Complete by
Subsystem Report.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985
6.13.15.2 CALC_SS_WORK -
OVERVIEW:
This procedure calculates the total amount of work left in a
subsystem by activity.
EXCEPTIONS HANDLED:
none
HISTORY:
written by Bonnie Burkhardt March 1985