Service object modeling method based on service main body characteristic

Abstract

The invention relates to a business object modeling method based on business ontology features, which comprises the steps of creating a syntax database in a business domain model; establishing a specific business architecture model, thinning express the characteristic, behavior, attribute of an object on each layer to obtain a specific domain object business syntax database. By providing a modeling basic syntax for a business domain model, the method lays a foundation for reusability and share of business ontology syntax database in domain software development.

Description

technical field [0001] The present invention relates to the modeling technology of computer, in particular to a business object modeling method and device based on business ontology features. Background technique [0002] At present, the modeling field is mainly dominated by the Model Driven Architecture (MDA) proposed by the Object Management Organization (OMG). UML for short), Meta-Object Facility (MOF for short), eXtensible MarkupLanguage (XML for short), XML-based MetadataInterchange (XMI for short), model query / view / conversion etc. However, there are still serious problems in the practical application of MDA: firstly, the complexity of MDA specification limits its application; secondly, as a general software system modeling method and standard specification, MDA itself has many unsolved problems. There are only a few model conversion methods and tools, and the heterogeneity between them makes it difficult to reuse the model conversion code, and makes learning and lea...

AI Technical Summary

Problems solved by technology

However, there are still serious problems in the practical application of MDA: first, the complexity of the MDA specification is high, which limits its application; Difficulties, such as: model conversion, synchronization between models and codes, etc. At present, there are only a few methods and tools for model conversion. The heterogeneity between them makes it difficult to reuse codes for model conversion, and makes learning and The cost of using the model conversion method increases; and the synchronization problem between the model and the code requires developers to maintain both sides, which also makes the actual application of MDA complicated and difficult; moreover, the mainstream MDA tool currently only has UML, and UML is not suitable for domain-oriented The ability to express individual needs is seriously insufficient

However, the current construction of the N-tier software architecture is not rigorous, because although there is a consensus on the N-tier software architecture in the industry, there is no standard or fact. Inaccurate layer definitions, blurred layer boundaries, and chaotic logical relationships between layers, etc., lead to the failure of reasonable and correct use of the N-layer software architecture, which seriously affects the realization of software functions and software performance.

Images