JPH10105390A - Inter-specifications cross-reference table - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide the inter-specifications cross-reference table through which the influence range of a change in customer's request on respective specifications and a source program can easily be grasped. SOLUTION: An identification number specifying an entry place of software request specifications is entered into a field 2, an identification number specifying an entry place of software design specifications is entered into a field 3, and a mark 61 showing whether or not there is the relativity between the entry places of the software request specifications and software design specifications is entered into a 1st matrix field 6. Similarly, an identification number specifying an entry place of program specifications is entered into a field 4 and a mark 71 showing whether or not there is the relativity between the entry places of the software design specifications and program specifications is entered into a 2nd matrix field 7. Further, an identification number specifying a constitution unit of the source program is entered into a field 5 and a mark 81 showing whether or not there is the relativity between the entry place of the program specifications and the constitution unit of the source program is entered into a 3rd matrix field 8.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a cross-reference table between specifications, which is created in a software development work, and whose relation to a source program is clear at a glance.

[0002]

2. Description of the Related Art Generally, a computer source program is developed by dividing the development process into several steps, creating a specification at the end of each step, and moving to the next step. FIG. 1 shows the relationship between such a software development process and specifications created in each process. As shown in the figure, a source program A, which is a product of software development, has a customer analysis B as a starting point, a software analysis process C which is the most upstream process, a schematic design process D which is the next process, and a next design process D which is the next process. It is developed through four processes: a detailed design process E, which is a process, and a manufacturing process F, which is the most downstream process.

In a software analysis process C, a customer request B
Based on the above, the environment surrounding the system and the functions and performance required for the software are analyzed, and these are summarized as software requirements specifications. A document describing the contents of the software requirement specification is a software requirement specification G.
The software requirement specification G describes the outline of the system, the contents of processing of each function, the implementation requirement specification, and the like, and all the subsequent steps are performed based on the software requirement specification G.

The following schematic design process D and detailed design process E
Then, the software requirement specifications created in the software analysis step C are converted into design specifications having a structure that can be efficiently executed on a computer. Of these, in the schematic design process D, the system is divided into several programs based on software requirement specifications, each program is further divided into several modules, a connection method and the like between them are determined, and software design is performed. Summarize as specifications. A document describing the contents of the software design specification is the software design specification H, and the system hierarchy,
The function hierarchy, interfaces between modules, functions of individual modules, and the like are described. On the other hand, detailed design process E
Then, based on the software design specifications created in the schematic design process D, determine the processing procedure of each module,
This is summarized as a program specification, and a program specification I is created. This program specification I describes the module structure, the file and table structures, the processing procedure of the module represented by a flowchart, and the like.

In a final manufacturing process F, a source code of the program is described based on the program specifications created in the detailed design process E, and a source program A including a plurality of modules is created.

[0006]

The development of a source program proceeds in the above-described steps, and in the process, various specifications are created. However, each specification exists independently, and other specifications exist. The details of the correlation with the book are not described. For this reason, there is a problem that it is difficult to understand how the items described in each specification are reflected in other specifications. Therefore, if the customer's requirements change after the production of the source program, it is not easy to grasp the influence on each specification and the source program. Conversely, if the contents of the source program are changed (addition, deletion, etc.), it will affect which items in each specification and how much will eventually affect customer requirements. It was not easy to figure out.

Japanese Patent Application Laid-Open No. Hei 6-139061 describes a technique for automatically generating specifications that accurately reflect the contents of a source program from a source program itself. This document describes a technique for creating a system diagram of document information such as a functional manual, an instruction manual, and a module specification document relating to a program. By applying these techniques, it is possible to understand to some extent the range of influence on the program specification when the contents of the source program are changed. However, the range of influence on the software design specification and software requirement specification in the further upstream process is unknown, and therefore, it is also unknown how much influence it has on customer requirements. Further, it is not useful for grasping the range of influence on each specification and the source program when a change occurs in a customer's request.

The present invention solves such a conventional problem. The purpose of the present invention is to change the range of influence of a change in a customer request on each specification and a source program and vice versa. It is an object of the present invention to provide a cross-reference table between specifications which can easily grasp the range of influence on specifications and customer requirements.

[0009]

