On Software Component Development Wu Xudong Outline: 1. The work I have held. 2, development models and selection of fields. 3, the choice of system architecture. 4, multiplexed assets and multiplexed components. 5. Universal Short Message Interface Protocol SORBA. 6, the implementation of components in various environments. 7, support for third-party development. 8, long-term training. 9. Defect in work. Abstract: In the planning and development of a mobile short message value-added application system I have, in the face of mobile short messages, and the ASP in many different industries, huge software development workload. We have chosen component software development, and we have achieved ideal effects in terms of functionality, performance, development efficiency and investment. Text: In October 2000, I started to serve as the person in charge of the mobile short message value-added application system (SMASP) development department in Sichuan, the main job is to plan and implement the development of Smasp development for General Manager. Smasp's communication service provider is China Unicom, service content provider, such as: taxi management company of taxi dispatching system; commercial electrical code company for electric code anti-counterfeiting system; water and electrical three table meter reading system water-electricity company; mobile securities Systems of securities companies, etc., as well as many known and unknown applications where the mobile short message value-added application has potential demand will be added to the SMASP. The first phase of SMASP is applied to China Unicom Sichuan, the second phase of the project will be promoted to Shandong, Henan, Guangdong, Fujian, Hubei and other provinces and cities, and gradually promote the application to national Unicom. Since the project is in its infancy, there is no fixed system model and successful application mode, so choose a good system architecture and development model becomes a top priority. Selection of the field. Usually, a special asset in a field is to be applied to unrelated areas. The primary work of component development is the area engineering, and the system objects that can be reused can be extracted in this field. Create multiple assets, development multiplexing Component. SMASP is just such a facial facility, and the system needs to be continuously upgraded and has long-term continuous development needs. Therefore, in the primary stage of SMASP construction, it is feasible to create multiplexed assets for Smasp and have rewarded. Selection of components (COM) architecture. SMASP has already been built on the Windows / NT server, but considering that this system will be promoted to Unicom's Unicom, future remote system maintenance and remote operation control and system overall performance, I recommend companies to system background The application part is transplanted to the UNIX system mainly based on the Sun system, which has been supported by the company. Our service content providers are a wide range of industries, there are different applications in operation, which is available in Unix, Windows, Windows / NT, Linux, NetWare, etc., is a multi-platform system. In order to select a good architecture and development method for such a multi-platform, multi-application, long-term continuous development, will determine the quality, continuous availability, upgradeable maintenance, scalability, and development of Smasp in future development practices. Items of workload and investment. After repeated consideration, we divide the entire system into individual constituent objects, each object independent work, and each other to complete the functionality of the system, so that individual objects form a system components. In these components, some are common in Smasp, which is functionally stable in the system; there are also a wide range of components that face different ASP (service content providers). The development of these components is relatively independent, mutually disrupt, so the system's unsuccessful evolution can be achieved. Create multiplex assets and multiplexing components. Usually the asset that can be reused is an object that is more versatile in the field. Through in-depth analysis, we decided to establish a short message value-added application system platform MIS Platform.
MIS Platform itself is a multi-level, componentized architecture composed of multiple components, and various applications of ASPs running on him can also view each component of MIS Platform. MIS Platform architecture, detailed definition of each component, interface definition, decentralization specification, a large number of code, and documents of each part are potentially accessible assets. There is a certain difference between multiplexed assets and multiplexed components. The range of multiplex assets is relatively wide, and the multiplexing components are more specific, and it is often referred to as programs that can be embedded directly into the target system or run independently to complete a particular function. Modules or objects. Not all accessible assets can be made into multiplex components, and further refinement after the demultiplexing assets, as we created in MIS Platform, Index Management Components, TCP / IP Communications Components, interface components, encryption components, etc. have good versatility. General interface definition. In component development, since the system is to rely on prefabricated or independently running components to achieve system function targets, the exchange between components will be inevitable, but to successfully exchange information between components, Communication interfaces that define all components can be parsed. In our system, SORBA (Short Message Object Request Agent Structure) assumes this role, and his definition can be identified and parsed in MIS Platform, which becomes a link to work together. The definition of SORBA should take into account the platform, independent of the operating system, independent of the compile system, independent of the development tool, because in this wide range of platforms, we cannot guarantee that everyone can use the same The development tool, even if the development tool is the same, it is impossible to ensure that the data structure of communication is absolutely not changed, so the independence and flexibility of SORBA definition is quite important. Components are implemented under various platforms. Since our system is multi-platform, multiplexing components need to be implemented under multi-platform. At present, everyone discussed much as COM, CORBA, ActiveX et al, Windows can provide the component's implementation as DLL or OLE technology. And I think this understanding is narrow, and the component can be implemented in a variety of ways. In addition to DLL and OLE, in Windows systems, you can also implement static connection, message queue, etc., which can be implemented in Unix, and technologies such as static connection, message queue, shared memory. It can be seen that a message queue is provided on UNIX and Windows (2000 or more versions). The independently running components in the MIS Platform are linked through the message queue. This mechanism is used under UNIX and Windows, such as encrypted components and communication components, short message processing centers and communication components, communication components and ASP application components. Between communication between messages. Embedded components such as basic tables, indexes, Indexes, and SORBA interface protocols are implemented under Unix, and two technologies are used in Windows, and two technologies are used under WINDOWS. Whether it is an embedded component or an independently running component, the multi-platform demand should be considered when implementing, the components should be independent of the development tool, with a high degree of plasticity, and the interface is clear and reliable. Support for third-party development. We can't guarantee that the entire SMASP will always bear all the software development work, MIS Platform provides support for third-party development. Third-party developers have to get the SORBA interface component "DataPack.dll" (under Windows) or "DataPack.Lib" (under Windows or UNIX), and related documentation, they can access MIS Platform, regardless of MIS Platform How to upgrade, no matter what the MIS Platform is available to provide services, our customers do not have to modify their application. Pay attention to training work.
