JPS63219036A - Software development support system - Google Patents

Abstract

PURPOSE:To automatically process a software by isolating an operation such as an input, an output or an operation, etc., for a 'matter', and making them into one of parts as a unit, and preventing one processing from influencing many modules. CONSTITUTION:In a step 1, the data flow chart of a system is formed. Next, in the step 2, input/output processings are grouped, while the objective 'matter' (input key, printer, displayer, file, etc.) being considered as a center. In the step 3, the processings for one 'matter', related to plural places, are made into a lump. In the step 4, the processing for the 'matter' is detailed. In the step 5, the respective processing is registered in the file as the part for the 'matter'. In the step 6, as considering the flow of the processing, the part is selected, and a processing program is formed. Thus, the automatic processing, different from a customary one fundamentally, can be realized.

Description

[Detailed Description of the Invention] [Industrial Field of Application] The present invention relates to a software development support system, and particularly to componentization of software with a focus on "R" products.

The present invention relates to a software development support method effective for managing, using, etc. software components.

[Conventional technology] Conventionally, when developing software, external specifications 1
Programs were constructed using functional specifications and coding.

Generally, software is thought of as having a focus on functionality.
The handling of the software components that make up the system and the functional steps that make up the source code of the software components are handled manually. .

[Problem that the invention seeks to solve]

In the above-mentioned conventional technology, when developing software, the number of modules and the way of writing the design document vary depending on the designer, and when maintaining the completed program, the source program is analyzed and corrected. There was a problem in that this method required a lot of labor.

In addition, since software component management was performed in units of functional steps in the source code, when changing data attributes within a software component, it was necessary to search for related software components based on the software component specifications.
There were problems in that software production was delayed due to omissions in searches, and as the number of software components increased, management became complicated and oversights occurred.

The present invention has been made in view of the above circumstances, and its first purpose is to solve the above-mentioned problems in conventional software development support systems, to componentize program structure and processing, and to improve maintainability of software. The objective is to provide a software development support method that is possible.

A second object of the present invention is to systematically manage the usage information of componentized software, centering on the data that constitutes the software.

The object of the present invention is to provide a software development support method that automatically manages a database file that stores software components.

[Means for solving problems]

The first object of the present invention is to create a data flow diagram that expresses input and output processing for "things" by focusing on "things" when developing a software system; This is achieved by converting the process into software components.

The second object of the present invention is to create history information of software components and history information and attribute information of data constituting software components from software component usage information in a database file storing software components; This is achieved by linking the software components as management information.

[Effect]

In the present invention, first, input, output, calculation, and other operations for "things" are made independent, and these are made into components as units, so that one process does not affect many modules.

As a result, the independence of the modules is increased, and the parts to be modified or changed can be localized, so that the maintainability of the program can be improved.

Furthermore, in the present invention, history information of software components and history information and attribute information of data constituting the software components are created and linked from software component usage information in a database file that stores software components. This information is stored in a database file as management information for a database file in which software components are stored, and the management information is searched by following the above link and reported to the user who is attempting to obtain the information.

〔Example〕

Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a one-step flowchart showing an example of a software development support method that can componentize program structure and processing and improve software maintainability, which is the first objective of the present invention. It is.

First, in step 1, a data flow diagram for software six-engine system development is created. This data flow diagram is a very common document created during program development.

In other words, a data flow diagram shows the flow of data in a software system.
What kind of data is input data (or generated internally) transformed into by processing?

This indicates whether the data is passed to the next process, stored in a file, or output to an output device such as a printer.

FIG. 2 shows a data flow diagram of a store system as an example. The processing functions are divided into sales management, accounting management, and single item management, and data flows between them as shown by arrows. The meanings of the symbols used in the figure are shown at the bottom left of the figure.

Figure 3 shows a part of the sales management described above in more detail. This figure shows a part of product registration during sales operation processing in sales management. In other words, "10" key + "department" key when selling products to customers, or rlO
This shows the part where the preset product name and price are searched and displayed by pressing the J key + "Product number" key.

