(c) 2008 Japan Users Association of Information Systems
1
Study on standard manufacturing schedule
・
We analyzed interrelation between number of man-months and manufacturing term from the beginning of
project to cut-over about 203 system development projects and reached the conclusion that standard
manufacturing term was third root of number of man-months times 2.4.
・
We did not calculate correct values of ‘a ‘and ‘b’ of formula, i.e. ‘manufacturing term’ = ‘a’ x (number of man-months) ‘b’
multiplier, from distribution chart and did not get difficult expression. We got preferably plain formula and with it user and
vender can easily calculate number of man-months and manufacturing term in there meeting.
工期-工数グラフ
0 5 10 15 20 25 30 35 40 45 0 2.5 5 7.5 10 12.5 15全体工数
全体工期
100人月
15人月
400人月
1000人月
2000人月
3000人月
Y
＝２
.
４
X
T otal manufacturing term
Total no. of man-months
Assessment measure of manufacturing term and action
z
Important points about
manufacturing term (from specification definition phase to cut-over)
Same as left items
+
Management by super project manager
and full backup and control by total
company
Scheduling with PERT method
Assignment of the best member
‘
Clean room
’
method
Arrangements in two-shift system
Forming customer-oriented test team
Utilization of system packages
Re-utilization of system parts
Same as left items
+
Assignment of good
programmers
Partial cut-over in
function or works
division
RAD + DOA
System performance
test in advance
Complete control of
specification changes
Total planning by
WBS and
phase-oriented system
development
methodology
Reviewing
completely
Rich test cases
Full utilization of
converted data
Sure control of
specification
Quality-oriented
test planning and
elaborate plan of
test cases
Split step cut-over
for stable operation
Other
countermeas
ure
To enhance short range scheduling (Daily
control)
To enhance middle
range scheduling
(Weekly Control)
To enhance middle
range scheduling
(Control of WBS by
division of roles)
To secure enough
time for system
tests
Countermeasur e by scheduling method
System development under unavoidable circumstances (Strategy of competition, sale of new products, putting on market, company integration and so on)
User’s request
Many cases in distribution industry
‘Cube root of number of man-months’ x 2.4 (For example: 1000 man-month project takes 24 month term)
Quality-oriented and no defect project such as banking system Basic concepts
about manufacturing term
Shortening term by more than 25% Shortening 25% term
Standard term Longer term than
(c) 2008 Japan Users Association of Information Systems
3
Productivity index
This chart shows several kinds of productivity index that were find out from under 1000
man-month projects.
They differ from kind of operation, kind of industry and degree of quality required. Therefore
they need to accumulate results and find out their own standard value.
51
107
46
107
155
Number of
data
12.6
（
0.88
）
87.5
（
0.88
）
116
（
0.98
）
Regression
formula
(Coefficient
of
correlation)
9.93
1.03
11.7
70.4
113
Weighted
average
Productivity
(FP /
man-month)
Productivity
(KLOC /
man-month)
FP unit price
(10 thousand
yen / FP)
KLOC unit
price (10
thousand yen /
KLOC)
Man-month unit
price (10
thousand yen /
man-month)
Unit price by development phase
•
As to unit price by development phase, we received 42 to 50 responses by each development phase.
•
They could be classified into two types. One is the system development that use package software,
as called below ‘package development’, and the other is it that is developed in scratch manner, as
called below ‘scratch-type development’.
Requirement
specification
phase
Designing
phase
Implementation
phase
Test phase
Total unit price
Number of projects
4
4
4
4
7
Maximum value
300.0
250.0
200.0
250.0
250.0
Average value
187.5
160.0
137.5
157.5
142.1
Minimum value
100.0
100.0
100.0
100.0
100.0
Number of projects
36
45
46
45
35
Maximum value
170.0
170.0
170.0
168.0
157.0
Average value
107.9
102.8
84.2
94.5
94.7
Minimum value
60.0
60.0
50.0
55.0
60.0
Number of projects
40
49
50
49
42
Maximum value
300.0
250.0
200.0
250.0
250.0
Average value
115.9
107.5
88.5
99.7
102.6
Minimum value
60.0
60.0
50.0
55.0
60.0
Total
Unit price by phase (10 thousand yen / month)
Package
development
Scratch-type
development
(c) 2008 Japan Users Association of Information Systems
5
JUAS survey report list in 2006
200 pages Evaluation of IT investment value
For polic
y
making
280 pages Survey on state of user’s behavior about IT in 2007 ＊
150 pages Survey on information security governance
500 pages System reference manual : Vol.2 ＊
This will be opened on the HP of IPA. (Total 300 pages) 100 pages
Text book for developing CIO of small-to-medium-sized company
This is included in ‘Survey on software metrics’ To develop ‘Training load map’.
Appendix
100 pages Standard for information system user’s skill ＊
250 pages Survey on software metrics in 2007＊
Report Name of project
Cate gory
100 pages Survey team for sensitive ability of problem and its closure ability
（ＲＳＴ・・Requirement Specification Technology）
Survey team for application of OSS
200 pages Survey project for UVC
150 pages Survey project for usability ＊
Survey project for system development productivity
Surve
y
proj
ect
〃
Study team for how to use IT by users
〃
Study team for management of company information
〃
Study team for system operation
〃
Study team for intelligence sharing
〃
Study team for human resource development
Not for sale Study team for IT policy
Stud
y
team
