Design of Embedded Systems

Small and medium enterprises have a lot of things to take care of, and it is too late to save fire every day. What iterative improvements do they need? Especially self-reliant companies, in addition to a bunch of old products to be maintained, there are also a bunch of product features to be developed. How can this problem be solved? All day, R & D personnel are exhausted. It is difficult to sum up with the mood and time. This causes the problem to be inherited from a version to the next version, and the bug is transmitted from generation to generation.

You have to be careful about similar projects. Summary:

1. Simplify the business model through rational design. We used to design a RTOS system project. In the original design, dozens of semaphores were used in large and small sizes. By thoroughly understanding the project requirements, we can re-optimize the design and reduce the number of semaphores to less than 10. This greatly reduces the complexity of system synchronization and the possibility of errors. In addition, the reduction in synchronization requirements is actually a reduction in the degree of coupling between modules, reducing the direct benefits and greatly reducing the difficulty of debugging and development. The next advantage is the improvement of project delivery quality.

2. The process is an organic combination of tools, methods, technologies and people. The key to this integration process is people. The quality and pattern of people determine many things. A friend once told me today that the quality of software has been tested. I do not think so. quality should be a people's war. Imagine that the quality of writing for programmers is very bad. A bunch of problems are delivered to QA. Can QA test cases cover all problems? Even if it can be covered, a bunch of problems are pushed back to R & D, and R & D and re-engineering, which is a bunch of problems. Slow convergence speed. QA faces a lot of problems and limited development time. Only major test cases can be selected for testing. In this way, how can we ensure the final quality? Besides, QA test cases also have a development process, and it is impossible to test all the problems. Therefore, the eyes of the masses are bright.

Improve the quality of personnel in each link from the perspective of needs. Brainstorm, do not throw the problem to QA, and reduce the burden on the brothers. Improve the combat capability of the entire team.

3. to shorten the time for a project, it is necessary to make rational use of resources. Resources in many enterprises cannot be reused, and the efficiency is low. You can start with some core resources, such as establishing a unified business platform. For example, for companies that use RTOS, a set of RTOS is definitely not enough. For high-end products, good systems may be used, and low-end systems may be used. The Code may need to maintain two sets. You can build a compatible library or a central library to achieve compatibility with the two systems. The central database is added slowly to abstract standard business models and perform rigorous tests on the premise of reliability and universality. It can greatly shorten the project delivery cycle. A unified R & D process and a unified development method can avoid possible risks in the next project.

It is not always easy to use CMMs. Cmme itself is only a process guide and does not involve detailed operations. In addition, in practice, due to the unfamiliar and misinterpretation of CMMS, this waste has little effect. Some good methods can be extracted from CMMI to gradually implement the solution, focusing on stability, and gradually improving iteration.