CN104850399B - A kind of component interface realizes the retrospective analysis method and system of mapping table with component - Google Patents
A kind of component interface realizes the retrospective analysis method and system of mapping table with component Download PDFInfo
- Publication number
- CN104850399B CN104850399B CN201510213960.0A CN201510213960A CN104850399B CN 104850399 B CN104850399 B CN 104850399B CN 201510213960 A CN201510213960 A CN 201510213960A CN 104850399 B CN104850399 B CN 104850399B
- Authority
- CN
- China
- Prior art keywords
- node
- component
- attribute
- information
- realized
- 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.)
- Active
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The retrospective analysis method and system of mapping table are realized with component the present invention relates to a kind of component interface, belong to the retrospective analysis field of component.The present invention includes ontological construction module, establishes ontology model for being realized to component interface and component, and represented with XML；File analyzing module, ontology model is established for being realized to component interface and component, and represented with XML；Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；Retrospective analysis module, for analyzing and showing retrospective analysis result.Combination member interface of the present invention and the characteristics of realizing, realized using ontology describing component interface and component；It is improved on the basis of traditional retrospective analysis method, generates the mapping table between the component realization for demand analysis, the component interface of design phase and coding stage；By mapping table, collection is influenceed by component interface modification in analysis and display member realization.
Description
Technical field
The present invention relates to the retrospective analysis method and system that a kind of component interface and component realize mapping table, belong to component
Retrospective analysis field.
Background technology
Component and component-based software engineering (Component-based Software Engineering, abbreviation
CBSE the focus of field of software engineering) is turned into.Component is the software entity that can be re-used, mainly by component interface and component
Realize composition.The quality of software systems is largely dependent upon the quality of the component of composition system, the demand of component, is related to
Or coding modification may all bring influence to component, it is also possible to the whole software systems having influence on where component.With to soft
What part multiplexing understood gos deep into, and the concept of component has been no longer limited to source code, and extend into component and system requirements, framework,
According to this and the useful information of other split hairs activities, these information can for design, document, test plan, test cases sum
Referred to as Reusable design.Due to the complication of component concept and the structuring of component information, structure is represented using body
Part information, on the one hand can it is more accurate, intactly component is described, while component retrieval can also be realized；The opposing party
Face also provides abundant semantic annotation for the faceted description of component.
In the Evolutionary Cycles of component-based software, component testing is guarantee and improves one of important means of component quality,
Laid a good foundation for later stage integration testing, system testing and regression test.Need to be changed influence point before software implementation
Analysis, estimates influence caused by software change, and supporting item manager and developer assess and implemented change.By effectively changing
Impact analysis can reduce the cost of software maintenance and the cost of regression test.Software change impact analysis at present mainly has two
Kind method, a kind of is the change impact analysis based on retrospect, and another kind is the change impact analysis based on dependence.Based on chasing after
Analysis of tracing back refers to that " some component can be traced from forward and backward both direction in the member corresponding to life cycle each stage
Element ".Retrospective analysis method provides the detailed assessment to correlation between all types of entities.
In the life cycle of component, the modification made to component is not only related to the source code of component, also literary with demand
The correlations such as shelves, design documentation and test case.Change impact analysis based on retrospect can not only trace first in same level
Relation between element, it can also trace some element of a certain level and its in the element corresponding to another level.Therefore, user is worked as
When proposing some modification, by this retrospective, it may recognize that in different levels by the element of potential impact.Except this
Outside, object and its incidence relation that retrospective analysis defines retrospect entity, should traced back to.Retroactive method uses significant name
Word marks data in code and document, such as function, variable, type, class and method, can be with by the analyses of these marker characters
The concept of the documentation of program of different levels is associated in help.Therefore, using ontology describing component model, the mapping between body is passed through
Relation --- mapping table, direction is established which depict retrospect entity relationship, so as to propose the component retrospective analysis based on body
Process.Compared with other change influence techniques, the component retrospective analysis based on body can effectively analyze and maintenance system.
The content of the invention
In view of the above-mentioned problems, the invention provides a kind of component interface and component realize mapping table retrospective analysis method and
System.
The technical scheme is that：A kind of component interface realizes the retrospective analysis method of mapping table with component, including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Component interface is referred to as source body, and component, which is realized, is referred to as target body, and the component interface realizes that generation is reflected with component
The method of firing table, comprises the following steps：
Step1, when source body and target ontological existence and be not space-time, pass through parserXML () method and parse source body
With target body；
Step2, attribute node object in the body of source, taking-up attribute section are obtained by getAttributenode () method
The title and value of point；
Step3, according to the source Noumenon property nodename obtained, searched and parsed by findName () method
Target Noumenon property nodename in whether there is corresponding node：
If corresponding attribute node title be present, source body and target body category are judged by matchValue () method
Whether the value of property node matches：If attribute node value matches, pass through xmlDepth () method extreme saturation target body；If
Attribute node value mismatches, then performs step Step7；
If in the absence of corresponding attribute node title, step Step7 is performed；
Step4, pass through each target Noumenon property node of getPath () method acquisition to the most short undirected road of root node
Footpath, so as to the public ancestor node of attribute node matched, pass through getNbnode () method and obtain public ancestor node
Adjacent attribute node；Wherein, all properties node under public ancestor node is referred to as adjacent in addition to match attribute node
Attribute node；It is an XML document tree to make T, and n and n0 are two nodes in T, and n and n0 most short undirected path are removed by n and n0
The path composition that top outside root node arrives n and n0 respectively, public ancestor node refer in most short undirected path distance n and
Same node point farthest n0；
Step5, by semanticRelated () method judge that the attribute node that is matched in target body is adjacent thereto
Whether attribute node is semantic related：
If semantic related, the attribute node of target body is obtained in identical father by getRelatedNode () method
The adjacent attribute node of node；If semantic uncorrelated, step Step7 is performed；
Wherein, the tree of all nodes composition under node t1, node t2 public ancestor node, is expressed as relational tree T
And if only if in all nodes under (t1, t2), node t1 and node t2 nearest public ancestor node node t1 or node t2
Title exist and unique, claim node t1 to node t2 to be semantic related；
Step6, by crateTable () method by the attribute node object of the source body of acquisition, corresponding target sheet
The attribute node object of body and adjacent attribute node object deposit set of node, belong to the attribute node object of source body as source
Property, and the attribute node object of target body and adjacent attribute node object are shown in the form of a table as objective attribute target attribute；
Step7, end；
Component interface includes syntactic information, semantic information, protocol information, test information；Syntactic information describes including function
And non-functional description, function description include method information, parameter information, text description, method information includes method name, returns to class
Type, parameter information include parameter name, parameter type；Non-functional description includes quality of service information and additional information, service quality
To define satisfaction of the user using service, including expense, time, reliability, credit worthiness, additional information includes opening information
Originator, version number, application field, deadline；Semantic information includes contract, and contract includes precondition, postcondition and not
Variant；Protocol information includes composite component, solid memder and flow address；Testing information includes test case, testing time, survey
Examination evaluation；
Component, which is realized, includes class；Contain essential information and the function description of class in class, the essential information of class include class name,
Parent name and class annotation, function description include method information and parameter information, and method information includes method name, return type and side
Method annotates, and parameter information includes parameter name, parameter type；
In the ontology model of component interface, method name, return type, parameter name, parameter type, text description, expense, when
Between, reliability, credit worthiness, developer, version number, application field, deadline, precondition, postcondition and invariant are multiple
Close component, solid memder and flow address, test case, testing time, test evaluation, the above node and be referred to as attribute section
Point；
Class name, parent name, class annotation in the ontology model that component is realized, method name, return type, method annotation, ginseng
Several, parameter type, above node are referred to as attribute node.
The step of display retrospective analysis result, is as follows：
Step1, modification content is determined by modifyJudge () method；
Step2, established by searchMap () method according to modification content and inquire about and judge to change whether content is reflecting
In firing table：
If changing content in the mapping table, step Step3 is performed；
If modification content in the mapping table, does not perform step Step4；
Step3, obtain the record in the attribute of component interface source with modification content in the mapping table by getMapsc ()
Set R, to each record R in Ri(i=1 ..., n), take out the set T that component realizes objective attribute target attributei, to TiTake and occur simultaneously
To impacted result set, step Step6 is then performed；
Step4, the component matched by modification content search of the findModify () method in component interface are real
It is existing, when lookup component is realized in component base, information in component interface is organized into m word first, the rope as query term Q
Draw list, component is realized as Di, similar value is obtained according to probability Similarity Measure, obtained in getSimilarity () method
Take and realized with component interface similarity highest component；
Calculate document DiWith the similarity between inquiry Q：
Similarity(Di, Q) and=Pr (Di|Q)
Using Bayesian formula, by conditional probability Pr (Di| Q) change into：
In above-mentioned formula, Pr (Q) is the prior probability for inquiring about Q, i.e. constant；Pr(Di) it is document DiPrior probability, institute
Ask Pr (Q | Di) it is document D after known inquiry Q occursiConditional probability；Conditional probability Pr (Q | Di) in, inquiry Q is one group
The index list of word, there is m word, therefore：
Pr(Q|Di)=Pr (W1,W2,…,Wm|Di)
If the component for finding matching is realized, step Step5 is performed；
If the component for not finding matching is realized, step Step7 is performed；
Step5, component realization in by findSC () method according to modification content retrieval, the result conduct retrieved
Impacted result set；
The impacted result set of Step6, display is as retrospective analysis result；
Step7, end.
A kind of component interface realizes the retrospective analysis system of mapping table with component, it is characterised in that：Including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
The present invention operation principle be：
The present invention has initially set up component interface, including syntactic information, semantic information, protocol information, test information.Mainly
Content is as follows：
(1) syntactic information：Including function description and non-functional description；
(2) semantic information：Including contract；
(3) protocol information：Including composite component, solid memder and flow address；
(4) information is tested：Including test case, testing time, test evaluation.
Component interface information (1) layer is syntactic information, the structure or form of representation program, that is, represents to form each of language
Combination rule between individual identifier, but it is not related to the specific meanings of these identifiers, it is not directed to use with person yet.Therefore, grammer
Information includes function description (FunctionalDescription) and non-functional description (Non-
FunctionalDescription).1st, function describes, including method information (FunctionalInformation), parameter letter
Cease (ParameterInformation), text description (TextDescription).Method information
(FunctionalInformation) mainly by method name (FunctionalName), return type (ReturnType).Parameter
Information (ParameterInformation) includes parameter name (ParameterName), parameter type (ParameterType).
2nd, non-functional description, including quality of service information (QoSInformation) and additional information
(AdditionalInformation).Quality of service information, to define satisfaction of the user using service, including expense
(Cost), time (Time) reliability (Reliability), credit worthiness (Reputation).Additional information includes developer
(Creator), version number (Version), application field (Domain), deadline (Deadline).
Component interface (2) layer is contract information, and contract is exactly a kind of stipulations, contract in simple terms, and it is management object
Between one group of interaction rule.Contract indicates invocation of procedure side and realization side mutual responsibility and interests：Customer only has
Process corresponding to could being called in the case where meeting precondition；At the end of the side's of realization promise process, what postcondition indicated
Work will be done, and invariant is still met.Responsibility when contract can be used for distinguishing software failure：If precondition quilt
Violate, then should find mistake in customer；If postcondition or invariant are breached, responsibility is in realization side.Therefore, contract
(Contract) include：Precondition (Precondition), postcondition (Postcondition) and invariant
(Invariant)。
Component interface (3) layer is protocol information, is to provide angle from the service of component, in order to preferably describe structure
Part information, in component interface content be single to component or composite component all gives information, while also provides and make
With flow address during service.Therefore, protocol information includes：Composite component (CompositedService), solid memder
And flow address (URL) (SingleComponent).
Component interface (4) layer is test information, and in order to meet the needs of user, information during component testing is deposited
Storage.It is all particularly significant for the supplier, component user and third party of component to test information.Component supplier is by checking
Can test information determines that component whether there is problem, be delivered for use；Component reusage person in component interface then by testing information
Description, understand component whether quality reliable and should be noted that the problem of avoiding during multiplexing；Third party is surveyed by checking
Examination information is integrated with an objective appraisal to component.Therefore, test information includes：When test case (TestCase), test
Between (TestingTime) and test evaluation (TestingEvaluation).
The feature that component is realized is considered, for the structure matching in mapping process with component interface, with object-oriented structure
Exemplified by part.Realize that (SourceCode) includes class (ClassDescription) in component.The basic of class is contained in class
Information (ClassInformation) and function description (FunctionalDescription).The essential information of class includes class name
(ClassName), parent name (FatherClassName) and class annotation (ClassAnnotation).Function description includes：Side
Method information (FunctionalInformation) and method parameter information (ParameterInformation).Method information master
To include method name (FunctionalName), return type (ReturnType) and method annotation
(FunctionalAnnotation).Parameter information includes parameter name (ParameterName), parameter type
(ParameterType)。
Hierarchical relationship all be present in the internal structure that component interface and component are realized, this is the important of extraction semantic information
Foundation.Therefore, realized using ontology describing component interface and component.Because concept is most important blocks of knowledge in body, generally
The definition of thought is to possess the group of individuals of some predicables.Body can represent and stored with the form of concept map, concept map
Structure mainly include node, three parts of line and conjunction.Node is just placed in the concept in circle.Line represents two
Meaning relation between concept.Conjunction is placed in being formed the contact word of proposition between two concepts on line.In level knot
Node in structure positioned at upper strata can generally draw several knowledge branches, therefore the node that can draw knowledge branch is referred to as
Concept node.But bottom node is the detailed description to upper layer node, it, which includes value but its, cannot draw knowledge branch,
Therefore bottom node is referred to as attribute node.In the ontology model of component interface, method name (FunctionalName), return
Type (ReturnType), parameter name (ParameterName), parameter type (ParameterType), text description
(TextDescription), expense (Cost), time (Time), reliability (Reliability), credit worthiness
(Reputation), developer (Creator), version number (Version), application field (Domain), deadline
(Deadline), precondition (Precondition), postcondition (Postcondition), invariant (Invariant),
Composite service (CompositedService), single service (SingleComponent), flow address (URL), test case
(TestCase), testing time (TestingTime), test evaluation (TestingEvaluation), above node are referred to as attribute
Node.
In the ontology model that component is realized, class name (ClassName), parent name (FatherClassName), class annotation
(ClassAnnotation), method name (FunctionalName), return type (ReturnType), method annotation
(FunctionalAnnotation), parameter name (ParameterName), parameter type (ParameterType), above node
Referred to as attribute node.
Based on the above, the invention provides a kind of component interface based on body and component to realize mapping table generation side
Method, in the method, component interface are referred to as source body, and component, which is realized, is referred to as target body, comprises the following steps：
Step1, when source body and target ontological existence and be not space-time, pass through parserXML () method and parse source body
With target body；
Step2, attribute node object in the body of source, taking-up attribute section are obtained by getAttributenode () method
The title and value of point；
Step3, according to the source Noumenon property nodename obtained, searched and parsed by findName () method
Target Noumenon property nodename in whether there is corresponding node：
If corresponding attribute node title be present, source body and target body category are judged by matchValue () method
Whether the value of property node matches：If attribute node value matches, pass through xmlDepth () method extreme saturation target body；If
Attribute node value mismatches, then performs step Step7；
If in the absence of corresponding attribute node title, step Step7 is performed；
Step4, pass through each target Noumenon property node of getPath () method acquisition to the most short undirected road of root node
Footpath, so as to the public ancestor node of attribute node matched, pass through getNbnode () method and obtain public ancestor node
Under adjacent attribute node, i.e., all properties node under public ancestor node is referred to as adjacent attribute in addition to match attribute node
Node.Definition：It is an XML document tree to make T, and n and n0 are two nodes in T, and n and n0 most short undirected path are by n and n0
Top (in addition to root node) arrive n and n0 path composition respectively, public ancestor node refers in most short undirected path middle-range
The same node point farthest from n and n0；By taking Fig. 1 as an example, the most short undirected path of node (7) is (7)-(5)-(4)-(2), section
The most short undirected path of point (9) is (9)-(6)-(4)-(2), thus according to public ancestor node definition understand node (7) and
The public ancestor node of node (9) is (2)；The most short undirected path of node (8) is (8)-(5)-(4)-(2), according to public
Ancestor node defines, most short undirected path (7)-(5)-(4)-(2) of node (7), the phase farthest apart from node (7), (8)
It is node (2) with node, therefore the public ancestor node of node (7) and node (8) is 2.
Step5, by semanticRelated () method judge that the attribute node that is matched in target body is adjacent thereto
Whether attribute node is semantic related；Node t1, node t2 public ancestor node under all nodes composition tree, be expressed as closing
System tree T (t1, t2), and if only if in all nodes under node t1 and node t2 nearest public ancestor node node t1 or section
Point t2 title is present and uniquely, title node t1 is semantic related to node t2.
By taking Fig. 1 as an example, the relational tree T { (3), (7) } of node (3) and (7) is as shown in Fig. 2 the title of its interior joint (3)
Level is present and unique, then node (3) with (7) is semantic related, similarly knowable to node (3) and node (8), node (9),
Node (10) is semantic related；But node (7) is that semanteme is incoherent with node (10) with node (9), node (7), because
Be node (4) for nearest public ancestor node, all nodes under nearest public ancestor node for (4), (5), (6), (7),
(8), (9), (10) }, node (7), node (9), the title of node (10) are present, but not unique therefore uncorrelated.
If semantic related, the attribute node of target body is obtained in identical father by getRelatedNode () method
The adjacent attribute node of node；If semantic uncorrelated, step Step7 is performed；
Step6, by crateTable () method by the attribute node object of the source body of acquisition, corresponding target sheet
The attribute node object of body and adjacent attribute node object deposit set of node, belong to the attribute node object of source body as source
Property, and the attribute node object of target body and adjacent attribute node object are shown in the form of a table as objective attribute target attribute；
Step7, end；
Present invention also offers a kind of retrospective analysis system, the system includes：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Ontological construction module further comprises：File Open module, for selecting opening members interface document and component real
Existing file；File analyzing module, ontology model is established for being realized to component interface and component, and represented with XML.
Mapping is established module and further comprised：Syntactic information mapping table generation module.
Retrospective analysis module retrospective analysis module, further comprises：Show retrospective analysis result.Generated according in the present invention
Mapping table in carry out retrospective analysis, comprise the following steps：
(1) modification content is determined by modifyJudge () method；
(2) established by searchMap () method according to modification content and whether inquire about and judge to change content in mapping table
In：
If changing content in the mapping table, step (3) is performed；
If modification content in the mapping table, does not perform step (4)；
(3) being obtained in the mapping table by getMapsc () has the record set of modification content in the attribute of component interface source
R is closed, to each record R in Ri(i=1 ..., n), take out the set T that component realizes objective attribute target attributei, to TiCommon factor is taken to obtain
Impacted result set, then perform step (6)；
(4) component matched by modification content search of the findModify () method in component interface is realized,
When lookup component is realized in component base, information in component interface is organized into m word first, the index column as query term Q
Table, component is realized as Di, similar value is obtained according to probability Similarity Measure, with getSimilarity () method obtain with
Component interface similarity highest component is realized；
Calculate document DiWith the similarity between inquiry Q：
Similarity(Di, Q) and=Pr (Di|Q)
Using Bayesian formula, by conditional probability Pr (Di| Q) change into：
In above-mentioned formula, Pr (Q) is the prior probability for inquiring about Q, i.e. constant；Pr(Di) it is document DiPrior probability, institute
Ask Pr (Q | Di) it is document D after known inquiry Q occursiConditional probability；Conditional probability Pr (Q | Di) in, inquiry Q is one group
The index list of word, there is m word, therefore：
Pr(Q|Di)=Pr (W1,W2,…,Wm|Di)
If the component for finding matching is realized, step (5) is performed；
If the component for not finding matching is realized, step (7) is performed；
(5) it is used as in component realization by findSC () method according to content retrieval, the result retrieved is changed by shadow
Loud result set；
(6) show impacted result set as retrospective analysis result；
(7) terminate.
The beneficial effects of the invention are as follows：
1) combination member interface and the characteristics of realizing, realized using ontology describing component interface and component；
2) it is improved, is generated for demand analysis, design phase on the basis of traditional retrospective analysis method
Mapping table between component interface and the realization of the component of coding stage；
3) by mapping table, collection is influenceed by component interface modification in analysis and display member realization.
Brief description of the drawings
Fig. 1,2 be the present invention a kind of mapping table generating method citing；
Fig. 3 is a kind of structured flowchart of retrospective analysis system of the present invention；
Fig. 4 is the ontology model of the component interface of embodiments of the invention 2；
Fig. 5 is the ontology model that the component of embodiments of the invention 2 is realized；
Fig. 6 is a kind of broad flow diagram of mapping table generating method of the present invention；
Fig. 7,8 be embodiments of the invention 2 most short undirected path；
Fig. 9 is the public ancestors of embodiments of the invention 2；
Figure 10 is the adjacent attribute node of embodiments of the invention 2；
Figure 11 is a kind of broad flow diagram of retrospective analysis method of the present invention.
Embodiment
Embodiment 1：As shown in figs. 1-11, a kind of component interface realizes the retrospective analysis method of mapping table with component, including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Component interface is referred to as source body, and component, which is realized, is referred to as target body, and the component interface realizes that generation is reflected with component
The method of firing table, comprises the following steps：
Step1, when source body and target ontological existence and be not space-time, pass through parserXML () method and parse source body
With target body；
Step2, attribute node object in the body of source, taking-up attribute section are obtained by getAttributenode () method
The title and value of point；
Step3, according to the source Noumenon property nodename obtained, searched and parsed by findName () method
Target Noumenon property nodename in whether there is corresponding node：
If corresponding attribute node title be present, source body and target body category are judged by matchValue () method
Whether the value of property node matches：If attribute node value matches, pass through xmlDepth () method extreme saturation target body；If
Attribute node value mismatches, then performs step Step7；
If in the absence of corresponding attribute node title, step Step7 is performed；
Step4, pass through each target Noumenon property node of getPath () method acquisition to the most short undirected road of root node
Footpath, so as to the public ancestor node of attribute node matched, pass through getNbnode () method and obtain public ancestor node
Adjacent attribute node；Wherein, all properties node under public ancestor node is referred to as adjacent in addition to match attribute node
Attribute node；It is an XML document tree to make T, and n and n0 are two nodes in T, and n and n0 most short undirected path are removed by n and n0
The path composition that top outside root node arrives n and n0 respectively, public ancestor node refer in most short undirected path distance n and
Same node point farthest n0；
Step5, by semanticRelated () method judge that the attribute node that is matched in target body is adjacent thereto
Whether attribute node is semantic related：
If semantic related, the attribute node of target body is obtained in identical father by getRelatedNode () method
The adjacent attribute node of node；If semantic uncorrelated, step Step7 is performed；
Wherein, the tree of all nodes composition under node t1, node t2 public ancestor node, is expressed as relational tree T
And if only if in all nodes under (t1, t2), node t1 and node t2 nearest public ancestor node node t1 or node t2
Title exist and unique, claim node t1 to node t2 to be semantic related；
Step6, by crateTable () method by the attribute node object of the source body of acquisition, corresponding target sheet
The attribute node object of body and adjacent attribute node object deposit set of node, belong to the attribute node object of source body as source
Property, and the attribute node object of target body and adjacent attribute node object are shown in the form of a table as objective attribute target attribute；
Step7, end；
Component interface includes syntactic information, semantic information, protocol information, test information；Syntactic information describes including function
And non-functional description, function description include method information, parameter information, text description, method information includes method name, returns to class
Type, parameter information include parameter name, parameter type；Non-functional description includes quality of service information and additional information, service quality
To define satisfaction of the user using service, including expense, time, reliability, credit worthiness, additional information includes opening information
Originator, version number, application field, deadline；Semantic information includes contract, and contract includes precondition, postcondition and not
Variant；Protocol information includes composite component, solid memder and flow address；Testing information includes test case, testing time, survey
Examination evaluation；
Component, which is realized, includes class；Contain essential information and the function description of class in class, the essential information of class include class name,
Parent name and class annotation, function description include method information and parameter information, and method information includes method name, return type and side
Method annotates, and parameter information includes parameter name, parameter type；
In the ontology model of component interface, method name, return type, parameter name, parameter type, text description, expense, when
Between, reliability, credit worthiness, developer, version number, application field, deadline, precondition, postcondition and invariant are multiple
Close component, solid memder and flow address, test case, testing time, test evaluation, the above node and be referred to as attribute section
Point；
Class name, parent name, class annotation in the ontology model that component is realized, method name, return type, method annotation, ginseng
Several, parameter type, above node are referred to as attribute node.
The step of display retrospective analysis result, is as follows：
Step1, modification content is determined by modifyJudge () method；
Step2, established by searchMap () method according to modification content and inquire about and judge to change whether content is reflecting
In firing table：
If changing content in the mapping table, step Step3 is performed；
If modification content in the mapping table, does not perform step Step4；
Step3, obtain the record in the attribute of component interface source with modification content in the mapping table by getMapsc ()
Set R, to each record R in Ri(i=1 ..., n), take out the set T that component realizes objective attribute target attributei, to TiTake and occur simultaneously
To impacted result set, step Step6 is then performed；
Step4, the component matched by modification content search of the findModify () method in component interface are real
It is existing, when lookup component is realized in component base, information in component interface is organized into m word first, the rope as query term Q
Draw list, component is realized as Di, similar value is obtained according to probability Similarity Measure, obtained in getSimilarity () method
Take and realized with component interface similarity highest component；
Calculate document DiWith the similarity between inquiry Q：
Similarity(Di, Q) and=Pr (Di|Q)
Using Bayesian formula, by conditional probability Pr (Di| Q) change into：
In above-mentioned formula, Pr (Q) is the prior probability for inquiring about Q, i.e. constant；Pr(Di) it is document DiPrior probability, institute
Ask Pr (Q | Di) it is document D after known inquiry Q occursiConditional probability；Conditional probability Pr (Q | Di) in, inquiry Q is one group
The index list of word, there is m word, therefore：
Pr(Q|Di)=Pr (W1,W2,…,Wm|Di)
If the component for finding matching is realized, step Step5 is performed；
If the component for not finding matching is realized, step Step7 is performed；
Step5, component realization in by findSC () method according to modification content retrieval, the result conduct retrieved
Impacted result set；
The impacted result set of Step6, display is as retrospective analysis result；
Step7, end.
A kind of component interface realizes the retrospective analysis system of mapping table with component, it is characterised in that：Including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Embodiment 2：As shown in figs. 1-11, ontological construction module 201 is after retrospective analysis system is opened, ontological construction mould
File Open module in block 201 can select to be used for component with opening members interface and component interface, file analyzing module
Interface and component, which are realized, establishes ontology model.The hierarchical structure realized according to component interface in the content of the invention and component, uses Prot é
The ontology edit tool that r é realize as component interface and component, passes through the concept hierarchy of Graphviz show ontologies, base
In body component interface as shown in figure 4, component based on body realize as shown in figure 5, finally with XML represent component interface and
The ontology model that component is realized：
Mapping establishes that module 202 is main to have used retrospect table generating method, the method information in main pin syntactic information, reflects
Firing table generating process is as shown in fig. 6, step is as follows：
(A) when source body and target ontological existence and be not space-time, by parserXML () method parse source body and
Target body；
(B) attribute node object in the body of source is obtained by getAttributenode () method：Method name and return
Type, the title FunctionalName and value getMaxNum of removing method name attribute node, return type attribute node
Title ReturnType and value int；
(C) according to source Noumenon property nodename FunctionalName, the ReturnType obtained, pass through
FindEqualname () method is searched whether there is corresponding node in the target Noumenon property nodename parsed；
(D) if corresponding attribute node title be present, target Noumenon property node is judged by matchValue () method
Value whether matched with getMaxNum and int；
(E) if attribute node value matches, xmlDepth () method extreme saturation target body is passed through；If attribute node
Value mismatches, then performs step (J)；
(F) target Noumenon property node FunctionalName, ReturnType are obtained by getPath () method
Most short undirected path is respectively：FunctionalName—FunctionalInformation—
FunctionalDescription-ClassDescription (as shown in Figure 7), ReturnType-
FunctionalInformation-FunctionalDescription-ClassDescription (as shown in Figure 8), from
And the public ancestor node of the attribute node matched, according to the definition of public ancestor node in the present invention：Most short undirected
Distance n and n0 farthest same node point in path, therefore attribute node FunctionalName, ReturnType public ancestors
Node is ClassDescription (as shown in Figure 9), obtains the adjacent attribute node under public ancestor node
FatherClassName, ClassName, ClassAnnotation, FunctionalAnnotation,
ParameterName, ParameterType } (as shown in Figure 10)；
(G) attribute node matched in target body is judged by semanticRelated () method
FunctionalName, ReturnType attribute node adjacent thereto FatherClassName, ClassName,
ClassAnnotation, FunctionalAnnotation, ParameterName, ParameterType } whether semantic phase
Close；
Wherein, attribute node FunctionalName, ReturnType of matching and any adjacent attribute node
FatherClassName, ClassName, ClassAnnotation, FunctionalAnnotation,
ParameterName, ParameterType } public ancestor node under all nodes composition tree, its recently public ancestors
And if only if in all nodes under node attribute node title FunctionalName, ReturnType,
FatherClassName, ClassName, ClassAnnotation, FunctionalAnnotation, ParameterName,
ParameterType, exist and uniquely, therefore matched node is semantic related to adjacent attribute node；
(H) attribute node of target body is obtained in the adjacent of identical father node by getRelatedNode () method
Attribute node ClassName, FatherClassName；
(I) by crateTable () method by the attribute node object of the source body of acquisition (FunctionalName,
ReturnType), the attribute node object (FunctionalName) of corresponding target body and adjacent attribute node
(ClassName, FatherClassName) object is stored in set of node, using the attribute node object of source body as source attribute, and
The attribute node object of target body and adjacent attribute node object are shown, method information as objective attribute target attribute with sheet form
Mapping table it is as shown in table 1；
(J) terminate.
Table 1
Following retrospective analysis module 203 is traced back in component realization, and show when component interface is changed by table 1
Collection is influenceed by component interface modification.When being changed in component interface, by retrospective analysis method in 203 modules, such as Figure 11 institutes
Show, step is as follows：
(1) modification content --- return type ReturnType is determined by modifyJudge () method；
(2) inquiry ReturnType is established according to modification content by searchMap () method and judges that changing content is
It is no in the source attribute InterfaceSpecification of table 1：
Content ReturnType is changed in the source attribute InterfaceSpecification of table 1 ReturnType,
Then perform step (3)；
(3) obtain component interface source attribute InterfaceSpecification's in table 1 by getMapsc ()
Have in ReturnType modification content ReturnType set of records ends R (getMaxNum, int, Max, Null,
GetMaxNum) }, to unique record R, the set T { (Max, Null, getMaxNum) } that component realizes objective attribute target attribute is taken out, it is right
Ti takes common factor to obtain impacted result set, i.e. { (Max, Null, getMaxNum) }；
(4) show that impacted result set { (Max, Null, getMaxNum) } is used as retrospective analysis result；
(5) terminate.
Embodiment 3：As shown in figs. 1-11, a kind of component interface realizes the retrospective analysis method of mapping table with component, including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Component interface is referred to as source body, and component, which is realized, is referred to as target body, and the component interface realizes that generation is reflected with component
The method of firing table, comprises the following steps：
Step1, when source body and target ontological existence and be not space-time, pass through parserXML () method and parse source body
With target body；
Step2, attribute node object in the body of source, taking-up attribute section are obtained by getAttributenode () method
The title and value of point；
Step3, according to the source Noumenon property nodename obtained, searched and parsed by findName () method
Target Noumenon property nodename in whether there is corresponding node：
If corresponding attribute node title be present, source body and target body category are judged by matchValue () method
Whether the value of property node matches：If attribute node value matches, pass through xmlDepth () method extreme saturation target body；If
Attribute node value mismatches, then performs step Step7；
If in the absence of corresponding attribute node title, step Step7 is performed；
Step4, pass through each target Noumenon property node of getPath () method acquisition to the most short undirected road of root node
Footpath, so as to the public ancestor node of attribute node matched, pass through getNbnode () method and obtain public ancestor node
Adjacent attribute node；Wherein, all properties node under public ancestor node is referred to as adjacent in addition to match attribute node
Attribute node；It is an XML document tree to make T, and n and n0 are two nodes in T, and n and n0 most short undirected path are removed by n and n0
The path composition that top outside root node arrives n and n0 respectively, public ancestor node refer in most short undirected path distance n and
Same node point farthest n0；
Step5, by semanticRelated () method judge that the attribute node that is matched in target body is adjacent thereto
Whether attribute node is semantic related：
If semantic related, the attribute node of target body is obtained in identical father by getRelatedNode () method
The adjacent attribute node of node；If semantic uncorrelated, step Step7 is performed；
Wherein, the tree of all nodes composition under node t1, node t2 public ancestor node, is expressed as relational tree T
And if only if in all nodes under (t1, t2), node t1 and node t2 nearest public ancestor node node t1 or node t2
Title exist and unique, claim node t1 to node t2 to be semantic related；
Step6, by crateTable () method by the attribute node object of the source body of acquisition, corresponding target sheet
The attribute node object of body and adjacent attribute node object deposit set of node, belong to the attribute node object of source body as source
Property, and the attribute node object of target body and adjacent attribute node object are shown in the form of a table as objective attribute target attribute；
Step7, end；
Component interface includes syntactic information, semantic information, protocol information, test information；Syntactic information describes including function
And non-functional description, function description include method information, parameter information, text description, method information includes method name, returns to class
Type, parameter information include parameter name, parameter type；Non-functional description includes quality of service information and additional information, service quality
To define satisfaction of the user using service, including expense, time, reliability, credit worthiness, additional information includes opening information
Originator, version number, application field, deadline；Semantic information includes contract, and contract includes precondition, postcondition and not
Variant；Protocol information includes composite component, solid memder and flow address；Testing information includes test case, testing time, survey
Examination evaluation；
Component, which is realized, includes class；Contain essential information and the function description of class in class, the essential information of class include class name,
Parent name and class annotation, function description include method information and parameter information, and method information includes method name, return type and side
Method annotates, and parameter information includes parameter name, parameter type；
In the ontology model of component interface, method name, return type, parameter name, parameter type, text description, expense, when
Between, reliability, credit worthiness, developer, version number, application field, deadline, precondition, postcondition and invariant are multiple
Close component, solid memder and flow address, test case, testing time, test evaluation, the above node and be referred to as attribute section
Point；
Class name, parent name, class annotation in the ontology model that component is realized, method name, return type, method annotation, ginseng
Several, parameter type, above node are referred to as attribute node.
The step of display retrospective analysis result, is as follows：
Step1, modification content is determined by modifyJudge () method；
Step2, established by searchMap () method according to modification content and inquire about and judge to change whether content is reflecting
In firing table：
If changing content in the mapping table, step Step3 is performed；
If modification content in the mapping table, does not perform step Step4；
Step3, obtain the record in the attribute of component interface source with modification content in the mapping table by getMapsc ()
Set R, to each record R in Ri(i=1 ..., n), take out the set T that component realizes objective attribute target attributei, to TiTake and occur simultaneously
To impacted result set, step Step6 is then performed；
Step4, the component matched by modification content search of the findModify () method in component interface are real
It is existing, when lookup component is realized in component base, information in component interface is organized into m word first, the rope as query term Q
Draw list, component is realized as Di, similar value is obtained according to probability Similarity Measure, obtained in getSimilarity () method
Take and realized with component interface similarity highest component；
Calculate document DiWith the similarity between inquiry Q：
Similarity(Di, Q) and=Pr (Di|Q)
Using Bayesian formula, by conditional probability Pr (Di| Q) change into：
In above-mentioned formula, Pr (Q) is the prior probability for inquiring about Q, i.e. constant；Pr(Di) it is document DiPrior probability, institute
Ask Pr (Q | Di) it is document D after known inquiry Q occursiConditional probability；Conditional probability Pr (Q | Di) in, inquiry Q is one group
The index list of word, there is m word, therefore：
Pr(Q|Di)=Pr (W1,W2,…,Wm|Di)
If the component for finding matching is realized, step Step5 is performed；
If the component for not finding matching is realized, step Step7 is performed；
Step5, component realization in by findSC () method according to modification content retrieval, the result conduct retrieved
Impacted result set；
The impacted result set of Step6, display is as retrospective analysis result；
Step7, end.
Embodiment 4：As shown in figs. 1-11, a kind of component interface realizes the retrospective analysis system of mapping table with component, and it is special
Sign is：Including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Above in conjunction with accompanying drawing to the present invention embodiment be explained in detail, but the present invention be not limited to it is above-mentioned
Embodiment, can also be before present inventive concept not be departed from those of ordinary skill in the art's possessed knowledge
Put and make a variety of changes.
Claims (3)
1. a kind of component interface realizes the retrospective analysis method of mapping table with component, it is characterised in that：Including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result；
Component interface is referred to as source body, and component, which is realized, is referred to as target body, and the component interface realizes generation mapping table with component
Method, comprise the following steps：
Step1, when source body and target ontological existence and be not space-time, pass through parserXML () method and parse source body and mesh
Sample body；
Step2, attribute node object in the body of source obtained by getAttributenode () method, take out the name of attribute node
Claim and be worth；
Step3, according to the source Noumenon property nodename obtained, searched by findName () method in the target parsed
It whether there is corresponding node in Noumenon property nodename：
If corresponding attribute node title be present, source body and target Noumenon property node are judged by matchValue () method
Value whether match：If attribute node value matches, pass through xmlDepth () method extreme saturation target body；If attribute section
Point value mismatches, then performs step Step7；
If in the absence of corresponding attribute node title, step Step7 is performed；
Step4, each target Noumenon property node is obtained by getPath () method to the most short undirected path of root node, from
And the public ancestor node of the attribute node matched, the adjacent of public ancestor node is obtained by getNbnode () method
Attribute node；Wherein, all properties node under public ancestor node is referred to as adjacent attribute section in addition to match attribute node
Point；It is an XML document tree to make T, and n and n0 are two nodes in T, and root node is removed in n and n0 most short undirected path by n and n0
The outer top path composition for arriving n and n0 respectively, public ancestor node refer to that distance n and n0 are farthest in most short undirected path
Same node point；
Step5, the attribute node attribute section adjacent thereto for judging to match in target body by semanticRelated () method
Whether point is semantic related：
If semantic related, the attribute node of target body is obtained in identical father node by getRelatedNode () method
Adjacent attribute node；If semantic uncorrelated, step Step7 is performed；
Wherein, under node t1, node t2 public ancestor node all nodes composition tree, be expressed as relational tree T (t1,
T2), and if only if in all nodes under node t1 and node t2 nearest public ancestor node node t1 or node t2 name
Claim to exist and unique, title node t1 is semantic related to node t2；
Step6, by crateTable () method by the attribute node object of the source body of acquisition, the category of corresponding target body
Property node object and adjacent attribute node object deposit set of node, using the attribute node object of source body as source attribute, and
The attribute node object of target body and adjacent attribute node object are shown in the form of a table as objective attribute target attribute；
Step7, end；
Component interface includes syntactic information, semantic information, protocol information, test information；Syntactic information include function description and it is non-
Function describes, and function description includes method information, parameter information, text description, and method information includes method name, return type,
Parameter information includes parameter name, parameter type；Non-functional description includes quality of service information and additional information, quality of service information
To define satisfaction of the user using service, including expense, time, reliability, credit worthiness, additional information include exploitation
Person, version number, application field, deadline；Semantic information includes contract, and contract includes precondition, postcondition and constant
Formula；Protocol information includes composite component, solid memder and flow address；Testing information includes test case, testing time, test
Evaluation；
Component, which is realized, includes class；Essential information and the function description of class are contained in class, the essential information of class includes class name, parent
Name and class annotation, function description include method information and parameter information, and method information includes method name, return type and method note
Release, parameter information includes parameter name, parameter type；
In the ontology model of component interface, method name, return type, parameter name, parameter type, text description, expense, the time,
Reliability, credit worthiness, developer, version number, application field, deadline, precondition, postcondition and invariant are compound
Component, solid memder and flow address, test case, testing time, test evaluation, the above node are referred to as attribute node；
Class name, parent name, class annotation in the ontology model that component is realized, method name, return type, method annotation, parameter name,
Parameter type, above node are referred to as attribute node.
2. component interface according to claim 1 realizes the retrospective analysis method of mapping table with component, it is characterised in that：Institute
The step of stating display retrospective analysis result is as follows：
Step1, modification content is determined by modifyJudge () method；
Step2, established by searchMap () method according to modification content and whether inquire about and judge to change content in mapping table
In：
If changing content in the mapping table, step Step3 is performed；
If modification content in the mapping table, does not perform step Step4；
Step3, obtain the set of records ends in the attribute of component interface source with modification content in the mapping table by getMapsc ()
R, to each record R in Ri(i=1 ..., n), take out the set T that component realizes objective attribute target attributei, to TiTake common factor obtain by
The result set of influence, then perform step Step6；
Step4, the component matched by modification content search of the findModify () method in component interface are realized, in structure
Component is searched in part storehouse when realizing, information in component interface is organized into m word first, as query term Q index list,
Component is realized as Di, similar value is obtained according to probability Similarity Measure, with the acquisition of getSimilarity () method and component
Interface similarity highest component is realized；
Calculate document DiWith the similarity between inquiry Q：
Similarity(Di, Q) and=Pr (Di|Q)
Using Bayesian formula, by conditional probability Pr (Di| Q) change into：
<mrow>
<mi>Pr</mi>
<mrow>
<mo>(</mo>
<msub>
<mi>D</mi>
<mi>i</mi>
</msub>
<mo>|</mo>
<mi>Q</mi>
<mo>)</mo>
</mrow>
<mo>=</mo>
<mfrac>
<mrow>
<mi>Pr</mi>
<mrow>
<mo>(</mo>
<mi>Q</mi>
<mo>|</mo>
<msub>
<mi>D</mi>
<mi>i</mi>
</msub>
<mo>)</mo>
</mrow>
<mi>Pr</mi>
<mrow>
<mo>(</mo>
<msub>
<mi>D</mi>
<mi>i</mi>
</msub>
<mo>)</mo>
</mrow>
</mrow>
<mrow>
<mi>Pr</mi>
<mrow>
<mo>(</mo>
<mi>Q</mi>
<mo>)</mo>
</mrow>
</mrow>
</mfrac>
</mrow>
In above-mentioned formula, Pr (Q) is the prior probability for inquiring about Q, i.e. constant；Pr(Di) it is document DiPrior probability, it is required
Pr(Q|Di) it is document D after known inquiry Q occursiConditional probability；Conditional probability Pr (Q | Di) in, inquiry Q is one group of word
Index list, there is m word, therefore：
Pr(Q|Di)=Pr (W1,W2,…,Wm|Di)
If the component for finding matching is realized, step Step5 is performed；
If the component for not finding matching is realized, step Step7 is performed；
Step5, component realization in by findSC () method according to modification content retrieval, the result retrieved is as impacted
Result set；
The impacted result set of Step6, display is as retrospective analysis result；
Step7, end.
3. a kind of realize that the retrospective analysis method of mapping table is real using component interface according to claim 1 or 2 and component
Existing system, it is characterised in that：Including：
Ontological construction module, ontology model is established for being realized to component interface and component, and represented with XML；
Module is established in mapping, for realizing generation mapping table according to the component interface using ontology describing and component；
Retrospective analysis module, for analyzing and showing retrospective analysis result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510213960.0A CN104850399B (en) | 2015-04-30 | 2015-04-30 | A kind of component interface realizes the retrospective analysis method and system of mapping table with component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510213960.0A CN104850399B (en) | 2015-04-30 | 2015-04-30 | A kind of component interface realizes the retrospective analysis method and system of mapping table with component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104850399A CN104850399A (en) | 2015-08-19 |
| CN104850399B true CN104850399B (en) | 2018-03-06 |
Family
ID=53850062
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510213960.0A Active CN104850399B (en) | 2015-04-30 | 2015-04-30 | A kind of component interface realizes the retrospective analysis method and system of mapping table with component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104850399B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108376101B (en) * | 2018-01-23 | 2022-06-07 | 珠海金山网络游戏科技有限公司 | Method and device for managing resources in Unity3D runtime |
| CN109165351B (en) * | 2018-08-27 | 2021-11-26 | 成都信息工程大学 | Service component search recommendation method based on semantics |
| CN110097375A (en) * | 2019-03-25 | 2019-08-06 | 安徽中医药大学 | A kind of Chinese medicine quality tracing modeling method that data granularity is gradable |
| CN110968101A (en) * | 2019-12-19 | 2020-04-07 | 南京航空航天大学 | Unmanned vehicle behavior decision method based on ontology and Bayesian network |
| CN111427568A (en) * | 2020-03-30 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Interface configuration method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7206726B2 (en) * | 2002-03-20 | 2007-04-17 | Composite Technologies, Corporation | Method of designing partially composite concrete sandwich panels and such panels |
| CN102222005B (en) * | 2011-07-12 | 2013-10-30 | 铜陵玉成软件科技有限责任公司 | Service model-oriented software running platform, running mode and development method |
-
2015
- 2015-04-30 CN CN201510213960.0A patent/CN104850399B/en active Active
Non-Patent Citations (3)
| Title |
|---|
| An Analysis of the Requirements Traceability Problem;Orlena C.Z. Gotel et al;《Requirtments 1994.，Proceedings or the First International Conference on.IEEE》;19941231;第1994年卷;第94-101页 * |
| 一种XML的树匹配改进方法;于亚君等;《计算机工程与应用》;20121030;第48卷(第20期);第177-210页 * |
| 本体论与构件复用;王良斌等;《计算机工程与应用》;20040730;第2004年卷(第14期);第53-56页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104850399A (en) | 2015-08-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104850399B (en) | A kind of component interface realizes the retrospective analysis method and system of mapping table with component | |
| CN103631882B (en) | Semantization service generation system and method based on graph mining technique | |
| La Rosa et al. | Merging business process models | |
| Brockmans et al. | Semantic Alignment of Business Processes. | |
| Stumptner et al. | On the road to behavior-based integration | |
| Kalenkova et al. | Discovering high-level BPMN process models from event data | |
| Al-Obeidallah et al. | A survey on design pattern detection approaches | |
| Landolfi et al. | An ontology based semantic data model supporting a MaaS digital platform | |
| Castano et al. | On the ontology instance matching problem | |
| Weinreich et al. | A fresh look at codification approaches for sakm: A systematic literature review | |
| Kő et al. | A development method for ontology based business processes | |
| van der Aalst | Discovering directly-follows complete Petri nets from event data | |
| El-Boussaidi et al. | Detecting patterns of poor design solutions using constraint propagation | |
| Zhang et al. | Activity based CIM modeling and transformation for business process systems | |
| Wilberg et al. | Development of a catalogue supporting idea generation for internet of things use cases | |
| Fiorini et al. | Process reuse architecture | |
| Paim et al. | Towards a methodology for requirements analysis of data warehouse systems | |
| Wang et al. | Using workflow patterns to model and validate service requirements | |
| Coskuncay et al. | Transformation from business process models to process ontology: A case study | |
| M'Baba et al. | Blockchain logging for process mining: a systematic review | |
| Pinciroli et al. | Aspect-Oriented Business Process Modeling Approaches: An assessment of AOP4ST | |
| Florez et al. | Modeling and Analyzing Imperfection in Enterprise Models. | |
| Umoh et al. | REFINTO: An ontology-based requirements engineering framework for business-IT alignment in financial services organizations | |
| Feng et al. | ASMaaS: Automatic Semantic Modeling as a Service | |
| CN109299381A (en) | A kind of software defect retrieval and analysis system and method based on semantic concept |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |