WO2012053392A1

WO2012053392A1 - Software-product-line development assisting device, method thereof, and program thereof

Info

Publication number: WO2012053392A1
Application number: PCT/JP2011/073318
Authority: WO
Inventors: 佐藤　昇
Original assignee: 株式会社日立製作所
Priority date: 2010-10-20
Filing date: 2011-10-11
Publication date: 2012-04-26
Also published as: JP2012088933A; GB201307123D0; JP5319643B2; GB2498305A; GB2498305A8

Abstract

The present invention enables the arbitrary mapping of components executed in the transition conditions for state transition, and enables the reuse of features. This software-product-line development assisting device (1) of a software system is provided with: a feature information recording unit (23) wherein feature information is recorded that represents characteristics including state transition information indicating the transition of the state of a virtual subject or control subject in the software system; a determination component selection means (13) that performs determination for causing transition of each state with respect to a user and enables the selection of any given determination component on the basis of the features; and a determination component management means (13) that enables the reading as needed and the recording/holding in a determination component recording unit (22) of selectable determination components.

Description

Software product line development support apparatus, method and program thereof

The present invention relates to a software product line development support apparatus that manages information related to software product line development of a control monitoring system, a method thereof, and a program thereof.

Conventionally, a feature model associated with features (characteristics) is generally used to develop a software product line that supports user software development. When creating this feature model, the model creator is required to extract appropriate features and associations between features.

For example, Patent Document 1 describes a system that provides a development environment for a feature-oriented software product line. This system of Patent Document 1 applies a known software product line methodology to a specific domain (or region), and performs necessary feature selection for feature analysis and application program development on the domain (for example, controlled object). , Generation of reusable asset components (program module assets), generation of software components through macro processing and shape management for components (creation of program sources), application software development using software components and software testing in virtual environments It is intended to support.

In the conventional technology including Patent Document 1, domain analysis / feature analysis clearly analyzes the common points and differences between functional, environmental, technical, and realization, and reflects them in component development. It has the advantage of increasing usability and applicability.

JP 2007-12003 A

By the way, in general, a control monitoring system for controlling a plant or the like has the following functions. Acquires information on equipment to be controlled and monitored (hereinafter referred to as equipment status monitoring function), performs control computation (hereinafter referred to as control computing function) based on the equipment status, Control output (hereinafter referred to as a control output function) to control the equipment.

Equipment status monitoring function and control output function are different for each system. Protocols) are considered as differences, domain (for example, control target) analysis and feature (characteristic) analysis are performed, and reusable components (program modules) can be created.

However, the control calculation function has a function of comprehensively determining the state of the equipment to be controlled and monitored and the state of the entire system and performing the calculation, and outputting to the equipment to be controlled and monitored. The state of these facilities and the state of the entire system are generally different for each user's system, and it is common to express them with conventional functional, environmental, technical, and actual domain analysis and feature analysis. The reusability is difficult.

For example, in a user's centralized A system, if a failure occurs in some devices, the control operation function must determine not to perform control output. On the other hand, in the distributed B system of other users, when a failure occurs in some devices, the control operation function performs control output semi-automatically, but when a serious failure occurs in the entire B system, It is determined not to perform control output.

In this way, the functions to be executed differ depending on the system operation, and the point of which device is treated as a major failure when it fails depends on the system configuration for each user and the operation of each user. It is necessary to create as many features as (system configuration × operation), and it is difficult to create a reusable feature in another user's system.

That is, in the conventional software product line development, feature modeling and component development are performed based on functional, environmental, technical, and concrete domain analysis and feature analysis. However, in a control and monitoring system in which user operations and system configurations differ from system to system, features that are functionally combined add or delete components within the features, so the reusability of features cannot be expected depending on the system configuration There's a problem.

As described above, since the functions of each system for each user are different for each control monitoring system, it is impossible to share functions in the current software product line that is performed by rearranging the modules for each function, making it difficult to deal with them. ing.

SUMMARY OF THE INVENTION In view of the above circumstances, an object of the present invention is to provide a software product line development support apparatus, a method thereof, and a program thereof that can arbitrarily map components executed under transition conditions of state transitions and can reuse features. .

A software product line development support apparatus according to claim 1 of the present invention is a software product line development support apparatus of a software system, and indicates a state transition of a control target or a virtual target in the software system. A feature information storage unit that stores feature information representing characteristics including transition information, and a determination for shifting each state, and a user can arbitrarily select a determination component based on the feature Judgment component selection means, and judgment component management means for storing and holding the selectable judgment components in the judgment component storage unit and reading them out as necessary are provided.

A software product line development support apparatus method according to claim 11 of the present invention is a software product line development support apparatus method of a software system, wherein the software product line development support apparatus includes a feature information storage unit, A feature representing a characteristic including state transition information indicating a state transition of a control target or a virtual target in the software system in the feature information storage unit. Information is stored, and the determination component selection unit makes a determination for transitioning the respective states and allows a user to arbitrarily select a determination component based on the feature. Selectable The Do decision component, it is made possible to read as required and stores held in determining the component storage section.

The software product line development support apparatus program according to claim 21 of the present invention is a program for causing a computer to execute the method of the software product line development support apparatus of claim 11 of the present invention. .

According to the present invention, it is possible to realize a software product line development support apparatus, a method thereof, and a program thereof that can arbitrarily map components executed under the transition condition of the state transition and can reuse the feature.

1 is a block diagram of a software product line development support apparatus according to an embodiment of the present invention. The figure which shows an example of a structure of the execution component information which concerns on embodiment. The figure which shows an example of a structure of the judgment component information which concerns on embodiment. The figure which shows an example of a structure of the feature information which concerns on embodiment. The conceptual diagram for demonstrating registration of the state identification information which concerns on embodiment. The figure which shows the state identification information edit screen which concerns on embodiment. The conceptual diagram for demonstrating registration of the relevant information between states which concerns on embodiment. The figure which shows the related information edit display screen between states which concern on embodiment. The figure which shows the related information edit screen between states which displayed the state transition which takes the nested structure which concerns on embodiment. The conceptual diagram of the consistency check of the state transition information which concerns on embodiment. The figure which shows an example of the conditions which cannot change the state which concern on embodiment.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
FIG. 1 is a block diagram of a software product line development support apparatus 1 according to an embodiment of the present invention.
In the present embodiment, a software product line development support device 1 for developing a software product line of a train operation management system that manages train operations on railways will be described. The control target of the train operation management system (monitoring control system) is equipment related to train operation.

The software product line development support device 1 of the embodiment includes a storage unit 2 that is a storage unit such as a hard disk that stores information on features indicating various characteristics related to train operations, and an input device such as a mouse, a keyboard, and a touch panel. 31 and a user interface unit 3 including a display device 32 such as an LCD (Liquid Crystal Display), and a control unit 4 that controls the entire software product line development support device 1.

The storage unit 2 stores a software product line development support program 10 responsible for control (processing) of the software product line development support device 1. The control unit 4 is implemented by executing a software product line development support program 10 (hereinafter referred to as a development support program 10) by a CPU (Central Processing Unit). In FIG. 1, the CPU reads the development support program 10 from the storage unit 2 such as an HDD (Hard disk drive), develops and executes it in the main storage unit (not shown), and embodies the control unit 4. It shows the state.

The storage unit 2 manages an execution component information storage unit 21 that manages information (execution component information) of an execution component that is a program module to be executed, and information (determination component information) of a determination component that is a program module that performs a determination. Determination component information storage unit 22, feature information storage unit 23 that stores information of features (characteristics) including state transitions such as equipment related to operation, and feature model analysis result storage that stores the results of analyzing each information Part 24.

