|
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: M T
Length: 18630 (0x48c6)
Types: TextFile
Names: »MANPOWER_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⟧
XDJDE FORMAT=P06PDE,MARGIN=(0.5 IN),END;\f
USERS MANUAL
version 1.0
for
MANPOWER
by
Bonnie Burkhardt
May 9, 1985
Western Division
GTE Government Systems Group
100 Ferguson Drive
Mountain View, CA 94039
\f
Page 2
1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . 2
2.0 USAGE INSTRUCTIONS: . . . . . . . . . . . . . . . . 2
2.1 Change The Parameters . . . . . . . . . . . . . . 2
2.2 Size Of The Project . . . . . . . . . . . . . . . 3
2.3 Schedule Equations . . . . . . . . . . . . . . . . 3
2.4 Write Another Report . . . . . . . . . . . . . . . 4
3.0 SAMPLE OUTPUT . . . . . . . . . . . . . . . . . . . 6
\f
Page 3
1 INTRODUCTION
The Manpower program calculates the amount of effort and the
corresponding time schedule for a project of a specified size. It
plots a series of graphs showing the tradeoffs between effort and
time.
2 USAGE INSTRUCTIONS:
2.1 Change The Parameters
After invoking MANPOWER, the user is asked if the parameters
should be changed. The following prompt is written to the screen:
Would you like to change any of the parameters in the COCOMO equations?
(Y or N -- def=N) :
If the response is 'Y' or 'y', the program prompts the user for
new parameter values as described below. If any other response is
entered or a <ret> is pressed, the program proceeds on to the next
section, "Size of Project".
After determining that the parameters should be changed, each
COCOMO equation (Organic, Semidetached, and Embedded) is displayed on
the screen with the default values of the parameters. The user is
then prompted to fill in the desired parameter values. The parameters
can assume a new value by entering a real number and pressing <ret>,
or they can assume the default value by pressing <ret> only.
The prompt for the Organic equation is as follows:
Enter the value of the parameter (X.X)
(Press <ret> to assume the default value)
Organic MM = 2.400 * KSLOC ** 1.050
TDEV = 2.500 * MM ** 0.380
Enter coefficient of the ManMonth equation
(default = 2.400) :
Enter exponent of the ManMonth equation
(default = 1.050) :
Enter coefficient of the Development Schedule equation
(default = 2.500) :
Enter coefficient of the Development Schedule equation
(default = 0.380) :
\f
Page 4
The Semidetached and Embedded equations are listed below. The
parameters can be changed by responding to a set of prompts similar to
the Organic equation.
Semidetached MM = 3.000 * KSLOC ** 1.120
TDEV = 2.500 * MM ** 0.350
Embedded MM = 3.600 * KSLOC ** 1.200
TDEV = 2.500 * MM ** 0.320
2.2 Size Of The Project
The user will then be prompted for the size of the project. The
following is written to the screen:
Enter # of lines of source code in thousands (XX.X) :
The user then enters the number of lines of code as a real number,
e.g., 0.2 or 2.0.
2.3 Schedule Equations
The user is then prompted to select the mode which best suits the
project in question. The following prompt is written to the screen:
Basic Cocomo Effort and Schedule Equations:
1. Organic
2. Semidetached
3. Embedded
Enter number corresponding to MODE type desired:
The modes, according to Barry W. Boehm, are described as
follows:
1. Organic mode -- Relatively small software teams develop
software in a highly familiar, in-house environment. Most
people connected with the project have extensive experience
in working with related systems within the organization, and
have a thorough understanding of how the system under
development will contribute to the organization's objectives.
2. Semidetached mode -- This mode represents an intermediate
stage between the organic and embedded modes. This means
either an intermediate level of the project characteristic or
a mixture of the organic and embedded mode characteristics.
Any of the following would be characteristic of a
semidetached mode project: 1. The team members all have an
intermediate level of experience with related systems. 2.
\f
Page 5
The team has a wide mixture of experienced and inexperienced
people. 3. The team members have experience related to some
aspects of the system under development, but not others.
3. Embedded mode -- The major distinguishing factor of an
embedded-mode software project is a need to operate within
tight constraints. The product must operate within (is
embedded in) a strongly coupled complex of hardware,
software, regulations, and operational procedures.
2.4 Write Another Report
The last prompt written to the screen is:
Do you want to write another report (Y or N -- def=N):
If the user replies 'Y', the program goes back to the point where the
users is prompted for the size of the project, and repeats. Any
additional reports are appended to the previous one. If the user
replies 'N' or just presses <ret>, the program terminates and the
report generated is located in the file called 'MANPOWER.RPT'.
XDJDE FORMAT=LNDPDE,MARGIN=(0 IN),END;\f
Page 6
3 SAMPLE OUTPUT
Boehm / DeMarco / GTE Estimated Staffing Profiles
lines of source code in thousands (KSLOC) = 50.0000
Man-months of effort (equation from Barry W. Boehm, pg.75, table 6-1) = 239.8654
Most likely delivery time (equation from Barry W. Boehm, pg.75, table 601) = 17.0188
The impossible region (equation from Tom DeMarco, pg.181) = 11.805 months or less
Equation mode type used: SEMIDETACHED
\f
Page 7
Nominal Schedule
--------------------
********** Acceleration rate = 0.014 ***** Peak staffing occurs around month 6.0 **********
Staffing Estimate: Month Est. Staff
----- ----------
24 | * * * 1 6.62286
23 | 2 12.70092
22 | * 3 17.76339
21 | * 4 21.47354
20 | 5 23.66424
19 | * 6 24.34403
18 | * 7 23.67542
17 | * 8 21.93248
16 | 9 19.44815
15 | 10 16.56202
14 | * 11 13.57762
13 | * 12 10.73419
12 | 13 8.19461
11 | * 14 6.04714
10 | 15 4.31707
9 | 16 2.98356
8 | * 17 1.99719
7 | *
6 | *
5 |
4 | *
3 | *
2 | *
1 |
+---------------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Duration (months)
\f
Page 8
EXTENDED SCHEDULE
--------------------
********** Acceleration rate = 0.010 ***** Peak staffing occurs around month 7.1 **********
Staffing Estimate: Month Est. Staff
----- ----------
21 | * 1 4.74957
20 | * * 2 9.21841
19 | * * 3 13.15323
18 | * 4 16.35199
17 | 5 18.68074
16 | * * 6 20.08181
15 | 7 20.57271
14 | * 8 20.23668
13 | * 9 19.20709
12 | * 10 17.64831
11 | 11 15.73599
10 | 12 13.63939
9 | * * 13 11.50756
8 | * 14 9.46038
7 | 15 7.58449
6 | * 16 5.93368
5 | * * 17 4.53248
4 | 18 3.38186
3 | * 19 2.46575
2 | * * 20 1.75732
1 |
+------------------------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Duration (months)
\f
Page 9
COMPRESSED SCHEDULE
--------------------
********** Acceleration rate = 0.020 ***** Peak staffing occurs around month 5.0 **********
Staffing Estimate: Month Est. Staff
----- ----------
29 | * 1 9.40463
28 | * * 2 17.71390
27 | 3 24.04229
26 | 4 27.86849
25 | * 5 29.09715
24 | * 6 28.02121
23 | 7 25.20676
22 | 8 21.34129
21 | * 9 17.08886
20 | 10 12.98490
19 | 11 9.38486
18 | * 12 6.46310
17 | * 13 4.24674
16 | 14 2.66515
15 | 15 1.59880
14 |
13 | *
12 |
11 |
10 |
9 | * *
8 |
7 |
6 | *
5 |
4 | *
3 | *
2 | *
1 |
+---------------------------------------------
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Duration (months)