WO2015196780A1 - 一种基于系统元模型以构造系统模型的通用建模方法 - Google Patents

一种基于系统元模型以构造系统模型的通用建模方法 Download PDF

Info

Publication number
WO2015196780A1
WO2015196780A1 PCT/CN2015/000451 CN2015000451W WO2015196780A1 WO 2015196780 A1 WO2015196780 A1 WO 2015196780A1 CN 2015000451 W CN2015000451 W CN 2015000451W WO 2015196780 A1 WO2015196780 A1 WO 2015196780A1
Authority
WO
WIPO (PCT)
Prior art keywords
model
attribute
activity
component type
algorithm
Prior art date
Application number
PCT/CN2015/000451
Other languages
English (en)
French (fr)
Inventor
符长明
Original Assignee
成都普中软件有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 成都普中软件有限公司 filed Critical 成都普中软件有限公司
Priority to US15/322,077 priority Critical patent/US20170139684A1/en
Priority to EP15811524.6A priority patent/EP3163435A4/en
Priority to CA2952072A priority patent/CA2952072A1/en
Publication of WO2015196780A1 publication Critical patent/WO2015196780A1/zh

Links

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
    • G06F30/00—Computer-aided design [CAD]
    • G06F30/10—Geometric CAD
    • G06F30/18—Network design, e.g. design based on topological or interconnect aspects of utility systems, piping, heating ventilation air conditioning [HVAC] or cabling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/10—Requirements analysis; Specification techniques
    • 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/34—Graphical or visual programming