In step 2 of FIG. 1, processes for "things" such as data, files, external devices, etc. are extracted from the data flow diagram. What is expressed as "r things" in FIG. 3 is the "10" mentioned above. key, "department" key.

These include the keyboard on the terminal such as the "product number" key, data work areas such as numerical stack tables and product stack buffers, external files such as department files and product number files, and output devices such as displays and printers. Also, as a process for the above-mentioned "things".

Input, check, set, search 1 display, output, etc. are shown.

In FIG. 3, the area bounded by large curves such as broken lines and dashed-dotted lines indicates processing for one "r item". The numerical stack table shown in the area surrounded by the dashed line, the product stack buffer shown in the area surrounded by the dashed-dotted line, and the 10 shown in the area surrounded by the dashed-double line.
The key, the display device, and the printer shown in the area surrounded by solid lines appear on the data flow diagram both when the department key is pressed and when the product number key is pressed.

The step 3 in FIG. 1, in which processes for one "thing" related to multiple locations are summarized, indicates that a plurality of processes for the same "thing" appear on the data flow diagram. Figure 4 shows these all together.

In FIG. 4, "r items" (a) to (f) are objects to be processed that appear on the data flow diagram of FIG. For example, the processing of the numerical stack table in (a) is set, input, and check processing, and the check items include checking the number of digits and checking the maximum value. For input processing and set processing of other files and buffers, use their format.

Since the processing may differ depending on the difference in items, etc., if the parts are managed so that they can be changed, the parts become highly maintainable.

FIG. 5 is a representation of the process for the above-mentioned "thing" in a different format, and shows the situation in which the process becomes more detailed. The meaning of the diagram is shown in the upper right corner of the diagram. Step 4 in FIG. 1 is detailed as shown in FIG. Note that the thick-lined and diagonally shaded portions in FIG. 5 indicate the processing used when the department key and product number key shown in the data flow diagram of FIG. 3 are pressed.

FIG. 6 shows the above processes arranged in the order of execution. That is, by creating a processing component for the "r item" shown in FIG. 5, registering it in a file, and selecting the necessary processing at the time of execution, the task can be accomplished. This is step 5 and step 6 in FIG.

According to the above embodiment, when developing a software system, a program can be managed as a collection of small parts, and thereby a system can be constructed by combining parts.

FIG. 7 shows the second object of the invention mentioned above. This figure shows a block configuration of a computer system, which is an embodiment of a software development support method that automatically manages a database file that stores software components.

In the figure, reference numeral 11 indicates an interactive display terminal device, 12 a computer processing device, 20 an accumulation database file of software components, and 21 an accumulation database file of management information of software components.

Inside the computer processing device 12 described above, there is a software component usage information input reception unit 14 that receives information using the software component storage database file 20. a software component management information creation unit 15 that analyzes the input information and creates management information for a database file in which software components are stored; an accumulation unit 16 that stores the management information in the storage database file 11 for software component management information; A search information input reception unit 17 that receives information for searching the accumulated database file 21 of software component management information inputted from an interactive display terminal; analyzes the information and searches the accumulated database file 21 of software component management information. Management information search unit 18 to search
．． There is a search result output unit 19 that outputs the search results to the interactive display terminal device 11.

FIG. 8 is a processing flowchart of FIG. 7, and FIG.
FIG. 13 shows information given to and obtained from the processing flowchart of FIG. 8.

In this embodiment, the management control unit 13 shown in FIG.
First, the process determination in step 31 of FIG. 8 is a management information creation process, and the usage information of the software component storage database file 20 is accepted by the software component usage information input reception unit 14, and the information shown in FIG. input.

