CN111461666A

CN111461666A - Demand tracking matrix display method and system

Info

Publication number: CN111461666A
Application number: CN202010266752.8A
Authority: CN
Inventors: 刘伟; 周可; 李迎辉
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp
Priority date: 2020-04-07
Filing date: 2020-04-07
Publication date: 2020-07-28

Abstract

The embodiment of the application provides a method and a system for displaying a demand tracking matrix, wherein the method comprises the following steps: receiving a state query request aiming at a target software development project, wherein the state query request comprises a requester role identifier; selecting at least one piece of preset display visual angle information as target visual angle information according to the role identifier of the requester; selecting a corresponding target demand tracking matrix from a plurality of demand tracking matrices corresponding to a target software development project based on target visual angle information, wherein the demand tracking matrix is generated offline according to state data of the target software development project collected offline in each development stage in a preset software full life cycle and a corresponding data table model; and outputting the target demand tracking matrix to a preset visualization unit for displaying. The display comprehensiveness and the reliability of the demand tracking matrix can be effectively improved, the demand tracking matrix with strong pertinence can be displayed quickly and in real time, and user experience is effectively improved.

Description

Demand tracking matrix display method and system

Technical Field

The application relates to the technical field of data processing, in particular to a method and a system for displaying a demand tracking matrix.

Background

The demand tracking matrix is a table that links product demand from its source to deliverables that meet the demand, and relates product demand to business or project goals, enabling easy observation of the status of each demand during the entire project cycle, ensuring that each demand approved in the demand document is delivered at the end of the project. Meanwhile, when the requirements are changed, the design is changed, the codes are changed and the test cases are changed, the influence range affected by the change can be effectively analyzed, and a basis is provided for making effective measures. At present, a demand tracking matrix becomes a convenient tool for effectively knowing the development progress of a software product, and how to display the demand tracking matrix also becomes a basic subject for researching the development progress of the software product.

At present, the display mode of the demand tracking matrix is mainly to display a demand tracking matrix with a uniform format to all viewing users, however, in the whole project cycle, the attention points of each team and each role are different, and the individual demands of each team cannot be met by one uniform display result. Meanwhile, data at each stage in the full life cycle, such as demands, implementation progress and the like, are usually distributed on different platforms, and it is difficult to display a comprehensive demand tracking matrix on one platform when a customer queries.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a method and a system for displaying a demand tracking matrix, which can effectively improve the display comprehensiveness and reliability of the demand tracking matrix, can quickly display the demand tracking matrix with strong pertinence in real time, further effectively improve the user experience, and effectively improve the efficiency and accuracy for acquiring the development progress of a software product according to the display content of the demand tracking matrix.

In order to solve the technical problem, the application provides the following technical scheme:

in a first aspect, the present application provides a method for displaying a demand tracking matrix, including:

receiving a state query request aiming at a target software development project, wherein the state query request comprises a requester role identifier;

selecting at least one piece of preset display visual angle information as target visual angle information according to the requester role identification;

selecting a corresponding target demand tracking matrix from a plurality of demand tracking matrices corresponding to the target software development project based on the target visual angle information, wherein the demand tracking matrix is generated offline according to state data of the target software development project in each development stage in a preset software full life cycle collected offline and a corresponding data table model;

and outputting the target demand tracking matrix to a preset visualization unit for displaying.

Further, the requester role identification includes: at least one of a business requirement presenter identification, a product manager identification, a project manager identification, and a technology implementer identification;

correspondingly, the selecting at least one of the preset display view angle information as the target view angle information according to the requester role identifier includes:

and selecting target visual angle information from the project visual angle information corresponding to the service requirement presenter, the service requirement visual angle information corresponding to the product manager, the requirement item visual angle information corresponding to the project manager and the requirement plan visual angle information corresponding to the technical implementer according to the requester role identifier, wherein the target visual angle information is the same as the requester role identifier in number.

Further, the plurality of requirement tracking matrices corresponding to the target software development project include:

the system comprises a demand tracking matrix corresponding to a project visual angle, a demand tracking matrix corresponding to a business demand visual angle, a demand tracking matrix corresponding to a demand project visual angle and a demand tracking matrix corresponding to a demand plan visual angle.

Further, before the receiving the status query request for the target software development project, the method further includes:

collecting state data of each development stage of the target software development project in a preset software full life cycle in an off-line manner, wherein the state data of each development stage comprises the following steps: developing task data, analyzing number data, designing number data, developing number data, component unit data, building and assembling data, application and assembling data, user test data and version inspection data;

acquiring a preset data table model, dimensionality, a construction functional module and construction logic data corresponding to each piece of display visual angle information;

generating a demand tracking matrix corresponding to each piece of display visual angle information in an off-line manner based on state data of each development stage of the target software development project in a preset software full life cycle, and a data table model, a dimension, a construction function module and a construction logic corresponding to each piece of display visual angle information;

and storing the demand tracking matrix corresponding to each piece of display visual angle information as a plurality of demand tracking matrices corresponding to the target software development project.

Further, the data table model is used for storing the corresponding relation among data names, field types and description contents;

the data sheet model comprises a preset demand tracking matrix project visual angle model, a project visual angle and business department visual angle sub-sheet model, a business department visual angle model, a demand item visual angle model and a development task detail model.

Further, after the outputting the target demand tracking matrix to a preset visualization unit for displaying, the method further includes:

if a keyword retrieval request aiming at a target software development project is received, extracting keywords corresponding to the keyword retrieval request;

and searching and displaying data corresponding to the keywords in a target demand tracking matrix in the visualization unit.

In a second aspect, the present application provides a demand tracking matrix display system comprising:

the system comprises a first request receiving subsystem, a first state query subsystem and a second state query subsystem, wherein the first request receiving subsystem is used for receiving a state query request aiming at a target software development project, and the state query request comprises a requester role identifier;

the target visual angle determining subsystem is used for selecting at least one piece of preset display visual angle information as target visual angle information according to the requester role identifier;

a target demand tracking matrix selection subsystem, configured to select a corresponding target demand tracking matrix from multiple demand tracking matrices corresponding to the target software development project based on the target view information, where the demand tracking matrix is generated offline according to state data of the target software development project collected offline in each development stage within a preset software full life cycle and a corresponding data table model;

and the target demand tracking matrix display subsystem is used for outputting the target demand tracking matrix to a preset visualization unit for display.

correspondingly, the target view determining subsystem is specifically configured to perform the following:

Further, still include:

the off-line data collection subsystem is used for off-line collecting the state data of each development stage of the target software development project in a preset software full life cycle, wherein the state data of each development stage comprises: developing task data, analyzing number data, designing number data, developing number data, component unit data, building and assembling data, application and assembling data, user test data and version inspection data;

a generation parameter acquisition subsystem, configured to acquire a preset data table model, a dimension, a construction function module, and construction logic data corresponding to each piece of display view information;

the matrix offline generation subsystem is used for generating a demand tracking matrix corresponding to each piece of display visual angle information in an offline manner based on state data of each development stage of the target software development project in a preset software full life cycle, and a data table model, a dimension, a construction function module and a construction logic corresponding to each piece of display visual angle information;

and the matrix storage subsystem is used for storing the demand tracking matrixes corresponding to the display visual angle information into a plurality of demand tracking matrixes corresponding to the target software development project.

Further, still include:

the second request receiving subsystem is used for extracting keywords corresponding to the keyword retrieval request if the keyword retrieval request aiming at the target software development project is received;

and the filtering display subsystem is used for searching and displaying the data corresponding to the keywords in the target demand tracking matrix in the visualization unit.

In a third aspect, the present application provides an electronic device, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the demand tracking matrix display method when executing the program.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the demand tracking matrix display method described herein.

According to the technical scheme, the demand tracking matrix display method and system provided by the application comprise the following steps: receiving a state query request aiming at a target software development project, wherein the state query request comprises a requester role identifier; selecting at least one piece of preset display visual angle information as target visual angle information according to the requester role identification; selecting a corresponding target demand tracking matrix from a plurality of demand tracking matrices corresponding to the target software development project based on the target visual angle information, wherein the demand tracking matrix is generated offline according to state data of the target software development project in each development stage in a preset software full life cycle collected offline and a corresponding data table model; the target demand tracking matrix is output to a preset visualization unit for display, the use conditions of the demand items in each development stage can be displayed and counted in different visual angles according to roles in the whole life cycle, thereby effectively improving the display comprehensiveness and the reliability of the demand tracking matrix, collecting the state data of the software development project in each development stage of different platforms in advance in an off-line manner, and generating all demand tracking matrixes corresponding to the software development project in advance and off-line based on the state data, further, when a state inquiry request is received, the corresponding demand tracking matrix can be displayed rapidly and in real time, the displayed content is very comprehensive, so that the user experience can be effectively improved, and the efficiency and the accuracy of acquiring the development progress of the software product according to the display content of the demand tracking matrix are effectively improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is an exemplary diagram of a software full lifecycle.

Fig. 2 is a schematic flow chart of a demand tracking matrix display method in the embodiment of the present application.

Fig. 3 is a flowchart illustrating a method for displaying a demand tracking matrix including step 210 according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating a method for displaying a demand tracking matrix including steps 010 to 040 according to an embodiment of the present invention.

Fig. 5 is a flowchart illustrating a method for displaying a demand tracking matrix according to an embodiment of the present invention, including steps 500 to 600.

Fig. 6 is a data processing flow chart provided in an application example of the present application.

FIG. 7 is a diagram illustrating the effect of viewing angle display of requirement items in an application example of the present application.

Fig. 8 is a view showing a service requirement view in an application example of the present application.

Fig. 9 is a view showing a project view in an application example of the present application.

Fig. 10 is a view showing a demand planning perspective in an application example of the present application.

Fig. 11 is a schematic diagram of a first structure of a demand tracking matrix display system in an embodiment of the present application.

Fig. 12 is a schematic diagram of a second structure of the demand tracking matrix display system in the embodiment of the present application.

Fig. 13 is a schematic diagram of a third structure of the demand tracking matrix display system in the embodiment of the present application.

Fig. 14 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The demand tracking matrix has no specified implementation method, the aspects of each group are different, the created demand tracking matrix is also different, and the implementation mode of the demand tracking matrix with different visual angles is introduced from the perspectives of business requirement proposers, product managers, project managers and technology implementers.

Generally, a requirement tracking matrix starts from business requirements, and combines requirement items, business requirements, related projects, implementation departments, development tasks and development progress (analysis, design, development, application assembly, user inspection and version inspection) work items into the same report. The application provides a method for realizing a demand tracking matrix, which is used for showing the relationships of demand items, business requirements, affiliated projects, development tasks, development progress and the like at different visual angles from the viewpoints of product management, project management and implementation management, and simultaneously showing the completion degree state of the current demand, and better assisting a project manager in carrying out demand tracking and progress management.

The known technical content is as follows: (1) managing projects; (2) managing products; (3) implementing management; (4) a demand tracking matrix;

the requirement tracking matrix is used, the requirement state can be tracked, the requirement change control is carried out, the changes of requirement change, design change, code change, test cases and the like and the influence range of the change can be checked, and the important guidance function is realized in the whole project cycle. However, in the whole project cycle, the attention points of each team and each role are different, and the individual requirements of each team cannot be met by giving a uniform display result. Meanwhile, data at each stage in the full life cycle, such as demands, implementation progress and the like, are usually distributed on different platforms, and a comprehensive demand tracking matrix cannot be displayed on one platform.

In view of the above disadvantages, the present application provides a method for displaying a requirement tracking matrix, a system for displaying a requirement tracking matrix, an electronic device, and a computer-readable storage medium, by receiving a status query request for a target software development project, where the status query request includes a requester role identifier; selecting at least one piece of preset display visual angle information as target visual angle information according to the requester role identification; selecting a corresponding target demand tracking matrix from a plurality of demand tracking matrices corresponding to the target software development project based on the target visual angle information, wherein the demand tracking matrix is generated offline according to state data of the target software development project in each development stage in a preset software full life cycle collected offline and a corresponding data table model; and outputting the target demand tracking matrix to a preset visualization unit for displaying. According to the method and the device, the scattered data of each stage are collected in an off-line mode, the conditions that the demand items are used in the following development stages, namely development tasks, analysis number, design number, development number, component units, building and assembling, application and assembling, user testing and version checking, are displayed and counted in different view angles according to roles in the whole life cycle, and user experience is improved.

In one or more embodiments of the present application, the requirement tracking matrix refers to an effective tool for mainly managing requirement change and verifying whether a requirement is realized, and the state of each requirement can be tracked by the aid of the requirement tracking matrix.

In one or more embodiments of the present application, the service requirement refers to a requirement that a service party puts forward for its service.

In one or more embodiments of the present application, the requirement item refers to a product manager analyzing a business requirement, and further splitting an implementable product requirement item.

In one or more embodiments of the present application, the development task refers to a development behavior set performed to fulfill some requirements and realize some functions, one development task corresponds to one production of one project, for example, if one project is produced in multiple batches within a project period, multiple development tasks need to be created, and one development task can only belong to one project.

Referring to the full life cycle of software shown in fig. 1, it can be seen that a product manager analyzes a service requirement, divides the service requirement into a plurality of requirement items, evaluates the requirement by a design principal to display the design, creates a development task by the development principal, associates the related requirement items with the development task, distributes the development task to developers of corresponding modules to develop, tests by testers of the corresponding modules after the development is completed, and releases the product on line after the full tests. In general, 1 service requirement corresponds to N requirement items, 1 development task corresponds to N modules, 1 development task corresponds to N developers, and 1 development task corresponds to N testers.

The generation of the demand tracking matrix has the following difficulties:

(1) the related models are many, including project table project, project section table project _ depth _ info, requirement item table biz _ requirement _ item, development task table tasks _ depth, test plan table testplan, design workpiece table definition, development workpiece table definition _ operation, business section view table configuration _ parameter _ view, requirement item and business function analysis/user work function relation table query _ track _ rule _ relationship _ parameter _ analysis _ and _ specification _ view, The demand tracking matrix-test-function range req _ track _ matrix _ qc _ function _ scope, etc.

(2) Data is often not concentrated on one platform and needs to be collected from multiple platforms.

(3) Part of the display indexes need to be obtained through calculation, such as the number of required items, the completion proportion of each step (analysis, design, development, application assembly, user test and version inspection) in the implementation stage and the like.

In order to display all effective information of a full life cycle of software in a demand tracking matrix, meanwhile, due to the fact that different roles have different attention points in a project and the demand tracking matrices seen by different roles have differences, the real-time display of related tables is carried out in real time, and the speed cannot meet the demand, the application provides a demand tracking matrix display method. Specifically, the following examples are given to illustrate the respective embodiments.

In order to effectively improve the display comprehensiveness and reliability of the demand tracking matrix and display the demand tracking matrix with strong pertinence quickly and in real time, the application provides an embodiment of a demand tracking matrix display method, and referring to fig. 2, the demand tracking matrix display method specifically includes the following contents:

step 100: and receiving a state query request aiming at the target software development project, wherein the state query request comprises a requester role identifier.

Step 200: and selecting at least one piece of preset display visual angle information as target visual angle information according to the requester role identification.

It can be understood that the display perspective information may be pre-stored in a local or preset database of the demand tracking matrix display system, and each display perspective information is in a one-to-one correspondence relationship with each requestor role identifier.

Step 300: selecting a corresponding target demand tracking matrix from a plurality of demand tracking matrices corresponding to the target software development project based on the target visual angle information, wherein the demand tracking matrix is generated offline according to state data of each development stage of the target software development project in a preset software full life cycle collected offline and a corresponding data table model.

It can be understood that the plurality of requirement tracking matrices corresponding to the target software development project may be pre-stored in a local requirement tracking matrix display system or a preset database, and each requirement tracking matrix is in a one-to-one correspondence relationship with each display view angle information.

Step 400: and outputting the target demand tracking matrix to a preset visualization unit for displaying.

In step 400, the visualization unit refers to a device having a display function, such as a display screen or a touch screen.

In order to effectively improve the efficiency and reliability of selecting the target view angle information so as to further improve the display efficiency and reliability of the demand tracking matrix, in an embodiment of the demand tracking matrix display method provided by the present application, the requester role identifier includes: at least one of a business requirement presenter identification, a product manager identification, a project manager identification, and a technology implementer identification; referring to fig. 3, the step 200 of the demand tracking matrix display method specifically includes the following steps:

step 210: and selecting target visual angle information from the project visual angle information corresponding to the service requirement presenter, the service requirement visual angle information corresponding to the product manager, the requirement item visual angle information corresponding to the project manager and the requirement plan visual angle information corresponding to the technical implementer according to the requester role identifier, wherein the target visual angle information is the same as the requester role identifier in number.

In an embodiment of the demand tracking matrix display method of the present application, the plurality of demand tracking matrices corresponding to the target software development project include:

(1) and (5) a demand tracking matrix corresponding to the project view angle.

In step 200, if the target perspective information is project perspective information, selecting a demand tracking matrix corresponding to the project perspective from a plurality of demand tracking matrices corresponding to the target software development project as a target demand tracking matrix.

(2) And a requirement tracking matrix corresponding to the service requirement visual angle.

In step 200, if the target view information is service requirement view information, selecting a requirement tracking matrix corresponding to the service requirement view from a plurality of requirement tracking matrices corresponding to the target software development project as a target requirement tracking matrix.

(3) And a requirement tracking matrix corresponding to the requirement item visual angle.

In step 200, if the target perspective information is the perspective information of the requirement item, selecting a requirement tracking matrix corresponding to the perspective of the requirement item from a plurality of requirement tracking matrices corresponding to the target software development project as a target requirement tracking matrix.

(4) And a demand tracking matrix corresponding to the demand plan view.

In step 200, if the target view information is the requirement plan view information, selecting a requirement tracking matrix corresponding to the requirement plan view from a plurality of requirement tracking matrices corresponding to the target software development project as a target requirement tracking matrix.

In order to display a highly targeted demand tracking matrix quickly and in real time, in an embodiment of the demand tracking matrix display method provided by the present application, referring to fig. 4, before step 100 of the demand tracking matrix display method, the following contents are further included:

step 010: collecting state data of each development stage of the target software development project in a preset software full life cycle in an off-line manner, wherein the state data of each development stage comprises the following steps: developing task data, analyzing number data, designing number data, developing number data, component unit data, building and assembling data, application and assembling data, user testing data and version checking data.

Step 020: and acquiring a preset data table model, dimensionality, a construction functional module and construction logic data corresponding to each piece of display visual angle information.

Step 030: and generating a demand tracking matrix corresponding to each piece of display visual angle information in an off-line manner based on state data of each development stage of the target software development project in a preset software full life cycle, and a data table model, a dimension, a construction function module and a construction logic corresponding to each piece of display visual angle information.

Step 040: and storing the demand tracking matrix corresponding to each piece of display visual angle information as a plurality of demand tracking matrices corresponding to the target software development project.

In an embodiment of the demand tracking matrix display method of the present application, the data table model is used for storing a correspondence between data names, field types, and description contents; the data sheet model comprises a preset demand tracking matrix project visual angle model, a project visual angle and business department visual angle sub-sheet model, a business department visual angle model, a demand item visual angle model and a development task detail model.

And the requirement tracking matrix corresponding to the project visual angle is realized by adopting a preset requirement tracking matrix project visual angle model and/or the project visual angle and business department visual angle sub-table model. The requirement tracking matrix corresponding to the service requirement visual angle needs to be realized by adopting a project visual angle and service department visual angle sub-table model and/or a service department visual angle model. And the requirement tracking matrix corresponding to the requirement item visual angle needs to be realized by adopting a requirement item visual angle model. And the requirement tracking matrix corresponding to the requirement plan view angle needs to be realized by adopting a development task detail model.

In order to further improve the efficiency and accuracy of obtaining the development progress of the software product according to the display content of the demand tracking matrix and further improve the user experience, in an embodiment of the demand tracking matrix display method provided by the present application, referring to fig. 5, the following content is further specifically included after step 400 of the demand tracking matrix display method:

step 500: and if a keyword search request aiming at the target software development project is received, extracting keywords corresponding to the keyword search request.

Step 600: and searching and displaying data corresponding to the keywords in a target demand tracking matrix in the visualization unit.

To further illustrate the present solution, the present application further provides a specific application example of the method for displaying the demand tracking matrix, and referring to fig. 6, the demand tracking matrix is displayed from 4 different viewing angles in the application example of the present application, that is: a demand item view (see FIG. 7), a business requirement view (see FIG. 8), a project view (see FIG. 9), and a demand planning view (see FIG. 10)

The design of the key data model in the application example comprises the following steps:

(1) the demand tracking matrix project view model (req _ track _ matrix _ project _ view), see table 1.

TABLE 1

Name (R)	Type of field	Description of the invention
			prj_id	varchar	Item numbering
prj_name	varchar	Name of item
			prj_type	varchar	Item type
prj_status	varchar	Item status
			implement_department_id	varchar	Enforcement of department numbering
implement_department_name	varchar	Name of implementation department
			business_req_item_number	int	Project scope/requirements item
l3av_number	int	Project scope/level three tasks
			c4tk_number	int	Project scoping/level four tasks
deleted	boolean	Delete mark

In table 1, each record in table 1 is obtained by joint query of the item table (project), the item department table (project _ depth _ info), and the requirement item table (biz _ requirement _ item).

(2) The project view sub-table model (req _ track _ matrix _ project _ sub _ view), see table 2.

TABLE 2

Name (R)	Type of field	Description of the invention
			view_id	int	Master table ID
view_type	varchar	Type of angle of view
			task_id	varchar	Development task
task_name	varchar	Development task name
			version_date	varchar	Time of line-up
prj_name	varchar	Name of item
			business_req_item_sub_number	int	Number of demand items
analysis_number	int	Implementation/analysis
			design_number	int	Implementation/design
develop_number	int	Implementation/development
			component_unit_covered_number	int	Number of unit cell covered
component_unit_covered_total	int	Embodiment/assembly unit
			component_group_covered_number	int	Number of assembly covers
component_group_covered_total	int	Implementation/assembly of components
			application_group_number	int	Implementation/application assembly
user_test_number	int	Implementation/user testing
			version_test_number	int	Implementation/version checking
task_progress	char	Task progress
			deleted	boolean	Delete mark

In table 2, the project view/business section view data is obtained by querying a design artifact table (design), a development artifact table (level operation), a business section view table (business _ destination _ view), a requirement item table (biz _ requirement _ item), a development task table (tasks _ level), a project table (project), a test plan table (testplan), a requirement item and business function analysis/user workflow relationship table (req _ track _ matrix _ and _ ywgnfx _ relation), and a requirement tracking matrix/test/function scope (req _ track _ matrix _ qc _ function _ scope).

(3) Business _ department _ view model, see table 3.

TABLE 3

Name (R)	Type of field	Description of the invention
			business_request_id	varchar	Service requirement numbering
business_request_name	varchar	Business requirement name
			propose_department_id	varchar	Propose department number
propose_department_name	varchar	Put forward the name of the department
			propose_date	date	Date of filing
business_req_item_number	int	Business/requirements item
			l3avy_number	int	Business/tertiary activity
l4tk_number	int	Business/level fourTask
			deleted	boolean	Delete mark

In table 3, the records in table 3 are obtained by querying the business requirement table (biz _ request) and the requirement item table (biz _ request _ item) jointly.

(4) The view model of the demand item (business _ req _ item _ view), see table 4.

TABLE 4

(5) A task detail model (tasks _ info) was developed, see table 5.

TABLE 5

Name (R)	Type of field	Description of the invention
			task	int	Development task
begin_date	date	Scheduled start time
			end_date	date	Scheduled end time
finish_begin_date	date	Actual start time
			finish_end_date	date	Actual end time
stage	varchar	At the stage of
			analysis_begin_date	date	Analyzing planned start times
analysis_end_date	date	Analyzing planned end times
			analysis_finish_begin_date	date	Analyzing actual start time
analysis_finish_end_date	date	Analyzing actual end time
			design_begin_date	date	Design plan start time
design_end_date	date	Design plan end time
			design_finish_begin_date	date	Designing an actual start time
design_finish_end_date	date	Design of actual end time
			develop_begin_date	date	Development plan start time
develop_end_date	date	Development plan end time
			develop_finish_begin_date	date	Developing the actual start time
develop_finish_end_date	date	Actual end time of development
			test_begin_date	date	Test plan start time
test_end_date	date	Test plan end time
			test_finish_begin_date	date	Testing actual start time
test_finish_end_date	date	Test actual end time
			version_date	date	Scheduled online time
finish_version_date	date	Actual time of line

(II) implementation of demand tracking matrix

1. Demand item view angle of demand tracking matrix

1-1. dimension

The visual angle takes the requirement item as a dimension to find which development task the requirement item belongs to, and counts the conditions of the requirement item in the following development stages, namely development task, analysis number, design number, development number, component unit, assembly and assembly, application and assembly, user test and version inspection.

1-2. modules involved in the perspective of a requirement

(1) A management service requirement module: the IT management platform responsible for the management of the requirement items provides the service requirement item information, namely the number, the third-level activity and the fourth-level task, and hyperlinks are used for viewing the requirement item information of each data.

(2) A project module: project information (project) is provided by an IT management platform responsible for project management.

(3) A development task implementation module: development task information provided by an IT management platform responsible for implementing the management. And finding the development task to which the demand item belongs according to the demand item, and checking the information of the development task through the hyperlink.

(4) Analyzing the workpiece module: a service function information table (ywgnfx) provided by a VBA managed by demand, and a user workflow table (yhlc).

(5) Designing a workpiece module: design workpiece information table (design) provided by the implementation process.

(6) Developing a workpiece module: development work information table (developmentation) provided by the implementation process.

(7) A test module: a service function information table/user workflow information table (req _ track _ matrix _ relative _ req _ item) provided by the resource data platform.

1-3 interface design, see table 6.

TABLE 6

1-4. design points

1-4-1. data sheet design:

(1) main table (business _ req _ item _ view): requirement item, development task, test, etc.

(2) And the requirement item information table (biz _ requirement _ item) is provided by the IT management platform.

(3) Development task information table (tasks _ develoop): provided by the IT management platform.

(4) Project information table (project): provided by the IT management platform.

(5) Design artifact table (design): provided by the set of implementation process items.

(6) Development of a workpiece table (development): provided by the set of implementation process items.

(7) Test data table (req _ track _ matrix _ qc _ function _ scope): provided by a resource data platform.

1-4-2. logic design:

in the embodiment of the application, in order to provide a demand tracking matrix with the demand items as dimensions, the data to be displayed is assembled by taking the demand items as primary keys according to the incidence relation among tables.

(1) The data in the requirement item information table (biz _ requirement _ item) is processed cyclically piece by piece.

(2) And obtaining a corresponding development task number (task _ id) according to the service requirement item number (bsn _ rqm _ itm _ id).

(3) And obtaining project information corresponding to the development task according to the association between the development task number (task _ id) and the development task table (task _ devildop).

(4) And associating the demand item number (bsn-rqm _ itm _ id) in the demand item information table (biz _ requirement _ item) with the service function table (ywgnfx) and the user workflow information table (yhlc) to obtain analysis information and storing the analysis information into the relation table (req _ track _ matrix _ and _ ywgnfx _ relation).

(5) And obtaining the design information id in the design workpiece table according to the association of the business function analysis table (ywgnfx) id, the user flow (yhlc) id and the design workpiece table (design).

(6) And obtaining the development workpiece information according to the association of the design information id and the development workpiece table (development).

(7) And obtaining test information according to the association of the service function id and the user flow and the test information table (req _ track _ matrix _ relative _ req _ item).

2. Business requirement view angle of demand tracking matrix

2-1. dimension

The visual angle takes the service requirement as a dimension, counts the number of the demand items hung below the service requirement, and counts the conditions of the demand items used in the following development stages, namely development tasks, analysis number, design number, development number, component units, assembly and assembly, application assembly, user test and version inspection.

2-2. modules involved in project views

