CN116501295A - Vectorization demand analysis system and method in software development stage - Google Patents
Vectorization demand analysis system and method in software development stage Download PDFInfo
- Publication number
- CN116501295A CN116501295A CN202310766839.5A CN202310766839A CN116501295A CN 116501295 A CN116501295 A CN 116501295A CN 202310766839 A CN202310766839 A CN 202310766839A CN 116501295 A CN116501295 A CN 116501295A
- Authority
- CN
- China
- Prior art keywords
- software
- software development
- class
- development
- points
- 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
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000004458 analytical method Methods 0.000 title claims abstract description 36
- 238000005516 engineering process Methods 0.000 claims abstract description 5
- 238000004806 packaging method and process Methods 0.000 claims abstract description 5
- 230000008569 process Effects 0.000 claims description 24
- 238000013461 design Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 8
- 238000005538 encapsulation Methods 0.000 claims description 7
- 230000009471 action Effects 0.000 claims description 6
- 238000004891 communication Methods 0.000 description 17
- 230000005540 biological transmission Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012827 research and development Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001680 brushing effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000002844 melting Methods 0.000 description 1
- 230000008018 melting Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
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
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/279—Recognition of textual entities
- G06F40/284—Lexical analysis, e.g. tokenisation or collocates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/279—Recognition of textual entities
- G06F40/289—Phrasal analysis, e.g. finite state techniques or chunking
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a system and a method for analyzing vectorization requirements in a software development stage, wherein the system comprises the following steps: part of speech analysis unit, keyword confirm unit and variable point confirm unit; the invention provides a set of vectorization demand analysis method by finding the name shape, asking IPO and grasping the easy-to-change point; determining the class, attribute, method and condition of the application program by finding the dynamic name; confirming the service data flow condition of the application program by asking IPO; through grabbing the easy variable points, the scalability, maintainability and testability of the application program are improved by utilizing packaging, abstract and polymorphic technologies and combining a single function principle, an open and closed principle, relying on an inversion principle and the like.
Description
Technical Field
The invention belongs to the technical field of software engineering, and particularly relates to a system and a method for analyzing vectorization requirements in a software development stage.
Background
Along with the rapid development of informatization progress in China, more and more people enter the IT industry, and the background and quality of the people are uneven. Some are non-computer and software specialized, some are on duty after training in training institutions for several months, some are only concerned with developing specific functions, and most people lack clear and systematic comprehensive demand analysis consciousness.
The software development cycle generally comprises demand analysis, software design, coding implementation, software testing and operation maintenance, and the demand analysis is a source of a research and development stage and is also a main line of research and development work, and objective, effective and accurate analysis of the demand directly influences the usability, the suitability, the expansibility and the maintainability of an application program.
In the existing practical development work, research and development personnel generally lack a clear software demand analysis thought method, are insensitive to easy-to-expand points, and have poor capacity of coping with demand change in the later period, often are function-oriented development, and do not consider maintainability, testability and reusability of application programs.
Disclosure of Invention
Aiming at the defects in the prior art, the vectorization demand analysis system and the vectorization demand analysis method for the software development stage solve the problems that the existing software development demand analysis stage is insensitive to an easily-expanded point, so that the subsequent development software has poor adaptability to demand change, and maintainability, testability and reusability of an application program are not considered.
In order to achieve the aim of the invention, the invention adopts the following technical scheme: a software development stage vectorized demand analysis system comprising:
part of speech analysis unit: analyzing the service demand description and classifying the parts of speech of the descriptive words; the parts of speech includes nouns, verbs and adjectives; the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
keyword determination unit: determining software research and development keywords according to the service data flow condition of the software program; the keywords comprise data input objects, data input contents, data processing modes, data output contents and data output objects;
a variable point determination unit: and determining the variable points of the service demands based on the descriptors of adjective classes, and converting the variable points into the extensible points in the software development process.
Further, the elements of the service requirement description at least comprise service roles, service scenes, requirement descriptions and acceptance criteria.
Further, the extensible points converted by the variable point determining unit are presented in the mode of interfaces, abstract classes or design modes in the software development process.
A software development stage vectorization demand analysis method comprises the following steps:
s1, analyzing service demand description, and determining nouns, verbs and adjectives in descriptive words;
the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
s2, determining software research and development keywords according to service data flow conditions of the software program;
s3, determining the easy variable point of the service requirement according to adjective class descriptors, and converting the easy variable point into an easy expansion point in the process of software research and development;
s4, carrying out software research and development according to the determined class, attribute, method and condition, software research and development keywords and easy expansion points, and realizing vectorization demand analysis;
the keywords comprise data input objects, data input contents, data processing modes and data output objects.
Further, in the step S1, the determined nouns are reflected in the software development process with object-oriented encapsulation characteristics, and correspond to entities, classes or attributes in the software development program;
the determined verbs correspond to specific functions in the software development program based on the single function principle;
the adjective is determined as an extensible description of nouns or verbs.
Further, the easy variable points are implementation elements of nouns or verbs corresponding to adjectives in software development, and each implementation element corresponds to one easy expansion point.
Further, in the step S3, the extensible point is converted into a corresponding interface or abstract class according to the open-closed principle, the single function principle and the dependency inversion principle by using the object-oriented encapsulation, polymorphism and abstraction technology in the software development process, and the software development is performed by adopting a corresponding design mode.
Further, the extensible points with the same attribute are converted into corresponding abstract classes in the process of software development, and the extensible points with different attributes are converted into corresponding interfaces in the process of software development.
Further, for a single easy-to-expand point, a design mode of a strategy mode is adopted for software research and development; and for different points of easy expansion, adopting a design mode of combining a constructor mode and a factory mode to carry out software development.
The beneficial effects of the invention are as follows:
(1) The invention provides a set of vectorization demand analysis method by finding the name shape, asking IPO and grasping the easy-to-change point; determining the class, attribute, method and condition of the application program by finding the dynamic name; confirming the service data flow condition of the application program by asking IPO; through grabbing the easy variable points, the scalability, maintainability and testability of the application program are improved by utilizing packaging, abstract and polymorphic technologies and combining a single function principle, an open and closed principle, relying on an inversion principle and the like.
(2) The core value of the IT industry is standardized by an extensible business scene, namely, the core value of the IT industry=standardization+business scene+extensible; the invention standardizes the demand analysis process, analyzes the service scene, and realizes expandability by determining the variable points.
Drawings
Fig. 1 is a flowchart of a software development stage vectorized demand analysis method provided by the present invention.
Fig. 2 is a schematic diagram of a multi-login policy mode according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention is provided to facilitate understanding of the present invention by those skilled in the art, but it should be understood that the present invention is not limited to the scope of the embodiments, and all the inventions which make use of the inventive concept are protected by the spirit and scope of the present invention as defined and defined in the appended claims to those skilled in the art.
Example 1:
the embodiment of the invention provides a software development stage vectorization demand analysis system, which comprises the following components:
part of speech analysis unit: analyzing the service demand description and classifying the parts of speech of the descriptive words; the parts of speech includes nouns, verbs and adjectives; the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
keyword determination unit: determining software research and development keywords according to the service data flow condition of the software program; the keywords comprise data input objects, data input contents, data processing modes, data output contents and data output objects;
a variable point determination unit: and determining the variable points of the service demands based on the descriptors of adjective classes, and converting the variable points into the extensible points in the software development process.
The elements of the service requirement description in the embodiment of the invention at least comprise service roles, service scenes, requirement description and acceptance criteria.
In the embodiment of the invention, the extensible points converted by the variable point determining unit are presented in the form of interfaces, abstract classes or design modes in the process of software development.
In this embodiment, part-of-speech analysis may be performed after the business requirement description is formed based on a technical protocol or a requirement specification.
In this embodiment, for the service data flow situation, the first party, the product manager, the project manager, etc. may be queried, and further the keywords of the software development include determining the data input object, the data input content, the data output content and the data output object, and determining the data processing mode based on the software development expertise.
In the embodiment, the determined extensible points are realized by adopting an open closed principle, a single function principle and a dependence inversion principle and adopting a strategy design mode; based on the mode, software research and development is performed, and the usability, expandability, maintainability and testability of the application program are improved.
Wherein, the open-close principle refers to open to modification closure and expansion to improve maintainability and reusability; the single function principle means that there should be and only one reason for a class or method to cause its change to improve scalability, maintainability and testability; the dependency inversion principle means that the high-level class should not depend on the low-level class, nor should the low-level class depend on the high-level class, and they should all depend on abstraction to improve maintainability, scalability and testability of the software program.
Example 2:
the embodiment of the invention provides a vectorization demand analysis method corresponding to the vectorization demand analysis system based on the software development stage in the embodiment 1, as shown in fig. 1, comprising the following steps:
s1, analyzing service demand description, and determining nouns, verbs and adjectives in descriptive words;
the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
s2, determining software research and development keywords according to service data flow conditions of the software program;
s3, determining the easy variable point of the service requirement according to adjective class descriptors, and converting the easy variable point into an easy expansion point in the process of software research and development;
s4, carrying out software research and development according to the determined class, attribute, method and condition, software research and development keywords and easy expansion points, and realizing vectorization demand analysis;
the keywords comprise data input objects, data input contents, data processing modes and data output objects.
In step S1 of the embodiment of the present invention, the determined nouns are reflected in the software development process with object-oriented encapsulation characteristics, corresponding to entities, classes or attributes in the software development program; the determined verbs correspond to specific functions in the software development program based on the single function principle; the adjective is determined as an extensible description of nouns or verbs.
In step S2 of the embodiment of the present invention, the service data flow condition is determined by asking the IPO, so as to determine the software development keyword, where IPO is Input, process and Output correspond to who inputs and what the input content is, how to perform data processing, and who outputs and what the Output content is, and specifically, the IPO and Output content may be obtained by asking the first party, the product manager, the project manager, and the like.
In step S3 of the embodiment of the present invention, the easy variable point is an implementation element of a noun or a verb corresponding to an adjective during software development, and each implementation element corresponds to an easy expansion point.
In step S3 of the embodiment of the present invention, in the process of software development, the easily-extensible point is converted into a corresponding interface or abstract class according to the open-closed principle, the single function principle and the dependency inversion principle by using the object-oriented encapsulation, polymorphism and abstraction technology, and software development is performed by adopting a corresponding design mode.
In this embodiment, the extensible points with the same attribute are converted into corresponding abstract classes in the process of software development, and the extensible points with different attributes are converted into corresponding interfaces in the process of software development.
In this embodiment, for a single point easy to expand, a design mode of a policy mode is adopted to perform software development; and for different points of easy expansion, adopting a design mode of combining a constructor mode and a factory mode to carry out software development.
Example 3:
the present embodiment gives a specific example of the easy-to-expand point analysis performed in the demand analysis method in embodiment 2:
in this embodiment, it is assumed that the service requirements in the real service scenario are described as follows:
service roles: and (5) operating and maintaining personnel.
Business scenario: the operation and maintenance personnel need to access various types of equipment of different manufacturers into the existing system.
Business requirement description: and interfacing different equipment interfaces of different manufacturers, and sending the received equipment information to the front end for UI display.
Acceptance criteria: the front end can normally display the state information of the equipment.
In the above description of service requirements, access of different devices is related to device communication, and three factors including the type of communication protocol, the format of communication content carrier and the type of transmission information need to be considered in relation to communication; aiming at different equipment of different manufacturers described in the above requirements, three kinds of elements can be easily obtained, wherein the three kinds of elements are all the easy-to-change points of the requirements, such as the types of communication protocols including network ports, serial ports and optical ports; the format of the communication content carrier comprises JSON, XML and character strings; the types of transmitted information include control classes, status and data classes.
The traditional function development-oriented mode is to design and process a communication protocol, a communication content carrier and a transmission information type in an entity class aiming at each type of equipment, so that the program coupling degree is high, and the flexibility and the expansibility are poor; for example, a communication content carrier needs to be added to be in a data frame format, and the entity class needs to be modified, so that the open-closed principle is violated, and the stability of a program is easily affected.
For the above case, the communication protocol, the communication content carrier, the transmission information type may be packaged as separate interfaces or abstract classes, respectively, based on a single functional principle (one class or interface has and only one reason to influence its change). Whether the interface or the abstract class is adopted or not is determined by a method of sharing the attribute and the shared implementation, if so, the abstract class is selected, and otherwise, the interface is selected. Because the design of the interface or abstract class is adopted, the dependency inversion principle (namely, the high class does not depend on the low class, the low class does not depend on the high class, and both depend on and abstract) is satisfied, and the coupling of the application program is reduced; and the open and closed principle is satisfied, if the type of the communication content carrier is needed to be newly added, the implementation interface is only required to be expanded, and the original application program is not influenced.
In combination with the requirement, the analysis of the variable point requirement of the communication protocol alone can know that the communication is realized by different strategies, and a strategy mode in a design mode can be adopted; and so on, the communication content carrier and the transmission information type can be realized by adopting a strategy mode. The essence of the whole equipment access process is the combination of communication protocol, communication content carrier and transmission information type, and the construction of the equipment access link can be realized by adopting a constructor mode and a factory mode.
The process for determining the easy-to-expand point is based on a single function, relies on inversion and open sealing principles, combines the characteristics of an object-oriented packaging characteristic, the characteristics of an interface and an abstract class and a design mode so as to improve the flexibility and the expandability of an application program to the greatest extent, and ensures the integrity of the easy-to-expand point through flexible expansion.
Example 4:
the present embodiment gives a specific example of the demand analysis method in embodiment 2:
in this embodiment, the service requirements of the real service scenario are described as follows:
service roles: user' s
Business scenario: the user may log into the system in different ways.
Business requirement description: the user can log in the system by inputting a user name, a password, a mobile phone number, a verification code and the like.
Acceptance criteria: the user logs into the system normally or gives friendly abnormal prompts.
The specific analytical flow using the vectorization requirement method of example 2 is shown in table 1 below:
table 1: vectorized demand analysis flow
In order to improve the expandability of the developed application program and further ensure the integrity of the variable points, the requirement design in the embodiment adopts a multi-login mode strategy mode which defines a group of login modes, packages each login mode and enables the login modes to be mutually converted. The core idea of the multi-sign-on policy model is an object-oriented encapsulation, abstraction and polymorphism mechanism, the class diagram of which is shown in fig. 2.
In fig. 2, the multi-login policy mode role is illustrated in table 2 below:
table 2: multi-login mode policy mode role specification
| English of entity role | Entity role Chinese | Description of the invention |
| Client | Client terminal | Clients that can log in through different login modes. |
| EntryStrategyCo ntext | Strategically in a login mode The following objects | The login mode policy context object plays a role in packaging up and down, and shields the high-level module from directly using the policy algorithmAccess, encapsulation of possible variants And (5) melting. Reducing the coupling between policy users and policies. |
| IEntryStrategy | Login policy access Mouth(s) | An abstraction of the login style, typically an interface, defines the methods and attributes that each specific login style must possess. |
| UserInfoEntrySt rategy | User name password login Strategy | Login is performed using a username password. |
| PhoneInfoEntryS trategy | Mobile phone number verification code login Recording strategy | And logging in by using the mobile phone number verification code. |
| OtherEntryStrat egy | Other login methods Slightly omitted | The other login mode strategies are reserved extensible classes of the storage terminals, are abstract descriptions of other storage terminals, and can be increased or decreased according to actual conditions. For example Can comprise two-dimension code registration, fingerprint registration, face brushing registration and the like |
In the embodiment of the invention, in order to exert the function of the method in software research and development to the maximum extent, users need to have certain knowledge, experience and business application accumulation in terms of object-oriented, design principle and design mode.
The principles and embodiments of the present invention have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Those of ordinary skill in the art will recognize that the embodiments described herein are for the purpose of aiding the reader in understanding the principles of the present invention and should be understood that the scope of the invention is not limited to such specific statements and embodiments. Those of ordinary skill in the art can make various other specific modifications and combinations from the teachings of the present disclosure without departing from the spirit thereof, and such modifications and combinations remain within the scope of the present disclosure.
Claims (9)
1. A software development stage vectorized demand analysis system, comprising:
part of speech analysis unit: analyzing the service demand description and classifying the parts of speech of the descriptive words; the parts of speech includes nouns, verbs and adjectives; the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
keyword determination unit: determining software research and development keywords according to the service data flow condition of the software program; the keywords comprise data input objects, data input contents, data processing modes, data output contents and data output objects;
a variable point determination unit: and determining the variable points of the service demands based on the descriptors of adjective classes, and converting the variable points into the extensible points in the software development process.
2. The software development stage vectoring need analysis system of claim 1 wherein the elements of the business need description comprise at least business roles, business scenarios, need descriptions and acceptance criteria.
3. The system according to claim 1, wherein the extensible points converted by the variable point determining unit are presented in the form of interfaces, abstract classes or design patterns during the software development process.
4. A vectorized demand analysis method based on the software development stage vectorized demand analysis system of any one of claims 1 to 3, comprising the steps of:
s1, analyzing service demand description, and determining nouns, verbs and adjectives in descriptive words;
the method comprises the steps of determining the class, attribute, method and condition of a software program by using descriptors of the name word class and the action word class;
s2, determining software research and development keywords according to service data flow conditions of the software program;
s3, determining the easy variable point of the service requirement according to adjective class descriptors, and converting the easy variable point into an easy expansion point in the process of software research and development;
s4, carrying out software research and development according to the determined class, attribute, method and condition, software research and development keywords and easy expansion points, and realizing vectorization demand analysis;
the keywords comprise data input objects, data input contents, data processing modes and data output objects.
5. The method according to claim 4, wherein in the step S1, the determined nouns are represented in an object-oriented packaging characteristic during the software development process, and correspond to entities, classes or attributes in the software development program;
the determined verbs correspond to specific functions in the software development program based on the single function principle;
the adjective is determined as an extensible description of nouns or verbs.
6. The method of claim 5, wherein the easy variable points are implementation elements of nouns or verbs corresponding to adjectives during software development, and each implementation element corresponds to an easy expansion point.
7. The method according to claim 5, wherein in step S3, the extensible point is converted into a corresponding interface or abstract class according to an open-closed principle, a single function principle and a dependency inversion principle by using an object-oriented encapsulation, polymorphism and abstraction technology in a software development process, and performs software development by adopting a corresponding design mode.
8. The method of claim 7, wherein points of easy expansion having the same attribute are converted into corresponding abstract classes during software development, and points of easy expansion having different attributes are converted into corresponding interfaces during software development.
9. The method of claim 7, wherein for a single point of easy expansion, software development is performed using a design pattern of a policy pattern; and for different points of easy expansion, adopting a design mode of combining a constructor mode and a factory mode to carry out software development.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310766839.5A CN116501295A (en) | 2023-06-27 | 2023-06-27 | Vectorization demand analysis system and method in software development stage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310766839.5A CN116501295A (en) | 2023-06-27 | 2023-06-27 | Vectorization demand analysis system and method in software development stage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116501295A true CN116501295A (en) | 2023-07-28 |
Family
ID=87323478
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310766839.5A Pending CN116501295A (en) | 2023-06-27 | 2023-06-27 | Vectorization demand analysis system and method in software development stage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116501295A (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020120540A1 (en) * | 2000-12-01 | 2002-08-29 | Michael Kende | System and method for automatic analysis of rate information |
| US20040030421A1 (en) * | 2000-05-24 | 2004-02-12 | Paul Haley | System for interprise knowledge management and automation |
| KR20050013025A (en) * | 2003-07-26 | 2005-02-02 | 박현준 | Knowledge information and search service based on sort of a part of speech of language |
| US20060130002A1 (en) * | 2002-09-09 | 2006-06-15 | Sadahiro Hirayama | Requirement defining method, method for developing software, and method for changing requirement word, and newly defining method |
| CN101539907A (en) * | 2008-03-19 | 2009-09-23 | 日电（中国）有限公司 | Part-of-speech tagging model training device and part-of-speech tagging system and method thereof |
| CN103793373A (en) * | 2014-01-23 | 2014-05-14 | 福建工程学院 | Tracking relation recovery method based on syntax |
| CN109117363A (en) * | 2018-06-28 | 2019-01-01 | 腾讯科技（深圳）有限公司 | A kind of method for generating test case, device and server |
| CN111309288A (en) * | 2020-01-20 | 2020-06-19 | 北京国舜科技股份有限公司 | Analysis method and device of software requirement specification file suitable for banking business |
| CN111831920A (en) * | 2020-07-30 | 2020-10-27 | 平安普惠企业管理有限公司 | User demand analysis method and device, computer equipment and storage medium |
| CN112784598A (en) * | 2019-11-11 | 2021-05-11 | 北京京东尚科信息技术有限公司 | Method, device and equipment for generating thinking guide graph and storage medium |
| CN113111650A (en) * | 2021-04-16 | 2021-07-13 | 中国工商银行股份有限公司 | Text processing method, device, system and storage medium |
| CN114118086A (en) * | 2020-08-26 | 2022-03-01 | 复旦大学 | Association set extraction method based on airborne field-oriented element description template |
| CN114625340A (en) * | 2022-05-11 | 2022-06-14 | 深圳市商用管理软件有限公司 | Commercial software research and development method, device, equipment and medium based on demand analysis |
| US11379538B1 (en) * | 2016-05-19 | 2022-07-05 | Artemis Intelligence Llc | Systems and methods for automatically identifying unmet technical needs and/or technical problems |
-
2023
- 2023-06-27 CN CN202310766839.5A patent/CN116501295A/en active Pending
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040030421A1 (en) * | 2000-05-24 | 2004-02-12 | Paul Haley | System for interprise knowledge management and automation |
| US20020120540A1 (en) * | 2000-12-01 | 2002-08-29 | Michael Kende | System and method for automatic analysis of rate information |
| US20060130002A1 (en) * | 2002-09-09 | 2006-06-15 | Sadahiro Hirayama | Requirement defining method, method for developing software, and method for changing requirement word, and newly defining method |
| KR20050013025A (en) * | 2003-07-26 | 2005-02-02 | 박현준 | Knowledge information and search service based on sort of a part of speech of language |
| CN101539907A (en) * | 2008-03-19 | 2009-09-23 | 日电（中国）有限公司 | Part-of-speech tagging model training device and part-of-speech tagging system and method thereof |
| CN103793373A (en) * | 2014-01-23 | 2014-05-14 | 福建工程学院 | Tracking relation recovery method based on syntax |
| US11379538B1 (en) * | 2016-05-19 | 2022-07-05 | Artemis Intelligence Llc | Systems and methods for automatically identifying unmet technical needs and/or technical problems |
| CN109117363A (en) * | 2018-06-28 | 2019-01-01 | 腾讯科技（深圳）有限公司 | A kind of method for generating test case, device and server |
| CN112784598A (en) * | 2019-11-11 | 2021-05-11 | 北京京东尚科信息技术有限公司 | Method, device and equipment for generating thinking guide graph and storage medium |
| CN111309288A (en) * | 2020-01-20 | 2020-06-19 | 北京国舜科技股份有限公司 | Analysis method and device of software requirement specification file suitable for banking business |
| CN111831920A (en) * | 2020-07-30 | 2020-10-27 | 平安普惠企业管理有限公司 | User demand analysis method and device, computer equipment and storage medium |
| CN114118086A (en) * | 2020-08-26 | 2022-03-01 | 复旦大学 | Association set extraction method based on airborne field-oriented element description template |
| CN113111650A (en) * | 2021-04-16 | 2021-07-13 | 中国工商银行股份有限公司 | Text processing method, device, system and storage medium |
| CN114625340A (en) * | 2022-05-11 | 2022-06-14 | 深圳市商用管理软件有限公司 | Commercial software research and development method, device, equipment and medium based on demand analysis |
Non-Patent Citations (6)
| Title |
|---|
| CKXGZXA: "第三章 需求分析", pages 1, Retrieved from the Internet <URL:《https://blog.csdn.net/CKXGZXA/article/details/117021691#WarnierIPO_180》> * |
| S. ARASH OSTADZADEH: "Profile-guided application partitioning for heterogeneous reconfigurable platforms", 《THE 16TH CSI INTERNATIONAL SYMPOSIUM ON COMPUTER ARCHITECTURE AND DIGITAL SYSTEMS (CADS 2012)》, pages 1 - 7 * |
| 三太子敖丙: "年初敖丙天猫面试真题：如果设计一个数据库？我人傻了", pages 1 - 10, Retrieved from the Internet <URL:《https://my.oschina.net/javaFamily/blog/4795561》> * |
| 肖人彬: "数据驱动的产品创新设计研究", 《机械设计》, pages 1 - 5 * |
| 胡文生: "基于灰色聚类算法的需求分析", 《计算机科学》, pages 471 - 475 * |
| 胡文生;杨剑锋;赵明;: "基于灰色聚类算法的需求分析", 计算机科学, no. 1, pages 1 - 9 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022160707A1 (en) | Human-machine interaction method and apparatus combined with rpa and ai, and storage medium and electronic device | |
| US11048682B2 (en) | Custom lightning connect adapter for google sheets web-based spreadsheet program | |
| US7567968B2 (en) | Integration of a non-relational query language with a relational data store | |
| CN109858286B (en) | Security policy management system for trusted computing platform | |
| US11348597B2 (en) | Intent-based network validation | |
| EP0782080A1 (en) | System and method for propagating revisions through a communications network | |
| CN111913734A (en) | On-line development platform based on micro-service technology system | |
| CN115640045B (en) | Low-code development platform based on domain-driven design and business system creation method | |
| US20060225026A1 (en) | User-defined type consistency checker | |
| US8392298B2 (en) | Invoice adjustment data object for a common data object format | |
| CN112068843A (en) | Modeling method for business data in application software | |
| US7503063B1 (en) | Container level access control mechanism | |
| JP2022189805A (en) | Computer-implemented method, information processing system and computer program (performance monitoring in anomaly detection domain for it environment) | |
| Wang et al. | Do as you say: Consistency detection of data practice in program code and privacy policy in mini-app | |
| CN116501295A (en) | Vectorization demand analysis system and method in software development stage | |
| CN112835784A (en) | Method for evaluating and optimizing interoperation capacity of complex giant system | |
| WO2023221644A1 (en) | Aiot device reuse modeling method based on cloud-edge collaboration system | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN108718339A (en) | Data processing method, device and server | |
| Nawaz et al. | Using PVS for modeling and verification of probabilistic connectors | |
| CN112764722A (en) | AADL-based system vulnerability model design method | |
| CN112051990A (en) | Network management northbound interface model adaptation method and system | |
| CN115220811A (en) | Third party interface docking method, system and medium applied to government hall | |
| CN118536105A (en) | Block chain intelligent contract verification method and system based on formalization method | |
| CN114861189A (en) | Intelligent screening method, system, equipment and computer-readable storage medium for data security loophole |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230728 |