The net chamber process is not allowed, it is strictly forbidden to reprint this column This paper is reproduced from the Software Engineering Expert Network www.21cmm.com. Do not reprint without 9CBS, thank you for your cooperation clean room reference model (CRM) by software engineering (Linger and Trammell 1996) proposed that it defines a complete set of processes and work products for the lash project. The following figure shows that CRM consists of 14 independent processes corresponding to software management, specification, development and authentication: 1. The management process includes project planning, project management, performance improvements, and engineering changes. 2, the specification process includes demand analysis, functional specifications, use specifications, usage specifications, structural specifications, and incremental programs. 3. The development process includes software re-engineering, incremental design and correctness verification. 4. The authentication process includes using modeling, test planning, statistical testing and certification. The four management processes in the top of the figure affect all other processes. During the project plan, the team should cut the clipping room process according to the project environment and develop and maintain the software development plan. These planned management and control of incremental development and certification during project management. Performance improvement processes are used to assess project performance, clear and improve improvement. The engineering change process provides configuration management and engineering rules for all possible changes. The structural specification process defines the architecture and strategy across the entire lifecycle. It will affect many aspects of demand to the underlying design. The demand analysis process is an initial definition for user needs. This requirement definition is accurately described in the function specification process (specifications for external behavior) and use specification processes (generating users, usage environments, and software systems using models). Incremental development plans to assign a series of increments for specific software functions, and arrange the development and authentication progress of these increments based on the structure and progress of the project. The development and certification process in the laminated frame on the right side of the figure, these laminated frames represent the increment of successful development. Software Comrade Engineering Processes are used in an increment to prepare existing software. Incremental design and correctness verification process is used to design and encode an increment, and certify its correctness. In parallel with the introduction of models and test planning processes in each increment, and generate test cases from the model. Whether the statistical test and certification process evaluation increment is easy to use. At the end of an increment, the user provides feedback to the operating system and provides feedback for the needs confirmation. Figure net room reference model