Definitions

  • the invention relates to the technical field of software engineering, in particular to a general modeling method and a computer program product based on a system metamodel to construct a system model.
  • a system is a collective term for things in the real world or in the world of imagination.
  • a system model is a structured description of people's knowledge about things, especially complex ones.
  • System modeling is the activity or process of constructing a system model based on the laws and characteristics of objective things.
  • system modeling has been widely used in various social practice activities such as scientific research, engineering, military, and production.
  • the system metamodel is a model of the system model, an abstraction of the system model, providing a precise definition of the building elements and rules needed to create a rigorous system model.
  • the system metamodel is used as a specification for system modeling and plays a decisive role in the quality of the system model and the efficiency of system modeling.
  • UML Unified Modeling Language
  • UML is the current industry standard for object-oriented visual modeling languages.
  • UML is a software meta-model for software development developed with the object-oriented software method, it is actually used by people as a system metamodel.
  • UML has the following drawbacks: First, no modeling method is provided; UML explicitly states that it does not provide a modeling method, but is a description language for modeling methods. UML is used by program developers.
  • UML is intended to be designed for programmers. Its complexity and confusion are not only difficult for programmers to master, but also incomprehensible by domain personnel, far from meeting the needs of modeling practice.
  • the sysML language for the visual modeling language for engineering is born out of UML, and the above comments apply.
  • the ontology meta-model has recently become a research hotspot.
  • the ontology is defined as a clear specification of the conceptual model.
  • the ontology metamodel is based on concept Elements, using formal language as a means of description and formal logic as a means of reasoning, can effectively identify concepts that are commonly recognized in the field and give a clear definition of the relationship between these concepts and concepts.
  • the ontology meta-model focuses on the establishment of conceptual systems, application and information knowledge classification, expression, and reasoning.
  • the modeling metaphor of ontology metamodel theory includes concepts, relationships, functions, axioms, and examples.
  • the international standard ISO/IEC19763 Interoperability Metamodel Framework MFI
  • ISO/IEC19763 Interoperability Metamodel Framework MFI
  • the ontology and process ontology are the core knowledge management norms, and the information sharing norm with the ontology registration metamodel and the process model registration metamodel as the core
  • the Chinese patent application 200610125050.8 provides the ontology registration metamodel and process model registration based on ISO/IEC19763.
  • the metamodel and Protege ontology description tools are applied to the WEB service for domain requirements modeling. From the point of view of system modeling, first, the ontology meta-model focuses on knowledge management and information sharing, and does not focus on general-purpose system modeling. Second, the ontology meta-model adopts formal language and is not easy to be used in common fields. Personnel mastered.
  • the object of the present invention is achieved by the following means.
  • the sequence code contains a set of instructions that can be executed by the processor of the computer.
  • the system model is constructed based on the system metamodel, and the system metamodel used includes the following components:
  • Hierarchical module Describes the hierarchical model of the system model in a tree structure with the component type as a node, and uses it as a template in the actual system modeling environment to configure a hierarchical model that forms the system model;
  • the hierarchical model refers to the system model a hierarchical relationship consisting of a component type as a node;
  • the component type refers to a set of component instances having the same external feature; and
  • a tree structure in which the component type is a node in the system model is called a hierarchical tree;
  • Interface module The interface model is described in three parts: attribute set, function set, and event set. It is used as a template in the actual system modeling environment to configure the interface model.
  • the interface model refers to the external features of the component type.
  • the functions in the function set include two functions: algorithm function and process function; the implementation of the algorithm function is provided by the algorithm model; and the implementation of the process function is provided by the combination of the process model and the transmission model;
  • Algorithm module The algorithm model is described by a tree structure with arithmetic elements as nodes, and is used as a template in the actual system modeling environment to configure an algorithm model.
  • the algorithm model refers to an algorithm description that implements functions by using an arithmetic combination;
  • the arithmetic unit refers to a pre-implemented component having a specific function;
  • Process module a process description model is described by combining activities as nodes, and is used as a template in an actual system modeling environment to configure a process model; the process model refers to a way of implementing functions by using a combination of activities; Refers to one execution of the function;
  • Transmission module a transmission model is used to describe the transmission model, and is used as a template in the actual system modeling environment to configure a transmission model; the transmission model refers to the data transmission of the activity involved. a transfer relationship; the transfer in the transfer set is a data transfer relationship between one attribute and another attribute;
  • Construction level model The level module reads the hierarchical model operation information sent from the actual system modeling environment, and the hierarchical model operation information refers to the hierarchical tree such as newly created component type, added component type, selected component type, Name the component type, delete the operation information of the component type, and the hierarchical module responds to the hierarchical model operation information to perform a corresponding operation on the component type node of the hierarchical tree to obtain the hierarchical model;
  • step 2) Constructing an interface model: constructing an interface model one by one for the component types in the hierarchical model obtained in step 1), and the construction steps of each interface model include: the interface module reads the interface model operation information sent from the actual system modeling environment; The operation information of the interface model refers to operation information such as newly created, named, and deleted attributes, functions, and events; the interface module obtains an interface model by performing corresponding operations on the interface model operation information; and the algorithm model for implementing the algorithm function is performed by step 3 Construction, the process model for implementing the process function is constructed by step 4);
  • step 2) Constructing an algorithm model: constructing an algorithm model one by one for the algorithm functions obtained in step 2), and the construction steps of each algorithm model include: the algorithm module reads the operation information of the algorithm model sent from the actual system modeling environment;
  • the process model is constructed one by one for the process functions obtained in step 2), and the process steps of each process model include: the process module reads the process model operation information sent from the actual system modeling environment;
  • each transmission model includes: the transmission module reads the transmission model operation information sent from the actual system modeling environment; the transmission model operation information refers to performing, for example, adding transmission, selecting transmission, deleting transmission Operation information, the transmission module responds to the transmission model operation information and performs corresponding operations to obtain a transmission model;
  • the system metamodel uses the following modeling rules:
  • the process module and transport module combination is a general way of describing and configuring the function implementation; the algorithm module is used as an alternative process module and transport module if and only if the operator is only used for combination description and configuration implementation functions. A simplified way of combining.
  • the system metamodel recursively describes the system model with the parent-child structure as the smallest recursive unit.
  • the parent-child structure refers to a parent-child relationship structure in the hierarchical tree composed of the component type node and all its child component type nodes;
  • step 2) can only be selected among the algorithm function and the flow function.
  • the step 3) constructing the algorithm model in the algorithm model operation information refers to the operation information such as adding an arithmetic element, selecting an arithmetic element, naming an arithmetic element, deleting an arithmetic element, adding a value, selecting a value, and deleting a value;
  • the algorithm model is obtained by performing corresponding operations in response to the algorithm model operation information.
  • the arithmetic unit includes both a logical function having a logical function and an operational unit having an operation function; the tree structure in which the operator is a node is called an algorithm tree; and the value is a set of two in the attribute set of the algorithm.
  • An assignment relationship between attributes; the attribute set of the algorithm refers to the attribute set of the attribute type of the component type and the attribute set of all the elements in the algorithm model a collection of
  • the step 4) constructs the process model operation information in the process model refers to the operation information such as adding an activity, selecting an activity, naming an activity, and deleting the activity, and the process module responds to the process model operation information to perform a corresponding operation to obtain the process model.
  • the activity includes two types of component activities and arithmetic activities; the component activities are one-time execution of functions of the parent-child structure function set; the parent-child structure function set refers to a function set of the component types involved in the parent-child structure and all of them a set of function sets of sub-component types; the operand activity refers to one execution of functions of the opera; the process model includes two forms of an attribute process model and an event flow model; the process module includes an attribute flow module And an event flow module in two forms; the attribute flow module describes a property flow model in a process tree structure, the process tree is a tree structure composed of activities as nodes; the event flow module is associated with an event The set describes the event process model as a structure; an event association in the event association set is an event between the parent and child structure event sets, and an operand activity or a component activity.
  • the parent-child structure event set refers to a collection of event sets of the component types involved in the parent-child structure and event sets of all of the child component types.
  • the attribute associated with the transmission is limited to the attribute in the parent-child structure attribute set;
  • the active attribute refers to the attribute of the component in which the activity is located;
  • the parent-child structure attribute set refers to the type of the component involved in the parent-child structure a collection of attribute sets and attribute sets of all of its subcomponent types;
  • the present invention completes the construction of the system model by using the hierarchical model, the interface model, the algorithm model, the process model, and the transmission model as step elements, and provides versatility and ease of use for various fields.
  • Advantages of System Modeling Specification Ben
  • the system model of the invention is executable, the structure is clear, the level is adjustable, and the modeling granularity is controllable; the modeling is convenient for top-down analysis and design, and is also convenient for bottom-up integration, and is suitable for various systems including Modeling software systems and information systems; the number of modeling elements is small, and the modeling method is simple. Even ordinary people in the field who are not familiar with modeling languages and computer programming languages can independently construct system models, eliminating professional modeling personnel. Or the dependency and communication of the program developer, the modeling time is greatly shortened.
  • the present invention has the following significant advantages over the prior art:
  • a system model constructed using the present invention is executable, ie having integrity and sufficient consistency that can be mapped to a computer executable program;
  • the system model constructed by the invention has clear structure, adjustable hierarchy, controllable granularity, and versatility suitable for modeling various systems. It can be used for algorithm modeling, and is also suitable for system rapid prototyping. It is more suitable for large-scale complex system modeling. It is convenient for top-down analysis and design, and it is also convenient to realize integrated integration from bottom to bottom. It is suitable for system integration based on prefabricated components. System extension based on custom components is also suitable for interconnection and interoperability of distributed systems; it is applicable to both actual engineering system modeling and various software systems and information system modeling; it is applicable to simulation modeling of equipment information systems.
  • management information system modeling applicable to desktop software system modeling, embedded device software system modeling, mobile terminal software system modeling, also applicable to LAN software system modeling, WAN software system modeling, also applicable to Cloud computing environment software system modeling; applicable to both application software system modeling and software development environment modeling;
  • Figure 1 shows the system metamodel.
  • Figure 2 shows the system model construction steps.
  • Figure 3 shows the active and parent-child structure feature set.
  • Figure 4 shows the event association and parent-child structure event set.
  • Figure 5 shows the transfer and parent-child structure attribute set.
  • 6 is a computer implementing a general modeling method based on a system metamodel to construct a system model.
  • Figure 7 shows the hierarchical model of the business management YWGL model.
  • Figure 8 shows the business management YWGL interface model.
  • Figure 9 shows the sales management XSGL interface model.
  • Figure 10 shows the production management SCGL interface model.
  • Figure 11 shows the procurement management CGGL interface model.
  • Figure 12 shows the distribution product FXP interface model.
  • Figure 13 shows the direct sales ZXP interface model.
  • Figure 14 shows the main part ZJ interface model.
  • Figure 15 shows the part LJ interface model.
  • Figure 16 shows the finished CP interface model.
  • Figure 17 is a main part processing algorithm model.
  • Figure 18 shows the main part delivery algorithm model.
  • Figure 19 shows the part processing algorithm model.
  • Figure 20 shows the part delivery algorithm model.
  • Figure 21 shows the accessory receiving algorithm model.
  • Figure 22 shows the finished assembly algorithm model.
  • Figure 23 shows the business process flow model.
  • Figure 24 shows the business configuration process model.
  • Figure 25 shows the business operation process model.
  • Figure 26 shows the internal order process model.
  • Figure 27 shows the sales and shipping process model.
  • Figure 28 shows the sales order process model.
  • Figure 29 shows the production planning process model.
  • Figure 30 shows the production implementation process model.
  • Figure 31 shows the production delivery process model.
  • Figure 32 shows the business operation loop transfer model.
  • Figure 33 shows the sequence number assignment transfer model.
  • Figure 34 shows the production example creation transfer model.
  • Figure 35 shows the production configuration traversal transfer model.
  • Figure 36 shows the production number plus one transmission model.
  • Figure 37 shows the production serial number assignment transfer model.
  • Figure 38 shows the purchase instance creation transfer model.
  • Figure 39 shows the procurement configuration traversal transfer model.
  • Figure 40 is a purchase number plus one transfer model.
  • Figure 41 shows the purchase number assignment transfer model.
  • Figure 42 shows the sales sequence numbering assignment transfer model.
  • Figure 43 shows the sales instance creation transfer model.
  • Figure 44 is a sales configuration traversal transfer model.
  • Figure 45 is a sales serial number plus one transmission model.
  • Figure 46 Sales serial number assignment transfer model.
  • Figure 47 is a sales production configuration traversal transfer model.
  • Figure 48 is a sales production configuration comparison transfer model.
  • Figure 49 is a sales production configuration condition transmission model.
  • Figure 50 is a sales production assignment transfer model.
  • Figure 51 shows the sales procurement configuration traversal transfer model.
  • Figure 52 shows the sales purchase configuration comparison transfer model.
  • Figure 53 shows the sales procurement configuration condition transfer model.
  • Figure 54 shows the sales procurement configuration transfer model.
  • Figure 55 shows the production run traversal transfer model.
  • Figure 56 shows the procurement run traversal transfer model.
  • Figure 57 is a sales run traversal transfer model.
  • Figure 58 is a sales production run traversal transfer model.
  • Figure 59 shows the sales production run comparison transfer model.
  • Figure 60 is a sales production operating condition transfer model.
  • Figure 61 shows the production and sales receipt transfer model.
  • Figure 62 shows the production internal order transfer model.
  • Figure 63 is a sales procurement operation traversal transfer model.
  • Figure 64 shows the sales purchase run comparison transfer model.
  • Figure 65 shows the sales procurement operation condition transfer model.
  • Figure 66 shows the purchase and sales receipt transfer model.
  • Figure 67 shows the procurement internal order transfer model.
  • Figure 68 shows the contract statistics transfer model.
  • Figure 69 shows the demand statistics transfer model.
  • Figure 70 shows the order statistics transmission model.
  • Figure 71 shows the shipment statistics transfer model.
  • Figure 72 shows the inventory statistics transfer model.
  • Figure 73 is a receipt statistics transmission model.
  • Figure 74 shows the statistical transmission model of the main part to be worked.
  • Figure 75 is a part transfer statistics transfer model.
  • Figure 76 is an accessory receiving transmission model.
  • Figure 77 shows the finished assembly transfer model.
  • Figure 78 shows the completed delivery transfer model.
  • Figure 79 shows the delivery total statistical transmission model.
  • the computer generally includes a central processing unit, a memory and input/output interface, and a bus.
  • the computer is connected to an input/output device and a storage medium.
  • the central processor is responsible for calculating and controlling the functions of the computer.
  • the central processing unit may contain only one central processing unit or multiple central processing units distributed in one or more places.
  • the memory medium may be comprised of any known computer readable storage medium.
  • the buffer store can temporarily store some program code to reduce the time it takes to extract code from mass storage during program execution.
  • memory can reside in a physical location, be stored by one or more data, or be distributed in multiple physical systems in different forms.
  • memory can be distributed over a local area network (LAN) or wide area network (WAN).
  • the memory may contain program code that implements a generic modeling method that constructs a system model based on the system metamodel, and may include other code not shown in the figure, such as an operating system.
  • the input and output interfaces allow the computer to exchange information with the storage medium or another computer.
  • Input and output devices include any known external device type, such as display devices, keyboards, mice, printers, stereos, handheld devices, masks, and the like.
  • the bus provides communication connections between various components within the computer, including electrical, optical, wireless, and the like.
  • Storage media includes any known computer readable storage media such as a magnetic disk, optical disk, and the like.
  • a storage medium may contain a generic system model instance constructed from one or more system metamodels. Those skilled in the art will appreciate that the present invention may be implemented as an all-hardware product, an all-software product, or a combination of hardware and software commonly referred to as a module.
  • the invention can be implemented as a computer program product embodied on a computer readable medium.
  • the computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or combination of the foregoing. Examples of more specific non-exhaustive computer readable storage media are as follows: random access memory (RAM), read only memory (ROM), rewritable programmable read only memory (EPROM or flash), removable read only memory ( CD-ROM), optical storage device, magnetic storage device, and a combination of any of the foregoing.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash rewritable programmable read only memory
  • CD-ROM removable read only memory
  • optical storage device magnetic storage device, and a combination of any of the foregoing.
  • Computer program code implementing the methods of the present invention can be written in one or more programming languages, including, for example, Java, Small, C++, C#, etc., and a process oriented programming language such as C.
  • the program code can run on a personal computer, handheld device or LAN LAN, WAN WAN.
  • An embodiment is to construct a business management YWGL model. It should be noted that this embodiment is merely a specific application example of the present invention, and the technical essence of the present invention is not limited by this example.
  • Embodiment Constructing a Business Management YWGL Model
  • the sales management module collects the contract quantity and shipment quantity of the direct sales and sales of each product, receives the delivery information of the production management module and the procurement management module, and purchases the production management module according to the sales status.
  • the management module issues order information; the production management module and the procurement management module receive the order information of the sales management module, start the internal process, and submit the delivery information to the sales management module.
  • Figure 7 shows the hierarchical model of the business management YWGL model after completion.
  • the detailed process of constructing the hierarchical model of this embodiment is given below:
  • the hierarchical module creates a component type as the root node of the hierarchical tree for the business management YWGL model, and the component type on the root node is simply referred to as the root component type;
  • the hierarchical module receives operational information of the selected root component type sent from the actual system modeling environment, and the hierarchical module responds to the aforementioned operational information to set the root component type to the involved component Type; the hierarchical module receives the operation information sent from the actual system modeling environment to modify the name of the component type to "business management YWGL", and the hierarchical module responds to the aforementioned operation information, and changes the name of the root component type to " Business Management YWGL”; the name of the root component type is simply referred to as the business management YWGL component type, and other component types are deduced by analogy; the hierarchical module receives the number of component component instances sent from the actual system modeling environment to 1 Operation information, the level module responds to the foregoing operation information, and sets the number of component instances of the business management YWGL component type to 1;
  • the hierarchical module receives and responds to operational information sent from the actual system modeling environment, adding a sub-component type for the business management YWGL component type; the hierarchical module sets the aforementioned sub-component type to the component type involved; the hierarchical module receives and In response to the operational information sent from the actual system modeling environment, the name of the component type is modified to "sales management XSGL"; the number of component instances of the sales management XSGL component type is set to 1;
  • a sub-component type with a component instance number of 0 is added for the business management YWGL component type: production management SCGL, procurement management CGGL;
  • a sub-component type with a component instance number of 1 is added for the production management SCGL component type: main component ZJ, part LJ, finished product CP;
  • Figure 8 shows the interface model of the business management YWGL component type after completion.
  • the name of the component type is referred to as the business management YWGL interface model.
  • the names of other interface models are similar.
  • the construction process of the business management YWGL interface model is as follows:
  • the hierarchical module receives and responds to operational information sent from the actual system modeling environment, and sets the business management YWGL component type to the type of component involved;
  • the interface module receives and responds to the operational information sent from the actual system modeling environment, and performs the corresponding operation: adding a new attribute to the business management YWGL interface model; setting the aforementioned new attribute to the attribute in question; and the data type of the attribute in question Modify to bool; modify the attribute name of the attribute to the business operation state, the attribute name is the business operation state attribute referred to as the business operation state attribute, the subsequent attribute and so on, no longer repeat; the business operation state attribute attribute The value is set to true;
  • attributes to the business management YWGL interface model production normal state attribute, data type is bool, attribute value is true; production variety number attribute, data type is int, attribute value is 3; purchase item number attribute, data type is Int, attribute value is 2; sales item number attribute, data type is int, attribute value is 0; product serial number attribute, data type is int, attribute value is 0; constant zero attribute, data type is int, attribute value is 0 ; comparison result attribute, the data type is bool, the attribute value is true;
  • the interface module receives and responds to the operational information sent from the actual system modeling environment, and completes the corresponding operation: adding a process function to the business management YWGL interface model; setting the foregoing function as the function involved; modifying the name of the function in question to In the main business process, the function named as the main business process is referred to as the main business process function, and the subsequent functions are based on this type. Push, no longer repeat;
  • Figure 9 shows the sales management XSGL interface model after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set product name attribute, data type is string, attribute value is sales item; product serial number attribute, data type is int, attribute value is 1; inventory quantity attribute, data type is int, attribute value is 0; minimum inventory attribute, The data type is int, the attribute value is 0; the contract quantity attribute, the data type is int, the attribute value is 0; the goods receipt quantity attribute, the data type is int, the attribute value is 0; the order quantity attribute, the data type is int, the attribute Value is 0; shipment quantity attribute, data type is int, attribute value is 0; shipment total attribute, data type is int, attribute value is 0; demand quantity attribute, data type is int, attribute value is 0;
  • Function set three process functions: internal ordering, sales and shipping, and sales ordering.
  • Figure 10 shows the production management SCGL interface model after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set product name attribute, data type is string, attribute value is self-research product; product serial number attribute, data type is int, attribute value is 1; order quantity attribute, data type Type is int, attribute value is 0; completion quantity attribute, data type is int, attribute value is 0; delivery quantity attribute, data type is int, attribute value is 0; delivery total attribute, data type is int, attribute The value is 0;
  • Function set three process functions: production planning, production implementation, and production delivery.
  • Figure 11 shows the procurement management CGGL interface model after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set product name attribute, data type is string, attribute value is purchase item; product serial number attribute, data type is int, attribute value is 1; quantity to be purchased attribute, data type is int, attribute value is 0; purchase quantity Attribute, data type is int, attribute value is 0; delivery quantity attribute, data type is int, attribute value is 0; delivery total attribute, data type is int, attribute value is 0;
  • Feature set Two algorithm functions: purchase implementation and purchase delivery.
  • Figure 12 shows the finished product FXP interface model after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set Minimum inventory attribute, data type is int, attribute value is 5; contract quantity attribute, data type is int, attribute value is 12; shipment quantity attribute, data type is int, attribute value is 8.
  • Figure 13 shows the ZXP interface model of the direct sales product after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set Minimum stock attribute, data type is int, attribute value is 6; contract quantity attribute, data type is int, attribute value is 3; shipment quantity attribute, data type is int, attribute value is 4.
  • Figure 14 shows the ZJ interface model of the main component after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set the main part name attribute, the data type is string, the attribute value is the main part; the number of work is required, the data type is int, the attribute value is 0; the number of completion attributes, the data type is int, the attribute value is 0; Number attribute, data type is int, attribute value is 0; delivery total attribute, data type is int, attribute value is 0;
  • Function set There are two algorithm functions for main part processing and main parts delivery.
  • Figure 15 shows the LJ interface model of the part after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set part name attribute, data type is string, attribute value is part; number of work to be worked, data type is int, attribute value is 0; number of completion attribute, data type is int, attribute value is 0; delivery quantity attribute , the data type is int, the attribute value is 0; Total quantity attribute, the data type is int, and the attribute value is 0;
  • Function set Two algorithm functions for part processing and part delivery.
  • Figure 16 shows the finished CP interface model after completion.
  • the construction process is similar to the "Business Management YWGL Interface Model", which reads as follows:
  • Attribute set the name of the finished product, the data type is string, the attribute value is the finished product; the number of work is required, the data type is int, the attribute value is 0; the number of completion attributes, the data type is int, the attribute value is 0; single set of main parts Quantity attribute, data type is int, attribute value is 2; single set part quantity attribute, data type is int, attribute value is 6; main part inventory attribute, data type is int, attribute value is 0; main item receipt quantity attribute , the data type is int, the attribute value is 0; the part inventory attribute, the data type is int, the attribute value is 0; the part receipt quantity attribute, the data type is int, the attribute value is 0;
  • Function set two algorithm functions: accessory receiving and finished product assembly.
  • Figure 17 shows the main part machining algorithm model after completion.
  • the construction process is as follows:
  • the hierarchical module receives and responds to operational information sent from the actual system modeling environment, setting the main component ZJ component type to the component type involved;
  • the interface module receives and responds to the operation information sent from the actual system modeling environment, and sets the main part processing function as the function involved; according to the function name, the algorithm model for realizing the main part processing function is referred to as the main part processing algorithm model;
  • the algorithm model of other functions is analogous, and will not be described again;
  • the algorithm module receives and responds to the operation information sent from the actual system modeling environment, and completes the corresponding operation: adding an assignment operator, naming the main component to be completed, and assigning the operand; establishing the number of labors from the main component ZJ component type The value of the input attribute of the attribute to the completion value of the main component is completed; the value of the attribute from the output attribute of the completion value of the main component to the ZJ component type of the main component is established;
  • adding a subtraction operator naming the main component to be cleared to the operator; establishing a value of the subtracted attribute from the number of work-receiving attributes of the main component ZJ component type to the work-piece zero-clearing element of the main component; Establishing the value of the subtraction attribute from the number of work-receiving attributes of the main component ZJ component type to the work-piece zero-clearing element of the main component; establishing the difference attribute from the main component to be cleared to the main component ZJ component type The value of the number of employees to be worked;
  • Figure 18 shows the main part delivery algorithm model after completion.
  • the construction process is similar to the "main part processing algorithm model", which reads as follows:
  • An assignment operator named as the main piece completion delivery operator; the operand has the following values: from the completion number attribute of the main part ZJ component type to the input attribute of the main piece completion delivery unit, from the completion of the main piece The output attribute of the goods calculation element to the delivery quantity attribute of the main piece ZJ component type;
  • a subtraction operator named as the main piece completion zeroing operator; the operand has the following values: from the number of completions of the ZJ component type of the main component to the attribute of the subtotal of the completion of the main component, from the main component The number of completion attributes of the ZJ component type to the subtraction attribute of the completion zeroing element of the main piece, from the difference attribute of the completion element of the main piece to the number of completions of the ZJ component type of the main part;
  • An addition operator named as the total delivery amount of the main component; the operand has the following values: from the number of completions of the ZJ component type of the main component to the additive attribute of the total delivery quantity of the main component, The total amount of delivery of the main part ZJ to the add-on attribute of the total delivery quantity of the main part, from the sum attribute of the main part delivery total to the total quantity attribute of the main part ZJ component type.
  • Figure 19 shows the model of the part processing algorithm after completion.
  • the construction process is similar to the "main part processing algorithm model", which reads as follows:
  • An assignment operator is named as the part-to-work completion assignment operator; the operand has the following values: from the number of work-receiving attributes of the part LJ component type to the input attribute of the part-finished assignment-valued operator, from the part to be completed Assign the output attribute of the operand to the number of completions of the part LJ component type;
  • a subtraction operator named as a part-to-work zero-clearing element; the operand has the following values: from the number of work-receiving attributes of the part LJ component type to the attribute of the fractional part of the part-for-work zero-clearing element, from the part LJ The number of work-receiving attributes of the component type to the sub-quantity attribute of the part-to-work zero-clearing element, from the difference attribute of the part-to-work zero-clearing element to the number-of-work attribute of the part LJ component type.
  • Figure 20 shows the part delivery algorithm model after completion.
  • the construction process is similar to the "main part processing algorithm model", which reads as follows:
  • An assignment operator named as the part completion delivery operator; the operand has the following values: from the completion number attribute of the part LJ component type to the input attribute of the part completion delivery element, from the part completion delivery operator Output attribute to the delivery quantity attribute of the part LJ component type;
  • a subtraction operator named as the part completion zeroing operator; the operand has the following values: from the number of completions of the part LJ component type to the attribute of the part of the finished zeroing operator, the number of pieces from the part LJ To the fractional attribute of the part completion zeroing operator, from the difference attribute of the part completion zeroing operator to the number of completions of the part LJ component type;
  • An addition operator named as the part delivery total operator; the operand has the following values: from the number of completions of the part LJ component type to the addend attribute of the part delivery total operator, from the part LJ The add-in attribute of the total quantity attribute to the total quantity of parts delivery, from the sum attribute of the total quantity of parts delivery to the total quantity attribute of the part LJ component type.
  • Figure 21 shows the accessory receiving algorithm model after completion.
  • the construction process is similar to the "main part processing algorithm model", which reads as follows:
  • an addition operator named as the main component receiving the operand; the operand has the following values: from the main component inventory attribute of the finished CP component type to the addend attribute of the main component receiving the operand, from the master of the finished CP component type
  • the goods receipt attribute of the piece receives the addend attribute of the main unit receiving the operand, and receives the sum attribute of the operand from the main part to the main item stock attribute of the finished CP component type;
  • An addition operator named as a part receiving operand; the operand has the following values: from the part inventory attribute of the finished CP component type to the addend attribute of the part receiving element, and the received quantity of the part from the finished CP component type
  • the attribute to the part receives the addend attribute of the operand, and receives the sum attribute of the operand from the part to the part stock attribute of the finished CP component type.
  • Figure 22 shows the finished product assembly algorithm model after completion.
  • the construction process is similar to the "main part processing algorithm model", and its contents are as follows:
  • a multiplication element named as the assembly principal element; the element has the following values: from the number of work-receiving attributes of the finished CP component type to the multiplicand attribute of the assembly principal element, from the finished CP component type Set the number of main pieces to the multiplier attribute of the assembly principal element;
  • a subtraction operator named as the assembly main component inventory operator; the operand has the following values: from the main component inventory attribute of the finished CP component type to the reduced attribute of the assembly main component inventory operator, calculated from the assembly principal The attribute of the product of the element to the subordinate attribute of the assembly main component inventory element, from the difference attribute of the assembly main component inventory element to the main part inventory attribute of the finished CP component type;
  • a multiplication element named as an assembly part operator; the element has the following values: from the number of work-receiving attributes of the finished CP component type to the multiplicand attribute of the assembly part, from a single set of finished CP component types The multiplier attribute of the number attribute to the assembly part operand;
  • a subtraction operator named as the assembly part inventory operator; the operand has the following values: from the part inventory attribute of the finished CP component type to the subtracted attribute of the assembly part inventory element, from the product of the assembly part operator The attribute of the number attribute to the fractional attribute of the assembly part inventory element, from the difference attribute of the assembly part inventory element to the part inventory attribute of the finished CP component type;
  • An assignment operator named as the finished completion operator; the operator has the following values: from the number of work-receiving properties of the finished CP component type to the input property of the finished completion operator, from the output attribute of the finished completion operator to the finished CP The number of completions of the component type;
  • a subtraction operator is named as the finished product to be cleared by the operator; the operator has the following values: from the number of work-receiving properties of the finished CP component type to the subtracted property of the finished work-clearing zero operator, from the finished CP The number of work-receiving attributes of the component type to the subtraction attribute of the finished product zero-clearing element, from the difference attribute of the finished product clearing arithmetic element to the number of labor-receiving attributes of the finished CP component type.
  • Figure 23 shows the business process flow model of the business management YWGL component type after completion.
  • the construction process is as follows:
  • the hierarchical module receives and responds to operational information sent from the actual system modeling environment, setting the business management YWGL component type to the component type involved;
  • the interface module receives and responds to the operation information sent from the actual system modeling environment, and sets the business main process function as the function involved;
  • the process model of the business main process function is simply referred to as the business main process flow model according to the function name; other functions The process model and so on, no longer repeat them;
  • the process module first creates a sequential activity for the business master process flow model as the root activity; the sequential activity is a logical activity with sequential execution functions; the sequential activity has a start node, an end node, and a start node and an end Between nodes, multiple nodes are sequentially provided to add other activities; the root activity is called the business main process root activity according to the process model name; it should be noted that the process module creates a root activity for each process model, root The naming of activities and so on will not be repeated;
  • the process module receives and responds to the operation information sent from the actual system modeling environment, and adds an activity based on the service configuration function of the business management YWGL component type; the function name executed according to the activity is simply referred to as the service configuration activity, and subsequent activities. And so on, no longer repeat; the process module responds to the foregoing operational information, adding a service configuration activity in the main process root activity of the business;
  • a loop activity is added to the main business process root activity, which is simply referred to as a business operation loop activity;
  • the loop activity is an arithmetic activity with a loop function;
  • the loop activity internally includes a loop sequence,
  • the loop sequence consists of multiple nodes that can accommodate activities;
  • an activity based on the business operation function of the business management YWGL component type is added to the cyclic sequence of the business operation cycle activity, which is simply referred to as a business operation activity;
  • Figure 24 shows the business configuration process model of the business management YWGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • the assignment operator activity is an arithmetic activity with an assignment function
  • adding an instance to the business configuration root activity to create an arithmetic activity referred to as a production instance creation activity
  • the instance creation arithmetic activity is an arithmetic activity with a function of creating a component instance
  • adding a traversal activity in the business configuration root activity referred to as a production configuration traversal activity
  • the traversal activity internal Include a sequence of nodes, each node accommodating an activity; the traversal activity refers to an arithmetic activity that performs a sequence of nodes for each component instance of the determined component type;
  • Adding an additional activity in the traversal sequence of the production configuration traversal activity referred to as a production serial number plus an activity
  • the additional activity refers to a pre-made arithmetic activity having an integer value plus one function
  • the production serial number assignment activity Adding an assignment activity to the traversal sequence
  • Add an instance to create an arithmetic activity in the business configuration root activity referred to as a procurement instance creation activity
  • add a traversal activity in the business configuration root activity referred to as a procurement configuration traversal activity
  • Adding an additional activity in the traversal sequence of the procurement configuration traversal activity referred to as the purchase serial number plus one activity
  • adding an assignment activity in the traversal sequence of the purchase configuration traversal activity referred to as the purchase serial number assignment activity;
  • Add an assignment operator activity in the business configuration root activity referred to as the sales serial number clear assignment activity
  • add an instance creation transaction activity in the business configuration root activity referred to as the sales instance creation activity
  • add in the business configuration root activity An traversal activity, referred to as a sales configuration traversal activity;
  • Adding an additional activity in the traversal sequence of the sales configuration traversal activity referred to as the sales serial number plus one activity
  • adding an assignment activity in the traversal sequence of the sales configuration traversal activity referred to as the sales serial number assignment activity
  • in the sales configuration traversal activity Add a traversal activity in the traversal sequence, referred to as the sales production configuration traversal activity;
  • the sales production configuration comparison activity Adding the same comparison activity in the traversal sequence of the sales production configuration traversal activity, referred to as the sales production configuration comparison activity; the same comparison activity is a pre-made arithmetic activity having the function of comparing whether the two input items are the same; Adding a conditional activity, referred to as a sales production configuration condition activity, to the traversal sequence of the sales production configuration traversal activity; the conditional activity is a pre-made logical activity with a conditional selection function;
  • Adding a same comparison activity in the traversal sequence of the sales procurement configuration traversal activity referred to as a sales procurement configuration comparison activity
  • adding a condition activity in the traversal sequence of the sales procurement configuration traversal activity referred to as a sales procurement configuration condition activity
  • Figure 25 shows the business operation process model of the business management YWGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • Adding an activity based on the production planning function of the production management SCGL component type to the traversal sequence of the production operation traversal activity referred to as the production planning activity; adding a production implementation based on the production management SCGL component type in the traversal sequence of the production operation traversal activity Functional activities, referred to as production implementation activities; adding an activity based on the production management SCGL component type production delivery function in the traversal sequence of production operation traversal activities, referred to as production delivery activities;
  • Adding an activity based on the procurement management function of the procurement management CGGL component type to the traversal sequence of the procurement operation traversal activity referred to as the procurement implementation activity
  • adding a purchase delivery based on the procurement management CGGL component type in the traversal sequence of the procurement operation traversal activity Functional activities, referred to as purchasing delivery activities;
  • Adding a same comparison activity in the traversal sequence of the sales production traversal activity referred to as the sales production operation comparison activity; adding a condition activity in the traversal sequence of the sales production operation traversal activity, referred to as the sales production operation condition activity;
  • Adding a same comparison activity in the traversal sequence of the sales procurement operation traversal activity referred to as the sales procurement operation comparison activity
  • adding a condition activity in the traversal sequence of the sales procurement operation traversal activity referred to as the sales procurement operation condition activity;
  • the activity of managing the sales and shipping functions of the XSGL component type is referred to as the procurement and sales shipping activity; adding an activity based on the internal order function of the sales management XSGL component type in the true branch of the sales procurement operation condition activity, referred to as the procurement internal Ordering activities.
  • Figure 26 shows the internal order process model of the sales management XSGL component type after completion.
  • the construction process is similar to the "business main process flow model", which reads as follows:
  • the addition activity is an arithmetic activity with an addition function
  • the internal ordering root activity Add an addition activity, referred to as the demand statistics activity; add a subtraction activity in the internal order root activity, referred to as the order statistics activity; the subtraction activity is an arithmetic activity with a subtraction function.
  • Figure 27 shows the sales and shipping process model of the sales management XSGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • Add an addition activity in the sales and shipping root activity referred to as the shipping statistics activity
  • add a subtraction activity in the sales shipping root activity referred to as the inventory statistical activity
  • the subtraction activity is an arithmetic activity with a subtraction function .
  • Figure 28 shows the sales order process model of the sales management XSGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • Figure 29 shows the production planning process model of the production management SCGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • the multiplication activity is an arithmetic activity with multiplication function; adding another multiplication activity in the production plan root activity, referred to as part waiting Statistics activities.
  • Figure 30 shows the production implementation process model of the production management SCGL component type after completion.
  • the construction process is similar to the "business main process flow model", and its contents are as follows:
  • Adding an activity of the main part processing function based on the main part ZJ component type in the production implementation root activity referred to as the main part processing activity; adding an activity of the main part delivery function based on the main part ZJ component type in the production implementation root activity, Referred to as the main parts delivery activity; adding a part processing function based on the part LJ component type in the production implementation root activity, referred to as part processing activity; adding a part delivery function based on the part LJ component type in the production implementation root activity , referred to as the part delivery activity; adding an activity based on the receiving function of the finished CP component type in the production implementation root activity, referred to as accessory receiving; adding an activity based on the finished component assembly function of the finished CP component type in the production implementation root activity, Referred to as the finished assembly activities.
  • Figure 31 shows the production delivery process model of the production management SCGL component type after completion.
  • the construction process is similar to the “business main process flow model”, which reads as follows:
  • Add an assignment activity in the production delivery root activity referred to as the completion delivery activity; add an addition activity in the production delivery root activity, referred to as the total delivery statistics activity.
  • Figure 32 shows the completed business operation loop transfer model.
  • the construction process is as follows:
  • the hierarchical module receives and responds to operational information sent from the actual system modeling environment, setting the business management YWGL component type to the component type involved;
  • the interface module receives and responds to operational information sent from the actual system modeling environment, and sets the business main process function to the function involved;
  • the process module receives the operation information sent by the actual system modeling environment, and sets the business operation cycle activity as the activity involved; the transmission module constructs the transmission model with the activity involved, and forms a transmission model of the business operation cycle activity;
  • the transmission model of the business operation cycle activity is simply referred to as the business operation cycle transmission model according to the name of the activity, and other transmission models are not described in detail.
  • the transport module receives and responds to operational information sent from the actual system modeling environment, establishing a transfer of status attributes from the business operational state attribute of the business management YWGL component type to the business operational cycle activity; the state of the business operational cycle activity
  • the attribute refers to the short name of the status attribute of whether the business operation loop activity control is running, and is a Boolean variable; the meanings of other subsequent activity attributes are similar, and will not be described again;
  • Figure 33 shows the serial number clear assignment transfer model after completion.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 34 shows the completed production instance creation transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its contents include the following transfers:
  • Figure 35 is a completed production configuration traversal transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 36 shows the completed production serial number plus one transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its content includes the following transmissions:
  • Fig. 37 is a completed production serial number assignment transmission model, and its construction process is similar to the "business operation loop transmission model", and its content includes the following transmission:
  • Figure 38 shows the completed purchase instance creation transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transfers:
  • Figure 39 shows the completed procurement configuration traversal transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 40 shows the completed purchase serial number plus one transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 41 shows the completed purchase number assignment transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its contents include the following transfers:
  • Figure 42 shows the completed sales order number clear assignment transfer model, and its construction process is similar.
  • "Business Operation Loop Transfer Model” the content of which includes the following transmissions:
  • Figure 43 shows the completed sales instance creation transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transfers:
  • the type attribute of the activity is created from the name of the sales management XSGL component type to the sales instance; from the sales item number attribute of the business management YWGL component type to the quantity attribute of the sales instance creation activity.
  • Figure 44 shows the completed sales configuration traversal transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transfers:
  • Figure 45 shows the completed sales number plus one transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its contents include the following transmissions:
  • Figure 46 is a completed sales number assignment transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 47 is a completed sales production configuration traversal transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 48 shows the completed sales production configuration comparison transmission model.
  • the construction process is similar to the "business operation cycle transmission model", and its content includes the following transmissions:
  • Figure 49 is a completed sales production configuration condition transmission model, the construction process is similar to the "business operation loop transmission model", the content of which includes the following transmission:
  • Figure 50 shows the completed sales production assignment transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its contents include the following transfers:
  • Figure 51 shows the completed sales procurement configuration traversal transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 52 shows the completed sales and purchase configuration comparison transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 53 shows the completed sales procurement configuration condition transmission model.
  • the construction process is similar to the “business operation loop transmission model”, and its content includes the following transmissions:
  • Figure 54 shows the completed sales procurement configuration transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 55 is a completed production run traversal transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 56 shows the completed procurement operation traversal transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 57 is a completed sales operation traversal transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 58 is a completed sales production operation traversal transfer model, the construction process is similar to the "business operation loop transfer model", the content of which includes the following transmission:
  • Figure 59 shows the completed sales and operation run comparison transfer model.
  • the construction process is similar to the "business operation cycle transfer model", and its content includes the following transmissions:
  • Fig. 60 is a completed sales production operation condition transmission model, and the construction process is similar to the "business operation loop transmission model", and the content thereof includes the following transmission:
  • Figure 61 shows the completed production and sales receipt transfer model.
  • the construction process is similar to the “business operation cycle transfer model”, and its content includes the following transmissions:
  • Figure 62 shows the completed production internal order transfer model.
  • the construction process is similar to the “business operation cycle transfer model”, and its content includes the following transmissions:
  • Figure 63 shows the completed sales procurement operation traversal transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its content includes the following transmissions:
  • Figure 64 shows the completed sales and purchase operation comparison transfer model.
  • the construction process is similar to the "business operation cycle transfer model", and its content includes the following transmissions:
  • Fig. 65 is a completed sales procurement operation condition transmission model, and its construction process is similar to the "business operation loop transmission model", and its content includes the following transmission:
  • Figure 66 shows the completed purchase and sales receipt transfer model.
  • the construction process is similar to the “business operation cycle transfer model”, and its content includes the following transmissions:
  • Figure 67 shows the completed internal order transfer model after completion.
  • the construction process is similar to the “business operation loop transfer model”, and its content includes the following transmissions:
  • Figure 68 shows the completed contract statistics transmission model.
  • the construction process is similar to the “business operation loop transmission model”, and its content includes the following transmissions:
  • Figure 69 shows the completed demand statistics transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its content includes the following transmissions:
  • Figure 70 shows the completed ordering statistics transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its content includes the following transmissions:
  • Figure 71 shows the completed shipment statistics transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its content includes the following transmissions:
  • Figure 72 shows the completed inventory statistics transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its contents include the following transfers:
  • Figure 73 shows the completed receipt statistics transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its contents include the following transmissions:
  • Figure 74 shows the completed master-study statistical transmission model.
  • the construction process is similar to the “business operation loop transmission model”, and its content includes the following transmissions:
  • Figure 75 is a completed part of the work-study statistical transmission model, the construction process is similar to the "business operation loop transmission model", the content of which contains the following transmission:
  • Figure 76 shows the completed accessory receiving transmission model.
  • the construction process is similar to the "business operation loop transmission model", and its contents include the following transmissions:
  • Figure 77 shows the finished product assembly transfer model.
  • the construction process is similar to the "business operation loop transfer model", and its contents include the following transfers:
  • Figure 78 shows the completed delivery delivery model.
  • the construction process is similar to the “business operation loop transmission model”, and its content includes the following transmissions:
  • Figure 79 shows the statistical model of the total delivery of delivery after completion.
  • the construction process is similar to that of the industry.
  • the business management YWGL system model consisting of a hierarchical model, an interface model, an algorithm model, a process model, and a transmission model is constructed.
  • This embodiment demonstrates an ordinary manager who does not master the existing complex system modeling language and does not master the computer programming language. It does not need to rely on professional modelers and program developers. How to independently put forward his own ideas about business management.
  • the invention is used to construct an executable business management system model in a short period of time. Not only the construction process is clear, the construction method is simple, and the quality of the system model is significantly higher, and the time spent is significantly less.
  • the manager uses the invention to independently develop the business management system model, and achieves the following obvious effects:

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Geometry (AREA)
  • Computational Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mathematical Analysis (AREA)
  • Mathematical Optimization (AREA)
  • Pure & Applied Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Evolutionary Computation (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

一种基于系统元模型构造系统模型的通用建模方法，在确定系统元模型基础组元后通过以层级模型、接口模型、算法模型、流程模型、传输模型为步骤要素完成系统模型的构造，为各种领域提供具有通用性、易用性优点的系统建模规范；其构造的系统模型具有可执行性，结构清晰，层次可调，建模粒度可控。该建模方法既可以自顶向下分析设计，也可以自底向上实现集成，适用于对包括各种应用环境的软件系统及信息系统的各种系统进行建模，其建模要素数量少、方法简单，缩短了建模时间。

Description

一种基于系统元模型以构造系统模型的通用建模方法 技术领域
本发明涉及软件工程技术领域，具体是一种基于系统元模型以构造系统模型的通用建模方法和计算机程序产品。
背景技术
系统是现实世界或想象世界的事物的统称，系统模型是人们关于事物特别是复杂事物的知识的结构化描述。系统建模是人们根据客观事物的规律和特征构造系统模型的活动或过程。早在软件出现前，系统建模已广泛地存在于科研、工程、军事、生产等各种社会实践活动之中。在信息技术特别是软件技术高度发展的今天，系统建模更成为一种深刻影响社会发展的基础活动。系统建模的质量和效率已经成为能否利用信息技术发挥知识优势获得竞争和发展的关键因素。
在为具体的系统进行建模时，人们发现这些系统模型共享了很多共同的构造，通过对这些模型进行抽象，可以得到这些系统模型都遵循的模型，称为系统元模型。系统元模型是关于系统模型的模型，是系统模型的抽象，提供一套创建严谨的系统模型所需要的构件元素和规则的一个精确定义。系统元模型用作系统建模的规范，对于系统模型的质量和系统建模的效率具有决定性的作用。
正由于系统元模型对系统建模的重要作用，人们一直关注于系统元模型的研究。状态机、petri网等都是典型的代表，但这些系统元模 型通常都是针对某类具体类型问题的，并非一个具有普适性的通用系统模型描述。UML(统一建模语言，Unified Modeling Language)是当前主流的面向对象可视化建模语言工业标准。UML虽然是随着面向对象的软件方法发展起来的面向软件开发的软件元模型，但实际上很大程度上被人们当成系统元模型来使用。对于系统建模来讲，UML存在如下的缺陷：第一，不提供建模方法；UML明确声明不提供建模方法，只是一种建模方法的描述语言。UML是面向程序开发人员使用的，定位于软件开发过程中的制品建模，实际上侧重于基于面向对象方法的程序实现模型的描述，并非是一个超越软件开发的一般性系统建模方法。第二，非执行性是致命缺陷：UML从根本上缺乏严谨的建模理论支撑，这点一直为业界诟病；缺乏完整性和一致性约束致使利用UML构造的系统模型缺乏可执行性，即采用UML描述的模型无法由计算机自动转化成可以运行的软件，要获得可以由计算机运行的软件必须最终由人工通过代码的形式进行编辑；这个缺陷也使得UML只能成为一种系统模型的辅助性表示工具，而不能成为真正的系统元模型；第三，难于理解和使用：UML创造了大量的概念、大量的关系和大量的图。这些概念、关系、图之间的关系又多又松散。UML本意是面向程序人员所设计，其复杂和混乱不仅程序员很难掌握，领域人员更无法理解，远不能满足建模实践的需要。面向工程领域的可视化建模语言sysML语言脱胎于UML，上面的评述同样适用。
随着知识工程的潮流的逐渐兴起，本体元模型最近成为研究热点。本体被定义为概念模型的明确的规范说明。本体元模型以概念为核心 要素，以形式语言为描述手段，以形式逻辑为推理手段，可以有效地确定领域内共同认可的概念，并给出这些概念和概念之间相互关系的明确定义。本体元模型侧重于概念体系的建立，应用与信息知识分类、表达、推理。本体元模型理论的建模元语包括概念、关系、函数、公理、实例，从知识管理的角度提供了一个理论框架；国际标准ISO/IEC19763(互操作性元模型框架MFI)提供了从以概念本体、过程本体为核心知识管理规范，以及以本体注册元模型、过程模型注册元模型为核心的信息共享规范；而中国专利申请200610125050.8提供了基于ISO/IEC19763中的本体注册元模型、过程模型注册元模型和Protege本体描述工具面向WEB服务进行领域需求建模的应用方法。从系统建模的观点来看，第一，本体元模型侧重于知识管理和信息共享，并不侧重于通用性的系统建模；第二，本体元模型采用形式化语言，不容易被普通领域人员掌握。
总的看来，目前还缺乏一种容易被普通领域人员理解和使用的系统元模型，提供通用性的系统建模规范，支持各种领域系统建模活动，以构造具有可执行性的的系统模型。
发明内容
鉴于现有技术的以上缺点，本发明的目的是提供一种基于系统元模型以构造系统模型的通用建模方法，以克服现有技术的以上缺点。
本发明的目的是通过如下的手段实现的。
一种基于系统元模型以构造系统模型的通用建模方法，基于一个含有计算机可读程序代码的计算机可读存储介质，所述计算机可读程 序代码包含一组可以被计算机的处理器所执行的指令，通过对由一个系统元模型定义的数据进行处理，来实现基于系统元模型构造系统模型，其所用的系统元模型包含如下组元：
层级模件：以由构件类型为节点的树形结构描述系统模型的层级模型，并在实际系统建模环境中用作模板以配置形成系统模型的层级模型；所述层级模型是指系统模型中以构件类型为节点组成的层级关系；所述构件类型是指一组具有相同外部特征的构件实例；所述系统模型中以构件类型为节点的树形结构称为层级树；
接口模件：以属性集、功能集、事件集三部分可选结构描述接口模型，并在实际系统建模环境中用作模板以配置形成接口模型；所述接口模型是指构件类型的外部特征；所述功能集中的功能包括算法功能、流程功能两种形式；算法功能的实现方式由算法模型提供；流程功能的实现方式由流程模型与传输模型相组合提供；
算法模件：以算元为节点的树形结构描述算法模型，并在实际系统建模环境中用作模板以配置形成算法模型，所述算法模型是指利用算元组合实现功能的算法描述；所述算元是指预先实现的具有特定功能的构件；
流程模件：以活动为节点进行组合描述流程模型，并在实际系统建模环境中用作模板以配置形成流程模型；所述流程模型是指利用活动组合实现功能的方式描述；所述活动是指功能的一次执行；
传输模件：采用传输集描述传输模型，并在实际系统建模环境中用作模板以配置形成传输模型；所述传输模型是指所涉活动的数据传 递关系；所述传输集中的传输为一个属性和另一个属性之间的数据传递关系；
采用如上所述的五个模件构造系统模型的具体步骤如下：
1)构造层级模型：层级模件读入从实际系统建模环境送来的层级模型操作信息，所述层级模型操作信息是指对层级树进行如新建构件类型、添加构件类型、选择构件类型、命名构件类型、删除构件类型的操作信息，层级模件响应层级模型操作信息对层级树的构件类型节点进行相应操作而获得层级模型；
2)构造接口模型：对步骤1)得到的层级模型中的构件类型逐一构造接口模型，各接口模型的构造步骤包括：接口模件读入从实际系统建模环境送来的接口模型操作信息；所述接口模型操作信息是指对属性、功能、事件进行如新建、命名、删除的操作信息；接口模件响应接口模型操作信息进行相应操作而获得接口模型；实现算法功能的算法模型由步骤3)构造，实现流程功能的流程模型由步骤4)构造；
3)构造算法模型：对步骤2)中得到的算法功能逐一构造算法模型，各算法模型的构造步骤包括：算法模件读入从实际系统建模环境送来的算法模型操作信息；
4)构造流程模型：对步骤2)中得到的流程功能逐一构造流程模型，各流程模型的构造步骤包括：流程模件读入从实际系统建模环境送来的流程模型操作信息；
5)构造传输模型：对步骤4)中得到的流程模型中的活动逐一构 造传输模型，各传输模型的构造步骤包括：传输模件读入从实际系统建模环境送来的传输模型操作信息；所述传输模型操作信息是指进行如添加传输、选择传输、删除传输的操作信息，传输模件响应传输模型操作信息进行相应操作而获得传输模型；
至此，由层级模型、接口模型、算法模型、流程模型、传输模型为要素所构成的系统模型构造完成。
系统元模型采用如下建模规则：
流程模件和传输模件组合是描述和配置功能实现的一般性方式；所述算法模件当且仅当仅使用算元进行组合描述和配置实现功能时用作替代流程模件和传输模件组合的简化方式。
系统元模型以父子结构为最小递归单元，对系统模型进行递归描述。所述父子结构是指层级树中由所涉构件类型节点及其所有子构件类型节点组成的父子关系结构；
步骤2)所述的具体功能，仅能在算法功能和流程功能中选择其一。
所述步骤3)构造算法模型中算法模型操作信息是指如添加算元、选择算元、命名算元、删除算元以及添加传值、选择传值、删除传值的操作信息；算法模件响应算法模型操作信息进行相应操作而获得算法模型。所述算元既包括具有逻辑功能的逻辑算元，也包括具有运算功能的运算算元；所述以算元为节点的树形结构称为算法树；所述传值是算法属性集中的两个属性之间的一个赋值关系；所述算法属性集是指由所涉构件类型的属性集和算法模型中的所有算元的属性集构 成的集合；
所述步骤4)构造流程模型中流程模型操作信息是指如添加活动、选择活动、命名活动、删除活动的操作信息，流程模件响应流程模型操作信息进行相应操作而获得流程模型。所述活动包括构件活动和算元活动两种类型；所述构件活动是父子结构功能集中的功能的一次执行；所述父子结构功能集是指父子结构中所涉构件类型的功能集和其所有子构件类型的功能集构成的集合；所述算元活动是指算元的功能的一次执行；所述流程模型包括属性流程模型和事件流程模型两种形式；所述流程模件包括属性流程模件和事件流程模件两种形式；所述属性流程模件以流程树为结构描述属性流程模型，所述流程树是以活动为节点构成的树形结构；所述事件流程模件以事件关联集为结构描述事件流程模型；所述事件关联集中的一个事件关联，为父子结构事件集中的一个事件，与一个算元活动或一个构件活动之间的关联关系。所述父子结构事件集是指父子结构中的所涉构件类型的事件集及其所有子构件类型的事件集构成的集合。
所述传输所关联的属性，除活动属性外，仅限于父子结构属性集中的属性；所述活动属性是指活动所在的构件的属性；所述父子结构属性集是指父子结构中所涉构件类型的属性集和其所有子构件类型的属性集构成的集合；
这样，本发明在确定系统元模型基础组元后通过以层级模型、接口模型、算法模型、流程模型、传输模型为步骤要素完成系统模型的构造，为各种领域提供具有通用性、易用性优点的系统建模规范：本 发明构造的系统模型具有可执行性，结构清晰，层次可调，建模粒度可控；该建模既方便自顶向下分析设计，也方便自底向上实现集成，适用于对各种系统包括软件系统及信息系统进行建模；建模要素数量少，建模方法简单，即使不熟悉建模语言和计算机程序语言的普通领域人员，也能独立轻松构造系统模型，免除了对专业建模人员或程序开发人员的依赖和沟通，建模时间大大缩短。
概括起来，本发明与现有技术相比，具有如下明显的优点：
(1)可执行性：利用本发明构造的系统模型具有可执行性，即具有可以被映射为计算机可运行程序的完整性和充分一致性；
(2)通用性：本发明构造的系统模型结构清晰，层次可调，粒度可控，具有适用于各种系统建模的通用性。即可以进行算法建模，也适合系统快速原型，更适合大型复杂系统建模；既方便自顶向下分析设计，也方便自底向上实现整合集成；既适合基于预制构件的系统集成，也适合基于定制构件的系统扩展，还适合分布式系统的互联互通；既适用于实际工程系统建模，也适用于各种软件系统及信息系统建模；既适用于装备信息系统的仿真建模，也适用于管理信息系统建模；既适用于桌面软件系统建模、嵌入式设备软件系统建模、移动终端软件系统建模，也适用于局域网软件系统建模、广域网软件系统建模，也适用于云计算环境软件系统建模；既适用于应用软件系统建模，也适用于软件开发环境建模；
(3)易用性：本发明要素简明，规则简单，方法统一。即使不掌握繁琐的建模语言和计算机编程语言的普通领域人员也很容易利 用本发明在相对较短的时间内构造出本领域的具有可执行性的系统模型，免除了对专业建模人员或程序开发人员的依赖和沟通，完成的系统模型更符合领域人员的期望，消除了专业建模人员或程序开发人员的理解偏差；同时，由于省去了大量的沟通时间，建模时间大大缩短。
附图说明：
图1为系统元模型。
图2为系统模型构造步骤。
图3为活动与父子结构功能集。
图4为事件关联与父子结构事件集。
图5为传输与父子结构属性集。
图6为实现基于系统元模型以构造系统模型的通用建模方法的计算机。
图7为业务管理YWGL模型的层级模型。
图8为业务管理YWGL接口模型。
图9为销售管理XSGL接口模型。
图10为生产管理SCGL接口模型。
图11为采购管理CGGL接口模型。
图12为分销品FXP接口模型。
图13为直销品ZXP接口模型。
图14为主件ZJ接口模型。
图15为零件LJ接口模型。
图16为成品CP接口模型。
图17为主件加工算法模型。
图18为主件交货算法模型。
图19为零件加工算法模型。
图20为零件交货算法模型。
图21为配件接收算法模型。
图22为成品装配算法模型。
图23为业务主过程流程模型。
图24为业务配置流程模型。
图25为业务运行流程模型。
图26为内部订货流程模型。
图27为销售出货流程模型。
图28为销售订货流程模型。
图29为生产计划流程模型。
图30为生产实施流程模型。
图31为生产交货流程模型。
图32为业务运转循环传输模型。
图33为序号清零赋值传输模型。
图34为生产实例创建传输模型。
图35为生产配置遍历传输模型。
图36生产序号加一传输模型。
图37为生产序号赋值传输模型。
图38为采购实例创建传输模型。
图39为采购配置遍历传输模型。
图40为采购序号加一传输模型。
图41为采购序号赋值传输模型。
图42为销售序号清零赋值传输模型。
图43为销售实例创建传输模型。
图44为销售配置遍历传输模型。
图45为销售序号加一传输模型。
图46销售序号赋值传输模型。
图47为销售生产配置遍历传输模型。
图48为销售生产配置比较传输模型。
图49为销售生产配置条件传输模型。
图50为销售生产赋值传输模型。
图51为销售采购配置遍历传输模型。
图52为销售采购配置比较传输模型。
图53为销售采购配置条件传输模型。
图54为销售采购配置传输模型。
图55为生产运行遍历传输模型。
图56为采购运行遍历传输模型。
图57为销售运行遍历传输模型。
图58为销售生产运行遍历传输模型。
图59为销售生产运行比较传输模型。
图60为销售生产运行条件传输模型。
图61为生产销售收货传输模型。
图62为生产内部订货传输模型。
图63为销售采购运行遍历传输模型。
图64为销售采购运行比较传输模型。
图65为销售采购运行条件传输模型。
图66为采购销售收货传输模型。
图67为采购内部订货传输模型。
图68为合同统计传输模型。
图69为需求统计传输模型。
图70为订货统计传输模型。
图71为出货统计传输模型。
图72为存货统计传输模型。
图73为收货统计传输模型。
图74为主件待工统计传输模型。
图75为零件待工统计传输模型。
图76为配件接收传输模型。
图77为成品装配传输模型。
图78为完工交货传输模型。
图79为交货总量统计传输模型。
如上所列图中，其中表示传输模型的图中以黑体字突出显示了所 涉活动的传输模型。同时，为了阅读的方便性，在图中也以非黑体字同时显示出了所涉活动的信息。
具体实施方式
下面结合附图及一个具体实施例对本发明做进一步详细的说明：计算机一般包括一个中央处理器，一个内存和输入输出接口和一个总线。另外，计算机与输入输出设备、存储介质相连接。中央处理器负责计算和控制计算机的功能。中央处理器可以只包含一个中央处理单元，也可以是分布在一个或多个地方的多个中央处理单元。
内存介质可能由任何已知的计算机可读存储介质构成。比如，缓冲存储可以暂存一些程序代码以便在程序执行时降低从大容量存储器中提取代码的时间。同时，内存可以驻留在某个物理位置，由一种或多种数据存储，或以不同形式分布在多个物理系统中。另外，内存还可以分布在本地局域网(LAN)或广域网(WAN)上。内存中可以包含实现基于系统元模型构造系统模型的通用建模方法的程序代码，也可能包括图中未显示的其他代码，如操作系统。
输入输出接口允许计算机与存储介质或另一台计算机交换信息。输入输出设备包含任何已知的外部设备类型，如显示设备、键盘、鼠标、打印机、音响、手持设备、面罩，等等。总线提供计算机内部各个部件之间的通信连接，包括电气、光学、无线等多种传送连接形式。存储介质包括任何已知的计算机可读存储介质，如磁盘，光盘等等。存储介质可以包含一个或多个系统元模型构造的通用系统模型实例。 业内人士可以料想，本发明可能实现为全硬件产品、全软件产品，或通常称为模块的软硬件结合产品。另外，本发明可以实现为一个保存在计算机可读介质的计算机程序产品。计算机可读介质可能是，举例来说但并不限于：电子的、磁性的、光学的、电磁的、红外或半导体系统、装置、设备或前述项的结合。更具体的非尽列的计算机可读存储介质的例子如下：随机存储内存(RAM)、只读内存(ROM)、可擦写可编程只读内存(EPROM或闪存)、可移动只读存储器(CD-ROM)、光存储设备、磁存储设备，以及任何前述项的结合体。
实现本发明的方法的计算机程序代码可以用一种或多种程序语言编写，包括诸如Java，Small，C++，C#等，以及诸如C之类的面向过程的编程语言。程序代码可以运行在个人电脑，手持设备或局域网LAN、广域网WAN上。
业内人士当然知道本发明的方法也可以表示以图形表示，这些图形表示都可以实现为计算机程序代码。这些程序代码可以被一般电脑、专用电脑和其他可编程数据处理装置处理，实现这些图形表示的功能。
在以下的实施例中，为保持系统模型的描述完整性，我们分别列出了所有活动的传输模型。其中，有些活动不需要数据传输，其传输模型的内容为空，以文字“空”进行表示。
实施例为构造业务管理YWGL模型。需要说明的是，这个实施例仅是本发明的具体应用示例而已，本发明的技术实质不受这个实例限制。
实施例：构造业务管理YWGL模型
假设企业的的业务模式是通过销售自己生产的产品和外部采购的产品来获取利润，本实施例将对实现如下意图的业务管理系统进行建模：
(1)明确区分生产管理、采购管理、销售管理三大模块；
(2)配置功能：将生产品种数目和采购品种数目的和用于配置销售品种数目；
(3)运行功能：销售管理模块对每项产品的直销和销售的合同订量和出货数量进行统计，接收生产管理模块、采购管理模块的交货信息，根据销售状况向生产管理模块、采购管理模块发出订货信息；生产管理模块、采购管理模块接收销售管理模块的订货信息，启动内部过程，并向销售管理模块提交交货信息。
下面给出构造本实施例的系统模型的详细过程。
构造层级模型
图7给出了完成之后的业务管理YWGL模型的层级模型，下面给出构造本实施例的层级模型的详细过程：
在建模开始前的初始状态，层级模件就为业务管理YWGL模型省缺创建一个构件类型作为层级树的根节点，该根节点上的构件类型简称为根构件类型；
层级模件接收从实际系统建模环境送来的选中根构件类型的操作信息，层级模件响应前述操作信息，将根构件类型设置为所涉构件 类型；层级模件接收从实际系统建模环境送来的将所涉构件类型名称修改为“业务管理YWGL”字样的操作信息，层级模件响应前述操作信息，将根构件类型的名称修改为“业务管理YWGL”；根据根构件类型的名称简称为业务管理YWGL构件类型，其他构件类型依此类推；层级模件接收从实际系统建模环境送来的将所涉构件构件实例数量设置为1的操作信息，层级模件响应前述操作信息，将业务管理YWGL构件类型的构件实例数量设置为1；
层级模件接收并响应从实际系统建模环境送来的操作信息，为业务管理YWGL构件类型添加一个子构件类型；层级模件将前述子构件类型设置为所涉构件类型；层级模件接收并响应从实际系统建模环境送来的操作信息，将所涉构件类型的名称修改为“销售管理XSGL”；将销售管理XSGL构件类型的构件实例数量设置为1；
同上步骤，为业务管理YWGL构件类型添加构件实例数量均为0的子构件类型：生产管理SCGL、采购管理CGGL；
同上步骤，为销售管理XSGL构件类型添加构件实例数量均为1的子构件类型：分销品FXP、直销品ZXP；
同上步骤，为生产管理SCGL构件类型添加构件实例数量均为1的子构件类型：主件ZJ、零件LJ、成品CP；
至此，本实施例的层级模型构造完成。
构造接口模型
接下来，将介绍层级模型中各个构件类型的接口模型的构造过程。
业务管理YWGL接口模型
图8给出完成之后的业务管理YWGL构件类型的接口模型，根据构件类型的名称简称为业务管理YWGL接口模型，其他接口模型的名称依此类推。业务管理YWGL接口模型的构造过程如下：
层级模件接收并响应从实际系统建模环境送来的操作信息，将业务管理YWGL构件类型设置成为所涉构件类型；
接口模件接收并响应从实际系统建模环境送来的操作信息，完成相应操作：为业务管理YWGL接口模型添加一个新属性；将前述新属性设置为所涉属性；将所涉属性的数据类型修改为bool；将所涉属性的属性名称修改为业务运转态，前述属性名称为业务运转态的属性简称为业务运转态属性，后续属性依此类推，不再赘述；将业务运转态属性的属性值设置为true；
同上步骤，为业务管理YWGL接口模型添加属性：生产正常态属性，数据类型为bool，属性值为true；生产品种数目属性，数据类型为int，属性值为3；采购品种数目属性，数据类型为int，属性值为2；销售品种数目属性，数据类型为int，属性值为0；产品序号属性，数据类型为int，属性值为0；常数零属性，数据类型为int，属性值为0；比较结果属性，数据类型为bool，属性值为true；
接口模件接收并响应从实际系统建模环境送来的操作信息，完成相应操作：为业务管理YWGL接口模型添加一个流程功能；将前述功能设置为所涉功能；将所涉功能的名称修改为业务主过程，前述功能名称为业务主过程的功能简称为业务主过程功能，后续功能依此类 推，不再赘述；
同上步骤，为业务管理YWGL接口模型添加流程功能：业务配置、业务运行；
至此，业务管理YWGL接口模型构造完毕。
销售管理XSGL接口模型
图9给出完成之后的销售管理XSGL接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：产品名称属性，数据类型为string，属性值为销售品；产品序号属性，数据类型为int，属性值为1；存货数量属性，数据类型为int，属性值为0；最低存量属性，数据类型为int，属性值为0；合同订量属性，数据类型为int，属性值为0；收货数量属性，数据类型为int，属性值为0；订货数量属性，数据类型为int，属性值为0；出货数量属性，数据类型为int，属性值为0；出货总量属性，数据类型为int，属性值为0；需求数量属性，数据类型为int，属性值为0；
功能集：内部订货、销售出货、销售订货共三个流程功能。
生产管理SCGL接口模型
图10给出完成之后的生产管理SCGL接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：产品名称属性，数据类型为string，属性值为自研品；产品序号属性，数据类型为int，属性值为1；订货数量属性，数据类 型为int，属性值为0；完成数量属性，数据类型为int，属性值为0；交货数量属性，数据类型为int，属性值为0；交货总量属性，数据类型为int，属性值为0；
功能集：生产计划、生产实施、生产交货共三个流程功能。
采购管理CGGL接口模型
图11给出完成之后的采购管理CGGL接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：产品名称属性，数据类型为string，属性值为采购品；产品序号属性，数据类型为int，属性值为1；待购数量属性，数据类型为int，属性值为0；购回数量属性，数据类型为int，属性值为0；交货数量属性，数据类型为int，属性值为0；交货总量属性，数据类型为int，属性值为0；
功能集：采购实施、采购交货共两个算法功能。
分销品FXP接口模型
图12给出完成之后的分销品FXP接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：最低存量属性，数据类型为int，属性值为5；合同订量属性，数据类型为int，属性值为12；出货数量属性，数据类型为int，属性值为8。
直销品ZXP接口模型
图13给出完成之后的直销品ZXP接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：最低存量属性，数据类型为int，属性值为6；合同订量属性，数据类型为int，属性值为3；出货数量属性，数据类型为int，属性值为4。
主件ZJ接口模型
图14给出完成之后的主件ZJ接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：主件名称属性，数据类型为string，属性值为主件；待工数目属性，数据类型为int，属性值为0；完工数目属性，数据类型为int，属性值为0；交货数目属性，数据类型为int，属性值为0；交货总量属性，数据类型为int，属性值为0；
功能集：主件加工、主件交货共两个算法功能。
零件LJ接口模型
图15给出完成之后的零件LJ接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：零件名称属性，数据类型为string，属性值为零件；待工数目属性，数据类型为int，属性值为0；完工数目属性，数据类型为int，属性值为0；交货数目属性，数据类型为int，属性值为0；交 货总量属性，数据类型为int，属性值为0；
功能集：零件加工、零件交货共两个算法功能。
成品CP接口模型
图16给出完成之后的成品CP接口模型，其构造过程类似“业务管理YWGL接口模型”，其内容如下：
属性集：成品名称属性，数据类型为string，属性值为成品；待工数目属性，数据类型为int，属性值为0；完工数目属性，数据类型为int，属性值为0；单套主件数量属性，数据类型为int，属性值为2；单套零件数量属性，数据类型为int，属性值为6；主件存量属性，数据类型为int，属性值为0；主件收货量属性，数据类型为int，属性值为0；零件存量属性，数据类型为int，属性值为0；零件收货量属性，数据类型为int，属性值为0；
功能集：配件接收、成品装配共两个算法功能。
构造算法模型
接下来，将详细说明各个算法模型的构造过程。
主件加工算法模型
图17给出完成之后的主件加工算法模型，其构造过程如下：
层级模件接收并响应从实际系统建模环境送来的操作信息，将主件ZJ构件类型设置为所涉构件类型；
接口模件接收并响应从实际系统建模环境送来的操作信息，将主件加工功能设置为所涉功能；根据功能名称将实现主件加工功能的算法模型简称为主件加工算法模型；后续其他功能的算法模型依此类推，不再赘述；
算法模件接收并响应从实际系统建模环境送来的操作信息，完成相应操作：添加一个赋值算元，命名为主件待工完工赋值算元；建立从主件ZJ构件类型的待工数目属性向主件待工完工赋值算元的输入属性的传值；建立从主件待工完工赋值算元的输出属性向主件ZJ构件类型的完工数目属性的传值；
同上步骤，添加一个减法算元，命名为主件待工清零算元；建立从主件ZJ构件类型的待工数目属性向主件待工清零算元的被减数属性的传值；建立从主件ZJ构件类型的待工数目属性向主件待工清零算元的减数属性的传值；建立从主件待工清零算元的差数属性向主件ZJ构件类型的待工数目属性的传值；
至此，主件加工算法模型构造完毕。
主件交货算法模型
图18给出完成之后的主件交货算法模型，其构造过程类似“主件加工算法模型”，其内容如下：
一个赋值算元，命名为主件完工交货算元；该算元有以下传值：从主件ZJ构件类型的完工数目属性到主件完工交货算元的输入属性，从主件完工交货算元的输出属性到主件ZJ构件类型的交货数目属性；
一个减法算元，命名为主件完工清零算元；该算元有以下传值：从主件ZJ构件类型的完工数目属性到主件完工清零算元的被减数属性，从主件ZJ构件类型的完工数目属性到主件完工清零算元的减数属性，从主件完工清零算元的差数属性到主件ZJ构件类型的完工数目属性；
一个加法算元，命名为主件交货总量算元；该算元有以下传值：从主件ZJ构件类型的完工数目属性到主件交货总量算元的被加数属性，从主件ZJ的交货总量到主件交货总量算元的加数属性，从主件交货总量算元的和数属性到主件ZJ构件类型的交货总量属性。
零件加工算法模型
图19给出完成之后的零件加工算法模型，其构造过程类似“主件加工算法模型”，其内容如下：
一个赋值算元，命名为零件待工完工赋值算元；该算元有以下传值：从零件LJ构件类型的待工数目属性到零件待工完工赋值算元的输入属性，从零件待工完工赋值算元的输出属性到零件LJ构件类型的完工数目属性；
一个减法算元，命名为零件待工清零算元；该算元有以下传值：从零件LJ构件类型的待工数目属性到零件待工清零算元的被减数属性，从零件LJ构件类型的待工数目属性到零件待工清零算元的减数属性，从零件待工清零算元的差数属性到零件LJ构件类型的待工数目属性。
零件交货算法模型
图20给出完成之后的零件交货算法模型，其构造过程类似“主件加工算法模型”，其内容如下：
一个赋值算元，命名为零件完工交货算元；该算元有以下传值：从零件LJ构件类型的完工数目属性到零件完工交货算元的输入属性，从零件完工交货算元的输出属性到零件LJ构件类型的交货数目属性；
一个减法算元，命名为零件完工清零算元；该算元有以下传值：从零件LJ构件类型的完工数目属性到零件完工清零算元的被减数属性，从零件LJ完工数目属性到零件完工清零算元的减数属性，从零件完工清零算元的差数属性到零件LJ构件类型的完工数目属性；
一个加法算元，命名为零件交货总量算元；该算元有以下传值：从零件LJ构件类型的完工数目属性到零件交货总量算元的被加数属性，从零件LJ交货总量属性到零件交货总量算元的加数属性，从零件交货总量算元的和数属性到零件LJ构件类型的交货总量属性。
配件接收算法模型
图21给出完成之后的配件接收算法模型，其构造过程类似“主件加工算法模型”，其内容如下：
一个加法算元，命名为主件接收算元；该算元有以下传值：从成品CP构件类型的主件存量属性到主件接收算元的被加数属性，从成品CP构件类型的主件收货量属性到主件接收算元的加数属性，从主件接收算元的和数属性到成品CP构件类型的主件存量属性；
一个加法算元，命名为零件接收算元；该算元有以下传值：从成品CP构件类型的零件存量属性到零件接收算元的被加数属性，从成品CP构件类型的零件收货量属性到零件接收算元的加数属性，从零件接收算元的和数属性到成品CP构件类型的零件存量属性。
成品装配算法模型
图22给出完成之后的成品装配算法模型，其构造过程类似“主件加工算法模型”，其内容如下：
一个乘法算元，命名为装配主件算元；该算元有以下传值：从成品CP构件类型的待工数目属性到装配主件算元的被乘数属性，从成品CP构件类型的单套主件数属性到装配主件算元的乘数属性；
一个减法算元，命名为装配主件存量算元；该算元有以下传值：从成品CP构件类型的主件存量属性到装配主件存量算元的被减数属性，从装配主件算元的积数属性到装配主件存量算元的减数属性，从装配主件存量算元的差数属性到成品CP构件类型的主件存量属性；
一个乘法算元，命名为装配零件算元；该算元有以下传值：从成品CP构件类型的待工数目属性到装配零件算元的被乘数属性，从成品CP构件类型的单套零件数属性到装配零件算元的乘数属性；
一个减法算元，命名为装配零件存量算元；该算元有以下传值：从成品CP构件类型的零件存量属性到装配零件存量算元的被减数属性的，从装配零件算元的积数属性到装配零件存量算元的减数属性，从装配零件存量算元的差数属性向成品CP构件类型的零件存量属性；
一个赋值算元，命名为成品完工算元；该算元有以下传值：从成品CP构件类型的待工数目属性到成品完工算元的输入属性，从成品完工算元的输出属性向成品CP构件类型的完工数目属性；
一个减法算元，命名为成品待工清零算元；该算元有以下传值：从成品CP构件类型的待工数目属性到成品待工清零算元的被减数属性，从成品CP构件类型的待工数目属性到成品待工清零算元的减数属性，从成品待工清零算元的差数属性到成品CP构件类型的待工数目属性。
本实施例中所有的算法模型构造完毕。
构造流程模型
接下来，将详细说明各个流程模型的构造过程。
业务主过程流程模型
图23给出完成之后的业务管理YWGL构件类型的业务主过程流程模型，其构造过程如下：
层级模件接收并响应从实际系统建模环境送来的操作信息，将业务管理YWGL构件类型设置为所涉构件类型；
接口模件接收并响应从实际系统建模环境送来的操作信息，将业务主过程功能设置为所涉功能；根据功能名称将业务主过程功能的流程模型简称为业务主过程流程模型；其他功能的流程模型依此类推，不再赘述；
流程模件首先为业务主过程流程模型创建一个顺序活动用作根活动；所述顺序活动是一个具有顺序执行功能的逻辑活动；所述顺序活动具有开始节点、结束节点，并在开始节点和结束节点之间，顺序提供多个节点以便添加其他活动；根据流程模型名称称所述根活动为业务主过程根活动；需要说明的是，流程模件为每个流程模型都会创建一个根活动，根活动命名依此类推，不再赘述；
流程模件接收并响应从实际系统建模环境送来的操作信息，添加一个基于业务管理YWGL构件类型的业务配置功能的活动；根据该活动所执行的功能名称简称为业务配置活动，后续其他活动依此类推，不再赘述；流程模件响应前述操作信息，在业务主过程根活动中添加一个业务配置活动；
同上步骤，在业务主过程根活动中添加一个循环活动，简称为业务运转循环活动；所述的循环活动是一个具有循环功能的算元活动；所述的循环活动内部包含一个循环序列，所述循环序列由多个可以容纳活动的节点组成；
同上步骤，在业务运转循环活动的循环序列中添加一个基于业务管理YWGL构件类型的业务运行功能的活动，简称为业务运行活动；
至此，业务主过程流程模型构造完毕。
业务配置流程模型
图24给出完成之后的业务管理YWGL构件类型的业务配置流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在业务配置根活动中添加一个赋值算元活动，简称为序号清零赋值活动；所述赋值算元活动是一个具有赋值功能的算元活动；在业务配置根活动中添加一个实例创建算元活动，简称为生产实例创建活动；所述实例创建算元活动是一个具有创建构件实例功能的算元活动；在业务配置根活动中添加一个遍历活动，简称为生产配置遍历活动；所述遍历活动内部包含一个节点序列，每个节点容纳一个活动；所述遍历活动是指对确定的构件类型的各个构件实例均执行一遍节点序列的算元活动；
在生产配置遍历活动的遍历序列中添加一个加一活动，简称为生产序号加一活动；所述加一活动是指预制的具有使整数值加一功能的算元活动；在生产配置遍历活动的遍历序列中添加一个赋值活动，简称为生产序号赋值活动；
在业务配置根活动中添加一个实例创建算元活动，简称为采购实例创建活动；在业务配置根活动中添加一个遍历活动，简称为采购配置遍历活动；
在采购配置遍历活动的遍历序列中添加一个加一活动，简称为采购序号加一活动；在采购配置遍历活动的遍历序列中添加一个赋值活动，简称为采购序号赋值活动；
在业务配置根活动中添加一个赋值算元活动，简称为销售序号清零赋值活动；在业务配置根活动中添加一个实例创建算元活动，简称为销售实例创建活动；在业务配置根活动中添加一个遍历活动，简称为销售配置遍历活动；
在销售配置遍历活动的遍历序列中添加一个加一活动，简称为销售序号加一活动；在销售配置遍历活动的遍历序列中添加一个赋值活动，简称为销售序号赋值活动；在销售配置遍历活动的遍历序列中添加一个遍历活动，简称为销售生产配置遍历活动；
在销售生产配置遍历活动的遍历序列中添加一个相同比较活动，简称为销售生产配置比较活动；所述的相同比较活动是一个预制的具有比较两个输入项是否相同的功能的算元活动；在销售生产配置遍历活动的遍历序列中添加一个条件活动，简称为销售生产配置条件活动；所述的条件活动是一个预制的具有条件选择功能的逻辑活动；
在销售生产配置条件活动的为真分支中添加一个赋值活动，简称为销售生产赋值活动；
在销售配置遍历活动的遍历序列中添加一个遍历活动，简称为销售采购配置遍历活动；
在销售采购配置遍历活动的遍历序列中添加一个相同比较活动，简称为销售采购配置比较活动；在销售采购配置遍历活动的遍历序列中添加一个条件活动，简称为销售采购配置条件活动；
在销售采购配置条件活动的为真分支中添加一个赋值活动，简称为销售采购赋值活动。
业务运行流程模型
图25给出完成之后的业务管理YWGL构件类型的业务运行流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在业务运行根活动中添加一个遍历活动，简称为生产运行遍历活动；
在生产运行遍历活动的遍历序列中添加一个基于生产管理SCGL构件类型的生产计划功能的活动，简称为生产计划活动；在生产运行遍历活动的遍历序列中添加一个基于生产管理SCGL构件类型的生产实施功能的活动，简称为生产实施活动；在生产运行遍历活动的遍历序列中添加一个基于生产管理SCGL构件类型的生产交货功能的活动，简称为生产交货活动；
在业务运行根活动中添加一个遍历活动，简称为采购运行遍历活动；
在采购运行遍历活动的遍历序列中添加一个基于采购管理CGGL构件类型的采购实施功能的活动，简称采购实施活动；在采购运行遍历活动的遍历序列中添加一个基于采购管理CGGL构件类型的采购交货功能的活动，简称采购交货活动；
在业务运行根活动中添加一个遍历活动，简称为销售运行遍历活动；
在销售运行遍历活动的遍历序列中添加一个遍历活动，简称称为销售生产运行遍历活动；
在销售生产运行遍历活动的遍历序列中添加一个相同比较活动，简称为销售生产运行比较活动；在销售生产运行遍历活动的遍历序列中添加一个条件活动，简称为销售生产运行条件活动；
在销售生产运行条件活动的为真分支中添加一个基于销售管理 XSGL构件类型的销售收货功能的活动，简称生产销售收货活动；在销售生产运行条件活动的为真分支中添加一个基于销售管理XSGL构件类型的销售出货功能的活动，简称生产销售出货活动；在销售生产运行条件活动的为真分支中添加一个基于销售管理XSGL构件类型的内部订货功能的活动，简称生产内部订货活动；
在销售运行遍历活动的遍历序列中添加一个遍历活动，简称为销售采购运行遍历活动；
在销售采购运行遍历活动的遍历序列中添加一个相同比较活动，简称为销售采购运行比较活动；在销售采购运行遍历活动的遍历序列中添加一个条件活动，简称为销售采购运行条件活动；
在销售采购运行条件活动的为真分支中添加一个基于销售管理XSGL构件类型的销售收货功能的活动，简称为采购销售收货活动；在销售采购运行条件活动的为真分支中添加一个基于销售管理XSGL构件类型的销售出货功能的活动，简称为采购销售出货活动；在销售采购运行条件活动的为真分支中添加一个基于销售管理XSGL构件类型的内部订货功能的活动，简称为采购内部订货活动。
内部订货流程模型
图26给出完成之后的销售管理XSGL构件类型的内部订货流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在内部订货根活动中添加一个加法活动，简称为合同统计活动；所述加法活动是一个具有加法功能的算元活动；在内部订货根活动中 添加一个加法活动，简称为需求统计活动；在内部订货根活动中添加一个减法活动，简称为订货统计活动；所述减法活动是一个具有减法功能的算元活动。
销售出货流程模型
图27给出完成之后的销售管理XSGL构件类型的销售出货流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在销售出货根活动中添加一个加法活动，简称为出货统计活动；在销售出货根活动中添加一个减法活动，简称为存货统计活动；所述减法活动是一个具有减法功能的算元活动。
销售订货流程模型
图28给出完成之后的销售管理XSGL构件类型的销售订货流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在销售收货根活动中添加一个加法活动，简称为收货统计活动。
生产计划流程模型
图29给出完成之后的生产管理SCGL构件类型的生产计划流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在生产计划根活动中添加一个乘法活动，简称为主件待工统计活动；所述乘法活动是一个具有乘法功能的算元活动；在生产计划根活动中添加另一个乘法活动，简称为零件待工统计活动。
生产实施流程模型
图30给出完成之后的生产管理SCGL构件类型的生产实施流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在生产实施根活动中添加一个基于主件ZJ构件类型的主件加工功能的活动，简称主件加工活动；在生产实施根活动中添加一个基于主件ZJ构件类型的主件交付功能的活动，简称主件交付活动；在生产实施根活动中添加一个基于零件LJ构件类型的零件加工功能的活动，简称零件加工活动；在生产实施根活动中添加一个基于零件LJ构件类型的零件交付功能的活动，简称零件交付活动；在生产实施根活动中添加一个基于成品CP构件类型的配件接收功能的活动，简称配件接收；在生产实施根活动中添加一个基于成品CP构件类型的成品装配功能的活动，简称成品装配活动。
生产交货流程模型
图31给出完成之后的生产管理SCGL构件类型的生产交货流程模型，其构造过程类似“业务主过程流程模型”，其内容如下：
在生产交货根活动中添加一个赋值活动，简称为完工交货活动；在生产交货根活动中添加一个加法活动，简称为交货总量统计活动。
与此同时，本实施例的所有流程模型构造完毕。
构造传输模型
接下来，将详细说明各个活动的传输模型的构造过程。
业务配置传输模型
空。
业务运转循环传输模型
图32为完成后的业务运转循环传输模型，其构造过程如下：
层级模件接收并响应从实际系统建模环境送来的操作信息，将业务管理YWGL构件类型设置为所涉构件类型；
接口模件接收并响应从实际系统建模环境送来的操作信息，将业务主过程功能设置为所涉功能；
流程模件接收实际系统建模环境送来的操作信息，将业务运转循环活动设置为所涉活动；传输模件以所涉活动为对象构造传输模型，形成业务运转循环活动的传输模型；为了简便起见，根据活动的名称将业务运转循环活动的传输模型简称为业务运转循环传输模型，其他传输模型依此类比，不再赘述；
传输模件接收并响应从实际系统建模环境送来的操作信息，建立一个从业务管理YWGL构件类型的业务运转态属性到业务运转循环活动的状态属性的传输；所述业务运转循环活动的状态属性是指业务运转循环活动控制是否运行的状态属性的简称，为布尔变量；后续其他活动属性的含义依此类推，不再赘述；
至此，业务运转循环传输模型构造完毕。
业务运行传输模型
空。
序号清零赋值传输模型
图33为完成后的序号清零赋值传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的常数零属性到序号清零赋值活动的输入属性；从序号清零赋值活动的输出属性到业务管理YWGL构件类型的产品序号属性。
生产实例创建传输模型
图34为完成后的生产实例创建传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的名称属性到生产实例创建活动的类型属性；从业务管理YWGL构件类型的生产品种数目属性到生产实例创建活动的数量属性。
生产配置遍历传输模型
图35为完成后的生产配置遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的名称属性到生产配置遍历活动的类型属性。
生产序号加一传输模型
图36为完成后的生产序号加一传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到生产序号加一活动的输入属性；从生产序号加一活动的输出属性到业务管理YWGL构件类型的产品序号属性。
生产序号赋值传输模型
图37为完成后的生产序号赋值传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到生产序号赋值活动的输入属性；从生产序号赋值活动的输出属性到生产管理SCGL构件类型的产品序号属性。
采购实例创建传输模型
图38为完成后的采购实例创建传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的名称到采购实例创建活动的类型属性；从业务管理YWGL构件类型的采购品种数目属性到采购实例创建活动的实例数量属性。
采购配置遍历传输模型
图39为完成后的采购配置遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的名称到采购配置遍历活动的类型属性。
采购序号加一传输模型
图40为完成后的采购序号加一传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到采购序号加一活动的输入属性；从采购序号加一活动的输出属性到业务管理YWGL构件类型的产品序号属性。
采购序号赋值传输模型
图41为完成后的采购序号赋值传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到采购序号赋值活动的输入属性；从采购序号赋值活动的输出属性到采购管理CGGL构件类型的产品序号属性。
销售序号清零赋值传输模型
图42为完成后的销售序号清零赋值传输模型，其构造过程类似 “业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的常数零属性到销售序号清零赋值活动的输入属性；从销售序号清零赋值活动的输出属性到业务管理YWGL构件类型的产品序号属性。
销售实例创建传输模型
图43为完成后的销售实例创建传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的名称到销售实例创建活动的类型属性；从业务管理YWGL构件类型的销售品种数目属性到销售实例创建活动的数量属性。
销售配置遍历传输模型
图44为完成后的销售配置遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的名称到销售配置遍历活动的类型属性。
销售序号加一传输模型
图45为完成后的销售序号加一传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到销售序号加一活 动的输入属性；从销售序号加一活动的输出属性到业务管理YWGL构件类型的产品序号属性。
销售序号赋值传输模型
图46为完成后的销售序号赋值传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的产品序号属性到销售序号赋值活动的输入属性；从销售序号赋值活动的输出属性到销售管理XSGL构件类型的产品序号属性。
销售生产配置遍历传输模型
图47为完成后的销售生产配置遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的名称到销售生产配置遍历活动的类型属性。
销售生产配置比较传输模型
图48为完成后的销售生产配置比较传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的产品序号属性到销售生产配置比较活动的被比较属性；从生产管理SCGL构件类型的产品序号属性到销售生产配置比较活动的比较属性，从销售生产配置比较活动的结果 属性到业务管理YWGL构件类型的比较结果属性。
销售生产配置条件传输模型
图49为完成后的销售生产配置条件传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的比较结果属性到销售生产配置条件活动的状态属性。
销售生产赋值传输模型
图50为完成后的销售生产赋值传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的产品名称属性到销售生产赋值活动的输入属性；从销售生产赋值活动的输出属性到销售管理XSGL构件类型的产品名称属性。
销售采购配置遍历传输模型
图51为完成后的销售采购配置遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的名称到销售采购配置遍历活动的类型属性。
销售采购配置比较传输模型
图52为完成后的销售采购配置比较传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的产品序号属性到销售采购配置比较活动的被比较属性；从采购管理CGGL构件类型的产品序号属性到销售采购配置比较活动的比较属性；从销售采购配置比较活动的结果属性到业务管理YWGL构件类型的比较结果属性。
销售采购配置条件传输模型
图53为完成后的销售采购配置条件传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的比较结果属性到销售采购配置条件活动的状态属性。
销售采购配置传输模型
图54为完成后的销售采购配置传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的产品名称属性到销售采购赋值活动的输入属性；从销售采购赋值活动的输出属性到销售管理XSGL构件类型的产品名称属性。
生产运行遍历传输模型
图55为完成后的生产运行遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的名称到生产运行遍历活动的类型属性。
生产计划传输模型
空。
生产实施传输模型
空。
生产交货传输模型
空。
采购运行遍历传输模型
图56为完成后的采购运行遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的名称到采购运行遍历活动的类型属性。
采购实施传输模型
空。
采购交货传输模型
空。
销售运行遍历传输模型
图57为完成后的销售运行遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的名称到销售运行遍历活动的类型属性。
销售生产运行遍历传输模型
图58为完成后的销售生产运行遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的名称到销售生产运行遍历活动的类型属性。
销售生产运行比较传输模型
图59为完成后的销售生产运行比较传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的产品序号属性到销售生产运行比 较活动的被比较属性；从生产管理SCGL构件类型的产品序号属性到销售生产运行比较活动的比较属性；从销售生产运行比较活动的结果属性到业务管理YWGL构件类型的比较结果属性。
销售生产运行条件传输模型
图60为完成后的销售生产运行条件传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的比较结果属性到销售生产运行条件活动的状态属性。
生产销售收货传输模型
图61为完成后的生产销售收货传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的交货数量属性到生产销售收货活动的收货数量属性。
生产销售出货传输模型
空。
生产内部订货传输模型
图62为完成后的生产内部订货传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产内部订货活动的订货数量属性到生产管理SCGL构件类型的订货数量属性。
销售采购运行遍历传输模型
图63为完成后的销售采购运行遍历传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的名称到销售采购运行遍历活动的类型属性。
销售采购运行比较传输模型
图64为完成后的销售采购运行比较传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的产品序号属性到销售采购运行比较活动的被比较属性；从采购管理CGGL构件类型的产品序号属性到销售采购运行比较活动的比较属性；从销售采购运行比较活动的结果属性到业务管理YWGL构件类型的比较结果属性。
销售采购运行条件传输模型
图65为完成后的销售采购运行条件传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从业务管理YWGL构件类型的比较结果属性到销售采购运行条件活动的状态属性。
采购销售收货传输模型
图66为完成后的采购销售收货传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购管理CGGL构件类型的交货数量属性到采购销售收货活动的收货数量属性。
采购销售出货传输模型
空。
采购内部订货传输模型
图67为完成后的采购内部订货传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从采购内部订货活动的订货数量属性到采购管理CGGL构件类型的待购数量属性。
合同统计传输模型
图68为完成后的合同统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从分销品FXP构件类型的合同订量属性到合同统计活动的被加数属性；从直销品ZXP构件类型的合同订量属性到合同统计活动的加数属性；从合同统计活动的和数属性到销售管理XSGL构件类型的合同订量属性。
需求统计传输模型
图69为完成后的需求统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的最低存量属性到需求统计活动的被加数属性；从销售管理XSGL构件类型的合同订量属性到需求统计活动的加数属性；从需求统计活动的和数属性到销售管理XSGL构件类型的需求数量属性。
订货统计传输模型
图70为完成后的订货统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的需求数量属性到订货统计活动的被减数属性；从销售管理XSGL构件类型的存货数量属性到订货统计活动的减数属性；从订货统计活动的差数属性到销售管理XSGL构件类型的订货数量属性。
出货统计传输模型
图71为完成后的出货统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从分销品FXP构件类型的出货数量属性到出货统计活动的被加数属性；从直销品ZXP构件类型的出货数量属性到出货统计活动的加数属性；从出货统计活动的和数属性到销售管理XSGL构件类型的 出货数量属性。
存货统计传输模型
图72为完成后的存货统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的存货数量属性到存货统计活动的被减数属性；从销售管理XSGL构件类型的出货数量属性到存货统计活动的减数属性；从存货统计活动的差数属性到销售管理XSGL构件类型的存货数量属性。
收货统计传输模型
图73为完成后的收货统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从销售管理XSGL构件类型的存货数量属性到收货统计活动的被加数属性；从销售管理XSGL构件类型的收货数量属性到收货统计活动的加数属性；从收货统计活动的和数属性到销售管理XSGL构件类型的存货数量属性。
主件待工统计传输模型
图74为完成后的主件待工统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的订货数量属性到主件待工统计活 动的被乘数属性；从成品CP构件类型的单套主件数量属性到主件待工统计活动的乘数属性；从主件待工统计活动的积数属性到主件ZJ构件类型的待工数目属性。
零件待工统计传输模型
图75为完成后的零件待工统计传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的订货数量属性到零件待工统计活动的被乘数属性；从成品CP构件类型的单套零件数量属性到零件待工统计活动的乘数属性；从零件待工统计活动的积数属性到零件LJ构件类型的待工数目属性。
主件加工传输模型
空。
主件交货传输模型
空。
零件加工传输模型
空。
零件交货传输模型
空。
配件接收传输模型
图76为完成后的配件接收传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从主件ZJ构件类型的交货数目属性到配件接收活动的主件收货量属性；从零件LJ构件类型的交货数目属性到配件接收活动的零件收货量属性。
成品装配传输模型
图77为完成后的成品装配传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从成品装配活动的完工数目属性到生产管理SCGL构件类型的完成数量属性。
完工交货传输模型
图78为完成后的完工交货传输模型，其构造过程类似“业务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的完成数量属性到完工交货活动的输入属性；从完工交货活动的输出属性到生产管理SCGL构件类型的交货数量属性。
交货总量统计传输模型
图79为完成后的交货总量统计传输模型，其构造过程类似“业 务运转循环传输模型”，其内容包含如下传输：
从生产管理SCGL构件类型的交货数量属性到交货总量统计活动的被加数属性；从生产管理SCGL构件类型的交货总量属性到交货总量统计活动的加数属性；从交货总量统计活动的和数属性到生产管理SCGL构件类型的交货总量属性；
本实施例中由层级模型、接口模型、算法模型、流程模型和传输模型构成的业务管理YWGL系统模型构造完毕。
本实施例演示了一个不掌握现有复杂系统建模语言、不掌握计算机程序语言的普通管理人员，无须依赖专业建模人员和程序开发人员，如何独立地将自己关于业务管理的构想，在相对短的时间内利用本发明构造出一个具有可执行性的业务管理系统模型。不但构造过程清晰，构造方法简单，而且，系统模型质量明显较高，花费的时间明显较少。
与该同一个管理人员与专业建模人员或程序开发人员的协同开发业务管理系统模型的模式相比，该管理人员利用本发明独立开发业务管理系统模型，取得了如下的明显效果：
(1)质量高：构造完成的系统模型是该管理人员心目中所需要的，避免了专业建模人员或程序开发人员与该管理人员对业务管理系统模型的理解偏差；
(2)时间短：由于节省了管理人员与专业建模人员或程序开发人员之间的繁杂沟通，整个建模花费的时间周期缩短到原来的1/5，大大地节约了时间、精力和经费。

Claims (7)

  1. 一种基于系统元模型以构造系统模型的通用建模方法，基于一个含有计算机可读程序代码的计算机可读存储介质，所述计算机可读程序代码包含一组可以被计算机的处理器所执行的指令，通过对由一个系统元模型定义的数据进行处理，来实现基于系统元模型构造系统模型，其所用的系统元模型包含如下组元：
    层级模件：以由构件类型为节点的树形结构描述系统模型的层级模型，并在实际系统建模环境中用作模板以配置形成系统模型的层级模型；所述层级模型是指系统模型中以构件类型为节点组成的层级关系；所述构件类型是指一组具有相同外部特征的构件实例；所述系统模型中以构件类型为节点的树形结构称为层级树；
    接口模件：以属性集、功能集、事件集三部分可选结构描述接口模型，并在实际系统建模环境中用作模板以配置形成接口模型；所述接口模型是指构件类型的外部特征；所述功能集中的功能包括算法功能、流程功能两种形式；算法功能的实现方式由算法模型提供；流程功能的实现方式由流程模型与传输模型相组合提供；
    算法模件：以算元为节点的树形结构描述算法模型，并在实际系统建模环境中用作模板以配置形成算法模型，所述算法模型是指利用算元组合实现功能的算法描述；所述算元是指预先实现的具有特定功能的构件；
    流程模件：以活动为节点进行组合描述流程模型，并在实际系统建模环境中用作模板以配置形成流程模型；所述流程模型是指利用活 动组合实现功能的方式描述；所述活动是指功能的一次执行；
    传输模件：采用传输集描述传输模型，并在实际系统建模环境中用作模板以配置形成传输模型；所述传输模型是指所涉活动的数据传递关系；所述传输集中的传输为一个属性和另一个属性之间的数据传递关系；
    采用如上所述的五个模件构造系统模型的具体步骤如下：
    1)构造层级模型：层级模件读入从实际系统建模环境送来的层级模型操作信息，所述层级模型操作信息是指对层级树进行如新建构件类型、添加构件类型、选择构件类型、命名构件类型、删除构件类型的操作信息，层级模件响应层级模型操作信息对层级树的构件类型节点进行相应操作而获得层级模型；
    2)构造接口模型：对步骤1)得到的层级模型中的构件类型逐一构造接口模型，各接口模型的构造步骤包括：接口模件读入从实际系统建模环境送来的接口模型操作信息；所述接口模型操作信息是指对属性、功能、事件进行如新建、命名、删除的操作信息；接口模件响应接口模型操作信息进行相应操作而获得接口模型；实现算法功能的算法模型由步骤3)构造，实现流程功能的流程模型由步骤4)构造；
    3)构造算法模型：对步骤2)中得到的算法功能逐一构造算法模型，各算法模型的构造步骤包括：算法模件读入从实际系统建模环境送来的算法模型操作信息；
    4)构造流程模型：对步骤2)中得到的流程功能逐一构造流程模 型，各流程模型的构造步骤包括：流程模件读入从实际系统建模环境送来的流程模型操作信息；
    5)构造传输模型：对步骤4)中得到的流程模型中的活动逐一构造传输模型，各传输模型的构造步骤包括：传输模件读入从实际系统建模环境送来的传输模型操作信息；所述传输模型操作信息是指进行如添加传输、选择传输、删除传输的操作信息，传输模件响应传输模型操作信息进行相应操作而获得传输模型；
    至此，由层级模型、接口模型、算法模型、流程模型、传输模型为要素所构成的系统模型构造完成。
  2. 根据权利要求1所述之基于系统元模型构造系统模型的通用建模方法，其特征在于，流程模件和传输模件组合是描述和配置功能实现的一般性方式；所述算法模件当且仅当使用算元进行组合以描述和配置实现功能时用作替代流程模件和传输模件组合的简化方式。
  3. 根据权利要求1所述之基于系统元模型构造系统模型的通用建模方法，其特征在于，系统元模型采用如下建模规则：系统元模型以父子结构为最小递归单元，对系统模型进行递归描述；所述父子结构是指层级树中由所涉构件类型节点及其所有子构件类型节点组成的父子关系结构。
  4. 根据权利要求1所述之基于系统元模型构造系统模型的通用建模方法，其特征在于，步骤2)所述的具体功能，仅能在算法功能和流程功能中选择其一。
  5. 根据权利要求1所述之基于系统元模型构造系统模型的通用 建模方法，其特征在于，所述步骤3)构造算法模型中算法模型操作信息是指如添加算元、选择算元、命名算元、删除算元以及添加传值、选择传值、删除传值的操作信息；算法模件响应算法模型操作信息进行相应操作而获得算法模型；所述传值是算法属性集中的两个属性之间的一个赋值关系；所述算法属性集是指由所涉构件类型的属性集和算法模型中的所有算元的属性集构成的集合。
  6. 根据权利要求1所述之基于系统元模型构造系统模型的通用建模方法，其特征在于，所述步骤4)构造流程模型中流程模型操作信息是指如添加活动、选择活动、命名活动、删除活动的操作信息，流程模件响应流程模型操作信息进行相应操作而获得流程模型；所述活动包括构件活动和算元活动两种类型；所述构件活动是父子结构功能集中的功能的一次执行；所述父子结构功能集是指父子结构中所涉构件类型的功能集和其所有子构件类型的功能集构成的集合；所述算元活动是指算元的功能的一次执行；所述流程模型包括属性流程模型和事件流程模型两种形式；所述流程模件包括属性流程模件和事件流程模件两种形式；所述属性流程模件以流程树为结构描述属性流程模型，所述流程树是以活动为节点构成的树形结构。
  7. [根据细则26改正17.08.2015]　
    根据权利要求1所述之基于系统元模型构造系统模型的通用建模方法，其特征在于，所述传输所关联的属性，除活动属性外，仅限于父子结构属性集中的属性；所述活动属性是指活动所在的构件类型的属性；所述父子结构属性集是指父子结构中所涉构件类型的属性集和其所有子构件类型的属性集构成的集合。
PCT/CN2015/000451 2014-06-25 2015-06-25 一种基于系统元模型以构造系统模型的通用建模方法 WO2015196780A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/322,077 US20170139684A1 (en) 2014-06-25 2015-06-25 General modeling method to construct system models based on a system meta model
EP15811524.6A EP3163435A4 (en) 2014-06-25 2015-06-25 Method for general modeling basing on system meta model to construct system model
CA2952072A CA2952072A1 (en) 2014-06-25 2015-06-25 Method for general modeling basing on system meta model to construct system model

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410292935.1A CN105224299B (zh) 2014-06-25 2014-06-25 一种基于系统元模型构造系统模型的通用建模方法
CN201410292935.1 2014-06-25

Publications (1)

Publication Number Publication Date
WO2015196780A1 true WO2015196780A1 (zh) 2015-12-30

Family

ID=54936677

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/000451 WO2015196780A1 (zh) 2014-06-25 2015-06-25 一种基于系统元模型以构造系统模型的通用建模方法

Country Status (5)

Country Link
US (1) US20170139684A1 (zh)
EP (1) EP3163435A4 (zh)
CN (1) CN105224299B (zh)
CA (1) CA2952072A1 (zh)
WO (1) WO2015196780A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112099784A (zh) * 2020-08-18 2020-12-18 西安合科软件有限公司 一种模型创建方法与装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107766033A (zh) * 2017-10-10 2018-03-06 广西师范大学 一种基于问题框架的敏捷需求拆分方法
CN107832043B (zh) * 2017-11-16 2019-05-03 广州今宏信息科技有限公司 一种基于软件元视图构造视图的可视软件建模方法
CN109815242B (zh) * 2019-02-02 2021-04-02 中国农业银行股份有限公司 一种数据处理方法及系统
CN110784545B (zh) * 2019-10-31 2022-02-11 上海埃威航空电子有限公司 实时数据分发系统
CN112784417B (zh) * 2021-01-25 2024-03-22 中国商用飞机有限责任公司北京民用飞机技术研究中心 一种基于SysML的航电分布式联合仿真方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794170A (zh) * 2005-12-29 2006-06-28 吉林大学 一种基于统一建模语言的电信领域建模工具及建模方法
US20090132211A1 (en) * 2007-11-19 2009-05-21 International Business Machines Corporation Automated solution for generating architectural design models for service-oriented architecture (soa) information services
CN101477462A (zh) * 2009-02-12 2009-07-08 山东浪潮齐鲁软件产业股份有限公司 一种用于动态改变系统行为的模型驱动软件开发方法
CN101876896A (zh) * 2009-04-30 2010-11-03 深圳市永兴元科技有限公司 一种提升信息化技术的电子政务开发系统
CN103092594A (zh) * 2011-11-07 2013-05-08 金蝶软件（中国）有限公司 模型转换方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101561837A (zh) * 2009-05-25 2009-10-21 北京理工大学 面向对象的图形模块化建模方法及求仿真系统参数的方法
CN102298660B (zh) * 2011-10-10 2013-05-15 吉林大学 一种离散元法边界建模的通用方法
CN103176776A (zh) * 2011-12-21 2013-06-26 德商赛克公司 创建元模型的系统和/或方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794170A (zh) * 2005-12-29 2006-06-28 吉林大学 一种基于统一建模语言的电信领域建模工具及建模方法
US20090132211A1 (en) * 2007-11-19 2009-05-21 International Business Machines Corporation Automated solution for generating architectural design models for service-oriented architecture (soa) information services
CN101477462A (zh) * 2009-02-12 2009-07-08 山东浪潮齐鲁软件产业股份有限公司 一种用于动态改变系统行为的模型驱动软件开发方法
CN101876896A (zh) * 2009-04-30 2010-11-03 深圳市永兴元科技有限公司 一种提升信息化技术的电子政务开发系统
CN103092594A (zh) * 2011-11-07 2013-05-08 金蝶软件（中国）有限公司 模型转换方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3163435A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112099784A (zh) * 2020-08-18 2020-12-18 西安合科软件有限公司 一种模型创建方法与装置

Also Published As

Publication number Publication date
CN105224299B (zh) 2018-06-26
EP3163435A1 (en) 2017-05-03
CN105224299A (zh) 2016-01-06
CA2952072A1 (en) 2015-12-30
EP3163435A4 (en) 2018-02-21
US20170139684A1 (en) 2017-05-18

Similar Documents

Publication Publication Date Title
WO2015196782A1 (zh) 一种构造系统模型的可视建模编辑器
WO2015196783A1 (zh) 一种基于软件元模型以构造软件模型的通用软件建模方法
WO2015196780A1 (zh) 一种基于系统元模型以构造系统模型的通用建模方法
WO2015196784A1 (zh) 一种基于软件元视图以构造软件视图的可视软件建模方法
CN104732306B (zh) 一种业务应用系统的快速开发系统及方法
US20140372969A1 (en) Computer aided visualization of a business object model lifecycle
WO2015196785A1 (zh) 一种构造软件模型的可视软件建模编辑器
Wang et al. An automatic model-to-model mapping and transformation methodology to serve model-based systems engineering
US8862637B2 (en) Generating data access operations based on a data model using a data services model
WO2015196781A1 (zh) 一种基于系统元视图以构造系统视图的可视建模方法
Krogstie Capturing enterprise data integration challenges using a semiotic data quality framework
CN112948110A (zh) 云应用的拓扑与编排系统、方法、存储介质及电子设备
US8209201B1 (en) System and method for correlating objects
US10949758B2 (en) Data management externalization for workflow definition and execution
Kharmoum et al. A novel automatic transformation method from the business value model to the UML use case diagram
Ng et al. The development of an enterprise resources planning system using a hierarchical design pyramid
Mos et al. Business matter experts do matter: a model-driven approach for domain specific process design and monitoring
WO2015196786A1 (zh) 一种基于界面元模型以构造界面模型的通用界面建模方法
Shershakov DPMine graphical language for automation of experiments in process mining
WO2015196787A1 (zh) 一种基于界面元视图以构造界面视图的可视界面建模方法
Fischer et al. Towards a Task Driven Approach Enabling Continuous User Requirements Engineering.
JP2020027663A (ja) 仕様書作成部
Bollen Business process model semantics in BPMN
Bell A practical high volume software product line
Cohen et al. Enterprise architecture with executable modelling rules: A case study at the Swedish defence materiel administration

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15811524

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2952072

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 15322077

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015811524

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015811524

Country of ref document: EP