CN113342331A - Evolution analysis method of ecology-oriented software service system - Google Patents
Evolution analysis method of ecology-oriented software service system Download PDFInfo
- Publication number
- CN113342331A CN113342331A CN202110558968.6A CN202110558968A CN113342331A CN 113342331 A CN113342331 A CN 113342331A CN 202110558968 A CN202110558968 A CN 202110558968A CN 113342331 A CN113342331 A CN 113342331A
- Authority
- CN
- China
- Prior art keywords
- evolved
- target
- model
- value
- initial
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004458 analytical method Methods 0.000 title claims description 23
- 238000000034 method Methods 0.000 claims abstract description 108
- 230000008569 process Effects 0.000 claims abstract description 60
- 239000012634 fragment Substances 0.000 claims description 38
- 238000004364 calculation method Methods 0.000 claims description 10
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 29
- 235000019580 granularity Nutrition 0.000 description 11
- 230000000694 effects Effects 0.000 description 6
- 238000011160 research Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 230000004308 accommodation Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000036541 health Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000007717 exclusion Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000013598 vector Substances 0.000 description 2
- 241000282887 Suidae Species 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000005764 inhibitory process Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001629 suppression Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000002195 synergetic effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/72—Code refactoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/12—Hotels or restaurants
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an evolution method of an ecology-oriented software service system, which comprises the following steps: 1: obtaining a domain base model library, 2: acquiring a software service system model to be evolved, 3: obtaining an evolved software service system value model; 4: reconstructing a software service system model to be evolved; 5: determining a value evolution point based on the value model after evolution and the initial value model to obtain a value target to be evolved; 6: selecting a corresponding evolution mode based on the value target to be evolved, 7: acquiring an evolved target model based on a population evolution method; 8: acquiring an evolved target model 9 based on a community-type evolution method: and acquiring an evolved flow model based on the evolved target model, and finishing the evolution of the software service system facing the ecology. The method is beneficial to guiding the evolution process of the software service system facing the multi-field evolution requirement.
Description
Technical Field
The invention relates to the technical field of modern service industry, software ecosystem and service calculation, in particular to an evolution analysis method of an ecology-oriented software service system.
Background
The cooperative win-win and value-creation are important characteristics of the development of the modern service industry. With the development of internet technology, the great demand of increasing users makes modern enterprises no longer concentrate on their own fields, and more tend to cooperate with each other continuously, so that the business mode and business boundary are extended continuously to create greater business value. The interaction among services, enterprises and users connects the modern service industry into a highly-relevant value co-creation complex ecosystem, the phenomena of cross-domain cooperation and service evolution emerge continuously, and the development of a software ecosystem is promoted.
In a software ecosystem, different roles have complex interaction relations, more human activities enable user requirements to show uncertainty and dynamic variability of multiple fields, however, an initial software service system often faces to a single field to meet the user requirements and cannot meet the user requirements facing to cross fields, so that the software service system needs to face to other fields to continuously evolve to meet the complex requirements of users, and further the value of the software ecosystem is increased. Under the background, the analysis of the evolution behavior of the software service system is urgently needed, so as to guide the realization of the healthy evolution and the stable evolution of the software ecosystem.
Value realization is the overall health development goal of software ecosystems. From the value perspective, Touliou et al research developers make different value propositions on the influence of the health of the software ecosystem; haile et al evaluate the influence of a software ecosystem on user value acquisition based on a utility theory, a technical acceptance theory and a structural equation model of a network externality theory; haile et al also describes, in other studies, relationships between stakeholders (e.g., program service users, service developers, and service platform providers) in a software ecosystem using a value creation model that can perform value calculations for different stakeholders in the software ecosystem, and can also assist in inferring the relative impact of different factors on the value evolution of the stakeholders of the software service platform. Pant et al, in consideration of complementarity of different enterprises and software products in a cooperative competition relationship, proposed a software ecosystem value modeling analysis framework that fuses an i-target model and an e3value, and evaluated the impact on value collaborative creativity by comparing complementary alternative combinations of different software products in a software ecosystem.
In recent years, the evolution of the software ecosystem obtains the research and attention of a plurality of scholars, for example, Andre Hora et al analyze the influence of the evolution of the API on the software service ecosystem, and Alexandre observes the evolution situation of the software service ecosystem by analyzing the dependence between a software package and a class library. Valentina concerns the impact of technical debt problems on the evolution of software ecosystems. Tommen analyzed the problem of co-evolution of the software ecosystem by analogy with the software ecosystem and the natural ecosystem. Djamel et al studied the problem of code co-evolution as software service systems evolve. Qing et al identified and detected evolution events of the software ecosystem in gitub through a community detection algorithm, and analyzed the characteristics of software ecosystem evolution from three aspects of ecosystem structure, scale and activity. Teixeira et al believe that the evolution analysis of a software ecosystem should not only be limited to its internal boundaries, but also require attention to the synergistic evolution between different software ecosystems, and discover and discuss the mechanisms and factors of the interaction of seven software ecosystems.
Although the research focuses on value realization and evolution analysis of the software ecosystem, research on an evolution mode and a method of the software ecosystem under the cross-domain characteristic in the modern service industry does not appear. That is, the method in the prior art cannot realize automatic evolution of cross-domain services.
Disclosure of Invention
Aiming at the requirement of a software service system for cross-domain evolution in a software ecosystem, the invention provides an evolution method of the software service system facing to ecology, which can realize the automatic evolution of the software service system facing to multi-domain services in the software service ecosystem, thereby guiding the software service system to complete the expansion evolution of the core service of the software service system facing to other domain services, and having good practicability.
The invention provides an evolution analysis method of an ecology-oriented software service system, which comprises the following steps: s1: acquiring a field basic model library, including a basic value model library, a basic target model library and a basic flow model library of different fields of a software ecosystem; s2: acquiring an initial software service system model which needs to be evolved under the evolution requirement, wherein the initial software service system model comprises an initial value model, an initial target model and an initial flow model, and the initial software service system model is used as a software service system model to be evolved; s3: obtaining an evolved value model obtained by a software service system through value realization; s4: reconstructing a software service system model to be evolved, specifically comprising reconstructing an initial value model and an initial target model, and segmenting an evolved value model; s5: determining a value evolution point based on the value model after evolution and the initial value model to obtain a value target to be evolved; s6: selecting a corresponding evolution mode based on the value target to be evolved, wherein the evolution mode comprises a population evolution method and a community evolution method, if the population evolution method is selected, executing S7, and if the community evolution method is selected, executing S8; s7, carrying out evolution operation on the initial target model based on a population evolution method to obtain an evolved target model; s8, carrying out evolution operation on the initial target model based on a community-type evolution method to obtain an evolved target model; s9: and acquiring the process model after evolution based on the target model after evolution, and finishing the evolution of the software service system facing the ecology.
One or more technical solutions in the embodiments of the present application have at least one or more of the following technical effects:
the invention provides an evolution method of an ecology-oriented software service system, which comprises two evolution modes of population evolution and community evolution and is beneficial to guiding the evolution process of the software service system facing to the multi-field evolution requirement. And based on the method, the method is helpful for helping demand analysts to obtain the potential evolution direction of the software service system from the ecological perspective by taking the value creation of the software service system as a drive, and is helpful for assisting the health evolution analysis of the software ecosystem to realize value increment.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a general framework diagram of an evolution method of an ecology-oriented software service system according to the present invention.
FIG. 2 is a value model evolution modeling interface for the demand evolution modeling system developed by the present invention.
FIG. 3 is a target model evolution modeling interface for the demand evolution modeling system developed by the present invention.
FIG. 4 is a flow model evolution modeling interface for the demand evolution modeling system developed by the present invention.
FIG. 5 is a schematic illustration of a domain base model library stored by the demand evolution modeling system developed by the present invention.
Fig. 6 is an initial value model diagram of an example of "aviation travel service and insurance service provided by the pig software ecosystem" according to the present invention.
FIG. 7 is a diagram of an evolved value model of an example of the "aviation travel service and insurance service provided by the pig software ecosystem" of the present invention.
FIG. 8 is a diagram of an evolved value model after reconstruction of an "aviation travel service and insurance service provided by the pig software ecosystem" example of the present invention.
FIG. 9 is a diagram of an initial target model after reconstruction of an example of "aviation travel service and insurance service provided by the pig software ecosystem" according to the present invention.
Fig. 10 is a schematic diagram of acquiring a value target to be evolved in an example of "providing aviation travel service and insurance service by a pig software ecosystem" according to the present invention.
Fig. 11 is a schematic diagram of determining a target of a point to be evolved in an example of "providing aviation travel service and insurance service by a pig software ecosystem" according to the present invention.
FIG. 12 is a schematic diagram of adding an initial target to be evolved into an initial character target model segment according to an embodiment of the invention, namely the pig software ecosystem provides aviation travel service and insurance service
FIG. 13 is a schematic diagram of example search of target model fragments to be evolved in the case of "providing aviation travel service and insurance service by pig software ecosystem" according to the present invention
FIG. 14 is a schematic diagram of adding target model fragments to be evolved into initial role target model fragments in the example of "providing aviation travel service and insurance service by pig software ecosystem" of the present invention
Fig. 15 is a schematic diagram of an evolved target model obtained by updating a corresponding dependency of an initial role target model in an "aviation travel service and insurance service provided by a pig software ecosystem" example according to the present invention.
Fig. 16 is a schematic diagram of an initial flow model of an example of the "aviation travel service and insurance service provided by the pig software ecosystem" according to the present invention.
Fig. 17 is a schematic diagram of an example of "the pig software ecosystem provides aviation travel service and insurance service" of the invention as an evolved flow model.
Fig. 18 is a diagram of an initial value model of an example of the "pig software ecosystem offering airline reservation and hotel reservation services" of the present invention.
FIG. 19 is a diagram of an evolved value model of an example of the "pig software ecosystem offering airline reservation and hotel reservation services" of the present invention.
FIG. 20 is a diagram of an evolved value model after reconstruction of an "pig software ecosystem offers airline reservation and hotel reservation services" example of the present invention.
FIG. 21 is a diagram of an initial target model after reconstruction of an example of the "pig software ecosystem offering airline reservation and hotel reservation services" of the present invention.
FIG. 22 is a schematic diagram of obtaining a value target to be evolved in an example of "a flight software ecosystem provides airline reservation and hotel reservation services" according to the present invention.
Fig. 23 is a schematic diagram of adding a to-be-evolved value target to the position of the root target of the initial target model as an initial to-be-evolved target in the case of providing airline ticket booking and hotel booking services by the pig software ecosystem according to the embodiment of the present invention.
FIG. 24 is a schematic diagram of an example of finding a target model segment to be evolved in an embodiment of the invention, namely that the pig software ecosystem provides airline ticket booking and hotel booking services.
FIG. 25 is a schematic diagram of adding an object model segment to be evolved to an initial role object model segment in an example of "airline ticket booking and hotel booking services provided by the pig software ecosystem" according to the present invention
Fig. 26 is a schematic diagram of an evolved target model obtained by updating corresponding dependencies for an initial role target model in an "air ticket booking and hotel booking service provided by a pig software ecosystem" example according to the present invention.
Fig. 27 is a schematic diagram of an initial flow model of an example of the "pig software ecosystem offering airline reservation and hotel reservation services" of the present invention.
Fig. 28 is a schematic diagram of an example of "the pig software ecosystem provides airline ticket booking and hotel booking services" as an evolved process model according to the present invention.
Detailed Description
The embodiment of the invention provides an evolution analysis method of an ecology-oriented software service system, which comprises the following steps:
s1: acquiring a field basic model library, including a basic value model library, a basic target model library and a basic flow model library of different fields of a software ecosystem; s2: acquiring an initial software service system model which needs to be evolved under the evolution requirement, wherein the initial software service system model comprises an initial value model, an initial target model and an initial flow model, and the initial software service system model is used as a software service system model to be evolved; s3: obtaining an evolved value model obtained by a software service system through value realization; s4: reconstructing a software service system model to be evolved, specifically comprising reconstructing an initial value model and an initial target model, and segmenting an evolved value model; s5: determining a value evolution point based on the value model after evolution and the initial value model to obtain a value target to be evolved; s6: selecting a corresponding evolution mode based on the value target to be evolved, wherein the evolution mode comprises a population evolution method and a community evolution method, if the population evolution method is selected, executing S7, and if the community evolution method is selected, executing S8; s7, carrying out evolution operation on the initial target model based on a population evolution method to obtain an evolved target model; s8, carrying out evolution operation on the initial target model based on a community-type evolution method to obtain an evolved target model; s9: and acquiring the process model after evolution based on the target model after evolution, and finishing the evolution of the software service system facing the ecology.
First, the related concepts and features related to the present application are explained as follows:
VM { Role, valuegol, valueacity, ValueObject, valuearltion, Domain }, where Role is a participating Role in the software ecosystem; ValueGoal is a value target to be realized by a role, and ValueActivity is a value activity to be performed by the role for realizing the value target; ValueObject is a value object, namely resource transfer, involved in the progress of a value activity; ValueRealtion is a relationship between value targets, including AND, OR, promotion, suppression, mutual exclusion, AND dependency; domain is the Domain to which the value target belongs.
Definition 2, target model gm (goal model):
GM { Role, rolleal, Resource, Realtion, Domain, valuegal }, where Role is a participating Role in the software ecosystem; RoleGoal is a target to be realized by a role, AND comprises a functional target, a non-functional target AND an operability target, Resource is a Resource transmitted among participants, AND relationship is a relationship among targets, AND comprises AND, OR, promotion, inhibition, mutual exclusion AND dependence; domain is the Domain to which the target belongs, and ValueGoal is the value target that the role target can achieve. The flow model follows the BPMN specification in the field of demand engineering.
In the invention, the software service system is a research object with domain characteristics and role characteristics, and the value model, the target model and the process model can be divided into model segments with role granularity from the granularity based on roles, so that the requirement design is supported by better multiplexing, and related elements such as different value models, target models and the like of the roles under the granularity can belong to different domains. Therefore, the invention provides a role-based model segment division method. The role-based model fragment dividing method divides a model based on the granularity of roles to obtain role-based model fragments, and specifically comprises a role value model fragment and a role target model fragment. The specific definition is as follows:
definition 3, role value Model Fragment VMFR (value Model Fragment of role): each role and its associated value targets, value activities, value objects and relationships make up a role value Model segment, which can be viewed as a value Model for only one role, which can be expressed as VMFR (value Model Fragment of role). A character value model segment, such as character r1, is VMFR (r1) ═ VM | VM.
Definition 4, role target Model Fragment gmfr (goal Model Fragment of role): each role and its associated targets, resources and relationships constitute a role target model segment, which can be viewed as a target model for only one role, and can represent gmfr (goal model fragment of role). A character target model segment, such as character r1, is GMFR (r1) ═ GM | GM.
Since the same role in a software ecosystem may belong to different domains, its value and goal also exist across domain features. Therefore, value targets in one character value model segment may belong to different fields respectively, and targets in one character target model segment may belong to multiple fields.
Definition 5, to-evolve value target nvg (new value goal to be evolved):
the value target to be evolved is a value target in the value model after the evolution, but not a value target in the initial value model. Namely NVG (New value goal to be evolved),
wherein, the EVM (evolution Value model) is an evolved Value model; OVN (Ori)A digital Value Model) is an initial Value Model before evolution. The set of all value targets to be evolved is NVGL (new value goal List to be evolved), NVGL ═ NVG }.
Definition 6, initial Role to evolve or (original Role to be evolved): the role is a subordinate role of the value target to be evolved in the evolved value model, and the role is also an existing role in the initial value model. OR { evm.role () | evm.role () ∈ ovm.role (); roll (). valuegol (). epsilon NVGL }
Definition 7, new Role to be evolved nr (new Role to be evolved): the role is a subordinate role of the target to be evolved in the evolved value model, but the role is not an existing role in the initial value model. Namely, it is
Definition 9, to-be-evolved initial Domain od (original Domain to be evolved): the domain is a subordination domain of a value target to be evolved in the value model after evolution, and is also an existing domain in the initial value model. Namely:
OD＝{EVM.domain()|EVM.domain()∈OVM.domain()；EVM.domain().valueGoal()
∈NVGL}
definition 10, new Domain to be evolved nd (new Domain to be evolved): the field is a subordination field of a value target to be evolved in the value model after evolution, but is not an existing field in the initial value model. Namely, it is
Definition 11, area to evolve: the initial domain OD to be evolved and the new domain ND to be evolved are collectively called the domain to be evolved. The set of all the domains to be evolved is EDL (domain list to be evolved), EDL ═ OD, ND }.
Fig. 1 is a general framework diagram of an evolution method of an ecology-oriented software service system according to the present invention, and in a specific implementation process, the field basis model library obtained in step S1 includes a basis value model library, a basis target model library and a basis process model library of different fields of a software ecosystem. In the process of demand modeling, many researches reuse target model fragments, process model fragments and the like to improve modeling design efficiency. In order to quickly realize the process of the software service system facing other fields to evolve, the invention reuses the model segments in different fields as the field basic model segments for reference, namely, the related model segments in different fields existing in the software ecosystem are used as a field basic model library. Step S2: acquiring a software service system model to be evolved, namely acquiring an initial software service system model which needs to be evolved facing other fields under the requirement of evolution, wherein the initial software service system model comprises an initial Value model OVM (original Value model), an initial target model OGM (original Goal model) and an initial Process model OPM (original Process model). Step S3: obtaining an evolved Value model of the software service system, namely an evolved Value model EVM (evolved Value model) after the software service system realizes evolution through Value. Step S4: and reconstructing the value model after the evolution and the software service system model to be evolved to obtain model segments with different granularities. The method specifically comprises the step of carrying out fragment division on the value model after evolution, the initial value model and the initial target model.
In one embodiment, S4 specifically includes:
s4.1: reconstructing the value model after evolution to obtain the value model fragment after evolution of the role granularity;
s4.2: reconstructing the initial value model to obtain initial value model fragments of role granularity;
s4.3: and reconstructing the initial target model to obtain the initial target model segment of the role granularity.
In a specific implementation process, S4.1 specifically includes: dividing the evolved Value Model based on the role granularity to obtain an evolved role Value Model Fragment EVMFR (evolved Value Model Fragment of role) of different roles. If the set of roles in the evolved value model is Role ═ r1, r2, r3 … …, the corresponding evolved character value model segments are EVMFR (r1), EVMFR (r2), EVMFR (r3) … …, respectively, and the set of evolved character value model segments is EVMFRs ═ { EVMFR (r1), EVMFR (r2), EVMFR (r3) … … }.
S4.2 specifically comprises: dividing the initial Value Model based on the role granularity to obtain initial role Value Model fragments OVMFR (original Value Model Fragment of role) of different roles. If the set of roles in the initial value model is Role ═ r1, r2, r3 … …, then the corresponding initial Role value model segments are respectively OVMFR (r1), OVMFR (r2), OVMFR (r3) …, and the set of initial Role value model segments is OVMFRs ═ OVMFR (r1), OVMFR (r2), OVMFR (r3) … ….
S4.3 specifically comprises: dividing the initial target Model based on the role granularity to obtain initial target Model fragments OGMFR (original Goal Model Fragment of role) of different roles. If the Role set in the initial target model is Role ═ { r1, r2, r3 … … }, the corresponding initial character target model segments are OGMFR (r1), OGMFR (r2), and OGMFR (r3) … …, respectively.
In one embodiment, S5 specifically includes:
s5.1: traversing the initial value model to obtain all value target lists in the initial value model;
s5.2: traversing the value model after evolution, and acquiring all value target lists in the value model after evolution;
s5.3: and comparing the value target list of the value model after the evolution with the value target list in the initial value model, wherein if a certain value target in the value model after the evolution is not the value target in the initial value model, the value target is the value target to be evolved.
In one embodiment, S6 specifically includes:
s6.1: acquiring a role to which the value target to be evolved belongs in the value model after evolution based on the value target to be evolved, and taking the role as the role to be evolved;
s6.2: acquiring a domain to which the value target to be evolved belongs in the value model after evolution based on the value target to be evolved, and taking the domain as the domain to be evolved;
s6.3: selecting a corresponding evolution mode based on the to-be-evolved field to which the to-be-evolved value target belongs, if the to-be-evolved field of the to-be-evolved value target is the to-be-evolved initial field, selecting a population evolution mode to perform evolution operation, and executing step S7; if the to-be-evolved field of the to-be-evolved value target is the to-be-evolved new field, selecting a community-type evolution mode to perform an evolution operation, and executing step S8.
In one embodiment, S6.1 specifically includes:
s6.1.1: acquiring a role list of an initial value model and a role list of an evolved value model;
s6.1.2: acquiring a role to be evolved based on the value target to be evolved, wherein if the role to which the value target to be evolved belongs is the existing role of the initial value model, the value target to be evolved belongs to the initial role to be evolved; and if the role to which the value target to be evolved belongs is not the existing role of the initial value model, the value target to be evolved belongs to a new role to be evolved.
In one embodiment, S6.2 specifically includes:
s6.2.1: acquiring a domain list of an initial value model and a domain list of an evolved value model;
s6.2.2: acquiring a to-be-evolved field based on the to-be-evolved value target, wherein if the field to which the to-be-evolved value target belongs is the existing field of the initial value model, the to-be-evolved value target belongs to the to-be-evolved initial field; and if the field to which the value target to be evolved belongs is not the existing field of the initial value model, the value target to be evolved belongs to a new field to be evolved.
In one embodiment, S7 specifically includes:
s7.1: if the role to be evolved of the value target to be evolved is the initial role to be evolved, executing the step 7.2 to obtain an evolved target model; if the role to be evolved of the value target to be evolved is a new role to be evolved, executing the step 7.3 to obtain an evolved target model;
s7.2: determining a target evolution point in the initial role target model segment based on the value target to be evolved, and acquiring an evolved target model;
s7.3: and determining a target evolution point of the new role to be evolved in the initial role target model segment based on the value target to be evolved, and acquiring the evolved target model.
In one embodiment, S7.2 specifically includes:
s7.2.1: respectively acquiring character value model segments of the character to be evolved in the value model and the initial value model after the character evolves, namely an initial character value model segment of the character to be evolved and a character value model segment after the character evolves; if the role is an initial role to be evolved, the membership field of the role in the value model after evolution and the initial value model is the initial field to be evolved;
s7.2.2: finding an initial role target model segment to which a role to be evolved belongs in the initial target model;
s7.2.3: recording a value target to be evolved as an initial target to be evolved, and adding the initial target to be evolved as a target into an initial role target model segment to which the role to be evolved belongs;
s7.2.4: searching targets similar to the initial target to be evolved in a field basic target model library, wherein the similarity between the targets is obtained in a semantic similarity calculation mode, the similar targets are marked as the target to be evolved, and the target to be evolved and sub-targets thereof are marked as target model segments to be evolved;
s7.2.5: replacing the initial target to be evolved with the target to be evolved, and sequentially adding the target model segment to be evolved into the initial role target model segment to obtain an evolved initial role target model segment;
s7.2.6: and determining a depended set on which the target model segment to be evolved depends according to the dependency relationship among the roles in the initial target model, and sequentially adding the depended set to obtain the evolved target model.
Specifically, S7.2.1 specifically includes the following sub-steps:
s7.2.1.1: and acquiring an evolution rear role value segment EVMFRs (OR) of the role based on the evolution rear value model.
S7.2.1.2: and acquiring an initial role value fragment OVMFRs (OR) of the role to be evolved based on the initial value model.
S7.2.3.1: and judging whether a target similar to the initial target to be evolved exists in the initial role target model segment. Wherein S7.2.3.1 specifically includes the following steps:
step S7.2.3.1.1: and calculating the similarity between the target in the initial role target model segment and the initial target to be evolved. The target similarity calculation method is as follows:
the method adopts a semantic similarity calculation mode to obtain the similarity between targets, firstly obtains Word vectors of the targets based on Word2vec, and calculates the vocabulary similarity by adopting Cosine similarity. Wherein, the Cosine similarity calculation formula of the word is as follows:
wherein WmAnd WnFor vectorized representation of two words, WmiVector of points WmThe ith dimension of (2).
In the invention, each target in the target model can be regarded as a verb-noun pair of 'verb + noun', so that the targets are firstly participled, then the verb semantic similarity and the noun semantic similarity in the target verb-noun pair are respectively calculated, and the similarity of the targets is obtained by weighting and summing, as shown in formula (2):
GoalSim(Goal1,Goal2)
＝α1·Cosine(Goal1.verb,Goal2.verb)+α2 (2)
·Cosine(Goal1.noun,Goal2.noun)
wherein alpha is1And alpha2Is a weight factor, and α1+α 21. Since the influence of the verb in the target on the meaning of the target to be expressed is small, according to the experience, the verb similarity is weighted by alpha1Set to 0.2, noun similarity weight α2Set to 0.8. If the similarity between the two objects is greater than a certain threshold, the objects are considered similar, and the threshold is 0.5 according to the experience in the invention.
Step S7.2.3.1.2: if the similarity is lower than the threshold, it is determined that there is no target similar to the initial target to be evolved in the initial character target model segment, the initial target to be evolved is added as another root target of the initial character target model segment, and step S7.2.4 is directly executed. If the similarity between the targets is greater than a specified threshold, the targets in the initial role target model segment are considered to be similar to the initial target to be evolved, if the similarity of a plurality of targets is greater than the specified threshold, the target with the maximum similarity is regarded as the target similar to the initial target to be evolved and is marked as the initial target to be evolved, and S7.2.3.1.3 is executed.
Step S7.2.3.1.3: and adding the initial target to be evolved into the initial role target model segment according to the incidence relation between the initial target to be evolved and the initial target to be evolved. Step S7.2.3.1.3 specifically includes the following substeps:
step S7.2.3.1.3.1: and judging the incidence relation between the initial target to be evolved and the initial target to be evolved. After dividing the target into words, judging the upper and lower relation among nouns in the target, and further judging the association relation among the targets, wherein the specific judgment method comprises the following steps:
the invention judges the upper and lower relation of the target by utilizing the wordnet, if the noun A is the upper word of the noun B, the target containing the noun A is considered to be a parent target of the target containing the noun B; if the noun A is the hyponym of the noun B, the object containing the noun A is considered as a subclass object of the object containing the noun B; if noun A is a synonym for noun B, then the target containing noun A is considered to be the sibling target of the target containing noun B.
Step S7.2.3.1.3.2: if the initial target to be evolved is a parent target of the initial target to be evolved, taking the initial target to be evolved as a sub-target of the initial target to be evolved and adding the sub-target into the initial role target model segment; and if the initial point target to be evolved is a child target of the initial target to be evolved, taking the initial target to be evolved as a parent target of the initial point target to be evolved and sub-targets of the parent target of the initial point target to be evolved, and adding the sub-targets into the initial role target model segment. And if the initial point target to be evolved is a brother target of the initial target to be evolved, combining adjacent hypernyms of the two as parent targets, taking the initial point target to be evolved and the initial target to be evolved as child targets, and adding the hypernym parent target into the initial role target model segment as a sub-target of the initial parent target of the initial point target to be evolved.
Step S7.2.6 specifically includes the following substeps:
step S7.2.6.1: obtaining a depended set of initial character object model segments. If a certain target can be realized only by relying on the resources of other roles in the initial target model segment, the role is regarded as a relied role.
Step S7.2.6.2: and acquiring the evolved role target model segment of the depended role. A role depends on another role through a resource to accomplish a corresponding goal, and the role that provides the resource is referred to as a depended-on. When the original role to be evolved has a target to be evolved, the role of the depended person correspondingly adds a target to correspondingly solve the target to be evolved of the original role to be evolved, and the added target is the target to be evolved of the depended person. Therefore, the depended object to be evolved is added into the role object model of the depended role to obtain the evolved role object model segment of the depended role, and the specific steps are as above.
Step S7.2.6.3: and sequentially adding dependencies between the initial role target model segment and the evolved role target model segment of the depended role to obtain an evolved target model.
Step S7.3 specifically includes the following substeps:
step S7.3.1: adding a new role to be evolved into the initial target model, taking a value target to be evolved as a root target of the new role to be evolved, marking as an initial target to be evolved, and adding the initial target model.
Step S7.3.2: and searching a target similar to the initial target to be evolved in the field basic target model library, wherein the similarity calculation method is the same as the above. And recording the similar target as a target to be evolved, and recording the target to be evolved and the sub-targets thereof as target model segments to be evolved.
Step S7.3.3: and replacing the initial target to be evolved with the target to be evolved, and sequentially adding the target model segment to be evolved into the initial role target model segment to obtain the evolved initial role target model segment.
Step S7.3.4: and determining a depended set on which the target model segment to be evolved depends according to the dependency relationship among the roles in the initial target model, and sequentially adding the depended set to obtain the evolved target model, namely the evolved target model. The specific steps are the same as S7.2.6 above.
In one embodiment, S8 specifically includes:
s8.1: if the role to be evolved of the value target to be evolved is the original role to be evolved, executing the step 8.2 to obtain an evolved target model; if the role to be evolved of the value target to be evolved is a new role to be evolved, executing the step 8.3 to obtain an evolved target model;
s8.2: determining a new-field target evolution point of the original role to be evolved based on the value target to be evolved, and acquiring an evolved target model;
s8.3: and determining a new field target evolution point of the new role to be evolved based on the value target to be evolved, and acquiring an evolved target model.
In a specific implementation process, the step S8.2 includes the following substeps:
step S8.2.1: and acquiring a role target model segment of the role to be evolved based on the initial target model, and recording the role target model segment as the initial role target model segment to be evolved.
Step S8.2.2: and taking the value target to be evolved as a root target based on the initial role target model segment to be evolved, recording the root target as an initial target to be evolved, and adding the initial target to be evolved into the initial role target model segment to be evolved.
Step S8.2.3: in the field basic target model base, a target similar to the initial target to be evolved is searched, the similar target is marked as a target to be evolved, and the target to be evolved and sub-targets thereof are marked as target model segments to be evolved.
Step S8.2.4: and searching a depended role object model segment on which an object to be evolved depends in a domain basic object model library. In this scenario, the target to be evolved is realized by relying on resources provided by other roles in the field where the target to be evolved is located, and a part of target segments of the roles can be used as a solution for realizing the target to be evolved. And searching a target similar to the target to be evolved in a domain target model fragment library in a domain range to which the target to be evolved belongs, recording a role target model fragment to which the target belongs as a depended role target model fragment, and adding the depended role target model fragment into the initial target model.
Step S8.2.5: and adding dependence in the initial role target model segment to be evolved and the depended role target model segment to obtain an evolved target model.
Step S8.3 specifically includes the following substeps:
step S8.3.1: and adding a new role to be evolved into the initial target model, taking the value target to be evolved as a root target of the new role to be evolved, recording the root target as an initial target to be evolved, and adding the initial target to the initial target model.
Step S8.3.2: and searching a target similar to the initial target to be evolved in the field basic target model library, wherein the similarity calculation method is the same as the above. And recording the similar target as a target to be evolved, and recording the target to be evolved and the sub-targets thereof as target model segments to be evolved.
Step S8.3.3: and replacing the initial target to be evolved with the target to be evolved, and sequentially adding the target model segment to be evolved into the initial role target model segment to obtain the evolved new role target model segment to be evolved.
Step S8.3.4: and searching a depended role object model segment on which an object to be evolved depends in a domain basic object model library. In this scenario, the target to be evolved is realized by relying on resources provided by other roles in the field where the target to be evolved is located, and a part of target segments of the roles can be used as a solution for realizing the target to be evolved. And searching a target similar to the target to be evolved in a domain target model fragment library in a domain range to which the target to be evolved belongs, recording a role target model fragment to which the target belongs as a depended role target model fragment, and adding the depended role target model fragment into the initial target model.
Step S8.3.5: and adding dependence in the original role target model segment to be evolved and the depended role target model segment to obtain an evolved target model.
In one embodiment, S9 specifically includes:
s9.1: based on the target model segment to be evolved in the target model after evolution, searching a process segment which can realize each target in the target model segment to be evolved in a field basic process model library, and recording the process segment as the process segment to be evolved;
s9.2: and adding the process segment to be evolved into the initial process model to obtain an evolved process model.
Specifically, in S9.1, each flow model segment in the domain-based flow model library can achieve a specific goal, and the flow model segment has a corresponding goal label capable of achieving the goal. According to the target label of the process segment, the semantic similarity between the process segment and the target to be evolved is calculated, the process segment exceeding a certain threshold is regarded as the process segment capable of realizing the target to be evolved, and the process segment is recorded as the process segment to be evolved. The similarity calculation method is the same as above.
Step S9.2 is implemented as follows:
step S9.2.1: and determining a target execution sequence according to the incidence relation between the target to be evolved and the initial non-evolved target in the evolved target model.
Step S9.2.2: the execution sequence of the flow is determined according to the execution familiarity of the target. And adding the process segment to be evolved into the initial process model according to the process execution sequence, and acquiring the evolved process model.
In the specific implementation process, the method of the invention can be realized through the flow of a computer.
The following is a specific example of the evolution of a software service system in a software ecosystem by applying the method of the present invention. The invention provides an air ticket type insurance service in a pig flight software ecosystem and provides an air ticket booking and hotel booking service in the pig flight software ecosystem by two examples, and the implementation process of the invention is described in detail by combining with the accompanying drawings.
According to the evolution method of the ecology-oriented software service system, a system supporting the evolution modeling of the requirement of the software service system is developed. The demand evolution modeling system can build a value model, a target model and a process model of the software ecosystem. When the evolution analysis is carried out on the software service system in the software ecosystem, an initial value model, an initial target model and an initial flow model can be firstly introduced into the demand evolution modeling system, and an evolved value model is introduced to start the evolution modeling process of the software service system. When evolution analysis modeling is carried out, firstly, an initial target model is introduced into a target model modeling page, a value target to be evolved is added into the initial target model as an initial target to be evolved according to a population evolution method or a community evolution method, a target model segment similar to the initial target to be evolved is searched in a field basic target model library and is added into the initial target model to obtain an evolved target model, and finally, corresponding process evolution is carried out according to the mapping relation between the target model and the process model to obtain an evolved process model. The value model evolution modeling interface is shown in fig. 2, the target model evolution modeling interface is shown in fig. 3, and the process model evolution modeling interface is shown in fig. 4.
The implementation process of the population evolution method of the invention is first described in detail through 'providing air ticket insurance service in a pig software ecosystem'.
Firstly, step 1 is executed to obtain basic model libraries of different fields of the software ecosystem, and provide a multiplexing basis of modeling design for evolution analysis of the software service system, as shown in fig. 5, for an example of a certain target segment in the basic model library of the software ecosystem field stored in the demand evolution system. And 2, acquiring an initial model of the software ecosystem of the flying pig to be evolved, wherein the initial model comprises an initial value model, an initial target model and an initial flow model, and fig. 6 is an initial value model diagram of the embodiment. The pig software ecosystem comprises four roles of a pig platform, a user, an insurance company and an airline company under the scene that pigs provide airline tickets and insurance type selling services, and relates to the three fields of the tourism field, the insurance field and the airline field. In the original scene, the value target of a user is the appearance of taking an airplane conveniently, namely 'airplane convenient travel', the value target of an airline company is 'providing aviation travel service', the value target of a pig flying platform is 'providing travel service', the value target of an insurance company is 'providing a guarantee mechanism', and the four realize value circulation through different resource dependence. When the situations of flight delay, flight cancellation and the like frequently occur in an airline company, so that the user trip loss is caused, and the pig flying platform and the airline company suffer from negative benefits such as complaints and the like, under the situations, in a real pig flying software ecosystem, the change of multiple demands urges the emergence of aviation insurance services, so that the value of the user, the pig flying platform, the airline company and the insurance company is increased integrally. The value model of the aviation insurance service of the pig software ecosystem is not shown as an initial value model; and the value model when the aviation insurance service occurs is an evolved value model.
And step 3, obtaining the value model of the software service system after evolution. FIG. 7 is a diagram of an evolved value model of the present example; and 4, executing the step 4, and reconstructing the software service system model to be evolved. Fig. 8 is a reconstructed value model after evolution, and fig. 9 is a reconstructed initial target model. And 5, executing the step 5, and obtaining the value target to be evolved based on the value model after evolution and the initial value model. As shown in fig. 10, the role "insurance company" newly adds a value target "add aviation insurance types". And 6, executing a step 6, wherein for the role insurance company, the value target to be evolved, namely the increase of aviation insurance varieties, belongs to the insurance field in the initial field, and therefore, a population evolution method is selected. And 7, executing a step 7, and obtaining an evolved target model based on a population evolution method. The value target to be evolved 'increase aviation insurance types' belongs to an initial role 'insurance company' in an initial field 'insurance field', firstly, a role target model segment of the initial role 'insurance company' to be evolved is obtained, targets similar to the value target to be evolved 'increase aviation insurance types' are matched in the initial role target model segment, and as shown in figure 11, a 'guarantee range' of the point target to be evolved is determined. The value target to be evolved is used as an initial target to be evolved, namely 'increase aviation insurance variety', and grade judgment is carried out on the value target to be evolved and a 'guarantee range making' point target to be evolved to obtain a subclass target of which the initial target to be evolved is the point target to be evolved, so that the initial target to be evolved is added into an initial role target model as the subclass target with the targets to be evolved, as shown in fig. 12. And searching targets and sub-targets thereof similar to the initial target to be evolved in the field basic target model library to serve as target model segments to be evolved, wherein the similarity of the target 'aviation insurance type' and 'increased aviation insurance type' is highest as shown in fig. 13. Replacing the similar target "aviation insurance type" with the initial target "add aviation insurance type" to be evolved, and adding the sub-targets "offer air ticket cancellation risk" and "offer air ticket delay risk" of the "aviation insurance type" as target model segments to be evolved into the initial role model segment of "insurance company" in sequence, as shown in fig. 14. And finally, updating the relevant dependence according to the initial target model to obtain the evolved target model, as shown in fig. 15. And 9, executing corresponding process evolution according to the mapping relation between the evolved target model and the initial process model, acquiring an evolved process model, such as the initial process model shown in fig. 16, and obtaining the evolved process model shown in fig. 17 after evolution. It should be noted that in the pig software ecosystem, an insurance company serves as a depended party to provide insurance services for a pig platform and an airline company, and in the case of the evolution targets of the pig platform 'increase aviation insurance services' or the airline company 'increase aviation insurance services', the insurance companies are all depended on resources and need to perform synchronous evolution.
The implementation process of the community evolution method of the invention is described in detail by 'flight provides hotel reservation and airline ticket reservation services'.
The traditional travel service providing platform is often independent and separated in providing travel and accommodation services, and with the development of technical services and the evolution of user requirements, a dragon-style travel service experience becomes the business evolution direction of more and more travel service providers. In this example, the community evolution method provided by the present invention is specifically described by expanding a real scene of accommodation reservation service to the hotel field when the flight pig provides the airline ticket travel reservation service. Before the evolution of the demand, the embodiment mainly comprises three roles of a user, a pig flying platform and an airline company, and relates to two fields of a travel field and an airline field, wherein the value target of the user is mainly 'take an airplane for travel', the value target of the pig flying platform is 'provide an airplane ticket booking service', and the value target of the airline company is 'provide an airplane travel service'. The domain base model library in step 1 is a reusable model library, and this example is not described again.
And 2, executing the step 2 to obtain a software service system model to be evolved. FIG. 18 is a diagram of an initial value model of the present example.
And step 3, obtaining the value model of the software service system after evolution. Fig. 19 is a diagram of an evolved value model of the present example. And 4, executing the step 4, and reconstructing the software service system model to be evolved. For example, fig. 20 is the reconstructed value model after evolution, and fig. 21 is the reconstructed initial target model. And 5, executing the step 5, and obtaining the value target to be evolved based on the value model after evolution and the initial value model. As shown in fig. 22, after the demand evolves, the user wants the pig platform to recommend hotel accommodation service while providing travel service, and the role "pig platform" adds a value target "providing hotel reservation service". And 6, executing a step 6, and selecting a community evolution method for the role 'pig flying platform', wherein the value target to be evolved 'providing hotel reservation service' belongs to the new field 'hotel field'. And 7, executing the step 7, and obtaining an evolved target model based on the community type evolution method. The to-be-evolved value target "providing hotel booking service" belongs to an initial role "pig platform" in the new field "hotel field", and first, a role target model segment of the to-be-evolved initial role "pig platform" is obtained, the to-be-evolved value target "providing hotel booking service" is used as an initial to-be-evolved target, and the to-be-evolved value target "providing hotel booking service" is added to the role target model segment of the "pig platform" in the form of a root target, as shown in fig. 23. Searching a target similar to the initial target to be evolved, namely 'providing hotel reservation service' and a sub-target thereof in a domain basic target model library, using the target as a target model fragment to be evolved, as shown in FIG. 24, the target 'providing hotel reservation service' has the highest similarity with 'providing hotel reservation', replacing the initial target to be evolved, namely 'providing hotel reservation service', with the similar target, namely 'providing hotel reservation', and sequentially adding the sub-target 'providing room selection' and 'providing room reservation' as target model fragments to be evolved into an initial role model fragment of 'flying pig platform', as shown in FIG. 25. Finally, updating the related dependency according to the initial target model to obtain the evolved target model, as shown in fig. 26, business evolution is performed from the pig platform to the hotel field, and the hotel reservation service provided by the business evolution also needs to depend on related resources in the hotel field, so that the role target model of the depended party, namely the hotel, is also added to the target model, the dependency is updated, and the evolved target model is obtained. And 9, executing corresponding process evolution according to the mapping relation between the evolved target model and the initial process model to obtain an evolved process model, such as the initial process model shown in fig. 27, and after the evolution, obtaining the evolved process model shown in fig. 28.
The specific embodiments described herein are merely illustrative of the methods and steps of the present invention. Those skilled in the art to which the invention relates may make various changes, additions or modifications to the described embodiments (i.e., using similar alternatives), without departing from the principles and spirit of the invention or exceeding the scope thereof as defined in the appended claims. The scope of the invention is only limited by the appended claims.
Claims (10)
1. An evolution analysis method of an ecology-oriented software service system is characterized by comprising the following steps:
s1: acquiring a field basic model library, including a basic value model library, a basic target model library and a basic flow model library of different fields of a software ecosystem;
s2: acquiring an initial software service system model which needs to be evolved under the evolution requirement, wherein the initial software service system model comprises an initial value model, an initial target model and an initial flow model, and the initial software service system model is used as a software service system model to be evolved;
s3: obtaining an evolved value model obtained by a software service system through value realization;
s4: reconstructing a software service system model to be evolved, specifically comprising reconstructing an initial value model and an initial target model, and segmenting an evolved value model;
s5: determining a value evolution point based on the value model after evolution and the initial value model to obtain a value target to be evolved;
s6: selecting a corresponding evolution mode based on the value target to be evolved, wherein the evolution mode comprises a population evolution method and a community evolution method, if the population evolution method is selected, executing S7, and if the community evolution method is selected, executing S8;
s7, carrying out evolution operation on the initial target model based on a population evolution method to obtain an evolved target model;
s8, carrying out evolution operation on the initial target model based on a community-type evolution method to obtain an evolved target model;
s9: and acquiring the process model after evolution based on the target model after evolution, and finishing the evolution of the software service system facing the ecology.
2. The evolution analysis method of claim 1, wherein S4 specifically comprises:
s4.1: reconstructing the value model after evolution to obtain the value model fragment after evolution of the role granularity;
s4.2: reconstructing the initial value model to obtain initial value model fragments of role granularity;
s4.3: and reconstructing the initial target model to obtain the initial target model segment of the role granularity.
3. The evolution analysis method of claim 1, wherein S5 specifically comprises:
s5.1: traversing the initial value model to obtain all value target lists in the initial value model;
s5.2: traversing the value model after evolution, and acquiring all value target lists in the value model after evolution;
s5.3: and comparing the value target list of the value model after the evolution with the value target list in the initial value model, wherein if a certain value target in the value model after the evolution is not the value target in the initial value model, the value target is the value target to be evolved.
4. The evolution analysis method of claim 1, wherein S6 specifically comprises:
s6.1: acquiring a role to which the value target to be evolved belongs in the value model after evolution based on the value target to be evolved, and taking the role as the role to be evolved;
s6.2: acquiring a domain to which the value target to be evolved belongs in the value model after evolution based on the value target to be evolved, and taking the domain as the domain to be evolved;
s6.3: selecting a corresponding evolution mode based on the to-be-evolved field to which the to-be-evolved value target belongs, if the to-be-evolved field of the to-be-evolved value target is the to-be-evolved initial field, selecting a population evolution mode to perform evolution operation, and executing step S7; if the to-be-evolved field of the to-be-evolved value target is the to-be-evolved new field, selecting a community-type evolution mode to perform an evolution operation, and executing step S8.
5. The evolution analysis method of claim 4, characterized in that S6.1 specifically comprises:
s6.1.1: acquiring a role list of an initial value model and a role list of an evolved value model;
s6.1.2: acquiring a role to be evolved based on the value target to be evolved, wherein if the role to which the value target to be evolved belongs is the existing role of the initial value model, the value target to be evolved belongs to the initial role to be evolved; and if the role to which the value target to be evolved belongs is not the existing role of the initial value model, the value target to be evolved belongs to a new role to be evolved.
6. The evolution analysis method of claim 4, characterized in that S6.2 specifically comprises:
s6.2.1: acquiring a domain list of an initial value model and a domain list of an evolved value model;
s6.2.2: acquiring a to-be-evolved field based on the to-be-evolved value target, wherein if the field to which the to-be-evolved value target belongs is the existing field of the initial value model, the to-be-evolved value target belongs to the to-be-evolved initial field; and if the field to which the value target to be evolved belongs is not the existing field of the initial value model, the value target to be evolved belongs to a new field to be evolved.
7. The evolution analysis method of claim 1, wherein S7 specifically comprises:
s7.1: if the role to be evolved of the value target to be evolved is the initial role to be evolved, executing the step 7.2 to obtain an evolved target model; if the role to be evolved of the value target to be evolved is a new role to be evolved, executing the step 7.3 to obtain an evolved target model;
s7.2: determining a target evolution point in the initial role target model segment based on the value target to be evolved, and acquiring an evolved target model;
s7.3: and determining a target evolution point of the new role to be evolved in the initial role target model segment based on the value target to be evolved, and acquiring the evolved target model.
8. The evolution analysis method of claim 7, wherein S7.2 specifically comprises:
s7.2.1: respectively acquiring character value model segments of the character to be evolved in the value model and the initial value model after the character evolves, namely an initial character value model segment of the character to be evolved and a character value model segment after the character evolves; if the role is an initial role to be evolved, the membership field of the role in the value model after evolution and the initial value model is the initial field to be evolved;
s7.2.2: finding an initial role target model segment to which a role to be evolved belongs in the initial target model;
s7.2.3: recording a value target to be evolved as an initial target to be evolved, and adding the initial target to be evolved as a target into an initial role target model segment to which the role to be evolved belongs;
s7.2.4: searching targets similar to the initial target to be evolved in a field basic target model library, wherein the similarity between the targets is obtained in a semantic similarity calculation mode, the similar targets are marked as the target to be evolved, and the target to be evolved and sub-targets thereof are marked as target model segments to be evolved;
s7.2.5: replacing the initial target to be evolved with the target to be evolved, and sequentially adding the target model segment to be evolved into the initial role target model segment to obtain an evolved initial role target model segment;
s7.2.6: and determining a depended set on which the target model segment to be evolved depends according to the dependency relationship among the roles in the initial target model, and sequentially adding the depended set to obtain the evolved target model.
9. The evolution analysis method of claim 1, wherein S8 specifically comprises:
s8.1: if the role to be evolved of the value target to be evolved is the original role to be evolved, executing the step 8.2 to obtain an evolved target model; if the role to be evolved of the value target to be evolved is a new role to be evolved, executing the step 8.3 to obtain an evolved target model;
s8.2: determining a new-field target evolution point of the original role to be evolved based on the value target to be evolved, and acquiring an evolved target model;
s8.3: and determining a new field target evolution point of the new role to be evolved based on the value target to be evolved, and acquiring an evolved target model.
10. The evolution analysis method of claim 1, wherein S9 specifically comprises:
s9.1: based on the target model segment to be evolved in the target model after evolution, searching a process segment which can realize each target in the target model segment to be evolved in a field basic process model library, and recording the process segment as the process segment to be evolved;
s9.2: and adding the process segment to be evolved into the initial process model to obtain an evolved process model.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110558968.6A CN113342331B (en) | 2021-05-21 | 2021-05-21 | Ecological-oriented software service system evolution analysis method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110558968.6A CN113342331B (en) | 2021-05-21 | 2021-05-21 | Ecological-oriented software service system evolution analysis method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113342331A true CN113342331A (en) | 2021-09-03 |
| CN113342331B CN113342331B (en) | 2023-10-03 |
Family
ID=77470583
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110558968.6A Active CN113342331B (en) | 2021-05-21 | 2021-05-21 | Ecological-oriented software service system evolution analysis method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113342331B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114202451A (en) * | 2021-12-16 | 2022-03-18 | 华侨大学 | Evolution analysis method, device, equipment and storage medium of service ecosystem |
| CN116185379A (en) * | 2022-11-17 | 2023-05-30 | 北京东方通科技股份有限公司 | Method for optimizing code hosting platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090024426A1 (en) * | 2007-07-18 | 2009-01-22 | Hung-Yang Chang | Method and Apparatus for Dynamic Evolution in Business Performance Management |
| CN102567845A (en) * | 2011-12-15 | 2012-07-11 | 北京航空航天大学 | Online migration method and equipment for running example during combined service evolution |
| CN107797814A (en) * | 2017-10-17 | 2018-03-13 | 云南大学 | Systemic-function behavior congruence analysis method and system in a kind of Software Evolution |
| CN111191088A (en) * | 2020-01-02 | 2020-05-22 | 武汉大学 | Method, system and readable medium for analyzing cross-boundary service demand |
| CN111241307A (en) * | 2020-01-23 | 2020-06-05 | 复旦大学 | Software project and third-party library knowledge graph construction method for software system |
| CN112712396A (en) * | 2021-01-14 | 2021-04-27 | 清华大学 | Service internet control method based on service community succession prediction model |
-
2021
- 2021-05-21 CN CN202110558968.6A patent/CN113342331B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090024426A1 (en) * | 2007-07-18 | 2009-01-22 | Hung-Yang Chang | Method and Apparatus for Dynamic Evolution in Business Performance Management |
| CN102567845A (en) * | 2011-12-15 | 2012-07-11 | 北京航空航天大学 | Online migration method and equipment for running example during combined service evolution |
| CN107797814A (en) * | 2017-10-17 | 2018-03-13 | 云南大学 | Systemic-function behavior congruence analysis method and system in a kind of Software Evolution |
| CN111191088A (en) * | 2020-01-02 | 2020-05-22 | 武汉大学 | Method, system and readable medium for analyzing cross-boundary service demand |
| CN111241307A (en) * | 2020-01-23 | 2020-06-05 | 复旦大学 | Software project and third-party library knowledge graph construction method for software system |
| CN112712396A (en) * | 2021-01-14 | 2021-04-27 | 清华大学 | Service internet control method based on service community succession prediction model |
Non-Patent Citations (2)
| Title |
|---|
| 王怀民;史佩昌;丁博;尹刚;史殿习;: "软件服务的在线演化", 计算机学报, no. 02 * |
| 黄定轩;吴永娇;佘升翔;: "服务生态系统价值共创单元共生演化分析", 生态经济, no. 07 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114202451A (en) * | 2021-12-16 | 2022-03-18 | 华侨大学 | Evolution analysis method, device, equipment and storage medium of service ecosystem |
| CN116185379A (en) * | 2022-11-17 | 2023-05-30 | 北京东方通科技股份有限公司 | Method for optimizing code hosting platform |
| CN116185379B (en) * | 2022-11-17 | 2023-09-22 | 北京东方通科技股份有限公司 | Method for optimizing code hosting platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113342331B (en) | 2023-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Fu et al. | SpanNER: Named entity re-/recognition as span prediction | |
| Kanani et al. | Improving Author Coreference by Resource-Bounded Information Gathering from the Web. | |
| CN113342331A (en) | Evolution analysis method of ecology-oriented software service system | |
| Zavitsanos et al. | Discovering subsumption hierarchies of ontology concepts from text corpora | |
| Zhang et al. | Selection bias explorations and debias methods for natural language sentence matching datasets | |
| Bhatia et al. | Automatic text summarization and it's methods-a review | |
| Gutiérrez et al. | Spreading semantic information by word sense disambiguation | |
| Khalid et al. | Rubert: A bilingual roman urdu bert using cross lingual transfer learning | |
| Sachan et al. | Spatial compactness meets topical consistency: Jointly modeling links and content for community detection | |
| Sachan et al. | An active learning approach to coreference resolution | |
| Subash et al. | DISCO: A dataset of Discord chat conversations for software engineering research | |
| Gutiérrez et al. | UMCC-DLSI: Integrative resource for disambiguation task | |
| Chen et al. | Unidu: Towards a unified generative dialogue understanding framework | |
| Criado-Alonso et al. | Enriched line graph: A new structure for searching language collocations | |
| Hu et al. | A multi-modal global instance tracking benchmark (mgit): Better locating target in complex spatio-temporal and causal relationship | |
| Lee et al. | Character network embedding-based plot structure discovery in narrative multimedia | |
| Hafiene et al. | A new structural and semantic approach for identifying influential nodes in social networks | |
| CN110941638B (en) | Application classification rule base construction method, application classification method and device | |
| Zhu et al. | TDP: personalized taxi demand prediction based on heterogeneous graph embedding | |
| Dhole | Large language models as SocioTechnical systems | |
| Gadek et al. | Measures for topical cohesion of user communities on twitter | |
| Zhan et al. | Multi-objective privacy-preserving text representation learning | |
| Smani et al. | Maximization influence in dynamic social networks and graphs | |
| Tiwana et al. | Atrophy in aging systems: Evidence, dynamics, and antidote | |
| Wang et al. | Contextual compositionality detection with external knowledge bases and word embeddings |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |