Quality Control of Real Time Control Software (1)
Chen Zigi (reproduced from the computer world network)
How to ensure the quality of embedded real-time control software? How to effectively quality control for the production process of such software? This is an important research topic. Subsequent software engineering to solve the software crisis successfully solve many problems in software development. It not only has a direct impact on software development, design and production, but also has a significant effectiveness of improving software quality. Practice shows that the use of software engineering methods can achieve general quality requirements. However, when the software quality requires higher requirements, some special reliability engineering techniques and methods must be taken while implementing software engineering to ensure the reliability of demand. Software engineering refers to the production and development of software in accordance with the laws of the project. Software engineering requirements are based on software quality control as the core, closely seize 8 main links such as software production methods, demand analysis, software design, software production tools, test, verification and confirmation, review and management (Figure 1). Software production method software is a product. From the sense of the product, the so-called software development should be software production. The software should be produced by engineering, structured and standardized methods. Software engineering refers to the use of software engineering to standardize all activities in the software development process. Hardware production has a mature engineering method, software should learn to hardware, harden the software, and regard the software as a product in a software factory. Software standardization refers to software production activities must strictly follow various software specifications and standards in software survival cycles. Experience has proved that there is no product without a standard, and there is no software. The implementation specification must be real. The implementation of the standard work is somewhat (the workload is mainly in document, review, verification, review, and management), but benefit is obvious. Since the software development process specification has improved software quality, it is not only reduced losses, but also promotes the production of software, and improves software productivity. Software structure means structural analysis and structured design methods during software production. The purpose of software demand analysis software demand analysis is to make software designers and users to communicate with users to clarify what software needs to be in the user. The main contents of the need to communicate are: the concepts, definitions, objects, indicators, functions, control logic, algorithms, environment, timing, execution processes, and characteristics of the software will be developed. Software specifications generated by demand analysis is the basis of this subsequent software design, debugging, and testing, is one of the basis for software review, identification, and acceptance. Therefore, demand analysis is a primary step in software production. A software specification manual quality, on the one hand, depending on the extent to which the analysis is needed, on the other hand, depending on the correctness, integrity, rationality, and consistency of the system analysts. It is well known that software is afraid of modification, more afraid of demand changes. The reason is that the software modification works greatly, any modification of key software, must experience a debugging, test, verification and confirmation step. · The cost of spending high, the software passed by the test, and changed the software demand, even if only one parameter is changed, it also needs to repeat the changes to the changed software. Some real-time control systems have a considerable price. · The software modification involves wide, often there is a problem of moving the whole body. In particular, systems consisting of multiple divided systems (eg, military command C3i systems), any of the modifications should consider whether there will be other divided systems. Software reliability demand analysis requires comprehensive, meticulous and in-depth. It is not difficult to see that the process of software demand analysis is also the brewing process of software design. The conclusions of the correctness, rationality and integrity of the user needs should be obtained; at the same time, the feasibility, reliability, and security conclusions should also be obtained. The connection between software demand analysis is shown in Figure 2. Software design software is also the same as hardware, and its quality is designed, produced. Among them, design is a critical impact on software quality.