According to the present invention, there is provided a cross-reference table between specifications, wherein a software request in which identification numbers for specifying a description location of a software requirement specification created based on a customer request in software development work are described in a row. A specification identification number column, a software design specification identification number column in which identification numbers for specifying a description portion of a software design specification created based on a software requirement specification in software development work are arranged in a row, and two adjacent sides. One is a matrix column that contacts the software requirement specification identification number column, and the other is a matrix column that contacts the software design specification identification number column, and is specified by the identification number described in the software requirement specification identification number column. The location of the software requirement specification and the software design specification Whether or not there is a relationship with the description part of the software design specification identified by the identification number described in the number column is determined by the presence or absence of a mark on the intersection of the row and column determined by the position of the identification number in both columns The first expressed
A matrix column, a program specification identification number column in which identification numbers for specifying a description portion of a program specification created based on the software design specification in software development work are listed in a row, and one of two adjacent sides is In the software design specification identification number field, the other is a matrix field which is in contact with the program specification specification identification number field, respectively, and the software design specification specification identified by the identification number described in the software design specification identification number field. The presence or absence of a relationship between the description location and the description location of the program specification specified by the identification number described in the program specification identification number column is determined by the row and column determined by the description position of the identification number in both columns. A second matrix column expressed by the presence or absence of a mark on the intersection of A source program identification number column in which identification numbers for specifying constituent units of a source program created based on a program specification are listed in a row, one of two adjacent sides is in the program specification identification number column, and the other is the source. A matrix column that is in contact with each of the program identification number columns, a description portion of the program specification specified by the identification number described in the program specification identification number column, and an identification number described in the source program identification number column And a third matrix field that expresses the relevance of the source program to the constituent units specified in the above by the presence or absence of a mark on the intersection of a row and a column determined by the position of the identification number in both columns. Have been.

Further, according to the present invention, an identification number for specifying a location of a software requirement specification, an identification number for specifying a location of a software design specification, and an identification number for specifying a location of a program specification are included in each specification. , Which has an identification number assigned to each content of the table of contents, and has a format of specification section-chapter number-item number.

In the cross-reference table between specifications according to the present invention, for example, a specification classification is performed for each content of a table of contents of a software requirement specification created based on a customer request.
By specifying an identification number such as a chapter number-item number, the description location is specified, and similarly, the description location of the software design specification and the program specification is specified by the same identification number,
The mark on the first matrix column associates the relevant description places between the software requirement specification and the software design specification, and the mark on the second matrix column shows the relevant description place between the software design specification and the program specification document. And the mark on the third matrix column associates the location of the program specifications with the constituent units of the source program. Therefore, the range of influence of the change in customer requirements on each specification and the source program is as follows. It can be easily confirmed by sequentially examining the first matrix column, the second matrix column, and the third matrix column. Conversely, the range of influence of the change of the source program on each specification and customer requirements is as follows.
This can be easily confirmed by sequentially examining the third matrix column, the second matrix column, and the first matrix column.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 2 is a plan view of an embodiment of the cross-reference table between specifications according to the present invention. The inter-specification cross reference table in this example is a table showing the mutual relation between the software requirement specification G, the software design specification H, the program specification I, and the source program A described with reference to FIG. 4 on paper 1 such as white paper
One identification number column 2, 3, 4, 5 and a total of three matrix columns 6, 7, 8 are drawn.

The identification number column 2 is a software requirement specification identification number column in which identification numbers for specifying the description location of the software requirement specification G are vertically arranged in a line. In the identification number column 2, identification number description fields 20 are arranged vertically in a line, and one identification number can be described in each of them.

The identification number column 3 is a software design specification identification number column in which identification numbers for specifying the description locations of the software design specification H are described in a row. In the identification number column 3, identification number description fields 30 are arranged in a row in a row, and one identification number can be described in each of them.

The identification number column 4 is a program specification identification number column in which identification numbers for specifying the location of the program specification I are vertically arranged in a line. In the identification number column 4, identification number description fields 40 are arranged in a row in a row, and one identification number can be described in each of them.

The identification number column 5 is a source program identification number column in which identification numbers for specifying the constituent units of the source program A are described in a row. In the identification number column 5, identification number description fields 50 are arranged horizontally in a line, and one identification number can be described in each of them.

The first matrix column 6 is drawn such that one of two adjacent sides is in contact with the vertical side of the identification number column 2 and the other is in contact with the horizontal side of the identification number column 3, respectively. It has a matrix (lattice) 60 consisting of a row corresponding to the identification number description field 20 in the column 2 on a one-to-one basis and a column corresponding to the identification number description field 30 in the identification number column 3 on a one-to-one basis.

In the second matrix column 7, one of two adjacent sides is located on the side opposite to the first matrix column 6 in the identification number column 3, and the other is located on the vertical side of the identification number column 4. A matrix which is drawn so as to be in contact with each other and has a row corresponding to the identification number description field 40 of the identification number column 4 on a one-to-one basis and a column corresponding to the identification number description field 30 of the identification number column 3 on a one-to-one basis. (Grating) 70.

In the third matrix column 8, one of two adjacent sides is a vertical side of the identification number column 4 opposite to the second matrix column 7, and the other is a horizontal side of the identification number column 5. The matrix is drawn so as to be in contact with each other, and is made up of a row corresponding to the identification number description field 40 of the identification number column 4 on a one-to-one basis and a column corresponding to the identification number description field 50 of the identification number column 5 on a one-to-one basis. (Grating) 80.

The first matrix column 6 contains an identification number column 2
Indicates whether there is a relationship between the description location of the software requirement specification G specified by the identification number described in the above and the description location of the software design specification H specified by the identification number described in the identification number column 3 The mark 61 is displayed at an appropriate place.
That is, at the intersection of the row and the column determined by the identification number description fields 20 and 30 in both columns, the software requirement specification G and the software design specification H specified by the identification numbers described in both fields. Are described, for example, the mark 61 is displayed, otherwise the mark 61 is not displayed.

The second matrix column 7 has an identification number column 3
Mark indicating whether or not there is a relationship between the description location of the software design specification H specified by the identification number described in (1) and the description location of the program specification I specified by the identification number described in the identification number column 4 71 is displayed in place. That is,
At the intersection of the row and the column determined by the identification number entry fields 30 and 40 in both fields, the description location of the software design specification H and the program specification I specified by the identification numbers entered in both fields Are related to each other, for example, the mark 71 is displayed. Otherwise, the mark 71 is not displayed.

The third matrix column 8 contains an identification number column 4
Specification I specified by the identification number described in
And a mark 81 indicating whether or not there is a relationship between the described location and the constituent unit of the source program A specified by the identification number described in the identification number column 5 is displayed at an appropriate place. That is, at the intersection of the row and the column determined by the identification number description fields 40 and 50 of both columns, the description location of the program specification I characterized by the identification number described in both fields and the source program A Are associated with each other, for example, the mark 81 is displayed, otherwise the mark 81 is not displayed.

According to the cross reference table between specifications having such a configuration, for example, when there is a change in a customer request,
An identification number description field 20 in which the identification number of the description part of the software specification G related to the change is described is searched from the identification number column 2, and a circle mark on the row of the first matrix column 6 corresponding to this field 20 61, and by looking at the identification number in the identification number entry field 30 of the identification number column 3 corresponding to the column that intersects with the row marked with the mark 61, it is possible to find the location of the affected software design specification H. You can know. In addition, the O mark 71 on the column of the second matrix column 7 corresponding to the identification number description field 30 is found, and the identification number column 4 corresponding to the row crossing the column where the O mark 71 is attached is identified. By looking at the identification number in the number description field 40, it is possible to know the location where the program specification I is affected.
Further, a circle mark 81 on the row of the third matrix column 8 corresponding to the identification number description field 40 is found,
By looking at the identification number in the identification number entry field 50 of the identification number column 5 corresponding to the column that intersects with the row marked with the mark 81, it is possible to know the constituent units of the source program A affected.

On the other hand, when a certain structural unit of the source program A is changed, an identification number description field 50 in which the identification number of the structural unit related to the change is described is searched from the identification number column 5. The third corresponding to
Is found on the column of the matrix column 8 of the above, and by looking at the identification number in the identification number description field 40 of the identification number column 4 corresponding to the row intersecting the column where the circle mark 81 is attached, It is possible to know the places described in the extended program specification I. In addition, the O mark 71 on the row of the second matrix column 7 corresponding to the identification number description field 40 is found, and the identification number column 3 corresponding to the column intersecting the row where the O mark 71 is attached is identified. By looking at the identification number in the number description field 30, it is possible to know the description location of the affected software design specification H. Further, the O mark 61 on the column of the first matrix column 6 corresponding to the identification number description field 30 is found, and the identification number column 2 corresponding to the row intersecting the column where the O mark 61 is attached is identified. By looking at the identification number in the number description field 20, it is possible to know the description location of the affected software requirement specification G, and therefore the impact on the customer requirement.

Next, an example of a method for creating a cross reference table between specifications according to the present invention will be described.

First, the identification numbers described in the identification number columns 2, 3, and 4 will be described.

As with ordinary books, the software requirement specification G, software design specification H, and program specification I generally have a table of contents. The table of contents is
Chapters such as Chapter 1 and Chapter 2 are divided, and each chapter is often divided into Sections 1 and 2. For this reason, it is possible to specify the description portion of the specification at the table of contents level. Further, different specifications can be identified by using abbreviations of the names of the specifications. FIG.
(A) shows a general format example of an identification number based on such a concept.

In FIG. 3A, "specification class" is a code for distinguishing each specification from other specifications. For example, as shown in FIG. "REQ" for software design specifications, "DSG" for software design specifications, and "P
RG "are respectively assigned.

In FIG. 3A, the "chapter number" is a code for identifying each of the sections belonging to the major category appearing in the table of contents of each specification, and the "section number" is the part of each section. Is a code for further classifying.

FIG. 4 shows an example of a table of contents of the software requirement specification G and an example of assignment of identification numbers. Since the specification category of the software requirement specification G is REQ from FIG. 3B, the head of all identification numbers is REQ. The table of contents for this example is described in “Chapter 1 Overview”, “Chapter 2 Function Requirements Specifications”, “Chapter 3 Implementation Requirements Specifications”, “Chapter 4 External Interface Requirements Specifications”, and “Chapter 5 Design Requirements”. It consists of five chapters, which correspond to major categories. For this reason, identification numbers REQ-1 to REQ-5 are assigned to each of them. Further, since each chapter is divided into several items as exemplified in “Chapter 2. Function Group 1” and “2. Function Group 2” in Chapter 2, item numbers are assigned, and for example, “1. REQ-2-1 for "Function group 1", R for "2. Function group 2"
An identification number such as EQ-2-2 is used.

Further, as shown in “1. Function Group 1”, these items are “(1) Function 1-1”,
If it is further classified as “(2) Function 1-2”,
REQ-2-11 for "(1) Function 1-1"
The identification number REQ of the parent “1. Function group 1” as in REQ-2-12 for “(2) Function 1-2”
The identification number is obtained by adding a numerical value to be a serial number to the end of the item number of -2-1. Further, when the content is further divided into several parts as in “(1) Function 1-1”, the identification number of the parent is distinguished by adding a serial number to the end of the item number. For example, REQ-2-111, "General description"
REQ-2-112 for “Description of command processing”,
REQ-2-113, "Description of alarm processing"
REQ-2-114 is assigned to “state transition”, REQ-2-115 is assigned to “interface”, and REQ-2-116 is assigned to “performance request”. Similarly, when these contents are further subdivided, a serial number is added to the end of the item number of the parent identification number. In FIG.
REQ-2 for refining "description of command processing"
−1121 to REQ-2-112m are used, and REQ-2-11 is used to refine the “description of alarm processing”.
31 to REQ-2-113n are used.

By describing the unique identification numbers as described above in each part of the table of contents of the software requirement specification G, the description location of the software requirement specification G created based on customer requirements in software development work is specified. be able to. Similarly, it is possible to specify the description places of the software design specification H and the program specification I.

Next, the identification numbers described in the identification number column 5 will be described. The identification number described in the identification number column 5 is an identification number that specifies a constituent unit of the source program A. Since the source program A has no table of contents unlike the specifications G, H, and I, a unique name for each structural unit is used as the identification number. For example, each module generally has a unique module name,
This module name can be used as an identification number.

Now, once the identification numbers for specifying the places to be described in the specifications G, H, and I and the identification numbers of the constituent units of the source program A are determined, they are entered into the identification number fields 2 and 3 in FIG.
Described in a line in 3, 4, and 5. Then, the relevance between the description location of the software requirement specification G and the description location of the software design specification H is checked, and the corresponding mark in the first matrix column 6 is marked with a circle 61, and the software design specification H Of the program specification I is checked by checking the relevance between the description part of the program specification I and the mark 71 at the corresponding position in the second matrix column 7.
Of the description unit and the constitutional unit of the source program A, a mark 81 is added to a corresponding position of the third matrix column 8, and a cross reference table between specifications is completed.

[0036]

As described above, according to the present invention, the following effects can be obtained.

By sequentially examining the first matrix column, the second matrix column, and the third matrix column, it is possible to easily confirm the influence range of the change of the customer request on each specification and the source program.

Conversely, by sequentially examining the third matrix column, the second matrix column, and the first matrix column, it is possible to easily confirm the influence range of the change of the source program on each specification and customer requirements.

As described above, the relevance between the various specifications created in the software development work and the relationship with the source program is made clear at a glance by the inter-specification cross reference table of the present invention. In addition, it is possible to quickly carry out the work of changing the source program, and conversely, it is possible to carry out the work of changing various specifications accompanying the change of the source program and to evaluate the impact on customer requirements promptly, thus improving the efficiency of software development work. Is possible.

Since the software design specification identification number column is common to the first and second matrix columns and the program specification identification number column is common to the second and third matrix columns, the software There is an advantage that the work of tracing the identification number related to the direction from the specification identification number column to the source program identification number column or the opposite direction can be easily performed, and the required paper area can be reduced.

Further, since the matrix column is used, one to n
Can also be easily expressed.

[Brief description of the drawings]

FIG. 1 is a diagram showing a relationship between a software development process and specifications created in each process.

FIG. 2 is a plan view of an embodiment of a cross reference table between specifications according to the present invention.

FIG. 3 shows a general format example of identification numbers set in a software requirement specification identification number column, a software design specification identification number column, and a program specification identification number column, and a code of a specification classification code of each specification. It is a figure which shows an example.

FIG. 4 is a diagram showing an example of a table of contents of a software requirement specification and an example of assignment of identification numbers.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Paper 2 ... Software requirement specification identification number column 3 ... Software design specification identification number column 4 ... Program specification identification number column 5 ... Source program identification number column 6 ... 1st matrix column 7 ... 2nd matrix column 8: Third matrix field 20, 30, 40, 50 ... Identification number description field 61, 71, 81 ... Mark indicating relevance

Claims (3)

[Claims] 1. A software requirement specification identification number field in which identification numbers for specifying a description location of a software requirement specification created based on a customer request in a software development operation are listed in a row, and a software requirement specification document in the software development operation. A software design specification identification number field in which identification numbers for specifying the description places of the software design specification document created based on the above are described in a row, one of the two adjacent sides is in the software requirement specification identification number field, and the other is on the other side. A matrix field adjacent to the software design specification identification number field, a description location of a software requirement specification identified by an identification number described in the software requirement specification identification number field, and a software design specification identification The software settings identified by the identification number described in the number column A first matrix column expressing the presence or absence of relevance to the specification location by the presence or absence of a mark on the intersection of a row and a column determined by the location of the identification number in both columns; A program specification identification number column in which identification numbers for specifying a description portion of a program specification created based on a design specification are described in a row, and one of two adjacent sides is in the software design specification identification number column, and the other is in the other side. Is a matrix column that is in contact with the program specification identification number column, respectively, a description location of the software design specification identified by the identification number described in the software design specification identification number column, and the program specification identification number In both columns, the presence or absence of relevance to the location of the program specification specified by the identification number described in the column is identified. A second matrix column expressed by the presence or absence of a mark on the intersection of a row and a column determined by the description position of a number, and an identification number for specifying a constituent unit of a source program created based on a program specification in software development work A source program identification number column described in a line, and a matrix column in which one of two adjacent sides is in contact with the program specification identification number column and the other is a matrix column in contact with the source program identification number column. Column, the location of the program specification specified by the identification number described in the column, and the presence or absence of association with the source program configuration unit specified by the identification number described in the source program identification number column, Expressed by the presence or absence of a mark on the intersection of the row and column determined by the position of the column identification number Cross-reference table between the composed specification from three of the matrix column. 2. An identification number for specifying a location of a software requirement specification, an identification number for specifying a location of a software design specification, and an identification number for specifying a location of a program specification are listed in the table of contents of each specification. 2. The cross-reference table between specifications according to claim 1, wherein the identification number is an identification number assigned to each content. 3. An identification number for specifying a place to be described in a software requirement specification, an identification number for specifying a place to be described in a software design specification, and an identification number for specifying a place to be described in a program specification are classified into specification sections-chapter numbers-. 3. The cross-reference table between specifications according to claim 2, wherein the cross-reference table has an item number format.