CN112612465B - Domain ontology multiplexing-oriented information system and development method - Google Patents
Domain ontology multiplexing-oriented information system and development method Download PDFInfo
- Publication number
- CN112612465B CN112612465B CN202011510625.4A CN202011510625A CN112612465B CN 112612465 B CN112612465 B CN 112612465B CN 202011510625 A CN202011510625 A CN 202011510625A CN 112612465 B CN112612465 B CN 112612465B
- Authority
- CN
- China
- Prior art keywords
- business
- model
- component
- layer
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000011161 development Methods 0.000 title claims abstract description 45
- 238000000034 method Methods 0.000 title claims description 75
- 230000010354 integration Effects 0.000 claims abstract description 10
- 230000007246 mechanism Effects 0.000 claims abstract description 6
- 230000005012 migration Effects 0.000 claims abstract description 5
- 238000013508 migration Methods 0.000 claims abstract description 5
- 230000008569 process Effects 0.000 claims description 67
- 238000004458 analytical method Methods 0.000 claims description 53
- 230000000694 effects Effects 0.000 claims description 47
- 230000006870 function Effects 0.000 claims description 27
- 230000008520 organization Effects 0.000 claims description 14
- 238000007726 management method Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 claims description 10
- 230000003993 interaction Effects 0.000 claims description 9
- 230000008859 change Effects 0.000 claims description 8
- 238000012423 maintenance Methods 0.000 claims description 7
- 239000000463 material Substances 0.000 claims description 4
- 238000005206 flow analysis Methods 0.000 claims description 3
- 230000018109 developmental process Effects 0.000 abstract description 42
- 230000033772 system development Effects 0.000 abstract description 9
- 238000010276 construction Methods 0.000 abstract description 5
- 238000000926 separation method Methods 0.000 abstract description 2
- 238000005516 engineering process Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000029531 common bile duct development Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000005714 functional activity Effects 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
Abstract
The invention discloses an information system for domain ontology multiplexing, which is applicable to the field of system development. Comprising the following steps: the business modeling layer is used for building and maintaining a business model; a component layer for building, maintaining and assembling components based on the service model, wherein the components comprise service components and public components; the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the migration and the reusability of the information system by establishing an architecture and a specification, and realizing the information sharing and the application integration of the information system; the software supporting platform layer comprises an operating system, a database management system and a network system and is used for providing a basic platform and a supporting environment for the business modeling layer, the component layer and the basic framework platform. The invention adopts business construction development, and is carried out in a 'top-down' driving 'bottom-up' mode, and each development stage has high concurrency, can adapt to changing requirements, reduces B-T separation and promotes industrialization of software production.
Description
Technical Field
The invention relates to the field of system development, in particular to an information system and a development method for domain ontology multiplexing.
Background
In the development process of a domain information system, how to better improve the reusability of a domain service model is a general concern of developers. The domain business model is an abstract description of specific business knowledge in the domain system, and the good domain business model can effectively support the development of the domain information system. An ontology refers to a formalized, explicit and detailed description of a shared concept system, which can provide a shared vocabulary to determine concepts and related relationships in a particular domain. The ontology-based domain business model takes a business domain ontology as a meta-model to provide common understanding and sharing domain models for personnel in all aspects of the domain.
The information system development process is a generic term for a series of activities that convert the needs of a user into a software system, and can implement the function operation of converting the functional needs in a corresponding business system into an information system. Software multiplexing is the process of using pre-established software elements to construct a new software system. The starting point of software multiplexing is that the development of an application system does not adopt all modes from beginning to end, but takes the basis of the existing work, and fully utilizes the accumulated knowledge and operation in the development of the application system in the past, thereby improving the efficiency and quality of the software development.
Disclosure of Invention
The technical problem to be solved by the invention is how to provide an information system and a development method for domain ontology-oriented multiplexing, which improve the reusability of a domain business model.
In order to solve the technical problems, the invention adopts the following technical scheme:
an information system for domain-oriented ontology multiplexing, comprising:
the business modeling layer is used for building and maintaining a business model, and the business model comprises a function model, an organization model, an information model, a resource model, a control model, a process model and an activity model;
a component layer for building, maintaining and assembling components based on the service model, wherein the components comprise service components and public components;
the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the migration and the reusability of the information system by establishing an architecture and a specification, and realizing the information sharing and the application integration of the information system;
and the software supporting platform layer comprises an operating system, a database management system and a network system and is used for providing a basic platform and a supporting environment for the service modeling layer, the component layer and the basic framework platform.
Further, the business component comprises a business use case component and a business object component;
the business use case component is used for representing the business activities of the field and comprises a planning component, a organizing component, a coordination component, a control component and a decision component;
the business object component is used for representing business concepts to be applied in the business process and comprises a personnel component, an information component, a material component, a command component and an indication component;
the public component comprises an information receiving and transmitting component, a query statistics component, a data maintenance component and a situation display component.
Further, the component layer comprises a service component system, and the association rule of the service component system is as follows: the upper layer traffic component may depend on any lower layer traffic component but cannot depend on the same layer or upper layer traffic component.
Further, the business component comprises a user interface layer, a working space layer, an organization layer and a resource layer, wherein:
the user interface layer is used for interacting with a user;
the working space layer is used for coordinating activities of a plurality of parallel users and maintaining consistency inside a single activity;
the organization layer is used for managing the consistency of the shared resources, executing the system rules and transmitting the system data to the working space layer;
the resource layer is used for providing access service of the system shared resource.
Further, the software infrastructure layer combines processes, software, standards and hardware to enable seamless integration between two or more information systems.
A development method of an information system for domain ontology multiplexing comprises the following steps:
constructing a domain service model, taking a service domain ontology as a meta model, and providing a domain service model for personnel in the domain, wherein the domain service model comprises service domain demand analysis and domain service model development;
information system development, developing an information system for domain-oriented ontology multiplexing according to any one of claims 1 to 5 based on a domain business model.
Further, the business field requirement analysis is used for acquiring requirements in the field and classifying the requirements, and reflecting the functional requirements of users in the field on the system.
Further, the domain business model development includes business function analysis, business flow analysis, business object analysis, object behavior analysis, and object activity analysis, wherein:
the business function analysis is used for generating a business function model by describing the input, output, control and constraint of each function activity;
the business process analysis is used for describing a business framework and a business process and generating a business process model;
the business object analyzes the object for definitely participating in the business process or activity and generates a business object model;
the object behavior analysis is used for analyzing the change of the object state in the business process or the activity, describing the change of the object state by using a state diagram in UML, and generating an object state model;
the object activity analysis is used for analyzing the cooperative relationship among a plurality of objects in a business process or activity, describing the cooperative relationship of the objects by using an interaction graph in UML, and generating an object activity model.
The beneficial effects of adopting above-mentioned technical scheme to produce lie in: the invention adopts business construction development, and is carried out in a 'top-down' driving 'bottom-up' mode, and each development stage has high concurrency, can adapt to changing requirements, reduces B-T separation and promotes industrialization of software production. The invention is based on the modeling theory of the business field, abstracts and describes various elements and relations related to the business, the realization part of the information system is encapsulated in the business software platform, and the development mode of the componentized business components is adopted, so that the most difficult realization part and a large number of repeated business logics do not need to be programmed, and the main work required by the information system developer is to develop specific business logics, namely, a special field business model is established on the basis of the business field model. The invention separates the service model and the information system realization technology, thereby fundamentally improving the technical independence of the information system.
Drawings
The invention will be described in further detail with reference to the drawings and the detailed description.
FIG. 1 is a diagram of a domain business model and business domain ontology of the present invention;
FIG. 2 is a diagram of a domain business model development process of the present invention;
FIG. 3 is a schematic diagram of the development of an information system based on a business software platform of the present invention;
FIG. 4 is a relationship diagram of an operating system, infrastructure platform, and business software platform of the present invention;
FIG. 5 is a block diagram of an information system platform architecture of the present invention;
fig. 6 is a business component classification diagram of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways other than those described herein, and persons skilled in the art will readily appreciate that the present invention is not limited to the specific embodiments disclosed below.
The information system comprises a service modeling layer, a component layer, an infrastructure platform and a software supporting platform layer, as shown in fig. 5, wherein the service modeling layer is used for building and maintaining a service model, and the service model comprises a function model, an organization model, an information model, a resource model, a control model, a process model and an activity model; a component layer for building, maintaining and assembling components based on the service model, wherein the components comprise service components and public components; the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the migration and the reusability of the information system by establishing an architecture and a specification, and realizing the information sharing and the application integration of the information system; and the software supporting platform layer comprises an operating system, a database management system and a network system and is used for providing a basic platform and a supporting environment for the service modeling layer, the component layer and the basic framework platform.
In one embodiment of the present invention, the service components include a service instance component and a service object component; the business use case component is used for representing the business activities of the field and comprises a planning component, a organizing component, a coordination component, a control component and a decision component; the business object component is used for representing business concepts to be applied in the business process and comprises a personnel component, an information component, a material component, a command component and an indication component; the public component comprises an information receiving and transmitting component, a query statistics component, a data maintenance component and a situation display component. The component layer comprises a service component system, and the association rule of the service component system is as follows: the upper layer traffic component may depend on any lower layer traffic component but cannot depend on the same layer or upper layer traffic component.
In one embodiment of the invention, the business component comprises a user interface layer, a working space layer, an organization layer and a resource layer, wherein: the user interface layer is used for interacting with a user; the working space layer is used for coordinating activities of a plurality of parallel users and maintaining consistency inside a single activity; the organization layer is used for managing the consistency of the shared resources, executing the system rules and transmitting the system data to the working space layer; the resource layer is used for providing access service of the system shared resource. The software infrastructure layer combines processes, software, standards and hardware to enable seamless integration between two or more information systems.
The development method of the information system for domain ontology multiplexing comprises the following steps: constructing a domain service model, taking a service domain ontology as a meta model, and providing a domain service model for personnel in the domain, wherein the domain service model comprises service domain demand analysis and domain service model development; and developing an information system, namely developing the information system for domain ontology multiplexing based on a domain business model. The business field demand analysis is used for acquiring demands in the field and classifying the demands and reflecting the functional demands of users on the system in the field.
In one embodiment of the present invention, the domain business model development includes business function analysis, business process analysis, business object analysis, object behavior analysis, and object activity analysis, as shown in fig. 2, where the business function analysis is used to generate a business function model by describing input, output, control, and constraint of each function activity; the business process analysis is used for describing a business framework and a business process and generating a business process model; the business object analyzes the object for definitely participating in the business process or activity and generates a business object model; the object behavior analysis is used for analyzing the change of the object state in the business process or the activity, describing the change of the object state by using a state diagram in UML, and generating an object state model; the object activity analysis is used for analyzing the cooperative relationship among a plurality of objects in a business process or activity, describing the cooperative relationship of the objects by using an interaction graph in UML, and generating an object activity model.
The invention adopts the object-oriented modeling language UML to express the result of the field demand analysis, and better combines the field demand analysis with the system development to provide model reusability.
In one embodiment of the invention, the domain requirement analysis is a process of acquiring and classifying requirements in the service domain, is a union of a series of similar or related system requirements in the domain, represents the sum of the functional requirements of users in the domain on each system, and intensively reflects the functional requirements of the users in the domain on the system. Domain requirement analysis not only describes the requirements of the domain, but also, from the viewpoint of multiplexing, stands on the reusability of the requirements.
The invention takes the business field ontology as a meta-model for obtaining the requirements, standardizes the whole field requirement obtaining process, and completes the model construction of the target system by reusing the field model. As shown in fig. 1.
In one embodiment of the invention, an ontology-based domain business model development process is shown in FIG. 2. The domain business model development process is carried out under the joint participation of domain experts, users and system developers and under the condition of referring to the existing system demand model and demand document, the business ontology is used as the input of the domain model and used for organizing and expressing unified business knowledge, the problem of domain knowledge sharing is solved, and the communication barrier among the domain experts, users and system developers is effectively eliminated. The specific steps comprise 5 stages: business function analysis, business flow analysis, business object analysis, object behavior analysis and exclusive activity analysis, and finally outputting a domain business model. The specific contents of each stage are as follows:
the purpose of the business function analysis stage is to ascertain through which specific functional activities the business objectives of the business system are achieved, thereby determining the logical structure and interrelationships of the business functions. In the process of demand analysis, service function analysis generates a service function model by describing the input, output, control, constraint and the like of each function activity in detail on the basis of a domain service function model to form the function demand of a service system.
The goal of the business process analysis phase is to conceptually describe the business framework and processes of the business system. The business process of the system is composed of a plurality of business processes. The method takes domain knowledge provided by a business body as a support, takes a domain business process model as a basis, and carries out comprehensive and repeated discussion research with business personnel, system developers and the like so as to obtain comprehensive and accurate analysis results of a business process and generate the business process model.
The goal of the business object analysis phase is to ascertain the entities involved in the business process or activity. Based on system business process analysis, business object analysis analyzes each activity in the business process model in detail to determine the objects involved in the activity and the relation between the objects, and generates a business object model.
The object behavior analysis aims at analyzing the change of the object state in the analysis process of the business flow, describing the change of the object state by using a state diagram in UML and generating an object state model.
The object activity analysis aims at analyzing the cooperative relationship among a plurality of objects in the business process analysis process, describing the cooperative relationship of the objects by using an interaction graph in UML, and generating an object activity model.
The software system of the invention is an operating system, an infrastructure platform, a business software platform and application software. The development mode of the information system oriented to multiplexing is shown in fig. 3, the invention carries out information system development based on a service software platform, unifies the basic operation supporting environment of the information system by the service software platform, and takes a service modeling tool as a development maintenance tool of the information system. The whole development process takes a business modeling theory and technology as support, takes a business field model as a basis, adopts an object-oriented technology to construct a model, creates a business object of an application system, constructs a functional model, an organization model, an information model, a resource model, a process model and a control model in a specific organization, constructs an application system framework through model driving, defines business rules through a business operation engine, and drives the operation of a business process. The requirements of the information system are formally described, and the required information system is automatically or semi-automatically generated by using a reusable application generator.
The information system development mode oriented to multiplexing has the following characteristics:
based on the business field modeling theory, the business field model abstracts and describes various elements and relations related to the business, and the business field model is used as the basic basis and foundation of the information system, so that the rationality of the information system design is better ensured.
The development mode is mainly based on building a model, wherein the model is a business model, and is not a program structure model for programming and technical service. Because the implementation part of the information system is encapsulated in the service software platform, and because of adopting the development mode of the componentized service components, the most difficult implementation part and a large number of repeated service logics do not need to be programmed, and the main work required by the information system developer is to develop specific service logics, namely, building a special field service model on the basis of a service field model.
The model is driven to be automatic, after a developer finishes the business modeling work, the business developer can run a business model on a business software platform to process field business, and the field information system is constructed, developed and maintained by taking the business modeling as a basic means, so that the development and maintenance efficiency of the information system is obviously improved.
The technical independence separates the service model from the information system implementation technology, thereby fundamentally improving the technical independence of the information system. The business software platform enables users to pay more attention to processes, organizations and business logic, and does not need to pay attention to how the business is technically realized, so that the speed of information system deployment and implementation is greatly increased, and the development period of the information system is shortened.
The content of the application is separated from the running part, the content related to the application is stored in the database of the server, and the running part is independent of the application and can span various different software systems in a plurality of different ways. Therefore, the realization technology of the bottom layer is stripped from the construction and maintenance processes of the application system, and system developers do not need to spend time and energy to know, master and solve the realization problem of the technology of the bottom layer.
Based on the configurability of the quick dynamic modeling, the dynamic business modeling provides a framework structure for business operation so as to ensure that an information system can be closely matched with a business process and a business model, thereby being beneficial to reducing the complexity of the system, increasing the information flexibility, facilitating the simulation and analysis of the information system and further obtaining an optimized information system.
The business foundation software platform is used for further reducing the difficulty of developing a complex application system on the foundation framework platform, realizing the purpose of business guiding and driving, and rapidly constructing the software platform of the application software. As shown in fig. 4, the operating system platform solves the interaction and management problem between the information system and the hardware, the infrastructure platform solves the interaction and management problem between the information system and the operating system platform, and the business base software platform is used for solving the interaction and management problem between the business description of the software, the operating system platform and the infrastructure platform, and is a software architecture system which is guided and driven by the business.
The business foundation software platform is an architecture tool and an operation platform for information system construction, provides an omnibearing solution and a foundation framework of an application system, wherein the omnibearing solution and the foundation framework can complete command control, information integration, business process management, information release, cooperative communication and the like, and is a business foundation software platform taking field business as a background. The business foundation software platform extracts general business parts such as planning, organization, coordination, control, decision and the like in various software, and serves as a service provided by the platform, so that redesign and research and development of the functional modules are avoided when new software is developed.
The architecture of the information system platform based on the business field model of the present invention is shown in fig. 5, and the architecture comprises four layers: the system comprises a business modeling layer, a component layer, a software infrastructure layer and a software supporting platform layer.
(1) Service modeling layer
Object-oriented business modeling is the basis for building information systems. The modeling business software platform is based on business modeling, and long-term application expansion and smooth transition of the business model are ensured by building and maintaining an integrated business model. The business modeling tool is a development and management system of a business software platform, adopts business guidance, is constructed based on a business field model, and is used as a reference model for constructing a business model by presetting a business field model library, so that basic model research and development work is omitted, and the development efficiency of the model is improved.
(2) Component layer
The component management layer includes component management functions, component creation functions, and component assembly functions, and is a hierarchy for creating, maintaining, and assembling business components or other common components. The components can be divided into business case components, business object components and public components, wherein the business case components represent the business activities of the field itself, and the business components correspond to the system level or subsystem level of the public business process (such as planning, organizing, coordinating, controlling, deciding and the like); the business object components express business concepts to be applied by the business process, and correspond to the components of the business object (such as personnel, information, materials, plans, instructions and the like); the public components correspond to general information system development components (such as information transceiving, query statistics, data maintenance, battlefield situation display and the like).
(3) Software infrastructure layer
The software infrastructure layer shields some interaction technical details between the components and the basic platform and among the components, such as an operating system, a communication protocol, a storage mechanism, the positions of the components and the like, and provides a transparent interoperation mechanism for the components based on the middleware, so that a developer can concentrate on business logic, and the development efficiency is improved. The infrastructure platform is mainly used for solving the interconnection problem of hardware and software systems, and ensures the interoperability, the migration and the reusability of the distributed system by establishing a set of architecture and a set of specifications on a computer network, thereby realizing information sharing and application integration in a distributed environment. The infrastructure platform combines processes, software, standards, and hardware to achieve seamless integration between two or more information systems.
(4) Software supporting platform layer
The software supporting platform layer mainly comprises an operating system, a database management system and a supporting network environment system at the bottom layer, is the most basic environment for the whole system to operate, and comprises environments of a client side and a server side of an application.
In one embodiment of the invention, the business component is a software implementation of a business object, expressing an autonomous business concept; is an element of an autonomous, reusable information system, which can be composed of several soft components. If the business object is a concept of problem domain, then the business component is a concept of solution domain, and the business component is more focused on implementation. The business component system, also called business component system model (BusinessComponentSystem Model, BCSM), is a complete business concept system developed by a set of autonomous business components, and has two characteristics: a group of independently developed business components are distributed through cooperation; the association rules in the service component system are that an upper layer service component may rely on any lower layer service component, but cannot rely on the same layer or an upper layer service component. To avoid too many cross-correlations of components, the system evolves hard, and the business component system is divided into two layers: business process components, business object components, as shown in fig. 6. Business process components representing the business activities of the domain itself, such as planning, organization of activities, etc.; and the business object component expresses business concepts to be applied in the business process and comprises control information, personnel state information, data information and the like.
In one embodiment of the invention, the internal structure of the business component system is, from a distributed computing perspective, divided into four logical levels: user layer, working space layer, organization layer, resource layer. The four logic layers and the C/S physical structure are not in direct corresponding relation, and can be flexibly configured according to the needs. A business component system is a set of components that may be distributed across different logical layers to work cooperatively. Wherein:
user layer: the user interface layer is responsible for expressing the processing result and realizing interaction with the user.
Working space layer: supporting a local set of components belonging to the same user activity; the system is responsible for coordinating activities of a plurality of parallel users and maintaining consistency inside a single activity; executing local processing logic.
Tissue layer: manage the consistency of the shared resources, execute the system rules and pass the system data to its upper working space layer.
Resource layer: and providing access service of the system shared resource, and taking charge of accessing the database.
In one embodiment of the invention, the development process of the business component is as follows: centered on "autonomous": autonomous BCSM, autonomous service component package, autonomous service component itself, autonomous service component layer, autonomous distributed component, etc. From the beginning of the software lifecycle, the software project is supported by a Business Component System (BCSM), which can be self-developed, commercially available, or both. Even from scratch, candidate BCSMs are constructed by determining candidate service components before obtaining the demand. Such as the design of a new type of computer, the kind of components constituting the computer is determined on an industrial level, although the specific characteristics thereof are not known. Business component technology is a production technology representing the industrialization of software, and those candidate business components and candidate BCSMs can be obtained through industry experience. In summary, the concept of business components extends throughout the life of the system development, except that its connotation varies from development stage to development stage.
Compared with OO development and CBD development, the service component development has the following advantages:
(1) The development stages have high concurrency. Business component development is performed in a "top-down" driven "bottom-up" manner. The whole development is guided by a top-down architecture, while the functional definition, analysis, design, implementation and testing of specific business components can be performed early in a given business component system and application architecture, so that the stages of development can be performed concurrently.
(2) The stages are developed with a highly reuse-oriented lifecycle. The new project may reuse BCSM, business component packages, business components and their models, source code, executable files, and even placement and use guidelines.
(3) Can adapt to the changing requirements. Business components can well simulate business processes and smoothly transform them into software implementations. The business component model has the capability of seamlessly tracking the business process model, the application software model and the physical database model in the whole life cycle, and the well-designed business components can be flexibly recombined along with business changes in a plug-and-play mode, so that the business component model can respond to the changes rapidly, flexibly and effectively.
(4) Reducing B-T gap. Business components are a fusion of business objects and component concepts that facilitate a smooth transition of business architecture to technology architecture.
(5) And the industrialization of software production is promoted. The business component technology provides theoretical and technical basis for software production industrialization.
Claims (1)
1. The development method of the information system for domain ontology multiplexing is characterized by comprising the following steps of:
constructing a domain service model, taking a service domain ontology as a meta model, and providing a domain service model for personnel in the domain, wherein the domain service model comprises service domain demand analysis and domain service model development;
developing an information system, namely developing an information system for domain ontology multiplexing based on a domain service model;
the domain ontology multiplexing-oriented information system comprises:
the business modeling layer is used for building and maintaining a business model, and the business model comprises a function model, an organization model, an information model, a resource model, a control model, a process model and an activity model;
a component layer for building, maintaining and assembling components based on the service model, wherein the components comprise service components and public components;
the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the migration and the reusability of the information system by establishing an architecture and a specification, and realizing the information sharing and the application integration of the information system;
the software supporting platform layer comprises an operating system, a database management system and a network system and is used for providing a basic platform and a supporting environment for the service modeling layer, the component layer and the basic framework platform;
the business use case component is used for representing the business activities of the field and comprises a planning component, a organizing component, a coordination component, a control component and a decision component;
the business object component is used for representing business concepts to be applied in the business process and comprises a personnel component, an information component, a material component, a command component and an indication component;
the public component comprises an information receiving and transmitting component, a query statistics component, a data maintenance component and a situation display component;
the component layer comprises a service component system, and the association rule of the service component system is as follows: the upper layer service components may depend on any lower layer service components, but cannot depend on the same layer or upper layer service components;
the business component comprises a user interface layer, a working space layer, an organization layer and a resource layer, wherein:
the user interface layer is used for interacting with a user;
the working space layer is used for coordinating activities of a plurality of parallel users and maintaining consistency inside a single activity;
the organization layer is used for managing the consistency of the shared resources, executing the system rules and transmitting the system data to the working space layer;
the resource layer is used for providing access service of the shared resources of the system;
the software infrastructure layer combines processes, software, standards and hardware, and can realize seamless integration between two or more information systems;
the business field demand analysis is used for acquiring demands in the field and classifying the demands and reflecting the functional demands of users on the system in the field;
the domain business model development comprises business function analysis, business flow analysis, business object analysis, object behavior analysis and object activity analysis, wherein:
the business function analysis is used for generating a business function model by describing the input, output, control and constraint of each function activity;
the business process analysis is used for describing a business framework and a business process and generating a business process model;
the business object analyzes the object for definitely participating in the business process or activity and generates a business object model;
the object behavior analysis is used for analyzing the change of the object state in the business process or the activity, describing the change of the object state by using a state diagram in UML, and generating an object state model;
the object activity analysis is used for analyzing the cooperative relationship among a plurality of objects in a business process or activity, describing the cooperative relationship of the objects by using an interaction graph in UML, and generating an object activity model.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011510625.4A CN112612465B (en) | 2020-12-18 | 2020-12-18 | Domain ontology multiplexing-oriented information system and development method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011510625.4A CN112612465B (en) | 2020-12-18 | 2020-12-18 | Domain ontology multiplexing-oriented information system and development method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112612465A CN112612465A (en) | 2021-04-06 |
| CN112612465B true CN112612465B (en) | 2024-04-16 |
Family
ID=75241116
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011510625.4A Active CN112612465B (en) | 2020-12-18 | 2020-12-18 | Domain ontology multiplexing-oriented information system and development method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112612465B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857898B (en) * | 2023-02-25 | 2023-05-23 | 武汉万云网络科技有限公司 | Application system construction and operation method and device |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101281466A (en) * | 2008-05-27 | 2008-10-08 | 北京中企开源信息技术有限公司 | Service object modeling method based on service main body characteristic |
| CN101329629A (en) * | 2008-07-22 | 2008-12-24 | 中国科学院计算技术研究所 | Business level method, apparatus and system for managing service information |
| CN101876902A (en) * | 2009-11-24 | 2010-11-03 | 武汉大学 | Domain service asset organizing method based on RGPS (Role-Goal-Process-Service) meta-model frame |
| CN102034173A (en) * | 2010-12-31 | 2011-04-27 | 东莞市高明企业服务有限公司 | Service-oriented architecture (SOA) mold information collaborative management system developing method and system |
| CN102375731A (en) * | 2010-08-23 | 2012-03-14 | 融建信息技术(厦门)有限公司 | Coding-free integrated application platform system |
| CN103049279A (en) * | 2011-10-11 | 2013-04-17 | 神州数码信息系统有限公司 | Method for loading software business |
| CN103455325A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Business-model-based architecture platform |
| CN103761082A (en) * | 2013-12-31 | 2014-04-30 | 湖南大唐先一科技有限公司 | Componential research and development mode and domain driving model combined application development system and platform |
| CN106815013A (en) * | 2016-12-15 | 2017-06-09 | 北京航天测控技术有限公司 | A kind of seating plane health control ground support system framework of two-way interactive |
| CN107463358A (en) * | 2016-06-02 | 2017-12-12 | 华迪计算机集团有限公司 | A kind of management system based on business model |
| CN110058846A (en) * | 2019-04-19 | 2019-07-26 | 深圳市康拓普信息技术有限公司 | A kind of service application software development system and method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030009740A1 (en) * | 2001-06-11 | 2003-01-09 | Esoftbank (Beijing) Software Systems Co., Ltd. | Dual & parallel software development model |
| US8112257B2 (en) * | 2007-07-31 | 2012-02-07 | Sap Ag | Semantic extensions of business process modeling tools |
| US9015665B2 (en) * | 2008-11-11 | 2015-04-21 | International Business Machines Corporation | Generating functional artifacts from low level design diagrams |
| US9317814B2 (en) * | 2013-03-21 | 2016-04-19 | International Business Machines Corporation | Automatically generating an ontology and axioms from a business-process model |
-
2020
- 2020-12-18 CN CN202011510625.4A patent/CN112612465B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101281466A (en) * | 2008-05-27 | 2008-10-08 | 北京中企开源信息技术有限公司 | Service object modeling method based on service main body characteristic |
| CN101329629A (en) * | 2008-07-22 | 2008-12-24 | 中国科学院计算技术研究所 | Business level method, apparatus and system for managing service information |
| CN101876902A (en) * | 2009-11-24 | 2010-11-03 | 武汉大学 | Domain service asset organizing method based on RGPS (Role-Goal-Process-Service) meta-model frame |
| CN102375731A (en) * | 2010-08-23 | 2012-03-14 | 融建信息技术(厦门)有限公司 | Coding-free integrated application platform system |
| CN102034173A (en) * | 2010-12-31 | 2011-04-27 | 东莞市高明企业服务有限公司 | Service-oriented architecture (SOA) mold information collaborative management system developing method and system |
| CN103049279A (en) * | 2011-10-11 | 2013-04-17 | 神州数码信息系统有限公司 | Method for loading software business |
| CN103455325A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Business-model-based architecture platform |
| CN103761082A (en) * | 2013-12-31 | 2014-04-30 | 湖南大唐先一科技有限公司 | Componential research and development mode and domain driving model combined application development system and platform |
| CN107463358A (en) * | 2016-06-02 | 2017-12-12 | 华迪计算机集团有限公司 | A kind of management system based on business model |
| CN106815013A (en) * | 2016-12-15 | 2017-06-09 | 北京航天测控技术有限公司 | A kind of seating plane health control ground support system framework of two-way interactive |
| CN110058846A (en) * | 2019-04-19 | 2019-07-26 | 深圳市康拓普信息技术有限公司 | A kind of service application software development system and method |
Non-Patent Citations (4)
| Title |
|---|
| Domain-Specific Business Modeling with the Business Model Developer;Steve Boßelmann 等;《Springer》;第546-560页 * |
| Using Ontologies for Software Development Knowledge Reuse;Bruno Antunes 等;《Springer》;第357-368页 * |
| 一种基于关联规则与K-means的领域本体构建方法;李征;李斌;;河南师范大学学报(自然科学版);20200115(第01期);第30-38页 * |
| 业务本体开发与描述方法;刘云杰 等;《计算机应用》;第第27卷卷(第第06期期);第1423-1425页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112612465A (en) | 2021-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Granchelli et al. | Towards recovering the software architecture of microservice-based systems | |
| CN101901150B (en) | Universal distributed airborne equipment health management simulation platform and implementation method thereof | |
| Casale et al. | Current and future challenges of software engineering for services and applications | |
| Blobel | Application of the component paradigm for analysis and design of advanced health system architectures | |
| CN102375734B (en) | Application product development system, method and device and operation system, method and device | |
| CN102253974B (en) | Dynamic combination method for geographic model network services | |
| CN102034173A (en) | Service-oriented architecture (SOA) mold information collaborative management system developing method and system | |
| CN112612465B (en) | Domain ontology multiplexing-oriented information system and development method | |
| Wolf et al. | Reusability first: Toward FAIR workflows | |
| Redding et al. | Transforming object-oriented models to process-oriented models | |
| CN110766163B (en) | System for implementing machine learning process | |
| Pernici et al. | Conceptual modeling and software components reuse: towards the unification | |
| Bucchiarone et al. | Towards a domain specific language for engineering collective adaptive systems | |
| Anshina | Agile Architecture for Digital Enterprises | |
| Ruiz et al. | Model-driven organisational reengineering A framework to support organisational improvement | |
| Tsigkanos et al. | On formalizing and identifying patterns in cloud workload specifications | |
| CN112199075A (en) | Intelligent information processing method and framework based on micro-service | |
| Efendioglu et al. | Modelling method design: An adoxx realisation | |
| Dridi et al. | Towards a Multi-Viewpoints Approach for the SoS Engineering | |
| Liu et al. | Information system development method for domain ontology reuse | |
| Ostadzadeh et al. | An MDA-based generic framework to address various aspects of enterprise architecture | |
| Gu et al. | Multi-view modeling and analysis of embedded real-time software with meta-modeling and model transformation | |
| Kumar et al. | Review and refined architectures for monitoring, information exchange, and control of interconnected distributed resources | |
| CN112988695B (en) | Super-fusion mixed architecture computing material platform | |
| CN111562904B (en) | Reliability block diagram RBD (radial basis function) auxiliary modeling method based on SysML (SysML) system model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |