JPH02156330A - Software parts developing system - Google Patents

Abstract

PURPOSE:To facilitate maintenance and management of a software parts group and its concreting procedures by providing meta description in a part of software parts to easily recognize connection relations between software parts and lower-order parts. CONSTITUTION:Structure description to describe software parts is provided with a meta description part to select adoption or rejection of the description, and meta description of (map: X) or the like to evaluate essential description of each selection object X is used for the selection object in accordance with request specifications to develop and concrete processing contents desciprion of structure description. Thus, the general level of structure description which describes software parts is raised, and reduction of the number of parts, retrieval of parts, and maintenance and correction of a system are facilitated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Object of the Invention] (Field of Industrial Application) The present invention relates to a software component expansion method used in a program synthesis system and the like.

(Prior Art) Generally, software components for an automatic program synthesis system are defined so that each one can be applied to as wide a range of requirements as possible. Such versatility of a software component can be obtained by parameterizing a part of the description of the software processing content in the component definition as a variable part for responding to changes in required specifications. This is called generalization of the software component, and the parameterized part in the software component description is called the muddled parameter.

Conventionally, the method for implementing this muddying parameter according to required specifications and the definition of software components have been defined separately.

(Problem to be solved by the invention) However, in this way, the definition of software components,
Since the methods for embodying the muddying parameters according to the required specifications were defined individually, the muddying level of the parameters could not be set too high, and even if you looked only at the definition of the part, it was difficult to see if it corresponded to the required specifications. There were problems such as it was difficult to understand how the data was converted, and it was difficult to maintain consistency between the two.

In view of the above circumstances, the present invention can increase the level of muddiness of software components, thereby reducing the number of components, making it easier to search for components, and further facilitating system maintenance and modification. The purpose is to provide a software component deployment method.

[Structure of the invention]

(Means for Solving the Problem) In order to achieve the above object, the software component deployment method according to the present invention defines a software component by a description indicating processing content and a meta description for selecting this description, and The present invention is characterized in that the meta-description process is performed in accordance with specifications, and the description of the process content is developed and made concrete.

(Function) In the above configuration, a meta description is provided in a part of the software component so that processing contents can be selected. Facilitate maintenance and management of groups and their instantiation procedures.

(Embodiment) Hereinafter, a software component development method according to the present invention will be explained using a ladder program for a programmable controller as an example.

First, among sequence control programs, there is a program for selecting an operation mode, an operation location, and the like.

These programs typically perform the same function of selecting some object by keeping an output on while a certain condition is met, and they have a common logical structure.

The logical structure common to such similar software is
For example, it can be described as shown in FIG.

In the structural description shown in this figure, (map: :<1ocal
-variable>cbody-f'orm><al
ternative>) is one of the meta descriptions, and indicates that the body description <body-"orm> is to be evaluated for each selection target <alternative>.

In addition, X is a local variable local to store each selection target while evaluating the body description based on it.
-variable>. Also, (between
: A)B;C) is a description that expresses the condition that C is satisfied after A is satisfied until B is satisfied. Furthermore, (*G* selection command accepted) $(*G*
To simplify the description, $(*G* absolute condition) is a specification description of a lower-level part that summarizes functional units with a certain semantic coherence, and this is the expansion result of the lower-level part. The description is replaced.

For example, the lower part for (0 pieces selection command accepted) is configured by the description shown in FIG.

In the lower part description shown in this figure, (case: :cke
y-“.

rIn>(((kukey>*)*kukey>l cfo
rm>*)ri$(when: :ctest-fora
+><body-['or+g)) is also a meta description,
The former is generated based on the given requirement specifications.
<f' below <key> that matches y-f'orI>
orm>, the latter is replaced by <te
This is a description that is replaced by <body-f'orm> if the condition based on <body-f'orm> is satisfied under a given requirement specification. This description also includes descriptions such as specifying a lower functional component component (zero * self-selection command).

Below, other lower-level parts are described in the same way, and the meta description is also
Software that does not even include the specification of lower-level parts! - Once the software description is obtained, by converting it into the target language using a language converter, it is possible to complete a program that is executable and corresponds to the required specifications.

Next, an example of an actual processing procedure based on the above-mentioned software component development principle procedure will be explained with reference to FIG.

First, a plurality of software components having the above-described structure are registered in advance.

Then, applicable software components are searched and extracted according to the required specifications (step 5TI).

After this, the meta description process in the structural description of this software component is processed and developed into an appropriate software description (
Step 5T2).

Then, when the processing of the meta description part in the software component description is completed (step 5T3
), processes the designated description portion of the lower component in the structure description that describes this software component, and replaces the component description of the lower component with the designated description (step 5T4).

After this, when the processing of the lower parts is completed (step 5T5
), check whether a meta description is included in this lower-level component (step 5T6); if a meta description is included, return to the first step and repeat the above-mentioned process.

When software components and lower-level components that do not include meta-descriptions are obtained, they are converted into the target language by a language converter to create software components according to the required specifications (step 5T7).

In this way, in this embodiment, a meta description part is provided in the structural description that describes the software component to select the description, and the process in the structural description is performed using the meta description according to the required specifications. Since the content description is developed and made concrete, it is possible to increase the level of muddiness of the structural description that describes software components, thereby reducing the number of components, making it easier to search for components, and further improving system maintenance. , which can facilitate modification.

〔Effect of the invention〕

As explained above, according to the present invention, it is possible to increase the level of muddiness of software components, thereby reducing the number of components, making it easier to search for components, and further facilitating maintenance and modification of the system. Can be done.

[Brief explanation of the drawing]

FIG. 1 is a schematic diagram for explaining an embodiment of the software component deployment method according to the present invention, FIG. 2 is a schematic diagram for explaining the embodiment, and FIG. 3 is a schematic diagram for explaining the embodiment. It is a flowchart.

Claims (1)

[Claims] (1) A software component is defined by a description indicating processing content and a meta-description that selects this description, and the meta-description is processed according to the required specifications to develop and embody the processing content description. Software component deployment method.