JPH0752387B2 - Software development support device - Google Patents

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software development support device for efficiently developing software for system products using a computer.

2. Description of the Related Art A variety of system products using computers have been developed along with the development of computers, and software has been actively developed accordingly. Several software development support systems have also been proposed in order to efficiently develop this software. For example, the 50SM support system is shown in Toshiba Review Vol. 41, No. 8, pp. 672-676, and Proceedings of 31st National Convention of Information Processing Society of Japan, pages 492-493.

FIG. 5 shows a functional block diagram thereof.

In FCD editing / analysis 54, system design is performed using FCD diagrams that can simultaneously describe data flow and control flow. The FCD diagram is a description method peculiar to the conventional example and is represented by a combination of a rectangle, a parallelogram, a black-headed arrow, and a white-headed arrow. Using the FCD diagram, top-down function decomposition is performed based on required functions and constraints, and the whole system software is supported as a hierarchical structure of functional units, data flows, and control flows. In addition, it is possible to synthesize the information of the created FCD diagram, check the consistency, and create a report. The created FCD diagram is centrally managed and managed by the system design database 51.

In the TFF design document edit 55, a module design document (TFF sheet) can be created using TFF, which is a schematic representation of the program structure in the conventional example. In that case, other TFF sheets or the above-mentioned F
You can make it by referring to the CD diagram. The created TFF sheets are collectively managed by the module design database 52.
The TFF design test 56 can automatically generate a design review record table along the control path of the TFF sheet, and a person can view the record table to perform the coverage evaluation. The TFF code editing / code generation 57 allows coding of a program source corresponding to the TFF sheet while watching the TFF sheet. Therefore, the source code is partially automatically generated from the TFF design information. In addition, the source program is input, and the code review record table along the control path of the TFF code is output with the same function as the design review record table. The module unit test 58 assists in determining test data and expected output based on the input data and passing path information in the code review recording table. It also has a function to automatically generate a stub driver for unit testing. The source static analysis 59 has a function of analyzing the source code, omitting the description, and displaying grammatical errors. The module assembly 60 and assembly test 61 use the contents of the module design database 52 to support the integration test.

The module quality data 53 is used to save and manage the test execution results in the form of a test product report or a bug slip.
The document output 62 outputs the contents of the databases 51, 52, 53 to the printer.

Aiming to realize the above functions on high-end workstations and personal computers, some of them have been put to practical use to help improve the productivity of software development.

This conventional example uses a software development tool that has been used differently depending on the software development process until now. This is a typical example showing the future way of thinking of improving the efficiency of software development.

Problems to be Solved by the Invention However, this conventional example has the following problems.

During the software development work, the contents of the document created in the computer are not fully utilized for the downstream work, so the automation range of the work is narrow and the efficiency is low.

Since the search function of the created document contents is weak,
It is difficult to modify or divert documents.

Since the document format is fixed, it is difficult to deal with a wide range of system development contents.

Since the log data of stubs and drivers cannot be reused for debugging work when bugs are found, work efficiency is poor.

Since there is no debug function for the actual device using the in-circuit emulator (ICE), the environment for fixing bugs is weak.

SUMMARY OF THE INVENTION It is an object of the present invention to solve the above problems, expand the range of work automation, and provide a software development support system with excellent workability that can support a wide range of system development. .

Means for Solving the Problems In order to achieve the above object, the present invention provides a database for storing customized data, a database for storing documents created in each process of software development, a test process, and a debug process. It is equipped with a database that temporarily stores the data used for work and a database that stores the source code of the program. Using each database, design documents are created, documents are searched, program structure using graphics and source code Creation, mutual conversion of graphics and source code, debugging of source code using graphics, creation of test specifications and creation of test products.

Operation In the above configuration, the contents of the document created in the computer during the software development work are used for the creation of the contents of the downstream work, the range of automation is expanded, and the error caused by the carelessness of the worker is prevented. Also, by expressing the document contents in a relational database, it is possible to perform advanced searches and facilitate modification and diversion. Also, by providing the system with a customization function, the user can freely set the format of the document and deal with a wide range of system development contents. Further, the stub driver is automatically generated from the upstream document in the test process, and it can be used as it is for retesting and debugging work when a bug is found, thereby improving work efficiency.

Example FIG. 1 shows a functional block diagram of an example of a software development support device according to the present invention. FIG. 2 shows an example of system configuration as a software development support device. The data file is a document database 1 that collectively manages the documents created in each process of software development, a course code database 2 that exclusively manages the source code in the document database, and a user customized in advance 5
A customized database 3 that manages various formats used for design documents and the like, and the document format configured from the types of items in the format or the relationship between items, and holds temporary data It is composed of four types of log data 4. The customization 5 has a function of freely setting various formats used for design documents and the like, the types of items in the format, and the relationships between items. An example will be described with reference to FIG. Reference numeral 31 is a character string that has a meaning representing the name of the frame 32 in the system. 33 means a program name, 34 means a system name, and 35 means a subsystem name. in this case,
System name 34-subsystem name according to relational database
35-Define that there is a parent-child relationship for program name 33. Further, the function outline 36, the input format 37, and the output format 38 of the program can be associated with each other as the types of the description content of the program. In this way, the character string description area is defined as a format. It also defines graphics such as flowcharts and description areas such as tables. These format types and relationships are registered in the customized database 3 and used as a reference in the software development process. The design document creation 6 is an editor that creates a design document by taking out a customized document format from the customization database 3. The created design document is saved in the document database 1.

