CN113835960A - Method and device for monitoring and marking research and development state of aerospace measurement and control software - Google Patents
Method and device for monitoring and marking research and development state of aerospace measurement and control software Download PDFInfo
- Publication number
- CN113835960A CN113835960A CN202111114050.9A CN202111114050A CN113835960A CN 113835960 A CN113835960 A CN 113835960A CN 202111114050 A CN202111114050 A CN 202111114050A CN 113835960 A CN113835960 A CN 113835960A
- Authority
- CN
- China
- Prior art keywords
- development
- determining
- work item
- software
- work
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 93
- 238000012544 monitoring process Methods 0.000 title claims abstract description 77
- 238000005259 measurement Methods 0.000 title claims abstract description 62
- 238000012827 research and development Methods 0.000 title claims abstract description 56
- 238000011161 development Methods 0.000 claims description 54
- 230000006870 function Effects 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 15
- 238000013507 mapping Methods 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 11
- 238000012806 monitoring device Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 abstract description 48
- 230000018109 developmental process Effects 0.000 description 126
- 238000007726 management method Methods 0.000 description 25
- 238000013461 design Methods 0.000 description 24
- 238000012360 testing method Methods 0.000 description 21
- 238000010586 diagram Methods 0.000 description 17
- 238000004891 communication Methods 0.000 description 15
- 238000005516 engineering process Methods 0.000 description 13
- 239000011159 matrix material Substances 0.000 description 13
- 238000012545 processing Methods 0.000 description 12
- 230000009471 action Effects 0.000 description 10
- 230000008859 change Effects 0.000 description 9
- 238000004458 analytical method Methods 0.000 description 6
- 230000002457 bidirectional effect Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000007704 transition Effects 0.000 description 5
- 239000000872 buffer Substances 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 239000000047 product Substances 0.000 description 3
- 238000009826 distribution Methods 0.000 description 2
- 230000004927 fusion Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000000280 densification Methods 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for monitoring and marking the research and development state of aerospace measurement and control software, wherein the method comprises the following steps: determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software; determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items; and generating a monitoring marking form of the software development state according to the link mode. According to the method and the device, the integrated tracking and feedback can be carried out on the research and development process of the space measurement and control software according to the research and development data of each stage of the space measurement and control software.
Description
Technical Field
The application relates to the field of aerospace, in particular to a method and a device for monitoring and marking the research and development state of aerospace measurement and control software.
Background
The space flight measurement and control software generally comprises hundreds of professional processes such as real-time data processing, control and calculation, data storage, monitoring and display and the like, and the scale of the software is often up to the million-row magnitude. According to the organization characteristics of the aerospace engineering, the development of aerospace measurement and control software is close to the engineering terminal, and the development period is only a few months from the acquisition of task requirements to the meeting of task implementation conditions. In the meantime, since the time required for providing spacecraft parameters and processing by the industrial department is relatively late, the development process of the space measurement and control software faces frequent demand changes. Along with the trend of complexity and densification of the space mission, the scale and the complexity of space measurement and control task software are exponentially increased, the development period is greatly compressed, and higher requirements are provided for the development progress and the quality of the software. How to comprehensively collect software research and development states, realize that the whole process from development to delivery effectively tracks from technology to management, from system to configuration item, and has important significance for improving software research and development efficiency, improving software product quality and ensuring task success.
The purpose of software development state tracking is to establish and maintain consistency between "demand-design-code-test-delivery" to ensure that the final software product meets the demand. The software development state tracking runs through the whole software life cycle from the generation of software to the scrapping, the forward and reverse tracking is carried out, a complete closed loop is formed, and the changed influence domain can be judged quickly and accurately no matter which link is changed.
For how to track the software development state, the industry has two modes at present, the first mode is realized by compiling a bidirectional tracking table in a software engineering process document, the mode is separated from the practice of the actual software engineering process, the workload of manual compiling is huge, the state change cannot rapidly judge the influence domain, and the reusability is poor; the second is to establish a demand tracking matrix in demand management, and establish and maintain consistency between demand-design-coding-test in a table form. Although the tracking relation established in the way is more accurate, the working state of each stage of software development is not considered, and a complete closed loop is difficult to form for software change caused by requirements and problems; and the tracking relation between the software requirement and the software product is not considered, the whole software life cycle is not covered, and the establishment and maintenance cost of the table is huge.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides a software research and development state monitoring method and device, which can integrally track and feed back the research and development process of aerospace measurement and control software according to research and development data of each stage of the aerospace measurement and control software.
In order to solve the technical problem, the application provides the following technical scheme:
in a first aspect, the present application provides a software development state monitoring method, including:
determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items;
and generating a monitoring marking form of the software development state according to the link mode.
Furthermore, the research and development data of the space measurement and control software includes research and development function description, research and development time, research and development state and research and development relationship, the attributes include work item type, work item time, work item state and work item relationship, the work items to be monitored and the attributes corresponding to the work items are determined according to the research and development data of each stage of the space measurement and control software, and the method includes the following steps:
determining the type of the work item according to the development function description;
determining the work item time according to the research and development time;
determining the work item state according to the research and development state;
and determining the relation of the work items according to the research and development relation.
Further, the determining the link mode between the work items according to the preset link relationship between the work items and the attributes corresponding to the work items includes:
determining the current state of each work item according to the attribute corresponding to the work item;
and determining the link mode among the work items according to the link relation and the current state.
Further, the generating of the monitoring mark form of the software development state according to the link manner includes:
generating a header of the monitoring mark form according to each work item;
establishing a mapping relation between the work items according to the link mode between the work items;
and obtaining the monitoring mark form according to the form header and the mapping relation.
In a second aspect, the present application provides a software development status monitoring apparatus, including:
the system comprises a work item and attribute determining unit, a task item and attribute determining unit and a monitoring unit, wherein the work item and attribute determining unit is used for determining a work item to be monitored and an attribute corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
the link mode determining unit is used for determining the link mode among the work items according to the preset link relation among the work items and the attributes corresponding to the work items;
and the monitoring form determining unit is used for generating a monitoring marking form of the software development state according to the link mode.
Further, the space flight measurement and control software development data includes development function description, development time, development state and development relation, the attributes include work item type, work item time, work item state and work item relation, the work item and attribute determining unit includes:
the type determining module is used for determining the type of the work item according to the development function description;
the time determining module is used for determining the time of the work items according to the research and development time;
the state determining module is used for determining the state of the work item according to the research and development state;
and the relation determining module is used for determining the relation of the work items according to the research and development relation.
Further, the link mode determining unit includes:
the current state determining module is used for determining the current state of each work item according to the attribute corresponding to the work item;
and the link mode determining module is used for determining the link mode among the work items according to the link relation and the current state.
Further, the monitoring form determination unit includes:
the header generation module is used for generating a header of the monitoring mark form according to each work item;
the mapping relation generating module is used for establishing the mapping relation among the work items according to the link mode among the work items;
and the monitoring form determining module is used for obtaining the monitoring mark form according to the form header and the mapping relation.
In a third aspect, the present application provides an electronic device including 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 software development status monitoring 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 software development status monitoring method.
Aiming at the problems in the prior art, the software development state monitoring method and the software development state monitoring device provided by the application can realize the comprehensive collection and entry management of various data in the whole life cycle of the aerospace measurement and control software by defining different types of work items and configuring description fields with various attributes and surrounding a software development engineering process line and a software product line; by defining a typical link relation in the development process of the aerospace measurement and control software, the bidirectional tracking of work items in each stage of the development process of the aerospace measurement and control software is realized, and the change influence domain is quickly and accurately judged; by establishing a work item state conversion matrix and realizing software development state feedback from bottom to top through a work item state linkage method, the consistency and the integrity between software products from user requirements are quickly detected and verified, and the transparent management of the whole process from the requirements to the delivery of the software is realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a software development status monitoring method in an embodiment of the present application;
FIG. 2 is a flow chart of work item and attribute determination in an embodiment of the present application;
FIG. 3 is a flow chart of link mode determination in an embodiment of the present application;
FIG. 4 is a flow chart of monitoring form determination in an embodiment of the present application;
fig. 5 is a structural diagram of a software development state monitoring apparatus in an embodiment of the present application;
FIG. 6 is a block diagram of a workitem and attribute determination unit in an embodiment of the present application;
fig. 7 is a structural diagram of a link mode determining unit in the embodiment of the present application;
fig. 8 is a structural diagram of a monitoring form determination unit in the embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device in an embodiment of the present application;
FIG. 10 is a schematic view of a development workflow of aerospace measurement and control software in an embodiment of the present application;
FIG. 11 is a schematic diagram illustrating a mode of linking work items in a development process of space measurement and control software in an embodiment of the present application;
FIG. 12 is a diagram illustrating a state tracking matrix for software design work items according to an embodiment of the present application;
fig. 13 is a schematic diagram illustrating linkage of states between work items according to an embodiment of the present application.
Detailed Description
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 only a part of the embodiments of the present application, and not all of the 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.
In an embodiment, referring to fig. 1, in order to integrally track and feed back a development process of space measurement and control software according to development data of each stage of the space measurement and control software, the application provides a software development state monitoring method, which includes:
s101: determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
s102: determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items;
s103: and generating a monitoring marking form of the software development state according to the link mode.
It can be understood that in order to realize the tracking and management of the whole life cycle of software development, the requirement, the progress and the quality of software development are comprehensively tracked, the transparency of the software development process is realized, and the whole process transparent monitoring is carried out on the software development and management by the content item management of each stage of the software development, the multi-angle tracking of the software development process and the self-feedback technology of the software development state around the whole process of the aerospace flight control software development.
Specifically, the work items to be monitored and the attributes corresponding to the work items can be determined according to the research and development data of each stage of the aerospace measurement and control software. Different link modes exist among the work items, for example, the work item a is verified by the work item B, the work item C is realized by the work item D, and the like, if the work items are to be monitored in order, the link modes among the work items need to be described clearly, and finally, a monitoring mark form of the software development state is generated according to the link modes, as shown in fig. 12, and the specific implementation thereof can be referred to the following detailed description.
From the above description, the software development state monitoring method provided by the application can realize comprehensive collection and entry management of various data in the whole life cycle of the aerospace measurement and control software by defining different types of work items and configuring description fields with various attributes around a software development engineering process line and a software product line; by defining a typical link relation in the development process of the aerospace measurement and control software, the bidirectional tracking of work items in each stage of the development process of the aerospace measurement and control software is realized, and the change influence domain is quickly and accurately judged; by establishing a work item state conversion matrix and realizing software development state feedback from bottom to top through a work item state linkage method, the consistency and the integrity between software products from user requirements are quickly detected and verified, and the transparent management of the whole process from the requirements to the delivery of the software is realized.
In an embodiment, referring to fig. 2, the research and development data of the aerospace measurement and control software includes research and development function description, research and development time, research and development state, and research and development relationship, the attributes include work item type, work item time, work item state, and work item relationship, and the determining, according to the research and development data of each stage of the aerospace measurement and control software, a work item to be monitored and attributes corresponding to the work item includes:
s201: determining the type of the work item according to the development function description;
s202: determining the work item time according to the research and development time;
s203: determining the work item state according to the research and development state;
s204: and determining the relation of the work items according to the research and development relation.
In one embodiment, the software development process may be described using a software lifecycle model, which generally includes a requirements analysis phase, a design phase, an encoding phase, a testing phase, an operation and maintenance phase, and the like. Different types of software development processes tend to be a cut or a combination of multiple classical software lifecycle models. By analyzing different software life cycle models and combining the research and development characteristics of the space measurement and control software, the section provides a research and development working process of the space measurement and control software, and the research and development working process is shown in figure 10.
According to different work contents and different completed roles, the research and development working process of the aerospace measurement and control software can be divided into five stages: the first stage is a system design stage which mainly works to acquire the distribution requirement of the space measurement and control software according to the requirement of ground system development tasks, develop system design and form a design scheme of the space measurement and control software system; the second stage is a requirement analysis stage, which mainly serves to decompose according to configuration items according to a design scheme of the aerospace measurement and control software system to form software requirements of each configuration item, wherein the two stages correspond to a requirement analysis stage and a design stage in a software life cycle model; the third stage is a coding development stage, a software developer completes coding development and three-stage testing (software coding and unit testing, component integration and testing, configuration item integration and testing) according to software requirements, and the stage corresponds to a coding stage in a software life cycle model; the fourth stage is a system testing stage which is mainly completed by software testers and corresponds to a testing stage in the software life cycle model; and the fifth stage is a warehousing release stage, wherein the configuration management personnel manage the software product receiving and configuration library, release the compiled software product on line, wait for project acceptance check, and enter an operation and maintenance stage after the project acceptance check is passed. Frequent requirement change is a common characteristic of current aerospace measurement and control software research and development, and for later state acquisition requirements, the five stages can be circulated at any time. By setting different types of work items, the entry management of the progress states of 5 working stages of aerospace measurement and control software research and development can be realized.
Definition 1 (work item) a work item represents a certain problem to be handled in the software development process or a work element to be completed, and is the main focus of data and activities of each stage of software development.
In the software development process, a large number of work items are generated at different stages, the states of various work items change along with the work progress, and in order to record information contained in various work items and identify the states of the work items, the attributes of the work items need to be defined. Generally, the attributes of the work item mainly include ID number, type, time, participant, status, description, work record, link, and other categories, which are detailed in table 1.
TABLE 1 work item Attribute definition
In order to comprehensively describe a certain work item and record various types of information related to the work item, description fields with various attributes can be configured for the work item, and fields such as an ID number, a type, a start time, an end time, a responsible person, a state, main content, a change record and the like can be configured by taking a software requirement work item as an example. In each stage of software development, various work items can be used for recording software development activities, for example, in the stage of coding development, task work items, software source file work items and test case work items can be used for recording codes and three-stage test activities; in the system test phase, the system test activity and the like can be recorded by using a test case work item and a problem report work item.
The work items are defined around the software development engineering process line and the software product line, and as shown in tables 2 and 3, various types of data generated in the software development process are comprehensively collected.
TABLE 2 software product line work item definitions
TABLE 3 engineering Process line work item definitions
According to the software development state monitoring method, the work items to be monitored and the attributes corresponding to the work items can be determined according to the development data of each stage of the aerospace measurement and control software.
In an embodiment, referring to fig. 3, the determining a link manner between the work items according to a preset link relationship between the work items and the attributes corresponding to the work items includes:
s301: determining the current state of each work item according to the attribute corresponding to the work item;
s302: and determining the link mode among the work items according to the link relation and the current state.
It can be understood that the work items are basic elements for describing software development activities, but the software development process cannot be reflected only by collection and listing of the work items, the relationship between the work items is established, various work items are linked according to a software development process, and the key for realizing software development state tracking and influence analysis is realized. The relationships between workitems and workitems can be described by links, for example, developers can link software source file workitems to task workitems that produce them and can link task workitems to software requirement workitems that they implement, thus easily tracing back from the source file to their corresponding software requirements.
The definition of the link mode between the workitems mainly comprises two parts, namely a link type and a rule, wherein the link type describes which categories of link modes exist between the workitems, for example, a link 'trigger' can be specified for the link between the test case workitem and the problem report sheet workitem to indicate that the test case triggers the problem report sheet; when a certain type of link is defined, a reverse link corresponding to the link can also be defined, for example, a "trigger" link can have a reverse link "triggered" for linking a problem report work item to a test case. Rules define which types of links are allowed to exist between which types of work items, and a specified type of link is allowed from one or more work item types to one or more work item types, each rule having attributes "from type" and "to type", both of which may take multiple values, i.e., a rule may allow links from a single type to multiple types, from multiple types to a single type, from multiple types to multiple types, or from a single type to the same type only. For example, a rule that "implements" a link is to allow a task work item to a software requirements work item and a system design work item, a rule that "is verified" a link is to allow a system design work item and a software requirements work item to a test case work item, and so on. In this section, a typical link mode in the development process of space measurement and control software is defined as shown in table 4:
TABLE 4 definition of link patterns between work items
The link mode among the work items can be defined through the table 4, and traceability among software system design, software requirements, software design, software codes, software tests and software products can be established and maintained. And according to the definition of the incidence relation among the work items, automatically giving the incidence relation meeting the requirements when establishing the incidence relation among the work items. The mode of linking the work items at each stage of the development process of the space measurement and control software is shown in fig. 11.
As can be seen from the above description, the software development state monitoring method provided by the present application can determine the link mode between the work items according to the preset link relationship between the work items and the attributes corresponding to the work items.
In an embodiment, referring to fig. 4, the generating a monitoring mark form of the software development state according to the link manner includes:
s401: generating a header of the monitoring mark form according to each work item;
s402: establishing a mapping relation between the work items according to the link mode between the work items;
s403: and obtaining the monitoring mark form according to the form header and the mapping relation.
It can be understood that in the software development process, different work items have different life cycles due to different introduction times, for example, the life cycle of a software design work item may be from the beginning of software design until the software is released online, and the life cycle of a task work item may be from the beginning of code writing to the software being released online. In order to obtain the progress of the work represented by the work item in time, the state attribute of the work item may be used to define the states that the work item may have in its lifecycle, for example, the states "design in progress" and "design complete" may be defined for a software design work item, and in order to describe the state of a certain work item in its lifecycle and the circulation situation of the state, a state tracking matrix needs to be established. The establishment of the state tracking matrix requires the definition of two elements, a state and an action, the definition of the state requires the determination of the states that a work item can have at various stages of its lifecycle (e.g., "in system design", "system design complete", etc.), and the definition of the action determines what action is required to transition the work item from one state to another, e.g., "mark complete" action transition work item to "design complete" state. The status and the action of the work item are combined together through the status tracking matrix, and the status tracking can be realized in the life cycle of the work item, for example, the status tracking of the whole process from the software system design to the online release of the product can be realized by establishing the status tracking matrix of the software system design work item, which is shown in fig. 12.
The first row of the state tracking matrix lists all the states that the system design work items possess, the green arrow is a forward arrow, the red arrow is a reverse arrow, the forward and reverse arrows represent actions, and the direction of the state tracking matrix is from row to column. For example, a forward arrow at the intersection of row and column system design complete indicates a transition from the system design in state to the system design complete state, and at each intersection where a transition action exists, an action needs to be defined. The forward arrow in FIG. 12 represents the action "Mark" that may transition the software design work item from a current state to a subsequent state, and the reverse arrow represents the action "Back to" that may return the software design work item from the current state to a previous state.
Referring to fig. 13, in order to reflect the software development process from different levels and implement the state feedback from bottom to top, the state linkage between the work items linked with each other on the engineering process line and the product line can be implemented according to the link mode between the work items. The linkage algorithm is as follows:
1) when a work item is newly added in a certain software development stage, the state of the upstream work item is consistent with the state of the work item.
2) When the state of a certain work item on an engineering process line or a product line is changed, the state of the work item on the same layer is automatically inquired, and when the states of all the work items on the same layer meet the appointed state, the upstream work item is updated to the appointed state.
3) All work item status is passed from downstream work item status, and if non-leaf node work item status is artificially altered, all downstream work items of the work item are highlighted to remind the software developer to confirm.
After the state tracking matrix of the work items is established, the state distribution conditions of all system design items of a project can be counted from the perspective of the whole software research and development project management, and the short-line work items restricting the project progress can be identified in time; and consistency among system design, demand analysis, code development, system test and warehousing release can be tracked from the perspective of the life cycle of a work item, and a final product is ensured to meet the design requirement of the system.
As can be seen from the above description, the software development state monitoring method provided by the present application can generate the monitoring mark form of the software development state according to the link manner.
The invention is used for carrying out the development process management of the large-scale space mission software, and has the following advantages:
1. and the software research and development process integrates tracking and feedback. In the prior art, software development work is mainly managed by single-point tools at each stage of software development, software requirements are managed by open source requirement management tools such as Zen channel and the like, software system integration and test work is mainly managed and controlled by an open source software testlink software test management platform, software code and parameter management is mainly managed and controlled by SVN version management tools, data exchange between platforms and tools at each stage cannot be carried out, tracking of software development process is mainly carried out by manually maintaining a state management and control table, and the problems of incomplete data, inaccurate state, inconsistent reality and the like easily occur, by using the software development state tracking feedback method, various data records in the whole process from software requirements to software development of software products are realized, engineering personnel can comprehensively and accurately master the technical state of a project, and the whole process from requirements, design, development, testing to deployment of software development is effectively tracked.
2. And (5) management and engineering fusion. By using the software development state tracking method, engineering processes such as requirement analysis, software design, coding development, integrated test and the like are decomposed into work items, attributes such as states, time, link modes and the like are given to different types of work items, a platform report engine is used for analyzing and perspective the running state of a project in real time, management and engineering fusion are realized, work and data borne by all roles are clear at a glance, the whole software development process is more transparent, and the problems that the progress conditions of two skins and the project in the management process and the engineering process depend on manual statistical analysis and the like are solved.
Based on the same inventive concept, the embodiment of the present application further provides a software development state monitoring apparatus, which can be used to implement the method described in the above embodiment, as described in the following embodiments. Because the principle of the software development state monitoring device for solving the problems is similar to the software development state monitoring method, the implementation of the software development state monitoring device can refer to the implementation of the software performance reference determination method, and repeated parts are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
In an embodiment, referring to fig. 5, in order to integrally track and feed back the development process of the space measurement and control software according to the development data of each stage of the space measurement and control software, the software development state monitoring device according to the present application includes:
the work item and attribute determining unit 501 is configured to determine a work item to be monitored and an attribute corresponding to the work item according to research and development data of each stage of the aerospace measurement and control software;
a link mode determining unit 502, configured to determine a link mode between the work items according to a preset link relationship between the work items and the attributes corresponding to the work items;
and a monitoring form determining unit 503, configured to generate a monitoring marking form of the software development state according to the link manner.
In an embodiment, referring to fig. 6, the research and development data of the aerospace measurement and control software includes research and development function description, research and development time, research and development state, and research and development relationship, the attributes include work item type, work item time, work item state, and work item relationship, and the work item and attribute determining unit 501 includes:
a type determining module 601, configured to determine the type of the work item according to the development function description;
a time determining module 602, configured to determine the work item time according to the development time;
a state determining module 603, configured to determine the state of the work item according to the research and development state;
a relationship determining module 604, configured to determine the work item relationship according to the research and development relationship.
In an embodiment, referring to fig. 7, the link mode determining unit 502 includes:
a current state determining module 701, configured to determine a current state of each work item according to an attribute corresponding to the work item;
a link mode determining module 702, configured to determine a link mode between each work item according to the link relationship and the current state.
In an embodiment, referring to fig. 8, the monitoring form determining unit 502 includes:
a header generation module 801, configured to generate a header of the monitoring mark form according to each work item;
a mapping relationship generating module 802, configured to establish a mapping relationship between the work items according to a link manner between the work items;
and a monitoring form determining module 803, configured to obtain the monitoring marking form according to the header and the mapping relationship.
In order to integrally track and feed back the development process of the space measurement and control software according to the development data of each stage of the space measurement and control software on a hardware level, the application provides an embodiment of an electronic device for realizing all or part of the contents in the software development and control state monitoring method, and the electronic device specifically comprises 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 software research and development state monitoring device and relevant equipment such as a core service system, a user terminal, a relevant database and the like; the logic controller 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 logic controller may be implemented with reference to the embodiment of the software development state monitoring method and the embodiment of the software development state monitoring apparatus in the embodiment, and the contents thereof are incorporated herein, and repeated descriptions are omitted.
It is understood that the user terminal may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), an in-vehicle device, a smart wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..
In practical applications, part of the software development state monitoring method may be executed on the electronic device side as described above, or all operations may be completed in the client device. The selection may be specifically performed according to the processing capability of the client device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. The client device may further include a processor if all operations are performed in the client device.
The client device may have a communication module (i.e., a communication unit), and may be in communication connection with a remote server to implement data transmission with the server. The server may include a server on the side of the task scheduling center, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.
Fig. 9 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. 9, 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. 9 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 software development status monitoring method function may be integrated into the central processor 9100. The central processor 9100 may be configured to control as follows:
s101: determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
s102: determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items;
s103: and generating a monitoring marking form of the software development state according to the link mode.
From the above description, the software development state monitoring method provided by the application can realize comprehensive collection and entry management of various data in the whole life cycle of the aerospace measurement and control software by defining different types of work items and configuring description fields with various attributes around a software development engineering process line and a software product line; by defining a typical link relation in the development process of the aerospace measurement and control software, the bidirectional tracking of work items in each stage of the development process of the aerospace measurement and control software is realized, and the change influence domain is quickly and accurately judged; by establishing a work item state conversion matrix and realizing software development state feedback from bottom to top through a work item state linkage method, the consistency and the integrity between software products from user requirements are quickly detected and verified, and the transparent management of the whole process from the requirements to the delivery of the software is realized.
In another embodiment, the software development state monitoring device may be configured separately from the central processing unit 9100, for example, the software development state monitoring device of the data composite transmission device may be configured as a chip connected to the central processing unit 9100, and the function of the software development state monitoring method may be implemented by the control of the central processing unit.
As shown in fig. 9, 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. 9; in addition, the electronic device 9600 may further include components not shown in fig. 9, which may be referred to in the prior art.
As shown in fig. 9, 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.
The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD 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 lan module, may be disposed 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 steps in the software development state monitoring method in which an execution subject is a server or a client in the foregoing embodiments, 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 steps of the software development state monitoring method in which the execution subject is the server or the client, for example, when the processor executes the computer program, the processor implements the following steps:
s101: determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
s102: determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items;
s103: and generating a monitoring marking form of the software development state according to the link mode.
From the above description, the software development state monitoring method provided by the application can realize comprehensive collection and entry management of various data in the whole life cycle of the aerospace measurement and control software by defining different types of work items and configuring description fields with various attributes around a software development engineering process line and a software product line; by defining a typical link relation in the development process of the aerospace measurement and control software, the bidirectional tracking of work items in each stage of the development process of the aerospace measurement and control software is realized, and the change influence domain is quickly and accurately judged; by establishing a work item state conversion matrix and realizing software development state feedback from bottom to top through a work item state linkage method, the consistency and the integrity between software products from user requirements are quickly detected and verified, and the transparent management of the whole process from the requirements to the delivery of the software is realized.
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 (10)
1. A software development state monitoring method is characterized by comprising the following steps:
determining a work item to be monitored and attributes corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
determining a link mode between the work items according to a preset link relation between the work items and the attributes corresponding to the work items;
and generating a monitoring marking form of the software development state according to the link mode.
2. The software development state monitoring method according to claim 1, wherein the aerospace measurement and control software development data includes development function description, development time, development state and development relationship, the attributes include work item type, work item time, work item state and work item relationship, the determining of the work items to be monitored and the attributes corresponding to the work items according to the development data of each stage of the aerospace measurement and control software includes:
determining the type of the work item according to the development function description;
determining the work item time according to the research and development time;
determining the work item state according to the research and development state;
and determining the relation of the work items according to the research and development relation.
3. The method for monitoring the software development state according to claim 1, wherein the determining the link mode between the work items according to the preset link relationship between the work items and the attributes corresponding to the work items comprises:
determining the current state of each work item according to the attribute corresponding to the work item;
and determining the link mode among the work items according to the link relation and the current state.
4. The method for monitoring the development status of software according to claim 3, wherein the generating of the monitoring mark form of the development status of software according to the linking manner includes:
generating a header of the monitoring mark form according to each work item;
establishing a mapping relation between the work items according to the link mode between the work items;
and obtaining the monitoring mark form according to the form header and the mapping relation.
5. A software development status monitoring apparatus, comprising:
the system comprises a work item and attribute determining unit, a task item and attribute determining unit and a monitoring unit, wherein the work item and attribute determining unit is used for determining a work item to be monitored and an attribute corresponding to the work item according to research and development data of each stage of aerospace measurement and control software;
the link mode determining unit is used for determining the link mode among the work items according to the preset link relation among the work items and the attributes corresponding to the work items;
and the monitoring form determining unit is used for generating a monitoring marking form of the software development state according to the link mode.
6. The software development state monitoring device according to claim 5, wherein the aerospace measurement and control software development data includes development function description, development time, development state and development relationship, the attributes include work item type, work item time, work item state and work item relationship, and the work item and attribute determining unit includes:
the type determining module is used for determining the type of the work item according to the development function description;
the time determining module is used for determining the time of the work items according to the research and development time;
the state determining module is used for determining the state of the work item according to the research and development state;
and the relation determining module is used for determining the relation of the work items according to the research and development relation.
7. The software development state monitoring device according to claim 5, wherein the link mode determining unit includes:
the current state determining module is used for determining the current state of each work item according to the attribute corresponding to the work item;
and the link mode determining module is used for determining the link mode among the work items according to the link relation and the current state.
8. The software development status monitoring device according to claim 7, wherein the monitoring form determination unit includes:
the header generation module is used for generating a header of the monitoring mark form according to each work item;
the mapping relation generating module is used for establishing the mapping relation among the work items according to the link mode among the work items;
and the monitoring form determining module is used for obtaining the monitoring mark form according to the form header and the mapping relation.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the software development status monitoring method of any one of claims 1 to 4 are implemented when the program is executed by the processor.
10. 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 software development status monitoring method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111114050.9A CN113835960B (en) | 2021-09-23 | 2021-09-23 | Method and device for monitoring and marking research and development states of aerospace measurement and control software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111114050.9A CN113835960B (en) | 2021-09-23 | 2021-09-23 | Method and device for monitoring and marking research and development states of aerospace measurement and control software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113835960A true CN113835960A (en) | 2021-12-24 |
| CN113835960B CN113835960B (en) | 2024-07-02 |
Family
ID=78969234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111114050.9A Active CN113835960B (en) | 2021-09-23 | 2021-09-23 | Method and device for monitoring and marking research and development states of aerospace measurement and control software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835960B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2884339A1 (en) * | 2005-04-07 | 2006-10-13 | Abelsin France Sarl | Software testing designing and performing method for software development enterprise, involves performing study of domain of software testing and constitutive units of testing, where study is made on imperatives in testing materials |
| US20130117725A1 (en) * | 2011-11-06 | 2013-05-09 | International Business Machines Corporation | Using traceability links strength for software development integrity monitoring |
| CN104217035A (en) * | 2014-09-29 | 2014-12-17 | 余声 | Update method for software product database |
| CN106528119A (en) * | 2016-11-02 | 2017-03-22 | 北京神舟航天软件技术有限公司 | Requirement tracing method based on research and development work product identification |
| CN108388495A (en) * | 2018-01-10 | 2018-08-10 | 链家网（北京）科技有限公司 | A kind of data monitoring method and system |
| US10496402B1 (en) * | 2017-09-28 | 2019-12-03 | Amdocs Development Limited | System, method, and computer program for defining and utilizing minimal testable values for software project development and operations |
| CN111461666A (en) * | 2020-04-07 | 2020-07-28 | 中国建设银行股份有限公司 | Demand tracking matrix display method and system |
| CN112148252A (en) * | 2020-09-03 | 2020-12-29 | 杭州云徙科技有限公司 | Software research and development requirement-based full life cycle management system and tracking method |
| CN112905262A (en) * | 2021-03-09 | 2021-06-04 | 中国人民解放军63920部队 | Configuration method and device of aerospace measurement and control system |
-
2021
- 2021-09-23 CN CN202111114050.9A patent/CN113835960B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2884339A1 (en) * | 2005-04-07 | 2006-10-13 | Abelsin France Sarl | Software testing designing and performing method for software development enterprise, involves performing study of domain of software testing and constitutive units of testing, where study is made on imperatives in testing materials |
| US20130117725A1 (en) * | 2011-11-06 | 2013-05-09 | International Business Machines Corporation | Using traceability links strength for software development integrity monitoring |
| CN104217035A (en) * | 2014-09-29 | 2014-12-17 | 余声 | Update method for software product database |
| CN106528119A (en) * | 2016-11-02 | 2017-03-22 | 北京神舟航天软件技术有限公司 | Requirement tracing method based on research and development work product identification |
| US10496402B1 (en) * | 2017-09-28 | 2019-12-03 | Amdocs Development Limited | System, method, and computer program for defining and utilizing minimal testable values for software project development and operations |
| CN108388495A (en) * | 2018-01-10 | 2018-08-10 | 链家网（北京）科技有限公司 | A kind of data monitoring method and system |
| CN111461666A (en) * | 2020-04-07 | 2020-07-28 | 中国建设银行股份有限公司 | Demand tracking matrix display method and system |
| CN112148252A (en) * | 2020-09-03 | 2020-12-29 | 杭州云徙科技有限公司 | Software research and development requirement-based full life cycle management system and tracking method |
| CN112905262A (en) * | 2021-03-09 | 2021-06-04 | 中国人民解放军63920部队 | Configuration method and device of aerospace measurement and control system |
Non-Patent Citations (1)
| Title |
|---|
| 杨悦;秦湘河;杨永安;郭荣;: "航天测控软件测试用例标准及应用研究", 无线电工程, no. 09, 5 September 2013 (2013-09-05) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113835960B (en) | 2024-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Shrivastava et al. | A systematic review on extreme programming | |
| Janiesch et al. | Beyond process monitoring: a proof‐of‐concept of event‐driven business activity management | |
| EP3991112A1 (en) | System and method for modelling and monitoring processes in organizations using digital twins | |
| USRE44188E1 (en) | System and method for dynamically simulating process and value stream maps | |
| US8538797B2 (en) | Systems and methods for integrating business processes | |
| US20060241997A1 (en) | System and method for integrating workflow processes with a project management system | |
| CN113626914A (en) | Engineering project management method, device and system based on digital twins | |
| CN106933729A (en) | A kind of method of testing and system based on cloud platform | |
| CN112783793B (en) | Automatic interface test system and method | |
| US20230004149A1 (en) | Digital twin modeling and optimization of production processes | |
| CN115730783A (en) | BIM-based visual engineering construction management platform and system | |
| CN115394143A (en) | Virtual simulation education system based on digital twins and interaction method thereof | |
| van der Aalst et al. | Removing operational friction using process mining: challenges provided by the internet of production (IoP) | |
| Dovleac et al. | Quality management techniques embedded in Agile project development | |
| de Gea et al. | Requirements engineering tools: An evaluation | |
| Woitsch | Industrial digital environments in action: the OMiLAB innovation corner | |
| Ferreira et al. | Industry 4.0 as enabler for effective manufacturing virtual enterprises | |
| Santos et al. | Industrial IoT integrated with simulation-A digital twin approach to support real-time decision making | |
| Cosmas et al. | Transitions in System Analysis and Design Methodology | |
| Lu et al. | Collaborative scientific workflows | |
| Ahmed et al. | A comparison of three simulation methodologies for a Lean Six Sigma manufacturing project–a business case study | |
| CN113722564A (en) | Visualization method and device for energy and material supply chain based on space map convolution | |
| CN117744914A (en) | BIM-based construction digital management method, platform and computer equipment | |
| CN112783475A (en) | Embedded software demand analysis method | |
| Kruse et al. | Building a connection between decision maker and data-driven decision process |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |