JP4925340B2 - Software product creation system, method and program thereof - Google Patents

Description

  The present invention relates to a system, a method, and a program for creating a software product in software development.

  In software development, after creating a specification document that describes the functions, etc. of the software to be developed, a design document that defines the structure and architecture of the software with specific implementation in mind is created based on the specification document. To do. The developer then implements the software based on the design document. Software functions described in these specifications and design documents are represented by two aspects: static aspects such as information managed by software and dynamic aspects such as software operations. The information and operations described above are described in a document using a natural language, a diagram using a model language such as UML (Unified Modeling Language), and the like. By the way, as the scale of software increases, the amount of description and complexity of software operations increase. As a result, the time required for the developer to describe the operation of the software is increased, and thus there is a problem that the cost for software development increases and the software development period is prolonged.

  Therefore, in Non-Patent Document 1, in order to solve the above-mentioned problem, software frequently used in software that has already been created when creating a sequence diagram that expresses software operations in time series in a specification / design document. A method is proposed in which operations are patterned and accumulated, and a sequence diagram is automatically generated based on the patterns.

For example, in the sequence diagram representing the operation of the software, as shown in FIG. 16, a plurality of messages representing the behavior of the software are stored in a state where an abstract concept is associated with each message. In FIG. 16, the abstract concept “registration start” is associated with the first message, the abstract concept “registration” is associated with the second message, and the abstract concept “registration end” is associated with the third message. These abstract concepts are also associated with management information in a class diagram representing management information handled by software, as shown in FIG. For example, the abstract concept “registration start” is associated with management information “device type” and “IP address”, and the abstract concept “registration” is “device type”, “device No”, and “IP address”. Is associated with the management information. Further, the abstract concept of “registration end” is associated with management information “device No.”. Then, by assigning the management information associated with the abstract concept corresponding to the message to the parameter portion of each message shown in FIG. 16, it is possible to generate a sequence diagram as shown in FIG. Become.
Sato et al. “Proposal of OSS request definition method using pattern in device / NW management domain”, IEICE technical report vol. 105, no. 668, TM2005-70, pp. 85-90, March 2006

  However, in the conventional example, the software developer needs to extract and accumulate a common operation pattern as an abstract concept from a plurality of sequence diagrams that have already been created. In this case, since how to determine the operation pattern depends on the knowledge and experience of the software developer, the time required to extract the operation pattern varies from software developer to software developer and hinders efficient software development. It has become.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a software product creation system, method, and program thereof that can improve the efficiency of software development.

  In order to achieve the above object, the software product creation system of the present invention includes a task included in the second software product based on a task including a subject, an operation, and a parameter included in the first software product. Is a software product creation system that creates a software product by using a computer, wherein the computer generates a plurality of first and second software products that have already been created. Storage means for storing the task of the software product and the task of the second software product created based on the task in association with each other, and the task of each first software product stored in the storage means The same as the subject and operation of the task included in the other first software product stored in the storage means Task acquisition means for acquiring a task and a task of the second software product associated with the task, and a task of the second software product acquired by the task acquisition means. A task extraction unit that extracts the same task as the subject and operation of the task included in the other second software product, and creates a task of the second software product based on the task extracted by the task extraction unit Creating means.

  In addition, the software product creation method of the present invention is included in the second software product based on a task including a subject, an operation, and a parameter included in the first software product in order to achieve the object. A software product creation method for creating a software product by generating a task using a computer, wherein the computer generates a plurality of first and second software products already created. The task of one software product and the task of the second software product created based on the task are stored in association with each other, and each first stored in the storage unit is stored in a predetermined storage unit. Among the tasks of the software product, the same as the subject and the operation of the task included in the other first software product stored in the storage unit The task and the task of the second software product associated with the task are acquired, and included in the acquired second software product of the tasks of the acquired second software product The same task as the subject and the operation of the task is extracted, and a task of the second software product is created based on the extracted task.

  Furthermore, the software product creation program of the present invention causes the computer to execute the software product creation method in order to achieve the object.

  As a result, the same task as the subject and operation of the task included in the other first software product, and the task of the second software product associated with the task are acquired, and the acquired second Among the tasks of the software product, the same task as the subject and the operation of the task included in the other second software product is extracted, so that the task commonly used by the plurality of second software products Can be extracted.

  According to the software product creation system, method, and program thereof of the present invention, it is possible to extract a task that is used in common by a plurality of second software products. For example, the extracted task is used as an abstract concept. If this occurs, the time required for extracting abstract concepts can be shortened, and the efficiency of software development can be greatly improved.

  An embodiment of the present invention will be described below with reference to the drawings.

