CN102214091A - Method and system for positioning required change influence range during software development - Google Patents
Method and system for positioning required change influence range during software development Download PDFInfo
- Publication number
- CN102214091A CN102214091A CN2010101632157A CN201010163215A CN102214091A CN 102214091 A CN102214091 A CN 102214091A CN 2010101632157 A CN2010101632157 A CN 2010101632157A CN 201010163215 A CN201010163215 A CN 201010163215A CN 102214091 A CN102214091 A CN 102214091A
- Authority
- CN
- China
- Prior art keywords
- document
- key word
- entity
- code
- entities
- 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
Images
Abstract
The invention discloses a method and a system for positioning a required change influence range during software development. The method comprises the following steps of: inputting at least one required change request, at least one software document and at least one code file set corresponding to the software document; positioning influenced entities in the software document and the code file set according to the required change request; and outputting the influenced entities. By the invention, the required change request can automatically response to and track a code level, so the response of a required change can cover the complete software development flow.
Description
Technical field
The present invention relates to computer realm, relate in particular to the method and system of demand change coverage in a kind of positioning software exploitation.
Background technology
In the collaboration software exploitation, various team and teamworker participate in writing documents such as user's request, design, and realize systemic-function with the form of code.On the other hand, in order to tackle the change in document or the code or the problem of existence, the teamworker need understand the particular location of required modification in document or the code.Basically, these positions need be summarized as certain conclusion, thereby provide reference for the modification of follow-up document or code.
For these reasons, in the collaboration software exploitation, often there are strong needs to locate the change scope that change may influence.In a single day particularly change is arranged when requirement documents takes place, it is obvious further that this needs become.Because the pairing subordinate's document of demand has many types, design, code or the like all needs the correspondence of making amendment.In this case, one can location requirement the instrument of change coverage, will improve change reply efficient greatly.
Current, IBM DOORS is the demand management and the requirement Change Management instrument of a maturation.It attempts to improve the efficient and the quality of requirement Change Management in the software development process.In order to realize this target, DOORS is converted into the achievement item with documents such as demands, sets up the association between the achievement item of different document simultaneously.Based on these achievement items and corresponding related, the user can trace into the change of required correspondence, simultaneously corresponding change is made amendment and edits.In addition, number of patent application is the Japanese patent application of JP2008204333, disclose and attempted the manual mapping relations of setting up between the document chapters and sections, in case when the change of certain demand took place, system can create based on the reply task that is affected chapters and sections automatically and distribute to relevant teamworker's technical scheme.
But there are two deficiencies in technique scheme.At first, the association between the document chapters and sections is discerned by the people.When the quantity of document increases or upgrades frequent the time, the incidence relation between the document is difficult to upgrade in time synchronously.In addition, this manual incidence relation of safeguarding also needs to spend suitable manpower, particularly when Doctype is various or baroque.The second, source code is got up by management with related being difficult between other documents.Because the quantity of code is generally all huger, manual when setting up related between code and the document when attempting, be difficult to accomplish accurately and comprehensively cover all codes.In this case, design waits getting in touch between document and the code to be interrupted.Like this, the code level can not be tackled and be traced into to demand change request.This limitation has hindered the change of realization demand and has tackled the target that will cover the software development entire flow.
Summary of the invention
In view of this, the object of the present invention is to provide the method and system of demand change coverage in a kind of positioning software exploitation, make demand change request can tackle and trace into the code level automatically, thereby make the reply of demand change can cover the software development entire flow, and, before carrying out, change carries out cost estimating at demand change request.
According to an aspect of the present invention, provide the method for demand change coverage in a kind of positioning software exploitation, having comprised:
Importing at least one demand change request, at least one software document and code file that at least one is corresponding with described software document gathers;
According to described demand change request, in described software document and the set of described code file, locate affected entities;
Export described affected entities.
According to a feature of the present invention,
The location affected entities comprises in described software document and the set of described code file:
From described software document, extract document information, and from described code file set, extract code characteristic information;
Determine a plurality of entities and a plurality of key word according to described document information and code characteristic information;
Determine the degree of association of described a plurality of entities according at least one key word in described a plurality of key words;
The degree of association according to described a plurality of entities is created index file;
According to described index file, in described a plurality of entities, locate affected entities.
According to another feature of the present invention, described method further comprises:
The described key word in the described software document discerned in the use corpus;
The described key word that comprises in the code recognition rule cognizance code of use based on type of code;
Obtain the incidence relation between the described key word, and form the key word contingency table;
Based on described key word contingency table, set up association and similarity between the described entity;
Create index file, to store association and the similarity between the described entity.
According to another feature of the present invention, described method further comprises:
Create dictionary;
Use described dictionary to discern described key word in the described software document; Wherein, when new key word occurring in the described software document, add described new key word to described dictionary;
The described key word that comprises in the code recognition rule cognizance code of use based on type of code;
Obtain the incidence relation between the described key word, and form the key word contingency table;
Based on described key word contingency table, set up association and similarity between the described entity;
Create index file, to store association and the similarity between the described entity.
According to another feature of the present invention, described method further comprises:
Set up the V-arrangement model, according to the described affected entities of described V-arrangement model orientation.
According to another feature of the present invention,
In described V-arrangement model, comprise sane level document and subordinate's document;
Key word according to coupling in described sane level document and subordinate's document calculates coupling mark and similarity, according to described coupling mark, determine to mate entity most, and, determine in the described affected entities except that described other described affected entities of mating most the entity according to described similarity.
According to another feature of the present invention, described method further comprises:
According to described coupling mark and described similarity, output shows described affected entities in a predefined manner.
According to another feature of the present invention,
Described entity comprises chapters and sections, the code file bag of software document.
According to another feature of the present invention,
Described code file comprises a plurality of code file bags;
Described code file bag comprises a plurality of code files.
According to another feature of the present invention,
Described document information comprises: Doctype, document format, document content;
Described code characteristic information comprises: code file name, type of code;
For software document, described key word is the key word in the document content;
For the code file set, described key word is the code file name.
According to another feature of the present invention, described method further comprises:
According to described affected entities, cost estimating is carried out in described demand change request according to predetermined sentence cost.
According to a further aspect in the invention, provide the system of demand change coverage in a kind of positioning software exploitation, having comprised:
Load module is used to import at least one demand change request, at least one software document and code file that at least one is corresponding with described software document and gathers;
The requirement Change Management module is used for locating affected entities according to described demand change request in described software document and the set of described code file;
Output module is used to export described affected entities.
According to a feature of the present invention, described requirement Change Management module comprises:
Information extraction modules is used for extracting document information from described software document, and extracts code characteristic information from described code file set;
Text analysis model is used for determining a plurality of entities and a plurality of key word according to described document information and code characteristic information;
Related identification module is used for determining according at least one key word of described a plurality of key words the degree of association of described a plurality of entities;
The index creation module is used for creating index file according to the degree of association of described a plurality of entities;
Locating module is used for according to described index file, locatees affected entities in described a plurality of entities.
According to another feature of the present invention, in described system,
Formation is used to store described software document;
Described requirement Change Management module is further used for obtaining the described software document stored and creates described index file according to described software document in described formation;
Scheduler is used for intermittently calling the described index creation module of described requirement Change Management module to create described index file.
According to another feature of the present invention,
Described locating module is further used for setting up the V-arrangement model, according to the described affected entities of described V-arrangement model orientation.
According to a feature of the present invention,
In described V-arrangement model, comprise sane level document and subordinate's document;
Described locating module, be further used in described sane level document and subordinate's document, calculating coupling mark and similarity according to the key word that mates, according to described coupling mark, determine to mate most entity, according to described similarity, determine in the described affected entities except that described other described affected entities of mating most the entity.
According to another feature of the present invention,
Described output module is used for according to described coupling mark and described similarity, and output shows described affected entities in a predefined manner.
According to another feature of the present invention, described system comprises:
The cost estimating module is used for according to described affected entities, according to predetermined sentence cost cost estimating is carried out in described demand change request.
The method and system of demand change coverage in the positioning software exploitation of the present invention, not only can discern the association between the document chapters and sections automatically, and related between managed source code and other documents quickly and easily, thereby improved the efficient and the accuracy rate of location requirement change coverage greatly, the reply of the change of realization demand preferably can cover the target of software development entire flow.In addition, at demand change request, before carrying out, change carries out cost estimating, not only can make the developer understand the needed cost of different demand change requests in advance, in a planned way revise the project timetable, and then more advantageously guarantee carrying out smoothly of software development, and can make the software development investor according to the cost of development of pre-estimating, different demand change requests are screened pointedly, when guaranteeing that software development is carried out smoothly, the cost of development of control reality better.
Description of drawings
Fig. 1 shows the formation of a software project document;
Fig. 2 shows the system architecture diagram of demand change coverage in the exploitation of positioning software in the embodiment of the invention;
Fig. 3 shows the structured flowchart of the computer system at the system place of demand change coverage in the exploitation of positioning software in the embodiment of the invention;
Fig. 4 shows the multithreading processing procedure of requirement Change Management module in the embodiment of the invention;
Fig. 5 is the method flow diagram of demand change coverage during positioning software is developed in the embodiment of the invention;
Fig. 6 shows the detailed process of keyword recognition among Fig. 5;
Fig. 7 A has described the treatment scheme of determining the key word in the document files in the embodiment of the invention in further detail;
Fig. 7 B has described the treatment scheme of determining the key word in the code file set in the embodiment of the invention in further detail;
Fig. 8 shows the concrete example of the entity that exists according to the rule extraction code among Fig. 7 B;
Fig. 9 shows the composition of demand entity in the embodiment of the invention;
Figure 10 shows the composition of design entity in the embodiment of the invention;
Figure 11 shows the composition of code entity in the embodiment of the invention;
Figure 12 shows the basic structure model of key word in the embodiment of the invention;
Figure 13 shows the structure of key word contingency table in the embodiment of the invention;
Figure 14 shows the detailed process that forms the entity associated table in the embodiment of the invention;
Figure 15 shows the basic structure model of entity in the embodiment of the invention;
Figure 16 shows in the embodiment of the invention calculation of similarity degree example between the entity;
Figure 17 shows the structure of entity associated table in the embodiment of the invention;
Figure 18 shows the interface junction composition of load module in the embodiment of the invention;
Figure 19 shows the detailed process that changes request location affected entities in the embodiment of the invention according to demand;
Figure 20 shows the V-arrangement model structure in the embodiment of the invention;
Figure 21 shows and judge whether affected details flow process of certain entity in the embodiment of the invention in the V-arrangement model;
Figure 22 shows in the embodiment of the invention entity key word contingency table that key word in each entity and demand change request uses in relatively;
Figure 23 shows the embodiment that changes request location affected entities in the embodiment of the invention according to demand;
Figure 24 shows and uses ordering and color to represent the output interface of affected entities in the embodiment of the invention;
Figure 25 shows the output interface that represents affected entities in the embodiment of the invention based on sensing figure;
Figure 26 shows the output interface that represents affected entities in the embodiment of the invention based on histogram;
Figure 27 shows the output interface that represents affected entities in the embodiment of the invention based on label figure;
Figure 28 shows user-defined dictionary structure in the embodiment of the invention;
Figure 29 shows and uses dictionary to carry out the detailed process of keyword recognition in the embodiment of the invention;
Figure 30 shows increases the artificial interaction flow of confirming step in system in the embodiment of the invention;
Figure 31 shows in the embodiment of the invention and carries out cost estimation approach flow process according to influenced scope;
Figure 32 shows the system architecture diagram of demand change coverage in the positioning software exploitation that comprises the cost estimating module in the embodiment of the invention.
Embodiment
Describe specific embodiments of the invention in detail below in conjunction with Figure of description.
With reference to figure 1, Fig. 1 shows the formation of a software project document.For a software project is project A, and it comprises two documents, requirement documents demand _ A101 and design documentation design _ A102.Demand _ A has set forth all statement of requirements items of certain project or system, and design _ A has set forth all functions design that launches around demand _ A.Simultaneously, also have much for realize designing _ A in the source code _ A103 of all designs.Demand _ A, design _ A and source code _ A are stored in the file server.If some functions of demand _ A need to upgrade, the corresponding chapters and sections of design _ A also need synchronous renewal.Simultaneously, the developer also needs to upgrade source code _ A.
Realize in the positioning software document by the entity of demand change influence by the present invention, thereby need the scope revised among positioning design _ A and the source code _ A.
With reference to figure 2, Fig. 2 shows the system architecture diagram of demand change coverage in the exploitation of positioning software in the embodiment of the invention, comprises among Fig. 2:
Requirement Change Management module 202 is used for the request of changing according to demand, locatees affected entities in software document and code file set;
Wherein, requirement Change Management module 202 comprises:
Locating module 2025 is used for according to index file, locatees affected entities in a plurality of entities.
Fig. 3 shows the structured flowchart of the computer system at the system place of demand change coverage in the exploitation of positioning software in the embodiment of the invention.According to the various aspects that the present invention relates to, requirement Change Management module 202 need be set up mutual with application server 307, file server 303 and database 308.Requirement Change Management module 202 need be structured on the operating system 306 simultaneously, by hardware resources such as operating system scheduling central processing unit 301, i/o controller 305, system storages 302, use network adapter 304 to connect distributed network 309 simultaneously, thereby set up communication with other computing machines.
With reference to figure 4, Fig. 4 shows the multithreading processing procedure of requirement Change Management module in the embodiment of the invention.After importing all software documents, a formation 401 is created to be used for the cache software document.Requirement Change Management module 202 is obtained the software document of buffer memory in formation 401.Scheduler 402 intermittently calls the index creation module 2024 of requirement Change Management module 202 to create index file.
Fig. 5 is the method flow diagram of demand change coverage during positioning software is developed in the embodiment of the invention, comprises that step is as follows:
Input demand change request, software document and the code file set (step 501) corresponding with software document;
From software document, extract document information, and from the code file set, extract code characteristic information (step 502);
Determine a plurality of entities and a plurality of key word (step 503) according to document information and code characteristic information;
Determine the degree of association (step 504) of a plurality of entities according at least one key word in a plurality of key words;
The degree of association according to a plurality of entities is created index file (step 505);
According to index file, in a plurality of entities, locate affected entities (step 506);
Output affected entities (step 507).
Fig. 6 has described the treatment scheme of definite key word in detail.Input Software document (step 601); Judge whether software document is text (step 602), if, enter step 604, otherwise, step 603 entered.In the present embodiment, demand _ A and design _ A are judged as text, and source code _ A is judged as non-document file, i.e. code file.Determine the key word (step 603) of code file.System uses 612 pairs of texts of corpus to carry out participle (step 604) earlier.System judges whether the word that participle obtains is noun (step 605), if the word that participle obtains is not a noun, system will return step 604 and proceed participle; If the word that participle obtains is a noun, system will judge whether this word exists (step 606) in corpus, if this word exists in corpus, system will be directly to the key word cluster (step 611) in document and the code; If this word does not exist in corpus, what this word will be sought by system exists frequency (step 607), and the size (step 608) of assessment frequency is to judge whether this word is key word (step 609), if not key word, returning step 604 in system continues text is carried out participle, if key word, then this key word is added corpus (step 610) and begin the key word in document and the code is carried out cluster (step 611).
Fig. 7 A has described the treatment scheme of the key word in definite document files in further detail.Wherein, input document (step 7A01) is sought file catalogue (step 7A02) from the document configuration information of input, and the All Files (step 7A03) under the file catalogue of location.Judge whether comprise code file (step 7A04) in the All Files under the file catalogue,, will carry out the key word (step 7A05 is corresponding to the step 603 among Fig. 6) of determining code file if comprise code file.If do not comprise code file, then further judge whether to exist more multifile (step 7A06), if there is no multifile more, then finish document and extract (step 7A07), if there is more multifile, with the file (step 7A08) that loads in the multifile more, and read this document information (step 7A09).From fileinfo, determine the file layout (step 7A10) of this document.According to file layout, file is resolved, obtain the entity (step 7A11) in the document, for example,, then resolve the heading in the document if file layout is the word form, obtain the chapters and sections collection in the document; If file layout is the Excel form, then resolve the sheet in the document, obtain the sheet collection in the document; If file layout is the html form, then resolve the section in the document, obtain the section collection in the document.For other file layout, also can resolve by predefined resolution rules.Then, the entity in the document is joined (step 7A12) in the entity sets.
Fig. 7 B has described the treatment scheme of the key word in definite code file set in further detail.
In Fig. 7 B, after loading code collection (step 7B01), system can begin the form (step 7B02) of code analysis and load corresponding code analysis rule (step 7B03) according to the form of code.According to the code analysis rule, extract the entity (step 7B04) that exists in the code.Then, the key word (step 7B05) in the extraction entity.In the entity of higher level's document, seek key word (step 7B06), judge whether key word is present in certain entity (step 7B07) of higher level's document, if key word is present in certain entity of higher level's document, system will be to the key word cluster (step 7B08) in document and the code, otherwise, this key word will be joined corpus, and used (step 7B09) by the participle of next round and keyword recognition.
Suppose that source code _ A (103) is to use the Java language coding to realize.Fig. 8 is the extraction entity rule that example has been set forth step 7B04 with the resolution rules of Java.When the form that detects source code _ A when system is " .java ", load Java resolution rules (step 801), in code collection search all comprise the code packages of " .java ".Increase all code packages that comprise " .java " file to entity (step 803).Judge whether to exist more multiple entity (step 804), if there is more multiple entity, then load at least one entity (step 805), and obtain the filename (step 806) of all " .java " files in this entity and be associated with entity (step 807) as key word, return step 804, traveled through as sporocarp and to finish, do not had more multiple entity, system will begin the key word cluster (step 706) in document and the code.
Among this embodiment, the keyword recognition result of software document and code shows shown in Fig. 9-11.Among Fig. 9, entity _ demand is chapters and sections in the requirement documents, has comprised demand (Requirement), developer (Developer) and timetable 3 key words such as (Schedule).Among Figure 10, entity _ design is chapters and sections in the design documentation, has comprised demand change (Requirement Change), released version (Release) and timetable 3 key words such as (Schedule).Among Figure 11, entity _ code is wherein a part of source code, has comprised demand change (Requirement Change), and demand management (Requirement Management) is provided with quality (Design Quality) and other source code file.
With reference to Figure 12, the keyword structure 1201 in the index file comprises renewal/establishment/deletion time 1202, position 1203, associating key word 1204 and synonym key word 1205.Renewal/establishment/deletion time 1202 has been stored the corresponding operating time of this key word.Document or code entity that this key word exists have been stored in position 1202.Associating key word 1204 has been stored and related other key words of this key word, and this association is to set up by the clustering processing in the step 611.The set of keywords with this key word same meaning stored in synonym key word 1205, and this set of keywords also is to set up by the clustering processing of step 611.
In the present embodiment, the corpus technology is used the incidence relation that makes up between the key word, with reference to Figure 13.All key word associations are stored in form 1301.In form 1301, key word, corresponding target keywords and association type are all preserved in the mode of record.Target keywords represents that this key word is to be expanded by certain key word, for example, demand management (requirement management) is by demand (requirement) expansion of deriving, therefore, demand management is the target keywords of demand, and association type is to expand (EXTEND).When the association between the key word was more and more, more record will be added in the form 1301.
Entity associated table in the present embodiment is with reference to Figure 17.Among Figure 17, entity associated table 1701 attempts to calculate the similarity between the entity that all software documents comprise.In entity associated table 1701, because therefore entity and do not have the situation of similarity between himself, does not all have concrete numerical value in the cell on diagonal positions.In addition, because the value between the entity does not have directivity, therefore, the value of cell 1702 can be sky.This shows that second diagonal position in the entity associated table 1701 (being the value of the cell under the diagonal positions) can cover and represent the similarity between any two entities in all entities.
More specifically, according to the similarity calculation process 1401 in the entity associated table 1701 with reference to Figure 14.Among Figure 14, at first system is all entities (step 1402) in the load software document, and initialization entity associated table 1701 (step 1403).Judge whether to exist more multiple entity (step 1404), if there is no multiple entity more then finishes this flow process (step 1417).If there is more multiple entity, then system loading entity (step 1405) in the step 1405, is set and is loaded m entity.Read the key word (step 1406) that this m entity comprises, judge whether to exist more multiple key (step 1407), if there is no multiple key more, then system returns step 1405 and continues to load next entity; If there is key word, the key word (step 1409) in system loads key word (step 1408) and the key word of the inquiry contingency table then, and inquire about the associating key word (step 1410) of this key word correspondence.System judges whether to exist more associating key word (step 1411), and if there is no more associating key word, system will be returned step 1408 and continue to load other key words.If there is associating key word, this associating key word (step 1412) of system loads is also sought the entity (step 1413) that comprises this associating key word.System judges whether to exist the entity (step 1414) that comprises this associating key word, the entity that if there is no comprises this associating key word, then return step 1412 and load other associating key word, otherwise system will load this entity and be designated as a (step 1415), and it is capable to the m in the entity associated table 1701, (m, value a) adds 1 operation (step 1416) to a column unit lattice.
Repeat above-mentioned similarity calculation process 1401, the value that continues to load other entities and bring in constant renewal in the cell in the entity associated table 1701.
Entity structure in the index file as shown in figure 15.Entity structure 1501 comprises renewal/establishment/deletion time 1502, and position 1502 comprises key word 1503, associated entity 1504 and matched indicia 1506.Renewal/establishment/deletion time 1502 has been stored the corresponding operating time of this entity.Document or code provider location that this entity exists have been stored in position 1502.Comprise key word 1503 and stored the key word that comprises with this entity.Associated entity 1504 has been stored and the related entity sets of this entity, and it is to calculate resulting by similarity calculation process 1401.Whether matched indicia 1506 storages mate with certain demand change request most.If coupling, this is labeled as very, otherwise this is labeled as vacation.
The similarity of the entity _ demand among this embodiment and entity _ design is calculated as shown in figure 16.Among Figure 16, entity _ demand has comprised demand (Requirement), developer (Developer) and timetable 3 key words such as (Schedule).Entity _ design has comprised demand change (Requirement Change), released version (Release) and timetable 3 key words such as (Schedule).From form 1301 as can be seen, demand change (Requirement Change) exists related with demand (Requirement).Having same key word simultaneously is timetable (Schedule).According to the calculating of similarity calculation process 1401, the value that system can calculate the similarity (1601) between entity _ demand and the entity _ design is 2 like this.
As mentioned above, create in index creation module 2024 before the index file, the user is by load module 201 input demands change request.With reference to shown in Figure 180, at first the user need pass through drop-down menu 1801 specified documents types, the destination document type that on behalf of the demand change, it take place.In this embodiment, the demand change is relevant with demand, so the selection demand, also needs input demand change request content 1802 as Doctype.The user can specify the functional description that needs renewal or change.Afterwards, click application change 1803 buttons and can begin to apply for a new demand change.In addition, the user can click cancel button 1804 to cancel certain demand change request.The user can click the change of checking documents button 1805 track demand documents simultaneously.
Figure 19 shows the detailed process of change request location affected entities according to demand.Among Figure 19, the key word (step 1902) in the system loads demand change request and the matrix table (step 1903) of initialization entity and key word.System judges whether to exist more multiple key (step 1904), if there is more multiple key, the system loading key word also is designated as key word m (step 1905) and loads the entity (step 1906) that comprises this key word; Otherwise, enter step 1911.Whether in coverage, need in the V-arrangement model, judge (step 1907) in order to judge entity.System judges whether to exist more multiple entity (step 1908), if there is more multiple entity, the system loading entity also is designated as a (step 1909) with this entity, and at the capable a column unit of the m lattice (m of entity and key word matrix table, a) position adds 1 (step 1910), continues to load other entities and adds up; If there is no multiple entity more, system will return step 1904 and continue to judge and load key word till not having key word.In entity and key word matrix table, seek maximum summation (step 1911),, obtain the entity (step 1912) at maximum summation place according to this maximum summation position.The matched indicia 1506 (step 1903) of this entity is updated to very, in entity list, seeks all associated entity (step 1914) simultaneously.System judges whether to exist more associated entity (step 1915), if there is more associated entity, system will load associated entity (step 1916) and according to and mate similarity between the entity most and whether exceed coverage and judge (step 1917).If go beyond the scope, system will return step 1914 and continue to seek other associated entity.If do not go beyond the scope, this associated entity is increased in the affected entities, and continues to load entity.If there is no more associated entity, promptly all associated entity have been loaded and have been finished, in process ends (step 1918).In the present embodiment, we suppose that affected scope is 10.Suppose that entity _ design is the entity that mates most, in entity associated table 1701, seek all entities that are associated, the similarity that can find entity _ demand and entity _ design is 2, because it is less than 10, so entity _ demand will be excluded outside affected entities.Opposite, entity _ code is comprised within the affected entities, and reason is that the similarity between entity _ code and the entity _ design is 13.
Figure 20 shows the example of a V-arrangement model 2001.It has comprised the institute in the SDLC in steps.For example, demand analysis 2002 comprises 2003 and sane level activity Acceptance Tests 2004 of subordinate's activity system design.Coding 2005 does not have subordinate and sane level activity.The user can customize and revise this V-arrangement illustraton of model and adapt to their real software development mode.Software document among Fig. 2 then is the various achievement things that above-mentioned steps produced.
Figure 21 shows in the V-arrangement model whether affected process flow diagram of decision entities.At first, system is with the key word (step 2102) in the parsing demand change request.Based on these key words, change the middle search key (step 2103) of destination document (for example, the document of appointment in the drop-down menu 1801) of request in demand, and whether affected entity (step 2104) is arranged in the destination document location.Then, the rank (step 2105) of affected other documents is judged by system.System judges whether to exist sane level document (step 2106), if there is the sane level document, then locatees affected entity (step 2108) at sane level document searching key word (step 2107) and in the sane level document.In addition, system also judges whether to have subordinate's document (step 2109), if there is subordinate's document, then locatees affected entity (step 2111) at subordinate's document searching key word (step 2110) and in subordinate's document.If there is no, then finish this flow process 2112).By above-mentioned flow process, affected entity can filter according to the V-arrangement model.
Figure 22 shows the matrix table 2201 of entity and key word.This matrix table has been stored the coupling mark between all entities and the demand change request key word, wherein, and summation 2202 representatives keyword matching mark altogether.The coupling mark of cell 2203 representative design (Design) key words in entity _ demand.On behalf of entity _ design and all demand changes, cell 2204 ask the coupling mark summation of key words.The entity at the value place of summation 2202 maximums is for mating most entity.In this embodiment, because the value of the summation 2202 of entity _ design is 8, therefore, entity _ be designed to mate most entity.
Figure 23 shows affected entities location example 2301 in the present embodiment.Resolve the demand change request of input, thus the both keyword designing quality that obtains comprising (Design Quality) 2303 and demand change (Requirement Change) 2304.Inquire about key table that comprises from index file and the entity list and obtain, demand change (Requirement Change) 2304 and the coupling mark of designing quality (Design Quality) 2303 in entity _ design are the highest, see the cell 2204 among Figure 22 for details.Search in entity associated table 1701 and close on entity, find that entity _ code does not go beyond the scope, therefore, entity _ code and entity _ design are added in the affected entities, and show this affected entities by output module 203.
Figure 24 has provided a kind of output module 203.It will show all affected entities that the matrix table 2201 according to entity and key word calculates.The coupling mark that cell 2204 from Figure 22 can obtain entity _ design is 8.The similarity that obtains entity _ design and entity _ code in simultaneously can the cell 1703 from Figure 17 is 13.With the entity that closes on most relatively after, the coupling mark of entity _ design can be updated to 8 and add 13, promptly 21.The entity that entity _ design 2401 is mated with oblique line (it is red that oblique line equals, down together) expression most, entity _ code 2402 is with the entity of backslash (it is yellow that backslash equals, down together) the inferior coupling of expression.All affected entities will be presented in output module with different orders and color according to the coupling mark.Simultaneously, click entity _ design icon 2403, the details page of entity _ design will be shown, shown in text box 2404.The user can see the detailed content and the relevant information of relevant entity _ design from text box 2404.Further the reply action can be made a strategic decision based on these page infos.
Figure 25-27 has shown the output module interface that other are possible.
Figure 25 has shown the output module interface of organizing with associated nodes.In this output module interface, entity _ design 2401 shows that with rectangle middle directional ray has been represented the similarity between them with entity _ code 2402.The direction of line has shown the coupling mark size of entity.The entity that the coupling mark is little points to the big entity of coupling mark.Same, represent the entity that mates most with oblique line, represent time entity of coupling with backslash.
Figure 26 has shown the output module interface that another one is possible.The output module interface is with histogram graph representation, and in this histogram, the post bar of oblique line is represented the entity that mates most, represents time entity of coupling with the post bar of backslash.
Figure 27 has shown the output module interface that another one is possible.The output module interface shows all affected entities in the mode of label cloud, and by font size, information such as color represent entity information.
Certainly, be not limited in above-mentioned several output modules interface, in in the invention process, make the user can hold the coverage of this demand change as long as affected entities can be shown, and make the user see that the detailed content of corresponding entity and the output module interface of detailed information all are fine simultaneously.
In the above-described embodiments, explained it how is related and use these related further identification different software documents to comprise association between a large amount of entities of source code with corpus technology identidication key.In fact, the requirement Change Management module 201 among the present invention also provides the method for an alternative corpus identification keyword.
With reference to Figure 28, a dictionary 2801 was created before creating index.The structure of dictionary 2801 as shown in figure 28.The user can be increased to new key word in the dictionary 2801, also can be joined automatically in the dictionary 2801 when finding new key word by program simultaneously.The word sequence number is represented the uniquely tagged of certain key word.Part of speech is represented the part of speech of key word, such as noun (noun.), adverbial word (adv.) or the like.Other key words of synonym representative and this key word synonym.Atomicity represents whether this key word can segment again.If can not segment, then attribute is for being (Yes), otherwise is not (No).
Figure 29 shows and use dictionary and the difference of using corpus to exist when identidication key.Figure 29 and Fig. 6 difference are that at first, the word segmentation processing in the step 604 will be used the reference of dictionary 2801 as keyword recognition; Secondly, all key words in the search dictionary confirm whether current key word exists (step 2902) in dictionary; At last, after definite current word was key word, system was increased to this key word in the dictionary 2801 (step 2903).
The present invention can be applied in the various scenes that are not suitable for using corpus by using self-defining dictionary.On the other hand, program can accumulate keyword fast and in large quantities when creating index file.Increasing key word can be by the accumulation of Automatic Program, and the user only need confirm that emerging various key words get final product in the dictionary.Simultaneously, in order better to improve degree of accuracy of the present invention, some artificial operations also are supported.
Figure 30 shows increases the artificial interaction flow of confirming step in system.After user 3001 sends a request demand change (step 3002), requirement Change Management module 202 is with the key word (step 3003) in the change of the parsing demand automatically request.Then, the user can confirm these resolved demand change request key words (step 3004).Step 3004 can provide the guarantee of degree of accuracy for the influenced scope location (step 3005) of the use index file of next step execution.After requirement Change Management module 202 calculated affected entities, because system may not cover all and be affected entity, the user can be provided with coverage (step 3006) and expand possible affected entities scope to.This scope can re-execute in the calculating of the step 1917 among Figure 19, thereby locatees affected entities more accurately.In addition, the present invention also supports the user to confirm affected entities (step 3007).The user can judge whether that some entity needs is changed according to the experience of oneself like this.Can from output module, come from affected entities, to remove entity _ code by delete entity _ code 2402 such as the user.The user confirms that affected entities later includes only entity _ design 2401 like this.By the affirmation of this human intervention, affected entities will cover might need the entity that changes and can for after demand change reply accurate guarantee is provided.
Figure 31 shows in the embodiment of the invention and carries out cost estimation approach flow process according to influenced scope.In the function of cost estimating, according to aforesaid affected entities location, load possibility affected entity (step 3101), judge whether to exist more multiple entity (step 3102), if there is more multiple entity, to load current entity (step 3103) one by one, and load and be scheduled to sentence cost (step 3104), as each sentence of 0.018 man month, i.e. 0.018 man month/sentence, 1 man month was represented one month workload of a personal work, calculate possibility affected sentence number (step 3105) in the current entity according to search key again, sentence cost and the affected sentence number of possibility are multiplied each other, obtain the possible change cost (step 3106) of this entity, and with this cost be added to the change cost in (step 3107), up to there not being more multiple entity; If there is no multiple entity more then finishes cost estimating (step 3108).
Figure 32 shows the system architecture diagram of demand change coverage in the positioning software exploitation that comprises the cost estimating module in the embodiment of the invention.Among Figure 32, cost estimating module 204 is used for according to described affected entities, according to predetermined sentence cost cost estimating is carried out in described demand change request.
The above only is preferred embodiment of the present invention; not in order to restriction the present invention; within the spirit and principles in the present invention all, any modification, the change that the embodiment of the invention is done, make up, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (18)
1. the method for demand change coverage is characterized in that during a positioning software was developed, and comprising:
Importing at least one demand change request, at least one software document and code file that at least one is corresponding with described software document gathers;
According to described demand change request, in described software document and the set of described code file, locate affected entities;
Export described affected entities.
2. method according to claim 1 is characterized in that,
The location affected entities comprises in described software document and the set of described code file:
From described software document, extract document information, and from described code file set, extract code characteristic information;
Determine a plurality of entities and a plurality of key word according to described document information and code characteristic information;
Determine the degree of association of described a plurality of entities according at least one key word in described a plurality of key words;
The degree of association according to described a plurality of entities is created index file;
According to described index file, in described a plurality of entities, locate affected entities.
3. method according to claim 2 is characterized in that, described method further comprises:
The described key word in the described software document discerned in the use corpus;
The described key word that comprises in the code recognition rule cognizance code of use based on type of code;
Obtain the incidence relation between the described key word, and form the key word contingency table;
Based on described key word contingency table, set up association and similarity between the described entity;
Create index file, to store association and the similarity between the described entity.
4. method according to claim 2 is characterized in that, described method further comprises:
Create dictionary;
Use described dictionary to discern described key word in the described software document; Wherein, when new key word occurring in the described software document, add described new key word to described dictionary;
The described key word that comprises in the code recognition rule cognizance code of use based on type of code;
Obtain the incidence relation between the described key word, and form the key word contingency table;
Based on described key word contingency table, set up association and similarity between the described entity;
Create index file, to store association and the similarity between the described entity.
5. method according to claim 2 is characterized in that, described method further comprises:
Set up the V-arrangement model, according to the described affected entities of described V-arrangement model orientation.
6. method according to claim 5 is characterized in that,
In described V-arrangement model, comprise sane level document and subordinate's document;
Key word according to coupling in described sane level document and subordinate's document calculates coupling mark and similarity, according to described coupling mark, determine to mate entity most, and, determine in the described affected entities except that described other described affected entities of mating most the entity according to described similarity.
7. method according to claim 6 is characterized in that, described method further comprises:
According to described coupling mark and described similarity, output shows described affected entities in a predefined manner.
8. method according to claim 1 is characterized in that,
Described entity comprises chapters and sections, the code file bag of software document.
9. method according to claim 1 is characterized in that,
Described code file set comprises a plurality of code file bags;
Described code file bag comprises a plurality of code files.
10. method according to claim 2 is characterized in that,
Described document information comprises: Doctype, document format, document content;
Described code characteristic information comprises: code file name, type of code;
For software document, described key word is the key word in the document content;
For the code file set, described key word is the code file name.
11. method according to claim 1 is characterized in that, described method further comprises:
According to described affected entities, cost estimating is carried out in described demand change request according to predetermined sentence cost.
12. the system of demand change coverage is characterized in that during a positioning software was developed, and comprising:
Load module is used to import at least one demand change request, at least one software document and code file that at least one is corresponding with described software document and gathers;
The requirement Change Management module is used for locating affected entities according to described demand change request in described software document and the set of described code file;
Output module is used to export described affected entities.
13. system according to claim 12 is characterized in that,
Described requirement Change Management module comprises:
Information extraction modules is used for extracting document information from described software document, and extracts code characteristic information from described code file set;
Text analysis model is used for determining a plurality of entities and a plurality of key word according to described document information and code characteristic information;
Related identification module is used for determining according at least one key word of described a plurality of key words the degree of association of described a plurality of entities;
The index creation module is used for creating index file according to the degree of association of described a plurality of entities;
Locating module is used for according to described index file, locatees affected entities in described a plurality of entities.
14. system according to claim 13 is characterized in that, in described system,
Formation is used to store described software document;
Described requirement Change Management module is further used for obtaining the described software document stored and creates described index file according to described software document in described formation;
Scheduler is used for intermittently calling the described index creation module of described requirement Change Management module to create index file.
15. system according to claim 13 is characterized in that,
Described locating module is further used for setting up the V-arrangement model, according to the described affected entities of described V-arrangement model orientation.
16. system according to claim 15 is characterized in that,
In described V-arrangement model, comprise sane level document and subordinate's document;
Described locating module, be further used in described sane level document and subordinate's document, calculating coupling mark and similarity according to the key word that mates, according to described coupling mark, determine to mate most entity, according to described similarity, determine in the described affected entities except that described other described affected entities of mating most the entity.
17. system according to claim 16 is characterized in that,
Described output module is used for according to described coupling mark and described similarity, and output shows described affected entities in a predefined manner.
18. system according to claim 12 is characterized in that, described system comprises:
The cost estimating module is used for according to described affected entities, according to predetermined sentence cost cost estimating is carried out in described demand change request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101632157A CN102214091A (en) | 2010-04-09 | 2010-04-09 | Method and system for positioning required change influence range during software development |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101632157A CN102214091A (en) | 2010-04-09 | 2010-04-09 | Method and system for positioning required change influence range during software development |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102214091A true CN102214091A (en) | 2011-10-12 |
Family
ID=44745414
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010101632157A Pending CN102214091A (en) | 2010-04-09 | 2010-04-09 | Method and system for positioning required change influence range during software development |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102214091A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609402A (en) * | 2012-01-12 | 2012-07-25 | 北京航空航天大学 | Device and method for generation and management of ontology model based on real-time strategy |
| CN103729381A (en) * | 2012-10-16 | 2014-04-16 | 佳能株式会社 | Method and device used for recognizing semantic information in series of documents |
| CN104424285A (en) * | 2013-08-30 | 2015-03-18 | 国际商业机器公司 | Method and device for performing impact analysis on change request |
| CN104461572A (en) * | 2014-12-29 | 2015-03-25 | 常熟理工学院 | Analysis method for spreading effect of requirement change |
| CN106528119A (en) * | 2016-11-02 | 2017-03-22 | 北京神舟航天软件技术有限公司 | Requirement tracing method based on research and development work product identification |
| CN107066256A (en) * | 2017-02-24 | 2017-08-18 | 中国人民解放军海军大连舰艇学院 | A kind of object based on tense changes the modeling method of model |
| CN107844510A (en) * | 2016-09-20 | 2018-03-27 | 株式会社日立制作所 | Influence conformance analysis method and its device |
| CN110045981A (en) * | 2018-01-14 | 2019-07-23 | 北京关键科技股份有限公司 | A method of analytical technology is compared based on source code and establishes demand tracking relationship |
| CN110362538A (en) * | 2019-07-19 | 2019-10-22 | 中国工商银行股份有限公司 | Relationship determines method and apparatus, electronic equipment and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101256492A (en) * | 2008-03-31 | 2008-09-03 | 宋乃辉 | Software development method and system for executing model drive structure |
| US20080216056A1 (en) * | 2007-03-01 | 2008-09-04 | Stephen Bate | Fully integrated software change request system which includes but not limited to the following modules: change request, migration request, work flow engine project, collaboration, code movement, document tracking, code execution, status notification and database schema snapshot as well as various reporting capabilities. |
| CN101344859A (en) * | 2008-09-02 | 2009-01-14 | 中国科学院软件研究所 | Simulation method and system for estimating influence of requirement changeability to software project |
| CN101556553A (en) * | 2009-03-27 | 2009-10-14 | 中国科学院软件研究所 | Defect prediction method and system based on requirement change |
| CN101593111A (en) * | 2009-05-31 | 2009-12-02 | 大连新中连软件集团有限公司 | A kind of Service Component reaches the applied software development method and system based on Service Component |
-
2010
- 2010-04-09 CN CN2010101632157A patent/CN102214091A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080216056A1 (en) * | 2007-03-01 | 2008-09-04 | Stephen Bate | Fully integrated software change request system which includes but not limited to the following modules: change request, migration request, work flow engine project, collaboration, code movement, document tracking, code execution, status notification and database schema snapshot as well as various reporting capabilities. |
| CN101256492A (en) * | 2008-03-31 | 2008-09-03 | 宋乃辉 | Software development method and system for executing model drive structure |
| CN101344859A (en) * | 2008-09-02 | 2009-01-14 | 中国科学院软件研究所 | Simulation method and system for estimating influence of requirement changeability to software project |
| CN101556553A (en) * | 2009-03-27 | 2009-10-14 | 中国科学院软件研究所 | Defect prediction method and system based on requirement change |
| CN101593111A (en) * | 2009-05-31 | 2009-12-02 | 大连新中连软件集团有限公司 | A kind of Service Component reaches the applied software development method and system based on Service Component |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609402A (en) * | 2012-01-12 | 2012-07-25 | 北京航空航天大学 | Device and method for generation and management of ontology model based on real-time strategy |
| CN103729381A (en) * | 2012-10-16 | 2014-04-16 | 佳能株式会社 | Method and device used for recognizing semantic information in series of documents |
| CN104424285A (en) * | 2013-08-30 | 2015-03-18 | 国际商业机器公司 | Method and device for performing impact analysis on change request |
| CN104424285B (en) * | 2013-08-30 | 2018-01-26 | 国际商业机器公司 | For the method and apparatus for the impact analysis for change request |
| CN104461572B (en) * | 2014-12-29 | 2017-08-18 | 常熟理工学院 | A kind of demand change involves effect analysis method |
| CN104461572A (en) * | 2014-12-29 | 2015-03-25 | 常熟理工学院 | Analysis method for spreading effect of requirement change |
| CN107844510A (en) * | 2016-09-20 | 2018-03-27 | 株式会社日立制作所 | Influence conformance analysis method and its device |
| CN107844510B (en) * | 2016-09-20 | 2021-04-30 | 株式会社日立制作所 | Influence sum analysis method and device |
| CN106528119A (en) * | 2016-11-02 | 2017-03-22 | 北京神舟航天软件技术有限公司 | Requirement tracing method based on research and development work product identification |
| CN107066256A (en) * | 2017-02-24 | 2017-08-18 | 中国人民解放军海军大连舰艇学院 | A kind of object based on tense changes the modeling method of model |
| CN107066256B (en) * | 2017-02-24 | 2020-08-04 | 中国人民解放军海军大连舰艇学院 | Object change model modeling method based on tense |
| CN110045981A (en) * | 2018-01-14 | 2019-07-23 | 北京关键科技股份有限公司 | A method of analytical technology is compared based on source code and establishes demand tracking relationship |
| CN110362538A (en) * | 2019-07-19 | 2019-10-22 | 中国工商银行股份有限公司 | Relationship determines method and apparatus, electronic equipment and computer readable storage medium |
| CN110362538B (en) * | 2019-07-19 | 2022-02-25 | 中国工商银行股份有限公司 | Relationship determination method and apparatus, electronic device, and computer-readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102214091A (en) | Method and system for positioning required change influence range during software development | |
| JP4943240B2 (en) | Business process creation method, business process creation device, and business process creation program | |
| US20090083619A1 (en) | Reusable data markup language | |
| US20110282861A1 (en) | Extracting higher-order knowledge from structured data | |
| CN108762743B (en) | Data table operation code generation method and device | |
| KR102397495B1 (en) | No code web development and operating system, and service method using of it | |
| US8407235B2 (en) | Exposing and using metadata and meta-metadata | |
| US20110264678A1 (en) | User modification of a model applied to search results | |
| Hahn et al. | UIMA-based JCoRe 2.0 goes GitHub and Maven central―state-of-the-art software resource engineering and distribution of NLP pipelines | |
| CN115547466A (en) | Medical institution registration and review system and method based on big data | |
| EP2199905A1 (en) | Lifecycle management and consistency checking of object models using application platform tools | |
| CN111427577A (en) | Code processing method and device and server | |
| JP2021089666A (en) | Information processing apparatus and program | |
| JP2010015458A (en) | Program correction support system, program correction support method, and program correction support program | |
| KR100581687B1 (en) | A unification method of Query Analyzers of database management systems | |
| KR102547033B1 (en) | Method for providing information in the way user selected using keyword recognition function | |
| KR102532216B1 (en) | Method for establishing ESG database with structured ESG data using ESG auxiliary tool and ESG service providing system performing the same | |
| Wojszczyk et al. | The process of verifying the implementation of design patterns—used data models | |
| US11544331B2 (en) | Artificial intelligence for product data extraction | |
| US11275729B2 (en) | Template search system and template search method | |
| Hamdani et al. | A Novel Framework to Automatically Generate IFML Models From Plain Text Requirements | |
| JP6336922B2 (en) | Business impact location extraction method and business impact location extraction device based on business variations | |
| AU2014101413A4 (en) | Information displaying method and apparatus | |
| US20130265326A1 (en) | Discovering a reporting model from an existing reporting environment | |
| JP4352840B2 (en) | Program, data processing method and data processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20111012 |