CN112394927A - Dimension-increasing form of product model and model definition method - Google Patents
Dimension-increasing form of product model and model definition method Download PDFInfo
- Publication number
- CN112394927A CN112394927A CN202011442515.9A CN202011442515A CN112394927A CN 112394927 A CN112394927 A CN 112394927A CN 202011442515 A CN202011442515 A CN 202011442515A CN 112394927 A CN112394927 A CN 112394927A
- Authority
- CN
- China
- Prior art keywords
- product
- model
- behavior
- dictionary
- dictionary library
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000003190 augmentative effect Effects 0.000 claims abstract description 8
- 230000000877 morphologic effect Effects 0.000 claims abstract description 4
- 230000006399 behavior Effects 0.000 claims description 63
- 238000010586 diagram Methods 0.000 claims description 30
- 230000000694 effects Effects 0.000 claims description 7
- 230000003068 static effect Effects 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 7
- 238000013461 design Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000005477 standard model Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Abstract
A method for augmented form and model definition of a product model, comprising: preparing a database file; creating a property dictionary library; storing the attribute of the item into an attribute dictionary library; creating a product dictionary library and a product structure dictionary library; storing product information in a product dictionary library and storing a product structure in a product structure dictionary according to the product structure; creating a behavior dictionary library and a behavior flow dictionary library; storing behavior information in a behavior dictionary base and storing behavior flows in a behavior flow dictionary according to the behavior flow chart; in the product structure, selecting and adding required attributes from the attribute dictionary library for each node product; in the behavior prevalence, selecting and adding required input parameter attributes from the attribute dictionary library for each node behavior; creating a state dictionary base; assigning the product structure and the behavior flow to the model, and adding basic attributes to the model; an augmented morphological model of the product is created. The problem that the existing development mode cannot meet the requirement of industrial software is solved.
Description
Technical Field
The invention relates to the field of industrial software, in particular to a dimension-increasing form of a product model and a model definition method.
Background
In the field of industrial software, industrial products refer not only to products produced, but also to devices, production lines, systems, etc., which are collectively referred to as industrial products. The software developed for these industrial products we refer to as industrial software. Industrial software relates to the design, manufacture, operation and maintenance of industrial products and to managing the full lifecycle. There are many design methods for industrial software, and we mainly use model-driven industrial software method, where the model is the carrier of industrial software.
In the field of industrial software, a common model only contains a single item of an object or a behavior, but a product model is a combination of the two, and the two are automatically associated. Products and behaviors in the industrial field product model are defined as follows. The association is achieved by "the value of the type in the product attribute" being equal to "the value of the product type in the behavior attribute". In a computer implementation, the product meta model implements the above-defined automatic mapping in a computer by UML. A domain model in industrial software refers to the visual representation of concept classes within an industrial domain or industrial product objects in the real world. Traditional software development modes are object-oriented or process-oriented, but due to the complexity of industrial software, the development modes cannot meet the requirements of the industrial software.
Disclosure of Invention
In view of the above, the present invention has been made to provide a product model dimension-increasing form and a model definition method that overcome or at least partially solve the above problems.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method for augmented form and model definition of a product model, comprising:
s100, preparing a database file, and using an SQLite database as data storage for the created database;
s200, creating an attribute dictionary library, wherein the attribute dictionary library records basic attributes of items, attributes of products and attributes of behaviors;
s300, storing basic attributes, product attributes, behavior attributes and state attributes of the items into an attribute dictionary library;
s400, creating a product dictionary library and a product structure dictionary library, wherein the product dictionary library and the product structure dictionary library contain basic product information;
s500, storing product information in a product dictionary library and storing a product structure in a product structure dictionary according to the product structure;
s600, creating a behavior dictionary library and a behavior flow dictionary library;
s700, storing behavior information in a behavior dictionary base and storing behavior flows into a behavior flow dictionary according to the behavior flow chart;
s800, in a product structure, selecting and adding required attributes from an attribute dictionary library for each node product; in the behavior prevalence, selecting and adding required input parameter attributes from the attribute dictionary library for each node behavior;
s900, creating a state dictionary base;
s1000, assigning a product structure and a behavior flow to a model, and adding basic attributes to the model; creating an augmented dimensional morphological model of the product;
and S1100, generating a window view according to the configured structure, and generating a project template.
Further, in S200, the basic attribute of the item includes the number, name, and type information of the attribute.
Further, in S400, the product in the product dictionary library is a basic element for constructing a product configuration, and the product dictionary library may store each product element that may exist independently, and is composed of a product name, a product attribute, and the like.
Further, in S600, the dictionary library and the behavior flow dictionary library contain the number, name, input and output information of the behavior.
Further, in S900, the state dictionary library contains the numbers, names, input and output information of the dictionary.
Further, in S900 and S1000, the dimension-added form model includes a product structure and behavior flow and a model indicating a management method of the product model structure and behavior model flow, and is a basic model of the user process.
Further, in S1100, after the project template is generated, the end user creates and executes data input and display according to the project template, executes behaviors according to the model behavior flow, and obtains behavior states for display.
Further, the static structure of the model and the dynamic collaboration relationships within the model may be described by logical views.
Further, the static structure of the model is described in the class diagram and object diagram in the logical view, and the dynamic structure of the model is described in the state diagram, timing diagram, collaboration diagram, and activity diagram.
The technical scheme provided by the embodiment of the invention has the beneficial effects that at least:
the invention discloses a dimension-increasing form of a product model and a model definition method, and provides a model-oriented development mode, and a model-centered software development framework standard-model driving system structure. The present invention is a simplified description of a system as seen from a certain perspective or point of view, covering a certain aspect of the system, and omitting entities not relevant to this aspect. The problem that the software architecture cannot solve the concern of all risk undertakers due to the fact that the software architecture document excessively emphasizes one aspect of software development is solved. Since each software system has multiple stakeholders: end users, developers, system engineers, project managers, and the like. The problem that a software engineer wants to capture all system architecture points by using a single view and express blueprints exceeding the expression limit of the software engineer in the single view is solved. The description of the software architecture is organized using multiple concurrent views, each view serving to describe only a particular set of issues for the aspect of interest. The problem that the existing development mode cannot meet the requirement of industrial software is solved.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
fig. 1 is a flowchart of a dimension-increasing form of a product model and a model definition method in embodiment 1 of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In order to solve the problem that the existing development mode in the prior art cannot meet the requirement of industrial software, the embodiment of the invention provides a dimension-increasing form of a product model and a model definition method.
Example 1
The embodiment discloses a dimension-increasing form and model definition method of a product model, which comprises the following steps:
s100, preparing a database file, and using an SQLite database as data storage for the created database.
S200, creating an attribute dictionary library, wherein the attribute dictionary library records basic attributes of items, attributes of products and attributes of behaviors; specifically, in this embodiment S200, the basic attribute of the item includes information such as the number, name, and type of the attribute.
S300, storing the basic attribute, the product attribute, the behavior attribute and the state attribute of the item into an attribute dictionary library.
S400, creating a product dictionary library and a product structure dictionary library, wherein the product dictionary library and the product structure dictionary library contain basic product information.
In this embodiment S400, the products in the product dictionary library are basic elements for constructing product configurations, and the product dictionary library may store each product element that may exist independently, and is composed of product names, product attributes, and the like.
S500, storing product information in a product dictionary base and storing a product structure in a product structure dictionary according to the product structure.
S600, creating a behavior dictionary library and a behavior flow dictionary library; in this embodiment S600, the dictionary library and the behavior flow dictionary library contain the number, name, input and output information of the behavior.
S700, storing behavior information in a behavior dictionary base and storing behavior flows in a behavior flow dictionary according to the behavior flow chart.
S800, in a product structure, selecting and adding required attributes from an attribute dictionary library for each node product; in behavior prevalence, the required input parameter properties are selected from a property dictionary library for each node behavior.
S900, creating a state dictionary base; in this embodiment S900, the state dictionary library contains the numbers, names, input and output information of the dictionary.
S1000, assigning a product structure and a behavior flow to a model, and adding basic attributes to the model; creating an augmented dimensional morphological model of the product; in this embodiment S1000, the augmented form model includes the structure and behavior flow of the product, and a model indicating the management method of the structure and behavior flow of the product model, and is a basic model of the user process.
And S1100, generating a window view according to the configured structure, and generating a project template. In S1100 of this embodiment, after the project template is generated, the end user creates and executes data input and display according to the project template, executes behaviors according to the model behavior flow, and obtains behavior states for display.
In this embodiment, the static structure of the model and the dynamic collaboration relationship inside the model can be described by a logical view. The static structure of the model is described in the class diagram and object diagram in the logical view, and the dynamic structure of the model is described in the state diagram, timing diagram, collaboration diagram, and activity diagram.
Specifically, a Class diagram (Class diagram) shows the static structure of a model, particularly classes existing in the model, the internal structure of the classes, and their relationship with other classes. The class diagram does not show temporary information. Class diagrams are the main components of object-oriented modeling. It is used for both general conceptual modeling of system classes of applications and detailed modeling, converting models into programming code. Class diagrams can also be used for data modeling. The model of the product comprises basic attributes of the product, the attributes recorded by the basic attributes are all attributes shared by the product, and the specific attributes are newly established attributes selected from an attribute dictionary. The behavior model comprises basic attributes of the product, the attributes recorded by the basic attributes are all attributes shared by the behaviors, and the specific attributes are newly established attributes selected from an attribute dictionary.
Activity map (activity diagram) is used to clarify the workflow of business use case implementation. Business case workflows describe the work a business must do to provide its required value to the business principals being served. Business cases consist of a series of activities that collectively generate certain artifacts for a business initiative. The workflow generally includes a basic workflow and one or more alternative workflows, the structure of which is illustrated using an activity diagram.
Sequence Diagram (Sequence Diagram) is used primarily to display interactions between objects in the order in which they occur. Developers generally consider sequence diagrams to be meaningful only to them. However, a business person of an organization may find that a sequence diagram shows how different business objects interact, which is useful for communicating how the current business is going. In addition to recording the current events of an organization, a sequence diagram of a business level can be used as a requirement file to fulfill a future system delivery requirement. In the project's demand phase, the analyst can bring the use case to the next level by providing a more formal level of expression.
The dimension-increasing form of a product model and the model definition method disclosed by the embodiment provide a model-oriented development mode, and a model-centered software development framework standard-model driving system structure. The present invention is a simplified description of a system as seen from a certain perspective or point of view, covering a certain aspect of the system, and omitting entities not relevant to this aspect. Software architecture documentation over emphasizes certain aspects of software development. Software architectures do not address all of the concerns of stakeholders. Each software system has multiple stakeholders: end users, developers, system engineers, project managers, and the like. Software engineers want to capture all system architectural issues using a single view, trying to express blueprints beyond their expression limit in a single view. The description of the software architecture is organized using multiple concurrent views, each view serving to describe only a particular set of issues for the aspect of interest. The problem that the existing development mode cannot meet the requirement of industrial software is solved.
It should be understood that the specific order or hierarchy of steps in the processes disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. Of course, the processor and the storage medium may reside as discrete components in a user terminal.
For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or".
Claims (9)
1. A method for dimension-increasing form and model definition of a product model, comprising:
s100, preparing a database file, and using an SQLite database as data storage for the created database;
s200, creating an attribute dictionary library, wherein the attribute dictionary library records basic attributes of items, attributes of products and attributes of behaviors;
s300, storing basic attributes, product attributes, behavior attributes and state attributes of the items into an attribute dictionary library;
s400, creating a product dictionary library and a product structure dictionary library, wherein the product dictionary library and the product structure dictionary library contain basic product information;
s500, storing product information in a product dictionary library and storing a product structure in a product structure dictionary according to the product structure;
s600, creating a behavior dictionary library and a behavior flow dictionary library;
s700, storing behavior information in a behavior dictionary base and storing behavior flows into a behavior flow dictionary according to the behavior flow chart;
s800, in a product structure, selecting and adding required attributes from an attribute dictionary library for each node product; in the behavior prevalence, selecting and adding required input parameter attributes from the attribute dictionary library for each node behavior;
s900, creating a state dictionary base;
s1000, assigning a product structure and a behavior flow to a model, and adding basic attributes to the model; creating an augmented dimensional morphological model of the product;
and S1100, generating a window view according to the configured structure, and generating a project template.
2. The method according to claim 1, wherein in S200, the basic attribute of the item includes information of number, name and type of the attribute.
3. The method according to claim 1, wherein in S400, the product in the product dictionary repository is a basic element for constructing a product configuration, and the product dictionary repository stores each product element that can exist independently, and is composed of a product name and a product attribute.
4. The method for dimension-increasing form and model definition of a product model according to claim 1, wherein in S600, the dictionary library and the behavior flow dictionary library contain the number, name, input and output information of the behavior.
5. The method for dimension-increasing form and model definition of a product model according to claim 1, wherein in S900, the state dictionary library contains the numbers, names, input and output information of the dictionary.
6. The method according to claim 1, wherein in S900 and S1000, the augmented form model includes a structure and behavior flow of the product, and a model representing a management manner of the structure and behavior flow of the product model, and is a basic model of the user process.
7. The method according to claim 1, wherein in S1100, after the project template is generated, the end user creates and executes data input and display according to the project template, executes behavior according to the model behavior flow, obtains behavior state, and displays the behavior state.
8. The method for dimension-increasing form and model definition of a product model according to claim 1, characterized in that the static structure of the model and the dynamic cooperation inside the model can be described by logical views.
9. The method of claim 8, wherein the static structure of the model is described in a class diagram and an object diagram in a logical view, and the dynamic structure of the model is described in a state diagram, a timing diagram, a collaboration diagram, and an activity diagram.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011442515.9A CN112394927A (en) | 2020-12-08 | 2020-12-08 | Dimension-increasing form of product model and model definition method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011442515.9A CN112394927A (en) | 2020-12-08 | 2020-12-08 | Dimension-increasing form of product model and model definition method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112394927A true CN112394927A (en) | 2021-02-23 |
Family
ID=74625665
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011442515.9A Pending CN112394927A (en) | 2020-12-08 | 2020-12-08 | Dimension-increasing form of product model and model definition method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112394927A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113656520A (en) * | 2021-08-10 | 2021-11-16 | 广州市规划和自然资源自动化中心(广州市基础地理信息中心) | Spatial analysis method, spatial analysis device, computer equipment and storage medium |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060195460A1 (en) * | 2005-02-28 | 2006-08-31 | Microsoft Corporation | Data model for object-relational data |
| CN1912830A (en) * | 2006-08-25 | 2007-02-14 | 华为技术有限公司 | Method of operating interface of definition to object mould |
| US20070168924A1 (en) * | 2005-11-17 | 2007-07-19 | The Government Of The United States As Represented By The Secretary Of The Navy | Software modeling system and method |
| US7853922B1 (en) * | 2001-05-15 | 2010-12-14 | The Mathworks, Inc. | Data objects for model-based design |
| US20120096426A1 (en) * | 2010-10-15 | 2012-04-19 | Sis Consulting, Llc | Method of extensible business object modeling and generation of system artifacts from the models |
| CN102473097A (en) * | 2010-01-13 | 2012-05-23 | 塔塔咨询服务有限公司 | A computationally efficient system for developing configurable, extensible business application product lines using model-driven techniques |
| US20160307125A1 (en) * | 2015-04-20 | 2016-10-20 | Tomas VISNOVEC | Checklist Function Integrated with Process Flow Model |
| CN107358063A (en) * | 2017-06-14 | 2017-11-17 | 北京理工大学 | Towards the FBAS functional modes of Product Conceptual Design and the Method of Conceptual Design based on the functional mode and gene expression |
| US20180075511A1 (en) * | 2016-09-09 | 2018-03-15 | BloomReach, Inc. | Attribute extraction |
| CN110288237A (en) * | 2019-06-26 | 2019-09-27 | 北京矿冶科技集团有限公司 | A kind of implementation method of dynamically configurable mineral processing circuit |
| CN110750816A (en) * | 2018-07-19 | 2020-02-04 | 西安海平方网络科技有限公司 | Method and device for building model, computer equipment and readable storage medium |
| CN111144123A (en) * | 2018-10-16 | 2020-05-12 | 工业互联网创新中心（上海）有限公司 | Industrial Internet identification analysis data dictionary construction method |
| CN111399828A (en) * | 2020-03-13 | 2020-07-10 | 上海介方信息技术有限公司 | Model-driven logic device modeling method and terminal |
| CN111950048A (en) * | 2020-08-10 | 2020-11-17 | 上海数设科技有限公司 | Mapping method and device for model of development view and mechanism view framework product prototype |
-
2020
- 2020-12-08 CN CN202011442515.9A patent/CN112394927A/en active Pending
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7853922B1 (en) * | 2001-05-15 | 2010-12-14 | The Mathworks, Inc. | Data objects for model-based design |
| US20060195460A1 (en) * | 2005-02-28 | 2006-08-31 | Microsoft Corporation | Data model for object-relational data |
| US20070168924A1 (en) * | 2005-11-17 | 2007-07-19 | The Government Of The United States As Represented By The Secretary Of The Navy | Software modeling system and method |
| CN1912830A (en) * | 2006-08-25 | 2007-02-14 | 华为技术有限公司 | Method of operating interface of definition to object mould |
| CN102473097A (en) * | 2010-01-13 | 2012-05-23 | 塔塔咨询服务有限公司 | A computationally efficient system for developing configurable, extensible business application product lines using model-driven techniques |
| US20120096426A1 (en) * | 2010-10-15 | 2012-04-19 | Sis Consulting, Llc | Method of extensible business object modeling and generation of system artifacts from the models |
| US20160307125A1 (en) * | 2015-04-20 | 2016-10-20 | Tomas VISNOVEC | Checklist Function Integrated with Process Flow Model |
| US20180075511A1 (en) * | 2016-09-09 | 2018-03-15 | BloomReach, Inc. | Attribute extraction |
| CN107358063A (en) * | 2017-06-14 | 2017-11-17 | 北京理工大学 | Towards the FBAS functional modes of Product Conceptual Design and the Method of Conceptual Design based on the functional mode and gene expression |
| CN110750816A (en) * | 2018-07-19 | 2020-02-04 | 西安海平方网络科技有限公司 | Method and device for building model, computer equipment and readable storage medium |
| CN111144123A (en) * | 2018-10-16 | 2020-05-12 | 工业互联网创新中心（上海）有限公司 | Industrial Internet identification analysis data dictionary construction method |
| CN110288237A (en) * | 2019-06-26 | 2019-09-27 | 北京矿冶科技集团有限公司 | A kind of implementation method of dynamically configurable mineral processing circuit |
| CN111399828A (en) * | 2020-03-13 | 2020-07-10 | 上海介方信息技术有限公司 | Model-driven logic device modeling method and terminal |
| CN111950048A (en) * | 2020-08-10 | 2020-11-17 | 上海数设科技有限公司 | Mapping method and device for model of development view and mechanism view framework product prototype |
Non-Patent Citations (3)
| Title |
|---|
| 候学峰: "产品经理必看：常用的UML建模详解", Retrieved from the Internet <URL:https://www.woshipm.com/pd/2699075.html/comment-page-1> * |
| 张静: "支持业务流程变化的软件系统构建方法研究", 山东大学, 15 July 2008 (2008-07-15) * |
| 谭敏;刘连臣;倪晚成;: "基于UML的信息模型中数据字典的设计与实现", 计算机工程与设计, no. 04, 28 February 2008 (2008-02-28) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113656520A (en) * | 2021-08-10 | 2021-11-16 | 广州市规划和自然资源自动化中心(广州市基础地理信息中心) | Spatial analysis method, spatial analysis device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Frank | Multi-perspective enterprise modeling (memo) conceptual framework and modeling languages | |
| Sprott et al. | Understanding service-oriented architecture | |
| US20060229922A1 (en) | Association and visualization of schematized business networks | |
| CN106507686B (en) | Method and system for designing software architecture of complex cyber-physical systems in different technical fields with its various software artifacts | |
| Noble | Basic relationship patterns | |
| Wang et al. | e-Business systems integration: a systems perspective | |
| US20060241956A1 (en) | Transforming business models | |
| Brown et al. | On components and objects: the foundations of component-based development | |
| US20130124265A1 (en) | Enterprise System/Process Modeling System and Method | |
| US11037103B1 (en) | System and method for collaborative bill of materials management | |
| US20100250296A1 (en) | Calibration framework for effort estimation | |
| Oliveira et al. | BPMN patterns for ETL conceptual modelling and validation | |
| Mattsson | Evolution and composition of object-oriented frameworks | |
| US20090049025A1 (en) | System and method for harvesting service metadata from an architecture diagram into a metadata repository | |
| Brinkkemper et al. | Functional architecture modeling for the software product industry | |
| CN112394927A (en) | Dimension-increasing form of product model and model definition method | |
| US8711142B2 (en) | Visual model importation | |
| Beuche et al. | Using requirements management tools in software product line engineering: The state of the practice | |
| Repa et al. | Methodology for Modeling and Analysis of Business Processes (MMABP). | |
| Cadavid et al. | A Domain Specific Language to Generate Web Applications. | |
| Kirikova et al. | Renaissance of business process modelling | |
| Alam et al. | Modelling a family of systems for crisis management with concern‐oriented reuse | |
| Clements | Comparing the SEI's views and beyond approach for documenting software architectures with ansi-ieee 1471-2000 | |
| Schnabel et al. | Goal-driven software development | |
| Nitsche et al. | System Dynamics Modeling for Smart and Collaborative Last Mile Networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |