The Semantic Process System Three-Tier SOA Architecture And Implementation

Most enterprises were overwhelmed by the negative effects brought by the application system's "upgrading and modifying project". It's a major issue for system development and deployment that how to rationally use advanced system development technology and design ideas to develop system efficiently and flexibility, maintain system quickly and easily, reduce the resources waste and development costs, and design a kind of open, flexible and reliable system, which is also the research topic of this paper.Aimed at these existing problems of the system development and deployment, this research proposes a new set of system framework for developing, analyzing and implementing system:the semantic processes system three-tier SOA architecture. This research explains the implementing progress through example, solves problem in which meets, and verify the feasibility of this scheme.Firstly, elucidate the three-tier SOA architecture's core philosophy: "requirement analysis+semantic description+system implementation" Different from the traditional developing methods from business requirement to system implementation, the three-tier SOA architecture exchanges information between the business layer and the system layer through the middle semantic layer. In this way, ensure that the system is loose-coupling and flexible. We can accomplish new business requirement through the semantic appending, semantic extension and semantic description's change.Secondly, elaborate the three-tier SOA architecture's implementation strategy:"identify business processes+analyze business processes+implement business processes".1) Model business by using the BPM (Business Progress Management). Precisely analyze the business requirements through the BPM to identify the business processes, factor out the atomic operations and complete the business modeling.2) Find the system use-cases by decomposing, abstracting, mapping and mergering atomic operations. Get the basic components for system implementation through analyzing the system implementation processes. At last, realize the business processes by calling different basic components. In this way, avoid duplicate development and accomplish the system modeling.3) Establish the ontology models for business model and system model separately. Then build the mapping relation between the atomic operations and the system use-cases. In this way, we can get the whole semantic description from the business requirements to the system implementation.Thirdly, take the deposit system for example to describe in detail the three-tier SOA architecture's concrete implementation:"business modeling+ processes description+explaination and execution".1) Expatiate the practical process of the deposit system's business modeling and system modeling, and decompose the atomic operations and the system basic components. Then, establish the ontology models for business model and system model separately, realizing the semantic description from business requirement to the atomic operations and from the system scenes to the basic components. After this, build the mapping relation between the atomic operations and the system scenes to achieve the semantic expression from the business requirement to the basic components. Consequently, determine the longitudinal system logic relation from business requirement to the basic components.2) The relation model built above is a kind of "grape/tree" model. Analyzing the model with the existing semantic ontology tools, we can only determine these concepts'longitudinal logic relation, but can not laterally describe its leaf nodes'interoperating relation. Therefore this research defines a kind of processes description language compatibility with ontology description language to describe the basic components'lateral logic relation, and express the system control flow and data flow. Based on this, abstract this research's self-define process description language FL7 (Financial Level 7, the Financial Industry Application Layer Protocol) to accomplish the longitudinally and laterally whole semantic expression from business requirement to the system implementation.3) Design a simple workflow engine corresponding with the self-define language. Verify the design result to insure the usefulness of the process language. At the same time, it verifies this architecture's feasibility.In addition, this research summarizes and discusses the semantic process system three-tier SOA architecture's concrete implementation scheme. Propose the scheme of decomposing the basic components to the system implementation layer's atomic components with the above method. Besides, this research analyzes and contrasts the system implementation scheme from the atomic operations to the business requirement and from the atomic components to the business requirement. At last, this research makes a compromise between the "atomic operations" and the "atomic components", sets the basic components at the decomposing results of the system analysis layer. As a result, we can assemble any "basic components", which the system needs, with limited "atomic components" command set. On this basis, combine different "basic components" with semantic description to achieve different business requirement. This combination of "static and fixed" assembling process and "dynamic and variable" combining process, makes the system have good flexibility, stability, reusability, extendibility, loose-coupling and faster response speed.The above semantic processes system three-tier SOA architecture's core philosophy, implementation strategy and concrete implementation combine the theory, technology and advanced philosophy of the SOA, semantic ontology and workflow. Implement the business through the whole semantic description from the business to the basic components and the correspondingly longitudinal and lateral explanation and execution. This architecture is open and flexible, convenient and efficient, reusable and easy maintenance.