The control unit 4 embodied in the development support program 10 includes an interface unit 11 that manages input / output from the user interface unit 3 and an execution component information management unit that manages execution component information such as what program module level is present. 12, a judgment component information management unit 13 that manages judgment component information such as what kind of judgment is made for a program module, a feature information management unit 14 that manages information on features including state transitions such as equipment, System consistency check and automatic source code generation from information stored in each information storage unit (21, 22, 23, 24) of the storage unit 2 and the information management unit 15 for managing various types of information in an integrated manner And an information analysis unit 16 that performs system tests and the like. That.

The interface unit 11 exchanges information between the various functions of the software product line development support device 1 and the input device 31 and the display device 32 used by an operator (user). The display device 32 performs display when developing the software product line.

For example, the interface unit 11 is based on a function of transmitting an operator (user) instruction from the input device 31 to the information management unit 15 or the information analysis unit 16 and information transmitted from the information management unit 15 or the information analysis unit 16. And a function for generating a screen to be displayed on the display device 32 (for example, a screen definition, a screen object, etc.). The interface unit 11 also has a function (for example, a screen switching definition) for switching various screens displayed on the display device 32 in response to an operation of an operator (user) from the input device 31. .

The execution component information management unit 12 manages execution component information stored in the execution component information storage unit 21.
The execution component information storage unit 21 in the storage unit 2 stores execution component related information including execution component identification information for identifying individual execution components, and related information between execution components indicating parent-child relationships between execution components, and execution components. Storage medium.

The determination component information storage unit 22 of the storage unit 2 stores storage information including information on individual determination components (determination component information), for example, identification information of determination components, determination components, and related information between determination components. It is.
The determination component information management unit 13 of the control unit 4 manages the determination component information stored in the determination component information storage unit 22. That is, the determination component information management unit 13 stores / holds, reads, updates, and deletes determination component information in the determination component information storage unit 22.

The feature information storage unit 23 of the storage unit 2 stores the relationship between the state held by the equipment to be controlled and the determination component used for the state transition condition, and information on the execution component executed when the state transition occurs. This corresponds to a storage medium to be stored.
The feature information management unit 14 of the control unit 4 manages feature information including state transition information stored in the feature information storage unit 23. The feature information management unit 14 stores, reads, updates, and deletes feature information in the feature information storage unit 23. Note that the feature information storage unit 23 that stores feature information such as a state and the feature information management unit 14 that manages feature information define state, and thus are state definition means. An arbitrary state can be input from the user interface unit 3 by the user. Alternatively, data may be transferred from another system, and an arbitrary state may be recorded in the feature information storage unit 23 by the feature information management unit 14.

The information management unit 15 of the control unit 4 exchanges information between the

management units

12, 13, and 14 and the interface unit 11 and exchanges information with the information analysis unit 16.
The information analysis unit 16 displays the function for verifying the consistency of each information based on the execution component information acquired from the information management unit 15, the determination component information, and the feature information including the state transition, and the verification result. It has a function of outputting to the device 32 side, a function of automatically generating executable source code (program source code), and a function of testing the generated source code.
The feature model analysis result storage unit 24 of the storage unit 2 is a storage medium that stores the results analyzed by the information analysis unit 16.

<Configuration of information stored in each

information storage unit

21, 22, 23>
Next, the configuration of information stored in the various

information storage units

21, 22, and 23 will be described with reference to FIGS.
FIG. 2 is a diagram illustrating an example of the configuration of the execution component information J stored in the execution component information storage unit 21.
The execution component information J includes execution component identification information J1 and execution component related information J2.

The execution component identification information J1 includes information such as “execution component ID (Identification)” and “execution component name” for identifying individual execution components. In addition, the execution component identification information J1 includes “execution component comment” which is a comment about what the execution component does, and “creation date and time” of the execution component.

The execution component relation information J2 includes information such as “execution component relation ID” for uniquely identifying the relation information between execution components and “child execution component ID” for identifying the parent-child relationship of the execution components. . Furthermore, the inter-execution component relation information J2 indicates “relationship with child component” (in FIG. 2, “selection” for selecting either C10001 or C10002) indicating the relation with the child execution component, and the execution It includes “execution component reference relation” indicating related execution component information necessary for the component to operate. That is, FIG. 2 shows that in order for the execution component with the execution component ID “C10000” to operate, it is necessary to refer to the execution component with the execution component ID “C20001”.

FIG. 3 is a diagram illustrating an example of the configuration of the determination component information H stored in the determination component information storage unit 22 (see FIG. 1).
The judgment component information H includes judgment component identification information H1 and judgment component related information H2.
The determination component identification information H1 includes information such as “determination component ID” and “determination component name” for identifying individual determination components. Further, the determination component identification information H1 includes a “determination component comment” indicating the content of the determination component and its “creation date”.

The inter-determination component related information H2 includes information such as “relation ID between determination components” for uniquely identifying the relevant information of the determination component, and “child determination component ID” forming a parent-child relationship of the determination component. Further, in the relation information H2 between judgment components, “association with child components” indicating the relation with child judgment components (in FIG. 3, “selection type” for selecting either “C10001” or “C10002” is designated. "Indicates the relationship between determination components" indicating the determination components required when operating the determination component (W10000). That is, FIG. 3 shows that it is necessary to refer to the judgment components of judgment component IDs C20001, C20002, and C20003 in order to operate the judgment component (W10000).

FIG. 4 is a diagram illustrating an example of the configuration of the feature information F of the state transition information stored in the feature information storage unit 23.
The feature information F includes state identification information F1 and state related information F2.
The state identification information F1 includes information such as a “state ID” for identifying a state of each facility, a state name, an execution component F1a executed when the state is reached. The execution component F1a executes automatic control A when entering this state (entry), does nothing during this state (stay), and does nothing when exiting this state (exit). No (NULL). In the status identification information F1, “comment” explaining the contents of this status and “creation date” of this status are displayed.

The inter-state relation information F2 includes a “relation ID” for identifying inter-state relation information, which is relation information between states, and is used for transitioning between equipment states as “state transition information” from state to state. It includes a state determination component F2a, a state transition source F2b, and a state transition destination F2c that are used as conditions.

<Various processes to realize software product line development support>
Next, various processes for realizing software product line development support will be described with reference to FIGS.
In the following, regarding the state of equipment, etc., “1. Registration of state identification information”, “2. Registration of related information between states”, “3. Check consistency of state transitions”, “4. Sources for realizing state transitions” “Code generation” will be described, and then “5. Test of generated source code” which is a test of the generated program source will be described.

Note that the execution component information and the judgment component information are registered in the storage unit 2. Registration of execution component information and determination component information is similar to conventional component creation, application program creation, and software program creation, and is a well-known technique, and is not particularly described here. Furthermore, it is assumed that the execution component and the judgment component are tested at the time of registration and guaranteed.

1. Registration of State Identification Information FIG. 5 is a conceptual diagram for explaining registration of state identification information.
The state transition creator (user) P creates a state via the state identification information editing screen G1 shown in FIG.
In general, the state is created for specific objects that have state transitions, such as the equipment to be controlled and the state of the entire system, but states are defined for virtual equipment and events. It doesn't matter.

In the state identification information editing screen G1, an execution component (hereinafter referred to as an entry-time execution component) that is executed when transitioning to a defined state can be selected from the execution component combo box G1a. Specifically, when the execution component combo box G1a for selecting the entry execution component is clicked on the state identification information editing screen G1, the interface unit 11, the information management unit 15, and the execution component information management of FIG. The execution component information management unit 12 acquires a selectable execution component list from the execution component information storage unit 21 via the unit 12, and displays it in the execution component combo box G1a.
The user selects an execution component at the time of entry from the execution component list displayed in the execution component combo box G1a as necessary. If there is no need to execute at entry, there is no problem in the unselected state.

In addition, the component that is executed when stagnant in the defined state (maintaining the defined state), and the component that is executed when exiting from the state (hereinafter referred to as "stay execution component" and "exit execution" respectively) Similarly, it is possible to select an execution function feature (stay) combo box G1b and an execution function feature (exit) combo box G1c. In the state identification information editing screen G1, “comment” and “creation date / time” explaining the contents of the state name “NOP” are displayed.

When the state transition creator P presses the “Register” button G1d, information input on the state identification information editing screen G1 is transferred from the user interface unit 3 (see FIG. 1) to the interface unit 11, the information management unit 15, FIG. It is stored in the feature information storage unit 23 by the feature information management unit 14 via the feature information management unit 14.

2. Registration of related information between states FIG. 7 is a conceptual diagram for explaining registration of related information between states.
The state transition creator (user) P defines the condition of the state transition for transitioning from state to state via the inter-state related information edit display screen G2 shown in FIG. In general, the condition for state transition uses a feature that determines the condition, but input / output information of each facility (standard input / output information and input / output information of an external system) may be used.

First, the state transition creator P selects the state registered in “1. Registration of state identification information” from the state information list G2a on the inter-state related information edit display screen G2 in FIG. All status lists registered in the space of the status information list G2a on the inter-status related information edit display screen G2 are displayed.
The state transition creator (user) P selects a state to be used from the state information list G2a via the user interface unit 3 (see FIG. 1) and registers it in the inter-state related information editing screen G2b.

Next, in the user interface unit 3, in the state related information editing screen G2b of FIG. 8, the states where the state transition can occur are connected by the state transition line G2s by dragging with the mouse.
The result of selecting the state of the transition source (start point of the arrow) and the state of the transition destination (end point of the arrow) on the inter-state related information editing screen G2b of FIG. 8 is obtained via the interface unit 11 and the information management unit 15 of FIG. The feature information management unit 14 is notified, and is temporarily managed by the feature information management unit 14, for example, stored in a temporary storage area of the feature information management unit 14.

Further, as for the state G2b1 that can take a nested structure as shown in the inter-state related information editing screen G2b shown in FIG. 9, further state transitions can be stored in the state G2b1. That is, the state G2b2 that first transitions at the timing when the parent state (G2b1) is reached is defined in the same manner as described above.

Next, conditions for causing state transition are defined via the user interface unit 3 (see FIG. 1).
The state transition line G2s is clicked, and the judgment component and the return value G2d displayed in the condition component input combo box G2c are selected. Selectable determination components are determined by the determination component information management unit 13 from the determination component information storage unit 22 via the determination component information storage unit 22, the determination component information management unit 13, the information management unit 15, and the interface unit 11 of FIG. By acquiring, the result is displayed on the display device 32 (see FIG. 1).

Then, the selected result is notified to the feature information management unit 14 via the interface unit 11 and the information management unit 15 in FIG. 7, and is temporarily stored in the feature information management unit 14, for example, the feature information management unit 14 Save to the temporary storage area. Here, the number of determination components for state transition is not limited to one, and a plurality of determination components can be selected, and logical expressions of a plurality of determination components may be combined. The determination component selected in the conditional component input combo box G2c and the selected return value G2d are displayed in the conditional component list G2e.
When the state transition creator P presses the “Register” button G2f in FIG. 9, the input information is notified to the feature information management unit 14 via the interface unit 11 and the information management unit 15 in FIG. The information is stored in the feature information storage unit 23 by the unit 14.

3. State Transition Consistency Check FIG. 10 is a conceptual diagram for explaining state transition information consistency check.
After completion of the registration of “1. Registration of state identification information” and “2. Registration of related information between states”, the execution component information storage unit 21, the determination component information storage unit 22, and the feature information storage unit 23 shown in FIG. Check the consistency of the contents registered in.

First, whether the entry execution component, the stay execution component, the exit execution component, and the determination component stored in the feature information storage unit 23 exist in the execution component information storage unit 21 and the determination component information storage unit 22, respectively. The execution component information management unit 12 and the determination component information management unit 13 confirm each of them. If a non-existing feature is used, such as being deleted, it is displayed as an error on the display device 32 of the user interface unit 3 in FIG.

Next, the information analysis unit 16 performs a state transition consistency check. It is checked whether a state that cannot logically change state is defined.
FIG. 11 shows an example of the condition G2g where state transition is impossible.
As shown in the example of FIG. 11, when there is a state transition in which the logic is inconsistent or a condition incapable of state transition from one state as a result of the consistency check of the state transition of the information analysis unit 16 (FIG. 11 G2g) is displayed as an error on the display device 32 of the user interface unit 3 via the interface unit 11.

The state transition creator P (user) checks the contents of each error displayed on the display device 32, corrects the execution component information, the judgment component information, and the feature information as necessary, and performs the consistency check again. Call.

4). Source Code Generation that Realizes State Transition Next, source code that realizes state transition is generated.
The information analysis unit 16 automatically generates executable source code that realizes state transition based on the registered information. Since automatic source code generation using a state transition diagram is a well-known technique, it is not particularly described here.

The generated source code is code that is actually downloaded and controlled by the train operation management system (monitoring control system), and is used in “5. Test of generated source code” described below. The generated source code is stored in the feature model analysis result storage unit 24 by the information analysis unit 16.

5. Test of Generated Source Code Next, the information analysis unit 16 (see FIG. 1) performs a test of the source code generated in “4. Source code generation for realizing state transition”. A combination of the state transition, determination component, and execution component defined above is comprehensively tested on the virtual environment. When the test scenario is generated in the information analysis unit 16 at the source code generation, the test code is also discharged at the same time, and it can be verified whether the test scenario operates as intended in the virtual environment.

According to the above configuration, the condition of component execution (execution component, determination component) can be arbitrarily selected by the software developer (user) according to the state transition specified by the external definition.
In other words, in a control and monitoring system (for example, a train operation management system) with different system configuration and operation for each user, the component execution timing is different, but focusing on relatively uniform state transitions, state transitions As shown in Fig. 8 and Fig. 9, software developers (users) can arbitrarily map components that are executed under the transition conditions of the above, enabling feature reusability and high production of software product lines. Can be realized.

In the above embodiment, the software product line development support apparatus 1 exemplifies a case where the control unit 4 is accommodated in one form. However, if the described function can be performed, the control unit 4 is installed on a plurality of computers. May be deployed.
Moreover, the memory | storage part 2 may memorize | store in a separate database server, and may be divided | segmented and comprised.