<Premise>
The software product includes a static software product (hereinafter referred to as a static product) in which data information necessary for realizing the behavior of the development target software is defined, and the behavior of the development target software. There is a dynamic software product (hereinafter referred to as a dynamic product) in which dynamic information (tasks) for defining the data is expressed. In this embodiment, a plurality of software products already created in software development are present. A software product creation system for extracting a common task as an abstract concept from a dynamic product and generating a new dynamic product based on the abstract concept will be described.

  A software product creation system 10 according to the present invention includes a computer mainly composed of a well-known CPU. As shown in FIG. 1, a display unit 11, an information input unit 12, a dynamic product storage unit 13, and a matching task storage. Unit 14, abstract concept storage unit 15, and control unit 16.

  The display unit 11 is a module for displaying information, such as a liquid crystal display, and displays a product drawing screen 20 as shown in FIG. 2 under the control of the control unit 16.

  The information input unit 12 is a module for inputting information, such as a keyboard and a mouse, and transmits input information to the control unit 16.

  The dynamic product storage unit 13 is a module that stores a dynamic product already created in software development and a task structure described later.

  The matching task storage unit 14 selects a task that is the same as a task included in another dynamic product among tasks included in the dynamic product stored in the dynamic product 13 and a task associated with the task. The module to save.

  The abstract concept storage unit 15 is a module that stores, among the tasks stored in the matching task storage unit 14, tasks commonly used by a plurality of dynamic products as abstract concepts.

  The control unit 16 is a module that is connected to the modules 11 to 15 and transfers information between the modules 11 to 15 or information obtained by combining information between the modules 11 to 15. Further, the control unit 16 is provided with a storage device such as a ROM, and the control unit 16 controls the modules 11 to 15 by executing a program stored in the storage device. Further, the control unit 16 is provided with a task match determination unit 161 and an abstract concept extraction unit 162, and operations of the task match determination unit 161 and the abstract concept extraction unit 162 will be described later.

  As shown in FIG. 2, the product drawing screen 20 includes a product selecting unit 21 for selecting a dynamic product to be created, a drawing unit 22 for displaying the dynamic product to be created, The task display unit 23 displays a task of a dynamic product created in a process upstream of the dynamic product to be created. In addition, the drawing unit 22 includes a registration instruction unit (not shown) for registering the created dynamic product in the dynamic product storage unit 13, and an extraction instruction unit (instruction for extracting an abstract concept). (Not shown) is provided, and registration and extraction can be instructed using the information input unit 12.

  In the present embodiment, as shown in FIG. 3, the sequence diagram task as the second dynamic product is based on the task included in the UC (use case) description as the first dynamic product. Is generated.

<Formulation of dynamic product task>
In the dynamic product, behavior for functions realized by software is described as a flow of a plurality of tasks. This one task 30 is expressed as comprising four elements: an input main body 31, an output main body 32, an operation 33 and a parameter 34. When the task is expressed in a natural language, the input subject 31, the output subject 32, the action 33, and the parameter 34 correspond to the subject, indirect object, predicate, and object, respectively. For example, as shown in FIG. 4, the input subject 31 of the task “operator sends device information to the server” is “operator”, the output subject 32 is “server”, the operation 33 is “send”, and the parameter 34 is “Device information”. When a task is expressed from a sequence diagram message in UML, the task 30 is shown as in FIG. The structure expressed as shown in FIGS. 4 and 5 is referred to as a task structure, and tasks and messages included in the dynamic product are stored in the dynamic product storage unit 13 after being converted into the task structure. .

  Even if the dynamic product has the same function to be expressed, the level of detail (granularity) of the task included in the dynamic product differs for each software development process. That is, as shown in FIG. 6, the granularity of the first task 30a among the plurality of tasks 30a to 30d of the UC description created in the upstream process of software development is the first in the sequence diagram created in the downstream process. The granularity of the task described in task 30e is coarser. In addition, when the second task 30b in the UC description is decomposed into the second, third, fourth and fifth tasks 30f, 30g, 30h, and 30i in the sequence diagram, the second task 30b in the UC description and the sequence diagram in FIG. Between the second, third, fourth and fifth tasks 30f, 30g, 30h, 30i, the second task 30b in the UC description is the task on which the respective tasks 30f, 30g, 30h, 30i in the sequence diagram are based. Each of the tasks 30f, 30g, 30h, 30i in the sequence diagram is created based on the second task 30b in the UC description. In the present embodiment, information representing such a relationship is expressed as an achievement relationship 40, and the first task 30a in the UC description, the first task 30e in the sequence diagram, and the second task 30b in the UC description The second, third, fourth, and fifth tasks 30f, 30g, 30h, 30i in the sequence diagram are linked by the achievement relationship 40. In this case, the relationship between the task of the created dynamic product and the task for each process is expressed by a structure as shown in FIG. This structure is called a task achievement structure, and the task achievement structure is stored in the dynamic product storage unit 13.

<Create dynamic product>
The control unit 16 displays the product drawing screen 20 on the display unit 11 with a configuration as shown in FIG. The developer creates a dynamic product to be created in the drawing unit 22 after selecting a dynamic product (for example, a sequence diagram) to be created in the product selection unit 21 of the product drawing screen 20. At this time, the control unit 16 converts the task of the dynamic product (for example, UC description) created in the process upstream of the dynamic product selected by the product selection unit 21 into the dynamic product storage unit 13. And is displayed on the task display unit 23. Note that the format of the dynamic product rendered in the rendering unit 22 may be a diagram based on a natural language, UML such as an activity diagram and a sequence diagram.

  Here, the developer associates the task of the dynamic product displayed on the task display unit 23 with the task of the dynamic product displayed on the drawing unit 22. This association is performed by the developer selecting the task of the dynamic product displayed on the drawing unit 22 after selecting the task of the dynamic product displayed on the task display unit 23. In the present embodiment, the existing GUI function is used to move the pointer to the task displayed in the task display unit 23 and click the mouse, and then click the dynamic product task displayed in the drawing unit 22 It is possible to associate each task. At this time, the inter-task relationship information indicating that each task is associated with each other is generated by the control unit 16.

  As another method for creating a dynamic product, the technique described in Japanese Patent Application No. 2007-198845 proposed by the applicant may be used.

<Product registration>
After creating the dynamic product, the developer instructs the registration instruction unit of the product drawing screen 20 to register the dynamic product. At this time, the control unit 16 stores the created dynamic product in the dynamic product storage unit 13. In this case, the control unit 16 converts the dynamic product created based on the inter-task relationship information of each task into a task achievement structure, and stores the task achievement structure in the dynamic product storage unit 13. Note that the inter-task relationship information input at the time of creating the dynamic product is converted into the achievement relationship 40 in the task achievement structure.

  Similarly to the above, another dynamic product is created on the product drawing screen 20 and registered. The dynamic product registration may be performed after all dynamic products are created, or may be performed every time one software product is created.

<Abstract concept extraction>
A method of extracting an abstract concept from a plurality of already created dynamic products will be described with reference to FIG. 7 on the assumption that the product registration has been performed. Note that the UC description as the first software product and the sequence diagram as the second software product corresponding to the UC description are respectively created N pieces as shown in FIG. 8, and the tasks included in each UC description Are related to the task of the sequence diagram corresponding to the UC description by the achievement relationship 40.

  First, when extraction of an abstract concept is instructed by the extraction instruction unit of the product drawing screen 20, the control unit 16 acquires a task that satisfies the conditions from the already created product (step S1). Specifically, the task match determination unit 161 of the control unit 16 performs the processes described in the following procedures 1-1 to 1-3.

  1-1. First, one UC description (for example, UC description 1 in FIG. 8) is extracted from the N UC descriptions stored in the dynamic product storage unit 13, and each task (task A, B) of the extracted UC description is extracted. , C), the task whose operation / input subject / output subject all match is obtained from other UC descriptions (UC descriptions 2 to N).

  1-2. Next, the tasks of the sequence diagrams (sequence diagrams 1 to N) associated with the acquired task by the achievement relationship 40 are acquired.

  1-3. Then, the tasks acquired in 1-1 and 1-2 are stored in the matching task storage unit 14.

  In this way, a plurality of task achievement structures are stored in the matching task storage unit 14 as shown in FIG. In the above procedure 1-1, whether or not the tasks match is determined based on the operation of the task, the input subject, and the output subject. Therefore, the task is stored in the matching task storage unit 14 in 1-3. When storing, the task parameters may not be stored in the matching task storage unit 14.

  Next, an abstract concept is extracted from the acquired task (step S2). More specifically, the abstract concept extraction unit 162 of the control unit 16 performs the processing described in the following procedures 2-1 to 2-3.

  2-1. Among the task sequences of the plurality of sequence diagrams acquired in 1-2 above, a task sequence that is used in common among the sequence diagrams is extracted. Here, “common” refers to a case where the operations, input subjects, and output subjects of the tasks constituting each task sequence are the same, and the task order is the same. For example, as shown in FIG. 10, when there are task achievement structures corresponding to the tasks A in the three UC descriptions, the first task achievement structure and the second task achievement structure include task 1, task Since 2 and task 3 exist in common, a first task sequence including task 1, task 2 and task 3 is extracted. In addition, since task 3 and task 4 exist in common in the second task achievement structure and the third task achievement structure, a second task sequence including task 3 and task 4 is also extracted.

  2-2. A dynamic product (for example, a sequence diagram) is configured based on the task sequence acquired in 2-1 above. Referring to the first task sequence shown in FIG. 10, the operations, input subject, and output subject of each task in the task sequence correspond to the message, transmission object, and reception object in the sequence diagram, respectively. When 1, task 2 and task 3 are represented by sequence diagrams, the sequence diagram shown in FIG. 11 can be configured.

  2-3. Along with the sequence diagram configured in 2-2 above, each task in the task sequence is extracted as an abstract concept, and the abstract concept is stored in the abstract concept storage unit 15. For example, as shown in FIG. 12, a message “Operation 1” in the sequence diagram, that is, Task 1 is extracted as an abstract concept “Abstract Concept 1”, and a message “Operation 2 in the sequence diagram”, that is, Task 2 is “Abstract Concept 2”. It is extracted as an abstract concept. In addition, the message “operation 3”, that is, task 3 is extracted as an abstract concept “abstract concept 3”.

  As in the conventional example described above, the abstract concept corresponding to the message is associated with the parameter portion of each message in the sequence diagram by associating the abstract concept with the management information such as the class diagram in advance. Management information can be automatically substituted, and a sequence diagram including parameters can be easily generated.

  Here, the operation in the case of extracting an abstract concept using UC descriptions and sequence diagrams corresponding to the two functions “device registration function” and “card registration function” shown in FIG. 13 will be described.

  The task match determination unit 161 of the control unit 16 acquires the second task among the tasks of the UC description corresponding to the “device registration function”, that is, the task “Server confirms device information”. Then, the task match determination unit 161 includes, among the tasks of the UC description corresponding to the “card registration function”, the second task of the UC description corresponding to the “device registration function” and the operation / input subject / output subject. Get matching tasks. In this case, the second task of the UC description corresponding to the “card registration function”, that is, the operation “confirm” of “the server confirms the card information”, the input subject “server”, and the output subject “none” are mutually connected. Since they are the same, the second task of the UC description corresponding to the “card registration function” is extracted, and the task is the matching task storage unit 14 together with the second task of the UC description corresponding to the “device registration function”. Is remembered.

  Each task stored in the matching task storage unit 14 is stored together with the task of the sequence diagram associated with the task by the achievement relationship 40 as shown in FIG. That is, the second task 50 of the UC description corresponding to the “device registration function” includes a task 50a of “operation: sending, input subject: server, output subject: DB” and “operation: input subject to search. : Task, 50b: “DB, output subject: DB”, task 50c, “operation: send, input subject: DB, output subject: server”, and “operation: confirm existence, input subject: server, output subject: server” Are associated with the task 50d. Further, the second task 60 of the UC description corresponding to the “card registration function” includes a task 60a of “operation: send, input subject: server, output subject: DB”, and “operation: input subject to search”. : Task, 60b: “DB, output subject: DB”, task 60c “operation: send, input subject: DB, output subject: server”, “operation: confirm existence, input subject: server, output subject: server” Are associated with the task 60d of “task: non-existent, input subject: server, output subject: server”.

  Next, the abstract concept extraction unit 162 of the control unit 16 extracts an abstract concept using the task sequence stored in the matching task storage unit 14. In the example of FIG. 14, tasks 50 a and 60 a “operation: send, input subject: server, output subject: DB” and tasks 50 b, 60 b called “operation: search, input subject: DB, output subject: DB”. And tasks 50c and 60c called “operation: send, input subject: DB, output subject: server”, and tasks 50d, 60d called “operation: check existence, input subject: server, output subject: server”. Since the task sequence composed of tasks is included in the task achievement structure corresponding to the “device registration function” and the task achievement structure corresponding to the “card registration function”, the task sequence is extracted as a common operation pattern.

  Then, the abstract concept extraction unit 162 stores the extracted task sequence in the abstract concept storage unit 15 as an abstract concept. A sequence diagram configured based on the extracted task sequence is shown in FIG. In this case, the task 50a “operation: send, input subject: server, output subject: DB” is extracted as an abstract concept “abstract concept 1”, and “operation: search, input subject: DB, output subject: DB”. "50b" is extracted as an abstract concept "abstract concept 2." In addition, a task 50c “operation: send, input subject: DB, output subject: server” is extracted as an abstract concept “abstract concept 3”, and “operation: confirm existence, input subject: server, output subject: server” Is extracted as an abstract concept “abstract concept 4”.

  In addition, when the developer associates the abstract concept with the management information set in the class diagram or the like, the control unit 16 adds the abstract to the parameter portion of each task in the task sequence extracted as the abstract concept. A sequence diagram generated by substituting management information corresponding to a concept can be displayed on the drawing unit 22.

  In this way, the same task as the subject and operation of the tasks included in the plurality of UC descriptions and the task of the sequence diagram associated with the task are acquired, and among the tasks of the acquired sequence diagram, Since the same task as the subject and operation of the task included in the sequence diagram is extracted, it is possible to extract a task that is commonly used in a plurality of sequence diagrams.

  As described above, in the above embodiment, tasks commonly used in a plurality of sequence diagrams can be extracted. For example, when an extracted task is used as an abstract concept, the work time required to extract the abstract concept And the efficiency of software development can be greatly improved.

  In addition, among the task sequences in the sequence diagram acquired from the matching task storage unit 14, the subject, operation, and order of each task in the task sequence are the subjects of the tasks in the task sequence included in the other sequence diagrams acquired. Since a task sequence having the same operation and order is extracted and a sequence diagram task is created based on the extracted task sequence, a more detailed operation pattern can be extracted.

  In addition, said embodiment is only a specific example of this invention, and this invention is not limited only to the said embodiment. For example, the present invention can also be realized by installing a program having the above-described creation procedure on a known computer via a recording medium or a communication line.

The figure which shows the structure of the software product creation system in one Embodiment of this invention. Figure showing the product drawing screen Diagram showing an example of a dynamic product Diagram showing task structure Diagram showing task structure Diagram showing task achievement structure Flow diagram showing operations when extracting abstract concepts The figure which shows an example of the dynamic product memorize | stored in the dynamic product preservation | save part The figure which shows an example of the task achievement structure memorize | stored in the coincidence task preservation | save part The figure which shows an example of the task sequence used in common in two or more sequence diagrams The figure which shows the relationship between the task sequence of FIG. 10, and a sequence diagram The figure which shows the relationship between the sequence diagram of FIG. 11, and an abstract concept Diagram showing an example of UC description and sequence diagram Diagram showing task achievement structure Diagram showing the relationship between abstract concept, task sequence and sequence diagram Diagram showing the relationship between sequence diagrams and abstract concepts in the conventional example The figure which shows the relationship between the management information and the abstract concept in the conventional example Diagram showing an example of a sequence diagram created based on an abstract concept

Explanation of symbols

  10 ... Software product creation system, 11 ... Display unit, 12 ... Information input unit, 13 ... Dynamic product storage unit, 14 ... Match task storage unit, 15 ... Abstract concept storage unit, 16 ... Control unit, 30, 30a ˜30i, 50, 50a˜50d, 60, 60a˜60e ... task, 40 ... achievement relation, 161 ... task matching judgment unit, 162 ... abstract concept extraction unit.

Claims (5)

A software result for creating a software product by generating a task included in the second software product using a computer based on a task including an entity, an operation, and a parameter included in the first software product. An object creation system,
The computer
In a state where a plurality of first and second software products already created are associated with a task of each first software product and a task of a second software product created based on the task. Storage means for storing;
Of the tasks of each first software product stored in the storage unit, the same task as the subject and operation of the task included in the other first software product stored in the storage unit, and the task associated with the task Task acquisition means for acquiring a task of the second software product obtained,
Task extraction for extracting the same task as the subject and operation of the task included in another second software product acquired by the task acquisition unit from the tasks of the second software product acquired by the task acquisition unit Means,
A software product creation system comprising: creation means for creating a task of the second software product based on the task extracted by the task extraction means. The task extraction means includes
Among the task sequence of the second software product acquired by the task acquisition unit, the subject, operation, and order of each task in the task sequence are included in the other second software product acquired by the task acquisition unit. To extract the task sequence that is the same as the subject, action and order of each task
The creating means includes
The software product creation system according to claim 1, wherein a task of the second software product is created based on the task sequence extracted by the task extraction unit. A software result for creating a software product by generating a task included in the second software product using a computer based on a task including an entity, an operation, and a parameter included in the first software product. A method for creating objects,
The computer
In a state where a plurality of first and second software products already created are associated with a task of each first software product and a task of a second software product created based on the task. Memorize in a predetermined storage unit,
Of the tasks of each first software product stored in the storage unit, the same task as the subject and operation of the task included in the other first software product stored in the storage unit, and the task And a second software artifact task associated with the
From the acquired tasks of the second software product, extract the same task as the subject and operation of the task included in the other acquired second software product,
A software product creation method, characterized in that a task of a second software product is created based on the extracted task. The computer
Of the task sequence of the second software product acquired from the storage unit, the subject, operation, and order of each task in the task sequence are those of the task sequence included in the other acquired second software product. Extract the task sequence that is the same as the subject, action and order of each task,
The software product creation method according to claim 3, wherein a task of the second software product is created based on the extracted task sequence.   A software product creation program for causing a computer to execute the method according to claim 3.

Images