CN112612465A - Domain ontology multiplexing-oriented information system and development method - Google Patents
Domain ontology multiplexing-oriented information system and development method Download PDFInfo
- Publication number
- CN112612465A CN112612465A CN202011510625.4A CN202011510625A CN112612465A CN 112612465 A CN112612465 A CN 112612465A CN 202011510625 A CN202011510625 A CN 202011510625A CN 112612465 A CN112612465 A CN 112612465A
- Authority
- CN
- China
- Prior art keywords
- business
- model
- component
- domain
- layer
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 83
- 238000011161 development Methods 0.000 title claims abstract description 42
- 230000010354 integration Effects 0.000 claims abstract description 10
- 230000007246 mechanism Effects 0.000 claims abstract description 6
- 230000008569 process Effects 0.000 claims description 71
- 238000004458 analytical method Methods 0.000 claims description 59
- 230000000694 effects Effects 0.000 claims description 46
- 230000006870 function Effects 0.000 claims description 27
- 238000010586 diagram Methods 0.000 claims description 15
- 238000007726 management method Methods 0.000 claims description 12
- 230000008520 organization Effects 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 8
- 230000003993 interaction Effects 0.000 claims description 8
- 238000012423 maintenance Methods 0.000 claims description 7
- 239000000463 material Substances 0.000 claims description 4
- 230000018109 developmental process Effects 0.000 abstract description 38
- 230000033772 system development Effects 0.000 abstract description 9
- 238000010276 construction Methods 0.000 abstract description 5
- 238000005516 engineering process Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000005714 functional activity 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
- 238000006243 chemical reaction Methods 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
- 230000004927 fusion Effects 0.000 description 1
- 230000002452 interceptive effect 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
- 238000004904 shortening Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a domain ontology multiplexing-oriented information system, which is suitable for the field of system development. The method comprises the following steps: the business modeling layer is used for building and maintaining a business model; the component layer is used for establishing, maintaining and assembling components based on the business model, and the components comprise business components and public components; the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the mobility and the reusability of the information system by establishing a system structure 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 architecture platform. The invention adopts the business construction and development, is carried out in a bottom-up mode driven by top-down, has high concurrency in each stage, can adapt to the changing requirements, reduces the B-T gap and promotes the software production industrialization.
Description
Technical Field
The invention relates to the field of system development, in particular to a domain ontology multiplexing-oriented information system and a development method.
Background
In the development process of the domain information system, how to better improve the reusability of the domain business model is a problem generally concerned by developers. The domain business model is abstract description of concrete 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 the shared concept hierarchy," which can provide a shared vocabulary for determining domain-specific concepts and relationships. The ontology-based domain business model takes a business domain ontology as a meta-model, and provides a commonly understood and shared domain model for people in various aspects in the field.
The information system development process is a general term for converting the requirements of users into a series of activities of a software system, and can realize the conversion of the functional requirements in the corresponding business system into the functional operation of the information system. Software reuse is the process of using pre-established software elements to construct new software systems. The starting point of software reuse is that the development of the application system does not adopt a mode of all starting from the beginning any more, but takes the existing work as the basis, and fully utilizes the knowledge and the management accumulated in the development of the application system in the past, thereby improving the efficiency and the quality of software development.
Disclosure of Invention
The technical problem to be solved by the invention is how to provide a domain ontology multiplexing-oriented information system and a development method for improving the reusability of a domain business model.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a domain ontology-oriented multiplexing information system, 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;
the component layer is used for establishing, maintaining and assembling components based on the business model, and the components comprise business components and public components;
the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the mobility and the reusability of the information system by establishing an architecture and specifications, 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 architecture platform.
Further, the business components comprise business case components and business object components;
the business case component is used for representing the business activities of the field, and comprises a planning component, an organization component, a coordination component, a control component and a decision component;
the business object component is used for expressing business concepts to be applied in business processes 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, an inquiry counting component, a data maintenance component and a situation display component.
Further, the component layer comprises a business component system, and the association rule of the business component system is as follows: the upper level business components can rely on any lower level business components, but cannot rely on the same level or upper level business components.
Further, the business component comprises a user interface layer, a workspace layer, a organizational 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 the consistency in a single activity;
the organizational layer is used for managing the consistency of shared resources, executing system rules and transmitting system data to the workspace layer;
the resource layer is used for providing access service of system shared resources.
Further, the software infrastructure layer combines processes, software, standards, and hardware to enable seamless integration between two or more information systems.
A development method for a domain ontology multiplexing-oriented information system comprises the following steps:
constructing a domain business model, taking a business domain ontology as a meta-model, and providing a domain business model for personnel in the domain, wherein the domain business model comprises business domain demand analysis and domain business model development;
development of an information system based on a domain business model for domain ontology oriented multiplexing as claimed in any one of claims 1 to 5.
Furthermore, the service field requirement analysis is used for acquiring the requirements in the field and classifying the requirements, so that the functional requirements of the user on the system in the field are reflected.
Further, the domain business model development includes business function analysis, business process analysis, business object analysis, object behavior analysis and object activity analysis, wherein:
the business function analysis is used for describing input, output, control and constraint of each function activity to generate a business function model;
the business process analysis is used for describing a business framework and a business process and generating a business process model;
the business object analysis is used for definitely participating in the objects of the business process or the activity and generating a business object model;
the object behavior analysis is used for analyzing the change of the object state in the business process or activity, describing the change of the object state by using a state diagram in the UML and generating an object state model;
the object activity analysis is used for analyzing the cooperation relationship among a plurality of objects in a business process or activity, describing the cooperation relationship of the objects by an interaction diagram in the UML and generating an object activity model.
Adopt the produced beneficial effect of above-mentioned technical scheme to lie in: the invention adopts the business construction and development, is carried out in a bottom-up mode driven by top-down, has high concurrency in each stage, can adapt to the changing requirements, reduces the B-T gap and promotes the software production industrialization. The invention is based on the modeling theory of the business field, abstracts and describes various elements related to the business and the relationship thereof, the business software platform of the invention encapsulates the realization part of the information system and adopts a component business component development mode, so the most difficult realization part and a large amount of repeated business logics do not need programming, and the main work required by the information system developer is to develop specific business logics, namely, establish a special field business model on the basis of the business field model. The invention separates the business model from the information system realization technology, and fundamentally promotes the technical independence of the information system.
Drawings
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
FIG. 1 is a relational diagram of a domain business model and a business domain ontology of the present invention;
FIG. 2 is a domain business model development process diagram of the present invention;
FIG. 3 is a diagram of the information system development model based on the business software platform of the present invention;
FIG. 4 is a relational diagram of the operating system, infrastructure platform, and business software platform of the present invention;
FIG. 5 is a diagram of an information system platform architecture of the present invention;
fig. 6 is a traffic component classification diagram of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present 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 than those specifically described and will be readily apparent to those of ordinary skill in the art without departing from the spirit of the present invention, and therefore the present invention is not limited to the specific embodiments disclosed below.
The information system of the invention comprises a business modeling layer, a component layer, a basic framework platform and a software supporting platform layer, as shown in fig. 5, 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; the component layer is used for establishing, maintaining and assembling components based on the business model, and the components comprise business components and public components; the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the mobility and the reusability of the information system by establishing an architecture and specifications, 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 architecture platform.
In one embodiment of the invention, the business components comprise business use case components and business object components; the business case component is used for representing the business activities of the field, and comprises a planning component, an organization component, a coordination component, a control component and a decision component; the business object component is used for expressing business concepts to be applied in business processes 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, an inquiry counting component, a data maintenance component and a situation display component. The component layer comprises a business component system, and the association rule of the business component system is as follows: the upper level business components can rely on any lower level business components, but cannot rely on the same level or upper level business components.
In one embodiment of the invention, the business component comprises a user interface layer, a workspace layer, a organizational 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 the consistency in a single activity; the organizational layer is used for managing the consistency of shared resources, executing system rules and transmitting system data to the workspace layer; the resource layer is used for providing access service of system shared resources. The software infrastructure layer combines processes, software, standards, and hardware to enable seamless integration between two or more information systems.
The invention relates to a method for developing a domain ontology multiplexing-oriented information system, which comprises the following steps: constructing a domain business model, taking a business domain ontology as a meta-model, and providing a domain business model for personnel in the domain, wherein the domain business model comprises business domain demand analysis and domain business model development; and developing the information system, namely developing the field body multiplexing-oriented information system based on the field business model. The business field requirement analysis is used for acquiring the requirements in the field and classifying the requirements, and reflecting the functional requirements of the users on the system in the field.
In an 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, 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 analysis is used for definitely participating in the objects of the business process or the activity and generating a business object model; the object behavior analysis is used for analyzing the change of the object state in the business process or activity, describing the change of the object state by using a state diagram in the UML and generating an object state model; the object activity analysis is used for analyzing the cooperation relationship among a plurality of objects in a business process or activity, describing the cooperation relationship of the objects by an interaction diagram in the UML and generating an object activity model.
The method adopts the object-oriented modeling language UML to express the result of the field requirement analysis, and better combines the field requirement analysis with the system development to provide the model reusability.
In an embodiment of the present invention, the domain requirement analysis is a process of acquiring and classifying requirements in the business domain, and is a union of a series of similar or related system requirements in the domain, which represents a sum of functional requirements of users in the domain for each system, and centrally reflects the functional requirements of users in the domain for the system. The domain requirement analysis not only describes the requirements of the domain, but also, from a multiplexing point of view, relies on the reusability of the requirements.
The invention takes the service field body as the meta-model for acquiring the demand, standardizes the whole field demand acquisition 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 illustrated in FIG. 2. The domain business model development process is carried out under the condition of referring to the existing system demand model and demand documents under the joint participation of domain experts, users and system developers, and the business body is used as the input of the domain model and is used for unifying the organization and expression of business knowledge, solving the problem of domain knowledge sharing and effectively eliminating the communication obstacles among the domain experts, the users and the system developers. The concrete steps include 5 stages: the method comprises the steps of business function analysis, business process analysis, business object analysis, object behavior analysis and exclusive activity analysis, and finally, a domain business model is output. The specific content of each stage is as follows:
the purpose of the business function analysis phase is to figure out which specific functional activities the business objectives of the business system are implemented through, thereby determining the logical structure and interrelationships of the business functions. In the process of requirement analysis, the business function analysis forms the functional requirement of the business system by describing the input, output, control, constraint and the like of each functional activity in detail on the basis of the domain business function model, and generates the business function model.
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 domain knowledge provided by the business ontology is used as a support, and a domain business process model is used as a basis to carry out comprehensive and repeated discussion research with business personnel, system developers and the like so as to obtain a comprehensive and accurate analysis result of the business process and generate a business process model.
The goal of the business object analysis phase is to make the entities involved in the business process or activity up to date. The business object analysis is based on the system business process analysis, and each activity in the business process model is analyzed in detail to determine the objects involved in the activity and the relationship among the objects, and generate the business object model.
The purpose of the object behavior analysis is to analyze the change of the object state in the business process analysis process, describe the change of the object state by using a state diagram in the UML, and generate an object state model.
The object activity analysis aims to analyze the cooperation relationship among a plurality of objects in the business process analysis process, describe the cooperation relationship of the objects by an interaction diagram in the UML and generate an object activity model.
The software system of the invention is 'operating system + infrastructure platform + service software platform + application software'. The development mode of the multiplexing-oriented information system is shown in fig. 3, the information system is developed based on the service software platform, the basic operation supporting environment of the information system is unified by the service software platform, and the service modeling tool is used as the development maintenance tool of the information system. The whole development process is supported by a business modeling theory and technology, a business field model is used as a basis, an object-oriented technology is adopted to construct a model, a business object of an application system is created, a function model, an organization model, an information model, a resource model, a process model and a control model in a specific organization are constructed, an application system framework is constructed through model driving, a business rule is defined through a business operation engine, and the operation of a business process is driven. Formally describing the requirements of the information system, and automatically or semi-automatically generating the required information system by using a reusable application generator.
The multiplex-oriented information system development mode has the following characteristics:
based on the business field modeling theory, the business field model abstracts and describes various elements related to business and relations of the elements, and the business field model is used as a basic basis and a foundation of an information system, so that the rationality of the information system design is better ensured.
The development mode mainly takes modeling as the main mode, and the model is a business model and not a program structure model for programming and technical service. Because the implementation part of the information system is packaged in the service software platform and because a component-based service component development mode is adopted, the most difficult implementation part and a large amount of repeated service logics do not need programming, and the main work to be done by information system developers is to develop specific service logics, namely to establish a special field service model on the basis of a service field model.
The model is driven to be automatic, after developers finish the work of business modeling, the business personnel can operate the business model on the business software platform, process the field business, and construct, develop and maintain the field information system by taking the business modeling as a basic means, thereby obviously improving the efficiency of information system development and maintenance.
The technology independence separates the business model from the information system realization technology, and fundamentally improves the technology independence of the information system. The service software platform enables users to pay more attention to the process, organization and service logic without paying attention to how the service is technically realized, thereby greatly accelerating the deployment and implementation speed of the information system and shortening the development period of the information system.
The application content is separated from the run-time portion, the application-related content is stored entirely in the server-side database, and the run-time portion is application-independent and can span a variety of different software systems in a variety of different ways. Therefore, the implementation technology of the bottom layer is stripped from the construction and maintenance process of the application system, and system developers do not need to spend time and energy to know, master and solve the technical implementation problem of the bottom layer.
Based on the configurability of the rapid 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, which is beneficial to reducing the complexity of the system, increasing the flexibility of information, facilitating the simulation and analysis of the information system and further obtaining an optimized information system.
The service basic software platform is used for further reducing the difficulty of developing a complex application system on a basic architecture platform, realizing service guidance and driving and quickly constructing the software platform of the application software. As shown in fig. 4, the operating system platform solves the problem of interaction and management between the information system and the hardware, the infrastructure platform solves the problem of interaction and management between the information system and the operating system platform, and the service basic software platform is used for solving the problem of interaction and management between the service description of the software and the operating system platform and the infrastructure platform, and is a software architecture system that is service-oriented and driven.
The business basic software platform is a framework tool and an operation platform for information system construction, provides an all-round solution scheme and a basic framework of an application system which can complete command control, information integration, business process management, information release, cooperative communication and the like, and is a business basic software platform taking field business as the background. The business basic software platform extracts the general business parts in various software, such as planning, organizing, coordinating, controlling, deciding and the like, and the business basic software platform is used as the service provided by the platform, so that the redesign and the research and development of the functional modules are avoided when new software is developed.
The architecture diagram of the information system platform based on the service domain model of the invention is shown in fig. 5, and the architecture comprises four layers: the system comprises a business modeling layer, a component layer, a software basic framework layer and a software supporting platform layer.
(1) Business modeling layer
Object-oriented business modeling is the basis for building information systems. The modeled service software platform is based on service modeling, and ensures long-term application expansion and smooth transition of a service model by establishing and maintaining an integrated service 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 saves basic model research and development work and improves the development efficiency of the model by taking a preset business field model library as a reference model for constructing the business model.
(2) Component layer
The component management layer comprises a component management function, a component building function and a component assembling function, and is a layer for building, maintaining and assembling business components or other common components. The components can be divided into business use case components, business object components and public components, wherein the business use case components represent business activities of the field, and correspond to business components (such as planning, organization, coordination, control, decision and the like) of a system level or a subsystem level of a public business process; the business object component expresses the business concept to be applied by the business process and corresponds to the component of the business object (such as personnel, information, materials, plans, instructions and the like); the common components correspond to common information system development components (such as messaging, query statistics, data maintenance, battlefield situation display, etc.).
(3) Software infrastructure layer
The software basic architecture layer shields some interactive technical details among the components, the basic platform and 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 developers 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 interoperability, migratability and reusability of a distributed system by establishing a set of architecture and a set of specifications on a computer network, thereby realizing information sharing and application integration under a distributed environment. An infrastructure platform combines processes, software, standards, and hardware to enable 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 bottom layer supporting network environment system, is the most basic environment for running the whole system, and comprises the environments of an application client side and a server side.
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 that can be composed of several soft components. If the business object is the concept of the problem domain, then the business component is the concept of the solution domain, and the business component focuses more on the implementation. A business component system, also called a Business Component System Model (BCSM), is a complete business concept system developed by a group of autonomous business components, and has two characteristics: a group of independently developed business components release functions through cooperation; an association rule in a business building system is that an upper level business building can rely on any lower level business building, but cannot rely on a same level or upper level business building. In order to avoid too many cross-correlations of the components and difficult system evolution, the service component system is divided into two layers: business process components, business object components, as shown in FIG. 6. A business process component, representing the business activities of the domain itself, such as planning, organization of activities, etc.; the business object component expresses the business concept to be applied in the business process, and the business concept comprises control information, personnel state information, data information and the like.
In one embodiment of the invention, the internal structure of the business building system from the distributed computing perspective, the single business building is divided into four logical levels: user layer, workspace layer, organizational layer, resource layer. The four logic layers are not in direct correspondence with the C/S physical structure, and can be flexibly configured according to the requirement. A business building block system is a set of building blocks that can be distributed over different logical layers to act in concert. Wherein:
and (3) a user layer: namely, the user interface layer is responsible for expressing the processing result and realizing the interaction with the user.
Workspace layer: supporting a local set of building blocks belonging to the same user activity; the system is responsible for coordinating activities of a plurality of parallel users and maintaining the consistency in a single activity; local processing logic is executed.
Tissue layer: manage the consistency of the shared resources, enforce system rules and pass system data to its upper workspace layer.
Resource layer: and providing access service of system shared resources, and taking charge of accessing the database.
In one embodiment of the present invention, the development process of the business component is as follows: centering on "autonomy": an autonomous BCSM, an autonomous business component package, an autonomous business component itself, an autonomous business component layer, an autonomous distributed component, and the like. From 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 the beginning, candidate business components are determined and candidate BCSMs are constructed before demand is obtained. Although the specific features of a new computer are not known, the types of components that make up the computer are determined on an industrial scale. Business component technology is a production technology that represents software industrialization, and those candidate business components and candidate BCSMs can be obtained through industry experience. In summary, the concept of business building blocks extends throughout the life cycle of system development, with the implications differing from one development stage to another.
Compared with OO development and CBD development, the business component development has the following advantages:
(1) the development of each stage has high concurrency. Business building block development is conducted in a "bottom-up" manner driven "top-down". The whole development is guided by a top-down system structure, and the function definition, analysis, design, realization and test of specific business components can be carried out in the early stage of a given business component system and an application system structure, so that the development stages can be carried out concurrently.
(2) The development of each stage, a highly reuse-oriented lifecycle. New projects can reuse BCSMs, business building packages, business building blocks and their models, source code, executables, and even instructions for placement and use.
(3) Can be adapted to changing requirements. The business components can well simulate the business process and smoothly translate it into a software implementation. The service component model has the capability of seamlessly tracking the service process model, the application software model and the physical database model in the whole life cycle, and well-designed service components can be flexibly recombined along with service changes in a plug-and-play mode, so that the service component model can quickly, flexibly and effectively respond to changes.
(4) Reducing the B-T gap. Business components are a fusion of business objects and component concepts, which facilitates a smooth transition from business architecture to technology architecture.
(5) Promotes the industrialization of software production. The business component technology provides a theoretical and technical basis for software production industrialization.
Claims (8)
1. An information system for domain 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;
the component layer is used for establishing, maintaining and assembling components based on the business model, and the components comprise business components and public components;
the infrastructure platform is used for providing an interoperation mechanism for the components, ensuring the interoperability, the mobility and the reusability of the information system by establishing an architecture and specifications, 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 architecture platform.
2. The domain-ontology-oriented multiplexing information system of claim 1, wherein: the business components comprise business use case components and business object components;
the business case component is used for representing the business activities of the field, and comprises a planning component, an organization component, a coordination component, a control component and a decision component;
the business object component is used for expressing business concepts to be applied in business processes 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, an inquiry counting component, a data maintenance component and a situation display component.
3. The domain-ontology-oriented multiplexing information system of claim 1, wherein: the component layer comprises a business component system, and the association rule of the business component system is as follows: the upper level business components can rely on any lower level business components, but cannot rely on the same level or upper level business components.
4. The domain-oriented ontology multiplexing information system of claim 1, wherein the business components comprise a user interface layer, a workspace layer, a organizational 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 the consistency in a single activity;
the organizational layer is used for managing the consistency of shared resources, executing system rules and transmitting system data to the workspace layer;
the resource layer is used for providing access service of system shared resources.
5. The domain-oriented ontology multiplexing information system of claim 1, wherein the software infrastructure layer combines processes, software, standards and hardware to enable seamless integration between two or more information systems.
6. A development method for a domain ontology multiplexing-oriented information system is characterized by comprising the following steps:
constructing a domain business model, taking a business domain ontology as a meta-model, and providing a domain business model for personnel in the domain, wherein the domain business model comprises business domain demand analysis and domain business model development;
development of an information system based on a domain business model for domain ontology oriented multiplexing as claimed in any one of claims 1 to 5.
7. The method for developing a domain ontology multiplexing-oriented information system according to claim 6, wherein the business domain requirement analysis is used for acquiring requirements in a domain and classifying the requirements, so as to reflect functional requirements of users on the system in the domain.
8. The method for developing a domain ontology multiplexing-oriented information system according to claim 6, wherein the domain business model development comprises business function analysis, business process analysis, business object analysis, object behavior analysis and object activity analysis, wherein:
the business function analysis is used for describing input, output, control and constraint of each function activity to generate a business function model;
the business process analysis is used for describing a business framework and a business process and generating a business process model;
the business object analysis is used for definitely participating in the objects of the business process or the activity and generating a business object model;
the object behavior analysis is used for analyzing the change of the object state in the business process or activity, describing the change of the object state by using a state diagram in the UML and generating an object state model;
the object activity analysis is used for analyzing the cooperation relationship among a plurality of objects in a business process or activity, describing the cooperation relationship of the objects by an interaction diagram in the 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 true CN112612465A (en) | 2021-04-06 |
| CN112612465B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857898A (en) * | 2023-02-25 | 2023-03-28 | 武汉万云网络科技有限公司 | Application system construction and operation method and device |
Citations (15)
| 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 |
| 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 |
| US20090037237A1 (en) * | 2007-07-31 | 2009-02-05 | Sap Ag | Semantic extensions of business process modeling tools |
| US20100122238A1 (en) * | 2008-11-11 | 2010-05-13 | International Business Machines Corporation | Generating functional artifacts from low level design diagrams |
| 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 |
| US20140289173A1 (en) * | 2013-03-21 | 2014-09-25 | International Business Machines Corporation | Automatically generating an ontology and axioms from a business-process model |
| 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 |
-
2020
- 2020-12-18 CN CN202011510625.4A patent/CN112612465B/en active Active
Patent Citations (15)
| 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 |
| US20090037237A1 (en) * | 2007-07-31 | 2009-02-05 | Sap Ag | Semantic extensions of business process modeling tools |
| 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 |
| US20100122238A1 (en) * | 2008-11-11 | 2010-05-13 | International Business Machines Corporation | Generating functional artifacts from low level design diagrams |
| 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 |
| US20140289173A1 (en) * | 2013-03-21 | 2014-09-25 | International Business Machines Corporation | Automatically generating an ontology and axioms from a business-process model |
| 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 |
|---|
| BRUNO ANTUNES 等: "Using Ontologies for Software Development Knowledge Reuse", 《SPRINGER》, pages 357 - 368 * |
| STEVE BOSSELMANN 等: "Domain-Specific Business Modeling with the Business Model Developer", 《SPRINGER》, pages 546 - 560 * |
| 刘云杰 等: "业务本体开发与描述方法", 《计算机应用》, vol. 27, no. 06, pages 1423 - 1425 * |
| 李征;李斌;: "一种基于关联规则与K-means的领域本体构建方法", 河南师范大学学报(自然科学版), no. 01, 15 January 2020 (2020-01-15), pages 30 - 38 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857898A (en) * | 2023-02-25 | 2023-03-28 | 武汉万云网络科技有限公司 | Application system construction and operation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112612465B (en) | 2024-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Ambriola et al. | Assessing process-centered software engineering environments | |
| Ouyang et al. | Translating standard process models to BPEL | |
| CN110376959B (en) | Soft PLC configuration software generation system based on FPGA platform | |
| Kardas | Model-driven development of multiagent systems: a survey and evaluation | |
| CN101901150A (en) | Universal distributed airborne equipment health management simulation platform and implementation method thereof | |
| Tonelli et al. | Cyber-physical systems (CPS) in supply chain management: from foundations to practical implementation | |
| CN111736821A (en) | Visual modeling analysis method, system, computer device and readable storage medium | |
| CN102253974B (en) | Dynamic combination method for geographic model network services | |
| CN111400389A (en) | IFC expansion-based operation and maintenance 5D-BIM data integration and sharing system | |
| 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 | |
| CN102087595A (en) | Method and system for developing patent agency collaborative management system based on SOA (service oriented architecture) | |
| CN115469860B (en) | Method and system for automatically generating demand-to-software field model based on instruction set | |
| CN116301760A (en) | Application design system for software development | |
| Anshina | Agile Architecture for Digital Enterprises | |
| Gao et al. | Mission operations and autonomy | |
| Perry et al. | A Theory about the Structure of GTSEs | |
| Dridi et al. | Towards a Multi-Viewpoints Approach for the SoS Engineering | |
| Liu et al. | Information system development method for domain ontology reuse | |
| Augusto et al. | Ambiance: A mobile agent platform for end-user programmable ambient systems | |
| CN112817571B (en) | Man-machine object fusion application modeling method based on scene storyboard | |
| Singer | Business Process Modeling and Execution--A Compiler for Distributed Microservices | |
| Mustapha et al. | Agent-based supply chain simulation: Towards an organization-oriented methodological framework | |
| Gimenes et al. | A product line architecture for workflow management systems with component-based development | |
| Sun | 3D CAD Information System Integration Based on the Private Cloud Platform |
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 | ||
| GR01 | Patent grant |