A Study of Efficient and Precise Estimation Method for the System Architecture Design on IT Projects(<Special Issue>Project Planning and Evaluation)

DOI Web Site

Bibliographic Information

Other Title
  • ITプロジェクトにおけるシステム方式設計見積り効率化の検討(<特集>プロジェクトの計画と評価)
  • ITプロジェクトにおけるシステム方式設計見積り効率化の検討
  • IT プロジェクト ニ オケル システム ホウシキ セッケイ ミツモリ コウリツカ ノ ケントウ

Search this article

Abstract

There are many levels of customer requirements for system architecture design. There is only a few description related to the non-functional requirements in the RFP (Request for proposal) or customer requirements specification. As it is not necessarily the case that, all field requirements is included in the RFP or customer requirements specification, we must effort to draw out customer's true needs. In addition, project manager's wealth of experiences is necessary for the proposal of estimated specifications satisfied both customer budget and construction period. If there are insufficiency act of digging up field requirements needs or examination omission at the system architecture design, defects at operation test or high-load performance test may be actualized in lowest process. At the worst case, such situations may be caused postpone of commercial operation or rework of system construction. It is said that 80 percentages of right or wrong of project is decided at the time of estimation or contract. Investigation after receiving RFP is too late for the proposal of efficient and precise estimation minimizing the risks of non-conforming in system operation or deficiency in performance and reliability. It is important that we are prepare in advance standard examination contents of estimation as various templates which incorporate the project's historical data and expert's know-how, and visualize estimated artifact's development effort of assumed artifacts. In this paper, we propose the estimation method of system architecture design using standard estimation templates and validate the effectiveness.

Journal

Keywords

Details 詳細情報について

Report a problem

Back to top