JP4849555B2 - Software specification / design inconsistency detection apparatus, program and method thereof - Google Patents

Description

  The present invention belongs to the technical field of detecting inconsistencies in specifications / design documents expressing the operation of software to be developed during software development.

  In software development, create a specification that shows the items to be satisfied by the software to be developed, and create a design document that defines the structure and architecture of the software with specific implementation in mind based on the specification. The final implementation is based on the document. These specifications and design documents describe the functions of the software.

  Software functions are represented by two aspects: a static aspect in which information managed by software is expressed by classes and attributes, and a dynamic aspect in which software operations are expressed by messages and methods. Such information and operations are described in a document using a natural language or a diagram using a model language (UML: Unified Modeling Language). At this time, the larger the software scale, the more complicated the operation of the software, and the description amount and complexity of the operation increase. Therefore, it takes time for the software developer to describe the operation of the software, and it has been a problem that software development becomes expensive / long-term.

  As a cause of the high cost / prolongation, if a specification / design document created at a certain point contains an error and development is proceeding without noticing it, the error can be discovered and corrected later. Sometimes a return occurs and development is redone. In order to prevent such rework, there is a need for a technique for preventing errors in software specifications / design documents created during development.

  Non-Patent Document 1 reports a system for determining the consistency of UML coordination diagrams. However, software development does not completely solve the problem because it uses many documents other than cooperative diagrams.

  Non-Patent Document 2 proposes a method for verifying a UML class diagram. However, as in the case of Non-Patent Document 1, it cannot be applied to other documents, so it cannot be said that all problems have been solved.

  As one of other documents used for software development, a specification / design document that expresses the operation of software in time series is used. Hereinafter, a specification / design document that represents the operation of software in time series is referred to as a sequence diagram. The sequence diagram expresses the operation of software by sending and receiving messages of objects constituting the software. At this time, since it is difficult to determine whether the exchange of messages can represent the operation of the software without any contradiction, it has become a cause of error in the sequence diagram.

  As shown in FIG. 1, the sequence diagram is composed of an object that is the operation of the software, a message name indicating the content of the operation, and a parameter indicating information used for the operation. It is expressed by a message placed in In order to simplify the description, the following description will be made assuming that message name = message.

  Typical errors in the software operations described in the sequence diagram may be that unnecessary operations are described and necessary operations are not described. The error may be described on the sequence diagram as an object operation including the following inconsistency.

  Send information that has not been received from other objects.

  ・ Do not send information received from other objects.

  FIG. 2 shows an example of a sequence diagram including the above mismatch. In FIG. 2, the object 2 receives parameters a and b from the object 1 with the message 1 and transmits parameters a and c to the object 3 with the message 2. In this case, the object 2 has only the parameters a and b when the message 1 is received. Thereafter, the parameters transmitted by the message 2 are a and c, but the object 2 does not have the parameter c at that stage. That is, the object 2 is trying to transmit a parameter that the object 2 does not have to the object 3, which is inconsistent as a software operation.

Since the sequence diagram of FIG. 2 is simple, it is easy to find such inconsistencies, but it is difficult to find inconsistencies in larger and complex sequence diagrams.
Hiroyuki Nakanishi, Takao Miura “Realization of UML Consistency Verification System Using Description Logic”, DEWS 2005 Proceedings, 1-Ao4, May 2, 2005 Ken Sato, Ken Kaneiwa “On Consistency Checking Using Logic Programming in UML Class Diagrams”, Proceedings of the 22nd Annual Meeting of the Japan Society for Software Science and Technology, PD-11, 2005

  When the development proceeds with the sequence diagram including the above inconsistency, after development is performed according to the sequence diagram including the inconsistency, an error that caused the inconsistency is discovered, and the rework is to be repeated. Can happen. Therefore, there is a need for a technique for detecting inconsistencies in sequence diagrams and preventing rework from occurring.

  An object of the present invention is to provide an apparatus, a program, and a method for detecting inconsistencies in a sequence diagram that represents software operations in time series in software development.

  In order to detect inconsistencies in the sequence diagram, the transmitted parameter and the received parameter are recorded for each object. Since the sequence diagram represents a time-series software operation, detection processing is performed by tracing messages transmitted / received by the object in time-series.

  First, for each object in the sequence diagram, a transmission buffer for recording parameters of a message transmitted by the object and a reception buffer for recording parameters of a message received by the object are prepared. These buffers are used to record parameters sent and received by the object. FIG. 3 is an image of a transmission buffer and a reception buffer prepared for each object.

  In the present invention, inconsistencies in the sequence diagram are detected in the following flow shown in FIG.

  Messages are acquired in chronological order, and the following processing is performed on the sending object and receiving object of the message.

  s1: A message is acquired by tracing the sequence diagram from the top in time series.

  s2: It is checked whether or not the parameter of the acquired message is recorded in the reception buffer corresponding to the transmission object that is the object that transmitted the message. If it is recorded, the process proceeds to s3. . However, since one message may handle a plurality of parameters, each message is examined and processed.

  s3: The recorded parameter is added and recorded in the transmission buffer corresponding to the transmission object in order to record the fact that the parameter that has already been received is transmitted. Go to s5.

  s4: The parameter that has not been recorded records an inconsistency that the transmission object is trying to transmit a parameter that has not been received. Go to s5.

  s5: The parameter of the acquired message is added and recorded in the reception buffer corresponding to the reception object that is the object that received the message. This records the parameters received by the object. Go to s6.

  s6: Delete the parameter of the acquired message from the transmission buffer corresponding to the reception object. This records that the parameters received by the object are not yet used. Go to s7.

  s7: Check whether all messages have been acquired. If it is not finished yet, return to s1. When you are finished, go to s8.

  s8: For all objects, the recorded contents of the transmission buffer are compared with the recorded contents of the reception buffer. If the recorded contents are the same, the process ends. If not, go to s9.

  s9: The recorded content of the reception buffer of the object is not the same as the recorded content of the transmission buffer, which means that there is a parameter that has not yet been transmitted among the parameters received by the object. Record the inconsistency that the parameter is unused and exit.

  Note that s2 to s4 and s5 and s6 may be performed in the reverse order.

  According to the present invention, for each object, the parameter of the message transmitted by the object and the parameter of the received message are recorded in the transmission buffer and the reception buffer. Inconsistency that there is a parameter (unused parameter) that has not been transmitted can be detected.

<Software specification / design document inconsistency detection device>
FIG. 5 shows an example of an embodiment of the software specification / design inconsistency detection apparatus of the present invention. In the figure, 1 is a sequence diagram storage unit, 2 is a transmission buffer unit, 3 is a reception buffer unit, 4 is a mismatch recording unit, 5 is a message acquisition unit, 6 is a transmission object processing unit, 7 is a reception object processing unit, 8 is a buffer comparison unit, and 9 is a mismatch detection result display unit.

  The sequence diagram storage unit 1 is a software specification that is input directly from a keyboard or the like (not shown), read from a storage medium, or input from another device or the like via a communication medium. / Save the design document, here the sequence diagram.

  The transmission buffer unit 2 holds a transmission buffer for each object that records parameters transmitted by the object. The reception buffer unit 3 holds a reception buffer for each object that records parameters received by the object.

  Note that the transmission buffer and the reception buffer for each object read information about the object from the sequence diagram stored in the sequence diagram storage unit 1 in advance, and set the transmission buffer and the reception buffer corresponding to each object respectively. In addition, the message may be created in the reception buffer unit 3, or as will be described later, the identification information of the transmission object that is the object that transmitted the message together with the message in the message acquisition unit 5 and the reception object that is the object that received the message When the identification information is acquired, the transmission buffer and the reception buffer corresponding to the acquired identification information of the transmission object, and the transmission buffer and the reception buffer corresponding to the acquired identification information of the reception object are respectively transmitted to the transmission buffer. Part 2 and examines whether present in the receiving buffer unit 3, if there these transmit and receive buffers, respectively, may be created in the transmission buffer section 2 and the receiving buffer unit 3.

  The inconsistency recording unit 4 records the inconsistency detection result in the sequence diagram to be detected.

  The message acquisition unit 5 acquires messages from the sequence diagram stored in the sequence diagram storage unit 1 in chronological order. Strictly speaking, the message acquisition unit 5 is identification information of a transmission object that is an object that has transmitted the message, and an object that has received the message. Acquired together with the identification information of the reception object, outputs it to the transmission object processing unit 6 and the reception object processing unit 7, and performs this for all the messages in the sequence diagram.

  The transmission object processing unit 6 determines whether or not the parameter of the acquired message is recorded in the reception buffer corresponding to the transmission object (identification information) that is the object that transmitted the message in the reception buffer unit 3. If recorded, the parameter is recorded in a transmission buffer corresponding to the transmission object (identification information) in the transmission buffer unit 2, and if not recorded, the transmission object intends to transmit an unreceived parameter. The mismatch detection result is recorded in the mismatch recording unit 4.

  The reception object processing unit 7 records the acquired message parameters in the reception buffer corresponding to the reception object (identification information thereof) that is the object that received the message in the reception buffer unit 3 and also stores the parameter in the transmission buffer unit 2. Delete from the transmission buffer corresponding to the received object (identification information).

  The transmission object processing unit 6 and the reception object processing unit 7 perform the same processing on all messages in the sequence diagram acquired by the message acquisition unit 5.

  The buffer comparison unit 8 compares the recorded content of the transmission buffer in the transmission buffer unit 2 with the recorded content of the reception buffer in the reception buffer unit 3 for all objects. If they are not identical, there is an unused parameter. The inconsistency detection result is recorded in the inconsistency recording unit 4.

  The inconsistency detection result display unit 9 reads the recorded content of the inconsistency recording unit 4 and displays the inconsistency detection result in the sequence diagram to be detected (on a display unit not shown).

  The above-described apparatus can also be realized on a well-known computer. At this time, the sequence diagram storage unit 1, transmission buffer unit 2, reception buffer unit 3, and inconsistency recording unit 4 are a hard disk, a memory, etc. in the computer. The message acquisition unit 5, the transmission object processing unit 6, the reception object processing unit 7, the buffer comparison unit 8 and the inconsistency detection result display unit 9 are an arithmetic processing unit (CPU) and a display unit in a computer. A program corresponding to the flowchart of FIG.

<Software specification / design mismatch detection method>
Next, a software specification / design inconsistency detection method according to the present invention will be described with reference to the flowchart of FIG. 4 and the apparatus configuration diagram of FIG. In the transmission buffer unit 2 and the reception buffer unit 3, it is assumed that transmission buffers and reception buffers respectively corresponding to objects in the sequence diagram to be detected have been created.

  First, the message acquisition unit 5 receives from the sequence diagram storage unit 1 one message in the sequence diagram stored in the sequence diagram storage unit 1 from the top in time series order, identification information of the transmission object of the message, and Acquired together with the identification information of the reception object, and passes it to the transmission object processing unit 6 and the reception object processing unit 7 (s1).

  Next, the transmission object processing unit 6 determines whether or not the parameter of the message passed from the message acquisition unit 5 is recorded in the reception buffer corresponding to the transmission object (identification information) of the message in the reception buffer unit 3. (S2), if it is recorded, the parameter is recorded in a transmission buffer corresponding to the transmission object (identification information thereof) in the transmission buffer unit 2 (s3), and if not recorded, the transmission object A mismatch detection result indicating that an unreceived parameter is to be transmitted is recorded in the mismatch recording unit 4 (s4).

  Further, the reception object processing unit 7 records the parameter of the message passed from the message acquisition unit 5 in the reception buffer corresponding to the reception object (identification information) of the message in the reception buffer unit 3 (s5) and transmits it. It is deleted from the transmission buffer corresponding to the received object (identification information) in the buffer unit 2 (s6).

  The message acquisition unit 5 acquires all messages in the sequence diagram stored in the sequence diagram storage unit 1 from the sequence diagram storage unit 1 similar to the above, and sends the messages to the transmission object processing unit 6 and the reception object processing unit 7. The delivery is repeated (s7).

  Next, the buffer comparison unit 8 compares the recorded content of the transmission buffer in the transmission buffer unit 2 with the recorded content of the reception buffer in the reception buffer unit 3 for all objects (s8). A mismatch detection result indicating that there is a used parameter is recorded in the mismatch recording unit 4 (s9).

  If necessary, the inconsistency detection result display unit 9 reads the recorded contents of the inconsistency recording unit 4 and displays the inconsistency detection result in the sequence diagram to be detected.

  Hereinafter, a specific example of the software specification / design document mismatch detection according to the present invention, here, the operation when the sequence diagram shown in FIG. 6 is input to the apparatus of the present invention as the mismatch detection target will be described. In FIG. 6, A, B, C, and D exist as objects, and expresses the operation of software as shown in the figure. “Message 1” or the like is a message name, and “a” or “b” or the like is a parameter.

  Hereinafter, the transmission buffer of object A is referred to as transmission buffer A, the reception buffer is referred to as reception buffer A, and the same applies to other objects.

  First, the message acquisition unit 5 acquires the message 1 from the sequence diagram storage unit 1 and processes the transmission object A and the reception object B, respectively.

  Transmission object processing unit 6: Since reception buffer A is empty at this stage, parameters a and b of message 1 are determined to be NO in step s2, respectively, and the process proceeds to step s4 to record inconsistencies.

  Reception object processing unit 7: Adds parameters a and b to the reception buffer B in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after finishing the message 1:
> Reception buffer B (a, b)
> Inconsistent recording part ☆ “Unreceived parameter: message 1, object A (a, b)”.

  ● Message 2 is acquired, and transmission object B and reception object C are processed.

  Transmission object processing unit 6: Since a and b are stored in the reception buffer B, YES is determined in step s2, the process proceeds to step s3, and a and b are added to the transmission buffer B.

  Receive object processing unit 7: Adds parameters a and b to the receive buffer C in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after finishing the message 2:
> Reception buffer B (a, b)
> Transmission buffer B (a, b)
> Reception buffer C (a, b)
> Inconsistent recording part ☆ “Unreceived parameter: message 1, object A (a, b)”.

  ● Message 3 is acquired, and transmission object C and reception object B are processed.

  Transmission object processing unit 6: Since the parameters stored in the reception buffer C are a and b, the parameters c and d of the message 2 are determined to be NO in step s2, respectively, and the process proceeds to step s4 to record inconsistency.

  Reception object processing unit 7: Adds parameters c and d to the reception buffer B in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after the message 3 is finished:
> Reception buffer B (a, b, c, d)
> Transmission buffer B (a, b)
> Reception buffer C (a, b)
> Inconsistent recording section ☆ "Unreceived parameter: Message 1, object A (a, b)"
☆ “Unreceived parameter: message 3, object C (c, d)”.

  ● Message 4 is acquired, and transmission object B and reception object D are processed.

  Transmission object processing unit 6: Since the parameters stored in the reception buffer B are a, b, c, and d, the parameters c and d of the message 4 are determined to be YES in step s2, and c and d are stored in the transmission buffer B. to add. Further, the parameter e of the message 4 is determined as NO in step s2, and the process proceeds to step s4 to record inconsistency.

  Receive object processing unit 7: Adds parameters c, d, e to the receive buffer D in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after the message 4 is finished:
> Reception buffer B (a, b, c, d)
> Transmission buffer B (a, b, c, d)
> Reception buffer C (a, b)
> Reception buffer D (c, d, e)
> Inconsistent recording section ☆ "Unreceived parameter: Message 1, object A (a, b)"
☆ "Unreceived parameter: Message 3, object C (c, d)"
☆ "Unreceived parameter: message 4, object B (e)".

  ● Acquire message 5 and process transmission object D and reception object B, respectively.

  Transmission object processing unit 6: Since the parameters stored in the reception buffer D are c, d, and e, the parameter c of the message 5 is determined as YES in step s2, and c is added to the transmission buffer D. Further, the parameters b, f, and g of the message 5 are determined to be NO in step s2, and the process proceeds to step s4 to record inconsistency.

  Receive object processing unit 7: Parameters b, c, f, and g are added to the receive buffer B in step s5. Since b and c exist in the transmission buffer B, b and c are deleted from the transmission buffer B in step s6.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after finishing the message 5:
> Reception buffer B (a, b, c, d, f, g)
> Transmission buffer B (a, d)
> Reception buffer C (a, b)
> Reception buffer D (c, d, e)
> Transmission buffer D (c)
> Inconsistent recording section ☆ "Unreceived parameter: Message 1, object A (a, b)"
☆ "Unreceived parameter: Message 3, object C (c, d)"
☆ "Unreceived parameter: Message 4, Object B (e)"
☆ "Unreceived parameter: message 5, object D (b, f, g)".

  ● Acquire message 6 and process transmission object B and reception object A, respectively.

  Transmission object processing unit 6: Since the parameters stored in the reception buffer B are a, b, c, d, f, and g, the parameters f and g of the message 6 are determined to be YES in step s2, and the transmission buffer B stores them. Add f and g.

  Receive object processing unit 7: Adds parameters f and g to the receive buffer A in step s5.

-Status of the buffer storage unit and inconsistent recording unit after completion of message 6:
> Reception buffer B (a, b, c, d, f, g)
> Transmission buffer B (a, d, f, g)
> Reception buffer C (a, b)
> Reception buffer D (c, d, e)
> Transmission buffer D (c)
> Reception buffer A (f, g)
> Inconsistent recording section ☆ "Unreceived parameter: Message 1, object A (a, b)"
☆ "Unreceived parameter: Message 3, object C (c, d)"
☆ "Unreceived parameter: Message 4, Object B (e)"
☆ "Unreceived parameter: message 5, object D (b, f, g)".

  Since all messages have been completed, the buffer comparison unit 8 compares the transmission buffers and reception buffers of all objects.

  Object A: Since the reception buffer A has f and g and the transmission buffer A is empty, the fact that the parameters f and g are unused is recorded in the inconsistency recording unit 4.

  Object B: Compares the buffers and records that the parameters b and c are unused.

  Object C: Compare buffers and record that parameters a and b are unused.

  Object D: Compares the buffers and records that the parameters d and e are unused.

・ Inconsistent recording section> “unreceived parameter: message 1, object A (a, b)”
>"Unreceived parameter: message 3, object C (c, d)"
>"Unreceived parameter: message 4, object B (e)"
>"Unreceived parameter: message 5, object D (b, f, g)"
>"Unused parameter: Object A (f, g)"
>"Unused parameter: Object B (b, c)"
>"Unused parameter: object C (a, b)"
>"Unused parameter: object D (d, e)".

  The inconsistency detection result display unit 9 reads the contents of the inconsistency recording unit 4 and displays the inconsistency detection result of the sequence diagram.

  The sequence diagram of the first embodiment represents the operation of software in which all messages are continuously connected. Next, an embodiment of a sequence diagram in which messages are not continuous as shown in FIG. 7 will be described.

  ● Message 1 is acquired, and transmission object A and reception object B are processed.

  Transmission object processing unit 6: Since reception buffer A is empty at this stage, parameters a and b of message 1 are determined to be NO in step s2, respectively, and the process proceeds to step s4 to record inconsistencies.

  Reception object processing unit 7: Adds parameters a and b to the reception buffer B in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after finishing the message 1:
> Reception buffer B (a, b)
> Inconsistent recording part ☆ “Unreceived parameter: message 1, object A (a, b)”.

  ● Message 2 is acquired, and transmission object B and reception object C are processed.

  Transmission object processing unit 6: Since a and b are stored in the reception buffer B, YES is determined in step s2, the process proceeds to step s3, and a and b are added to the transmission buffer B.

  Receive object processing unit 7: Adds parameters a and b to the receive buffer C in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after finishing the message 2:
> Reception buffer B (a, b)
> Transmission buffer B (a, b)
> Reception buffer C (a, b)
> Inconsistent recording section ☆ “Unreceived parameter = message 1, object A (a, b)”.

  ● Message 3 is acquired, and transmission object B and reception object C are processed.

  Transmission object processing unit 6: Since the parameters stored in the reception buffer B are a and b, the parameter a of the message 3 is determined as YES in step s2, and a is added to the transmission buffer B. Further, the parameter c of the message 3 is determined to be NO in step s2, and the process proceeds to step s4 to record inconsistency.

  Receive object processing unit 7: Parameters a and c are added to the receive buffer C in step s5.

The situation of the buffer units 2 and 3 and the inconsistent recording unit 4 after the message 3 is finished:
> Reception buffer B (a, b)
> Transmission buffer B (a, b)
> Reception buffer C (a, b, c)
> Inconsistent recording section ☆ "Unreceived parameter: Message 1, object A (a, b)"
☆ "Unreceived parameter: message 3, object B (c)".

  Since all messages have been completed, the buffer comparison unit 8 compares the transmission buffers and reception buffers of all objects.

  Object C: Compare buffers and record that parameters a, b, and c are unused.

・ Inconsistent recording section> “unreceived parameter: message 1, object A (a, b)”
>"Unreceived parameter: message 3, object B (c)"
>"Unused parameter: object C (a, b, c)".

  The inconsistency detection result display unit 9 reads the contents of the inconsistency recording unit 4 and displays the inconsistency detection result of the sequence diagram.

An explanatory diagram showing an example of a sequence diagram Explanatory drawing which shows an example of the sequence diagram containing inconsistency Explanatory drawing of the transmission buffer and the reception buffer prepared for each object in the sequence diagram Flowchart of Software Specification / Design Document Inconsistency Detection Method of the Present Invention The block diagram which shows an example of embodiment of the inconsistency detection apparatus of the software specification / design document of this invention Explanatory drawing which shows the sequence diagram of the mismatch detection object which concerns on Example 1. FIG. Explanatory drawing which shows the sequence diagram of the mismatch detection object which concerns on Example 2. FIG.

Explanation of symbols

  1: sequence diagram storage unit, 2: transmission buffer unit, 3: reception buffer unit, 4: inconsistency recording unit, 5: message acquisition unit, 6: transmission object processing unit, 7: reception object processing unit, 8: buffer comparison Section 9: Inconsistency detection result display section.

Claims (3)

A software operation is expressed by an object that is the subject of the operation, a message name indicating the content of the operation, and a parameter indicating information used for the operation, and messages arranged in time series between the objects. A device for detecting inconsistencies between specifications / designs,
A specification / design document storage means for storing a specification / design document to be detected;
A send buffer for each object that records the parameters of the message sent by the object;
A receive buffer for each object that records the parameters of the message received by the object;
Inconsistency recording means for recording a detection result of inconsistency in a specification / design document to be detected;
Message acquisition means for acquiring messages from the specification / design document stored in the specification / design document storage means in chronological order;
It is determined whether or not the parameter of the acquired message is recorded in the reception buffer corresponding to the transmission object that is the object that transmitted the message. If the parameter is recorded, the parameter is recorded in the transmission buffer corresponding to the transmission object. And a transmission object processing means for recording inconsistency recording means a result of inconsistency detection indicating that the transmission object intends to transmit an unreceived parameter if not recorded,
A received object processing means for recording the parameter of the acquired message in a reception buffer corresponding to the reception object that is the object that has received the message and deleting the parameter from the transmission buffer corresponding to the reception object;
Buffer comparison means that compares the recorded contents of the transmission buffer with the recorded contents of the reception buffer for each object and records inconsistencies in the inconsistent recording means that there is an unused parameter if they are not the same. A software specification / design inconsistency detection device characterized by A software operation is expressed by an object that is the subject of the operation, a message name indicating the content of the operation, and a parameter indicating information used for the operation, and messages arranged in time series between the objects. A program for realizing a device for detecting inconsistency between specifications / designs using a computer including at least a storage device and an arithmetic processing unit,
The storage device of the computer,
A specification / design document storage means for storing a specification / design document to be detected;
A send buffer for each object that records the parameters of the message sent by the object;
A receive buffer for each object that records the parameters of the message received by the object;
In addition to functioning as inconsistency recording means for recording inconsistency detection results in the specification / design document to be detected,
An arithmetic processing unit of the computer,
Message acquisition means for acquiring messages from the specification / design document stored in the specification / design document storage means in chronological order;
It is determined whether or not the parameter of the acquired message is recorded in the reception buffer corresponding to the transmission object that is the object that transmitted the message. If the parameter is recorded, the parameter is recorded in the transmission buffer corresponding to the transmission object. And a transmission object processing means for recording inconsistency recording means a result of inconsistency detection indicating that the transmission object intends to transmit an unreceived parameter if not recorded,
A received object processing means for recording the parameter of the acquired message in a reception buffer corresponding to the reception object that is the object that has received the message and deleting the parameter from the transmission buffer corresponding to the reception object;
To compare the recorded contents of the transmission buffer and the recorded contents of the reception buffer for each object, and to function as a buffer comparison unit that records inconsistency that there is an unused parameter if they are not the same in the inconsistent recording unit program. A software operation is expressed by an object that is the subject of the operation, a message name indicating the content of the operation, and a parameter indicating information used for the operation, and messages arranged in time series between the objects. A method for detecting a mismatch between specifications / designs using a computer including at least a storage device and an arithmetic processing unit,
The computer processing unit is
A first step of acquiring messages from a specification / design document stored in a storage device in chronological order;
A second step of determining whether or not the parameters of the acquired message are recorded in a reception buffer corresponding to a transmission object that is an object that has transmitted the message;
A third step of recording the parameter in a transmission buffer corresponding to the transmission object if it is recorded as a result of the determination;
As a result of the determination, a fourth step of recording in a storage device a detection result of inconsistency indicating that the transmission object is trying to transmit an unreceived parameter if it is not recorded;
A fifth step of recording the parameters of the acquired message in a reception buffer corresponding to a reception object that is an object that has received the message;
A sixth step of deleting the parameters of the acquired message from the transmission buffer corresponding to the receiving object;
A seventh step of repeating the first to sixth steps until all the messages in the specification / design document are obtained;
An eighth step of comparing the recording contents of the transmission buffer and the recording contents of the reception buffer for each object;
And a ninth step of recording inconsistency in the storage device that there is an unused parameter if they are not identical as a result of the comparison, a software specification / design inconsistency detection method comprising: .

Images