CN117608524A - Project demand information architecture management system based on graphical mode - Google Patents

Abstract

The invention discloses a project demand information architecture management system based on a graphical mode, which comprises: the demand organization module is used for managing three types of nodes such as projects, folders and documents in the project demand management system; the demand information management module is used for managing and maintaining basic information, link types, document templates, development stages, baseline sets, bulletin management, partition management and other information of projects; the demand information architecture display module is used for displaying the demand information architecture of the project and establishing a link relation between the demand documents. The association relation and project information between the demand documents can be intuitively displayed and managed through the demand information architecture management system, and the uniformity, the integrity and the consistency of demand information organization are ensured.

Description

Project demand information architecture management system based on graphical mode

Technical Field

The invention relates to the field of demand engineering, in particular to a project demand information architecture management system based on a graphical mode.

Background

For the development of complex equipment systems, it is often necessary to decompose them in a hierarchical structure. The system level is added or subtracted according to the complexity of the project, for example, a large aircraft project usually comprises a plurality of complex systems such as avionics, flight control, environmental control, fire protection, electricity, power, hydraulic pressure, fuel oil and the like, and each system is decomposed into a plurality of subsystems of lower level, so that more levels are needed for decomposition, and the number of subsystems of each level should be reduced as much as possible, and the boundaries are clear and independent. Typically, during system demand development, the high-level demand at the system level may be broken down into a number of more detailed low-level demands that will be distributed among the top-level demands of the different subsystems, and of course, these demands will be broken down further into manufacturable, producible units at the device level or even lower.

The resolution of requirements is often developed for the statement of a problem, which once distributed among the subsystems of the system requires further consideration of the design implementation. The essence of complex equipment development is that determining the systems that need to be employed, assigning demands to those systems is an iterative design process, and the designer's task is to decide which systems to employ to address a problem and assign demands to those systems while taking into account all known or derived system constraints and requirements. Thus, the designer also decides on the optimal combination of systems based on constraints and ensures that it meets the top-level requirements to the greatest extent. However, in the actual project development process, a complex equipment system usually needs to be defined jointly by members of multiple teams and across professions, but due to different attention angles in the professional fields, certain requirements cannot be met at the same time or even contradict each other. Thus, there is a need for efficient organization and association of requirements of complex equipment systems through a requirement information architecture.

The demand information architecture is an overall understanding of the development process of the equipment system, and through the demand information architecture, a designer can globally understand the product design, quickly understand the inputs required by the product design and the outputs generated by the design activity. In the aspect of demand organization management, a current mainstream demand management tool at home and abroad has one mode of deeply binding demands and life cycle management of products, and paying attention to the consistency of upstream demands and downstream product designs in the product development process, but the method lacks overall grasp of the product demands; the other way is to establish the demand information architecture by adopting a traditional manual way, which is extremely easy to introduce errors due to human factors and cannot guarantee the correctness of the demand organization.

In a word, most of the demand management tools at home and abroad are difficult to ensure the integrity and the correctness of demand information organization in the demand organization mode and the management and maintenance process, and can not effectively manage and maintain the system demand information architecture. Therefore, there are many problems in the practical engineering application process, and an efficient and convenient system demand information architecture management system needs to be constructed so as to improve the demand organization management efficiency.

Disclosure of Invention

In order to solve the technical problems, the invention provides a project demand information architecture management system based on a graphical mode.

The technical scheme of the invention is as follows: a project demand information architecture management system based on a graphical manner, comprising:

the demand organization module is used for managing three types of nodes such as projects, folders and documents in the project demand management system;

the demand information management module is used for managing and maintaining basic information, link types, document templates, development stages, baseline sets, bulletin management, partition management and other information of projects;

the demand information architecture display module is used for displaying the demand information architecture of the project and establishing a link relation between the demand documents.

Compared with the prior art, the invention has the following advantages:

the invention discloses a project demand information architecture management system based on a graphical mode, which can create a demand organization frame based on the graphical mode, support the definition of multiple types and multiple levels of demand levels, support the establishment of tracking links among demand documents in a dragging mode, and support the display of the link relation among the documents in the graphical mode. Meanwhile, the system supports global configuration of information such as link types, document templates, development stages, bulletin management and the like on project nodes, supports establishment of baselines for any one or more documents under the project through a baseline set, and improves demand organization management efficiency. The system disclosed by the invention can change the traditional manual establishment and maintenance demand organization system mode, avoid the occurrence of errors caused by manual intervention and ensure the uniformity, the integrity and the consistency of demand information organization.

Drawings

FIG. 1 is a block diagram of a project demand information architecture management system based on a graphical manner in an embodiment of the present invention;

FIG. 2 is a schematic diagram of an organization structure of project requirements according to an embodiment of the present invention;

FIG. 3 is a basic information page diagram of an item in an embodiment of the present invention;

FIG. 4 is a schematic diagram of a link type page of an item in an embodiment of the present invention;

FIG. 5 is a schematic diagram of a document template page of an item in an embodiment of the present invention;

FIG. 6 is a schematic diagram showing all the custom template information under a project under a document template tab of the project in an embodiment of the invention;

FIG. 7 is a schematic view of a development stage page of an embodiment of the present invention;

FIG. 8 is a diagram of a baseline collection page of an item in an embodiment of the present invention;

FIG. 9 is a schematic diagram of an advertisement management page of an item according to an embodiment of the present invention;

FIG. 10 is a diagram of a partition management page of an item according to an embodiment of the present invention;

FIG. 11 is a diagram of basic information of a file folder or document in an embodiment of the invention;

FIG. 12 is a schematic diagram showing a graphical representation of a demand organization structure and a link relationship in an embodiment of the present invention.

Detailed Description

The invention provides a project demand information architecture management system based on a graphical mode, which can quickly establish a demand organization frame, intuitively display and manage association relations and project information among demand documents and ensure the uniformity, the integrity and the consistency of demand information organization.

The present invention will be further described in detail below with reference to the accompanying drawings by way of specific embodiments in order to make the objects, technical solutions and advantages of the present invention more apparent.

The demand information architecture is an overall grasp of the product development flow, and can help a designer to globally understand the product design, quickly understand the input required by the product design and the output generated by the design activity; the method can help the demand development to check leakage and repair deficiency of demands, and avoid conflict and inconsistency between demands; the method can help project management personnel to timely track the progress of demand development and analyze the change influence in the demand change process. The system provided by the invention can help a demand manager to conveniently and efficiently manage the demand information of the project, and ensure the uniformity, the integrity and the consistency of demand information organization.

Example 1

As shown in fig. 1, the project requirement information architecture management system based on a graphical manner provided in the embodiment of the present invention includes the following modules:

the demand organization module is used for managing three types of nodes such as projects, folders and documents in the project demand management system;

the demand information management module is used for managing and maintaining basic information, link types, document templates, development stages, baseline sets, bulletin management, partition management and other information of projects;

the demand information architecture display module is used for displaying the demand information architecture of the project and establishing a link relation between the demand documents.

As shown in table 1, the demand information architecture management system constructed in this embodiment uses 14 database object tables in the demand management tool.

Table 1 demand information architecture management system database object table

RDMS_DATABASE_TREE	Demand structure tree table
		RDMS_PROJECT	Item table
RDMS_PRO_MEMBER	Project membership list
		RDMS_FILE	Demand document form
RDMS_FOLDER	Demand folder meter
		RDMS_FILE_DIRECTOR	Document responsibility people table
RDMS_ORG_FOLDER_MEMBER	Organizing folder member tables
		RDMS_rightS	Demand rights table
RDMS_FILE_REL	Document relation table
		RDMS_DEV_STAGE	Development stage table
RDMS_LINK_STYLE	Link type table
		RDMS_SCAN_RECORD	Browsing record list
RDMS_NOTICE_MSG	Demand message table
		RDMS_PROJECT_FOCUS	Item table of interest

The requirement structure TREE table RDMS_DATABASE_TREE is used for storing requirement structure TREE information of a requirement DATABASE, the PROJECT table RDMS_PROJECT is used for storing PROJECT information in the requirement DATABASE, the requirement FOLDER table RDMS_FOLDER is used for storing FOLDER information in the requirement DATABASE, the requirement document table RDMS_FILE is used for storing document information in the requirement DATABASE, and the document relation table RDMS_FILE_REL is used for storing link information among documents in the requirement DATABASE. Wherein RDMS is item identification, DATABASE is DATABASE, TREE is structure TREE, FOLDER is FOLDER, FILE is document, REL is document relation.

The main interfaces operating the demand information architecture management system follow a restfull style, the main interfaces are shown in table 2, apI + items+modules+components are used as interface prefixes, actual function descriptions+path parameters are used as interface suffixes, 12 main interfaces related to a demand tree structure and prefixed by api/rdms/reqman/dms databasefiles are formed, 10 main interfaces related to items and prefixed by api/rdms/reqman/rdmssubjects are formed, 7 main interfaces related to folders and 15 main interfaces related to documents and prefixed by api/rdms/reqman/rdmsfiles are formed.

Table 2 requirement information architecture management system interface description

In one embodiment, the above construction of the demand organization module 1 specifically includes:

as shown in FIG. 2, requirements can be organized by type nodes such as projects, folders, documents, and the like.

The project is the highest node under the root node of the demand database, and only a new project can be built under the database, and folders or documents and the like cannot be built. After entering the system, the project manager firstly opens a main interface of the requirement information framework, the left interface is a TREE structure of the requirement information framework, the root node is a DATABASE, and the system acquires all node data with corresponding authority of the project manager from RDMS_DATABASE_TREE. The right key database menu of the project manager can open functions such as adding project, pasting, configuring data sources and the like, wherein clicking the adding project can create a project under the database; after copying other items, clicking "paste" can paste the content of the copied item under the item, clicking "configure data source" can configure data source information of other systems and then read the data to the system.

Folders or documents can be built under the project, and the project cannot be newly built. PROJECT data is obtained from rdms_process. The right-click project menu can open functions such as adding a folder, adding a document, editing, copying, pasting, deleting, extracting a template, attribute and the like, clicking the adding folder can create a folder under a project, clicking the adding document can create a document under the project, clicking the editing can modify basic information of the project, clicking the pasting can be performed under the project to paste data such as the folder and the document under the project after copying the folder and the document, clicking the deleting can delete all information under the project, clicking the extracting template can extract the project into a template to be stored in a template library, and clicking the attribute can check basic information and access right of the project.

FOLDERs or documents may be built under the FOLDERs, and the data of the FOLDERs is obtained from the rdms_folder table. The right-click folder menu enables opening "add folder", "add document", "edit", "copy", "paste", "delete", "attribute". Clicking the "add folder" can create a new folder under the folder, clicking the "add document" can create a document under the project, clicking the "edit" can modify the basic information of the folder, clicking the "paste" under the folder to paste the data under the folder after copying the folder, the document, clicking the "delete" can delete all the information under the folder, clicking the "attribute" can view the basic information and access rights of the folder.

The document is the end-most node, no type of node can be built under the document, and the document data is obtained from RDMS_FILE, RDMS_FILE_DIRECTOR tables. The right-key document menu can open functions such as read-only opening, editing opening, copying, pasting, deleting, extracting templates, attributes and the like. Clicking "read only open" can open definition and editing interface of demand and read only can not edit, clicking "edit open" can open definition and editing interface of demand and can edit, clicking "copy" can copy the file, clicking "delete" can delete all information under the file, clicking "extract template" can extract the file into file template, clicking "attribute" can look over project basic information, access right, history record, attribute, file trace back etc.

In one embodiment, the building the requirement information management module specifically includes:

as shown in fig. 3, the requirement information management module is capable of managing and maintaining management information of items, folders, and documents. When the click node is of a project type, information such as corresponding project basic information, link type, document template, development stage, baseline set, bulletin management, partition management and the like can be displayed on the right side interface of the demand information architecture main interface. When the click node is a folder or a document type, the right interface displays the basic information of the corresponding folder or document.

As shown in fig. 4, under the basic information tab of the item, basic information such as the name, security level, responsible person, etc. of the item is displayed, and the basic and modifiable information of the item can be modified by clicking "edit". In addition, the user may also focus on the item of interest by illuminating the focus icon.

As shown in FIG. 5, under the link type tab of an item, all of the base link types and custom link types in the item are displayed. Clicking "add" can open the newly added interface, filling in the link information and clicking to save the newly added link type. Clicking "edit" will prompt to select the data to be modified, clicking edit after selecting one piece of data to be modified can enter the editing interface, clicking save after modifying the data of the link type can modify the link type. Clicking "delete" will prompt the selection of data to delete, if the data prompt "determine that the selected data is to be deleted? "click on determine can delete the link type, choose cancel return to the list interface.

As shown in FIG. 6, under a document template tab for a project, all custom template information for the project is displayed. In the tab, daily maintenance operations such as adding, deleting, and the like can be performed on the document template. Clicking 'add', can open new interface of the file, fill in the field of name, type, etc., click save can newly add the file template, click cancel and return to the file template main interface; clicking "edit", which can open the editing interface of the document, after modifying the corresponding field, clicking save, which can modify the document template, clicking cancel, and returning to the document template main interface; clicking "delete" prompts "determining to clear? All information under the template is cleared and can not be recovered, the template can be deleted by clicking and determining, and the document template main interface is returned by clicking and canceling.

As shown in fig. 7, under the development stage tab of the project, all development stage information under the project is displayed. Clicking 'add', opening new interface, filling stage information, clicking and saving, and adding development stage; clicking "edit" can prompt to select the data to be modified, clicking edit after selecting one piece of data to be modified can enter an editing interface, clicking save after modifying the data of the stage can modify the development stage; clicking "delete" will prompt the selection of data to delete, if the data prompt "determine that the selected data is to be deleted? "click confirm can delete this development stage, choose cancel return to the tabulation interface.

As shown in FIG. 8, under the baseline set tab of the project, all the created baseline information under the project is displayed, and baseline operation can be performed on any one or more documents under the project, so that the baseline management on the requirements can be realized conveniently and efficiently. Clicking 'newly added', opening a newly added interface, filling in information such as names, descriptions, selecting modules for baseline making and the like, and clicking and storing to obtain a newly added baseline set; clicking "edit" can prompt to select the data to be modified, clicking edit after selecting one piece of data to be modified can enter the editing interface, clicking save after modifying the description of the baseline set, and modifying the baseline set.

As shown in fig. 9, under the bulletin management tab of an item, all bulletin detail information of the item is displayed. Clicking 'new adding', opening a new adding interface, filling out notice information, clicking and storing, and then, newly adding project notices; clicking edit, prompting to select data to be modified, clicking edit after selecting one piece of data to be modified, entering an edit interface, clicking save after modifying the announced data, and modifying the project announcement; clicking "delete" will prompt the selection of data to delete, if the data prompt "determine that the selected data is to be deleted? "click to confirm can delete the project bulletin, choose to cancel and return to the list interface.

As shown in fig. 10, under the partition management tab of an item, all the import partition and export partition information under the item is displayed. In the page, daily maintenance operations such as adding, deleting and synchronizing the partition can be performed. The partition management interface adopts an up-down layout, wherein the upper part is a export partition module, and the lower part is a import partition module. When exporting the partitions, the user can select the exported documents, set access rights for each document, edit the corresponding attributes or the corresponding views, remark the exported user, and then conduct the export operation. The derived data is generated and a corresponding key is generated. When the partition operation is imported, the data and the corresponding key are required to be imported at the same time, and the imported data can be processed only when the key verification is passed, so that the security of the data is improved.

As shown in fig. 11, when the click node is a folder or a document type, detailed information, typically basic information, of the corresponding folder or document is displayed, and "edit" is clicked, the basic and modifiable information of the folder, document can be modified.

In one embodiment, the building the requirement information architecture display module specifically includes:

as shown in fig. 12, the requirement information architecture display module can display all nodes under the project, parent-child relationships among the nodes and link relationships among the nodes.

All the sub-nodes under the project in the demand database are extracted, then are sequenced according to the path of each sub-node, and all the nodes under the project are displayed in rectangular graphic frames with different identifications by adopting an ant-x6 technology,representing items, & lt + & gt>Representing a folder->Representing a document. In addition, the new adding and deleting icons are added on the project and folder frames, so that the new adding and deleting functions can be realized. Clicking the "+" sign on the project graphic frame can create a new folder and document, clicking the "-" sign can delete the project; clicking the "+" sign on the folder graphic frame can create a new folder and document, and clicking the "-" sign can delete the folder; clicking on the "-" sign on the document graphical box may delete the document.

