ECBS benefits

Abstract

Organizations will introduce model based ECBS, only when they sell computer intensive products or services which require a system approach. The management will make decisions to utilize ECBS only if they perceive that the costs and risks of training and implementation will pay of well enough to impact the performance of their organization. ECBS must do the computer system job better, reduce risk, save money in product or service development, and better match product to marketplace. This can happen because the ECBS process works better and is much more efficient and cost effective than the present lack of ECBS and use of vernacular text. This paper describes the benefits of ECBS and estimates the magnitude of improvement possible by reducing the work of creating requirements, tracing them, creating designs, calculating system performance of designs, transforming information for design engineering and management, evaluating requirements changes, and generating test and validation scenarios.