(1) A management service requirement module: the IT management platform responsible for the business requirement management provides the business requirement information, namely the number, the third-level activity and the fourth-level task, and the requirement item information of each data is checked through the hyperlink.

(2) A development task implementation module: the IT management platform responsible for implementing management is used for counting development tasks under a service requirement according to the service requirement information and checking the information of the development tasks through hyperlinks.

(3) Analyzing the workpiece module: the system comprises a service function information table (ywgnfx) and a user workflow information table (yhlc), wherein the two information sources are provided by a VBA (visual basic architecture) of demand control.

(4) Designing a workpiece module: design workpiece information table (design) provided by the implementation process.

(5) Developing a workpiece module: development work information table (developmentation) provided by the implementation process.

(6) A test module: a service function information table/user workflow information table (req _ track _ matrix _ relative _ req _ item) provided by the resource data platform.

2-3. interface design, see table 7.

TABLE 7

2-4. design points

2-4-1. data design:

(1) main table (business _ priority _ view): service requirement information and project information.

(2) Sub table (req _ track _ matrix _ project _ sub _ view): and taking development tasks as dimensions, wherein one development task is data, and the main table id is a main foreign key.

(3) Design artifact table (design): provided by the set of implementation process items.

(4) Development of a workpiece table (development): provided by the set of implementation process items.

(5) Requirement item relationship information table (req _ track _ matrix _ relative _ req _ item): the relation between the requirement item and the service requirement, and the processed information required by the module, wherein the id of the req _ track _ matrix _ project _ sub _ view is a main foreign key.

(6) Test data table (req _ track _ matrix _ qc _ function _ scope): provided by a resource data platform.

2-4-2. logic design:

in the embodiment of the application, in order to provide a demand tracking matrix with a dimension according to a project, data to be displayed is assembled by taking a service requirement as a main key and according to an incidence relation between tables.

(1) And circularly processing the service requirement information (biz _ requirement) to obtain the requirement item information (bsn _ rqm _ itm _ id) below the service requirement.

(2) And obtaining development task information according to the service demand item number (bsn-rqm-itm _ id).

(3) Analyzing the original data of the business function table (ywgnfx) and the user workflow information table (yhlc), extracting the requirement item number bsn-rqm _ itm _ id of each record, and storing the corresponding relation between the requirement item number and the business function analysis and the corresponding relation between the requirement item number and the user workflow information into a relation table (req _ track _ matrix _ and _ ywgnfx _ relationship).

(4) And obtaining design workpiece information according to the correlation between the service function id and the user process id and a design workpiece table (design).

(5) And obtaining development workpiece information according to the association of the design id and a development workpiece table (development).

(6) And obtaining test information according to the correlation between the service function id and the user process id and the test information table (req _ track _ matrix _ relative _ req _ item).

3. Project view of demand tracking matrix

3-1. dimension

The view takes the item as the dimension, counts the number of the demand items hung below the item,

statistics is carried out on the conditions that the demand items are used in the following development stages, namely development tasks, analysis number, design number, development number, component units, assembly and assembly, application assembly, user test and version inspection.

3-2. modules involved in project perspective

(1) The project management module: project information provided by an IT management platform responsible for project management.

(2) A management service requirement module: service requirement information provided by an IT management platform in charge of service requirement management.

(3) A development task implementation module: development task information provided by an IT management platform responsible for implementing the management. And counting development tasks under a project according to the project information, and checking detailed development tasks through hyperlinks.

(4) Analyzing the workpiece module: service function information (ywgnfx) and user workflow information (yhlc) provided by the VBA of demand management.

(5) Designing a workpiece module: a design workpiece table (design) is provided by the implementation process.

(6) Developing a workpiece module: the implementation process provides a development work table (development).

(7) A test module: business function information/user workflow information (req _ track _ matrix _ relative _ req _ item) provided by the resource management platform.

3-3. interface design, see table 8.

TABLE 8

3-4. design points

3-4-1. data sheet design:

(1) demand tracking matrix item view master table (req _ track _ matrix _ project _ view): project information and service requirement item information.

(2) Requirement tracking matrix entry view sub-table (req _ track _ matrix _ project _ sub _ view): and taking development tasks as dimensions, wherein one development task is data, and the main table id is a main foreign key.

(3) The section relationship table (req _ track _ matrix _ impt _ depth _ relationship): the id of the real department relationship table for each item, req _ track _ matrix _ project _ view table, is the primary foreign key.

(4) Design artifact table (design): a design workpiece table is provided by the implementation process.

(5) Development of a workpiece table (development): the development work piece table is provided by the implementation process.

(6) Requirement item relationship information table (reg _ track _ matrix _ relative _ req _ item): the relation between the requirement item and the item, and the processed information required by the module, the id of req _ track _ matrix _ project _ sub _ view is the main foreign key.

(7) Test data (req _ track _ matrix _ qc _ function _ scope): data provided by the data management platform.

(8) Requirement item and service function, user flow relation table (req _ track _ matrix _ and _ ywgnfx _ relation): and storing the business function and user flow relation of the requirement item and the analysis stage.

3-4-2. logic design:

in the embodiment of the application, in order to provide a demand tracking matrix with items as dimensions, the items are used as primary keys, and data to be displayed is assembled according to the incidence relation among tables.

(1) And circularly processing the project information (project).

(2) And obtaining development task information according to the association of the project number code and the development task table (tasks _ develoop).

(3) And obtaining the implementation department information according to the association of the project number code and the project department relation table (project _ depth _ info).

(4) And associating the project number code with a project requirement item relation table (biz _ requirement _ item) to obtain requirement item information, three-level activity and four-level task information.

(5) Analyzing the original data of the business function table (ywgnfx) and the user workflow information table (yhlc), extracting the requirement item number bsn-rqm _ itm _ id of each record, and storing the corresponding relation between the requirement item number and the business function analysis and the corresponding relation between the requirement item number and the user workflow information into a relation table (req _ track _ matrix _ and _ ywgnfx _ relationship).

(6) And associating the service function table (ywgnfx) id and the user flow table (yhlc) id with a function design analysis field of a design workpiece table (design) to obtain design workpiece information.

(7) And obtaining development workpiece information according to the association of the design id and a development workpiece table (development).

(8) And the service function table (ywgnfx) id and the user flow table (yhlc) id are associated with the test information table (req _ track _ matrix _ relative _ req _ item) to obtain test information.

4. Demand plan view of demand tracking matrix

4-1. dimension

The view takes the requirement item as a dimension, searches which development task the requirement item belongs to, and displays data of each stage of the test plan in the development task.

4-2. modules involved in demand planning perspective

(2) The project management module: project information is provided by an IT management platform responsible for project management.

(3) A development task implementation module: and finding the development task according to the requirement item information, and finding the information of each stage of the test plan according to the development task id.

4-3. interface design, see table 9.

TABLE 9

4-4. design points

4-4-1. data sheet design:

(1) main table (business _ reg _ item _ view) -information such as requirement item, development task, test, etc.

(2) Development task stage detail (tasks _ info) — run batch (uliwebcluppdate _ tasks _ status) obtains time information of each stage of the development task.

4-4-2. logic design:

in the embodiment of the application, in order to provide a demand tracking matrix with the project as the dimension, the development task plan item is used as a main key, and data to be displayed is assembled according to the incidence relation among tables.

(1) The requirement item information (business _ req _ item _ view) is processed cyclically one by one.

(3) And obtaining the online time information of each stage of the development task according to the association between the development task id and the development task stage detail (tasks _ info).

From the above description, the demand tracking matrix display method provided by the application example of the present application shows the demand processing state from four angles, i.e., a project angle, a demand item angle, a business requirement angle, and a demand plan angle. And collecting scattered data of each stage in an off-line manner, and displaying and counting the conditions of the required items used in the following development stages, namely development tasks, analysis number, design number, development number, component units, construction and assembly, application and assembly, user test and version inspection according to the roles in the full life cycle in different view angles. And inquiring according to the business requirements, the requirement items, the current stage, the development team and other keywords, still inquiring on the result page, and displaying the filtered content. The application example of the application can display and count the use conditions of the demand items in the following development stages according to the roles in the whole life cycle in different visual angles; the data of all stages of the whole process of different software development are collected in an off-line mode, and the display content is very comprehensive.

In terms of software, in order to effectively improve the display comprehensiveness and reliability of the demand tracking matrix and to be able to quickly and real-timely display the demand tracking matrix with strong pertinence, the present application further provides an embodiment of a demand tracking matrix display system for implementing all or part of the content in the demand tracking matrix display method, and referring to fig. 11, the demand tracking matrix display system specifically includes the following contents:

the first request receiving subsystem 10 is configured to receive a status query request for a target software development project, where the status query request includes a requester role identifier.

And the target visual angle determining subsystem 20 is configured to select at least one of the preset plurality of pieces of display visual angle information as target visual angle information according to the requester role identifier.

And a target demand tracking matrix selecting subsystem 30, configured to select a corresponding target demand tracking matrix from multiple demand tracking matrices corresponding to the target software development project based on the target perspective information, where the demand tracking matrix is generated offline according to state data of the target software development project collected offline in each development stage within a preset software full life cycle and a corresponding data table model.

And the target demand tracking matrix display subsystem 40 is used for outputting the target demand tracking matrix to a preset visualization unit for display.

From the above description, it can be seen that the requirement tracking matrix display system provided by the embodiment of the present application can display and count the situations that the requirement items are used in each development stage according to roles in the whole life cycle and different viewing angles, thereby effectively improving the display comprehensiveness and the reliability of the demand tracking matrix, collecting the state data of the software development project in each development stage of different platforms in advance in an off-line manner, and generating all demand tracking matrixes corresponding to the software development project in advance and off-line based on the state data, further, when a state inquiry request is received, the corresponding demand tracking matrix can be displayed rapidly and in real time, the displayed content is very comprehensive, so that the user experience can be effectively improved, and the efficiency and the accuracy of acquiring the development progress of the software product according to the display content of the demand tracking matrix are effectively improved.

In order to effectively improve the efficiency and reliability of selecting the target view angle information, so as to further improve the display efficiency and reliability of the demand tracking matrix, in an embodiment of the demand tracking matrix display system provided by the present application, the requester role identifier includes: at least one of a business requirement presenter identification, a product manager identification, a project manager identification, and a technology implementer identification; the target view determination subsystem of the demand tracking matrix display system is specifically configured to perform the following:

In an embodiment of the demand tracking matrix display system of the present application, the plurality of demand tracking matrices corresponding to the target software development project include:

In order to display a highly targeted demand tracking matrix quickly and in real time, in an embodiment of the demand tracking matrix display system provided in the present application, referring to fig. 12, the demand tracking matrix display system further includes the following contents:

the offline data collecting subsystem 01 is configured to collect, offline, state data of each development stage of the target software development project in a preset software full life cycle, where the state data of each development stage includes: developing task data, analyzing number data, designing number data, developing number data, component unit data, building and assembling data, application and assembling data, user testing data and version checking data.

And the generation parameter acquisition subsystem 02 is used for acquiring a preset data table model, dimensionality, a construction functional module and construction logic data which respectively correspond to each piece of display visual angle information.

The matrix offline generation subsystem 03 is configured to generate, offline, a demand tracking matrix corresponding to each piece of display view information based on state data of the target software development project at each development stage in a preset software full life cycle, and a data table model, a dimension, a construction function module and a construction logic corresponding to each piece of display view information.

And the matrix storage subsystem 04 is configured to store the demand tracking matrices corresponding to the display perspective information as a plurality of demand tracking matrices corresponding to the target software development project.

In one embodiment of the demand tracking matrix display system of the present application, the data table model is used to store correspondences between data names, field types, and description contents; the data sheet model comprises a preset demand tracking matrix project visual angle model, a project visual angle and business department visual angle sub-sheet model, a business department visual angle model, a demand item visual angle model and a development task detail model.

In order to further improve the efficiency and accuracy of obtaining the development progress of the software product according to the display content of the demand tracking matrix and further improve the user experience, in an embodiment of the demand tracking matrix display system provided by the present application, referring to fig. 13, the demand tracking matrix display system further specifically includes the following contents:

and a second request receiving subsystem 50, configured to, if a keyword search request for the target software development project is received, extract a keyword corresponding to the keyword search request.

And the filtering display subsystem 60 is configured to search and display data corresponding to the keyword in the target demand tracking matrix in the visualization unit.

In order to effectively improve the display comprehensiveness and reliability of the demand tracking matrix and display the demand tracking matrix with strong pertinence in real time from a hardware level, the present application provides an embodiment of an electronic device for implementing all or part of the contents in the demand tracking matrix display method, where the electronic device specifically includes the following contents:

a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the communication interface is used for realizing information transmission between the electronic equipment and the user terminal and relevant equipment such as a relevant database and the like; the electronic device may be a desktop computer, a tablet computer, a mobile terminal, and the like, but the embodiment is not limited thereto. In this embodiment, the electronic device may refer to the embodiment of the requirement tracking matrix display method in the embodiment and the embodiment of the requirement tracking matrix display system, which are incorporated herein, and repeated details are not repeated.

Fig. 14 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 14, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this FIG. 14 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one embodiment, the demand tracking matrix display function may be integrated into a central processor. Wherein the central processor may be configured to control:

As can be seen from the above description, the electronic device provided in the embodiment of the present application can display and count the usage of the requirement items in each development phase according to the roles in the full life cycle at different viewing angles, so as to effectively improve the display comprehensiveness and reliability of the requirement tracking matrix, collect the state data of the software development project in each development phase of each different platform in an offline manner in advance, generate all the requirement tracking matrices corresponding to the software development project in an offline manner in advance based on the state data, and further quickly display the corresponding requirement tracking matrix in real time when receiving a status query request, so that the displayed content is very comprehensive, thereby effectively improving the user experience, and effectively improving the efficiency and accuracy of learning the development progress of the software product according to the display content of the requirement tracking matrix.

In another embodiment, the demand tracking matrix display system may be configured separately from the central processor 9100, for example, the demand tracking matrix display system may be configured as a chip connected to the central processor 9100, and the demand tracking matrix display function may be implemented by the control of the central processor.

As shown in fig. 14, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 14; further, the electronic device 9600 may further include components not shown in fig. 14, which can be referred to in the related art.

As shown in fig. 14, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

An input unit 9120 provides input to the cpu 9100, the input unit 9120 is, for example, a key or a touch input device, a power supply 9170 supplies power to the electronic apparatus 9600, a display 9160 displays display objects such as images and characters, and the display may be, for example, an L CD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

An embodiment of the present application further provides a computer-readable storage medium capable of implementing all the steps in the requirement tracking matrix display method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements all the steps of the requirement tracking matrix display method in which an execution subject is a server or a client, for example, when the processor executes the computer program, the processor implements the following steps:

From the above description, it can be seen that the computer-readable storage medium provided in the embodiments of the present application can show statistics of the situations where these requirement items are used in various development stages according to roles in the whole life cycle and different viewing angles, thereby effectively improving the display comprehensiveness and the reliability of the demand tracking matrix, collecting the state data of the software development project in each development stage of different platforms in advance in an off-line manner, and generating all demand tracking matrixes corresponding to the software development project in advance and off-line based on the state data, further, when a state inquiry request is received, the corresponding demand tracking matrix can be displayed rapidly and in real time, the displayed content is very comprehensive, so that the user experience can be effectively improved, and the efficiency and the accuracy of acquiring the development progress of the software product according to the display content of the demand tracking matrix are effectively improved.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. 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 means for implementing 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 instruction means which implement 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 principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A method for demand tracking matrix display, comprising:

2. The demand tracking matrix display method of claim 1, wherein the requester role identification comprises: at least one of a business requirement presenter identification, a product manager identification, a project manager identification, and a technology implementer identification;

3. The method of claim 2, wherein the plurality of requirement tracking matrices for the target software development project comprises:

4. The demand tracking matrix display method of claim 3, further comprising, prior to the receiving a status query request for a target software development project:

5. The demand tracking matrix display method of claim 4, wherein the data table model is used to store the correspondence between data names, field types and description contents;

6. The demand tracking matrix display method according to claim 1, further comprising, after outputting the target demand tracking matrix to a preset visualization unit for display:

7. A demand tracking matrix display system, comprising:

8. The demand tracking matrix display system of claim 7, wherein the requester role identification comprises: at least one of a business requirement presenter identification, a product manager identification, a project manager identification, and a technology implementer identification;

9. The demand tracking matrix display system of claim 8, wherein the plurality of demand tracking matrices for the target software development project comprises:

10. The demand tracking matrix display system of claim 9, further comprising:

11. The demand tracking matrix display system of claim 10, wherein the data table model is configured to store correspondences between data names, field types, and descriptive content;

12. The demand tracking matrix display system of claim 7, further comprising:

13. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program performs the steps of the demand tracking matrix display method of any of claims 1 to 6.

14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the demand tracking matrix display method of any one of claims 1 to 6.