Different color lines are used to represent different link types, arrows are used to represent the link relationships between documents under items, and the arrows point to represent parent-child relationships. Two circles "o" are provided on the right border of the document icon, wherein the "o" in the upper right corner indicates an incoming link, and the "o" in the lower right corner indicates an outgoing link. Clicking the O at the upper right corner of the document graphic frame to drag to the O at the upper right corner of another document, prompting the selection type, and establishing the link relation between the two modules after the selection type is finished. Clicking on the "x" on the link relationship line deletes the link between the two documents.

According to the embodiment of the invention, the demand structure tree information of the demand database is organized by three node types of the project, the folder and the document, the basic information, the link type, the document template, the development stage, the baseline set, the bulletin management, the partition management and other information of the project can be managed and maintained, and the architecture relationship among all folders and documents and the link relationship among the documents under the project can be intuitively displayed in a graphical mode. The system can rapidly initialize the product demand information architecture, provide convenient management functions of demand organization information, ensure uniformity, integrity and consistency of demand information organization, and avoid error occurrence of manual intervention, thereby improving demand organization management efficiency.

The above examples are provided for the purpose of describing the present invention only and are not intended to limit the scope of the present invention. The scope of the invention is defined by the appended claims. Various equivalents and modifications that do not depart from the spirit and principles of the invention are intended to be included within the scope of the invention.

Claims (10)

1. A project demand information architecture management system based on a graphical manner, comprising:

the demand organization module is used for managing three types of nodes of projects, folders and documents in the project demand management system;

the demand information management module is used for managing and maintaining basic information, link types, document templates, development stages, baseline sets, bulletin management and partition management information of projects;

the demand information architecture display module is used for displaying the demand information architecture of the project and establishing a link relation between the demand documents.

2. The system for managing project demand information architecture based on a graphical manner according to claim 1, wherein the demand organization module is configured to organize and manage demands, and specifically comprises:

organizing the requirements of each system or product by nodes, wherein the nodes comprise projects, folders and documents; the organization rules of each node are as follows:

the project is the highest node under the root node of the demand database, and only a new project can be built under the database, and a folder or a document cannot be built;

under the project allows the creation of folders or documents, but cannot create projects;

allowing a folder or a document to be built under the folder;

the document is the endmost node and no type of node can be built under the document.

3. The graphical-based project requirement information architecture management system according to claim 1, wherein the requirement information management module specifically comprises:

when clicking a certain node of the left tree, more detail information of the node can be seen according to the node type, and editing and modifying can be carried out on the detail information;

when the click node is a project type, displaying the project related detail information, including basic information, information architecture, link type, document template, development stage, baseline set, bulletin management and partition management information;

and when the clicked node is a folder or a document type, displaying basic information of the corresponding folder or document.

4. The graphical-based project demand information architecture management system of claim 1, wherein the demand information architecture display module specifically comprises:

displaying the architecture relation among all folders and documents under the project;

displaying the link relation between the documents under the project;

by dragging the creation links, various types of link relationships between documents can be established.

5. The graphical-based project requirement information architecture management system of claim 3, wherein:

and displaying the name, the security level and the responsible person information of the project under the basic information tab of the project.

6. The graphical-based project requirement information architecture management system of claim 3, wherein:

and displaying all basic link types and custom link types in the project under the link type tab of the project.

7. The graphical-based project requirement information architecture management system of claim 3, wherein:

and displaying all the custom template information under the project under the document template tab of the project.

8. The graphical-based project requirement information architecture management system of claim 3, wherein:

under the development stage tab of the project, displaying all development stage information under the project.

9. The graphical-based project requirement information architecture management system of claim 3, wherein:

displaying all created baseline information under the project under the baseline set tab of the project, or performing baseline operation on any one or more documents under the project;

displaying all announcement detail information under the project under the announcement management tab of the project;

under the partition management tab of an item, all imported partition and exported partition information under the item is displayed.

10. The graphical-based project demand information architecture management system of claim 4, wherein the demand information architecture presentation module:

all the sub-nodes under the items in the demand database are extracted, and then are sequenced according to the path of each sub-node to be displayed in different modes.