There are two aspects to quality in software project. One is the quality of product(or service) and the other is the quality of process which produces the product. The quality of process is a source of the quality of product. Therefore, a good quality process has a high possibility to produce a good quality product. From a point of this view, many process management techniques have been proposed. And the standardization is also carried out actively. Software project is a typical example performed with a form of project, and its characteristic is that the project itself has a lot of risks compared with the project in other field. Especially in the development of client/ server system, this characteristic is remarkable and is a cause of decreasing the process quality. In this paper, the flow of the studies and the existing state of the standardization on process management techniques are described. Then focusing on the risk management in client/ server system, its concept and an example of concrete technique are introduced.

View full abstract

It is said that more than the half of the total development effort is expended on the software testing in a large-scale software development. Therefore, the management of fault-detection and -correction activities in the testing phase is very important to develop a highly-reliable software product efficiently and economically. In this paper, we discuss the development results of a new management system. The system incorporates the software testing-management tool which can support the quality/reliability assessment in the testing phase, and the information sharing technology. Five software reliability growth models are built into this tool. Also, by building the database/file-server on an intranet, it can closely cooperate with all projects which progress at the same time. Therefore, the total project management in the software development can be attained.

View full abstract

There have been many issues in terms of software development processes in our company, e.g. our developers tend to work by mainly relying on their experiences in the development processes of new software products. Nothing to say, such works yield many problems such as the oversights of user-requirement and cause the delay of the development process. We have tackled these problems to achieve high-quality of the developed software system and enhance our company's skill on the software development activities, since the improvement of process quality is able to enhance the quality of the products. Before setting about planning the improvement activity for software development processes, we have firstly begun several risk management activities for our development project and made the project succeed by distinguishing the existing and forthcoming risks project during the actual project management. Simultaneously, we have focused on the CMM (Capability Maturity Model) as a guideline for the process improvement activity, and we have actually planned the guideline for the process improvement by aiming at the CMM level 2. At present, we have been trying to use this guideline for some new development projects. Also, we have been introducing several quality indices and a software reliability assessment tool into the software development processes effectively. In this paper, we present the case studies on requirements management and software quality assurance and discuss their effectiveness and improvements.

View full abstract

The software industry in Japan has entered revolution era by downsizing and open stream since 1990. Japanese economics came to serious depression by collapse of bubble economy. The software industry fell into disorder. This paper shows following two proposals and trial reports from the viewpoint of Quality Management and Project Management, by cause analysis for the disorder of the software industry. (1) The framework of software Quality Management System matching to the global standards (2)The hybrid system mixing software factory and project style

View full abstract

Quality of software product is mainly dependent on the influential human factors for software development, and introduction of software faults may be caused in the early development process such as design and coding phases. For improvement of software reliability and productivity, it is necessary to assess and predict software reliability more quickly, and to perform quality improvement actions such as quantitative clarifying and controlling the influence by the human factors to affect software reliability in the early development process. For the software design process, we have already proposed a new conceptual model and the "Taguchi-Method" based approach for analyzing the relationship among human factors and design review quality. On the other hand, based on the method of multiple regression, we have proposed a several software reliability prediction models for predicting the quality of a final product in the early development phase. In this paper, we discuss a new software reliability model to predict the number of faults remaining in the software product at the end of production phase based on the design reviewing characteristics. The result of an experiment shows that the proposed model is meaningful to improve the productivity of software development.

View full abstract