The present invention is not limited to the monitoring control system as long as it is a system or process that can be expressed using a state transition diagram, and can also be used in other system devices and processes.

DESCRIPTION OF SYMBOLS 1 Software product line development support apparatus 10 Software product line development support program 12 Execution component information management part (component definition means, execution component check means)
13 Judgment Component Information Management Unit (Judgment Component Selection Unit, Judgment Component Management Unit, Judgment Component Checking Unit)
14 Feature information management unit (feature management means, state definition means, component definition means, state management means, state transition means)
16 Information analysis section (source code generation means, software test means, consistency check means)
21 execution component information storage (component definition means)
22 Judgment Component Information Storage Unit (Judgment Component Storage Unit)
23 Feature information storage unit (state definition unit, feature information storage unit, state management unit, component definition unit)
24 Feature model analysis result storage F2 State related information (state transition means)

Claims

A software product line development support device for a software system,
A feature information storage unit that stores information on features representing characteristics including state transition information indicating state transition of a controlled object or a virtual object in the software system;
A determination component selecting means for making a determination for transitioning the states to the user and making it possible to arbitrarily select a determination component based on the feature;
A software product line development support apparatus comprising: a determination component management unit that stores and holds the selectable determination components in a determination component storage unit and that can be read out as necessary.
In the software product line development support device according to claim 1,
A software product line development support apparatus characterized by separating and managing the features grouped functionally and the determination component.
In the software product line development support device according to claim 2,
State defining means for defining an arbitrary state;
Each of the defined states includes an execution component that is executed for the first time when the state is reached, an execution component that is executed when the state is maintained, and an execution component that is executed when the next state is moved. A software product line development support device comprising a component definition means that can be defined.
In the software product line development support device according to claim 3,
A software product line development support apparatus, comprising: a state transition unit that transitions between the defined states using an execution result of a component selected by a user.
In the software product line development support device according to claim 3 or 4,
The state transition means includes
Transition between the states according to input / output information of the software system
A software product line development support device.
In the software product line development support device according to claim 3 or 4,
A software product line development support device comprising state management means for configuring the arbitrary state defined by a user in a nested structure.
In the software product line development support device according to claim 3 or 4,
Execution component check means for checking whether the execution component is in the execution component storage unit;
A software product line development support apparatus, comprising: determination component check means for checking whether the determination component is in the determination component storage unit.
In the software product line development support device according to claim 4,
A software product line development support device comprising consistency check means for checking whether the state transition is consistent.
In the software product line development support device according to claim 3 or 4,
A software product line development support device comprising source code generation means for generating executable source code from the feature defined by a user and the execution and determination components.
In the software product line development support device according to claim 4,
A software product line development support apparatus, comprising: software testing means for testing whether a combination of the transition between the states, the determination component, and the execution component operates as intended in a virtual environment.
A software product line development support apparatus method for a software system, comprising:
The software product line development support apparatus includes a feature information storage unit, a determination component selection unit, and a determination component management unit,
The feature information storage unit stores feature information representing characteristics including state transition information indicating state transition of a control target or a virtual target in the software system,
The determination component selection unit makes a determination for transitioning the states to the user and arbitrarily selects a determination component based on the feature.
The method of the software product line development support apparatus, wherein the determination component management means stores the selectable determination component in a determination component storage unit and can read out the determination component as necessary.
In the method of the software product line development support apparatus according to claim 11,
A software product line development support apparatus method characterized by separating and managing the functionally grouped features and the judgment component.
In the method of the software product line development support apparatus according to claim 12,
The software product line development support device comprises state definition means and component definition means,
The state defining means defines an arbitrary state,
The component definition means includes, in each defined state, an execution component that is executed for the first time when the state is reached, an execution component that is executed when the state is maintained, and a transition to the next state. A software product line development support apparatus method characterized in that execution components to be executed can be defined.
In the method of the software product line development support apparatus according to claim 13,
The software product line development support device comprises state transition means,
The state transition means transitions between the defined states using the execution result of the component selected by the user.
In the method of the software product line development support apparatus according to claim 13 or 14,
The state transition means includes
A method of a software product line development support apparatus, wherein transition between the states is made according to input / output information of the software system.
In the method of the software product line development support apparatus according to claim 13 or 14,
The software product line development support device comprises a state management means,
The state management means configures the arbitrary state defined by the user in a nested structure.
In the method of the software product line development support apparatus according to claim 13 or 14,
The software product line development support device includes execution component check means and determination component check means,
The execution component check means checks whether the execution component is in the execution component storage unit,
The method of software product line development support apparatus, wherein the determination component check means checks whether the determination component is in the determination component storage unit.
In the method of the software product line development support apparatus according to claim 14,
The software product line development support device comprises consistency check means,
The method of the software product line development support apparatus, wherein the consistency check means checks whether the state transition is consistent.
In the method of the software product line development support apparatus according to claim 13 or 14,
The software product line development support device comprises source code generation means,
The method of the software product line development support device, wherein the source code generation means generates executable source code from the feature defined by a user and the execution and determination components.
In the method of the software product line development support apparatus according to claim 14,
The software product line development support device comprises software testing means,
The method of the software product line development support apparatus, wherein the software test means tests whether the transition between the states and the combination of the determination component and the execution component operate as intended in a virtual environment.
A program for causing a computer to execute the method of the software product line development support apparatus according to any one of claims 11 to 14, or 18 or 20.