Centralized Control System Software Architecture And Design, Pattern-based Aviation

This paper mainly describes how to design the aviatic centralized control system software's architecture based design patterns, after author gained a solid understanding of aviatic information integrated technology. Nowadays our aviatic communicated system need support information exchange of every communication platform and can control work of all communication platform. System can not only support efficient and fast transmission of all kind of data, but also can realize many systematic function. The study of this information integrated technology is in order to satisfy the requirement above. Our system integrated platform can afford a uniform circumstance of information integration and integration service. Many divided subsystems and devices can work together on this platform, our system can control and manage them. Firstly we analyzed and study the requirement of aviatic communicated field. We found we must enough control and deal with vast data according to firm flow come from all kinds of communicated platform in order to support information exchanging and realize many concurrent function. Along with development and requirement of system many and many devices and subsystems will join, so our system should be extensible. Our project hope that we can develop a uniform and extensible communication manage platform which can satisfy development of system. But our actual development of software can not attain our requirement, include actual and future requirement. Especially if we use ordinary mode of software it can not attain reuse. The main difficult and innovation of this project is that based study of complicated system'structure theory we study and develop system platform, above all we use software design pattern to realize our software architecture. Because designing object-oriented software is hard, and designing reusable object-oriented software is even harder. You must find pertinent objects, factor them into classes at the right granularity, define class interfaces and inheritance hierarchies, and establish key relationships among them. Your design should be specific to the problem at hand but also general enough to address future problems and requirements. You also want to avoid redesign, or at least minimize it. Object-oriented design patterns will make your...