Further, the document search 7 can search the document by using the relational database. For example, a parent-child relationship between programs can be used to retrieve a list of programs having a parent-child relationship with a subsystem from a document database and display the list.

In the chart editor 8, it is possible to create a C language program by using a graphic called a structured chart, which is a graphic used in designing a program, such as an HCP diagram and a PAD diagram. The area in which the chart is described is defined by the customization 5 and stored in the customization database 3 as a document format, like the area in which the character string is described.
The relevant document format is taken out and described in the chart editor 8. For example, if you select a symbol from the menu on the display screen with the mouse to describe the symbol that means HCP diagram judgment,
In that column, if (), which is a C language meaning judgment, and
else is automatically generated. Also, if the processing contents are described in Japanese corresponding to the symbols, a schematic chart of the module design document can be created and managed in the document database 1.

The chart source conversion 9 has a function of converting the graphic program into C language source code in a format to be applied to a compiler. The relevant document format is extracted from the customized database 3 and the chart description area is extracted. The contents described in this area are converted to C language source code. Results are managed in both the document database 1 and the source code database 2. Further, since it also has a function of inversely converting a C language source code into a graphic program, it is possible to create a document from a past C language program. The source static analysis 10 has a function of analyzing C language source code and outputting it in a document collectively. The contents of the document include a list of parent-child relationships of modules, a list of function arguments, and a table of correspondence between files and functions.

The relevant document format is extracted from the customized database 3 and the description area is extracted. The generated contents are input to this area and the created document is stored in the document database 1.

Unlike the ordinary debugger, the chart debugger 11 can display, for example, the program structure around the breakpoint as a graphic. Therefore, it has an advantage that a bug can be easily found. In addition, the debugger with this graphic display can be realized by connecting it to the actual device via the ICE, improving the debugging efficiency.

Document database 1 for test specification creation 12
It has a function to create test specifications by referring to the design documents saved in. For example, data items for testing can be extracted from the data definition in the module. The relevant document format is extracted from the customized database 3 and the description area is extracted. The generated contents are input to this area and the created document is stored in the document database 1.

The stub driver generation 13 automatically generates a stub driver. A driver module and a stub module are required to test the module. A driver module is a module that is created to send a test case to a module to be tested or to operate on the test case. The stub module is not an actual module but a pseudo module created to operate the same function, and is for confirming the operation as if the relevant module was incorporated and tested. The stub / driver generation 13 generates this driver module and stub module, and creates a list of used functions and test cases from the test specifications.

Test run 14 after compile and link. The test report creation 16 is for generating the result obtained by the above test execution in a document. The relevant document format is taken out from the customized database 3 and the description area is extracted. The generated contents are input to this area and the created document is stored in the document database 1.

Another feature is that the data created by the test specification creation 12 and the stub driver generation 13 is saved as the log data 4 so that the test execution can be performed again and the chart debugger 11 can be used immediately when a bug occurs. In terms of availability, this saves a great deal of work compared to the prior art.

The details of the test / debug procedure will be described using a module test as an example. FIG. 4 shows a functional block diagram.

Module design documents already in the document database
71, module test specifications 73, and source code 72 are described. In the stub generation 75, the stub input value 74 is input by the operator, and the system automatically generates the stub 77 using the contents of the function used list in the module design document 71, the source code 72, and the module test specification 73. In the driver generation 76, the driver 78 is generated using the in-module data definition in the module design document 71, the source code 72, and the module test specification 73.

Since the test result is predicted in advance in the module test specification 73 according to the test condition, the result judgment data 79 can be created by extracting it. The input data 80 is created by extracting the module test specifications 73 and combining the test data 81 manually input by the operator.

The stub 77, the driver 78, the result judgment data 79, and the input data 80 created by the above procedure are input to the test execution 82, and the test is executed. The result of the test is predicted by the result judgment data 79, and it is possible to automatically judge whether or not the test is correctly executed. The result is automatically recorded in the module test product document 83.

In this way, the module design document created in the upstream process
By using 71, the module test specification 73, and the source code 72 for automation, the labor of the test work is made more efficient than before, and the risk of human error is eliminated.

In addition, the debugging work 85 was an independent work in the past, but in reality, the stub, driver, and input data are indispensable, so put the stub 77, driver 78, and input data 80 created in the test process in the log data, Reuse. This greatly improves the efficiency of the debugging task 85.

Returning to FIG. 2, the customization 5 shown in FIG. 1 is the CRT22.
While using the keyboard 23 and the mouse 26, the results are stored in the document database in the hard disk 24. Design document creation 6, document search 7, chart editor 8, chart / source code conversion 9, source static analysis 10, test specification creation 12, stub
The functions of driver generation 13 and test product documentation creation 16 are also CRT22
Is displayed on the screen and is operated by using the keyboard 23 and the mouse 26. The created document is a hard disk 24
Stored in. Log data during test / debug 4
Is also created on the hard disk 24 and used. The chart debugger 11 is used by connecting it to the actual machine via the insert kit emulator 27. In that case, the information is displayed on the CRT 22 and the information is input by the keyboard 23 and the mouse 26.
Done in.

The document output 15 is performed using the printer 25. As for the type of printer, any of dot printer, line printer, XY plotter, etc. can be used.

As described above, in the present embodiment, based on the customized document format, the document is created using the dedicated editor, the source is created from the created document, and various documents are created using the test execution means. However, the efficiency is realized from the upstream to the downstream of the software development process. In particular, the customization function can handle a wide range of software development. Further, by expressing the document contents in the relational database, it becomes easy to correct or divert the document, and the work becomes efficient.

In addition, the environment for testing and debugging work is greatly improved compared to the conventional example, which can contribute to the improvement of software quality. The program structure diagram that combines graphic expressions, the creation of source code, and conversely the creation of graphic information from source code are also improvements. It is also an advantage that existing development tools in UNIX environment can be used by making the source code database independent.

Effects of the Invention As described above, the software development support device according to the present invention has the following effects.

Since the contents of the document created in the computer can be used for the downstream work during the software development work, the range of automation of the work can be expanded and the software development work can be made efficient.

The contents of documents such as created design documents can be searched using the relational database, and it is easy to deal with the correction of documents and the diversion to other systems.

A high-quality program can be created because it is possible to create a program structure diagram that uses graphics such as HCP diagrams and PAD diagrams, and C language source code can be created step by step, and a document that expresses graphics from C language source code. Can be inversely generated.

With the customization function, the document format can be freely created and a wide range of system development contents can be dealt with.

Log data such as stub / driver test data generated during test work can be reused in the test process and debugging work when a bug is found, and work efficiency is improved.

The actual device debugging using the in-circuit emulator (ICE) can be performed by the graphic representation such as PAD diagram and HCP diagram, and it is possible to deal efficiently when a bug is found.

By making the source code database independent, it can be used as a starting point for using other software development tools built in UNIX etc.

[Brief description of drawings]

FIG. 1 is a functional block diagram of a software development supporting apparatus according to the present invention, FIG. 2 is a block diagram showing a system configuration example of the software development supporting apparatus according to the present invention, and FIG. 3 is an important function of the present invention. FIG. 4 is a diagram for explaining customization and document retrieval, FIG. 4 is a diagram for explaining a test process of software development according to the present invention, and a function for supporting debug work, and FIG. 5 is a conventional software development support device. It is a functional block diagram. 1 ... Document database, 2 ... Source code database, 3 ... Customized database, 5 ...
... Customization, 6 ... Design document creation, 7 ... Document search, 8 ... Chart editor, 9 ... Chart
Source code conversion, 11 …… Chart debugger, 12 …… Test specification writing, 16 …… Test product writing.

Claims (7)

[Claims] 1. A customizing means for defining various formats used for design documents or the like in computer software development, and a kind of items in the format or a relationship between items as a document format, and the customization. A first database for storing data customized by means, a second database for storing documents created in each step of software development according to a document format stored in the database, and a first database Design document creating means for creating a design document using the created document format and the data stored in the second database and storing the design document in the second database, and the types of items in the format stored in the first database Or a second database based on the relationship between items Means for retrieving the contents of the document from the above, and a program structure and source code using graphics in the area describing the chart defined as the format in the document format stored in the first database, and the second database The program structure and the source code using the chart editor stored in the second database and the graphics stored in the second database are searched by referring to the first database, and the graphics and the source code are converted to C language source code. Conversion means, a third database for holding the source code of the program converted by the mutual conversion means, a fourth database for temporarily storing data used for the test process and debugging work, and a third database State of source code stored in Create test specifications and test reports by referring to the chart debugger that displays charts, the document format stored in the first database, and the design documents saved in the second database created based on the document format. A software development support device, comprising: 2. The contents of a customized database are expressed by a relational database, and the contents of a document already created using this relational database are searched by a keyword. The described software development support device. 3. A test specification is automatically generated by using the contents of the design document in the document database, a stub driver is automatically generated, and a test product document is automatically generated from the result of executing the test. The software development support device according to claim 1. 4. The software development support apparatus according to claim 1, wherein the data created in the test specification creation and the stub driver creation is used as it is for the debugging work when a bug occurs. . 5. A source code database is provided separately from a document database, so that the source code database serves as a cut-off point for use in other software development support tools. The software development support device described in the item. 6. A chart editor has a function of creating a schematic chart showing the structure of a program and a C based on the definition of a graphic.
The software development support apparatus according to claim 1, which has at least a function of automatically generating a language source and a function of decoding an existing C language source to automatically generate a figure. 7. The software development support device according to claim 1, wherein the chart debug can operate by connecting to an actual machine via an in-circuit emulator.