Search

CN-116185394-B - SPL management method and system based on Scrum architecture and ontology technology

CN116185394BCN 116185394 BCN116185394 BCN 116185394BCN-116185394-B

Abstract

The invention belongs to the field of software development, and in particular relates to an SPL management method and system based on Scrum architecture and ontology technology, comprising the steps of constructing an SPL management system, acquiring user stories by a manager, matching the user stories by adopting an ontology model, generating demand characteristics, and adding the demand characteristics into a demand characteristic backlog list; the method comprises the steps of obtaining a component unique identifier and a component name of a demand feature body, searching and matching in an information base according to the component unique identifier and the component name, generating a demand matching list, comparing the matching degree of each component of the demand matching list with a set matching threshold value, constructing a project according to a comparison result, and developing a product according to the construction project, focusing on a demand analysis stage by taking concepts and technologies of Scrum architecture and SPL as centers, and providing a unified demand description specification with good definition by using the body, reducing large-scale early design, and improving software resource reusability and customization.

Inventors

  • CHEN JUNHUA
  • HUANG RUI

Assignees

  • 重庆邮电大学

Dates

Publication Date
20260512
Application Date
20230303

Claims (9)

  1. 1. A SPL management method based on Scrum architecture and ontology technology is characterized by comprising the following steps: S1, constructing an SPL management system, and initializing the system; S2, the manager acquires a user story, matches the user story by adopting an ontology model, generates demand characteristics, and adds the demand characteristics into a demand characteristic to-do list; s3, acquiring a component unique identifier and a component name of the demand feature body, searching and matching in an information base according to the component unique identifier and the component name, if no matching item exists, creating a new component, and adding the new component into a product backlog list; S4, comparing the matching degree of each component of the demand matching list with a set matching threshold, if the matching degree is smaller than the matching threshold, adding the demand feature body into the product backlog list, otherwise searching a component library through the matching body, if the corresponding code component of the component is found, adding the demand feature body and the similar code component thereof into the SPL backlog list, and if the corresponding code component is not found, rejecting the item in the demand matching list; S5, repeating the step S3 to the step S4 until the current demand characteristic backlog list is emptied, and carrying out a Sprint plan conference by Scrum specialists to obtain a Sprint target and a Sprint backlog list; s6, the DE uses the product backlog list to develop variable resources and a product line architecture and adds the variable resources and the product line architecture into an information base; And S7, the AE iteratively develops a new product by using the SPL backlog list.
  2. 2. The SPL management method based on Scrum architecture and ontology technology according to claim 1, wherein the process of matching user stories by adopting an ontology model comprises preprocessing user data, wherein the preprocessing comprises cleaning and complement processing of the data, extracting ontology segments from the preprocessed data by adopting the ontology model, wherein the ontology model comprises concept rules, data type attribute rules, object attribute rules, hierarchical relationship rules, axiom rules and instance rules, the concept rules are used for extracting concept features of the preprocessed user stories, the data type attribute rules are used for extracting data type attributes of the user stories, the object attribute rules are used for object attributes of the user stories, the hierarchical relationship rules are used for extracting hierarchical relationship features of the user stories, the axiom rules are used for extracting axiom features of the user stories, the instance rules are used for extracting instances of the user stories, matching the concept in the ontology segments according to concepts in the ontology model, and integrating all the ontology segments with the same probability to generate demand features.
  3. 3. The SPL management method based on Scrum architecture and ontology technology according to claim 1 is characterized in that the process of calculating the matching degree includes selecting two entity of two components from a demand matching list at random, selecting two corresponding nodes from the two entity, calculating the matching degree of the two nodes by means of Jaccard coefficients based on distance, and calculating the average value of the matching degrees of all the nodes, wherein the average value is used as the matching degree of the two components.
  4. 4. The SPL management method based on Scrum architecture and ontology technology according to claim 3, wherein the formula for calculating the matching degree of two nodes is: Wherein K represents a matching value, v 11 represents a1 st node in the 1 st ontology concept instance set, v 21 represents a1 st node in the 2 nd ontology concept instance set, S represents a function of an attribute and attribute value description node matching value K (v 11 ,v 21 ), and e t represents an ontology Data type attribute of single node in (a), f t represents attribute value of e t , and e c represents ontology F c represents the attribute value of e c , K sim represents a function based on path length and depth, K Jaccard represents Jaccard coefficients, γ represents the shortest path length parameter, μ represents the shortest path depth parameter, l represents the shortest path length in e t ,e c , and h is the depth of the words contained in the selected semantic web.
  5. 5. The SPL management method based on Scrum architecture and ontology technology according to claim 3, wherein the calculation formula of the matching degree of the two components is: Wherein, the A first component is shown as such, Representing the second component, N representing the total number of nodes, K representing the matching value, v 1k representing the kth node in the 1 st ontology concept instance set, v 2k representing the kth node in the 2 nd ontology concept instance set.
  6. 6. The SPL management method based on Scrum architecture and ontological techniques of claim 1, wherein the manager is a Scrum role responsible for managing to-do lists and their priorities, tracking product development.
  7. 7. The SPL management method based on Scrum architecture and ontology technology according to claim 1, wherein Scrum expert is Scrum role, responsible for assisting project team in implementing agile product line development management process based on virus, SPL and ontology.
  8. 8. The SPL management method based on Scrum architecture and ontological techniques of claim 1, wherein the Sprint planning session is a session involving Scrum experts and development teams for planning functions to be implemented in the current Sprint.
  9. 9. The SPL management system based on Scrum architecture and ontology technology is used for executing any SPL management method based on Scrum architecture and ontology technology according to claims 1-8, and is characterized by comprising a system management module, a demand management module and a product development module; The system management module is used for managing user accounts, operation authorities and data authorities, inputting team personnel information when a project is started, and distributing corresponding roles and related role authorities for the team personnel, wherein the functions comprise user management, role management, menu management and group management; The system comprises a demand management module, a product responsible person, a product management module and a priority ranking module, wherein the demand management module is used for systematically managing multiplexing demands, namely, a product responsible person uses a characteristic form to acquire user stories, and the product demands are refined, made into items and ranked in priority by means of management of demand workflow, demand analysis and demand traceability; the product development module is used for managing the working phase of the product development process and realizing the functions of task management, component uploading, iterative development and product delivery.

