-
Article type: Cover
2010 Volume 12 Issue 3 Pages
Cover1-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
i-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
ii-v
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
vi-vii
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
App1-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
App2-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Index
2010 Volume 12 Issue 3 Pages
Toc1-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Index
2010 Volume 12 Issue 3 Pages
Toc2-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Kiyohisa Okada
Article type: Article
2010 Volume 12 Issue 3 Pages
1-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Yukio Hoshi
Article type: Article
2010 Volume 12 Issue 3 Pages
2-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Yasuo Kainuma
Article type: Article
2010 Volume 12 Issue 3 Pages
3-6
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
In software development projects, problems are often caused by ambiguous project scope. Especially, the description of the contractual documents tends to become inadequate in the contract with the customer whose experience in software development is insufficient. In these cases the requirements of the customer would not be clearly described in scope statement, and the misunderstanding of the description will cause troubles afterward. To reduce such troubles, it is effective to promote the project by scope definition through the negotiations with the customer. The negotiations include comprehension of the customer's organization and technological level, identification of the key player, description and explanation concerning specification according to the customer's level, and strategy to remove customer's uneasiness.
View full abstract
-
Seiichi Komiya
Article type: Article
2010 Volume 12 Issue 3 Pages
7-12
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
A lot of whether or not a software project is successful depends on management ability of a software project manager and his/her management office. Therefore, EVA (Earned Value Analysis) has received a lot of attention recently, as a project manager can quantitatively measure/analyze the cost and schedule of a software project by using EVA, and manage them in an integrated fashion. Project manages can estimate SEAC (Schedule Estimate At Completion) and EAC (Estimate At Completion) by using EVA. However, as EVA is a method that any managers can not take into consideration the constraints (e.g. the constraints concerning available periods of each resource, etc.) to take into consideration in case of assigning workers for a software project, there are many cases that SEAC can not be exactly estimated by using EVA. Therefore, the author proposes/discusses a new metric for evaluating exactly the situation of project execution, through combining use of the method to estimate EAC by using EVA and the method to estimate SEAC exactly by taking into consideration the constraints.
View full abstract
-
Kazuhiko Komaki
Article type: Article
2010 Volume 12 Issue 3 Pages
13-18
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
When it is going to apply quantitative management to a software development project, it is required to estimate size of the software. It is a function point to be representative as a standard of the scales. It is the IFPUG method to be representative in function point technique. The IFPUG method is the technique that spread widely, but there is the software that a measurement is difficult by the IFPUG method. The function point measurement technique that I can recommend to such a software development project is the COSMIC method. This article introduces the measurement technique of the COSMIC method and a point to keep in mind on applying it.
View full abstract
-
Shoso Yamato
Article type: Article
2010 Volume 12 Issue 3 Pages
19-20
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Masafumi Kobayashi, Taro Shibagaki, Toshikazu Uchibori, Masaaki Nakaga ...
Article type: Article
2010 Volume 12 Issue 3 Pages
21-24
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
[in Japanese], [in Japanese], [in Japanese], [in Japanese], [in Japane ...
Article type: Article
2010 Volume 12 Issue 3 Pages
25-32
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Akiyuki Onaka
Article type: Article
2010 Volume 12 Issue 3 Pages
33-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Committee of International Affairs
Article type: Article
2010 Volume 12 Issue 3 Pages
34-37
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
38-39
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Tuguhito Sumi, Koji Ota
Article type: Article
2010 Volume 12 Issue 3 Pages
40-41
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
[in Japanese], [in Japanese]
Article type: Article
2010 Volume 12 Issue 3 Pages
42-43
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Koji Kuroki
Article type: Article
2010 Volume 12 Issue 3 Pages
44-45
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Jun'ichi Asami
Article type: Article
2010 Volume 12 Issue 3 Pages
46-49
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Hidetaka Nakajima
Article type: Article
2010 Volume 12 Issue 3 Pages
50-51
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Fumikazu Kaneko
Article type: Article
2010 Volume 12 Issue 3 Pages
52-53
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Shoji Tajima
Article type: Article
2010 Volume 12 Issue 3 Pages
54-57
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
58-59
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
60-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
61-63
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
64-65
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
66-67
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Appendix
2010 Volume 12 Issue 3 Pages
App3-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS
-
Article type: Cover
2010 Volume 12 Issue 3 Pages
Cover2-
Published: June 15, 2010
Released on J-STAGE: November 15, 2017
JOURNAL
RESTRICTED ACCESS