CN110084564B

CN110084564B - ICE architecture for project data management

Info

Publication number: CN110084564B
Application number: CN201910334986.9A
Authority: CN
Inventors: 李振
Original assignee: Individual
Current assignee: Individual
Priority date: 2019-04-24
Filing date: 2019-04-24
Publication date: 2021-07-02
Anticipated expiration: 2039-04-24
Also published as: CN110084564A

Abstract

The present invention relates to an ICE architecture for project data management, comprising: a summary database including a conceptual structure of a plurality of tree structures, the conceptual structure including an instance structure of a plurality of tree structures; wherein the tree hierarchy and the nodes of the example structure respectively correspond to the corresponding tree hierarchy and nodes of the concept structure; according to the invention, huge project data and process management work become clear, definite and orderly through the total database, the concept structure and the example structure.

Description

ICE architecture for project data management

Technical Field

The invention belongs to the technical field of data management and programming, and particularly relates to an ICE (Internet communications and Internet communications) architecture for project data management.

Background

Today, all walks of life are unable to keep computers in the advanced computer technology. We use computers to manage large numbers of data files. Some of the files are project results, some are semi-finished products in execution, some need editing, some need auditing and the like. Those industries that rely on electronic data are often faced with a tremendous amount of data file management tasks.

In the related art, computers need to manually classify and manage various files stored in the computers, so that data management work is very complicated and errors are easy to make. Although some industries have corresponding data and process management software on the market, most process software processes are rigid and cannot adapt to industries with diversified data management processes.

Disclosure of Invention

In view of the above, an objective of the present invention is to overcome the deficiencies of the prior art, and provide an ICE architecture for project data management to solve the problems in the prior art that the data management work in a computer is very complicated, errors are easy to occur, and the computer cannot adapt to diversified industries.

In order to achieve the purpose, the invention adopts the following technical scheme: an ICE architecture for project data management, comprising:

a summary database including a conceptual structure of a plurality of tree structures, the conceptual structure including an instance structure of a plurality of tree structures;

wherein the tree hierarchy and the nodes of the example structure respectively correspond to the corresponding tree hierarchy and nodes of the concept structure.

Further, the total database derivation planning module is used for providing a method for acquiring corresponding data paths according to different use platforms;

the conceptual structure derivative model module;

the instance structure derivative item module;

wherein the planning module comprises a plurality of model modules, and the model modules comprise a plurality of project modules.

Further, the model module comprises: field declarations and data declarations;

the project module includes: field values and data instances.

Further, the field declaration and the field value constitute a field system for storing names, types, qualification conditions and corresponding values of fields required in the project management process;

the data declaration and the data instance form a data system;

the data declaration is used for providing a base class for the data directory declaration and the data file declaration, namely the data directory declaration and the data file declaration are derived from the data declaration;

and the data instance is used for solving the actual name of the project file by combining the specific field value in the data instance according to the name expression so as to obtain the actual path of the project file.

Further, the data instance includes:

the data directory instance is used for realizing the data directory statement, namely, the result obtained according to the expression stored in the data directory statement;

data file instances for implementing data file statements, i.e., results derived from expressions stored by the data file statements.

Further, the data declaration includes:

the data directory statement is used for storing the data directory expression;

and the data file statement is used for storing the data file expression.

Further, the data system further comprises:

and the data container is used for providing a base class for the data directory declaration and the data directory instance, namely the data container derives the data directory declaration and the data directory instance.

Further, the planning module can add public attributes and public methods.

By adopting the technical scheme, the invention can achieve the following beneficial effects:

according to the invention, huge project data and process management work become clear, definite and orderly through the total database, the concept structure and the example structure.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a core infrastructure diagram of an ICE architecture for project data management in accordance with the present invention;

fig. 2 is a schematic diagram of a core structure of an ICE architecture for project data management and a relationship between the core structure and a PMP structure derived from the core structure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.

A specific ICE architecture for project data management provided in embodiments of the present application is described below with reference to the accompanying drawings.

As shown in fig. 1, the ICE architecture for project data management provided in the embodiment of the present application includes:

a general database 1, including a plurality of tree-structured conceptual structures 2, the conceptual structures including a plurality of tree-structured instance structures 3;

wherein, the tree hierarchy and the nodes of the example structure 3 respectively correspond to the corresponding tree hierarchy and nodes of the concept structure 2.

The operating principle of the ICE architecture for project data management is: the application provides an ICE (Idea-Concept-Example) architecture, which is a project data management thinking architecture with a wide application range; specifically, the Idea is taken as an overall database, and a Concept structure 2(Concept) of a tree structure is accommodated, wherein each Concept tree node corresponds to a plurality of Example structures 3 (instances). An Example is also a tree structure, but the Example tree node of each level corresponds to one Concept tree node of the corresponding level. Therefore, various tree concepts and corresponding example structures can be derived at the later stage so as to meet the requirements of project structures in different fields.

In some embodiments, as shown in fig. 2, the total database 1 is a derivation planning module, configured to provide a method for obtaining corresponding data paths according to different usage platforms;

the concept structure 2 derivative model module;

the instance structure 3 derived item module;

