JPH07129382A - Spiral type object oriented software development supporting system and software developing method - Google Patents

Abstract

PURPOSE:To provide a spiral type software development supporting system and a software developing method capable of reusing the constitutional elements of design information and packaging information. CONSTITUTION:This system is provided with a design information editor 2, a design information data base 3 for storing design information, a packaging information data base 4 for storing packaging information for packaging the design information on a source code, a format information storage device 5 storing at least one format file storing format information inherent in computer language to be used, and a source code generator 6 for inputting up-to-date design information, a necessary part in the packaging information and the format information and generating a source code. The system is also provided with a design information extracting device for reflecting the design information of a changed source code to a design information data base 3, a packaging information extracting device for reflecting the packaging information of the changed source code to the data base 4, a design information/packaging information linking device 9 for maintaining correspondence relation between both the data base 3, 4, and a management device 10 for managing the whole system.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for supporting software development of spiral type object-oriented software, and in particular, in the course of developing software in a spiral form, a spiral in which created format information and the like can be reused. Type object oriented software development support system.

[0002]

2. Description of the Related Art At present, object-oriented software has been widely used because reusability and expandability are required. As a method of this object-oriented software development, a spiral software development method is known.

FIG. 16 shows the concept of the method of developing the spiral object-oriented software. As shown in the figure, in spiral type software development, first, a design drawing etc. of the central part of the software is created based on the required specifications of the software, coding is performed based on this design drawing, and an experiment is conducted. The original required specifications are reviewed and evaluated, and the software is spirally completed by gradually adding functions while repeating the above process.

FIG. 17 shows each step of a conventional spiral type object-oriented software development method and a product of each step.

In the conventional spiral type software development method, first, a design document 51 such as a design drawing and a specification is created from a start point 50 based on required specifications (step 200).

Next, the design document 51 is converted into a modification source code 52 (step 210). A source code generator is generally used for this source coding. The source code 52 generated by this source code generator may be deficient in details due to mechanical generation, or the software may be changed on the source code. Therefore, an engineer adds the source code 52 to the source code. Modifications such as changes and deletions are made to create the changed source code 53 (step 220).

Next, the changed source code 53 is converted into the changed design document 54 by a parsing software such as a parser (step 230).

Next, the modified design document 54
Based on the above, the required specifications are reviewed, the design document is corrected by the screen editor, and the design document 51 which is the basis of the second development cycle is created (step 240).

After that, the above steps 210 to 240 are repeated, and while the software and the required specifications are reviewed, the functions of the software are gradually enhanced to complete the software.

The design information of the design documents 51 and 54 is composed of a frame element, a guidance element and a design-specific element. Here, the frame element is an element that constitutes the substance of object-oriented software such as a class, an object, an attribute, and a method. The guidance element is an element that describes each frame element. The design-specific element is an element indicating information unique to the design, such as the position and size of a graphic, the meaning of a diagram, and the like.

The mounting information included in the source codes 52 and 53 is composed of a frame element, a leaf element, a guidance element and a glue element. Here, the frame element and the guidance element are the same as those of the design information. The leaf element encodes the representation of methods, declarations, etc. The glue element is an element that includes a grammar and a promise specific to each computer language.

As shown in FIG. 18, the design information and the mounting information share a frame element and a guidance element. Design-specific elements are specific to design information, and leaf elements and glue elements are specific to implementation information.

Since the design information and the mounting information have the above-described structure, in the conventional spiral type software development, when the source code 52 for correction is generated from the design document 51 (step 210), as shown in FIG. To
Design-specific elements are dropped, and glue and leaf elements are added instead. That is, this conversion uses only the common frame and guidance elements.

In this case, step 21 is performed for each cycle.
In step 0, the engineer reviews the source code again and adds the leaf element and the guidance element.

When the changed design document 54 is generated from the changed source code 53 (step 230), the leaf element and the glue element of the source code are dropped as shown in FIG. In this case, the technician uses a screen editor to add design-specific elements to the design document.

[0016]

However, in the conventional spiral object-oriented software development support system and software development method described above, when the source code is modified and converted into a design drawing, etc., as described above, Alternatively, when the design drawing or the like is modified and then converted into the source code, the design-specific element, the guidance element, or the leaf element of the source code or the design drawing developed up to that time is lost.

These elements were produced over a long period of time, and it was extremely uneconomical to lose them after each conversion.

Particularly, when the source code is manually modified, leaf elements and guidance elements added are
It takes a lot of time for a skilled engineer to add, and although the source code modification is often done only on a part of the source code, it is started at each cycle of spiral software development. It was very inefficient to create these elements from.

Further, since the computer software has become complicated and large in size in recent years, it becomes more rational for a plurality of engineers to develop common software in a plurality of optimal computer languages. .

However, in the conventional spiral type software development, the source code is generated from the design drawing, etc.
Since the source code generator distributed in the general market was used, there was a problem that the software had to be developed in a computer language that the source code generator could convert.

Therefore, an object of the present invention is to solve the above-mentioned problems of the conventional spiral type software development, and to reuse leaf elements, guidance elements and design-specific elements once created, unless they are changed or deleted. Type software development support system and software development method.

Another object of the present invention is to provide a spiral type software development method capable of spirally developing common object-oriented software using a plurality of types of computer languages that differ for each object.

[0023]

In order to achieve the above object, a spiral type software development support system according to the present invention includes a design information editor for editing software design drawings and specifications, and a design information editor for editing the design drawings and specifications. A design information database storing the included design information, an implementation information database storing implementation information for implementing the design information in a source code, and at least one format file storing format information specific to the computer language used. A format information storage device, a source code generator that generates the source code by inputting the latest necessary parts of the design information and the mounting information, and the format information, and design information of the modified source code. Of the modified source code and the design information extraction device that reflects the above in the design information database. A mounting information extracting device that reflects information in the mounting information database, a design information / mounting information link device that maintains a correspondence relationship between the design information database and the mounting information database, and a management device that manages the entire system. It is characterized by having.

Further, the spiral software development method according to the present invention essentially provides the design information of the design drawing and the specification sheet from the object-oriented point of view with the design-specific element which is information unique only to the design drawing or the specification sheet. A frame element,
A design information database that classifies and stores guidance elements that describe the frame elements, implementation information that implements the design information in a source code, frame elements, guidance elements, and leaf elements that indicate attributes of the frame elements. First, create a software design drawing and specifications based on the required specifications by using the mounting information database that is categorized and stored in and the format file that stores the glue element that is the format information unique to each computer language. The first step of storing the design information of the design drawing or the specification in the design information database and storing the corresponding mounting information in the mounting information database, and the latest frame element from the design information database and the mounting information database. And the guidance element and leaf element, and from the format file The second step of selecting the glue element corresponding to the language of the code to generate the source code, the third step of modifying the source code, and converting the modified source code into a design drawing or specifications and The fourth step of writing the frame element, guidance element, and leaf element changed in the code correction stage in the design information database and the mounting information database, and reviewing the design drawing and specifications and correcting them as necessary, and design drawing / Fifth step of writing the frame element, guidance element, design-specific element and leaf element changed in the specification revision stage in the design information database and the mounting information database, and the second step after completing the first step It is characterized in that the software is completed by sequentially repeating the fourth to fourth steps.

[0025]

According to the spiral object-oriented software development support system and software development method of the present invention, the design information of the software is classified into the frame element, the guidance element and the design-specific element by the design information database and stored. Code implementation information,
The mounting information database classifies and stores the frame elements, the guidance elements, and the leaf elements.

Further, the information of the design information database and the information of the mounting information database are linked to each other by the design information / mounting information link device by utilizing the sameness of the frame elements so as to maintain the correspondence relationship.

With the above structure, when design information or mounting information is changed in each spiral type development cycle,
The contents of the design information database and the mounting information database are changed by the design information extracting device and the mounting information extracting device, and further, by the design information / mounting information link device,
The changed portion can be selected by using the frame element as a clue, and for the unchanged portion, the frame element, leaf element, guidance element, design-specific element, etc. can be reused as they are in the next cycle.

As a result, in each cycle of the spiral type software development, the reusable leaf elements, guidance elements, design-specific elements, etc. that have been created up to that point can be reused, and the spiral type software can be more efficiently used. Can do development.

Further, the spiral object-oriented software development support system and software development method of the present invention stores at least one format file for storing format information of a computer language used by the format information storage device.

By making the format file of this format information storage device selectable for each frame element, the system and software development method of the present invention develop common software by a plurality of different computer languages for each frame element. It will be possible.

[0031]

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows a configuration example of a spiral object-oriented software development support system according to the present invention.

The spiral object-oriented software development support system 1 of the present embodiment comprises design information editors 2a, 2b, 2c, a design information database 3, a mounting information database 4, a format information storage device 5, and a source code generator. 6, and design information extraction devices 7a and 7
b, 7c, mounting information extracting devices 8a, 8b, a design information / mounting information link device 9, and a management device 10.

Design information editors 2a, 2b, 2c
Is a screen editor for creating and editing design drawings such as message flow diagrams, state transition diagrams, sequence charts, and the like. With this design information editor 2a, 2b, 2c, the software developer creates a design drawing / specification of the software according to the required specifications.

Design information extracting devices 7a, 7b, 7c
Is an apparatus for extracting design information such as design drawings created by the design information editors 2a, 2b, 2c as data of the design information database 3. This design information extraction device 7
Reference characters a, 7b, and 7c have a parser / generation function, and interpret various figures and explanations of a design drawing to extract various elements constituting design information.

The design information database 3 is a database for classifying and storing various elements of the design information extracted by the design information extracting devices 7a, 7b, 7c.

The mounting information database 4 is a database for classifying and storing various elements of mounting information for mounting the design information on the source code.

The contents of the design information database 3 and the mounting information database 4 are rewritten in each cycle of spiral type software development.

The design information / mounting information link device 9 is a device that compares information stored in two databases and creates a logical link between data. By the design information / mounting information link device 9, common elements (frame elements) of the design information database 3 and the mounting information database 4
Are linked so that the correspondence between the contents of both databases is maintained.

The format information storage device 5 is a storage device for storing information regarding a format unique to each computer language. The format information storage device 5 has a plurality of format files that store format information of a plurality of computer languages, and can output appropriate format information in response to a request.

The source code generator 6 is a device for converting the design information into a source code, and reads out the format information of the format information storage device 5, the design information of the design information database 3, and the mounting information of the mounting information database 4. And design code the source code according to the format information.

In FIG. 1, reference numerals 11 and 12 represent examples of source codes in the computer languages C ++ and Smalltalk, respectively.

The mounting information extracting devices 8a and 8b are devices for parsing the source code and extracting various elements of the mounting information. By the mounting information extracting devices 8a and 8b, the components of the mounting information are extracted from the C ++ source code 11 and the source code 12 of Smalltalk and stored in the mounting information database 4.

The management device 10 controls and manages the operation of each device according to each stage of spiral type software development.

Next, a software development method using the spiral object-oriented software development support system 1 of this embodiment will be described.

FIG. 2 shows a method for developing spiral object-oriented software. In FIG.
Spiral software development is a starting point 2
Starting from 0, the design information editors 2a, 2b,
The initial design drawing 21 is created by 2c (step 100). When the design drawing of the above step 100 is created, the design information is extracted by the design information extracting devices 7a, 7b, 7c of FIG. 1 and stored in the design information database 3 after being classified into frame elements, guidance elements and design-specific elements. (Step 101).

The information stored in the design information database 3 is stored in the design information / mounting information link device 9 shown in FIG.
Correspondence is established with each element of the mounting information database 4 (step 102). In the first cycle, only the frame element and the guidance element corresponding to the frame element and the guidance element of the design information database 3 are generated in the mounting information database 4.

Next, the source code generator 6 of FIG.
Thus, the source code 22 for correction is generated from the design drawing 21 (step 110). When generating the source code 22 for correction, the source code generator 6
Is a design information database 3 and a mounting information database 4
Then, necessary frame elements and guidance elements are acquired from (steps 111 and 112), and further, a glue element specific to the computer language to be used is acquired from the predetermined format file 23 of the format information storage device 5 (step 113).

Next, the modified source code 24 is created from the modification source code 22 (step 120).
This work is done by the engineer by adding the source code,
This is achieved by making changes and deletions. The changed source code 23 is a frame element, a leaf element,
The format of the source code is adjusted by including glue elements.

Next, the modified source code 24 is as follows.
The mounting information extracting devices 8a and 8b in FIG. 1 convert the changed design drawing 25 (step 130). At this time, the mounting information of the changed source code 24 is reflected in the mounting information database 4 (step 131).

The changed mounting information reflected in the mounting information database 4 is linked to the design information database 3 by the design information / mounting information link device 9 (step 102). This link is performed by comparing the mounting information after the change with the design information before the change and logically associating equivalent frame elements.

The frame elements of the equivalent design information are
The frame element and its associated design-specific elements and guidance elements are preserved, as they mean the elements that have not changed.

On the other hand, the non-equivalent design information frame element means an element added or deleted at the stage of source code modification, so that the design information database is designed so that the design information and the mounting information match. Fix 3.

Design information database 3 with the above modifications
The design information of is reflected in the changed design drawing 25 (step 132). Conversion from the design information database 3 to the changed design drawing 25 is performed by changing the design information extracting devices 7a and 7 shown in FIG.
b, 7c.

Next, the design information editors 2a, 2b, 2c
The modified design drawing 25 is edited by to generate the design drawing 21 which is the basis of the next spiral type software development cycle (step 140).

The design information changed in this process is reflected in the design information database 3 via the design information extracting devices 7a, 7b, 7c (step 141). The information of the design information database 3 after this change is again sent to the mounting information database 4 by the design information / mounting information link device 9.
It will be linked to the implementation information of and maintained so as to have consistency in terms of content.

In the second and subsequent spiral type software development cycles, the processes of steps 110 to 141 are repeated to complete the software. It should be noted here that in the second and subsequent spiral cycles, as described above, the leaf elements, guidance elements, design-specific elements, etc. created up to the previous time are reused as they are unless they are changed, added, or deleted. Is to be done.

In FIG. 2, a region R surrounded by virtual lines shows a range where software development is performed by the spiral object-oriented software development support system 1 of the present invention.

Next, a concrete method of reusing the unchanged frame element and its associated elements will be described with reference to FIGS.

FIG. 3 shows an example of the element configuration of the design information and the mounting information stored in the design information database 3 and the mounting information database 4, respectively. In FIG. 3, reference numerals 31 and 32 show examples of the element configuration of the design information and the element configuration of the mounting information, respectively.

The design information element structure 31 includes frame elements 33a, 33b, 33c, 33d, 33e,
It has 33f. This frame element 33a, ..., 3
3f corresponds to the object configuration of the object-oriented software illustrated in FIG. The class, method, port, inheritance, type, attribute, and type shown in FIG. 4 are frame elements.

The frame elements 33a, ..., 33f include:
A guidance element for explaining the frame element and a design-specific element for indicating design-specific information such as position and size are attached. The guidance element and the design-specific element are also related to each other.

On the other hand, the mounting information element configuration example 32 is similar to the frame elements 34a, 34b, 34c, 34d corresponding to the respective objects of the object-oriented software.
It has a tree structure of 34e and 34f.

The frame elements 34a, ..., 34f include:
A guidance element that explains the frame element and a leaf element that defines the method are attached.

The equivalent frame elements of the design information element structure 31 and the mounting information element structure 32 are related by the design information / mounting information link device 9 so as to correspond to each other.

FIG. 5 shows the structure of each frame element 34a, ..., 34f of the mounting information element structure 32. As shown in FIG. 5, each frame element 34a, ..., 34f has a frame name 35 that identifies the frame element, and a plurality of expressions 36a, 36b, 36c (for example, descriptions in a plurality of different computer languages) are provided for each frame. Element 34a,
..., subordinate to 34f.

FIG. 6 shows the structure of each expression 36a, ..., 36c. As shown in FIG. 6, each expression 36a, ...,
36c has an expression name 37 that identifies the expression, and a guidance element 38, a glue element 39, and a front leaf element 40.
, And the rear leaf element 41 are subordinate to each expression 36a, ..., 36c.

FIG. 7 shows a method of expanding the mounting information having the above structure into a source code. When the source code is generated, the expression name 37 is specified for the expanded frame elements 34a, ..., 34f to request the code generation.

The frame elements 34a, ..., 34f are the glue elements 3 corresponding to the specified expressions 36a ,.
9 is selected, and expansion is requested for the expressions 36a, ..., 36c.

The expressions 36a, ..., 36c expand the source code by adding the front leaf element 40, the rear leaf element 41, the guidance element 38, and the glue element 39 to the attributes of the frame elements 34a, ..., 34f. The name 42 of the frame element is also expanded if necessary.

Further, when it is necessary to code a frame element subordinate to the frame element to be source coded, the expansion request is sent to the child frame element. In the child frame element, the source code is further expanded by the above method.

FIG. 8 shows an example of the source code generated as described above. In FIG. 8, a part surrounded by a thin broken line is a glue element, a part surrounded by a thick broken line is a guidance element, an underlined part is a frame element, and a part without a letter is a leaf element. As is apparent from this source code, the source code generator 6 adds leaf elements, guidance elements, and glue elements to the frame elements to form a source code in a predetermined format as a whole.

FIG. 9 shows the storage locations of the above-described elements, the documents (design documents, source codes, etc.) in which they are expressed, and their corresponding relationships.

As shown in FIG. 9, the design-specific element, the guidance element, and the frame element are stored in the design information database 3, and these correspond to the information of the design documents 21 and 25. The guidance element, the frame element, and the leaf element are stored in the mounting information database 4, and these correspond to the source codes 22 and 24. The glue element is stored in the format information storage device 5, and this glue element is used in the expressions of the source codes 22 and 24.

Here, it should be noted that the frame elements of the design information database 3 and the frame elements of the mounting information database 4 are logically linked (linked). By the action of this link, leaf elements and the like can be reused.

Next, a specific method of the above logical link will be described. For example, after the source code is added, changed, or deleted in step 120 of FIG. 2, the changed mounting information is parsed by the design information extracting devices 7a, 7b, 7c and stored in the mounting information database 4. It

In this state, the element configuration 32 of the mounting information in FIG. 3 has been changed, but at this point, the element configuration 32 of the mounting information is irrelevant to the design information element configuration 31.

10 and 11 conceptually show a method of linking the constituent elements of the design information element structure 31 and the constituent elements of the mounting information element structure 32.

As shown in FIG. 10, in order to perform logical linking, each frame element of the element structure 32 of the changed mounting information and the frame structure 31 of the element information of the design information before the change are compared via the logical ID and are equivalent. Identify non-equivalent to

Here, “equivalent” means a component that exists before the change and that exists after the change. Equivalent elements include equivalent elements whose contents completely match and non-equivalent elements in which a part (name, etc.) of the contents on the implementation information side has been changed.

The non-equivalent means a component that does not correspond in the element configuration 32 of the mounting information after the change and the element configuration 31 of the design information before the change. The non-equivalent elements include an isolated element on the mounting information side and an isolated element on the design information side. The isolated element on the implementation information side is generated by adding a new element to the implementation information by modifying the source code. The isolated element on the design information side is generated by deleting the element of the implementation information by modifying the source code.

As shown in FIG. 11, the logical link is performed for each element of the parent set of the mounting information element set, and subsequently for each element of the child set attached to each element. In the element structure of the tree structure, logical links are made from the top element of the tree, and the logical links of the respective elements are expanded downward in a fan shape.

As shown in FIG. 12, the logical ID consists of a product name, a version name, and an integer value. The product name is the name of the unit that manages the storage and retrieval of information. The version name is a character string or a value that represents the version of the product name. The integer value is an integer value that uniquely determines a specific frame element within a management unit of a predetermined version (for example, within a file of a predetermined version).

After comparing and logically linking all the constituent elements, regarding the frame elements having the same value,
Reuse the design-specific and guidance elements that come with it in the next spiral software development cycle. For non-equivalent frame elements, the software developer modifies the elements on the design information side to make them consistent. For non-equivalent frame elements, elements on the design information side are added or deleted. Through this work,
The design information element configuration 31 and the mounting information element configuration 32 are completely matched, and the elements are connected by a logical link.

FIG. 13 is a diagram for explaining that the components of the design information before the change are reused. In the figure, it is assumed that the element indicated by the symbol A is not changed on the mounting information side, the element indicated by the symbol B is deleted, and the element indicated by the symbol C is added, on the side of the design information which is not changed by the logical link. Element a is identified and this element a is reused.

The element b on the design information side corresponding to the element B deleted on the mounting information side is deleted at the stage of forming a logical link. As for the element C added on the mounting information side, a new frame element c is formed on the design information side.

As is apparent from the above, according to this method, among the constituent elements on the design information side, the element a which has not been changed by the modification of the source code is the one created in the previous cycle. It can be reused as it is in the next spiral type software development cycle, and efficient spiral type software development can be performed.

According to the present invention, the mounting information can be reused as in the case of reusing the design information. 14
Shows a method of reusing the mounting information when a change in the design information is reflected in the mounting information.

In the method shown in FIG. 14, the changes made by the design information editors 2a, ..., 2c on the design information side are stored as instructions in each frame element. When the design information is converted into a source code, the equivalent and latest mounting information (previous version) is fetched from the mounting information database 4 and each instruction of the design information is sequentially executed with respect to the mounting information. As a result, the implementation information is updated and the source code is generated.

According to this method, for the design information element in which no instruction is stored, that is, the element which has not been changed, the mounting information of the previous version is used as it is, and it is reused in the next cycle of the spiral type software development. Used.

FIG. 15 shows another method for reflecting the changed design information in the mounting information. In this method, the mounting information of the current version is generated based on the changed design information. A logical link is generated between the mounting information of this current version and the design information, as shown in the figure. At this point, each frame element of the implementation information of the current version has no expression element.

Next, the "spatial equivalent" mounting information, that is, the mounting information of the previous version is acquired from the mounting information database 4. Here, “spatial equivalence” means the logical ID
Product name and integer value are the same, but only the version name is different.

Next, an attachment element such as a representation of the mounting information of the previous version is added to the mounting information of the current version via the logical ID.

By this, attached elements such as expressions created up to the previous version are reused.

Further, according to the spiral object-oriented software development support system and software development method of the present invention, a plurality of engineers can develop common object-oriented software in different types of computer languages. This is because the frame element has a plurality of expression elements attached thereto as shown in FIG. 5, and the format information storage device 5 outputs predetermined format information in response to a request from the source code generator 6. To be achieved.

That is, according to the present invention, each frame element includes information that constitutes the substance of software such as an attribute and a method of an object, the information is converted into various source codes by expression, and each frame is converted. Since each element can be independently developed spirally by the above method, common software can be simultaneously developed by a plurality of different kinds of computer languages.

[0096]

As is apparent from the above description, according to the spiral object-oriented software development support system and the software development method of the present invention, the design information and the mounting information developed in each spiral software development cycle are stored. Each component is classified and stored in the design information database and the mounting information database, and those common elements are logically linked.

With this configuration, when any one of the design information and the mounting information is changed, the changed component and the unchanged component are selected by the logical link, and the unchanged component is selected. It can be reused as it is.

As a result, in each cycle of spiral type software development, the software portion developed up to the previous cycle is reproduced, only the minimum necessary corrections can be made, and efficient spiral type software development is carried out. You can

Further, the format information storage device of the spiral type object-oriented software development support system of the present invention has a format file storing format information of different kinds of computer languages, and is suitable according to the request of the source code generator. Format information is provided, and since each frame element has different types of expression elements, it is possible to provide a spiral type software development method capable of developing common software by different types of computer languages for each frame element. it can.

[Brief description of drawings]

FIG. 1 is a diagram showing the configuration of a spiral object-oriented software development support system of the present invention.

FIG. 2 is a diagram showing each step of the spiral object-oriented software development method of the present invention.

FIG. 3 is a diagram exemplifying an element configuration of design information and mounting information.

4 is a diagram exemplifying a tree structure of object-oriented software which is a source of the element configuration of FIG.

FIG. 5 is a diagram showing a configuration of each frame element.

FIG. 6 is a diagram showing the content and structure of each expression of each frame element.

FIG. 7 is a diagram illustrating a method of converting each frame element of implementation information into a source code of a predetermined computer language.

FIG. 8 is a diagram showing an example of a source code generated from design information and mounting information.

FIG. 9 is a diagram showing a device in which elements of design information and components of mounting information are stored, documents representing these elements, and their mutual relationships.

FIG. 10 is a diagram showing a method of logically linking the mounting information element configuration after the change and the design information element configuration before the change.

11 is a diagram showing the expansion of the logical link of FIG.

FIG. 12 is a diagram showing a configuration of a logical ID used in a logical link.

[Fig. 13] When generating a design drawing from source code,
FIG. 4 is a diagram illustrating a manner in which a component of design information is reused.

FIG. 14 is a diagram illustrating a first method of reflecting changed design information on mounting information before change.

FIG. 15 is a diagram illustrating a second method for reflecting the changed design information in the mounting information before the change.

FIG. 16 is a diagram showing the concept of a spiral software development method.

FIG. 17 is a diagram showing each step by a conventional spiral type software development method and various documents generated by the step.

FIG. 18 is a diagram showing a relationship between components of design information and mounting information.

FIG. 19 is a diagram showing how information elements are exchanged when a modification source code is generated from a design document by a conventional spiral software development method.

FIG. 20 is a diagram showing how the information elements are replaced when a design drawing or the like is generated from the changed source code in the conventional spiral software development method.

[Explanation of symbols]

1 Spiral Object Oriented Software Development Support System 2 Design Information Editor 3 Design Information Database 4 Mounting Information Database 5 Format Information Storage Device 6 Source Code Generator 7 Design Information Extracting Device 8 Mounting Information Extracting Device 9 Design Information / Mounting Information Link Device 10 Management apparatus

Claims (5)

[Claims] 1. A design information editor for editing software design drawings and specifications, a design information database for storing design information included in the design drawings and specifications, and a design information database for implementing the design information in a source code. A mounting information database that stores mounting information, a format information storage device that stores at least one format file that stores format information specific to the computer language used, and the latest design information and necessary parts of the mounting information. A source code generator for generating a source code by inputting the above-mentioned format information, a design information extraction device for reflecting the changed source code design information in the design information database, and a changed source code implementation information. A mounting information extracting device which reflects the mounting information database; the design information database; A spiral object-oriented software development support system comprising: a design information / mounting information link device for maintaining a correspondence relationship with a packaging information database; and a management device for managing the entire system. 2. The format file has format information corresponding to a plurality of computer languages, and is configured to output a predetermined type of format information in response to a user's request. 1. A spiral object-oriented software development support system according to 1. 3. The design information / mounting information link device compares the shared elements of the design information and the mounting information to generate a logical link, and thereby the correspondence relationship between the source code and the element of the design drawing or the specification document. The spiral object-oriented software development support system according to claim 1, wherein 4. A spiral object-oriented software development method in which software is divided according to requirement specifications into objects, which are constituent parts, and the software is completed by repeating the steps of designing, coding, evaluation, and reviewing requirement specifications. In, the design information of the design drawing and the specification document, the design-specific element that is information unique only to the design drawing and the specification document, the frame element that is essential from an object-oriented viewpoint, and the guidance element that explains the frame element. And a design information database for classifying and storing the design information into the source code, and mounting information for classifying and storing the frame information, the guidance element, and the leaf element indicating the attribute of the frame element. A database and glue elements, which are format information specific to each computer language, are stored. First, create a software design drawing and specifications based on the required specifications, and store the design information of the design drawings and specifications in the design information database, and store the corresponding mounting information. A first step of storing in the mounting information database; obtaining the latest frame element, guidance element and leaf element from the design information database and the mounting information database, and a glue element corresponding to the language of the source code from the format file. The second step of selecting the source code to generate the source code, the third step of modifying the source code, and converting the modified source code into a design drawing or specifications and changing the frame in the source code modification stage. Elements, guidance elements and leaf elements are added to the design information database and implementation information database. And the fourth step of writing in the design drawing and the specification sheet, and if necessary, amending the frame element, the guidance element, the design-specific element and the leaf element which are changed at the design drawing / specification sheet amendment stage. The fifth step of writing in the information database and the mounting information database, and the second to fourth steps after completing the first step.
A spiral object-oriented software development method characterized by completing the software by repeating the steps in sequence. 5. A single object-oriented software, which allows corresponding glue elements to be selected from the format file for each frame element, thereby allowing different frame language expressions in different computer languages. The spiral object-oriented software development method according to claim 4.