Description

SPL management method and system based on Scrum architecture and ontology technology Technical Field The invention belongs to the field of software development, and particularly relates to an SPL management method and system based on Scrum architecture and ontology technology. Background With the rapid development of information technology, a large number of products running information system software have been deeply applied to various industries of society. As the demand for user population differentiation increases, manufacturers are faced with numerous challenges in product line branching. Traditional software development models have failed to meet the manufacturer's demand for shortening the product line development cycle. Enhancing product line software resource reuse is a reasonable approach to improving product development rates and solving this problem. At present, the software resource multiplexing mainly comprises demand multiplexing, component multiplexing, modeling multiplexing and the like. Currently, agile software development (Agile Software Development, ASD) and software product lines (Software Product Line, SPL) enhance the reuse of software resources in applications that expedite software product development, and have shown tremendous benefits in the software industry. SPL is a software development method based on practice or planning drivers, and SPL engineering enables mass production of a series of related products in the software industry. SPL contains two main development processes, domain engineering (Domain Engineering, DE) and application engineering (Application Engineering, AE). DE focuses on problem domains, defines commonalities and variability of SPL products to build features and describe requirements for developing and managing reusable core resources, AE focuses on resource reuse, and utilizes variability to develop software products. Although SPLs can develop high quality, complex software quickly, under the circumstance that business needs are often changed, SPLs often have too high coordination cost, slow development process and release cycle, and thus the software products cannot keep up with market needs. Thus, the present invention introduces agile development framework Scrum. Scrum is an iterative framework for planning and guiding project flows, featuring short iterative development cycles, dislike and introspection cycles, collaborative decisions, fast feedback, and code modification continuously integrated into the developing system. In Scrum development flow, software products are flexibly and rapidly developed by using iteration and increment methods, so that the problem of SPL in the development process can be effectively solved. However, in the agile software project, the document is not a priority item, so that the unified requirement description specification is lacking, and the coordination cost is too high, so that the requirement is inconvenient to manage. Therefore, a great deal of research discusses the feasibility and benefits of implementing SPL in Scrum framework, namely, cooperatively solving the weaknesses of the other party, and achieving the common goal of constructing and managing resources in the same field, developing series of software products and promoting the multiplexing of the software resources. However, the software development method for implementing SPL in Scrum framework still has high coordination cost problem. Software development is a complex process in which each software product is a knowledge representation that all relevant personnel mark or store in different ways, resulting in frequent comprehension bias among the parties of the developer, customer, etc. in the communication process regarding the product requirements. Disclosure of Invention In order to solve the problem, the invention introduces the ontology, which is often used as a description for capturing concepts and relations in a form in computer science, so that the problem of high coordination cost of multiple parties such as developers, clients and the like caused by improper communication in the software development process can be reduced. The invention provides an SPL management method based on Scrum architecture and ontology technology, which comprises the following steps: S1, constructing an SPL management system and initializing the system; S2, the manager acquires a user story, matches the user story by adopting an ontology model, generates demand characteristics, and adds the demand characteristics into a demand characteristic to-do list; s3, acquiring a component unique identifier and a component name of the demand feature body, searching and matching in an information base according to the component unique identifier and the component name, if no matching item exists, creating a new component, and adding the new component into a product backlog list; S4, comparing the matching degree of each component of the demand matching list with a set matching thr