Specifically, Idea, Concept and Example proposed in the present application derive three main concepts of Planning, Module and Project respectively to implement the ICE core architecture.

Planning, derived from Idea, has the functionality of Idea, and on top of that, various common attributes and methods can also be added by subsequent users. So that Planning can not only accommodate Concept but also adapt to a specific project environment. The relationship between Module and Project is the same as that between Concept and Example, and the relationship between field declaration and field value is similar, and the relationship between data declaration and data instance is also similar.

In some embodiments, the model module comprises: field declarations and data declarations;

the project module includes: an item field value and a data instance.

That is, the Module derived from Concept contains field declarations and data declarations, while the Project derived from Example contains item field values and data instances.

In some embodiments, the field declaration and field value constitute a field system for storing a name, a type, a qualification, and a corresponding value of a field required by the item structure;

the data declaration and the data instance form a data system;

and the data instance is used for solving the actual name of the data by combining the specific field value in the Project according to the name expression and acquiring the actual path of the data.

Specifically, the term "field" comes from database management, i.e., a record member that is used to compose a piece of data. Fields include the name, type and value of the field, for example: "name" is a field name, and the type of this field is a String (String), for example: the name and character of China are regulated to be between 2 and 6 Chinese characters, so the value of the field must be 2 to 6 Chinese characters, and the 'Xiaoming' is the value of the field. In the field system, the 'field declaration' is equivalent to the name, type and definition of a field, and a plurality of 'field declarations' are collected and put in a Module as an attribute which is specially used for storing a plurality of field names and types. In Project, there is a set of 'field value' corresponding to the Project, but there is not only 'field value' in the set, but also a set of 'field declaration' read from Module corresponding to the Project, each read 'field declaration' corresponds to a 'field value' of the same type, and then these data are stored in Project according to the correspondence. Thus, a complete field system is formed.

In some embodiments, the data instance comprises:

In some embodiments, the data declaration comprises:

the data directory statement is used for storing the data directory expression;

and the data file statement is used for storing the data file expression.

The relationships of "data claims" and "data instances" in the present application and the relationships of "field claims" and "field values" in the field system are similar, but there are two basic types of data: "directory" and "file". The 'directory declaration' exists in the Module, and in the Example corresponding to the Module, there is a 'directory instance' corresponding to the Module, and the 'directory declaration' is realized through the attribute and field value of the Example where the 'directory instance' exists. The "document declaration" and "document instance" are the same.

In short, it is the "data declaration" that determines how the directory should be named, and the "data instance" names the data exactly in the way the declaration is given.

For example, the following steps are carried out: the father of a surname king decides to name the children of four generations of Chinese characters according to a certain rule, namely, the four children respectively take one character of the Chinese characters in the Shaoxing as the second character of the name according to the size sequence, and the named expression in the data statement specified by the father is as follows: "surname of father-generation division word-the number of words in the Chinese idiom of revival is the number of children respectively. So his four children as "data instances" are named "king" for "king", for "king of the country", and for "king of the country", respectively.

In some embodiments, the data system further comprises:

Specifically, in a computer, whether a file or a directory is provided, a storage location is needed, that is, a "container" is a data container, and the directory can store the file, so that the directory can be seen as a container, and the disk can store the directory and the file, so that the disk is also a container, but the directory or the file cannot be stored under the file, so that the file is not a container.

In this architecture, the data root is the root node of the data hierarchy, below which all data belongs below this path. The "data root" provides three path string fields corresponding to the currently mainstream three major operating systems — Windows, MacOS, and Linux. And provides a method for acquiring corresponding path values according to different system platforms.

Preferably, the types of the fields include:

text, number, time, boolean, color, percentage.

Preferably, the values of the fields adopt: 2-6 Chinese characters.

Preferably, the planning module can also add public attributes and public methods.

In summary, the invention makes the huge project data and process management work clear, clear and orderly through the total database, the concept structure and the example structure.

It is understood that the above-mentioned embodiments of the method provided correspond to the above-mentioned embodiments of the ICE architecture for project data management, and the corresponding specific contents may be referred to each other, which is not described herein again.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create an ICE architecture for project data management that implements the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including an ICE architecture for project data management that implements the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. An ICE architecture for project data management, comprising:

wherein the tree hierarchy and the nodes of the example structure respectively correspond to the corresponding tree hierarchy and nodes of the concept structure;

the total database derivation planning module is used for providing a method for acquiring corresponding data paths according to different use platforms;

the conceptual structure derivative model module;

the instance structure derivative item module;

wherein the planning module comprises a plurality of model modules, the model modules comprising a plurality of project modules;

the model module comprises: field declarations and data declarations;

the project module includes: field values and data instances;

the field declaration and field value form a field system used for storing the name, type, limiting condition and corresponding value of the field required in the project management process;

the data declaration and the data instance form a data system;

2. The ICE architecture for project data management of claim 1, wherein the data instances comprise:

3. The ICE architecture for project data management according to claim 1, wherein the data declarations include:

the data directory statement is used for storing the data directory expression;

and the data file statement is used for storing the data file expression.

4. The ICE architecture for project data management of claim 1, wherein the data system further comprises:

5. The ICE architecture for project data management of claim 1, wherein the planning modules are further capable of adding common attributes and common methods.