CN115454382A - Demand processing method and device, electronic equipment and storage medium - Google Patents
Demand processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115454382A CN115454382A CN202211150193.XA CN202211150193A CN115454382A CN 115454382 A CN115454382 A CN 115454382A CN 202211150193 A CN202211150193 A CN 202211150193A CN 115454382 A CN115454382 A CN 115454382A
- Authority
- CN
- China
- Prior art keywords
- information
- subtask
- requirement
- subtask information
- task
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003860 storage Methods 0.000 title claims abstract description 26
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 238000000034 method Methods 0.000 claims abstract description 53
- 238000012827 research and development Methods 0.000 claims abstract description 42
- 230000015654 memory Effects 0.000 claims description 22
- 238000012545 processing Methods 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 12
- 238000000605 extraction Methods 0.000 claims description 5
- 238000011161 development Methods 0.000 description 35
- 238000005516 engineering process Methods 0.000 description 24
- 238000007726 management method Methods 0.000 description 21
- 238000012360 testing method Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 12
- 238000013515 script Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 239000000284 extract Substances 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 3
- 239000008186 active pharmaceutical agent Substances 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 235000015114 espresso Nutrition 0.000 description 2
- 238000003058 natural language processing Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 229910052711 selenium Inorganic materials 0.000 description 2
- 239000011669 selenium Substances 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
- G06V30/10—Character recognition
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Multimedia (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a demand processing method and device, electronic equipment and a computer readable storage medium, and belongs to the technical field of research and development management, wherein the method comprises the following steps: acquiring a requirement document; extracting a plurality of requirement information and a plurality of subtask information from a requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is used for representing research and development subtasks for completing the service requirements; dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the demand information one to one; and determining the man-hour required for completing the subtask information according to the quantity of the subtask information in the demand information and the corresponding task set. According to the method and the device, the requirement document is obtained, the requirement information and the subtask information are extracted from the requirement document, the subtask information is constructed into the task set, and the working hours required for completing each subtask information are determined according to the quantity of the requirement information and the corresponding subtask information in the task set, so that the purpose of saving labor cost is achieved.
Description
Technical Field
The present application relates to the field of research and development management technologies, and in particular, to a demand processing method and apparatus, an electronic device, and a storage medium.
Background
In an agile development mode, a developer of an application often splits the application into a plurality of independent subtasks, after the subtasks of main functions of the application are completed, the application is quickly online, and then the functions of the application are gradually extended through frequent iterative updating, so that the program development efficiency is improved.
Disclosure of Invention
The embodiment of the application mainly aims to provide a demand processing method and device, electronic equipment and a computer readable storage medium, which can automatically input data according to a demand document and calculate the working hours required by each research and development subtask, and save a large amount of manpower.
In order to achieve the above object, a first aspect of an embodiment of the present application provides a demand processing method, including: a method of demand handling, comprising: acquiring a requirement document; extracting a plurality of requirement information and a plurality of subtask information from the requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is used for representing research and development subtasks for completing the service requirements; dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the requirement information one to one; and determining the working hours required for completing the subtask information according to the quantity of the subtask information in the corresponding task set and the requirement information.
In some embodiments, the extracting the plurality of requirement information and the plurality of subtask information from the requirement document includes:
extracting a plurality of requirement information from the requirement document according to a preset first characteristic identifier, wherein the first characteristic identifier is used for indicating the requirement information;
and extracting a plurality of subtask information from the requirement document according to a preset second feature identifier, wherein the second feature identifier is used for indicating the subtask information.
In some embodiments, the dividing the plurality of subtask information into a plurality of task sets includes:
extracting a characteristic identifier from the subtask information, wherein the characteristic identifier is used for indicating a corresponding relation between the subtask information and the requirement information;
dividing at least one piece of subtask information corresponding to the same requirement information into the same task set according to the characteristic identification so as to obtain a plurality of task sets.
In some embodiments, after the dividing the plurality of the subtask information into a plurality of task sets, the method further includes:
under the condition that the requirement information is detected to comprise a preset task splitting identifier, copying each subtask information in the task set corresponding to the requirement information to obtain a plurality of second subtask information;
and dividing a plurality of second subtask information and the subtask information into the same task set.
In some embodiments, the requirement information includes a preset workload and the subtask information includes a man-hour label.
In some embodiments, the determining, according to each of the requirement information and the number of the subtask information in the corresponding task set, the man-hours required for completing the subtask information includes:
extracting a preset workload of a demand from the demand information;
and determining the working hours required for completing the subtask information according to the ratio of the preset workload to the number of the subtask information in the corresponding task set.
In some embodiments, after determining the man-hours required for completing the subtask information according to each of the requirement information and the number of the subtask information in the corresponding task set, the method further includes:
traversing all the subtask information in the task set;
and updating the man-hour label of each subtask information according to the man-hour of the subtask information.
A second aspect of an embodiment of the present application provides a demand processing apparatus, including:
an acquisition unit configured to acquire a demand document;
the information extraction unit is used for extracting a plurality of requirement information and a plurality of subtask information from the requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is used for representing research and development subtasks for completing the service requirements;
the task set dividing unit is used for dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the requirement information one to one;
and the man-hour calculating unit is used for determining the man-hours required for completing the subtask information according to the requirement information and the number of the subtask information in the corresponding task set.
A third aspect of the embodiments of the present application provides an electronic device, where the electronic device includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for implementing connection communication between the processor and the memory, where the program, when executed by the processor, implements the demand handling method according to any one of the above first aspect of the embodiments of the present invention.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium for computer-readable storage, where one or more programs are stored, and the one or more programs can be executed by one or more processors to implement the requirement processing method according to any one of the embodiments of the first aspect.
The requirement processing method and device, the electronic equipment and the computer-readable storage medium provided by the embodiment of the application acquire a requirement document; extracting a plurality of requirement information and a plurality of subtask information from the requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is used for completing research and development subtasks of the service requirements; dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the requirement information one to one; and determining the working hours required for completing the subtask information according to the quantity of the subtask information in the corresponding task set and the requirement information. According to the embodiment of the application, the requirement document is obtained, the requirement information and the subtask information are directly extracted from the requirement document, the step that manual work is conducted to enter the requirement information and the subtask information into a research and development management system one by one is replaced, a large amount of labor cost is saved, the subtask information is constructed into the task set, the man-hours needed by completion of each subtask information are determined according to the quantity of the requirement information and the corresponding subtask information in the task set, the step that the man-hours needed by completion of each subtask information are calculated manually is replaced, and the purpose of saving the labor cost is achieved.
Drawings
FIG. 1 is a flowchart of a demand handling method provided in an embodiment of the present application;
FIG. 2 is a sub-flowchart of a demand handling method provided in an embodiment of the present application;
FIG. 3 is a sub-flowchart of a method for processing a demand provided by an embodiment of the present application;
FIG. 4 is a sub-flowchart of a method for processing a demand provided by an embodiment of the present application;
FIG. 5 is a sub-flowchart of a demand handling method provided in an embodiment of the present application;
FIG. 6 is a sub-flowchart of a method for processing a demand provided by an embodiment of the present application;
fig. 7 is a block diagram of a module structure of a demand processing apparatus according to an embodiment of the present application;
fig. 8 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad application.
It should be noted that although functional blocks are illustrated as being partitioned in a schematic diagram of an apparatus and logical order is illustrated in a flowchart, in some cases, the steps illustrated or described may be executed in a different order than the partitioning of blocks in the apparatus or the order in the flowchart. The terms first, second and the like in the description and in the claims, and the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow diagrams depicted in the figures are merely exemplary and do not necessarily include all of the elements and operations/steps, nor do they necessarily have to be executed in the order depicted. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual operation sequence may be changed according to the actual situation.
First, several terms referred to in the present application are resolved:
agile development (Agile): in agile development, construction of a software project is split into a plurality of sub-projects, and results of each sub-project are tested and have the characteristics of integration and operability. In short, the agile development mode does not pursue perfect design and coding in the early stage, but strives to develop the core function of the product in a short period, and in the subsequent production period, the product is continuously updated and perfected according to new requirements.
Iterative incremental software development process (scrub): is one of the important development frameworks for agile development, including a series of time and predefined role process frameworks.
OCR character recognition: refers to a process in which an electronic device (e.g., a scanner or a digital camera) checks characters printed on paper and then translates the shape into computer text using a character recognition method; namely, the process of scanning the text data, then analyzing and processing the image file and obtaining the character and layout information.
Interface automation: a mode for simulating a user to manually operate a UI interface through scripts is commonly used for repeated function test and verification.
Natural Language Processing (NLP): the method is a science integrating linguistics, computer science and mathematics, and is mainly applied to the aspects of machine translation, public opinion monitoring, automatic summarization, viewpoint extraction, text classification, question answering, text semantic comparison, voice recognition, chinese OCR and the like.
Browser automation test framework (Selenium): a tool for Web application program testing is characterized in that a framework bottom layer simulates a real user to operate a browser by using JavaScript. When the test script is executed, the browser automatically performs operations such as clicking, inputting, opening, verifying and the like according to the script code, and tests the application program from the perspective of the terminal user as a real user does.
UIAutomator: a UI test framework can be operated in a cross-process mode based on the Accessibility service, and a series of automatic test operations such as clicking, sliding, keyboard input, long pressing and other common operations can be performed through an API provided by the framework.
The Espresso test framework: an automated testing framework provides a series of APIs for building UI tests to test user stream operations within apps. Through these APIs, compact and reliable automated UI tests can be written. Espresso is adapted to write white-box tests, where test code is written using program code implementation details in the app being tested.
jar package (Java Archive File): a document format of Java, which is a file obtained by packaging a class file, that is, a file obtained by packaging a written class.
JAVA script language (JavaScript, JS), a lightweight, interpreted or just-in-time, programming language with function precedence. Although it is named as a scripting language for developing Web pages, it is also used in many non-browser environments, javaScript is a dynamic scripting language based on prototypes, multiple paradigms, and supports object-oriented, imperative, declarative, functional programming paradigms.
Stack Style Sheets (screening Style Sheets, css): a computer language for expressing file styles such as HTML and XML can be used for statically modifying a webpage and dynamically formatting elements of the webpage in cooperation with various script languages. The method can accurately control the typesetting of the element positions in the webpage at a pixel level.
Hyper Text Markup Language (HTML), a Markup Language, includes a series of tags, through which the document format on the grid can be unified, so that the dispersed resources are connected into a logical whole, which is a descriptive Text composed of HTML commands.
Front-end (front-end) is a website foreground part, which runs on a PC (personal computer) end, and web pages displayed on a mobile end browser for a user to browse are generally divided into front-end design and front-end development, the front-end development is mainly realized by foreground codes of the website and is generally realized by programming technologies such as HTML (hypertext markup language) used for defining elements, CSS (cascading style sheet) used for positioning the elements, javascript used for realizing the interaction between the web pages and the user, and the interaction between the front end and the back end.
Rear end (back-end): the back end works in the background, controls the content displayed at the front end, is mainly responsible for designing architecture ideas and managing the database, and pays more attention to the protection of the back end and the database to process corresponding business logic, and how to realize functions, data storage, platform stability, performance and the like needs to be considered.
Array (Array): is an ordered sequence of elements. If a set of a finite number of variables of the same type is named, then this name is the array name. The individual variables that make up an array are referred to as the components of the array, also referred to as the elements of the array, and sometimes as subscript variables. The numerical numbering used to distinguish the various elements of the array is referred to as the subscript. An array is a form in which elements of the same type are organized in an ordered fashion for processing convenience in programming. The collection of these ordered homogeneous data elements is called an array. An array is a collection for storing multiple data of the same type.
Struct (struct) a composite data type, a data set consisting of a series of data of the same type or different types.
Tree structure (tree): a non-linear data structure, intuitively, is a structure of data elements (called nodes in a tree) organized in a branching relationship, much like a tree in nature.
Traversal (Traversal): refers to that along a certain search route, each node in the tree (or graph) is visited once in turn. The operation performed by the access node depends on the specific application problem, and the specific access operation may be to check the value of the node, update the value of the node, and the like. Different traversal methods have different access node orders. Traversal is one of the most important operations in the binary tree, and is the basis for performing other operations in the binary tree. The concept of traversal is also applicable to the case of multi-element sets, such as arrays.
In the conventional research and development management tool, after the business requirements are clarified through a conference and other manners and the research and development subtasks for solving each business requirement are arranged into a requirement document, man-hour required by each research and development subtask needs to be calculated through manpower, the business requirements, the research and development subtasks and the man-hour required by each research and development subtask need to be recorded into the research and development management tool, and a large amount of man-hour required by the research and development data needs to be calculated under the condition of large data volume.
Based on this, the embodiment of the application provides a demand processing method and apparatus, an electronic device, and a computer-readable storage medium, which can effectively achieve automatic data extraction according to a demand document and calculate the time required for completing each research and development subtask, thereby saving a lot of manpower.
The embodiment of the present application provides a demand method and apparatus, an electronic device, and a storage medium, and is specifically described with reference to the following embodiments, in which a demand processing method in the embodiment of the present application is first described.
The requirement processing method provided by the embodiment of the application can be applied to a terminal, can also be applied to a server, and can also be software which runs on the basis of the terminal or the server, such as jar packages which run on the terminal. In some embodiments, the terminal may be a smartphone, tablet, laptop, desktop computer, smart watch, or the like; the server side can be configured into an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and cloud servers for providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN (content delivery network) and big data and artificial intelligence platforms; the software may be an application or the like implementing the desired method, but is not limited to the form described above. Embodiments of the application are operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In the following embodiment of the invention, the requirement processing method provided by the embodiment of the application is applied to the server side, and a user can execute the requirement processing method in the embodiment of the application on the remote server only by uploading the requirement document through the terminal and then sending the requirement document to the server side, so that the problem of incompatibility caused by different working environments is solved.
Referring to fig. 1, the demand handling method according to the embodiment of the present disclosure includes, but is not limited to, steps S100 to S400.
Step S100, acquiring a requirement document;
step S200, extracting a plurality of requirement information and a plurality of subtask information from a requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is a research and development subtask used for representing and completing the service requirements;
step S300, dividing a plurality of subtask information into a plurality of task sets, wherein the task sets correspond to the demand information one to one;
and step S400, determining the working hours required for completing the subtask information according to the required information and the number of the subtask information in the corresponding task set.
In step S100 of some embodiments, the requirement document is a document or a table in which requirement information and subtask information for completing the requirement information are recorded, such as a document obtained by a product manager sorting requirements or a meeting record formed after a requirement discussion meeting, and in some possible embodiments, may also be a requirement document obtained by recognizing a paper meeting record through an OCR character recognition technology. Specifically, the acquiring of the demand document may be acquiring of a demand document actively uploaded to the server by the user through the browser web.
In step S200 of some embodiments, a plurality of requirement information and a plurality of subtask information are extracted from the requirement document, where the requirement information is used to characterize the business requirement, and at least includes a requirement name and a preset workload. The subtask information refers to a plurality of development subtasks for completing business requirements, wherein the development subtasks at least comprise a subtask name and a working hour label. Specifically, the requirement information and subtask information recorded in the requirement document can be extracted into the research and development management system one by one through an interface automation technology, wherein the interface automation technology is a technology enabling a machine to simulate operations such as user clicking, sliding and key triggering through a preset script program, the interface automation technology can be realized through an extension program of a browser web end, such as a chrome extension program of a google browser, the extension program of the browser is an extension program provided by the browser, and interaction with the browser can be performed through the extension program, such as user clicking, sliding and key triggering are simulated. In some embodiments, interface automation may also be implemented through interface automation scripts based on the Selenium framework, the espress framework, the uiautomation framework, or other UI automation framework.
In step S300 of some embodiments, the plurality of subtask information is divided into a plurality of task sets, where the task sets correspond to the requirement information one to one. Because each requirement information is realized by a plurality of subtasks together, on the basis, a plurality of subtasks corresponding to the same requirement information need to be divided into the same task set, so that a plurality of task sets respectively corresponding to each requirement information are obtained, and the number of research and development subtasks included in each requirement information is determined.
In step S400 of some embodiments, the man-hours required for the subtask information are determined according to the number of the subtask information in the requirement information and the corresponding task set, and specifically, after it is determined how many development subtasks are required to implement each requirement information, the preset workload of the requirement information may be allocated to each subtask information in the task set corresponding to the requirement information, so as to determine the man-hours required for completing each subtask information.
In the embodiment of the application, after the requirement document is obtained, the requirement information and the subtask information are extracted from the requirement document one by one through an interface automation technology, and then the subtask information is divided into a plurality of task sets, wherein each task set corresponds to the requirement information one by one, namely each task set corresponds to different requirement information, and based on the requirement information and the subtask information in the task set corresponding to the requirement information, the specific working hours of research and development of the subtask corresponding to each subtask information can be calculated according to the requirement information and the number of the subtask information in the task set corresponding to the requirement information. According to the method and the device, the requirement information and the subtask information in the requirement document are extracted into the research and development management system one by one through an interface automation technology, the subtask information is divided into the task set corresponding to each requirement information, the preset workload of the requirement information is distributed to each subtask information according to the number of the subtask information in the task set, the steps of inputting the requirement information and the subtask information into the research and development management system one by one and calculating the subtask working hours are replaced by manual work in an automatic mode, and a large amount of human resources are saved.
Referring to fig. 2, in some embodiments, step S200 includes, but is not limited to, steps S210 to S220.
Step S210, extracting a plurality of requirement information from a requirement document according to a preset first characteristic identifier, wherein the first characteristic identifier is used for indicating the requirement information;
step S220, extracting a plurality of subtask information from the requirement document according to a preset second feature identifier, where the second feature identifier is used to indicate the subtask information.
In step S210 of some embodiments, a plurality of requirement information is extracted from the requirement document according to a preset first feature identifier, where the first feature identifier is used to indicate the requirement information. For example, the requirement document is an excel form including a plurality of sheet pages, wherein a name of a certain sheet page is "business requirement", "property name", or other fields preset as a first feature identifier, after the system recognizes that the name of the sheet page is the preset first feature identifier, the system determines the content of the sheet page as requirement information, and then extracts the data in the sheet page one by one through an interface automation technology to a research and development management system as requirement information. In some embodiments, the requirement document may also be a table having multiple columns, where the header of each column has a type to which the content of the column belongs, and after the system recognizes that the header name of a certain column is "business requirement", "property information", or other fields preset as the first feature identifier, the system determines that the content of the column is property information, and then extracts the content of the column one by one into the research and development management system as requirement information through an interface automation technology. Specifically, the demand information in the document may be determined in an element locating manner, for example, by a find _ element function, according to a manner of locating the demand information as the first feature identifier, and then the demand information may be entered into the research and development management system item by item through an interface automation technology. The interface automation technology is realized by compiling or recording an interface automation script to simulate user operation, so that the requirement information is extracted into a research and development management system one by one, and can be understood as being realized based on a chrome extension program of a google browser, wherein the extension program of the browser is an extension program provided by the browser, and can interact with the browser through the extension program, such as simulating behaviors of clicking, sliding, key triggering and the like of a user.
In step S220 of some embodiments, a plurality of subtask information is extracted from the requirement document according to a preset second feature identifier, where the second feature identifier is used to indicate the subtask information. For example, the requirement document is an excel form including a plurality of sheet pages, wherein a name of a certain sheet page is "development subtask", "story information", "user story" or other fields preset as second feature identifiers, after the system recognizes that the name of the sheet page is a preset first feature identifier, the system determines the content of the sheet page as subtask information, and then extracts data in the sheet page one by one into the development management system as subtask information through an interface automation technology. In some embodiments, the requirement document may also be a table with multiple columns of contents, where the header of each column records the type to which the column of contents belongs, and after the system identifies that the header name of a certain column is "development subtask", "story information", "user story" or other fields preset as the second feature identifier, the system determines that the column of contents is subtask information, and then extracts the column of contents item by item through the interface automation technology into the development management system as subtask information. Specifically, the demand information in the document may be determined in an element locating manner, for example, by a find _ element function, according to a manner of locating the demand information as the first feature identifier, and then the demand information may be entered into the research and development management system item by item through an interface automation technology. The interface automation technology is realized by compiling or recording an interface automation script to simulate user operation, so that subtask information is extracted into a research and development management system one by one, and can be realized by a chrome extension program based on a google browser.
In the embodiment of the application, after a requirement document is obtained, requirement information is identified from the requirement document through a preset first feature identifier, subtask information is identified from the requirement document through a preset second feature identifier, the first feature identifier is used for indicating the requirement information, the second feature identifier is used for indicating the subtask information, the requirement information and the subtask information are extracted into a research and development management system one by one through an interface automation technology according to the first feature identifier and the second feature identifier, and therefore the step that the requirement information and the subtask information are manually input into the research and development management system one by one in an automated mode is replaced, and a large number of human resources are saved.
In some embodiments, as shown in fig. 3, step S300 includes, but is not limited to, the following steps S310 to S320.
Step S310, extracting characteristic identification from the subtask information, wherein the characteristic identification is used for indicating the corresponding relation between the subtask information and the requirement information;
step S320, dividing at least one sub-task information corresponding to the same requirement information into the same task set according to the characteristic identifier, so as to obtain a plurality of task sets.
In step S310 of some embodiments, a property identifier is extracted from the subtask information, where the property identifier is used to indicate a correspondence between the subtask information and the requirement information. For example, a sequence number is allocated to each required information in the required document, and a sequence number corresponding to each required information exists in the subtask information as the characteristic identifier. In some embodiments, a character string representing the requirement information may also be directly used as a characteristic identifier to indicate the corresponding relationship between the subtask information and the requirement information.
In step S320 of some embodiments, at least one piece of subtask information corresponding to the same requirement information is divided into the same task set according to the characteristic identifier, so as to obtain a plurality of task sets. It should be noted that the form of the task set may be any one of an array, a tree, a structure, and the like.
Specifically, taking an array as a task set form as an example, firstly, a plurality of dynamic arrays are applied according to the quantity of demand information, wherein each dynamic array corresponds to one demand information, each dynamic array is named according to the content of the demand information or according to the serial number of the demand information, then the characteristic identifier of each item of subtask information in a demand document is detected, and the subtask information is written into the corresponding dynamic array in a character string form according to the corresponding relation between the characteristic identifier and the dynamic array name, so that all subtask information corresponding to the same demand information is divided into the same task set to obtain a plurality of task sets. In some embodiments, the structure body can be used as a task set, and compared with an array, the structure body can store character strings and data in other formats at the same time; in some embodiments, a tree structure may also be used as a task set, for example, the requirement information is used as a root node, and the subtask information corresponding to the requirement information is used as a child node, so as to obtain a plurality of tree structures, where each tree structure corresponds to a requirement information.
In the embodiment of the application, at least one piece of subtask information corresponding to the same requirement information is divided into the same task set by the subtask information through the characteristic identifier, so that a plurality of task sets respectively corresponding to each requirement information are obtained.
In some embodiments, as depicted in fig. 4, step S300 is followed by, but not limited to, the following steps S410-S420.
Step S410, under the condition that the requirement information is detected to comprise a preset task splitting identifier, copying each subtask information in a task set corresponding to the requirement information to obtain a plurality of second subtask information;
step S420, assign a plurality of second subtask information and subtask information into the same task set.
In step S410 of some embodiments, under the condition that it is detected that the requirement information includes a preset task split identifier, each piece of subtask information in a task set corresponding to the requirement information is copied to obtain a plurality of pieces of second subtask information; specifically, because part of the business requirements in the application program research and development process need to be subjected to both front-end development and back-end development, and different programming languages are used for the front-end development and the back-end development, the front-end development task and the back-end development task should be distributed to developers in respective fields, and the front-end development and the back-end development of the same subtask are difficult to be performed synchronously, for requirement information that needs to be completed by both front-end development and back-end development, the task corresponding to the requirement information should be concentrated into each subtask information and further split into a front-end task and a back-end task. In some embodiments, after the subtask information is split into the front terminal task and the back terminal task, the front terminal task and the back terminal task also need to be renamed, for example, prefixes are added before the back terminal task and the front terminal task, and the back terminal task and the front terminal task are renamed to a Name (a "back end" Name "and a Name (a" front end ") respectively, so as to distinguish the two tasks to facilitate subsequent sub-task distribution.
In step S420 of some embodiments, since the second subtask information and the corresponding subtask information are a front-end subtask and a back-end subtask for implementing the same requirement information, the second subtask information is classified into a task set to which the corresponding subtask information belongs, so that the man-hours required for completing each subtask information and the distributed subtasks can be calculated more accurately subsequently.
In the embodiment of the application, after a requirement document is obtained, requirement information and subtask information are extracted from the requirement document one by one through an interface automation technology, and then the subtask information is divided into a plurality of task sets, wherein partial subtasks which can be realized only by performing front-end development and also by performing rear-end development are split to obtain front-terminal tasks respectively corresponding to the front-end development and rear-terminal tasks corresponding to the rear-end development, and then the front-terminal tasks and the rear-terminal tasks are divided into the original task sets of the subtask information, each task set corresponds to the requirement information one by one, namely each task set corresponds to different requirement information, and based on the requirement information and the number of the subtask information in the task set corresponding to the requirement information, the specific working hours for researching and developing the subtask corresponding to each subtask information can be calculated according to the requirement information and the number of the subtask information in the task set corresponding to the requirement information. According to the method and the device, the requirement information and the subtask information in the requirement document are extracted into the research and development management system one by one through an interface automation technology, the subtask information is divided into the task set corresponding to each requirement information, the preset workload of the requirement information is distributed to each subtask information according to the number of the subtask information in the task set, the steps of manually inputting the requirement information and the subtask information one by one and calculating the subtask working hours are replaced by an automatic mode, and a large amount of human resources are saved.
In some embodiments, as shown in fig. 5, step S400 includes, but is not limited to, the following steps S510 to S520.
Step S510, extracting a required preset workload from the required information;
and step S520, determining the working hours required by the completion of the subtask information according to the ratio of the preset workload to the number of the subtask information in the corresponding task set.
In step S510 of some embodiments, a preset workload of each demand information is extracted from the demand information, it is understood that the preset workload of each demand information is preset in the demand document, and after the keyword is identified, for example, a header of a certain column in the demand document is "required man-hour", "delivery deadline", "estimated workload", and the like, it is determined that the content of the column is the preset workload corresponding to each demand information, and each data of the column is the preset workload corresponding to the demand information of the row where the data of the column is located, and based on this, the preset workload of each demand information is extracted and determined from the content of the column.
In step S520 of some embodiments, the man-hours required for completing the subtask information are determined according to a ratio of the preset workload to the number of the subtask information in the corresponding task set, and it can be understood that, since the subtask information is obtained by subdividing the requirement information into a plurality of research and development subtasks, after the preset workload required for each requirement information is extracted, the preset workload of the requirement information is evenly distributed to each subtask information according to the number of the subtask information corresponding to each requirement information, thereby determining the man-hours of each subtask information.
In the embodiment of the application, after the requirement document is obtained, the requirement information and the subtask information are extracted from the requirement document one by one through an interface automation technology, and then the subtask information is divided into a plurality of task sets, wherein each task set corresponds to the requirement information one by one, namely each task set corresponds to different requirement information, and based on the requirement information and the subtask information in the task set corresponding to the requirement information, the specific working hours of research and development of the subtask corresponding to each subtask information can be calculated according to the requirement information and the number of the subtask information in the task set corresponding to the requirement information. According to the method and the device, the requirement information and the subtask information in the requirement document are extracted into the research and development management system one by one through an interface automation technology, the subtask information is divided into the task sets corresponding to each requirement information, the preset workload of the requirement information is distributed to each subtask information according to the number of the subtask information in the task sets, the steps of manually inputting the requirement information and the subtask information one by one and calculating the subtask working hours are replaced by an automatic mode, and a large amount of human resources are saved.
In some embodiments, as shown in fig. 6, step S400 is followed by, but not limited to, the following steps S610 to S620.
Step S610, traversing all subtask information in the task set;
and step S620, updating the man-hour label of each subtask information according to the man-hour of the subtask information.
In step S610 of some embodiments, all subtask information in the task set is traversed, specifically, each subtask information in the task set is accessed once after the working hours of each subtask information is determined. Specifically, taking the form of an array as a task set as an example, the array may be traversed through a map function.
In step S620 of some embodiments, the man-hour tag of each subtask information is updated according to the man-hour of the subtask information. Specifically, in the process of accessing each piece of subtask information in the task set, the labor hour tag of each piece of subtask information is updated according to the labor hour of the subtask information determined by the preset workload of the requirement information and the number of the subtask information in the corresponding task set. Specifically, taking the form of an array as a task set as an example, traversing the array through a map function can be realized, and parameter information in the array is modified in the traversing process, so that the man-hour label of each subtask information is updated.
In the embodiment of the application, after the specific working hours of the research and development subtasks corresponding to each subtask information are calculated according to the quantity of the required information and the subtask information in the task set corresponding to the required information, the task set is traversed, for example, an array of the task set is traversed through a map function, and the working hour label of each subtask information is updated in the traversing process. Therefore, the tedious step of manually updating the man-hour label of each research and development subtask is replaced, and a large amount of human resources are saved.
According to the demand processing method provided by the embodiment of the application, a plurality of demand information and a plurality of subtask information are extracted from a demand document by acquiring the demand document, wherein the demand information is used for representing service demands, and the subtask information is used for completing research and development subtasks of the service demands; dividing the plurality of subtask information into a plurality of task sets, wherein the task sets correspond to the demand information one to one; and determining the man-hour required for completing the subtask information according to the quantity of the subtask information in the requirement information and the corresponding task set. After the requirement document is obtained, through an interface automation technology, requirement information is extracted from the requirement document according to a preset first characteristic mark, and subtask information is extracted from the requirement document according to a second characteristic mark. According to the corresponding relation between the requirement information and the subtask information, the subtask information is automatically divided into a plurality of task sets, the task sets correspond to the requirement information one by one, and according to a preset task splitting identifier, all subtask information in the task set corresponding to the requirement information which can be realized only by front-end development and back-end development is copied and renamed, so that the subtask is split into a front-end development subtask and a back-end development subtask. And then determining the working hours of each subtask information according to the preset workload of the demand information and the number of the subtask information in the task set corresponding to the demand information, and updating the working hour labels of each subtask information through traversal operation after determining the working hours of each subtask information. Based on the method, a user can automatically input the requirement information and the subtask information into the research and development flow management system by only uploading one requirement document in the using process, automatically split the task into the front-end development subtask and the rear-end development subtask and automatically calculate the working hours of each subtask information. Therefore, the tedious steps that the man-hour of manual calculation of a user is replaced, and information is input into the research and development flow management system one by one are replaced, and a large amount of human resources are saved.
An embodiment of the present application further provides a requirement processing apparatus 700, as shown in fig. 7, which can implement the requirement processing method described above, and the requirement processing apparatus includes: an acquisition unit 710, an information extraction unit 720, a task set division unit 730, and a man-hour calculation unit 740; the obtaining unit 710 is configured to obtain a requirement document; the information extraction unit 720 is configured to extract a plurality of requirement information and a plurality of subtask information from the requirement document, where the requirement information is used to represent the service requirement, and the subtask information is a research and development subtask used to represent and complete the service requirement; the task set dividing unit 730 is configured to divide the plurality of pieces of subtask information into a plurality of task sets, where the task sets correspond to the requirement information one to one; the man-hour calculation unit 740 is configured to determine the man-hours required to complete the subtask information according to the requirement information and the number of subtask information in the corresponding task set.
The requirement processing apparatus 700 of the embodiment of the present application is configured to execute the requirement processing method in the above embodiment, and a specific processing procedure of the requirement processing apparatus 700 is the same as the requirement processing method in the above embodiment, and is not described here again.
An embodiment of the present application further provides an electronic device 800, including:
at least one processor, and,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions for execution by the at least one processor to cause the at least one processor, when executing the instructions, to implement a method as in any one of the embodiments of the present application.
The hardware structure of the electronic device is described in detail below with reference to fig. 8. The electronic device includes: a processor 810, a memory 820, an input/output interface 830, a communication interface 840, and a bus 850.
The processor 810 may be implemented by a general Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute a relevant program to implement the technical solution provided in the embodiment of the present Application;
the Memory 820 may be implemented in the form of a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a Random Access Memory (RAM). The memory 820 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present disclosure is implemented by software or firmware, the relevant program codes are stored in the memory 820 and called by the processor 810 to execute the requirement processing method according to the embodiments of the present disclosure;
an input/output interface 830 for implementing information input and output;
the communication interface 840 is used for realizing communication interaction between the device and other devices, and can realize communication in a wired manner (for example, USB, network cable, etc.) or in a wireless manner (for example, mobile network, WIFI, bluetooth, etc.);
a bus 850 that transfers information between the various components of the device (e.g., the processor 810, the memory 820, the input/output interface 830, and the communication interface 840);
wherein processor 810, memory 820, input/output interface 830, and communication interface 840 are communicatively coupled to each other within the device via bus 850.
The embodiment of the present application further provides a storage medium, which is a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used to enable a computer to execute the requirement processing method of the embodiment of the present application.
The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The embodiments described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided in the embodiments of the present application, and it is obvious to those skilled in the art that the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems with the evolution of technologies and the emergence of new application scenarios.
It will be understood by those skilled in the art that the embodiments shown in fig. 1 to 8 do not constitute a limitation of the embodiments of the present application, and may include more or less steps than those shown, or some steps may be combined, or different steps may be included.
The above-described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
One of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.
The terms "first," "second," "third," "fourth," and the like in the description of the application and the above-described figures, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is merely a logical division, and the actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not operated. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes multiple instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing programs, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and the scope of the claims of the embodiments of the present application is not limited thereto. Any modifications, equivalents and improvements that may occur to those skilled in the art without departing from the scope and spirit of the embodiments of the present application are intended to be within the scope of the claims of the embodiments of the present application.
Claims (10)
1. A method of demand handling, comprising:
acquiring a requirement document;
extracting a plurality of requirement information and a plurality of subtask information from the requirement document, wherein the requirement information is used for representing service requirements, and the subtask information is used for representing research and development subtasks for completing the service requirements;
dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the requirement information one to one;
and determining the working hours required for completing the subtask information according to the quantity of the subtask information in the corresponding task set and the requirement information.
2. The method of claim 1, wherein extracting the plurality of requirement information and the plurality of subtask information from the requirement document comprises:
extracting a plurality of requirement information from the requirement document according to a preset first characteristic identifier, wherein the first characteristic identifier is used for indicating the requirement information;
and extracting a plurality of subtask information from the requirement document according to a preset second feature identifier, wherein the second feature identifier is used for indicating the subtask information.
3. The method of claim 1, wherein the dividing the sub-task information into a plurality of task sets comprises:
extracting a characteristic identifier from the subtask information, wherein the characteristic identifier is used for indicating a corresponding relation between the subtask information and the requirement information;
dividing at least one piece of subtask information corresponding to the same requirement information into the same task set according to the characteristic identification so as to obtain a plurality of task sets.
4. The method according to claim 1, wherein after said dividing the sub-task information into task sets, further comprising:
under the condition that the requirement information is detected to comprise a preset task splitting identifier, copying each subtask information in the task set corresponding to the requirement information to obtain a plurality of second subtask information;
and dividing a plurality of second subtask information and the subtask information into the same task set.
5. The method of claim 1, wherein the demand information includes a preset workload and the subtask information includes a man-hour tag.
6. The method of claim 5, wherein determining the man-hours required to complete the subtask information according to the quantity of the subtask information in each of the requirement information and the corresponding task set comprises:
extracting a preset workload of a demand from the demand information;
and determining the working hours required for completing the subtask information according to the ratio of the preset workload to the number of the subtask information in the corresponding task set.
7. The method of claim 5, further comprising, after determining the man-hours required to complete the subtask information according to each of the requirement information and the number of the subtask information in the corresponding task set,:
traversing all the subtask information in the task set;
and updating the man-hour label of each subtask information according to the man-hour of the subtask information.
8. A demand processing apparatus, characterized in that the apparatus comprises:
an acquisition unit configured to acquire a demand document;
the information extraction unit is used for extracting a plurality of pieces of requirement information and a plurality of pieces of subtask information from the requirement document, wherein the requirement information is used for representing business requirements, and the subtask information is used for representing research and development subtasks for completing the business requirements;
the task set dividing unit is used for dividing the subtask information into a plurality of task sets, wherein the task sets correspond to the requirement information one to one;
and the man-hour calculating unit is used for determining the man-hours required for completing the subtask information according to the requirement information and the number of the subtask information in the corresponding task set.
9. An electronic device comprising a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for implementing a connection communication between the processor and the memory, the program implementing the demand handling method according to any one of claims 1 to 7 when executed by the processor.
10. A computer-readable storage medium for computer-readable storage, characterized in that the computer-readable storage medium stores one or more programs which are executable by one or more processors to implement the demand processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211150193.XA CN115454382A (en) | 2022-09-21 | 2022-09-21 | Demand processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211150193.XA CN115454382A (en) | 2022-09-21 | 2022-09-21 | Demand processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115454382A true CN115454382A (en) | 2022-12-09 |
Family
ID=84305175
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211150193.XA Pending CN115454382A (en) | 2022-09-21 | 2022-09-21 | Demand processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115454382A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117389514A (en) * | 2023-10-11 | 2024-01-12 | 国网上海能源互联网研究院有限公司 | Method, device and system for classifying micro-application development requirements of fusion terminal |
-
2022
- 2022-09-21 CN CN202211150193.XA patent/CN115454382A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117389514A (en) * | 2023-10-11 | 2024-01-12 | 国网上海能源互联网研究院有限公司 | Method, device and system for classifying micro-application development requirements of fusion terminal |
| CN117389514B (en) * | 2023-10-11 | 2024-04-02 | 国网上海能源互联网研究院有限公司 | Method, device and system for classifying micro-application development requirements of fusion terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10162610B2 (en) | Method and apparatus for migration of application source code | |
| US10705943B2 (en) | Automating identification of test cases for library suggestion models | |
| EP3433732B1 (en) | Converting visual diagrams into code | |
| CN110688307B (en) | JavaScript code detection method, device, equipment and storage medium | |
| CN109710528B (en) | Test script generation method, device, equipment and medium | |
| CN111552665A (en) | Method, device, equipment and medium for converting label information format | |
| CN104111852A (en) | Web application automated testing system and testing method based on data drive | |
| CN113901169A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN115438740A (en) | Multi-source data convergence and fusion method and system | |
| CN113918460A (en) | Page testing method, device, equipment and medium | |
| Bayer et al. | Design and development of a web-based EPANET model catalogue and execution environment | |
| CN115454382A (en) | Demand processing method and device, electronic equipment and storage medium | |
| Rocha Silva et al. | Ensuring the consistency between user requirements and graphical user interfaces: A behavior-based automated approach | |
| CN110928535B (en) | Derived variable deployment method, device, equipment and readable storage medium | |
| CN117891447A (en) | Enterprise management software development method, device, equipment and medium | |
| CN113901022B (en) | Method, device, equipment and storage medium for establishing business and data relationship model | |
| KR101632951B1 (en) | Computer readable medium recording program for converting to online learning data and method of converting to online learning data | |
| CN112667874A (en) | Webpage data extraction method and device, electronic equipment and storage medium | |
| CN111221610A (en) | Page element acquisition method and device | |
| Yu-Wei | R for data science cookbook | |
| CN113495753B (en) | Method and device for acquiring label of item, electronic equipment and storage medium | |
| CN118502773B (en) | A method and device for improving the real-time response performance of a cloud management platform | |
| CN110618809B (en) | Front-end webpage input constraint extraction method and device | |
| CN117608719A (en) | Page element searching method and device, electronic equipment and medium | |
| Gambo et al. | Mining Requirements and Design Documents in Software Repositories Using Natural Language Processing and Machine Learning Approaches |
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 |