JP2015138356A - Software structure visualization device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software structure visualization device that visualizes a connection between components to allow them to be easily understood even when it is software in which each component exchanges data via a particular component that handles common data.SOLUTION: A software structure visualization device of the present invention includes: a syntax analysis unit for analyzing syntax of software; a software structure recognition unit for recognizing structure of the software based on an analysis result of the syntax analyzed by the syntax analysis unit; an I/F associating unit for associating the structure recognized by the software structure recognition unit with a plurality of I/Fs used in the syntax based on a naming convention of the software; a structure conversion unit for converting the syntax by replacing the plurality of I/Fs associated by the I/F associating unit with one I/F; and a structure information presentation unit for presenting information on the syntax converted by the structure conversion unit.

Description

    The present invention relates to a software structure visualization apparatus.

  2. Description of the Related Art Conventionally, there is a source code analysis device that analyzes a source code and creates an inter-module call relation diagram expressed in module units set from a function call relationship and a function and module inclusion relationship (for example, see Patent Document 1). reference).

  In addition, there is document generation means that parses the source code of an input program according to a standard specification and generates structure information of the program reconstructed from the analysis result as a document (see, for example, Patent Document 2).

  Further, there is a syntax analysis unit that analyzes source code and outputs syntax information (see, for example, Patent Document 3).

JP 2008-293486 A JP 2009-080681 A JP2013-156786A

  However, in the above-mentioned prior art, when visualizing the structure of software that exchanges data via specific components that handle common data, a structure diagram is created in which each component is connected to a specific component. There was a case where it was done.

  Accordingly, the present invention provides a software structure visualization device that makes it easy to understand the connection between components even when the components exchange data via specific components that handle common data. With the goal.

  The software structure visualization device according to the present invention includes a syntax analysis unit that analyzes software syntax, a software structure recognition unit that recognizes the structure of the software based on an analysis result of the syntax analyzed by the syntax analysis unit, An I / F association unit that associates a plurality of I / Fs used in the structure based on the software naming recognition unit and the structure recognized by the software structure recognition unit, and a plurality of associations by the I / F association unit A structure conversion unit that converts the structure by replacing the I / F with one I / F, and a structure information presentation unit that presents information on the structure converted by the structure conversion unit.

  According to the embodiment of the present invention, there is provided a software structure visualization device that makes it easy to understand the connection between components even when the components exchange data via specific components that handle common data. Can be provided.

Block diagram showing an example of the configuration of a software structure visualization device Flow chart showing an example of the operation of the software structure visualization device Diagram showing an example of the relationship between components on the source code Diagram showing an example of data exchange between components on source code The figure which shows an example which directly converted the transmission / reception of the data on a source code into I / F Diagram showing an example of the relationship between the components shown

  Hereinafter, an embodiment which is an example of the present invention will be described with reference to the drawings.

  First, the configuration and operation of the software structure visualization apparatus will be described with reference to FIGS. 1 and 2. FIG. 1 is a block diagram illustrating an example of the configuration of the software structure visualization apparatus. FIG. 2 is a flowchart showing an example of the operation of the software structure visualization apparatus described in FIG.

  In FIG. 1, the software structure visualization device 1 includes functions of a syntax analysis unit 11, a software structure recognition unit 12, an I / F (Interface) association unit 13, a structure conversion unit 14, and a structure information presentation unit 15. Each function of the software structure visualization device 1 performs an operation in each step (S1 to S5) in FIG.

  The syntax analysis unit 11 analyzes the syntax of the input source code (S1). In the analysis of the syntax of the source code, for example, a description specifying a software component is extracted from the source code. A component is a unit of software, and is, for example, a folder, a source file, a function, or a collection of them. The component recognized in the present embodiment is a software component unit that exchanges data with other components by referring to variables, calling functions, and the like. The syntax analysis unit 11 outputs the analysis result of the component recognized from the description of the source code to the software structure recognition unit 12.

  The software structure recognition unit 12 recognizes the software structure from the analysis result of the source code input from the syntax analysis unit 11 (S2). Recognizing the structure of software means recognizing a connection between a component and other components through data exchange. The software structure recognition unit 12 recognizes an I / F for exchanging data between one component and another component, for example. The software structure recognition unit 12 outputs the recognition result as software structure information to the I / F association unit 13 and the structure conversion unit 14.

  The I / F associating unit 13 analyzes the I / F described in the software structure information input from the software structure recognizing unit 12 and determines a plurality of I / Fs that exchange data via the same data storage component. Associate (S3).

  The I / F analysis refers to, for example, a naming rule that defines function calls and variable references. As a naming rule, for example, there is AUTOSAR RTE (Automotive Open System Architecture Runtime Environment) which is an international standard of an in-vehicle software platform. The AUTOSAR RTE provides common board software (Basic Software: BSW) to applications running on the AUTOSAR RTE by a standardized naming convention. The AUTOSAR RTE can provide a software environment that does not depend on hardware, and thus enables common software development and software reuse in a plurality of ECUs. The I / F association unit 13 refers to the naming rule and outputs the I / F related by the naming rule described in the software structure information to the structure conversion unit 14 as a set of related I / Fs. As an alternative to the instruction rule, an I / F name or information related to an I / F may be used. These are provided, for example, by configuration information that defines the I / F in the software platform. The configuration information may be described and provided in, for example, XML (Extensible Markup Language).

  Here, the data storage component will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of a relationship between components on the source code.

  In FIG. 3, the component A 101, the component B 102, the component C 103, and the component D 104 use the data storage component 100 as a common data storage. The components A 101 to D 104 communicate with the data storage component 100 through an I / F that follows a naming convention for exchanging data. The I / F is, for example, a function call or a variable reference.

  For example, when data is transmitted from the component A 101 to the component B 102, the AUTOSAR RTE provides a protocol that passes through the data storage component 100 in order to simplify the exchange of data across ECUs (Electronic Control Units). That is, the component A 101 once writes the data to be transmitted to the data storage component 100 using the write function. The component B102 reads the data written in the data storage component 100 by a read function. As a result, even when the component A 101 and the component B 102 are created by different software vendors, for example, data can be exchanged by using a common I / F.

  The source code describes an I / F between components that exchange data. In the above example, the component A 101 is connected to the data storage component 100 by a write function, and the component B 102 is connected to the data storage component 100 by a read function. Therefore, in the conventional technique for visualizing the software structure as it is from the I / F described in the source code, the component A101 to the component D104 are connected to the data storage component 100 as shown in FIG. The exchange between the components D104 is not visualized. 3 is a structure diagram depending on a software platform such as a data storage component.

  1 and 2 again, the I / F association unit 13 analyzes the write function and the read function, which are I / Fs described in the software structure information, and exchanges data via the same data storage component. The above two functions are associated with each other as an I / F to be performed.

  Next, the structure converting unit 14 converts the software structure information input from the software structure recognizing unit 12 according to the set of associated I / Fs input from the I / F associating unit 13 (S4). ). The structure converting unit 14 replaces a plurality of associated I / Fs with one I / F with which a software component that exchanges data directly communicates, and converts software structure information. The structure conversion unit 14 outputs the converted software structure information to the structure information presentation unit 15.

  Here, details of the conversion of the software structure information will be described with reference to FIGS. FIG. 4 is a diagram illustrating an example of data exchange on the source code between the components described in FIG. FIG. 5 is a diagram illustrating an example of the relationship between components on the source code described with reference to FIG. 3, in which data exchange on the source code is directly converted into an I / F.

  In FIG. 4, the component A 101 writes the data α to the data storage component 100 using the function IF (X) defined by the instruction rule as the I / F. The function IF (X) is described as “Rte_Write_Port1_α ()”, for example. “Rte_Write_Port1_α ()” is a function that writes data α as an argument to the data storage 1001 (Port1).

  On the other hand, the component B 102 reads the data α from the data storage component 100 using the function IF (Y) defined by the instruction rule as the I / F. The function IF (Y) is described as “Rte_Read_Port1_α ()”, for example. “Rte_Read_Port1_α ()” is a function that reads data α as an argument from the data storage 1001 (Port1). The two functions IF (X) and IF (Y) are related by the I / F associating unit 13 because they define the exchange of data via the data storage 1001 (Port 1).

  In FIG. 5, the relationship between the component A 101 and the component B 102 is based on the data storage location 1001 and the relationship using the function IF (X) and the function IF (Y) that are two functions associated by the I / F association unit 13. , The relationship is converted into a relationship using the function IF (Z) which is one replaced function. That is, the structure conversion unit 14 converts the software structure into a structure in which the component A 101 and the component B 102 directly exchange data using the function IF (Z).

  Referring back to FIGS. 1 and 2 again, the structure information presentation unit 15 obtains a DSM (Dependency Structure Matrix) and a software structure diagram from the software structure information that is the structure information of the software after conversion input from the structure conversion unit 14. The software component and the I / F between the software components are illustrated (S5).

  The DSM is a matrix that shows the dependency between software components. For example, the dependency relationship between the component A 101 to the component D 104 can be visualized by the DSM. By visualizing the dependencies between software components, the software designer can easily understand and maintain the structure of the software components.

  Next, details of the software structure diagram will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of a relationship between components illustrated by the structure information presentation unit 15.

  FIG. 6 illustrates that the component A 101 and the component C 103 exchange data directly only with the component B 102. The component D104 directly exchanges data with only the component B102. The software structure diagram illustrated in FIG. 6 is a software structure diagram in which components for data storage are omitted, and thus is a structure diagram that does not depend on the software platform. Therefore, it is possible to visualize the data exchange between the components considered when the software designer designs the software. The software designer can easily understand and maintain the structure of the component by using the visualized software structure diagram.

  The software structure diagram can be displayed on a display device such as a liquid crystal display (not shown). Further, it can be printed on a printing device (not shown) and illustrated.

  Note that one or more functions of the syntax analysis unit 11, the software structure recognition unit 12, the I / F association unit 13, the structure conversion unit 14, and the structure information presentation unit 15 of the software structure visualization device 1 are not illustrated, for example. It can be realized by a program stored in a storage unit of a computer and executed by a CPU. Further, one or more functions of the software structure visualization device 1 can be realized by hardware or middleware.

  As mentioned above, although the form for implementing this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, Various modifications and changes are possible.

DESCRIPTION OF SYMBOLS 1 Software structure visualization apparatus 11 Syntax analysis part 12 Software structure recognition part 13 I / F correlation part 14 Structure conversion part 15 Structure information presentation part 100 Data storage component 101 Component A
102 Component B
103 Component C
104 Component D
1001 Data storage

Claims (1)

A parser that analyzes the syntax of the software;
A software structure recognition unit for recognizing the structure of the software based on the analysis result of the syntax analyzed by the syntax analysis unit;
An I / F association unit that associates the structure recognized by the software structure recognition unit with a plurality of I / Fs used in the structure based on a naming rule of the software;
A structure conversion unit that converts the structure by replacing a plurality of I / Fs associated by the I / F association unit with one I / F;
A software structure visualization device comprising: a structure information presentation unit that presents information on the structure converted by the structure conversion unit.

Images