CN109032921B - Method and device for automatically generating structured demand case - Google Patents

Abstract

The invention provides a method and a device for automatically generating a structured demand case, wherein the method comprises the steps of acquiring a demand record; carrying out structural analysis on the demand record, and constructing a model corresponding to the demand record; and outputting a structured demand use case corresponding to the demand record according to the model. The invention can structurally express the requirements through structural analysis, and the requirement case obtained according to the structural analysis method described in the embodiment of the invention can clearly express the specific content of the requirements and the original cause of the requirements, so that research and development personnel of products can communicate with each other in a language with strict logic, and the research and development efficiency is greatly improved.

Description

Method and device for automatically generating structured demand case

Technical Field

The invention relates to the field of computers, in particular to a method and a device for automatically generating a structured demand case.

Background

The demands involved in internet development are diverse and are often presented in a demand record. As shown in fig. 1, the requirement record is usually carried by a document, and mainly relates to the background of the requirement, the flowchart of the requirement, and the UI interaction flow. This requirement record is difficult to use for automated analysis and also suffers from the following drawbacks:

(1) it is not described which systems are needed to assist in completing the function that needs to be completed;

(2) the requirements consider which people have no evidence of interest in the implementation process;

(3) many cases are a schematic or a flow, which cannot clearly express the business rules designed in the process of realizing the requirements;

(4) in many cases, the need arises only from the user's perspective and not in consideration of the system performing the need, and therefore, mechanically coupling together multiple functions for use from the user's perspective, a well-developed system is not conducive to use by the user;

(5) lack of explicit requirements for system security, availability, performance, and lack of performance management of the developed systems results in loss of interest to the user or company.

Disclosure of Invention

In order to solve the technical problem, the invention provides a method and a device for automatically generating a structural requirement case. The invention is realized by the following technical scheme:

in a first aspect, a method for automatically generating a structured demand use case includes:

acquiring a demand record;

carrying out structural analysis on the demand record, and constructing a model corresponding to the demand record;

and outputting a structured demand use case corresponding to the demand record according to the model.

In a second aspect, an apparatus for automatically generating a structured requirement case includes:

the demand record acquisition module is used for acquiring a demand record;

the analysis module is used for carrying out structural analysis on the demand record and constructing a model corresponding to the demand record;

and the output module is used for outputting the structured demand use case corresponding to the demand record according to the model.

In a second aspect, a computer-readable storage medium is used for storing a program, and the program is used for implementing the method for automatically generating the structured demand use case.

In a third aspect, the server is configured to run the structured demand use case automatic generation apparatus.

The invention provides a method and a device for automatically generating a structured demand case, which have the following beneficial effects:

the invention can structurally express the requirements through structural analysis, and the requirement case obtained according to the structural analysis method described in the embodiment of the invention can clearly express the specific content of the requirements and the original cause of the requirements, so that research and development personnel of products can communicate with each other in a language with strict logic, and the research and development efficiency is greatly improved.

In addition, the structured demand use case clearly expresses the original appearance of the demand, reduces communication errors, meets the demand of people, and enables the demand of the system to better meet the benefit of people. By making the expression of the requirements more perfect and regular, the situation that research and development efficiency is reduced due to different requirement formats of research and development personnel is reduced, and therefore the communication efficiency of the product in the research and development process is higher.

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 described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a diagram of a document as a carrier for describing requirements provided by the background of the invention;

FIG. 2 is a flowchart of a method for automatically generating a structured requirement case according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a structured analysis rule provided by an embodiment of the present invention;

FIG. 4 is a flowchart of an interaction process in a code-scanning recharge process provided by an embodiment of the present invention;

FIG. 5 is a schematic diagram of a UI interface provided by an embodiment of the invention when a scannable man-hour is not configured;

FIG. 6 is a schematic diagram of a UI that is configured to be viewed by a supervisor after a merchant number of a card code-scanning list is configured according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a UI that an employee on a roster sees provided by an embodiment of the invention;

FIG. 8 is a schematic diagram of an interface seen by an employee in a non-roster provided by an embodiment of the present invention;

FIG. 9 is a block diagram of an apparatus for automatically generating a structured requirement case according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

An embodiment of the present invention provides an automatic generation method for a structured requirement case, as shown in fig. 2, including:

s101, acquiring a demand record.

In particular, the requirement record is a description of the requirement by the party providing the requirement. The demand record may be expressed using any expression, including but not limited to documents, voice, video, and pictures.

And S102, carrying out structural analysis on the demand record, and constructing a model corresponding to the demand record.

Specifically, the structured analysis may be performed according to preset structured analysis rules. The structured analysis rules are used for carrying out automatic modeling on the requirement records. And in the modeling process, extracting the demand elements in the demand record according to the structured analysis rule and acquiring the relation among the demand elements.

Specifically, the automatic analysis rule may be used to construct a static structure of a model, and the automatic analysis rule includes two parts, namely, attributes and relationships between the attributes, where the relationships between the attributes may be as follows: generalization, implementation, dependency, association, aggregation and/or combination.

Generalization means that one attribute inherits the content of another attribute and can add its own content; the dependence is that one attribute (A) depends on another attribute (B), and the change of the attribute (B) can affect the attribute (A); the association means that one attribute (A) strongly depends on the other attribute (B), the relationship is stronger than the dependence and is long-term, the relationship between the two parties is generally equal, and the association can be one-way or two-way; aggregation is a special case of association, and embodies the relationship between the whole and the part and possession, namely the relationship of has-a; the combination is also a special case of association relationship, which is embodied by a relationship of contacts-a, which is stronger than aggregation, also called strong aggregation; in general, the degrees of weakness represented by the latter relationships are in turn: combination > aggregation > association > dependency.

And S103, outputting a structured demand case corresponding to the demand record according to the model.

In particular, embodiments of the present invention provide a structured analysis rule that may be represented using a class diagram. As shown in fig. 3, the structured analysis rule in the embodiment of the present invention includes a first attribute group, a second attribute group, and a third attribute group, and a model constructed according to the structured analysis rule is output with a requirement case as an output; the first attribute group is a combination formed by attributes forming an aggregation relation with the requirement use case; the members in the second attribute group and one or more members in the first attribute group are in a generalization relation; and the members in the third attribute group and one or more members in the second attribute group are in a generalization relation or a combination relation.

Specifically, the attributes in the first attribute group include an actor, a crowd-sourcing benefit, a precondition, a postcondition, a path, and a supplemental constraint. Wherein the performers include a primary performer and a secondary performer; the supplemental constraints include four parts of a field list, business rules, quality requirements, and design constraints. Wherein the design constraints include platform constraints, interface constraints, and UI constraints; the path is expressed by an execution flow between the execution steps required for implementing the requirement case.

In one particular embodiment, the name of the use case is expressed using a move phrase, such as an actor using the system to do something, by relating to the source of the need, such as the laws, customs, and acquaintances of the party to whom the need relates.

Specifically, in the embodiment of the present invention, each field in each attribute group is explained in detail:

(1) the main performers:

the primary actor may be expressed using noun phrases. The main performer is a person or object that functionally interacts with the performing subject. The main actor does not belong to the execution body and the interaction with the execution body should be a functional interaction. For example, the ticket seller interacts with the ticket selling system (executive) using a mouse, but the executive is not a mouse because the interaction occurs from the functional needs of the primary executive.

Further, the primary actor may be a system: the system can be a human meat system, an intelligent system or even a special external system, namely time.

(2) The assistant performer:

the assistant performer may be expressed using noun phrases. The assistant executor is passively involved in the interaction process, but is required to achieve the target of the demand use case as the main executor. If the assistant executor does not participate in the demand use case, the demand use case can reach the required target (even though the experience is poor), and the demand use case has no assistant executor.

Taking a payment system as an example, a main executor of the payment system can be a bank system or a payment complete registered user, an auxiliary executor can be a business user who can complete the payment by inputting a password when handling the withdrawal, and the business user also plays a role of the auxiliary executor in the withdrawal requirement.

(3) Precondition:

the preconditions must be the constraints that the system must satisfy in order to implement the demand case before the demand case begins to be implemented and must be detected by the system before the demand case begins to be implemented. For example: the precondition of accepting a single refund that "there is enough money in the merchant account" is false because the money in the merchant account cannot be detected before the demand use case begins.

Specifically, the precondition may be expressed by [ system ] { already } { verb } { noun phrase }, where [ system ] represents the execution subject of the precondition and { already } represents a state in which the precondition should already exist. For example, the precondition may be already present or already logged in.

It is emphasized that the preconditions are constraints, not actions, such as: the "system records an order to complete payment" is an action, not a condition, which should be "the system has recorded an order to complete payment".

(4) Post-processing conditions:

the post-condition must be that the requirement case can be reached by following the path, and is a constraint that the system can detect and need to meet, for example: in the cashier check-out case, the post condition "the customer has left the store with the goods", which is undetectable by the system and therefore not a post condition.

Specifically, the postcondition may be expressed by [ system ] { already } { verb } { noun phrase }, where [ system ] represents the execution subject of the postcondition and { already } represents a state in which the postcondition should already exist. Such as the post condition may be saved, updated, created, generated, or recorded.

(5) Main path:

the executor and the execution body interact with each other in turn until the goal is achieved, and thus a main path is obtained. The steps of each round are divided into four categories: request, verify, change, respond. A round may have 2-4 of four classes such as request, verify, or request, verify, change, respond.

The subject of the main path can only be the main performer or system, such as: "system" and "direct connection merchant" are used to do something.

Writing method: { number }, { [ system ] | main actor } { state clause } { verb } { fixed language } { noun } [ { connecting word } |, ] { state clause } { verb } { fixed language } ] } noun } ] [ ] { (system) } main actor } ] { (state clause } ] { (verb) } verb } ] } verb } { fixed language } ] } noun } ] } [ ] [

{ clause in shape }: { preposition } [ { adverb } ] { adjective } { noun } [ { adverb } ]

The verb may specifically be: checking, updating, recording, creating, generating, presenting, feeding back, submitting, requesting, or sending. Numbering: the numbering can only be a number, e.g. 1, 2, 3; where the object clause may be exemplified by an appropriate account for { to | from }. Paths begin with a request and end with a response, there may be multiple rounds where the rules for the checked path should have a list of check fields.

(6) Expanding a path:

the extended path is the surprise and branch on the basic path that the system is to handle. Not all exceptions are extensions (which must be system-aware and handled). For example: the "merchant operator heart attack" results in "acceptance of the application agent to propose a refund" not being completed, but it is not an extension because the system cannot handle it. Reasons why an extension may occur may be the reason for the actor's selection, the reason for the business rules, the reason for system verification, and so forth.

It should be mentioned that the user's choice cannot be considered as an extended path, such as choosing a verification payment password, fingerprint payment, but only an option but not belonging to an extended path, whichever is chosen, is to verify the identity.

Writing method: { number } { sublumbering }, { [ system ] | main actor } { state clause } { verb } { determinism } { noun } { no } { adjective }

Sub-numbering: the extension path can only be a letter, and the extension sub-number of the extension path can only be a letter;

adjectives may be legal, compliant, failed; verbs can be checked, updated, recorded, created, generated, exposed, submitted, requested, needed, viewed.

In a preferred embodiment, each extension path related to system display, error reporting, prompting and requiring user selection automatically generates a corresponding UI interaction diagram, and the number of the UI interaction diagram is consistent with the number of the extension path; a legal business rule should correspond to an extended path, and the serial number of the business rule is consistent with that of the extended path.

(7) List of fields:

the input and output of the system are both provided with field lists corresponding to specific steps in the main path or the extended path, and the number of the field lists is corresponding to the number of the path.

Writing method: the list of fields entered contains: field name, whether padding is necessary, type, length, description, the output field list contains: field name, description.

(8) And (4) business rules:

the request validity rule should have a rule for checking a field list, one validity rule corresponds to one extension path, and the rule number is consistent with the extension path. In addition, the method also comprises a presentation rule, an error reporting rule, a prompt rule and a rule selected by a user.

(9) Design constraints are as follows:

interfaces, platforms, UI design constraints are included, and UI constraints correspond to specific paths.

The content can be known through the structural analysis rule expression, the demand records are analyzed according to the structural analysis rule, and the demand records can be converted into the structural use cases, so that the structural expression of the whole use cases is completed, the original appearance of the demand is clearly expressed, the communication errors are reduced, the requirement of people is met, and the requirement of the system can better meet the benefit of people. The expression mode of the structured demand use case enables the expression of the demand to be more perfect and regular, and reduces the condition that research and development efficiency is reduced due to different demand formats of research and development personnel, so that the communication efficiency of the product in the research and development process is higher. The clear requirements also reduce the repeated development of the system, reduce the useless functions and improve the accuracy of the system functions on the requirements of people involved.

In order to more clearly express the structured analysis method in the embodiment of the present invention, the present invention is exemplified by a specific small merchant code-scanning recharging process, as shown in fig. 4, an interaction process in the code-scanning recharging process includes the following actions: the method comprises the steps that a small and micro business user boss charges a payment account, a small and micro business user financial affairs configures a code scanning charging employee list to a payment system, the payment system updates the chargeable employee list, a small and micro business user financial obtains a payment system charging two-dimension code, a small and micro business user financial affairs scans the code scanning payment to the payment system, the payment system pays to a bank system, and the checking operation of the payment system is controlled according to time.

In the above requirements, taking the requirement of the financial exhibition code-scanning recharging interface of the small and micro business as an example, structured analysis is performed to obtain the specific contents of each attribute:

(1) the main performers: a merchant operator;

(2) and (4) concerning benefits:

the merchant: it is desirable to be able to recharge merchant accounts safely and quickly using WeChat payments;

the operator of the merchant: an operator in the list-scanning recharging list can smoothly scan codes;

WeChat payment principal: only limited talents can scan codes and recharge, so that the merchant is prevented from receiving bills by the function;

wind control responsible person: the wind control loophole is avoided when the code scanning recharging interface is displayed;

the safety responsible person: potential safety hazards are avoided on the display interface;

the customer service responsible person: the display interface and the description are clear, the consultation complaints of the merchants are reduced, and otherwise, the workload is increased;

(3) precondition: the merchant operator has logged in;

(4) post-processing conditions: none;

(5) the main path is as follows:

requesting code scanning recharging by a merchant operator;

(system) verifying the login status of the merchant operator;

the system displays a code scanning recharging interface;

(6) expanding a path:

(system) verify that the merchant operator does not have a login status, skip login, and end the use case;

(7) and (4) supplementary constraint:

A. the contents of the field list attribute are shown in table 1:

TABLE 1

B. The content of the business rule attribute comprises:

the prompt information display rule of the super management login is shown in table 2, the rule of the super management login after the once scannable code recharging list is modified is shown in table 3, and the prompt information display rule of the operator (non-super management) login is shown in table 4.

TABLE 2

TABLE 3

TABLE 4

(8) The content of the quality requirement attribute includes: the contents of five aspects of availability, performance, supportability, safety and usability;

(9) design constraints are as follows:

wherein the UI design constraints are as shown in FIGS. 5-8, FIG. 5 shows the UI interface when a scannable man-hour is not configured, FIG. 6 shows the UI interface viewed by the supervisor after a merchant number of a card code-scan business is configured, FIG. 7 shows the UI interface viewed by an employee on a list, and FIG. 8 shows the interface viewed by an employee not on a list.

The embodiment of the invention can carry out structured expression on the requirement through structured analysis, the structuralization of the requirement case relates to the case name, the benefits of people involved, the main executor, the auxiliary executor, the precondition, the postcondition, the path, the expanded path and the expression of the supplementary constraint, wherein the supplementary constraint also comprises the quality requirement and the design constraint, and the quality requirement also comprises the constraints of performance, usability, safety and usability.

An embodiment of the present invention further provides an automatic generation apparatus for a structured requirement case, as shown in fig. 9, including:

and the requirement record acquiring module 1 is used for acquiring requirement records.

And the analysis module 2 is used for carrying out structural analysis on the demand record and constructing a model corresponding to the demand record.

The structured analysis is executed according to a preset structured analysis rule; the structured analysis rule is used for automatically modeling the demand record; and in the modeling process, extracting the demand elements in the demand record according to the structured analysis rule and acquiring the relation among the demand elements.

The automatic analysis rule is used for constructing a static structure of the model and comprises attributes and relations between the attributes.

And the output module 3 is used for outputting the structured demand use case corresponding to the demand record according to the model.

The device and the method for automatically generating the structural requirement use case are based on the same inventive concept.

Embodiments of the present invention also provide a storage medium, which can be used to store program codes used in implementing the embodiments. Optionally, in this embodiment, the storage medium may be located in at least one network device of a plurality of network devices of a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Specifically, fig. 10 is a schematic diagram of a server structure provided in an embodiment of the present invention, where the server structure may be used to automatically generate a structured requirement use case. The server 800, which may vary significantly depending on configuration or performance, may include one or more Central Processing Units (CPUs) 822 (e.g., one or more processors) and memory 832, one or more storage media 830 (e.g., one or more mass storage devices) storing applications 842 or data 844. Memory 832 and storage medium 830 may be, among other things, transient or persistent storage. The program stored in the storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, a central processor 822 may be provided in communication with the storage medium 830 for executing a series of instruction operations in the storage medium 830 on the server 800. The server 800 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input-output interfaces 858, and/or one or more operating systems 841, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth. The steps performed by the above-described method embodiment may be based on the server architecture shown in fig. 10.

It should be noted that: the sequence of the above embodiments of the present invention is only for description, and does not represent the advantages and disadvantages of the embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (5)

1. A method for automatically generating a structured demand use case is characterized by comprising the following steps:

acquiring a demand record;

carrying out structural analysis on the demand record according to a preset structural analysis rule, and constructing a model corresponding to the demand record; the structured analysis rules are used for carrying out automatic modeling on the demand records, and in the automatic modeling process, demand elements in the demand records are extracted according to the structured analysis rules and the relation among the demand elements is obtained; the structured analysis rule is used for constructing a static structure of the model, and comprises attributes and two parts of contents of relations among the attributes;

outputting a structured demand use case corresponding to the demand record according to the model;

the attribute related to the demand use case is divided into a first attribute group, a second attribute group and a third attribute group in the structured analysis rule, and a combination formed by the attributes forming the aggregation relation with the demand use case in the structured analysis rule is the first attribute group; the members in the second attribute group and one or more members in the first attribute group are in generalized relation; the members in the third attribute group and one or more members in the second attribute group are in a generalization relationship or a combination relationship;

the attributes in the first attribute group comprise executors, audience interests, preconditions, postconditions, paths and supplementary constraints;

the performers comprise main performers and auxiliary performers; the main executor is a person or object which functionally interacts with the execution main body and does not belong to the execution main body; the auxiliary executor is an executor which participates passively in the interaction process and meets the requirement of the requirement use case target;

a source of the public interest expression requirement;

the precondition is the constraint which can be detected by the system and must be met in order to realize the requirement case before the requirement case starts;

the post-condition is a constraint which can be met by the requirement case according to the path execution and can be detected by the system and needs to be met;

the path comprises a main path and an expansion path, and the main path is expressed by implementing an execution flow among the execution steps required by the requirement use case; the extension path is an accident and branch on the main path that cannot be selected by the user, which the system can perceive and which is to handle;

the supplementary constraint comprises a field list, a business rule, a quality requirement and a design constraint; the design constraints include platform constraints, interface constraints, and UI constraints.

2. The method of claim 1, wherein:

relationships between various attributes include generalization, implementation, dependency, association, aggregation, and/or combination.

3. An apparatus for automatically generating a structured requirement use case, comprising:

the demand record acquisition module is used for acquiring a demand record;

the analysis module is used for carrying out structural analysis on the demand record according to a preset structural analysis rule and constructing a model corresponding to the demand record; the structured analysis rules are used for carrying out automatic modeling on the demand records, and in the automatic modeling process, demand elements in the demand records are extracted according to the structured analysis rules and the relation among the demand elements is obtained; the structured analysis rule is used for constructing a static structure of the model, and comprises attributes and two parts of contents of relations among the attributes;

the output module is used for outputting a structured demand use case corresponding to the demand record according to the model;

the attribute related to the demand use case is divided into a first attribute group, a second attribute group and a third attribute group in the structured analysis rule, and a combination formed by the attributes forming the aggregation relation with the demand use case in the structured analysis rule is the first attribute group; the members in the second attribute group and one or more members in the first attribute group are in generalized relation; the members in the third attribute group and one or more members in the second attribute group are in a generalization relationship or a combination relationship;

the attributes in the first attribute group comprise executors, audience interests, preconditions, postconditions, paths and supplementary constraints;

the performers comprise main performers and auxiliary performers; the main executor is a person or object which functionally interacts with the execution main body and does not belong to the execution main body; the auxiliary executor is an executor which participates passively in the interaction process and meets the requirement of the requirement use case target;

a source of the public interest expression requirement;

the precondition is the constraint which can be detected by the system and must be met in order to realize the requirement case before the requirement case starts;

the post-condition is a constraint which can be met by the requirement case according to the path execution and can be detected by the system and needs to be met;

the path comprises a main path and an expansion path, and the main path is expressed by implementing an execution flow among the execution steps required by the requirement use case; the extension path is an accident and branch on the main path that cannot be selected by the user, which the system can perceive and which is to handle;

the supplementary constraint comprises a field list, a business rule, a quality requirement and a design constraint; the design constraints include platform constraints, interface constraints, and UI constraints.

4. A computer-readable storage medium storing a program for implementing the method according to claim 1 or 2.

5. A server, characterized in that the server is adapted to run the method according to claim 1 or 2.

Images