When configuring the system vl of SYSTEM 1, the input information shown in FIG. 9 is input from the software component accumulation database file 20 shown in FIG. G, using BUHIN 3 (7) Vl,
BUHIN 1 (7) VH,: is vl of DATA 1
and DATA 2 vO data are used, and BUH
IN 2 (7) Vl D is DATA217) VO to D
ATA21(7)Vl.

DATA2217) Vl data is used, B
VH, - of UHIN3 is DATA 1 +7) Vl and D
ATA31(7)V2. The data DATA32 (7) V2 is used, and the Vl (7) attribute of DATA 1 is BIT (8), DATA 2 (7
) VO (7) attributes are BIT (16), DATA21 no V
The attribute of 1 and the Vl(7) attribute of DATA22 are BIN(1
6), DATA31 (7) V2 (7) attributes and DATA3
The attribute of 2(7)V2 indicates that it is DEC(5).

This input information is used by the software component management information creation unit 15 shown in FIG. 7 to create the software component history information 22 shown in FIG. unit, and in the data history information creation process of step 39 shown in FIG.
The history information 23 of the data constituting the software component shown in the figure is created for each part name, and step 4 shown in FIG.
In the data attribute information creation process of step 0, the attribute information 24 of the data constituting the software component shown in FIG. 10 is created for each data name, and in the link information creation process of step 41 shown in FIG. link information 25 between the history information 22 of the software component shown in FIG. 24 and the link information 26 with the existing management information shown in step 42 shown in FIG. Select the management information 27 of, or
If it does not exist, a new one is created, link information 28 is created with the history information 22 of the software component, and all of this is stored as software component management information by the management information storage unit 16 shown in FIG. 7, as shown in FIG. The information storage process in step 43 shown in FIG.

Furthermore, when the management control unit 13 shown in FIG. 7 sets the determination process in step 31 shown in FIG. As information for searching the database file 21, the search information input receiving unit 17 inputs the information shown in FIG. 12 in the input information receiving process of step 32 shown in FIG.

The input information shown in FIG. 12 is used when configuring a system called SYSTEM 1 v3.
It is shown that this can be done by changing the data attribute DATA 1 of the existing system. This input information is
The management information search unit 18 shown in FIG. 7 uses the input information analysis process in step 33 and the link information search process in step 34 shown in FIG. From, the 11th
Management information for the software components shown in the figure is selected to be stored in a database file, and SYS
From the link start position of the existing system called v2 of TEM 1, select the link information 28 with the history information 22 of the software component, select the history information 22 of the software component,
Selection of link information 25 between the history information 22 of the software component shown in FIG. 10 and the history information 23 of the data configuring the software component, selection of the history information 23 of the data configuring the software component, By selecting the link information 26 between the history information 23 and the attribute information 24 of the data configuring the software component, and selecting the attribute information 24 of the data configuring the software component, the names of the software components configuring v2 of SYSTEM 1, Obtain the name and attribute information of the data that constitutes the software component.

Note that the management information search unit 18 shown in FIG. 7 searches the attribute information of the data constituting the software component in FIG. 10 indicated by the data name DATA 1 to be changed by the management information search process in step 35 shown in FIG. 24, the history information 2 of the data that constitutes the software component is used as the search start position.
By tracing the link information 26 with 3, in the history information 23 of the data composing the software component, the data name DATA 1 to be changed is changed to the software component names BUHIN 1 (Vl) and BUHIN3 (Vl).
It turns out that it is used for.

This information is outputted by the search result output unit 19 shown in FIG. 7 to the dialog display terminal device 11 through the result output process of step 36 shown in FIG. Figure 13 shows the SYSTEM
1 (7) V3 and SYSTEM 1 V2 (71DA
When configuring the system by changing the data attribute TA1, the software component names are changed to 8INI and BINI.
3 indicates that the data DATA 1 is being used, and indicates that the changed locations are in BUHIN 1 and BUHIN3.

According to the above embodiment, the information management is automatically performed each time the stored database file of the software component shown in FIG. 7 is used, so that there is no omission in management. Furthermore, by searching for information in the database file that stores management information for software components, it is possible to quickly find out where to modify the software components, thereby making it possible to efficiently develop software.

Next, an automatic program synthesis system will be described as another embodiment of the software development support system of the present invention.

FIG. 14 shows the block configuration of the computer system of this embodiment. In the figure, 51 is a display terminal device for interaction, 52 is a computer processing device, and 59 is a program component database. Inside the computer processing device 52, there is a program automatic synthesis control section 53 that controls the entire synthesis system. An input data reception unit 54 that receives data from the interaction display terminal bag @51 as input data.
．． Temporary input data storage file 60 that retains received data only while the system is operating. An input data analysis unit 55 that converts input data into a form that can be processed later. Input data analysis result volume temporary file 61 that holds analysis results only during system operation. A program component execution control unit synthesis unit 56 that synthesizes a program component execution control unit based on input data analysis results. A program component database search unit 57 that searches the program component database based on input data analysis results. The program component execution control unit synthesis unit 56
and a program synthesis section 589 that arranges the program source code obtained by the program component database search section 57 and synthesizes the program.A program source code accumulation file 62 that accumulates the synthesized program source code.
exists.

FIG. 15 is a processing flowchart of FIG.
Figures 6 to 20 show POS (Point of 5al
es) is an explanatory diagram exemplifying the composition of terminal programs.

In this embodiment, the operation procedure of the data input device shown in FIG. 16 is as follows:
The information is input through the processes of data input completion determination, data reception, and input data accumulation (steps 71, 72, and 73) shown in FIG. The input data shown in FIG. 17 is centered around the Q mark and the Δ mark. (1) The solid line on the right side including the center indicates the flow of control in the downward direction.

(2) The solid line on the left shows the upward flow of control.

(3) The 0 mark indicates operation of the data input device.

(4) The characters inside the mouth seal indicate the name of the program component.

(5) Intersections between solid lines and intersections between solid lines and 0 marks are automatically added as intersection numbers in the order of data input.

Based on this rule, the input data is stored in the input data storage temporary file 60 shown in FIG.

FIG. 18 shows input data analysis completion determination in step 74, input data re-input in step 75, program component name analysis in step 76, and step 7 shown in FIG.
Through the program part connection analysis in step 7 and the analysis result accumulation in step 78, for each intersection number of the input data in FIG. 17, (1) What kind of relationship does the corresponding intersection number have with any other intersection number (2) At the corresponding intersection number, which program part is executed and which other intersection number is the next process? (3) When the process ends is the RETURN POINT, BRANCH
I POINT.

GATHERPOINT, FINAL, FROM, To, AFT
This is the keyword ER (after . . . ) and the analysis result data converted into program component names, and is output to the input data analysis result storage temporary file 61 in FIG.

FIG. 19 shows the control part synthesis completion determination in step 79, the analysis data input in step 80, the loop determination in step 81, the loop statement creation in step 82, the jumping operation determination in step 83, and the step 84 shown in FIG. Through the processes of immediately execution statement creation, conditional execution statement creation in step 85, and control part statement storage in step 86, the data input order shown in FIG. 18 is made to correspond to the label name of the PL/M program, and the
For the keywords in the figure, the RETURN statement is converted to the 0070 statement of the PL/M program source code. However, if the next keyword after the corresponding keyword is a program part, the I
Converted to conditional 0070 statement by F-THEN, BRA
NC) II statement is the IF of the PL/M program source code.
-Convert to THEN statement. However, if the next keyword after the keyword is a program part name, convert it to 0070 statement. Also, convert GATHER statement to a space statement, which is only the label of the PL/M program source code, program part name. is the CALL of the PL/M program source code.
This is the program component execution control unit PL/M source code that was converted into statements by determining the following intersection numbers of FROM, To, and AFTER statements, and is stored in the program source code accumulation file 62 in FIG. Output.

FIG. 20 shows parts search completion determination in step 87, analysis data input in step 88, and step 89 shown in FIG.
Through the component database search in step 90 and the component source code accumulation process in step 90, the program component execution control unit PL/M source code shown in FIG. 19 is allocated to the program component execution control unit, and the program component source code selected from the program component database is This is a PO8 terminal program obtained by distributing the following to the processing unit.

According to the above embodiment, a program is automatically synthesized from the operating procedure of a data input device in a terminal device, and a target program can be easily and quickly obtained.

Next, automatic generation of a program execution control table will be described as another embodiment of the software development support system of the present invention.

FIG. 21 is a functional block diagram of this embodiment. In the figure, 101 is a keyboard for inputting data;
2 is a part that takes in the data; 103 is a processing part that analyzes the syntax of the taken data and decomposes the business type and pressed keys; 104 sets key sequence/flow information from the decomposed data into a file 105; processing unit 106
108.109 is a processing unit that similarly sets matrix information in the file 107; 108.109 is a unit that extracts information from files 105.107 and displays an operation flow diagram and matrix table on the display screen 110;
Reference numeral 1 designates a processing unit that generates a source list of a procedure control table from information in files 105 and 107 and outputs it to a printer or the like 112.

FIG. 22 is a processing flowchart of FIG. 21.

In step 113, data from the keyboard 101 is accepted, and in step 114, the data is analyzed and decomposed.

The format of the data input here is shown in FIG.

(a) to (c) in FIG. 23(A) represent key sequences to be pressed for different jobs. For example, (a)
In Gl (task 1), the key A is pressed, and B, C, or D is selected and pressed first. The Δ (space) after D indicates that it may be omitted, ie 6.

This indicates that after A, there is a possibility of moving to the next one from B, C, or D, or without pressing anything. Similarly, the following shows whether E is pressed or nothing is pressed, indicating that the primary F and G are always pressed.

This is expressed as an operation flow in Figure 23C.
It will be like (a) in B). Now, (a) in Figure 23 (A)
) to (c) are input, the key information (operation flow diagram) for all tasks (Gl, G2.G3) in step 115 shown in FIG. 22 is as shown in FIG. 23 (
It will look like (d) in B). This is a chronological arrangement of keys that may be pressed for multiple tasks.

Therefore, in the syntax analysis and key-by-key decomposition in step 114 shown in FIG. It is a delimiter. The above-mentioned 'Δ (space)' indicates that the key may not be pressed in that status.

In step 116, pressed key information for each job is created and the information is saved in a file. The pressed keys for each task are decomposed from the input data ((a) to (C) in FIG. 23(A)) as shown in FIG. 24(A). This is a list of keys that are pressed for each job (Gl, G2, G3) arranged in a pressed category. rB, C, D in status 2 in the same figure,
Δ'' indicates that B, C, or D is selected or can be omitted.

Figure 24 (B) shows this with business on the horizontal axis.

The vertical axis represents the type of key that is pressed, and is arranged to show the conditions under which the key is pressed. In the table, a 0 mark indicates a key that can be selected or omitted, an O mark indicates a key that must be pressed, and a * mark indicates that any of the consecutive keys is selected and pressed.

Therefore, the diagram (table) output and displayed in steps 117 and 118 shown in FIG. 22 is either the operation flow diagram (d) in FIG.
This becomes the key/business matrix table of B).

In step 119, a procedure control table is automatically generated from the saved information. The procedure control table is a table that manages key sequences that are pressed for each job, and controls the process up to calling the processing program that corresponds to the pressed key.

FIG. 25 shows the link relationship of the table. The status management table 120 manages the type of job currently being executed and the status in which the job is being executed.When the operator selects a job, the status management table 120 manages the job type that is currently being executed and the status of the job being executed. table 12
Linked to 1.

The execution status field of the status management table 120 is an area for setting which status of the selected task is currently being executed, and the status advances each time a key is pressed. The execution status link is the status table 1 linked from the business type table 121.
This indicates which status number of 22 is currently being executed. The status table is linked to that status number. A process is selected from a table 123 listing keys that may be pressed, and the program is executed by linking with the actual program group 124.

According to the above embodiment, an execution control procedure table can be automatically generated by inputting a business procedure key sequence in a simple data format. Therefore, it is possible to improve the efficiency of program development, automatically create a highly reliable and maintainable program, and the diagrams and tables created at this time can also be used as program specifications.

〔Effect of the invention〕

As described above, according to one aspect of the present invention, when developing a software system, a data flow diagram is created that expresses the input and output processing for the "r thing", with the "r thing" as the center. The idea of converting the processing into software components.

Based on the idea of creating software component history information and the history information and attribute information of the data that makes up the software component from software component usage information in a database file that stores software components, and linking them to create software management information. This has the remarkable effect of making it possible to realize automatic processing, which is fundamentally different from conventional methods.

[Brief explanation of the drawing]

FIG. 11 is a processing flowchart of program componentization which is an embodiment of the present invention, FIG. 2 is a schematic data flow diagram as a specific example thereof, FIG. 3 is a data flow diagram showing further details, and FIG. 4 Figure 5 showing the processing for ``A r thing''.
6 is a diagram illustrating the processing configuration for components, FIG. 6 is a diagram explaining the processing execution procedure by componentization, FIG. 7 is a functional block diagram of automatic management of software components according to the second embodiment of the present invention, and FIG. Figure 8 is a processing flowchart, Figure 9 is a diagram showing an example of information in the database file, Figure 1O is a diagram showing an example of management information obtained by analyzing the above information, and Figure 1 is a diagram showing an example of information in the database file.
Figure 1 shows how management information is stored in the database.
FIG. 12 is a diagram showing an example of inputting search information in this system, FIG. 13 is a diagram showing an example of search results, and FIG. 14 is a functional block diagram of automatic program synthesis, which is another embodiment of the present invention. Figure 15 is a processing flowchart, Figure 16 is a diagram showing an example of operation procedure data of a data input device input to the system, Figure 17 is a diagram showing computer internal data of input data, and Figure 18 is a diagram of input data. A diagram showing an example of an analysis result, FIG. 19 is a diagram showing a source code of a program execution control program synthesized based on the above analysis result,
Fig. 20 is a diagram showing the source code of the finally synthesized program, Fig. 21 is a functional block diagram of automatic generation of a program execution control table according to yet another embodiment of the present invention, and Fig. 22 is the processing thereof. 23 is an input data format and key operation flow diagram, FIG. 24 is a business/key sequence matrix diagram, and FIG. 25 is a diagram showing the format of a generated control procedure table. 1: Data flow diagram creation, 2: Extraction of processing for "things", 3 Niger-ping, 4: Detailing, 5: Parts registration,
6: Program generation, 11, 51. 101: Interactive display terminal device, 12, 52: Computer processing device. 13: Management control unit, 14: Input reception unit, 15: Management information creation unit, 16: Management information storage unit, 18: Management information search unit, 20: Software component storage database file, 21: Management information storage database file , 25
．． 26.28: Link information, 53 Niprogram automatic synthesis control unit, 54: Input data reception unit, 55: Input data analysis unit, 56: Program component execution control unit synthesis unit, 57:
Program component database search unit, 58 Niprogram synthesis unit, 59 Niprogram component database, 62 Niprogram source code storage file, 102: Data import unit, 103: Syntax analysis unit, 104: Key sequence flow information processing unit, 105: Flow information storage file,
106: Matrix information processing unit, 107: Matrix information storage file, 108: Flow diagram drawing unit, 109: Matrix table drawing unit, 111: Control table generation processing unit. Figure 1 Figure 2 B: Terminal O: Processing data storage location → : Data (cold) Figure 4 Figure 7 Figure 8 Figure 9 Figure SYSTEM-NAME: 5YST belly 1 (V
2);5HIYOU-BUHIN: BUHIN
1 (Vl); : BUHIN 2 (Vl) ; : BUHIN 3 (Vl); DATA-KOUSEI : BUHIN 1 (V
l) + DATA l (Vl) + DATA 2 (VO); : BLJHIN 2 (Vl) + DATA 2 (VO) 10 DATA 21 (Vl) + DATA 22 (Vl); : BUHIN 3α1) + DATA 1 (Vl) + DATA 31 (V2) + DATA 32 (%'2); DATA-ZOKUSEI: DATA 1 (Vl
) = BIT et al.);: DATA 2 (VO) = B
IT (16);: DATA 21 (Vl) = BI
N (16);: DATA 22 (Vl) = BI
N(16);: DATA 31 (V2) = DEC
(5) i: DATA 32 (V2) = DEC (5)
;Fig. 11 Fig. 12 Fig. 13 HENKOU-BUHIN-NAME: BUHIN 1 jBUHIN3 Fig. 14 Fig. 18 DATA I RETUrtN POINT FROM
20DATA 2 BRANCI (I POINT
To 3&5DATA 3 TENKEY-NYURY
OKU-PP AFTER2DATA + ATSUK
AISHA-PP AFTI3DATA 5 GATH
ERPOINT FloM 2 & Cow DATA 19G
OUKEI-PP AFTER18DATA 20 r
(ETUIIN POINT To IDATA 21
5YURYO-PP AFTER20DATA 22
FINAL DATA PlloCCESS NYUKIN Is
1 Figure 19 C0NT[)L 1 : P[)C. 5TEP 1: 5TEP 2: IP KEY-10THEN Do
;3TEP SEN CALL ATSUKAISI(A-
PP; S'l'EP 5: END; 5TEI'19: ELSB Do 1CALL
GOUKEI-PP. END; 5TEP20: IF'KEYQ, 5YUrtYOTl-
IENGoToSTEPl;5TEP 21: CAL
L 5YLIRYO-PP; 5TEP 22: EN
D C0NTIIOL 1 ;-~ He
Yu 0〈 ・- Kum, 0＜＜＜

Claims (1)

[Claims] 1. Software development in an interactive manner by reusing software components, comprising a database file for storing software components, an interactive display terminal, and a computer for processing information input from the display terminal. In this method, a data flow diagram showing the data input/output relationship is created, and from the data flow diagram, the "thing" that generates the data, the "place" where the data is stored, the data input,
A software development support method that focuses on an item such as a "device" that is output or displayed, extracts data input/processing or editing/output processing for the item, and converts it into a component. 2. A system that supports software development in an interactive manner by reusing software components, which is equipped with a database file for storing software components, an interactive display terminal, and a computer that processes information input from the display terminal, Provided with a function to take the operating procedure of the terminal device as input data, analyze the received input data, and synthesize a source code of a program component execution control program, and a function to search for a corresponding program component from a program component database, A software development support method characterized by synthesizing source codes obtained by these functions. 3. By using the database file, it is possible to receive input of information that constitutes the system, analyze the input information, and obtain history information of software components, history information of data that constitutes software components, and data that constitutes software components. By linking attribute information, you can create systematic management information for the software components that make up the system.
It is characterized by accumulating the management information in the database file, accepting information for searching the management information from an interactive display terminal, analyzing the input information, and searching for the corresponding management information. Claim 2
Software development support method described in section. 4. When constructing a software system that performs one task by inputting a sequence of function keys, it is necessary to input key sequence information for each task in a data format based on simple rules, and to analyze the syntax of this input information. , a function of decomposing the analysis result into key sequence flow information and task-specific key sequence matrix information is provided, and a procedure control table is generated from the two pieces of information. 2
Software development support method described in section.