Methods, apparatus, devices, and media used for writing test cases

Abstract

This disclosure provides a method for writing use cases, applicable to the financial field. The method includes: when creating a target use case, first recommending at least one use case from a structured use case storage database based on the basic information of the target use case, wherein the use cases in the structured use case storage database are decomposed and structured according to their constituent elements, and the constituent elements of the target use case include basic information; then, based on the at least one use case, obtaining a draft of the target use case. This disclosure also provides an apparatus, device, storage medium, and program product for writing use cases.

Description

Technical Field

[0001] This disclosure relates to the field of artificial intelligence, and can be used in the financial field, and more specifically to a method, apparatus, device, medium, and program product for writing use cases. Background Technology

[0002] Currently, test case writing is mostly carried out by requirement designers based on their own business understanding. However, due to the objective differences in business experience among each requirement designer, test case writing is inefficient and of inconsistent quality, resulting in high cost of requirement management and an inability to efficiently guide development and testing. Summary of the Invention

[0003] In view of the above problems, this disclosure provides methods, apparatus, devices, media and program products for writing use cases to improve the efficiency and standardization of use case writing.

[0004] A first aspect of this disclosure provides a method for writing use cases. The method includes: when creating a target use case, recommending at least one use case from a use case structured storage database based on the content of basic information of the target use case; wherein the use cases in the use case structured storage database are decomposed and structured according to constituent elements, and the constituent elements of the target use case include the basic information; and obtaining a draft of the target use case based on the at least one use case.

[0005] According to embodiments of this disclosure, the basic information includes a creation basis asset, the original data of which is derived from a business architecture asset library, wherein the creation basis asset is used to indicate the asset to which each use case belongs in the business architecture asset library.

[0006] According to embodiments of this disclosure, the creation-based assets include business domains in the business architecture asset library and activities within those business domains.

[0007] According to embodiments of this disclosure, the creation of the underlying assets also includes customers, products, channels, and partners involved in the activity.

[0008] According to embodiments of this disclosure, the constituent elements of the target use case further include a first element. The method further includes: when writing the content of the first element of the target use case, recommending content matching the first element from tasks within the activity to which the target use case belongs.

[0009] According to embodiments of this disclosure, the first element includes at least one of the following: task, step, business rule, input information, or output information.

[0010] According to an embodiment of this disclosure, the constituent elements of the target use case further include a second element, and the method further includes: when writing the content of the second element of the target use case, recommending a content template from the element database corresponding to the second element as the writing template for the second element.

[0011] According to embodiments of this disclosure, the second element includes at least one of the following: interface elements, interface rules, preconditions, postconditions, test cases, or error handling.

[0012] According to an embodiment of this disclosure, the constituent elements of the target use case further include a second element, and the method further includes: when the content of the second element is generated through the user's writing operation during the writing of the target use case, storing the newly generated content of the second element as a content template in the element database corresponding to the second element.

[0013] According to an embodiment of this disclosure, obtaining the draft of the target use case based on the at least one use case includes: using the use case selected by the user from the at least one use case as the draft.

[0014] According to an embodiment of this disclosure, obtaining the draft of the target use case based on the at least one use case includes: when the at least one use case includes multiple use cases, forming the draft based on the splicing of different constituent elements in the multiple use cases.

[0015] According to embodiments of this disclosure, when creating a target use case, recommending at least one use case from a use case structured storage database based on the basic information of the target use case further includes: recommending use cases of the same type as the target use case from the use case structured storage database; wherein the constituent elements of use cases of different use case types are not completely the same.

[0016] According to an embodiment of this disclosure, obtaining the draft of the target use case further includes: setting the constituent elements in the draft according to the use case type of the target use case.

[0017] According to embodiments of this disclosure, the method further includes: setting the constituent elements of use cases for different use case types respectively.

[0018] According to embodiments of this disclosure, recommending at least one use case from a use case structured storage database based on the basic information of the target use case includes: using multiple first intelligent recommendation algorithms in a predetermined combination during the recommendation process.

[0019] According to embodiments of this disclosure, the plurality of first intelligent recommendation algorithms includes at least two of the following: content-based recommendation algorithms, collaborative filtering recommendation algorithms, association rule-based recommendation algorithms, utility-based recommendation algorithms, or knowledge-based recommendation algorithms. The combination method includes at least one of weighted, transformed, mixed, or layered approaches.

[0020] A second aspect of this disclosure provides an apparatus for writing use cases. The apparatus includes a use case recommendation module and a drafting module. The use case recommendation module is used to recommend at least one use case from a structured use case storage database based on the basic information of the target use case when creating a target use case; wherein, in the structured use case storage database, the use cases are decomposed and structured according to their constituent elements, and the constituent elements of the target use case include the basic information. The drafting module is used to obtain a draft of the target use case based on the at least one use case.

[0021] According to embodiments of this disclosure, the apparatus further includes an element recommendation module. The element recommendation module is used to recommend content matching the first element from tasks within the activity to which the target use case belongs, when writing the content of the first element of the target use case.

[0022] According to embodiments of this disclosure, the apparatus further includes an element recommendation module and an element data update module. The element recommendation module is used to recommend a content template from the element database corresponding to the second element as a writing template for the second element when writing the content of the second element in the target use case. The element data update module is used to store the newly generated content of the second element as a content template in the element database corresponding to the second element when the content of the second element is newly generated through the user's writing operation during the writing of the target use case.

[0023] According to embodiments of this disclosure, the apparatus further includes a use case type setting module. The use case type setting module sets the constituent elements of use cases for different use case types.

[0024] A third aspect of this disclosure provides an electronic device. The electronic device includes one or more processors and one or more memories. The one or more memories are used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the methods described above.

[0025] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described above.

[0026] A fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0027] According to embodiments of this disclosure, the writing method of test cases can be designed as an intelligent recommendation-assisted writing mode, that is, when creating test cases, the existing test cases in the test case structure storage database are recommended to form a writing draft, which can not only improve the efficiency of test case writing, but also help improve the standardization of test case writing.

[0028] According to other embodiments of this disclosure, the content of corresponding elements can be intelligently recommended when writing the specific content of the use case, further improving the efficiency and quality assurance of use case writing. Attached Figure Description

[0029] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0030] Figure 1 The illustration schematically depicts application scenarios of methods, apparatus, devices, media, and program products for writing use cases according to embodiments of the present disclosure;

[0031] Figure 2 A flowchart illustrating a method for writing use cases according to embodiments of the present disclosure is shown schematically;

[0032] Figure 3 A schematic diagram illustrating the data structure of a use case according to an embodiment of the present disclosure is shown.

[0033] Figure 4 This diagram illustrates the data structure within the business architecture asset library.

[0034] Figure 5 A flowchart illustrating a method for writing use cases according to another embodiment of this disclosure is shown schematically;

[0035] Figure 6 The diagram illustrates the relationship between the business architecture asset library and the element database during the use case writing process according to this disclosure;

[0036] Figure 7 A flowchart illustrating a method for writing use cases according to yet another embodiment of the present disclosure is shown schematically;

[0037] Figure 8 A block diagram illustrating an apparatus for writing use cases according to embodiments of the present disclosure is shown schematically; and

[0038] Figure 9 A block diagram schematically illustrates an electronic device suitable for implementing a method for writing use cases according to embodiments of the present disclosure. Detailed Implementation

[0039] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0041] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0042] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0043] It should be understood in this document that any number of elements in the specification and figures are for illustrative purposes and not for limitation, and that any naming (e.g., first, second) is for distinction only and has no limiting meaning.

[0044] The business requirements document mainly consists of five parts: a prospect document, a design overview, use cases, non-functional requirements, and attachments. Among them, use cases are used to specifically describe the functional requirements of the project. Use cases define a series of logically related interactions that may occur between the operator and the system, and these interactions provide value to the operator. Therefore, use cases are the atomic units for implementing business development and design. In the requirements phase, use cases serve as the carrier, carrying over the results of requirements analysis and overview design; in the development phase, use cases are used as the basis for issuing development tasks and identifying IT service modification content; and in acceptance testing, use use cases are used as the basis to clarify the test design scope and guide the test design content.

[0045] To address the current issues of low efficiency and difficulty in standardized management during test case writing, and to improve the standardization of test case design, this embodiment of the disclosure breaks down test cases according to their constituent elements and stores them in a structured manner, constructing a test case structured storage database. Then, when writing test cases, relevant existing test cases can be retrieved from the test case structured storage database based on the basic information provided by the user, forming a writing draft, thereby improving the efficiency of test case writing.

[0046] According to other embodiments of this disclosure, when constructing a structured storage database for use cases, a business architecture methodology is used to link use cases with the business architecture, establishing a structured storage database for use cases based on a business architecture asset library. The theoretical basis for linking use cases with the business architecture is that a use case is a specific implementation case designed for a particular business scenario within the business architecture. Therefore, use cases can be linked to the assets corresponding to that business scenario in the business architecture asset library. Based on this structured storage database for use cases, standardized and regulated use case writing and management can be achieved.

[0047] According to some embodiments of this disclosure, the content of test case writing is automatically standardized during the test case writing process. For example, it can intelligently recommend elements in the test case to assist users in writing standard, standardized, and complete test cases, thereby improving business development efficiency.

[0048] It should be noted that the methods, apparatus, devices, media, and program products provided in this disclosure for writing use cases can be used in the financial field, or in any field other than the financial field. This disclosure does not limit the application field.

[0049] Figure 1 The illustration schematically depicts application scenarios of methods, apparatus, devices, media, and program products for writing use cases according to embodiments of this disclosure. It should be noted that... Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0050] like Figure 1 As shown, application scenario 100 according to this embodiment may include at least one terminal device (three are shown in the figure, 101, 102, 103), a network 104, and a server 105. Network 104 is the medium providing a communication link between terminal devices 101, 102, 103, and server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0051] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as browsers, shopping applications, mobile banking applications, government affairs applications, etc. (for example only).

[0052] Server 105 may be a server that provides various services, such as a back-end management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only).

[0053] According to some embodiments of this disclosure, server 105 may also be a data management server for managing a use case structured storage database, or according to other embodiments of this disclosure, server 105 may be communicatively connected to a database management server for managing a use case structured storage database, a business architecture asset library, and / or at least one element database.

[0054] It should be noted that the method for writing test cases provided in this disclosure can generally be executed by server 105. Accordingly, the apparatus, device, medium, and program product for writing test cases provided in this disclosure can generally be located in server 105. The method for writing test cases provided in this disclosure can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103, and / or server 105. Accordingly, the apparatus, device, medium, and program product for writing test cases provided in this disclosure can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103, and / or server 105.

[0055] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0056] The following will be based on Figure 1 The described scene, through Figures 2-7 The method for writing use cases according to the disclosed embodiments is described in detail.

[0057] Figure 2 A flowchart illustrating a method for writing use cases according to an embodiment of this disclosure is shown schematically.

[0058] like Figure 2 As shown, the method for writing use cases may include operations S210 to S220.

[0059] First, in operation S210, when creating a target use case, at least one use case is recommended from the use case structured storage database based on the basic information of the target use case. In the use case structured storage database, use cases are broken down and structured according to their constituent elements, and the constituent elements of the target use case include basic information.

[0060] The basic information may include the business domain to which the target use case belongs, the function of the target use case, the type of the target use case, a performance overview of the target use case, or the author of the target use case. This basic information can be provided by the user; for example, a user interface can be provided on terminal devices 101, 102, and 103 for the user to fill in or select.

[0061] When recommending use cases from the existing use case structured storage database, one intelligent recommendation algorithm or a combination of multiple intelligent algorithms can be used for information matching.

[0062] Then, in operation S220, based on at least one recommended use case, a draft of the target use case is obtained.

[0063] In some embodiments, when a use case is recommended from the use case architecture asset library, that use case can be directly used as the writing draft.

[0064] In other embodiments, when multiple use cases are recommended from the use case architecture asset library, the user can select one use case from the recommended use cases as the writing draft when forming the draft, or the different components of multiple use cases can be combined to form the writing draft. When combining the content of different components from multiple use cases, the user can select the content of each component from multiple use cases and combine them, or the intelligent recommendation algorithm can intelligently recommend various components based on the user's historical writing habits, the content of basic information provided by the user, or the popularity of the content of each component in the current use case structured storage database, etc., to form the writing draft.

[0065] Therefore, according to the embodiments of this disclosure, the test case writing method can be designed as an intelligent recommendation-assisted writing mode to improve the efficiency of test case writing.

[0066] According to embodiments of this disclosure, the basic information in the constituent elements of a use case may include a creation-based asset. The original data for the creation-based asset originates from a business architecture asset library, wherein the creation-based asset indicates the asset to which the use case belongs in the business architecture asset library. According to some embodiments of this disclosure, the creation-based asset can be used to associate a use case with a business architecture.

[0067] The following combination Figure 3 and Figure 4 The basis for the association between the use case structured storage database and the business architecture asset library is explained.

[0068] Specifically, a "use case" is a requirements modeling language, or a requirements modeling method. A "use case" comprehensively describes the interactions of a "system" using "use case diagrams" and "use case specifications." In this disclosure, an embodiment of using a structured storage database for use cases, broken down and stored according to their constituent elements, can be found... Figure 3 .

[0069] Figure 3 A schematic diagram of the data structure of use case 300 according to an embodiment of the present disclosure is shown.

[0070] like Figure 3 As shown, use case 300 is stored in the use case structured storage database and may include components such as basic information 301, business process, business rules, accounting and fund settlement, input / output, risk control measures, and / or additional information.

[0071] Basic information 301 is used to describe the basic attributes of the use case, which typically includes the use case absolute reference number, use case name, use case author, brief overview, asset on which it was created 311, and / or use case overview, etc.

[0072] Business processes describe the workflow of a use case, aiming to define coherent behavior without revealing the system's internal structure. A business process can include sub-elements such as preconditions, processing flows, error handling, and postconditions. To further enhance the visual representation of business processes, graphical methods such as activity diagrams, functional flowcharts, and interaction flowcharts can be used to describe process patterns. Preconditions refer to the prerequisites that must be met before the system can begin executing a use case. Processing flows are typically represented as human-computer interaction steps, demonstrating the sequence of interactions between the role and the system—a dialogue flowing from preconditions to postconditions. Error handling describes the "error flow," also known as exceptions, primarily referring to conditions that potentially prevent the successful execution of a use case. Postconditions describe one or more system states after the use case execution is complete.

[0073] Business rules describe the business logic and constraints of use cases, and are used to maintain the business structure or control and influence business behavior. A use case's business rules should include the business logic and constraints corresponding to all business processes of the current use case; that is, the logical operations that must be performed to implement the business processes are the business rules.

[0074] Input and output information summarize the information carried by the current field. If a data dictionary is involved, it should be described in this information.

[0075] According to embodiments of this disclosure, the original data of the creation basis asset 311 in basic information 301 originates from the business architecture asset library and is used to describe the classification and affiliation of use case 300 within the business architecture. That is, use case 300 is designed for the business scenario described by creation basis asset 311 and belongs to that business scenario in the business architecture asset library. Therefore, creation basis asset 311 can be used to indicate the asset to which use case 300 belongs in the business architecture asset library. The assets included in creation basis asset 311 can be combined with... Figure 4 The following example illustrates this.

[0076] Figure 4 The diagram illustrates the data structure within the Business Architecture Asset Library 400.

[0077] like Figure 4 As shown, the business architecture asset library 400 can include various models such as process models, product models, and entity models.

[0078] A process model is a data model that describes the business execution process using a standardized, structured modeling language. It embodies the process by which an organization processes and delivers value by handling resources according to certain procedures and rules to meet internal and external needs. In this case, the original data for creating asset 311 in use case 300 can come from the process model.

[0079] The business domain is the first level of the process model, reflecting the organization's overall value creation process and demonstrating its service capabilities.

[0080] Value stream is the second level of the process model, belonging to the business domain above it. It is a relatively high-level description of how the business domain creates value, making it easier to quickly understand the operation process of that business domain.

[0081] Activities are the third level of the process model, belonging to the business domain and value stream above them. An activity is an event-triggered interaction process between stakeholders (such as customers or partners) to meet their needs or for specific business objectives, describing a complete end-to-end business process. A business domain can include one or more activities, each corresponding to a business scenario.

[0082] A task is the fourth level of the process model. It is the main component of the activity at the next higher level. It is a set of steps, rules, and operations that a role performs within a certain period of time and has a clear business purpose.

[0083] Based on the process model structure in the aforementioned business architecture, a matching analysis of use cases and the business architecture reveals that activities are abstract aggregations of multiple specific business scenarios used to satisfy the needs of specific stakeholders; while use cases are concrete descriptions of business scenarios after activities are reconstructed. Therefore, use cases can be positioned below activities. Furthermore, since use cases are concrete descriptions of business scenarios after activities are reconstructed—that is, use cases realize the interaction between operators and the system in a specific scenario by executing one or more tasks under an activity—use cases describe business processes and business rules at the task level. This allows use cases to be more accurately positioned below activities and above tasks. Specifically... Figure 4 In the Business Architecture Asset Library 400, use case 300 can be attached to the next level of an activity and the previous level of a task.

[0084] Therefore, in one embodiment, the creation basis asset 311 may include business domains and activities within the business architecture asset library. In some embodiments, the creation basis asset also includes business chain information within the activities (i.e., information on customers, products, channels, and partners, referred to as CPCP). Thus, based on the content of the creation basis asset 311, it can be determined under which asset in the business architecture asset library a use case is attached. For example, under which business domain, or which activity within that business domain, and even what the relevant CPCPs are. It is evident that this disclosure embodiment can rely on the business architecture methodology to construct a structured storage database for use cases based on business architecture, achieving structured storage of use cases, establishing the relationship between use cases and business architecture, and associating use case writing with business architecture assets, thereby quickly locating target use cases during the use case writing process.

[0085] Continue to refer to Figure 4 According to embodiments of this disclosure, by attaching use case 300 to an activity within the business architecture, the content of asset 311 upon which use case 300 is based can be associated with the business architecture asset library 400. For example, if the name of a business domain or activity in the business architecture asset library 400 is modified, the content of asset 311 upon which use case 300 is based will automatically change accordingly. This method enables the linkage between the use case structured storage database and the business architecture asset library, improving the efficiency of standardized management of the use case structured storage database.

[0086] Accordingly, according to the embodiments of this disclosure, when writing target use cases, in operation S210, the content of the entered basic information (e.g., business domain, activity, or CPCP, etc.) can be used as search keywords to find existing use cases belonging to the same business scenario from the use case structured storage database. This allows for the rapid formation of a writing draft in operation S220, thereby quickly writing the target use case and improving the reusability of information in existing use cases. It is understood that the content of the basic information provided by the user when making recommendations in operation S210 may involve only a portion of the content in basic information 301, or it may involve all of the content. This disclosure does not limit this.

[0087] According to embodiments of this disclosure, a test case writing draft can be assembled using an intelligent recommendation algorithm based on information such as the business area, activity, C (customer), P (product), C (channel), and P (partner) selected by the user, as well as test case element information associated with the above information in the test case structured storage database, so that the user can quickly start writing.

[0088] According to other embodiments of this disclosure, a large number of use cases can be divided into different use case types based on characteristics such as business functions, and the constituent elements of use cases for each use case type can be set separately. In this way, corresponding use case templates can be formed for use cases of different use case types, facilitating use case management. Furthermore, when recommending use cases in operation S210, the user can specify the use case type of the target use case, thereby recommending only use cases of the same use case type as the target use case. Correspondingly, when forming the use case draft in operation S220, the constituent elements in the draft can be set according to the use case type of the target use case, further improving the efficiency of use case writing.

[0089] Table 1 below illustrates the component settings for four types of use cases according to embodiments of this disclosure, where “√” indicates a required component in the use case type, “○” indicates an optional component in the use case type, and “---” indicates that the component is not required in the use case type.

[0090] Referring to Table 1, the constituent elements of use cases are not entirely the same for different use case types. This embodiment of the disclosure can design online structured writing tools for various types of use cases based on the structured storage database of use cases and the element information contained under different use case types. In this way, when creating a target use case, users can select the appropriate writing tool according to the use case type of the target use case, thereby making the recommendation of existing use cases and the formation of writing drafts more efficient and better ensuring the achievement of the integrity requirements in use case writing quality.

[0091] The above describes the relationship between the use case architecture asset library and the business architecture asset library in embodiments of this disclosure, and the process of quickly forming target use case writing drafts based on this. According to other embodiments of this disclosure, during the process of writing target use cases after forming the writing drafts, content recommendations can also be made for the written constituent elements. The following will combine... Figure 5 and Figure 6 This section describes how to recommend content for constituent elements during the process of writing target use cases using a draft.

[0092] Table 1

[0093]

[0094] Figure 5 A flowchart illustrating a method for writing use cases according to another embodiment of this disclosure is shown schematically.

[0095] like Figure 5 As shown, the method for writing test cases may include operations S531, or operations S532 to S533, in addition to operations S210 and S220.

[0096] First, in operations S210 to S220, the recommended pattern is used to quickly generate a draft of the target use case. For details, please refer to the previous introduction; it will not be repeated here.

[0097] Then, in operation S531, when the constituent elements of a use case include the first element, when writing the content of the first element of the target use case, content that matches the first element is recommended from the tasks in the activity to which the target use case belongs.

[0098] The first element can be an element whose corresponding asset content can be found in the business architecture. For example, tasks, steps, business rules, input information, or output information. As described above, use cases describe business processes and rules at the task level. This means that use cases involving components related to tasks or business processes can reference relevant information from the business architecture asset library without needing to rewrite them. Furthermore, directly referencing asset information from the business architecture asset library ensures the correctness and consistency of the information, avoiding human error introduced when rewriting the content of the first element. For example, when writing business rules in use case 300, rules can be directly selected from the task under the activity to which use case 300 belongs in the business architecture asset library 400 for reference. Moreover, according to embodiments of this disclosure, when the business rule referenced in the business architecture asset library 400 changes, the business rule in use case 300 can also be changed accordingly, thereby improving the efficiency of updating and maintaining use case 300.

[0099] Additionally, when operating S532, if the constituent elements of a use case also include a second element, the content template for the second element can be recommended from the element database corresponding to the second element. The second element is a unique element asset in the use case that differs from the business architecture asset library, such as interface elements, interface rules, preconditions, postconditions, test cases, or error handling.

[0100] After operating S532, you can also operate S533. In the process of writing the target use case, if the content of the second element is generated through the user's writing operation, the content of the newly generated second element is stored as a content template in the element database corresponding to the second element.

[0101] It should be noted that operation S533 following operation S532 is only one embodiment. In other embodiments, the second element is not created based on the second element's creation template, but is completely rewritten by the user. In this case, the content of the newly generated second element can also be stored as a content template in the element database corresponding to the second element.

[0102] According to embodiments of this disclosure, when a use case is completed, the content of the updated second element in the use case can be uploaded back to update the corresponding element database, thereby keeping the information in the structured storage database of the use case fresh.

[0103] Continue Figure 3 The components of use case 300 and Figure 4 By comparing the business architecture asset library shown, the matching analysis results of the benchmark business architecture assets can be as follows: Figure 6 As shown. From Figure 6 It can more intuitively distinguish the relationship between the basic information, primary and secondary elements in the use case and the business architecture asset library.

[0104] Figure 6 The diagram illustrates the relationship between the business architecture asset library and the element database during the use case writing process according to this disclosure.

[0105] exist Figure 6 The content of the business architecture asset corresponding to the basic information 301 in use case 300 is outlined by an elliptical dashed box 601, the content of the business architecture asset corresponding to the first element in use case 300 is outlined by an elliptical dashed box 602, and the content of the element database corresponding to the second element in use case 300 is outlined by a rounded rectangle dashed box 603.

[0106] Based on the content of the example with the elliptical dashed box 601, it can be seen that the creation basis asset 311 and the restoration of the CPCP activity diagram in the basic information of use case 300 can be matched with the activities, activity diagrams, tasks, customers, channels, and partners in the business architecture asset library.

[0107] Based on the content of example 602 (elliptical dashed box), it can be seen that the processing flow in the business process of use case 300 can be correlated with the tasks and steps under the tasks in the business architecture asset library. The business rules in use case 300 can be correlated with the business rules under the tasks in the business architecture asset library. The input and output information in use case 300 can be correlated with the model entity attributes in the business architecture asset library.

[0108] As can be seen from the example of rounded rectangle dashed box 603, a set of interface elements and a set of interface rules can be built for the user interface diagram and interaction flowchart in test case 300, respectively. For the preconditions, postconditions, error handling, and other constituent elements in test case 300, an element database such as a precondition library, a postcondition library, an error handling library, and a test case set can also be built.

[0109] based on Figure 6 The analysis results led to the construction of a structured storage database for use cases based on the business architecture. This database establishes a multi-level relationship between use cases and business architecture assets, enabling structured storage of use cases, full lifecycle management of use case assets, and updates and accumulation of use case assets as business development progresses.

[0110] According to the embodiments of this disclosure, the test case writing method is designed as an intelligent recommendation-assisted writing mode. On the one hand, it can intelligently recommend existing test cases in the test case structured storage database when the test case is created. On the other hand, it can intelligently recommend corresponding element content when writing specific content of the test case, so as to ensure the achievement of the accuracy requirements in the quality of the test cases as much as possible.

[0111] Figure 7 A flowchart illustrating a method for writing use cases according to another embodiment of the present disclosure is shown schematically. It should be noted that... Figure 7 The illustration shows a specific application example of a method for writing use cases according to an embodiment of this disclosure, which helps those skilled in the art to understand the solution more accurately and does not constitute a limitation on this disclosure.

[0112] like Figure 7 As shown, the method for writing use cases may include operations S710 to S780.

[0113] First, when operating the S710, the user enters basic information.

[0114] Then, in operation S720, the system matches existing use cases from the structured use case storage database to perform intelligent recommendations for existing use cases. Specifically, in operation S721, existing use cases can be matched based on the activities and CPCP information in the basic information input by the user.

[0115] Next, operate the S730 to determine if it matches any existing use cases.

[0116] If no existing use cases are found, then in operation S740, add a new use case. Specifically, in operation S741, the newly added use case can be submitted and simultaneously stored in the use case structured storage database.

[0117] If an existing use case is found, then in operation S750, the existing use case is referenced. Specifically, in operation S751, the existing use case that matches the one in the use case structured storage database is referenced.

[0118] Next, in operation S760, determine whether to modify the referenced existing use cases. If not, the existing use case will be used directly without writing any new ones. If yes, a writing draft will be created based on the referenced existing use case for writing the use cases. For example, one of the at least one matched use cases can be used as the writing draft for writing the use cases, or when multiple use cases are matched, different components from the multiple use cases can be combined to form the writing draft.

[0119] According to embodiments of this disclosure, when matching and recommending existing use cases, multiple first intelligent recommendation algorithms can be used in a predetermined combination. In one embodiment, the multiple first intelligent recommendation algorithms include any two of the following: content-based recommendation algorithms, collaborative filtering recommendation algorithms, association rule-based recommendation algorithms, utility-based recommendation algorithms, or knowledge-based recommendation algorithms. The combination of the multiple first intelligent recommendation algorithms includes at least one of weighted, transformed, mixed, or stacked methods.

[0120] Specifically, according to embodiments of this disclosure, combined intelligent recommendation algorithms can be used to match use cases from a structured storage database. For example, different intelligent recommendation algorithms can be used to generate a prediction result, and then the prediction results can be combined using corresponding methods to generate a final result. In one embodiment, the intelligent recommendation algorithm can include the following five types: content-based recommendation algorithm, collaborative filtering recommendation algorithm, association rule-based recommendation algorithm, utility-based recommendation algorithm, and knowledge-based recommendation algorithm. If these algorithms still cannot meet the requirements, the intelligent recommendation algorithm can be iteratively improved or expanded according to the actual situation.

[0121] In one embodiment, the combination of these intelligent recommendation methods can include the following four methods: weighted, transformed, hybrid, and cascaded. Weighted recommendation involves weighting the results of multiple intelligent recommendation algorithms. Transformation involves choosing different intelligent recommendation algorithms based on the needs, background, and actual situation or requirements. Hybrid recommendation involves simultaneously using multiple intelligent recommendation algorithms to provide users with various recommendation results for reference. Cascaded recommendation involves first using one intelligent recommendation algorithm to generate a relatively coarse recommendation result, and then using a second intelligent recommendation algorithm to generate a more precise recommendation result based on that result.

[0122] For example, we plan to develop use cases for individual customers purchasing smart fixed deposit products through the WeChat banking channel. Specifically, we can use a layered combination of content recommendation algorithms and collaborative filtering recommendation algorithms for intelligent recommendations.

[0123] When creating a use case, users need to select the business domain, activities, C (customer), P (product), C (channel), P (partner), and task information involved in the target use case. If the target use case is determined to be in the personal deposit domain, the activity of signing a personal deposit product agreement is selected, and the tasks include reviewing and signing personal deposit product agreement applications and withdrawing personal funds.

[0124] According to embodiments of this disclosure, a content-based recommendation algorithm can first be used to search for a batch of use cases related to matching content tags in a use case structured storage database based on information such as the business domain, activity, task, and CPCP selected by the user. The weighting rule for data matching degree in the recommendation algorithm is: business domain 10%, activity 20%, CPCP 30%, and task 40%. The top 20 use cases with the highest data matching degree are obtained as preliminary recommendation results and also as input information for the next recommendation algorithm.

[0125] Then, a collaborative filtering recommendation algorithm can be used to extract high-frequency keywords based on the user's previously created, viewed, and referenced use cases. These high-frequency keywords are then matched with the use case content in the preliminary recommendation results. The successfully matched use cases are used as the final intelligent recommendation results for the user to filter. When the user selects a recommended use case, the system automatically imports the content of the recommended use case as the use case draft. The user then completes the use case creation: "Signing a personal deposit product agreement through WeChat Banking Channel - Purchasing a smart fixed deposit product (optimized)," and proceeds with subsequent requirement writing.

[0126] Next, the S770 is operated to modify existing use cases and write new use cases. According to embodiments of this disclosure, element content recommendations can be made during use case writing. Specifically, when writing use cases, an intelligent recommendation algorithm can be used to recommend steps, business rules, preconditions, postconditions, error handling, input information, and output information from the structured storage database of use cases based on the user's selected use case type, business domain, activity, task, C (customer), P (product), C (channel), P (partner), etc., so that the user can quickly start writing.

[0127] Then, when operating S780 and submitting the completed test case, the newly written test case assets are simultaneously stored in the test case structured storage database.

[0128] According to embodiments of this disclosure, based on the process model in the business architecture assets, and using the domains, value streams, activities, and tasks in the process model as the basic standard architecture, use cases are matched and analyzed with the business architecture. The use cases are then linked to the business architecture to construct a structured storage database for use cases based on the business architecture. On the one hand, this structured storage database enables the structured storage of use cases, facilitating the retrieval and referencing of existing use cases. On the other hand, the linkage between the structured storage database and the business architecture asset library facilitates the standardized management and maintenance of use cases.

[0129] Based on the aforementioned structured storage database for use cases, this embodiment of the present disclosure can utilize intelligent recommendation algorithms to recommend existing use cases in the structured storage database based on the user's selected use case type, business domain, activity, C (customer), P (product), C (channel), P (partner), and other information, according to the asset storage tree structure. This allows users to use existing use cases as a draft for use case writing.

[0130] According to embodiments of this disclosure, online writing functions can also be provided based on standardized writing templates for different types of use cases. At the same time, for the writing content of different elements of use cases, target requirement content can be automatically recommended using technologies such as artificial intelligence and big data, thereby improving the standardization level of use case design process and promoting further improvement in the quality of use case output.

[0131] Based on the methods for writing use cases described in the above embodiments, this disclosure also provides an apparatus for writing use cases. The following will be combined with... Figure 8 The device is described in detail.

[0132] Figure 8 A block diagram of an apparatus 800 for writing use cases according to an embodiment of the present disclosure is shown schematically.

[0133] like Figure 8As shown, according to some embodiments of this disclosure, the device 800 may include a use case recommendation module 810 and a draft generation module 820. According to other embodiments of this disclosure, the device 800 may further include an element recommendation module 830, an element data update module 840, and / or a use case type setting module 850. The device 800 can be used to perform reference... Figures 2-7 The method described.

[0134] The use case recommendation module 810 is used to recommend at least one use case from the use case structured storage database based on the basic information of the target use case when creating a target use case; wherein, in the use case structured storage database, use cases are decomposed and structured according to their constituent elements, and the constituent elements of the target use case include basic information. In one embodiment, the use case recommendation module 810 can perform the operation S210 described above.

[0135] The drafting module 820 is used to obtain a draft of a target use case based on at least one use case. In one embodiment, the drafting module 820 may perform the operation S220 described above.

[0136] According to some embodiments of this disclosure, basic information includes creation basis assets, the original data for creating basis assets comes from a business architecture asset library, wherein the creation basis assets are used to indicate the assets to which each use case belongs in the business architecture asset library.

[0137] According to embodiments of this disclosure, the creation of assets includes business domains in a business architecture asset library and activities within those business domains.

[0138] According to embodiments of this disclosure, the creation of underlying assets also includes customers, products, channels, and partners involved in the activity.

[0139] Therefore, the use case structured storage database can be associated with the business architecture asset library by creating assets, and use cases can be attached to the assets to which they belong in the business architecture asset library.

[0140] Furthermore, in some embodiments, when the target use case includes a first element, wherein the original data of the first element originates from a task in an activity within the business architecture asset library, the element recommendation module 830 is used to recommend content matching the first element from the tasks within the activity to which the target use case belongs when writing the content of the first element. In one embodiment, the element recommendation module 830 may perform the operation S531 described above.

[0141] In other embodiments, when the target use case includes a second element, wherein the second element is unrelated to the assets in the business architecture asset library, the element recommendation module 830 is used to recommend a content template from the element database corresponding to the second element as the writing template for the second element when writing the content of the second element of the target use case.

[0142] Furthermore, the element data update module 840 can be used to store the newly generated content of the second element as a content template in the element database corresponding to the second element when the content of the second element is generated through the user's writing operation during the writing of the target use case. Accordingly, in one embodiment, the element recommendation module 830 can perform the operation S532 described above. The element data update module 840 can perform the operation S533 described above.

[0143] The use case type setting module 850 can be used to set the constituent elements of use cases for different use case types, such as setting use case templates for different use case types. Then, when recommending use cases, the use case recommendation module 810 can obtain the use case type of the target use case and then recommend use cases of the same use case type as the target use case.

[0144] According to embodiments of this disclosure, any multiple modules among the use case recommendation module 810, draft formation module 820, element recommendation module 830, element data update module 840, or use case type setting module 850 can be merged into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the use case recommendation module 810, draft formation module 820, element recommendation module 830, element data update module 840, or use case type setting module 850 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the use case recommendation module 810, draft generation module 820, element recommendation module 830, element data update module 840, or use case type setting module 850 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0145] Figure 9A block diagram schematically illustrates an electronic device suitable for implementing a method for writing use cases according to embodiments of the present disclosure.

[0146] like Figure 9 As shown, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0147] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0148] According to embodiments of this disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 99 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 99 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0149] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0150] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0151] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0152] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0153] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0154] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0155] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0156] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0157] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0158] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for writing use cases, comprising: When creating a target use case, at least one use case is recommended from a structured use case storage database based on the basic information of the target use case. In the structured use case storage database, the use cases are broken down and structured according to their constituent elements. These constituent elements include basic information, which includes creation-based assets. The original data of these creation-based assets originates from a business architecture asset library. These creation-based assets enable the association between the use cases in the structured use case storage database and the business architecture asset library. The constituent elements also include a first element and a second element. The first element is an element whose corresponding asset content can be found in the business architecture asset library, and the second element is an element asset in the use case that is unique to the business architecture asset library. Based on the at least one use case, a draft of the target use case is obtained; When writing the first element of the target use case using the target use case writing draft, the corresponding asset information is directly referenced from the business architecture asset library; and When writing the content of the second element of the target use case using the writing draft of the target use case, a content template recommended from the element database corresponding to the second element is used as the writing template for the second element; The ability to associate the use cases in the use case structured storage database with the business architecture asset library through the creation of the asset library further includes: when the business rules referenced by the use cases in the use case structured storage database in the business architecture asset library change, the business rules referenced by the use cases in the use case structured storage database are changed accordingly.

2. The method of claim 1, wherein, The assets on which creation is based include business domains in the business architecture asset library and activities within those business domains.

3. The method of claim 2, wherein, The assets on which the creation is based also include the customers, products, channels, and partners involved in the activity.

4. The method of claim 1, wherein, The first element includes at least one of the following: Tasks, steps, business rules, input information, or output information.

5. The method of claim 1, wherein, The second element includes at least one of the following: Interface elements, interface rules, preconditions, postconditions, test cases, or error handling.

6. The method of claim 1, wherein, The method further includes: If the content of the second element is generated through the user's writing operation during the writing of the target use case, the newly generated content of the second element is stored as a content template in the element database corresponding to the second element.

7. The method of claim 1, wherein, The process of obtaining the draft of the target use case based on the at least one use case includes: The use case selected by the user from the at least one use case shall be used as the draft.

8. The method of claim 1, wherein, The process of obtaining the draft of the target use case based on the at least one use case includes: When the at least one use case includes multiple use cases, the draft is formed by combining the different constituent elements of the multiple use cases.

9. The method of claim 1, wherein, The step of recommending at least one use case from the use case structured storage database based on the basic information of the target use case when creating the target use case also includes: Use cases of the same type as the target use case are recommended from the structured storage database of the use cases; wherein the constituent elements of use cases of different use case types are not completely the same.

10. The method of claim 9, wherein, The process of obtaining the draft of the target use case also includes: According to the type of use case for the target use case, set the constituent elements in the draft.

11. The method according to claim 9, wherein, The method further includes: Set the constituent elements of use cases for different use case types.

12. The method according to claim 1, wherein, The recommendation of at least one use case from the use case structured storage database based on the basic information of the target use case includes: During the recommendation process, multiple first-class intelligent recommendation algorithms are used to make recommendations in a predetermined combination.

13. The method according to claim 12, wherein, The various first intelligent recommendation algorithms include any two of the following: content-based recommendation algorithm, collaborative filtering recommendation algorithm, association rule-based recommendation algorithm, utility-based recommendation algorithm, or knowledge-based recommendation algorithm; as well as The combination method includes at least one of weighting, transformation, mixing, or stacking.

14. An apparatus for writing use cases, comprising: The use case recommendation module is used to recommend at least one use case from a structured use case storage database based on the basic information of the target use case when creating a target use case. In the structured use case storage database, the use cases are decomposed and structured according to their constituent elements. These constituent elements include basic information, specifically creation-based assets. The original data of these creation-based assets originates from a business architecture asset library, which allows association between the use cases in the structured use case storage database and the business architecture asset library. The constituent elements also include a first element and a second element. The first element is an element whose corresponding asset content can be found in the business architecture asset library, and the second element is an element asset in the use case that is unique to the business architecture asset library. The drafting module is used to obtain the drafting document for the target use case based on the at least one use case; The element recommendation module is used to directly reference relevant asset information from the business architecture asset library when writing the content of the first element of the target use case using the writing draft of the target use case; and When writing the content of the second element of the target use case using the writing draft of the target use case, a content template recommended from the element database corresponding to the second element is used as the writing template for the second element; The ability to associate the use cases in the use case structured storage database with the business architecture asset library through the creation of the asset library further includes: when the business rules referenced by the use cases in the use case structured storage database in the business architecture asset library change, the business rules referenced by the use cases in the use case structured storage database are changed accordingly.

15. An electronic device comprising: One or more processors; One or more memories for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 13.

16. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 13.

17. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 13.

Images