JPH01259423A - Software development supporting device - Google Patents

Abstract

PURPOSE:To reduce man-hours for generation of data and documents by unifying description contents of documents for generation of an OS having the data operation as the center and a program of a switchboard or the like. CONSTITUTION:A data distributing device 2 not only sends data received from each terminal to a data extracting device 3 or a document link device 4 in accordance with the classification of this data but also sends data sent from the data extracting device 3 to the terminal side. The data extracting device 3 accesses a data base 1 based on data sent from the data distributing device 2 to extract corresponding data and sends this data to the data distributing device 2. The document link device 4 gives a link between the document which is sent from the data distributing device 2 and is generated by a user and data related to this document and stores this link in the data base 1. Thus, documents linked to data as the operation object can be used again as parts at the time of generating a new document to reduce the man-hours.

Description

[Detailed Description of the Invention] [Summary] Regarding a software development support device that promotes the standardization of documents in a software development environment and the reuse of parts within the documents, programs for O8, exchanges, etc. that mainly involve data manipulation are created. The purpose is to unify the description content of documents for smooth communication between each process, and to reduce man-hours by efficiently reusing parts of documents. A database that stores a relationship between a document and data to be manipulated as a link, a data distribution device, a data extraction device, and a document link device,
The data distribution device sends data to the data extraction device or document link device depending on the type of data received from each terminal, and also sends the data output from the data extraction device to the terminal side. The extraction device accesses the database based on the data sent from the data distribution device, extracts the corresponding data, and sends it to the data distribution device, and the document link device extracts the corresponding data based on the data sent from the data distribution device. , a link is created between a document created by a user and the data related to the document, and the link is stored in the database.Thereby, when creating a new document, the document linked to the data to be operated on is created. Configure so that it can be reused as a part.

[Industrial application field]

The present invention relates to a software development support device that promotes the standardization of documents and the reuse of parts in documents in a software development environment, and particularly relates to external specifications when creating programs for operating systems (O3) and exchanges that mainly involve data manipulation. The present invention relates to a software development support device that standardizes documents at each level of writing, design, and coding, and reuses parts within the documents.

As shown in FIG. 10, the software development process includes steps such as creating external specifications, creating a system design document, and coding.

If the scale of the program is large, these steps may be performed by a large number of developers. In this case, if the description content of the document created as a result of the work in each process is not unified, there will be a problem that information will not be correctly transmitted to the next process.

[Problems to be solved by conventional technology and inventions] Conventionally, there were no measures to support software development.
Due to differences in the ability of developers and differences in the way they express themselves even if they have the same ability, the content of documents created as a result of work in each process is not unified, and the content of the documents created as a result of work in each process is not consistent. There was a problem that information was not being communicated.

For example, as shown in Figure 11, if the developer who created external specification A is different from the developer who created external specification B, the same error may occur: "rDN is not implemented in external specification A." In external specification B, it is sometimes written as "rDN unregistered". As a result, the contents of the next created design document and the contents of the coding may be different, resulting in a problem that the efficiency of software development deteriorates.

Furthermore, since no attempt is made to reuse parts within each document, as the scale of the program increases, the amount of documents also becomes enormous, leading to a reduction in the number of man-hours required to create them.

The purpose of the present invention is to unify the description content of documents (documents for creating programs for O8, switchboards, etc. that mainly involve data manipulation) so that information can be smoothly transmitted between each process, and to The objective is to reduce man-hours by efficiently reusing parts.

[Means to solve the problem]

FIG. 1 is a block diagram of the principle of the present invention.

In the figure, the software development support device according to the present invention includes a database 1 that stores relationships between various documents and data to be operated as links, a data distribution device 2, a data extraction device 3, and a document link device 4.
It is equipped with. The data distribution device 2 sends data to the data extraction device or document link device 4 according to the type of data received from each terminal, and
The data output from the data extraction device 3 is sent to the terminal side. The data extraction device 3 accesses the data hese 1 based on the data sent from the data distribution device 2, extracts the corresponding data, and transfers the data to the data distribution device 2.
It is sent to

The document link device 4 creates a link between a user-created document sent from the data distribution device 2 and data related to this document, and stores this link in the database 1.

With this configuration, when creating a new document, it becomes possible to reuse the document linked to the data to be manipulated as a component.

[For production]

The process of creating software, especially programs for operating systems and switching equipment, is centered around data manipulation. In the database 1, various documents are organized and stored by creating links between various documents and data to be manipulated by the documents. When creating a document, by searching database 1 for the data to be manipulated, documents that are already linked to the target data can be reused as parts, thereby making it easier to reuse parts. It can be promoted efficiently. For example, if there are documents that describe the same operations on the same data among people developing the same process, it will be possible to easily search for them and reuse parts. Furthermore, in order to reuse these parts, the method of expressing operations on data or the content of descriptions can be unified, and the developer of the next process can correctly understand the document.

〔Example〕

The present invention will be explained in detail by explaining the principle diagram of FIG. 1 in detail with reference to FIG. 2 and subsequent drawings. In FIG. 1, the terminal identifier adding device 5 on the terminal side adds the identifier of each terminal 6 to the data sent from the terminal side to the system side and sends it to the system side. The data is sent to the terminal corresponding to the terminal identifier added to the data.

FIG. 2 is a diagram showing an example of the configuration of the database 1. As mentioned above, the database 1 stores various documents, data, and links, and in order to enable easy searching, the data and various documents are arranged in alphabetical order of data name and document name, or Organized alphabetically. In the example shown in FIG. 2, respective parts 201, 202, and 203 of documents such as external specification A, design document A, and program A are linked to the data X portion. In addition, each part 204.205. of external specifications A, design document A, and program A.
206 is linked to the data Y portion. Similarly, the parts 207, 208, and 209 of external specifications B, design document B, and program B are linked to the data Y portion. Other document parts are also linked to data.

FIG. 3 is a diagram showing a screen image when creating external specifications. As shown in the figure, when an external specification is created, the name, function, input format, error end condition, related data name, etc. of the external specification are displayed on the display. When the external specification creator knows the related data, he inputs the data name from the keyboard of the terminal 6 ■. As a result, the name of the related data and the part of the external specification or related document linked to this will be displayed on the right side of the screen as shown in the figure.■
. The creator then specifies a reusable component and its copy destination, and copies the component onto the document being created. In the figure, a component called DN Not Implemented is copied to the "Error Termination Condition" column on the document. If there are no reusable parts, create the document as usual, extract the data-related parts from this document at the end of the creation, specify the parts and related data names, and finish the creation.■ .

FIG. 4 is a diagram showing a screen image when creating a design document or coding a program. As shown in the figure, when a design document is created, external specifications corresponding to the design document are also displayed. In the figure, an external specification C corresponding to the design document and related data and documents are displayed.

FIG. 5 is a flowchart showing the operation algorithm of the data distribution device 2 in the operation from the terminal side to the system side.

Assume that the format of data sent from the terminal side consists of data classification, terminal identifier, and data body, as shown in FIG.

In FIG. 5, in step 51, the data distribution device 2 waits for data from a terminal. When data is received from the terminal, it is determined whether data is extracted or document creation is complete, based on the data classification. When it is determined in step 53 that data should be extracted, the data body and the terminal identifier are sent to the data extraction device 3 in step 54. If it is determined in step 55 that document creation is complete, step 56
The entire document data and link information are sent to the document link device 4.

FIG. 6 is a flowchart showing the operation algorithm of the data distribution device 2 in the operation from the system side to the terminal side.

It is also assumed that the format of the data sent from the data extracting device 3 consists of data classification, terminal identifier, and data body, as shown in FIG.

In FIG. 6, in step 61, the data distribution device 2 waits for data from the data extraction device 3. Step 6
When the data distribution device 2 receives the data in step 1, it sends the data to the terminal corresponding to the terminal identifier therein.

FIG. 8 is a flowchart showing the operation algorithm of the data extraction device 3.

As shown in the figure, the content of the data body consists of search target data, target level, and search keyword. At step 81, the data extraction device 3 waits for data from the data distribution device 2. When the data is received, in step 82 it is determined from the search target data in the data body whether the search target is data or various documents.

If the search target is data, in step 83, data that matches the search keyword in the data body is extracted from database 1, and the document being created by the designer among the documents linked to that data is extracted. Extract documents at the same target level as, for example, external specifications.

If the search target is related to documents, such as external specifications, design documents, or programs, in step 84, documents that match the search keyword from the target level documents in the data body are searched in the database 1.
Extract from.

Step 85 to return the data or document extracted in step 83 or 84 to the destination terminal.
A terminal identifier is added to the data or document and sent to the data distribution device 2.

FIG. 9 is a flowchart showing the operation algorithm of the document link device 4.

As shown in the figure, the data sent from the data distribution device 2 to the document link device 4 includes data for the entire document and link information newly established at the time of document creation.

At step 91, the data of the entire document in the data body sent from the data distribution device 2 is stored at a predetermined location. In step 92, refer to the link information,
Determine whether a new link has been added. If a new link has been established, a link is established between the document and the data based on the link information in step 93, and the document is stored in a predetermined position, for example, in alphabetical order or in alphabetical order.

〔Effect of the invention〕

As explained above, according to the present invention, it is possible to unify the description contents of documents for creating programs for O8, exchanges, etc. that mainly involve data manipulation, thereby facilitating information transmission between each process. can be done. or,
Since document parts can be reused efficiently, it is possible to reduce man-hours when creating data and documents.

[Brief explanation of the drawing]

Figure 1 is a block diagram of the principle of the present invention, Figure 2 is a diagram showing the configuration of the database, Figure 3 is a diagram showing a screen image for creating external specifications, and Figure 4 is for creating a design document or coding. Figure 5 is a flowchart showing the operation algorithm from the terminal side to the system side of the data distribution device, Figure 6 is a flowchart showing the operation algorithm from the system side to the terminal side of the data distribution device, and Figure 7 is a diagram showing a screen image. FIG. 8 is a flowchart showing the operation algorithm of the data extracting device. FIG. 9 is a flowchart showing the operation algorithm of the document linking device. FIG. 10 is an explanatory diagram of the software development process that forms the background of the present invention, and FIG. 11 is a diagram for explaining conventional problems. In the figure, 1... Database, 2... Data distribution device, 3... Data extraction device, 4... Document link device, 5... Terminal identifier adding device, 6...
It is a terminal.

Claims (1)

[Claims] 1. A database (1) that stores relationships between various documents and data to be manipulated as links, a data distribution device (2), a data extraction device (3), and a document link device (4). ), and the data distribution device (2) sends the data to the data extraction device or the document link device (4) according to the type of data received from each terminal, and also outputs the data to the data extraction device or the document link device (4). The data output from the device (3) is sent to the terminal side, and the data extraction device (3) accesses the database (1) based on the data sent from the data distribution device (2). and extracts the corresponding data and sends it to the data distribution device (2),
The document link device (4) provides a link between the document created by the user and the data related to the document sent from the data distribution device (2), and links the link to the database (1). A software development support device characterized in that a document linked to data to be manipulated when creating a new document can be reused as a component.