Abstract:
An automatic program configuring apparatus capable of facilitating maintenance management of a storage device even when software components stored therein increase in number is disclosed. The apparatus includes a database unit storing software configuration information and software components corresponding to individual items of software component arrangement information which are organized in a tree structure which is represented by a markup language with tags being uniquely definable by a user. The apparatus further includes a configuration information input unit for inputting the software configuration information from the database unit, an interface unit for acceptance of selection of components by the user while displaying a component selection screen based on the input software configuration information, a software component input unit for inputting from the database storage unit software components corresponding to the user&#39;s component selection result, and a generator unit for combining together the input software components to generate a software program.

Description:
FIELD OF THE INVENTION 
       [0001]    The present invention relates to a method and apparatus for automatically configuring a software program. 
       BACKGROUND OF THE INVENTION 
       [0002]    Software programs to be built in electronic equipment increase in complexity year by year, resulting in likewise increases in development time period and costs thereof. Under such circumstances, it is useful for system engineers to develop a new software program by combining together the currently existing software components. Further, by selecting time-proven ones of the existing software components, it becomes possible to maintain the quality of a new version of software which was developed by combining them together. 
         [0003]    Note however that in cases where mechanical works for combining software components are manually performed by an operator or system designer, it is considered that there are risks which follow: defects can be occurred and mixed due to possible man-caused mistakes. Additionally, when the software components to be combined together increase in number to go beyond several hundreds or more, the mechanical works are no longer readily achievable. 
         [0004]    One known automatic program configuring apparatus which combines together the presently available software components to thereby generate source codes of a new software program in an automated way is disclosed, for example, in JP-A-02-105222, which is arranged to include a means for storing therein software component arrangement information as organized in a tree structure, and a means for storing software components corresponding to the individual configuration information elements making up the software configuration information in a tree structure that is the same as the tree structure. By use of these two separate storage means that store the software configuration information and the software components in the same tree structure, it becomes possible to readily specify a software component from among the configuration information elements making up the software configuration information. 
         [0005]    Unfortunately, it is a must for the prior art approach to perform maintenance management of the information being stored in each storage means in a way such that the same tree structure is established between the means for storing the software configuration information and the means for storing the software components. When the software components appreciably increase in number, costs needed for such the maintenance management increase accordingly. 
       SUMMARY OF THE INVENTION 
       [0006]    It is therefore an object of the present invention to make easier the maintenance management with respect to the means for storing software configuration information and software components even when these software components greatly increase in number. 
         [0007]    In accordance with one aspect of this invention, a technique for configuring a software program in an automated way is provided. A database storage unit is used to store therein software configuration information and software components corresponding to individual items of software component arrangement information included in the software configuration information in such a manner that these are organized in a single tree structure by means of a markup language with tags being uniquely definable by a user. Based on software configuration information as input from the database storage unit, display a component selection menu on a display screen for permitting a user to choose his or her preferred software components by using an input device. Then, input from the database unit one or more software components corresponding to the user&#39;s selection result. Next, combine together these input software components to thereby generate a software program required. Preferably, the component selection result which is accepted from the user is configured into a partial tree by means of the markup language and then output it. Upon receipt of those software components corresponding to this partial tree from the database unit, combine together the input software component to thereby produce a program. 
         [0008]    According to the present invention, it is possible to facilitate the maintenance management for the means for storing the software configuration information and software components even when the software components noticeably increase in number. 
         [0009]    Other objects, features and advantages of the invention will become apparent from the following description of the embodiments of the invention taken in conjunction with the accompanying drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0010]      FIG. 1  is a functional block diagram of an automatic software program configuring apparatus in accordance with one embodiment of the present invention. 
           [0011]      FIG. 2  shows a hardware configuration of the apparatus of  FIG. 1 . 
           [0012]      FIG. 3  shows one example of a tree structure which is included in a file  151  of  FIG. 1 , which is named the component arrangement information+software components.xml. 
           [0013]      FIG. 4  shows an example of the tree of  FIG. 3  which is described by XML. 
           [0014]      FIG. 5  shows an example which divides the file shown in  FIG. 3  into a plurality of files by using hyper links. 
           [0015]      FIG. 6  shows an exemplary component selection display screen of a GUI unit  111  of  FIG. 1 . 
           [0016]      FIG. 7  shows an example of a file named the choice result.xml indicating the contents by a logical tree. 
           [0017]      FIG. 8  shows an XML corresponding to  FIG. 7 . 
           [0018]      FIG. 9  shows an example which uses a template engine. 
           [0019]      FIG. 10  shows a source file generated by a code generator unit  120 . 
           [0020]      FIG. 11  shows an example of the component arrangement information +software components.xml file which indicates the contents in the form of a logical tree structure. 
           [0021]      FIG. 12  shows an example of the choice result.xml indicating the contents by a logical tree. 
           [0022]      FIG. 13  shows a template file in the case of using a template engine. 
           [0023]      FIG. 14  shows a source file generated by the code generator unit  120 . 
           [0024]      FIG. 15  shows a template file in the case of using a template engine. 
           [0025]      FIG. 16  shows a source file generated by the code generator unit  120 . 
           [0026]      FIG. 17  shows a template file in the case of using a template engine. 
           [0027]      FIG. 18  shows a source file generated by the code generator unit  120 . 
           [0028]      FIG. 19  shows a template file in the case of using a template engine. 
           [0029]      FIG. 20  shows a source file generated by the code generator unit  120 . 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0030]      FIG. 1  is a functional block diagram of an automatic software program configuring apparatus in accordance with one embodiment of the present invention.  FIG. 2  shows a hardware configuration of  FIG. 1 . 
         [0031]    The automatic software configuring apparatus functions to combine a plurality of software components together to thereby generate a new software program in an automated way, and is arranged to include an automatic configuring unit  100  and a software component database unit  150 . In this example, the auto-configuring unit  100  is built in a client computer  201  whereas the software component database  150  is provided in a server  202 , although the auto-configuring unit  100  and software component database  150  may be built in the same computer. Alternatively, a component selector unit  110  and code generator unit  120  in the auto-configuring unit  100  may be disposed in different computers, respectively, when the need arises. 
         [0032]    The software component database  150  stores therein software configuration information and a plurality of software components. The software configuration information is made up of a plurality of items of software component arrangement information. In the software component database  150 , one-to-one correspondence is established between the items of the software component arrangement information and the software components. Each item of the software component arrangement information represents the name and setup parameter(s) of its corresponding software component. A software component indicates either a source file or a partial string of source code characters. In the software component database  150 , all of the software components and software component arrangement information are managed in a single tree structure and are stored as a file  151  named “component arrangement information+software components.xml.” 
         [0033]      FIG. 3  shows an example of the tree that is included in the component arrangement information+software components.xml file  151  of  FIG. 1 .  FIG. 4  shows an example of the tree of  FIG. 3 , which is described by the so-called extensible markup language (XML). Although the example using XML is shown herein, any other markup languages which let users create uniquely defined and customized tags may alternatively be employable for the description, such as a standard generalized markup language (SGML) or else. 
         [0034]    Turning to  FIG. 1 , the auto-configuring unit  100  is made up of a component selection unit  110  and a code generation unit  120 . The component selector unit  110  is constituted from a graphical user interface (GUI) unit  111  and a configuration information input unit  112 . The configuration information input unit  112  extracts only the software component arrangement information from the component arrangement information+software components.xml file  151  that is stored in the software component database  150  and outputs the information to the GUI unit  111  functioning as a man-machine interface. The GUI unit  111  displays a component selection menu on a monitor display screen based on the software component arrangement information as input from the configuration information input unit  112 .  FIG. 6  shows one example of the component selection display screen of the GUI unit  111  of  FIG. 1 . It accepts choice of a software component or components by a user  160  of the automatic software configuring apparatus. Upon receipt of the choice of such software component(s), the GUI unit  111  outputs such choice result to a file named the software component choice result.xml.  FIG. 7  shows in a logical tree form the contents of the software component choice result.xml file in the case where a process includes the steps of selecting a software component “AnalogWeight” from the software component arrangement information shown in  FIG. 3 , performing parameter setting which sets “AN 1 ” to “AnalogPort,” performing parameter setting which sets “PB 0 ” to “DigitalPort” as a parameter of a software component “StartButton” and selecting a software component “beeper.” As shown in  FIG. 7 , the GUI unit  111  outputs the software component choice result.xml file in such a way that the tree which is included in the software component choice result.xml file becomes, without fail, a partial tree of the tree which is inherently included in the component arrangement information+software components.xml file  151 . Note here that it is not always required that the software component choice result is output to the software component choice result.xml file and may alternatively be output directly to the configuration information input unit  112  as a memory image, such as an object or the like. 
         [0035]    The code generator unit  120  is constituted from a generation unit  121  and a software component input unit  122 . The software component input unit  122  inputs a software component choice result.xml file  130 . Then, based on the tree included in this file, it extracts the selected software components from the component arrangement information+software components.xml file  151  and then outputs them to the generation unit  121 . The generation unit  121  appropriately combines together these software components which are input from the software component input unit  122  and then outputs it as a list of compilable source codes. 
         [0036]    A detailed explanation will be given of respective units making up the automatic software configuring apparatus of this embodiment below. 
         [0037]    Turning back to  FIG. 4 , an example of the XML description will be described in detail. Here, a part of the XML corresponding to nodes  300  to  321  in the logical tree shown in  FIG. 3  is shown for purposes of convenience in illustration and discussion herein. 
         [0038]    In  FIG. 4 , the attributes that are defined in those tags of &lt;Group&gt;, &lt;Component&gt;, &lt;ChoiceComponent&gt;, &lt;Parameter&gt; and &lt;ChoiceParameter&gt; indicate the items of software component arrangement information. For example, at a tag  406  of &lt;ChoiceComponent name=“BooleanWeight”&gt;, the portion “name=“BooleanWeight”” indicates the item of the software component arrangement information. Below is an explanation of each tag. 
         [0039]    A &lt;Group&gt; tag is for classification of the software component arrangement information. For example, in  FIG. 3 , a node  300  corresponds to the &lt;Group&gt; tag  400  in  FIG. 4 , for defining an oven range system of “MicrowaveOven” per se. More specifically, it is shown in the tree of  FIG. 3  that all descendant nodes of the node  300  are either software component arrangement information or software components concerning the microwave oven range system. In addition, nodes  302  and  340  show that the software component arrangement information concerning the oven range system are classified into “Sensors” and “Actuators.” Introducing the generation unit tags as shown in  FIG. 4  makes it possible to represent the embedded structure of these generator unit tags. And, it is defined by nodes  304  and  330 ,  341 ,  342  that software components “WeightSensor” and “StartButton” belong to the category “Sensors” whereas software components “Beeper” and “Light” belong to the category “Actuators.” 
         [0040]    A &lt;Component&gt; tag is for defining the configuration information corresponding directly to software components. For example, in  FIG. 3 , a node  330  defines software component arrangement information concerning buttons categorized as “SlantButton”. Additionally, “optional=“true”” is defined in nodes  341  and  342  as the software component arrangement information. This indicates that the functions of such software components corresponding to the both nodes are optional. On the other hand, the node  330  has no such definition. Accordingly, it is defined that “StartButton” is not optional but essential for the functionality of the oven range system. 
         [0041]    A &lt;ChoiceComponent&gt; tag is the one that defines configuration information directly corresponding to a software component-more precisely, this tag is for defining alternatives or options of a software component. For example, in  FIG. 3 , the nodes  304  and  306 ,  314  permit “BooleanWeight” and “AnalogWeight” to be defined in the software component of “WeightSensor” as selectable options thereof. Whereby, it is defined that either one of the software components “BooleanWeight” and “AnalogWeight” should be chosen as the “WeightSensor.” More precisely, the node  306  corresponds to the &lt;ChoiceComponent&gt; tag  406  in  FIG. 4  for defining the software component arrangement information as to a weight sensor in the oven system in the category of “BooleanWeight.” By the &lt;ChoiceComponent&gt; tag, a software component of “BooleanWeight” out of available weight sensors is defined as one of the user&#39;s selectable options. In addition, the node  314  corresponds to a &lt;ChoiceComponent&gt; tag  414  in  FIG. 4 , for defining software component arrangement information as to a weight sensor in the category of “AnalogWeight.” By the &lt;ChoiceComponent&gt; tag, a software component of “AnalogWeight” out of the weight sensors is defined as one of the existing options. 
         [0042]    A &lt;Parameter&gt; tag is to define setup parameters of a software component. A &lt;ChoiceParameter&gt; tag defines options of the setup contents in the parameter. For example, in  FIG. 3 , a node  308  corresponds to a &lt;Parameter&gt; tag  408  in  FIG. 4 , for defining “DigitalPort” as a setup parameter of the “BooleanWeight” node  306 . The nodes  310  and  312  correspond to &lt;ChoiceParameter&gt; tags  410  and  412  in  FIG. 4 , respectively, for defining “PA 0 ” and “PA 1 ” as options of the setup contents of this parameter. 
         [0043]    In contrast, a portion residing between a &lt;src&gt; tag and a &lt;/src&gt; tag indicates a software component. In the &lt;src&gt; and &lt;/src&gt; tags, either &lt;file&gt; tag or &lt;text&gt; tag is insertable. A portion which is interposed between &lt;file&gt; and &lt;/file&gt; tags indicates a source code-described file per se as a software component whereas a portion residing between &lt;text&gt; and &lt;/text&gt; tags indicates as a software component a string of characters which become a partial source code and the path name of a file into which the character string is to be inserted. An example is that in  FIG. 4 , source code-described files “/src/Sensors/BooleanWeight/BooleanWeight.c” and “/src/Sensors/BooleanWeight/BooleanWeight.h” are indicated as software components in a &lt;src&gt; tag  407  immediately below the &lt;ChoiceComponent&gt; tag  406 . In addition, in a &lt;src&gt; tag  409  immediately beneath the &lt;Parameter&gt; tag  408 , a software component is indicated, which has a file path name of “/src/Sensors/Sensors.h” into which a source code character string is to be inserted, wherein this character string is “#define WeightSensorPort.” By introduction of the &lt;file&gt; and &lt;text&gt; tags in the way stated above, it becomes possible for the generation unit  121  to perform processing while distinguishing over each other the one that deals with a file per se as a software component and the one that deals with a source code character string as a software component. 
         [0044]    Also importantly, by interposing the &lt;src&gt; tag between any two of the &lt;Component&gt;, &lt;Parameter&gt; and &lt;ChoiceParameter&gt; tags, a one-to-one correspondence relationship is established for software components and the software component arrangement information corresponding to these software components. For example, in  FIG. 4 , by letting a file “/src/Sensors/BooleanWeight/BooleanWeight.c” be interposed within the &lt;src&gt; tag  407  while at the same time causing the same &lt;src&gt; tag to be interposed immediately below the &lt;ChoiceComponent&gt; tag  406 , one-to-one correspondence is established between the software component arrangement information of “BooleanWeight” and the software component “/src/Sensors/BooleanWeight/BooleanWeight.c.” 
         [0045]    Note here that a software component is also definable within the &lt;src&gt; tag  401  residing just beneath the &lt;Group&gt; tag  400 , for example. As previously stated, the &lt;Group&gt; tag  400  is the one that defines the oven range system of “MicrowaveOven” per se. Accordingly, defining a software component in the &lt;src&gt; tag  401  makes it possible to define the same software component as a common software component in an entirety of the microwave oven system. By enabling definition of the &lt;src&gt; tag immediately below the &lt;Group&gt; tag also, it is possible to define more than one common software component between the software components. 
         [0046]    With the arrangement above, it becomes possible for the configuration information input unit  112  to extract only the software component arrangement information by paying attention to the &lt;Group&gt; tag and the &lt;Component&gt;, &lt;ChoiceComponent&gt;, &lt;Parameter&gt; and/or &lt;ChoiceParameter&gt; tag. Regarding the software component input unit  122 , it becomes possible to extract a software component which corresponds to each item of the software component arrangement information by paying attention to the &lt;src&gt; tag. 
         [0047]    The above-noted tree that is described in the component arrangement information+software components.xml file  151  may be a single one in a logical sense: the tree may be divided into parts which are described in a plurality of files in a physical sense. For example, as shown in  FIG. 5 , it is also possible to describe by using hyper links the software components and software component arrangement information in a plurality of physically separate files which are organized logically in a single tree structure. 
         [0048]    The configuration information input unit  112  inputs the component arrangement information+software components.xml file  151  and then extracts therefrom only the software component arrangement information for output to the GUI unit  111 . More practically, the configuration information input unit  112  extracts only the software component arrangement information by referring to the &lt;Group&gt; tag and the &lt;Component&gt;, &lt;ChoiceComponent&gt;, &lt;Parameter&gt; and/or &lt;ChoiceParameter&gt; tag. 
         [0049]    The GUI unit  111  inputs the software component arrangement information from the configuration information input unit  112  and then visually displays on a display screen a component select menu based on the same information. An example is that upon input of the software component arrangement information shown in  FIG. 3  (or  FIG. 4 ), the GUI unit  111  displays a component choice screen such as shown in  FIG. 6 . The user  160  of the automatic software configuring apparatus operates the same screen by use of a mouse pointer  640  to thereby make his or her choice of a software component(s) and also perform parameter setup. 
         [0050]    The GUI unit  111  performs a tree displaying operation based on the software configuration information in a way which follows. One or more nodes which are defined by the &lt;Group&gt; tag are displayed in the form of contents-expandable folders, such as those indicated by icons  601 ,  602 ,  603  and  604  in  FIG. 6 . Regarding a node which is defined by the &lt;Component&gt; tag, if the attribute “optional” is not defined thereto, the tag is displayed as a contents-expandable folder, such as an icon  630  in  FIG. 6 . As for nodes defined by the &lt;Component&gt; and &lt;ChoiceComponent&gt; tags with the attribute being defined to be “true,” check boxes  610  and  611  are displayed to thereby indicate that their corresponding software components are optional or alternative. For nodes each corresponding to the &lt;Parameter&gt; tag, icons  620  and  631  are used for distinguishing them from the others. When clicking on the icon  620  or  631 , a group of nodes corresponding to the &lt;ChoiceParameter&gt; tag is displayed as an option for parameter choice. As an example,  FIG. 6  shows a display screen in case a click is made on the “AnalogPort”  620 . Here, nodes  318 ,  320  and  322  residing in a lower hierarchical level of the node  316  in  FIG. 3  are displayed as a parameter choice screen indicated by reference numeral  650  in  FIG. 6 . 
         [0051]    Upon receipt of software component choice and/or parameter setup from the user  160  of the automatic software configuring apparatus via the component choice screen shown in  FIG. 6 , the GUI unit  111  outputs such received result as a software component choice result.xml file  130 .  FIG. 7  shows in the form of a logical tree an example of the contents of such software component choice result.xml file  130  in the case where the user  160  has selected a software component “Beeper” while selecting “AnalogWeight” as the software component “WeightSensor,” performing its parameter setup for setting “AN 1 ” to “AnalogPort,” and setting “PB 0 ” to “DigitalPort” as parameter setup of “StartButton.” In this way, the GUI unit  111  outputs the software component choice result.xml file  130  in such a manner as to become a partial tree of the logical tree of the software component arrangement information as input from the configuration information input unit  112 . To do this, it is necessary, when a software component corresponding to a certain node is chosen, to include in the same file all the ascendant nodes which contain a parent of such the node. An exemplary description of XML file corresponding to the tree of  FIG. 7  is shown in  FIG. 8 . 
         [0052]    The software component input unit  122  inputs the software component choice result.xml file  130  and specifies the selected software component(s) by referring to the &lt;src&gt; tag in the component arrangement information+software components.xml file  151 . More specifically, when this file  151  is stored in XML database, it is possible to specify the target software component by use of XML Path (XPath) or XML Query (XQuery). 
         [0053]    In case XPath is used for example, software component identification is enabled in a way which follows. Consider the component arrangement information+software components.xml file  151  shown in  FIG. 3  (or in  FIG. 4 ) and the software component choice result.xml file  130  shown in  FIG. 7  (or  FIG. 8 ). The software component input unit  122  tracks or “traces” the tree of the software component choice result.xml file  130  from its route node toward a leaf node to thereby perform for each node the following processing. 
         [0054]    Firstly at step 1, obtain XPath of a presently visiting node. For example, when presently visiting at a node which corresponds to a &lt;ChoiceComponent name=“AnalogWeight”&gt; tag  801  in  FIG. 8 , its XPath becomes: “/Group[attribute::name=“MicrowaveOven”]/subGroups/Group [attribute::name=“Sensors”]/subGroups/Group[attribute:: name=“WeightSensor”]/ChoiceComponent[attribute::name=“AnalogWeight”]”. 
         [0055]    Then, at step 2, add “/src” to the tail end of the XPath thus obtained at the step 1. Whereby, the XPath becomes: “/Group[attribute::name=“MicrowaveOven”]/subGroups/Group [attribute::name=“Sensors”]/subGroups/Group[attribute:: name=“WeightSensor”]/ChoiceComponent[attribute::name=“AnalogWeight”]/src”. 
         [0056]    At step 3, use the XPath obtained at the step 2 to search inside of the component arrangement information+software components.xml file shown in  FIG. 4 , which is stored in the XML database. Thus it is possible to specify character strings that are interposed by the &lt;src&gt; tag  415 : &lt;file&gt;/src/Sensors/AnalogWeight/AnalogWeight.c&lt;/file&gt;, and &lt;file&gt;/src/Sensors/AnalogWeight/AnalogWeight.h&lt;/file&gt;. In this way, the software component is able to be extracted, which is in one-to-one correspondence with the software component arrangement information of &lt;ChoiceComponent name=“AnalogWeight”&gt;. 
         [0057]    In the way stated above, it is possible to extract every necessary software component by performing the above-stated processing while at the same time tracking the logical tree of the software component choice result.xml file  130  from its route node toward a leaf node. Then, the software component input unit  122  outputs the extracted software components to the generation unit  121 . 
         [0058]    The generation unit  121  combines together the software components as input from the software component input unit  122  and then outputs a combined result as a source file. In case the input software component is absolutely a file per se, this file will be output directly as a source file, without change. As in the component arrangement information+software components.xml file  151  shown in  FIG. 4 , it is possible to define only the path name of a file that is a software component and then store the entity of such file in the database individually. It is also possible to include the entire contents of such file that is a software component in the component arrangement information+software components.xml file  151 . 
         [0059]    Alternatively, in a case where the software component which was input by the generation unit  121  is a string of source code characters, it is necessary for the generation unit  121  to insert this character string into the designated file. Here, it is also possible to prepare in advance a template of such file of insertion.  FIG. 9  shows, as an example of the template of the insertion file, a template of “/src/Sensors/Sensors.h” file in the case of using Velocity (http://jakarta.apache.org/velocity/), which is a template engine. In  FIG. 9 , an insertion location of the character string is defined as “$component.context.” In Velocity, use of the directive “#foreach” makes it possible to insert a plurality of character strings in a sequential way as shown in  FIG. 9 . For example, consider the case where the software component choice result.xml file shown in  FIG. 7  or  FIG. 8  is input to the software component input unit with respect to the component arrangement information+software components.xml file shown in  FIG. 3  or  4 . At this time, attention is taken to those software components corresponding to the nodes  316 ,  320  and  331 - 332  out of the software components to be identified by the software component input unit  122 . Suppose that these software components are with designation of a common insertion destination file “/src/Sensors/Sensors.h” and are source code character strings of “#define WeightSensorPort”, “AN 1 ¥n”, “#define StartButtonPort” and “PB 0 ¥n” respectively, where “¥n” is a character indicative of line feed (LF). The generation unit  121  that has input these four source code character strings from the software component input unit  122  uses the Velocity to insert them into the template file shown in  FIG. 9  in a sequential way to thereby generate a source file shown in  FIG. 10 . 
         [0060]      FIG. 11  shows XML corresponding to a partial tree at a level lower than the node  340  in  FIG. 3 . Here, consider the case where the software component choice result.xml file shown in  FIG. 12  is input to the software component input unit  122  with respect to the component arrangement information +software component.xml file shown in  FIG. 11 . In this case, when looking at nodes  1200  and  1201  in  FIG. 12 , it can be seen that optional software components “Beeper” and “Light” are presently chosen. The software components specified by the software component input unit  122  include software components corresponding to the software components “Beeper” and “Light” in which “/src/FW/extern.h”, “src/FW/init.c”, “/src/FW/entry.cc” and “/src/FW/exit.c” are defined as source code character string insertion destination files as shown in  FIG. 11 . Template files of the above-noted files are shown in  FIGS. 13 ,  15 ,  17  and  19 , respectively. As apparent from  FIG. 11 , the generation unit  121  generates source files shown in  FIGS. 14 ,  16 ,  18  and  20  by inserting source code character strings “#include &lt;src/Actuators/Beeper/Beeper.h” and “#include &lt;src/Actuators/Light/Light.h” into an insertion destination file “/src/FW/extern.h,” inserting source code character strings “Beeper_init( );¥n” and “Light_init( );¥n” into an insertion destination file “/src/FW/init.c,” inserting a source code character string “Light_on( );¥n” into an insertion destination file “/src/FW/entry.c” and inserting source code character strings “Beeper_beep( );¥n” and Light_off( );¥n” into an insertion destination file “/src/FW/exit.c.” 
         [0061]    It should be further understood by those skilled in the art that although the foregoing description has been made on embodiments of the invention, the invention is not limited thereto and various changes and modifications may be made without departing from the spirit of the invention and the scope of the appended claims.