KR102300005B1 - Method and system for assisting software development using connection of graphic objects, each representing a software component - Google Patents

Abstract

Provided is a software development method which allows for manipulation of connections between software component representations and graphic objects. According to an embodiment of the disclosure, the software development method includes the steps of: displaying a first graphic object pointing to a first source object and a second graphic object pointing to a second source object in a unit design view of a plurality of views provided by program development software; and automatically modifying a source code so that a reference to the second source object is added to the first source object.

Description

A software development assist method and system using connection operation between each graphic object representing a software component

This publication relates to a software development assist method and system using connection manipulation between respective graphic objects representing software components. More particularly, it relates to a method and system for providing a program development environment that considers connection manipulation between software component expression graphic objects that can be provided in an integrated development environment (IDE) based on a graphic user interface (GUI) environment, etc. .

An integrated development environment (IDE) is software in which various elements such as coding, debugging, compilation, and distribution necessary in the program development process are integrated in order to increase developer productivity. The integrated development environment has evolved in the direction of providing a GUI-based interface. Examples of the integrated development environment include Eclipse, Visual Studio, and the like.

In the integrated development environment, it is necessary to provide a guide that enables developers with little programming experience to proceed easily. To this end, it is desirable to provide a function for maximally setting the basic frame of the code through an intuitive user input.

US Patent No. 7613599 US Patent Publication No. 2013-0086551

The technical task to be achieved through some embodiments of this publication is to set a prototype on the source code by reflecting the manipulation of the connection between each graphic object representing the software component on the source code. A software development assist method and system are provided.

The technical task to be achieved through some other embodiments of this publication is to give a new meaning to the manipulation of the connection between each graphic object representing the software component, and to develop software that reflects this meaning on the source code An assist method and system are provided.

A technical task to be achieved through some other embodiments of this publication is an actor corresponding to a hardware part performing a specific operation, and a method and system for assisting development of control software that operates through message transmission/reception between the actors is to provide

The technical task to be achieved through some other embodiments of the present disclosure is a method for providing an intuitive GUI assisting prototyping for control software operating in a machine such as a production facility, and software development providing the system An assist method and system are provided.

The technical task to be achieved through some other embodiments of this publication is to reflect the matter according to the GUI-based user input indicating the connection between the higher-level software components to the source code, and to It is to provide a software development assist method and a system for supporting hierarchical prototyping by reflecting matters according to a GUI-based user input indicating a connection between conceptual modules in the source code of the software component.

The technical problems of this publication are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

A software development method according to an embodiment of the present disclosure includes a first graphic object pointing to a first source object and a second graphic object pointing to a second source object in a unit design view among a plurality of views provided by program development software. displaying; and when a user input in the unit design view connecting the first graphic object and the second graphic object is input, the first source object includes a reference to the second source object. 1 may include automatically modifying the source code of the source object.

In an embodiment, the program development software includes a plurality of actors and a message transmitted and received between the plurality of actors as a component of an integrated development environment for developing a program for driving a machine. Environment; IDE), the first source entity may be a source entity implementing a first actor among the plurality of actors, and the second source entity may be a source entity implementing a second actor among the plurality of actors. have. In this case, the first actor and the second actor are a built-in actor provided by default by the program development software or a subclassing actor that subclasses the built-in actor, and the built-in actor is a receiver built-in actor Provide a message sending function that provides a message sending function to, wherein the source object of the built-in actor includes a reference pointing to an instance of the receiver built-in actor, and the step of modifying the source code includes: Thereafter, the method may include displaying a code input guide UI of the message sending function for sending a message from the first actor to the second actor on the code view of the first source object.

In addition, the software development method may include, in response to receiving a user input in the unit design view creating a new unit a first actor subclassed to include a reference pointing to an instance of the second actor, further displaying in the unit design view a fourth graphic object indicating a subclassing actor of one actor; and displaying a warning indication indicating that the second actor should be connected to the fourth graphic object in the unit design view. It may further include the step of displaying. In this case, in the step of displaying the warning indication on the unit design view, when a predetermined user input for the fourth graphic object is input, the type of the graphic object displayed in the unit design view is an actor and the name is the second actor and displaying, on the unit design view, a connection suggestion graphic display that proposes a graphic object that most matches the name of , as a slave graphic object candidate. Also, the displaying of the warning indication on the unit design view may include displaying the warning indication at a position adjacent to the fourth graphic object. In addition, the step of displaying the warning indication on the unit design view may include, in response to a predetermined user input for a warning indication indicating that the second actor should be connected to the fourth graphic object, a delete menu. displaying and in response to a user input of the removal menu selection, a warning mark indicating that the second actor should be connected to the fourth graphic object is removed, and the connection between the first graphic object and the second graphic object is removed updating and displaying the unit design view so that a graphic object is removed; and automatically modifying the source code so that a reference to the second source object automatically added to the first source object is deleted. have. In addition, the first actor is subclassed to further include a reference pointing to a third actor among the plurality of actors, and the step of displaying the warning indication in the unit design view includes the second actor and the second actor. 3 displaying a warning mark indicating that the actor should be connected to the fourth graphic object; and displaying an Add Members menu in response to receiving a predetermined user input for the fourth graphic object or the warning display. In response to receiving a user input for selecting the Add Members menu, updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object and modifying the source code so that the reference to the second actor and the reference to the third actor are automatically added to the source object of the fourth graphic object. In this case, the step of updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object may include, in the fourth graphic object, the newly created second graphic object. The method may include updating and displaying the unit design view so that the graphic object of the actor and the graphic object of the newly created third actor are connected. In addition, the step of updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object includes generating the unit design view in the fourth graphic object and in the unit design view. The method may include updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor previously created are connected to the unit design view. In addition, the first actor is subclassed to further include a reference to a source entity implementing a value structure initially composed of a predetermined set of kernel data including a first value of a first type and a second value of a second type. In response to receiving a user input for selecting the Add Members menu, the unit design view is updated and displayed so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object. The step of: updating the unit design view so that the newly created graphic object of the second actor and the newly created graphic object of the third actor are connected to the fourth graphic object; The method may include updating the unit design view so that the graphic object of the source entity implementing the value structure created in advance is further connected to the unit design view.

In some embodiments, the first source entity is a source entity that implements a first one of the plurality of actors, and the second source entity includes a first value of a first type and a second value of a second type. It is a source object that implements a value structure initially composed of a predetermined set of kernel data, wherein the displaying is included in the value structure in response to a user input in the unit design view that selects the second graphic object It may include displaying a property view for editing each value, type, or variable name.

In some embodiments, the automatically modifying the source code comprises: in response to a unit design storage input for reflecting user inputs in the unit design view being input, converting the source code so that the user inputs are collectively reflected It may include modifying the source code.

In some embodiments, the user input for the unit design view connecting the first graphic object and the second graphic object may include sequential selection of the first graphic object and the second graphic object. At this time, the user input to the unit design view connecting the first graphic object and the second graphic object is a sequential selection of the first graphic object and the second graphic object, and the sequential selection is and typing input of the reference name of the second source entity via a dialog that is automatically displayed in response to completion.

In some embodiments, the software development method may further include displaying a code view displaying the source code of the first source entity. In this case, the step of displaying the code view includes: displaying a reference to the second source object automatically added to the source code of the first source object to be visually distinguished from the source code input by the user; , in response to a predetermined user input for a reference to a second source object displayed to be visually distinct, displaying a unit design view in which a connection graphic object connecting the first graphic object and the second graphic object is highlighted. may include the step of

In some embodiments, the step of automatically modifying the source code includes adding a connection graphic object connecting the first graphic object and the second graphic object to the unit design view in response to the user input, the first graphic object and It may include displaying the second graphic object together. In this case, the software development method may further include, in response to a predetermined user input for the connected graphic object, displaying a code view displaying a reference to the automatically added second source object. .

In some embodiments, automatically modifying the source code comprises: automatically adding a reference to the second source object in a deactivated state to the first source object; displaying a connected graphic object in a first state connecting two graphic objects on the unit design view; It may include activating a reference to the object in the source code, and updating and displaying the connected graphic object in the first state to the connected graphic object in the second state.

In some embodiments, automatically modifying the source code comprises: automatically adding a reference to the second source object in a deactivated state to the first source object; displaying a connected graphic object in a first state connecting two graphic objects on the unit design view; Displaying a source code view displaying a reference to the object, and analyzing the source code modification related to the reference to the second source object through the source code view, and as a result of the analysis, the reference to the second source object is determined to be activated, updating and displaying the connected graphic object in the first state to the connected graphic object in the second state.

In some embodiments, the automatically modifying the source code may include displaying a connection graphic object connecting the first graphic object and the second graphic object on the unit design view. In this case, the step of displaying the connected graphic object on the unit design view may include displaying the connected graphic object in a linear form in which a part of the center is erased. In this case, the step of linearly displaying the connection graphic object in a form in which a part of the center is erased is an outgoing wireless connection formed in an area in which an outgoing connection graphic object of the first graphic object is connected to the first graphic object. In response to a selection user input for a region, the method may include displaying all outgoing connection graphic objects of the first graphic object in a linear form in which a part of the center is erased. In addition, the step of linearly displaying the connection graphic object in a form in which a part of the center is erased may include an incoming wireless region formed in a region in which an incoming connection graphic object of the second graphic object is connected to the second graphic object. In response to a selection user input for , displaying all incoming connection graphic objects of the second graphic object in a form in which a part of the center is erased linearly. In addition, the step of linearly displaying the connected graphic object in a form in which a part of the center is erased includes measuring the graphic object density of the unit design view, and based on the measured graphic object density, the connected graphic object The method may include determining whether to display the object in a linear form in which a part of the center is erased. In this case, the measuring of the graphic object density may include measuring the graphic object density of the connected graphic object. In addition, the step of linearly displaying the connected graphic object in a form in which a part of the center is erased includes measuring a density of a graphic object in a predetermined area based on a center point of the connected graphic object, and the measured graphic object The method may include determining whether to linearly display the connected graphic object in a form in which a part of the center is erased, based on the density.

In some embodiments, the software development method receives a user input in the unit design view that further connects one or more graphic objects and the first graphic object, wherein each graphic object corresponds to a source object one-to-one in response to receiving a user input for inserting two or more of the second graphic object and the one or more graphic objects into the first tie graphic object displayed in the unit design view, inserting the graphic object in the first tie removing the graphic object from the unit design view, and displaying information about the graphic object inserted into the first tie graphic object in the first tie graphic object or in a position adjacent to the first tie graphic object may include In this case, the step of automatically modifying the source code includes automatically modifying the source code so that a reference to the second source object and a reference to each source object corresponding to the one or more graphic objects are added to the first source object. may include a step of modifying At this time, the graphic object inserted into the first tie graphic object is removed from the unit design view, and information on the graphic object inserted into the first tie graphic object is stored inside the first tie graphic object or the first tie The displaying in the adjacent position of the graphic object may include further removing all of the slave graphic objects of the graphic object inserted into the first tie graphic object from the unit design view. Also, in the software development method, when a user input in the unit design view connecting a fifth graphic object pointing to a fifth source entity and the first tie graphic object is input, a reference to the second source entity and the The method may further include automatically modifying the source code so that a reference to each source object corresponding to one or more graphic objects is added to the fifth source object. The software development method includes, in response to a user input in the unit design view copying the first tie graphic object being input, a second tie graphic object that is a duplicate of the first tie graphic object in the unit design view. In response to receiving a predetermined user input for further displaying, the second tie graphic object or a warning display indicating omission of a slave object of the graphic object included in the second tie graphic object, an Add Members menu is displayed. and in response to receiving a user input for selecting the Add Members menu, generating a slave object connection missing in each graphic object included in the second tie graphic object. At this time, the step of creating a slave object connection missing in each graphic object included in the second tie graphic object includes creating a new slave object for each slave object and creating a slave object connection to the newly created slave object. Method 1, or when a graphic object previously created in the unit design view is connected as a slave object, but a graphic object of a type corresponding to the missing slave object connection is not previously created in the unit design view, a slave object is newly created, It may include a step performed by the second method of creating a slave object connection to the newly created slave object. In addition, the graphic object inserted into the first tie graphic object is removed from the unit design view, and information about the graphic object inserted into the first tie graphic object is stored in the first tie graphic object or the first tie graphic object. The step of displaying at the adjacent position of the object includes the steps of receiving a tie target master object for a duplicate slave graphic object connected to two or more master objects among graphic objects inserted into the first tie graphic object by a user input, and the first tie graphic object; 1 removing the graphic objects other than the duplicate slave graphic object among graphic objects inserted into the tie graphic object from the unit design view, and connecting graphic objects between the duplicate slave graphic objects and the tie target master object to the unit may include removing it from the design view.

A software development method according to another embodiment of the present disclosure is a method performed in a computing device to develop a program including a unit operating in a Finite State Machine (FSM) method, wherein a first state of the unit is obtained. Displaying a first graphic object pointing to and a second graphic object indicating a second state of the unit on an FSM view among a plurality of views provided by program development software, from the first graphic object to the second graphic object; automatically displaying a dialog for receiving a trigger message name and an action function name in response to a user input in the FSM view for creating a connection of the trigger message name and action function name input through the dialog and automatically adding the prototype of the action function to the source code of the unit using .

In some embodiments, the prototype of the action function may include the name of the first state and the name of the trigger message as parameters, and the return may be automatically described as the second state.

In some embodiments, the step of automatically displaying a dialog for receiving the input of the trigger message name and the action function name includes, in response to completion of input of the trigger message name and the action function name through the dialog, the first graphic object and The method may include further displaying an action function graphic object that connects between the second graphic objects. In this case, the software development method automatically generates a dialog for receiving a trigger message name in response to a user input in the FSM view that creates a connection from the first graphic object to the action function graphic object. and automatically updating the trigger message name included in the action function prototype in the source code of the unit to the trigger message name input through the dialog. In addition, the software development method includes: when a user input in the FSM view that creates a connection from the action function graphic object to a third graphic object indicating a third state of the unit is input, the action function prototype is The method may further include automatically updating an included return state to the third state.

A software development method according to another embodiment of the present disclosure is a computing method that provides an integrated development environment (IDE) for developing a driving program of a machine including a plurality of actors as components. A method performed in an apparatus, wherein when a user input indicating a connection from a first actor graphic object to a second actor graphic object is input, a reference to the second actor is added to the source of the first actor. automatically modifying the source code of , and when a user input indicating entry into a finite state machine (FSM) editor for the first actor is input, displaying an FSM edit view of the first actor; When a user input for generating a connection from a graphic object indicating a first state of the first actor to a graphic object indicating a second state of the first actor is input through a view, the first state is displayed in the first state. and automatically adding to the source code of the first actor a prototype of an action function performed when transitioning to the second state.

A software development method according to another embodiment of the present disclosure includes a unit design view of a first graphic object pointing to a first source object and a second graphic object pointing to a second source object among a plurality of views provided by program development software displaying the first graphic object, and when a user input in the unit design view connecting the first graphic object and the second graphic object is input, the first source object includes an instance of the second source object. 1 may include automatically modifying the source code of the source object.

1 is a configuration diagram of a software development system according to an embodiment of the present disclosure.
2 is a flowchart of a software development method according to another embodiment of the present disclosure.
3 is a schematic diagram of an exemplary machine that may be referred to when understanding some embodiments of the present disclosure.
4 is a diagram illustrating a unit design view and exemplary unit design results that may be presented in some embodiments of the present disclosure.
5 is a diagram illustrating exemplary screen feedback when there is a user input for a connection between graphic objects representing different source objects in some embodiments of this publication.
FIG. 6 is a diagram of an exemplary code view for explaining a result of automatically adding a source code prototype according to an exemplary unit design result of FIG. 4 .
FIG. 7 is a diagram of an exemplary code view for explaining that a code input guide UI is provided for a message transmission function called when a master object sends a message to a slave object according to the prototype addition result of FIG. 6 .
8 shows that in some embodiments of this publication, when a built-in actor creates a new unit using a subclassed subclassing actor, a warning indication indicating the omission of a slave object is displayed in the new unit It is a drawing of an exemplary unit design view for explanation.
9 is a diagram of an exemplary unit design view for explaining a subsequent operation that occurs when some slave objects are deleted using a warning indication indicating omission of a slave object in some embodiments of the present disclosure;
10 to 13 are diagrams of an exemplary unit design view for explaining that an auxiliary function capable of collectively eliminating omission of a slave object is provided in some embodiments of the present disclosure.
14 is a diagram of an exemplary property view that is provided so that each value belonging to a value structure of a unit of VariableType can be modified on a GUI in some embodiments of the present disclosure.
15 and 16 illustrate that, in some embodiments of the present disclosure, a prototype in an inactive state is added to the source code when there is a user input for a connection between graphic objects representing different source objects. drawings to do
FIG. 17 is a diagram for explaining that a connection graphic object may be drawn in a partially erased form in some embodiments of the present disclosure.
18 to 22 are diagrams for explaining that the unit design view provides a tie function in order to solve the complexity of the arrangement of graphic objects in the screen in some embodiments of the present disclosure.
23 is a flowchart of a software development method according to another embodiment of the present disclosure.
FIG. 24 is a diagram illustrating exemplary screen feedback when there is a user input for connection between different states in some embodiments of the software development method described using FIG. 23 .
25 is a diagram illustrating exemplary screen feedback when there is a user input for connection between a state and an action.
FIG. 26 is a diagram illustrating an updated FSM (Finite State Machine) diagram of an editing target unit according to a user input illustrated in FIG. 25 .
27 is a diagram illustrating exemplary screen feedback when there is a user input for a further connection between a state and an action.
28 is a diagram illustrating an updated FSM diagram of an editing target unit according to a user input illustrated in FIG. 27 .
29 is a diagram illustrating exemplary screen feedback when there is a user input that removes a trigger message between a state and an action.
30 is a diagram illustrating an exemplary FSM diagram in which a connection graphic object is visually distinguished and displayed according to a type of a trigger message between a state and an action.
31 is a hardware configuration diagram of a developer terminal or an IDE service server included in a software development system according to another embodiment of the present disclosure.

Hereinafter, embodiments of the present specification will be described in detail with reference to the accompanying drawings. Advantages and features of the embodiments of the present specification, and methods for achieving them, will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the technical spirit of the present invention is not limited to the following embodiments, but may be implemented in various different forms, and only the following embodiments complete the technical spirit of the present invention, and the embodiments of the present specification belong It is provided to fully inform those of ordinary skill in the art the scope of the present invention, and the technical spirit of the present invention is only defined by the scope of the claims.

In adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the embodiments of the present specification, if it is determined that a detailed description of a related known configuration or function may obscure the subject matter, the detailed description thereof will be omitted.

Unless otherwise defined, all terms (including technical and scientific terms) used in this specification may be used in the meaning commonly understood by those of ordinary skill in the art to which the embodiments of the present specification belong. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular. The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the embodiments of the present specification. As used herein, the singular also includes the plural unless specifically stated otherwise in the phrase.

In addition, in describing the components of the embodiments of the present specification, terms such as first and second may be used. These terms are only for distinguishing the component from other components, and the essence, order, or order of the component is not limited by the term. Where a component or software component is described as being “connected”, “coupled” or “connected” to another component or software component, that component may be directly connected or connected to the other component, but each component It should be understood that another element may be “connected”, “coupled” or “connected” between elements.

Hereinafter, some embodiments will be described in detail with reference to the accompanying drawings.

The configuration and operation of a software development system according to an embodiment of the present disclosure will be described with reference to FIG. 1 .

The software development system according to the present embodiment includes the IDE service server 10 and developer terminals 20-1 and 20-2 that can be connected to the IDE service server 10 through a network as shown in FIG. may include The software development system shown in FIG. 1 provides a server-based IDE, such as a cloud-based IDE. The software development system according to the present embodiment does not necessarily have to be a server-based IDE. E.g,

Another embodiment of this publication may be an IDE installed only on the developer terminals 20-1 and 20-2 (client-alone). Some technical ideas provided by the server-based IDE described with reference to the present embodiment are naturally applicable to the IDE installed only in the developer terminals 20-1 and 20-2. For example, the IDE may be an IDE for developing a facility control program for developing software running in the facility. In this case, the IDE service corresponding to the IDE service server 10 of FIG. 1 may be installed in the developer terminals 20 - 1 and 20 - 2 . It goes without saying that the various embodiments presented herein may also be applied to the IDE for facility control development.

The IDE service server 10 may be connected to the IDE storage 11 for storing the output of the development project, such as source code, through a network or an internal network (not shown). Also, the IDE service server 10 may transmit data of the IDE GUI including a plurality of views to the developer terminals 20 - 1 and 20 - 2 . The IDE GUI may include a code view, a unit design view, and a property view.

Among the plurality of views of the IDE GUI, the unit design view will be representatively described. The unit design view displays a first graphic object pointing to a first source object and a second graphic object pointing to a second source object.

The first source entity is for implementing a first component of the software to be developed, and the second source entity is for implementing a second component of the software to be developed, for example, the first source entity is the first source. It points to the source code of the file, and the second source object may point to the source code of the second source file. However, the first source entity and the second source entity are not necessarily recorded in different source files. For example, the first source entity and the second source entity may respectively point to source codes in different regions of one source file.

A software component of the present description may be understood as a software module responsible for each of a plurality of functional units required for the overall operation of the software. In this case, the software component may be composed of a plurality of functions executing a specific function and variables involved in the execution of the function.

In addition, the software component of the present description may be understood as a software module responsible for each of a plurality of structural units required for the overall operation of the software. In this case, the software component may be understood as a value structure composed of a plurality of values constituting a set because the software component has a common purpose.

Each such software component does not necessarily have to be produced as a separate binary. That is, each software component may be understood as an implementation recorded in an individual source entity for the implementation of different functional units.

The unit design view provides a user interface that receives a user input for connecting the first graphic object and the second graphic object. This user interface will preferably be a graphical user interface (GUI). For example, the graphical user interface may include a drag input from the first graphical object to the second graphical object and output of the feedback.

In some embodiments, when a connection user input in the unit design view connecting the first graphic object and the second graphic object is input, the IDE service server 10 is an instance of the second source object. may automatically modify the source code to be added to the first source object. That is, the IDE service server 10 receives a user input in which graphic objects of different source objects are connected in the unit design view, and instantiates any one of the two source objects inside the other source object. will be.

In some other embodiments, when a connection user input in the unit design view connecting the first graphic object and the second graphic object is input, the IDE service server 10 determines that the first source object is the second graphic object. You can also automatically modify the source code to include a reference to an instance of the source object.

In this case, the instance of the second source entity may be automatically created in a separate source entity that is neither the first source entity nor the second source entity. For example, the IDE service server 10 may automatically include a source code for instantiating instances of all units belonging to a project in a separate code file. That is, the IDE service server 10 automatically instantiates each graphic object created in the unit setting view, and connects user input in the unit design view that connects the first graphic object and the second graphic object. Upon input, the source code of the first source object may be automatically modified such that the first source object includes a reference pointing to an instance of the second source object.

In an embodiment in which an instance of the second source object is added to the first source object when a connection user input in the unit design view connecting the first graphic object and the second graphic object is input, the Instances of the second source entity are dependent on the first source entity. That is, the second graphic object becomes subordinate to the first graphic object. Accordingly, to reflect this dependency, the unit design view may express an indicator indicating that the second graphic object is dependent on the first graphic object, and the second graphic object is a graphic object other than the first graphic object. A point that cannot be a dependent object of an object can be expressed as feedback to user input. For example, in response to a user input indicating that the second graphical object is dependent on a third graphical object, the unit design view may provide error-generating feedback.

On the other hand, when a connection user input in the unit design view connecting the first graphic object and the second graphic object is input, the first source object includes a reference to an instance of the second source object In the resulting embodiment, the instances of each graphic object have a horizontal relationship. That is, the instance of each graphic object does not belong to the instance of another graphic object, and when a connection user input for two graphic objects is input, an instance of one graphic object includes a reference to an instance of another graphic object. By doing so, it becomes possible to modify the variable value of the referenced instance or call a method through the reference. In this case, a certain graphic object may be referenced by a plurality of other graphic objects.

Hereinafter, for convenience of understanding, when a connection user input in the unit design view connecting the first graphic object and the second graphic object is input, the first source object is an instance of the second source object ), some embodiments will be described on the assumption that the embodiment includes a reference to . However, it should be noted that the embodiments described herein are also applicable to an embodiment in which the first source object includes an instance of the second source object according to the connection user input.

In this description, a graphic object of a source object accessed through a reference inside another source object will be referred to as a slave object. Also, the graphic object of the source object accessed through the reference to the slave object will be referred to as a master object.

In the conventional GUI-based IDE, a user interface such as including a control object such as a button in a dialog is provided in a GUI design tool. However, this user interface includes the lower graphic object in the upper graphic object and not the connection between the graphic objects. Also, each of the upper graphic object and the lower graphic object does not point to a different source object. That is, in the embodiments of the present disclosure, the source object of each software component is expressed as a graphic object on the screen, the connection between the graphic objects is generated by a user input through the GUI, and the connection between these graphic objects is a slave to the master object. The technical idea reflected in the source code in the form of adding a reference to an object has not been presented in the conventional GUI-based IDE.

Also, for developers familiar with the GUI, it is much more intuitive to create a connection from the master object to the slave object than to directly declare a reference to the instance of the slave object in the source code of the master object. will be

That is, the embodiments of the present disclosure support to make reference to a slave object in a new way that was not previously available, and by this method, the time required for source code prototyping at the initial stage of the development project and the complexity of the work This can be greatly improved.

Meanwhile, the IDE service server 10 may automatically modify the source code immediately in response to the connection user input. In this case, since the connected user input is safely directly reflected in the source code, it is possible to safely preserve the work result from various errors. In addition, the IDE service server 10 may automatically modify the source code so that the source object connection in the final state is reflected when there is a storage user input for the modification of the unit design view. That is, the IDE service server 10 does not immediately perform automatic correction of the source code in response to the connection user input, but waits until there is a stored user input for the modifications of the unit design view, so that frequent source files are have the effect of restricting access to Each IDE GUI will be described in detail later with reference to some drawings.

Various operations of the IDE service server 10 may be understood in more detail with reference to some embodiments to be described later.

Hereinafter, a software development method according to another embodiment of the present disclosure will be described with reference to FIG. 2 . Hereinafter, in describing the method according to the present embodiment, description of the subject of each operation may be omitted, and in this case, it may be understood that the subject of the operation is a computing device. The computing device may be, for example, each of the developer terminals 20 - 1 and 20 - 2 described with reference to FIG. 1 . Also, the method according to the present embodiment may be divided and performed by a plurality of computing devices. For example, at least one of the IDE server 10 and the IDE storage 11 described with reference to FIG. 1 , and the respective developer terminals 20 - 1 and 20 of the online communication server 200 and the online communication device 100 . The method according to the present embodiment may be performed by collaboration of -2).

In step S101, the developer terminal receives the data for configuring the unit design view and displays the unit design view. The configuration of the unit design view and various user interfaces provided based on the unit design view will be described below with reference to the exemplary unit design view 50 illustrated in FIG. 4 .

In step S103, the developer terminal receives a user input for generating each unit to be displayed on the unit design view, and displays a graphic object indicating each generated unit on the unit design view. Illustratively, the embodiments of the present description may be implemented for the purpose of developing a driving program (or control program) of a machine.

In this case, the unit may be understood as a unit constituting the machine. For example, the unit may be understood as an example of the software component described above. In this case, the unit may be divided into an actor unit that performs a specific operation and corresponds to a specific hardware part of the machine, and a variable type unit that corresponds to the above-described value structure.

It will be further described with reference to FIG. 3 . Each of the actor units 31 , 32 , and 33 has an independent FSM (Finite State Machine)-based operation method, and for this, each of the actor units 31 , 32 , 33 has state information 31a , 32a , 33a . Also, the actor units 31 , 32 , and 33 may send and receive messages to each other. For this purpose, each of the actor units 31 , 32 , 33 has a message queue 31b , 32b , 33b . Although the message queues 31b, 32b, and 33b are illustrated as being implemented as first-in-first-out (FIFO) in FIG. 3, message queues implemented in other manners may be included in each unit. Also, the variable type unit includes the above-described value structure. The exemplary machine shown in FIG. 3 includes three actor units 31 , 32 , 33 and one variable type unit 34 . The developer will be able to finish basic prototyping of the machine by creating a connection between each unit through the unit design view.

Next, when a connection user input for connecting between the graphic objects is input (S105), a connection graphic object representing creation of a connection between graphic objects according to the connection user input is drawn (S107).

The connection user input may include sequential selection of a master graphic object and a slave graphic object. The connection user input at this time may be understood as intuitively expressing the direction of the arrow pointing to the slave graphic object from the master graphic object. Conversely, the connected user input may include sequential selection of a slave graphic object and a master graphic object. The connection user input at this time may be understood as intuitively expressing the direction of the arrow, which means that the slave graphic object enters the master graphic object. In some embodiments, the connection user input may further include a drag input between selection of two graphic objects. That is, an arrow connecting the master graphic object and the slave graphic object may be expressed as a drag input. Accordingly, the developer will be able to accept the connection user input similar to drawing an arrow from the master graphic object to the slave graphic object.

As described above, the connected user input may be immediately reflected in the source code, but may be reflected in the source code only when the save button on the unit design view is input (S109) as shown in FIG. (S111).

Next, the master unit having the slave object may be added as a custom unit rather than a built-in unit to a tool box area on the unit design view (S113). Accordingly, by selecting the master unit having the slave object in the custom unit area, it can be easily displayed as a new unit on the unit design view.

Next, tie-related user input is processed. The tie may be understood as a user interface for bundle management by including units of the same level in the tie unit in order to prevent screen visibility from falling as the number of units displayed in the unit design view increases. , which will be described later in detail with reference to FIGS. 18 to 22 .

Next, when a designated user input (eg, double click) for the actor unit is input, the FSM editor for the actor unit may be executed (S117). As described above, each actor unit operates in an FSM manner, and the FSM editor may be executed for editing the FSM diagram of the actor unit. The FSM editor also receives a user input for connection between graphic objects and the connection is reflected in the source code of the actor unit. It is similar to the point reflected by reference in the source code. Operations related to the execution of the FSM editor for the actor unit will be described later in detail with reference to FIGS. 23 to 26 .

Hereinafter, various examples of a user input for a unit design view and feedback corresponding thereto in relation to the software development method according to the present embodiment will be described with reference to FIGS. 4 to 22 .

4 shows an exemplary unit design view 50 . On the right side, a panel on which graphic objects of units and connection graphic objects between each unit are drawn may be displayed, and on the left side, a tool box 40 may be displayed. The tool box 40 may include buttons 41 , 42 , 43 related to connection, an arrangement area 44 of a button for creating a custom object, and an arrangement area 45 of a button for creating a built-in object. have. The button arrangement area 45 for creating a built-in object may include a button arrangement area 46 for creating an actor unit and a button arrangement area 47 for creating a variable type unit.

Each of the three units 35, 36, 37 shown in FIG. 4 is created as a new unit using a rich actor among the built-in actor objects 46, and after connecting with other actor units and variable type units (Axis), As the modifications of the unit design view are saved through the save button 52 , it may be understood that each is registered as a custom object 44 . The reason that each of the three units 35 , 36 , and 37 are all registered as the custom object 44 is because all three units are master objects.

An operation when there is a connection user input between graphic objects of each unit will be described with reference to FIG. 5 . The developer may input the connection user input by clicking (35-1) on the Shoulder actor unit 35 and then dragging (35-2) to the Elbow actor unit 36. In response to the drag 35-2 being input to the Elbow actor unit 36, a dialog 35-3 for receiving the reference name 35-4 for the Elbow actor unit may be displayed. The reference name input through the dialog 35-3 will be written as the name of the reference when a reference to the instance of the Elbow actor unit 36 is automatically added on the source object of the Shoulder actor unit 35.

By inputting a designated user input such as double-clicking the connection graphic object 38-1, 38-2, 38-3 in the unit design view 50, the developer views the code view corresponding to the double-clicked connection graphic object can be set to automatically switch. For example, when the connection graphic object connecting the Elbow actor unit 36 as a master object and the Hand actor unit 37 as a slave object is double-clicked (38-2a), the code view 60 of FIG. 6 is activated status, and the cursor will be located on the reference code 61a of the Hand actor unit.

6 shows an exemplary code view 60 for explaining the result of the unit design view of FIG. 4 reflected in the source code. Each of the three units 35 , 36 , 37 of FIG. 4 may correspond to a source entity of an individual source file. 6 is a representation of some of the source entities of the Elbow actor unit 36 among them. As shown in Fig. 4, the Elbow actor unit 36 is connected with three slave objects. The three slave objects are the Shoulder actor unit (35), the Hand actor unit (37) and the Axis unit which is a variable type unit. 6 shows that three slave objects are referenced 61 inside the source object of the Elbow actor unit 36 .

Meanwhile, as shown in FIG. 6 , the source code related to the automatic reference 61 may be displayed to be visually distinguished from other source codes. For example, as shown in FIG. 6 , the source code related to the automatic reference 61 may be underlined 61a , 61b , 61c . Developers can check the unit design view in which the linked graphic object corresponding to the clicked referenced (61) related source code is highlighted by viewing the source code related to the visually distinct automatic reference (61) in the code view and clicking the underlined part. will be able As a result, the developer can easily understand the master and slave relationship between each unit while examining the source code in the code view.

The built-in actor provided by default has a message sending function implemented. Therefore, the built-in actor is a slave built-in actor referenced to the source object of the built-in actor, and can transmit a message using the message sending function. An actor unit created by subclassing a built-in actor can also send a message to a slave actor using the message sending function.

7 shows a code view of the source object of the Elbow actor unit 36 . Since the source object of the Elbow actor includes a reference 61a to the instance of the Hand actor, it can be seen that the Elbow actor can send a message to the Hand actor by using the message sending function 62 . In addition, a code input guide UI to help input a code corresponding to the prototype of the message sending function 62 may be displayed based on the position of the cursor 64 . For example, FIG. 7 illustrates a code input guide UI 63 indicating that the second parameter of the message sending function 62 is a void type message.

It will be described with reference to FIG. 8 . By clicking (44-1) the Hand actor among the custom actors 44, and specifying the location of the new graphic object of the Hand actor (37b), the subclassing actor 37-1 of the Hand actor is displayed in the unit design view. can be added. By the way, the Hand actor 37 has an Elbow actor 36 and an Axis variable type unit as a slave object. Accordingly, the subclassing actor 37-1 of the Hand actor requires connection with two slave objects. In order to prevent the connection with the slave object from being missed, a warning mark 37a indicating that the two slave objects should be connected may be displayed on the subclassing actor 37-1 of the Hand actor.

The warning display 37a may be displayed in a position adjacent to the target graphic object 37-1, or may be displayed together with information of the target graphic object in a designated warning display area.

The warning display 37a may include a list of reference names and unit types of slave objects for which connection is missing.

On the other hand, in order to help developers in the convenience of connecting the missing slave object, the unit type is the same as the connection missing slave object included in the warning display 37a among the graphic objects displayed in the unit design view, and the name of the unit is the connection missing slave Connection proposal graphics 37c and 37d that suggest a graphic object most similar to the reference name of the object as a slave graphic object candidate may be displayed. These proposals are inspired by the fact that developers mostly use a slightly modified version of the target unit's name as the name of the reference. For example, the reference name of the Hand actor unit 37 of the Elbow actor unit 36 is actorHand. ' indicates that the 'Hand' part overlaps.

After checking the connection suggestion graphics 37c and 37d, the developer may actually input a connection user input in the same way as the connection suggestion graphics 37c and 37d if it meets his/her intention.

The user input for displaying the connection suggestion graphic is, for example, when there is a click 37b on the graphic object of the subclassing actor 37-1 of the Hand actor or a long click input for the warning display 37a, Connection suggestion graphics 37c and 37d may be displayed.

Meanwhile, the developer may delete at least some of the connection missing slave objects included in the warning display 37a. For example, the developer determines that the reference name 'actorElbow' included in the warning display 37a is unnecessary, and the delete button 37e displayed by inputting a predefined user input such as a right-click on 'actorElbow'. you will be able to press However, if the subclassing actor 37-1 of the Hand actor does not need 'actorElbow' as a slave object, it will mean that the Hand actor 37 also does not need 'actorElbow' as a slave object. Therefore, when the delete button 37e is pressed, 'actorElbow' is not only deleted from the warning display 37a, but also a connection graphic object 38-2 that connects the Elbow actor 36 as a slave object of the Hand actor 37 ) will also be deleted automatically. FIG. 9 shows the unit design view updated as a result of pressing the delete button 37e of FIG. 8 . In this way, memory can be effectively prevented from being meaninglessly wasted by unnecessary reference variables remaining in the source object of the unit.

When a plurality of missing connection slave objects are included in the warning display 37a, it may take a lot of time to re-create the missing connection with the slave object. In order to reduce such time consumption, a function for automatically creating a connection with a missing connection slave object may be provided. It will be described with reference to FIG. 10 . The Add Members menu 37g may be included in the pop-up menu 37f displayed for the target unit 37-1 of the warning display 37a, and when the Add Members menu 37g is selected, the warning display 37a is displayed. A connection with an embedded missing connection slave object can be created automatically.

When the Add Members menu 37g function is executed, in some embodiments a new unit may be created, and a connection between the created new unit and the target unit 37-1 of the warning display 37a may be automatically created. In this case, as shown in FIG. 11, a subclassing actor of the Elbow actor unit is newly created (36-1), and the Axis variable type unit is also newly created (39-1), and two connected graphic objects (37i, 37h) may be added.

When the Add Members menu 37g function is executed, in some other embodiments, a unit corresponding to the missing connection slave object is identified from among the units previously created in the unit design view, and the identified unit and the target of the warning display 37a The connection of the unit 37 - 1 may be created automatically. That is, a new unit is not unconditionally created when the Add Members function is executed, but a new unit is created when the unit corresponding to the missing connection slave object is not created in the unit design view.

In order to find a unit corresponding to the missing connection slave object in the unit design view, a logic to find a unit whose name is most similar to the reference name of the missing connection slave object while matching the connection missing slave object and the unit type is performed. will be able In this case, as shown in Fig. 12, as slave objects of the target unit 37-1 of the warning display 37a, the Elbow actor unit 36 and the Axis variable type unit (36) that were previously created in the unit design view ( 39) will be identified, and connection graphic objects 37k, 37j will be created for the two identified slave objects.

When the Add Members menu (37g) function is executed, in some embodiments, depending on the unit type of the missing connection slave object, it is determined whether to create a new slave object or connect to a unit previously created in the unit design view. can be decided. That is, if the unit type of the missing connection slave object is an actor unit, a new slave object is created, and if the unit type of the connection missing slave object is a variable type, it will be connected to the unit previously created in the unit design view. In this case, as shown in FIG. 13 , as a slave object of the target unit 37-1 of the warning display 37a, the Axis variable type unit 39 that was previously created in the unit design view is identified, and Elbow A subclassing actor of the actor unit is newly created (36-1), and the connection graphic objects 37i and 37j for the Axis variable type unit 39 and the Elbow subclassing actor unit 36-1 are created. will be.

14 is a diagram of an exemplary property view that is provided so that each value belonging to a value structure of a unit of VariableType can be modified on a GUI in some embodiments of the present disclosure. So far, when a connection between a master actor unit and a slave actor unit is created according to user input, a reference pointing to an instance of the slave actor unit is automatically added to the source object of the master actor unit, so that intuitive reference is codeless. less) method was mainly explained.

However, in the unit design view, not only the connection between the actor units may be created, but also the connection between the actor unit and the variable type unit may be created. As described above, the variable type unit includes a value structure including one or more values, and the value of the variable type unit can be modified in a codeless manner through the property view as shown in FIG. 14 . Some embodiments of this publication are dragged from the graphic object of the master actor unit included in the unit design view to the graphic object of the variable type unit in order to reference the variable type unit that can freely modify its value in a codeless manner. It provides convenience of operation that only needs to be input.

In some embodiments of this publication, it is described that a prototype in an inactive state is added to the source code when there is a user input for a connection between graphic objects representing different source objects. In the present embodiment, even if there is a user input for connection between graphic objects representing different source objects, the source code is modified through additional verification, so in the process of adding a reference pointing to an instance of a slave object to the source object of the master object It has the effect of preventing mistakes or errors that may occur in advance.

It will be described with reference to FIG. 15 . In an embodiment, even if there is a user input connecting the first graphic object and the second graphic object, the graphic object of the connection may be displayed in the unit design view in a deactivated state. In addition, referenced code in a deactivated state can be inserted into the source object of the master object. The referenced code in the inactive state may point to the commented code. The first connected graphic object 38-4 and the second connected graphic object 38-5 of FIG. 15 are connected graphic objects displayed in an inactive state. The connected graphic object in the deactivated state is displayed to be visually distinguished from the connected graphic object in the activated state. In addition, deactivated reference code 61a and 61b corresponding to the connected graphic object in the deactivated state is shown in FIG. 16 .

The developer clicks (38-4a) a connection graphic object to be activated among inactive connection graphic objects on the screen of the unit design view 50 so that the activation button 38-4b is displayed, and the activation button 38-4b ) to activate the deactivated connection graphic object, and the deactivated reference code 61a, 61b may also be activated. In some embodiments, the inactive connection graphic object is activated by long-clicking or right-clicking the connection graphic object, and the deactivated reference code (61a, 61b) may be activated.

In one embodiment, when the activation button 38-4b is pressed, the activation of the inactive connection graphic object and also the activation of the inactive referenced code 61a, 61b may be performed automatically. The deactivated referencing code 61a, 61b may be activated, for example by deleting the annotation marks 61a-1, 61b-1.

In another embodiment, when the activation button 38-4b is pressed, a source code view may be displayed in which the deactivated referenced codes 61a, 61b are displayed. By displaying the source code view, the developer will be able to check whether the referenced code has been written as desired. When it is determined that there is no problem as a result of the check, the developer may activate the referenced code by directly modifying the deactivated referenced code 61a and 61b through the source code view. During this process, the developer will be able to modify the instance name. Next, the modification of the deactivated referenced code 61a, 61b through the source code view can be analyzed. As a result of the analysis, when it is determined that the inactive referenced codes 61a and 61b are activated due to deletion of comments, etc., the deactivated connection graphic object will be updated to an activated state.

In the embodiment described with reference to FIGS. 15 to 16 , in the process of adding a user input for activating the connection graphic object, the developer will naturally reexamine whether the connection between units has been accurately matched for the purpose of reference. In this process, mistakes or errors that may occur in the process of adding a reference can be prevented in advance.

Next, some embodiments will be described with reference to FIG. 17 . The connection graphic object may have a linear shape. In order to solve the difficulty of accurately grasping the connection relationship between the master unit object and the slave unit object in a situation where a large number of connection graphic objects are displayed in the unit design view, the connection graphic object may be drawn in a partially erased form.

In order to change the connection graphic object to a partially erased form, an outgoing connection graphic object of the master graphic object responds to a selection user input for the outgoing wireless region 80 formed in the region connected to the first graphic object Accordingly, all outgoing connection graphic objects of the master graphic object may be displayed linearly in a form in which a part of the center is erased ( 82 ).

In addition, a selection user input may be input to the area 84 immediately before deletion of the connected graphic object in order to change the partially erased connected graphic object to a normal form ( 83 ).

In addition, in order to change the connection graphic object to a partially erased form, a selection user input for the incoming wireless region 85 formed in the region where the incoming connection graphic object of the slave graphic object is connected to the second graphic object In response, all incoming connection graphic objects of the slave graphic object may be displayed linearly in a form in which a part of the center is erased ( 86 ).

Also, in some embodiments, a change between a normal shape and a partially erased shape of the connected graphic object may be performed automatically. This change may be performed based on the graphic object density of the unit design view. For example, when the density of the graphic object of the unit design view exceeds the reference value, the connected graphic object is automatically changed to a partially erased form, and when the density is less than the reference value, the connected graphic object is automatically changed to the normal form . The density of the graphic object may indicate the density of the connected graphic object. Also, in some embodiments, the graphic object density may not be measured globally in the unit design view, but may be measured in a predetermined area based on a center point of a connected graphic object. In this case, it is possible to obtain the effect that the connected graphic object is automatically displayed in a partially erased form where the density of the connected graphic object is high, and the connected graphic object is displayed in a normal form where the density of the connected graphic object is not high.

Next, some embodiments of the tie function will be described with reference to FIGS. 18 to 22 .

The tie function simplifies unit placement in the unit design view by including multiple units within one tie graphic object. Accordingly, the effect of increasing visibility may be obtained.

It will be described with reference to FIG. 18 . When a user input 43-1 of clicking the tie button 43 is input, and a user input designating an arrangement position of the tie graphic object is input, the tie graphic object 90 is displayed in the unit design view 50 . The tie graphic object 90 in the initial state is in an empty state. The two slave actor units of the elbow actor unit (36), the shoulder actor unit (35) and the hand actor unit (37) are selected (35-5, 37-2) and drag input to the tie graphic object (90) (35- 6, 37-3) will be inserted into the tie graphic object 90 by being input.

The shoulder actor unit (35) and the hand actor unit (37) can be inserted together in the tie graphic object (90), the shoulder actor unit (35) and the hand actor unit (37) are both of the elbow actor unit (36). Because it is a slave object. Both shoulder actor unit (35) and hand actor unit (37) are directly connected with elbow actor unit (36), so shoulder actor unit (35) and hand actor unit (37) have a relationship to elbow actor unit (36). It can be expressed that the depth is the same in . In other words, the shoulder actor unit 35 and the hand actor unit 37 can be inserted together in the tie graphic object 90, the depth of the shoulder actor unit 35 and the hand actor unit 37 is because it is the same At this time, the shoulder actor unit (35) and the hand actor unit (37) have the same depth with respect to the elbow actor unit (36), so the master object of the tie graphic object (90) is the elbow actor unit (36). will be

FIG. 19 shows the update result of the unit design view after the tie function related operation in FIG. 18 is completed. Reference names and unit types for the Elbow actor unit 36 of the inserted units may be displayed inside the tie graphic object 90 . In this way, it will be possible to identify which slave objects are tied. Since the Axis variable type unit, which is another slave object of the Elbow actor unit 36, is not inserted into the tie graphic object 90, the connection graphic object 38-3 between the Elbow actor unit 36 and the Axis variable type unit. It can be seen that is maintained as it is.

Meanwhile, FIG. 20 shows that a unit 91 other than the master object 36 of the tie graphic object 90 can also connect the tie graphic object 90 as a slave object 92 . For example, to create a new node by subclassing a Rich Actor among the built-in units, the developer clicks the Create Rich Actor button (46-1) and enters the name of the unit as 'Actor_X' to view the unit design view. You will be able to create it as a new unit at (50).

When the Actor_X unit 91 must have both a reference pointing to an instance of the Shoulder unit and a reference pointing to an instance of the Hand unit, just by dragging connection 92 to the tie graphic object 90, the Actor_X unit 91 is Inside the source object, both the reference of the Shoulder unit and the reference of the Hand unit will be added automatically. A statement to open the source file of the Actor_X unit 91, find the constructor of the class of the Actor_X unit 91 and add a reference pointing to an instance of the Shoulder unit, and a statement to add a reference pointing to an instance of the Hand unit (statement) ), it is possible to significantly reduce input traffic compared to the conventional IDE, which had to type all of them.

Of course, in some embodiments, the number of master objects that can be linked to the tie graphic object 90 may be limited to one. In this case, the change in the values of the units included in the tie graphic object 90 is referenced in the source object of the plurality of master objects, thereby preventing a result unintended by the developer from occurring. Also, in some embodiments, the number of master objects that can be connected may be determined according to the tie graphic object 90 . For example, the number of master objects that can be connected according to the tie graphic object 90 may be limited to one, or there may be no limit on the number of master objects that can be connected. For example, if the tie graphic object 90 includes an actor unit, the number of master objects that can be connected is limited to one, and if the tie graphic object 90 does not include an actor unit, the number of master objects that can be connected is limited there may not be

It will be described with reference to FIG. 21 . In some embodiments, DEEP CLONE may be performed on the tie graphic object 90 . For example, when a predetermined user input (for example, a right-click of a mouse) for the tie graphic object 90 is input, the deep duplicate button 93 may be displayed at a position adjacent to the tie graphic object 90 . . As a result of the deep duplicate button 93 being pressed, the duplicated tie graphic object 95 will be displayed. When the Actor_X unit 91 connects the original tie graphic object 90 as a slave object, it shares the Shoulder actor unit and the Hand actor unit as slave objects with the Elbow unit 36, while the Actor_X unit 91 connects the cloned tie. If the graphic object 95 is connected as a slave object, the Actor_X unit 91 will have its own reference of the Shoulder actor unit and the reference of the Hand actor unit. This can be understood as a result of performing deep cloning (DEEP CLONE) that duplicates even the referenced object.

A case in which a slave object connected to a plurality of master objects is inserted into a tie graphic object will be described with reference to FIG. 22 . In a situation where the Variable type unit 99 is connected to the two master objects 100 and 101, when a user input 103 for inserting the Variable type unit 99 into the tie graphic object 102 is input, the tie graphic object A dialog 103-1 for designating a master object of the Variable type unit 99 inserted in 102 and a checkbox of the master object may be displayed. The situation described above is shown at the top of FIG. 22 .

A change in the case where Actor_Y 101 is designated as the master object of the Variable type unit 99 inserted into the tie graphic object is shown at the bottom of FIG. 22 . As the Variable type unit 99 is inserted into the tie graphic object, the connection graphic object between the Variable type unit 99 and the Actor_Y 101 designated as its parent object will be removed. On the other hand, the Variable type unit 99 will remain intact despite insertion into the tie graphic object. This is because the master/slave relationship between the Actor_X 100 and the Variable type unit 99 is maintained as it is.

Up to now, embodiments related to a tie function have been described with reference to FIGS. 18 to 22 . According to the above-described tie function-related embodiments, all units having the same depth with respect to the master object may be inserted into the tie object. Alternatively, in some other embodiments related to the tie function, the type of unit that can be inserted into the tie object may be limited. For example, an actor type unit cannot be inserted into a tie object, but only a Variable type unit can be inserted. In this case, the nature of the tie function may be limited for the purpose of bundling various values. That is, when the actor unit has various variable type units as slave objects, the variable type units referenced by the actor unit can be intuitively understood by binding and displaying the variable type units as a tie object. In this case, when an actor-type unit is inserted into a tie object, feedback indicating an error may be displayed. This will prevent developers from accidentally tying actors.

Next, a software development method according to another embodiment of the present disclosure will be described with reference to FIG. 23 . 23 presents a series of operations that may be executed after the FSM editor for the actor unit described with reference to FIG. 2 is executed. In response to a predetermined user input (eg, left double-click) for a graphic object of an actor unit shown in the above-described unit design view, an FSM view for FSM editing for the actor unit is displayed (S119) ). Next, similar to the unit design view, a user input for generating each state is received, and a graphic object of each state is displayed on the FSM view (S121).

Each operation shown in FIG. 23 is not necessarily performed after each operation of FIG. 2 is performed. That is, the method of FIG. 23 may be independently performed. In this case, the method of FIG. 23 may be understood as a method of developing a program including a unit operating in the FSM method.

As already explained, each actor unit created on the unit design view can itself be understood as an individual FSM machine. Accordingly, it may be understood that different actor units have their own FSM diagrams.

A developer can design a machine by arranging a plurality of units in the unit design view and defining a master/slave relationship between each unit. It has been explained that a reference pointing to an instance of the source object of the slave unit is automatically declared inside the source object of the master unit by simply designating it through the user input to connect.

That is, it may be understood that the connection between units included in the machine results in automatic modification of the source entity. In FIG. 23, the scope is further narrowed to explain that the connection between modules included in the actor unit included in the machine results in automatic modification of the source entity. As described above, the actor unit operates based on FSM, and the connection between modules included in the actor unit is a connection between each state included in the state diagram of the actor unit, or different from the state in a specific state. It may be a connection between action functions that are performed when transitioning to a state.

When a connection user input between the first state and the second state is input in the FSM view (S123), a dialog for receiving the name of the trigger message and the name of the action function is automatically displayed (S125). Referring to FIG. 24 , when the selection user input 104 for the graphic object 103 in the first state and the drag user input 105 to the graphic object 106 in the second state are input, a trigger message is generated in response thereto. A dialog 107 for inputting a name and an action function name is automatically displayed. When the name of the trigger message and the name of the action function are input through the dialog 107, a prototype of the action function is automatically generated using the name of the trigger message and the name of the action function, and the prototype is the source code of the actor unit will be automatically added to (S128), and the graphic object of the action function will be automatically added to the FSM view.

In addition, as shown in FIG. 25 , when a selection user input 108 for the graphic object 103 in the first state and a drag user input 109 to the graphic object 110 of an action function are input, as a response A dialog 107 for receiving the name of the trigger message is automatically displayed. When the name of the trigger message is input through the dialog 107, the prototype of the action function will be automatically updated using the name of the trigger message.

In addition, when the selection user input 111 for the graphic object 110 of the action function and the drag user input 112 to the graphic object 113 in the third state are input, the return state of the action function is automatically changed to the first state. 3 will be updated with status.

FIG. 26 shows the result of updating the state diagram of the actor unit as a result of FSM view manipulation of FIG. 25 . On the other hand, in the state diagram situation of FIG. 26, when the developer inputs an additional input for state transition indicating transition to state 2 when the MsgBegin message is generated in state 1, when the MsgBegin message is generated in state 1 Since the existing graphic object 110 of the AcMid action function to be executed already exists, only the graphic object (not shown) connected from the existing graphic object 110 to the graphic object 106 of the state 2 is additionally displayed. In this way, overlapping display of graphic objects is prevented, thereby preventing developer confusion and wasting space in the FSM view.

In some embodiments, a state diagram may be created that includes transitions to a plurality of states after performing an action. At this time, as shown in FIG. 27 , a predetermined user input for adding a destination state (for example, clicking the shift key and clicking a mouse button at the same time) 114 is input to the graphic object 110 of the action function, and When a user input (eg, mouse drag) 115 designating the destination state 106 to be added is further inputted, the graphic object 110 of the action function and the additional destination state 106 as shown in FIG. 28 are further inputted. A connection graphic object 115 between them may be displayed. However, immediately after the graphic object 110 of the action function and the additional destination state 106 are connected, the return to the additional destination state 106 would not be included in the statement of the action function. To prevent the developer from missing coding the action function for return to an additional destination state 106 , a warning indication 116 indicating a mismatch between the state diagram and the source code is displayed in the graphical object 110 of the action function. can be

Another embodiment is described in which a warning indication indicating a mismatch between the FSM view and the source code is displayed. Referring to FIG. 29 , a user input for deleting ( 119 ) a trigger message generated to execute an action function in state 1 may be input. According to this deletion, the condition for executing the action function in state 1 is missing. In order to notify the omission of the trigger message, a warning display 118 indicating the omission of the trigger message may be displayed in the graphic object 103 in the state 1 to the connection graphic object connecting the action function graphic object 110 . Of course, even if a trigger message is not generated in a specific state, a bypass situation that automatically changes to another state may exist. For example, as shown in FIG. 30 , the graphic object 103 of the state 1 and the graphic object 110 of the action function may be connected by a connection graphic object 120 having a dotted line shape. When the developer sees the connection graphic object 120 of the dotted line shape, it can be intuitively understood that state 1 is naturally transitioned to state 2 or state 3 without generating a separate message.

As described with reference to FIGS. 27 to 30, a mismatch may occur between the updated state diagram and the source code prototype according to automatic source code modification by various manipulations on the FSM view. When generated, the FSM view according to embodiments of the present disclosure displays a warning indication adjacent to the related graphic object, thereby preventing developer's mistakes.

The manipulation of the FSM view will be repeated until the FSM view is terminated (S130).

When the method including each operation described through the flowcharts of FIGS. 2 and 23 is implemented, matters according to the GUI-based user input indicating the connection between the software components of the higher concept are reflected in the source code, , it will be possible to obtain the effect of supporting hierarchical prototyping by reflecting the matter according to the GUI-based user input indicating the connection between sub-concept modules within a specific software component to the source code of the software component.

The technical idea of the present disclosure described with reference to FIGS. 1 to 30 may be implemented as computer-readable codes on a computer-readable medium. The computer-readable recording medium may be, for example, a removable recording medium (CD, DVD, Blu-ray disk, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-equipped hard disk). can The computer program recorded in the computer-readable recording medium may be transmitted to another computing device through a network such as the Internet and installed in the other computing device, thereby being used in the other computing device.

Hereinafter, a hardware configuration of an exemplary computing device according to some embodiments of the present disclosure will be described with reference to FIG. 31 . The computing device described with reference to FIG. 31 may be, for example, a hardware configuration of the developer terminal or the IDE service server described with reference to FIG. 1 .

31 is an exemplary hardware configuration diagram that may implement a computing device in various embodiments of the present disclosure. The computing device 1000 includes one or more processors 1100, a system bus 1600, a communication interface 1200, and a memory 1400 for loading a computer program 1500 performed by the processor 1100; It may include a storage 1300 for storing the computer program 1500 .

The processor 1100 controls the overall operation of each component of the computing device 1000 . The processor 1100 includes at least one of a central processing unit (CPU), a micro processor unit (MPU), a micro controller unit (MCU), a graphic processing unit (GPU), or any type of processor well known in the art. may be included. Also, the processor 1100 may perform an operation on at least one application or program for executing the method/operation according to various embodiments of the present disclosure. The computing device 1000 may include two or more processors.

The memory 1400 stores various data, commands, and/or information. The memory 1400 may load one or more computer programs 1500 from the storage 1300 to execute methods/operations according to various embodiments of the present disclosure. An example of the memory 1400 may be a RAM, but is not limited thereto. The system bus 1600 provides a communication function between components of the computing device 1000 .

The system bus 1600 may be implemented as various types of buses, such as an address bus, a data bus, and a control bus. The communication interface 1200 supports wired/wireless Internet communication of the computing device 1000 . The communication interface 1200 may support various communication methods other than Internet communication. To this end, the communication interface 1200 may be configured to include a communication module well known in the art. The storage 1300 may non-temporarily store one or more computer programs 1500 . The storage 1300 may include a non-volatile memory such as a flash memory, a hard disk, a removable disk, or any type of computer-readable recording medium well known in the art.

The computer program 1500 may include one or more instructions in which methods/operations according to various embodiments of the present invention are implemented. When the computer program 1500 is loaded into the memory 1400 , the processor 1100 may execute the one or more instructions to perform methods/operations according to various embodiments of the present disclosure.

The exemplary computer program 1500 includes instructions for displaying a first graphic object pointing to a first source object and a second graphic object pointing to a second source object in a unit design view of a plurality of views provided by the program development software; When a user input in the unit design view connecting the first graphic object and the second graphic object is input, the source code is automatically added so that a reference pointing to an instance of the second source object is added to the first source object. Instruction for modifying, and displaying a first graphic object indicating a first state of the unit and a second graphic object indicating a second state of the unit in an FSM view among a plurality of views provided by the program development software In response to a user input in the FSM view that creates an instruction and a connection from the first graphic object to the second graphic object, automatically displaying a dialog for receiving a trigger message name and an action function name It may include at least a part of instructions and instructions for automatically adding the prototype of the action function to the source code of the unit using the trigger message name and the action function name input through the dialog.

Another exemplary computer program 1500 is, when a user input indicating a connection from a first actor graphic object to a second actor graphic object is input, a reference pointing to an instance of the second actor is added to the source of the first actor An instruction for automatically modifying the source code of the first actor so as to be possible, and an instruction for displaying the FSM edit view of the first actor when a user input indicating entry into the FSM (Finite State Machine) editor for the first actor is input And, when a user input for creating a connection from a graphic object indicating a first state of the first actor to a graphic object indicating a second state of the first actor is input through the FSM edit view, the second The method may include at least a part of instructions for automatically adding a prototype of an action function to be performed when transitioning from the first state to the second state to the source code of the first actor.

Although the embodiments of the present specification have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the embodiments of the present specification pertain can change the specific embodiments of the present specification without changing the technical spirit or essential features. It can be understood that it can also be implemented in a form. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent range should be interpreted as being included in the scope of the technical ideas defined by the present invention.

Claims (37)

A method performed on a computing device, comprising:
displaying the first graphic object pointing to the first source object and the second graphic object pointing to the second source object on a unit design view among a plurality of views provided by the program development software; and
When a user input in the unit design view connecting the first graphic object and the second graphic object is input, the source of the first source object is such that the first source object includes a reference to the second source object. including the step of automatically correcting the code;
How to develop software. The method of claim 1,
The program development software,
It is an integrated development environment (IDE) for developing a driving program of a machine including a plurality of actors and messages transmitted and received between the plurality of actors as components,
The first source entity is a source entity that implements a first actor among the plurality of actors,
The second source entity is a source entity that implements a second actor among the plurality of actors,
How to develop software. 3. The method of claim 2,
The first actor and the second actor are a built-in actor provided by default by the program development software or a subclassing actor that subclasses the built-in actor, and the built-in actor is a message to a receiver built-in actor Provide a message sending function that provides a sending function, wherein the source object of the built-in actor includes a reference pointing to an instance of the receiver built-in actor,
The step of modifying the source code is,
After the source code is modified, displaying a code input guide UI of the message sending function for sending a message from the first actor to the second actor in a code view of the first source object,
How to develop software. 3. The method of claim 2,
In response to receiving user input in the unit design view creating a new unit of a first actor subclassed to include a reference pointing to an instance of the second actor, subclassing an actor of the first actor further displaying a pointing fourth graphic object on the unit design view; and
Displaying, in the unit design view, a warning indication indicating that the second actor should be connected to the fourth graphic object;
How to develop software. 5. The method of claim 4,
Displaying the warning indication on the unit design view comprises:
When a predetermined user input for the fourth graphic object is input, a graphic object whose type is an actor and whose name most closely matches the name of the second actor among graphic objects displayed in the unit design view is suggested as a slave graphic object candidate displaying a connection suggestion graphical representation in the unit design view;
How to develop software. 5. The method of claim 4,
Displaying the warning indication on the unit design view comprises:
displaying the warning indication at an adjacent position of the fourth graphic object;
How to develop software. 5. The method of claim 4,
Displaying the warning indication on the unit design view comprises:
displaying a delete menu in response to a predetermined user input for a warning display indicating that the second actor should be connected to the fourth graphic object;
In response to a user input of the remove menu selection, a warning mark indicating that the second actor should be connected to the fourth graphic object is removed, and the connection graphic object of the first graphic object and the second graphic object is removed. updating and displaying the unit design view; and
and automatically modifying the source code so that the reference to the second source object automatically added to the first source object is deleted.
How to develop software. 5. The method of claim 4,
The first actor is subclassed to further include a reference pointing to a third actor among the plurality of actors,
Displaying the warning indication on the unit design view comprises:
displaying a warning indication indicating that the second actor and the third actor should be connected to the fourth graphical object;
displaying an Add Members menu in response to receiving a predetermined user input for the fourth graphic object or the warning display;
in response to receiving a user input for selecting the Add Members menu, updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object; and
modifying the source code so that the reference to the second actor and the reference to the third actor are automatically added to the source object of the fourth graphic object,
How to develop software. 9. The method of claim 8,
Updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object,
Updating and displaying the unit design view so that the newly created graphic object of the second actor and the newly created graphic object of the third actor are connected to the fourth graphic object,
How to develop software. 9. The method of claim 8,
Updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object,
Updating and displaying the unit design view so that the graphic object of the second actor previously created in the unit design view and the graphic object of the third actor previously created in the unit design view are connected to the fourth graphic object containing,
How to develop software. 9. The method of claim 8,
The first actor is subclassed to further include a reference to a source entity implementing a value structure initially composed of a predetermined set of kernel data including a first value of a first type and a second value of a second type. will,
In response to receiving a user input for selecting the Add Members menu, updating and displaying the unit design view so that the graphic object of the second actor and the graphic object of the third actor are connected to the fourth graphic object,
updating the unit design view so that the newly created graphic object of the second actor and the newly created graphic object of the third actor are connected to the fourth graphic object; and
Updating the unit design view so that the graphic object of the source object embodying the value structure previously created in the unit design view is further connected to the fourth graphic object,
How to develop software. The method of claim 1,
The program development software,
It is an integrated development environment (IDE) for developing a driving program of a machine including a plurality of actors and messages transmitted and received between the plurality of actors as components,
The first source entity,
a source entity implementing a first actor among the plurality of actors;
The second source entity,
A source entity implementing a value structure initially composed of a predetermined set of kernel data including a first value of a first type and a second value of a second type,
The displaying step is
In response to a user input in the unit design view for selecting the second graphic object, displaying a property view for editing each value, type, or variable name included in the value structure,
How to develop software. The method of claim 1,
The step of automatically modifying the source code is,
In response to a unit design storage input for reflecting user inputs in the unit design view is input, modifying the source code so that the user inputs are collectively reflected,
How to develop software. The method of claim 1,
The user input to the unit design view connecting the first graphic object and the second graphic object is,
including sequential selection of the first graphic object and the second graphic object,
How to develop software. 15. The method of claim 14,
The user input to the unit design view connecting the first graphic object and the second graphic object is,
sequential selection of the first graphic object and the second graphic object;
and typing input of the reference name of the second source entity via a dialog that is automatically displayed in response to completion of the sequential selection.
How to develop software. The method of claim 1,
Displaying a code view displaying the source code of the first source object, further comprising:
Displaying the code view comprises:
displaying a reference to the second source object automatically added to the source code of the first source object to be visually distinguished from the source code input by the user; and
In response to a predetermined user input for a reference to a second source object displayed to be visually distinct, displaying a unit design view in which a connection graphic object connecting the first graphic object and the second graphic object is highlighted. comprising steps,
How to develop software. The method of claim 1,
The step of automatically modifying the source code is,
Displaying a connection graphic object connecting the first graphic object and the second graphic object together with the first graphic object and the second graphic object in the unit design view in response to the user input,
in response to predetermined user input to the associated graphical object, further comprising displaying a code view displaying a reference to the automatically added second source object;
How to develop software. The method of claim 1,
The step of automatically modifying the source code is,
automatically adding a reference to the second source object in a deactivated state to the first source object;
displaying a connection graphic object in a first state connecting the first graphic object and the second graphic object on the unit design view;
activating a reference to a second source object in the deactivated state in source code in response to a predetermined user input for the connected graphic object in the first state; and
Including the step of updating and displaying the connected graphic object of the first state to the connected graphic object of the second state,
How to develop software. The method of claim 1,
The step of automatically modifying the source code is,
automatically adding a reference to the second source object in a deactivated state to the first source object;
displaying a connection graphic object in a first state connecting the first graphic object and the second graphic object on the unit design view;
in response to a predetermined user input to the connected graphical object in the first state, displaying a source code view displaying a reference to a second source object in the inactive state; and
Analyze the source code modification related to the reference to the second source object through the source code view, and when it is determined that the reference to the second source object is activated as a result of the analysis, the connected graphic object in the first state Including the step of updating and displaying the connected graphic object of the second state,
How to develop software. The method of claim 1,
The step of automatically modifying the source code is,
Displaying a connection graphic object connecting the first graphic object and the second graphic object on the unit design view,
Displaying the connection graphic object on the unit design view comprises:
Comprising the step of linearly displaying the connection graphic object in a form in which a part of the center is erased,
How to develop software. 21. The method of claim 20,
The step of displaying the connected graphic object in a linear form in which a part of the center is erased,
In response to a selection user input for an outgoing wireless area formed in an area where the outgoing connection graphic object of the first graphic object is connected to the first graphic object, all outgoing connection graphics of the first graphic object Including the step of displaying the object linearly in a form in which a part of the center is erased,
How to develop software. 21. The method of claim 20,
The step of displaying the connected graphic object in a linear form in which a part of the center is erased,
In response to a selection user input for an incoming wireless region formed in a region in which the incoming connection graphic object of the second graphic object is connected to the second graphic object, all incoming connection graphics of the second graphic object Including the step of displaying the object linearly in a form in which a part of the center is erased,
How to develop software. 21. The method of claim 20,
The step of displaying the connected graphic object in a linear form in which a part of the center is erased,
measuring a graphic object density of the unit design view; and
Based on the measured graphic object density, comprising the step of determining whether to linearly display the connected graphic object in a form in which a part of the center is erased,
How to develop software. 24. The method of claim 23,
Measuring the graphic object density comprises:
measuring the graphic object density of the connected graphic object;
How to develop software. 21. The method of claim 20,
The step of displaying the connected graphic object in a linear form in which a part of the center is erased,
measuring a density of a graphic object in a predetermined area based on a central point of the connected graphic object; and
Based on the measured graphic object density, comprising the step of determining whether to linearly display the connected graphic object in a form in which a part of the center is erased,
How to develop software. The method of claim 1,
receiving a user input in the unit design view further connecting one or more graphic objects and the first graphic object, wherein each graphic object corresponds to a source object one-to-one; and
In response to receiving a user input for inserting two or more of the second graphic object and the one or more graphic objects into the first tie graphic object displayed in the unit design view, the graphic object inserted into the first tie graphic object removing from the unit design view, and displaying information about the graphic object inserted into the first tie graphic object in the first tie graphic object or in a position adjacent to the first tie graphic object,
The step of automatically modifying the source code is,
automatically modifying the source code so that a reference to the second source object and a reference to each source object corresponding to the one or more graphic objects are added to the first source object.
How to develop software. 27. The method of claim 26,
The graphic object inserted into the first tie graphic object is removed from the unit design view, and information on the graphic object inserted into the first tie graphic object is stored in the first tie graphic object or of the first tie graphic object. The step of displaying in an adjacent position is,
further removing all of the slave graphic objects of the graphic object inserted into the first tie graphic object from the unit design view,
How to develop software. 27. The method of claim 26,
When a user input in the unit design view connecting a fifth graphic object pointing to a fifth source object and the first tie graphic object is input, a reference to the second source entity and each corresponding to the one or more graphic objects further comprising automatically modifying the source code so that a reference to the source object of
How to develop software. 27. The method of claim 26,
in response to a user input in the unit design view copying the first tie graphic object being input, further displaying a second tie graphic object that is a duplicate of the first tie graphic object in the unit design view;
displaying an Add Members menu in response to receiving a predetermined user input for a warning display indicating omission of the slave object of the second tie graphic object or the graphic object included in the second tie graphic object; and
In response to receiving a user input for selecting the Add Members menu, further comprising the step of creating a slave object connection missing in each graphic object included in the second tie graphic object,
The step of creating a slave object connection missing in each graphic object included in the second tie graphic object,
The first method of creating each slave object and creating a slave object connection to the newly created slave object, or connecting a graphic object previously created in the unit design view as a slave object, but missing slave object connection When a graphic object of a corresponding type is not previously created in the unit design view, a step of creating a new slave object and performing a slave object connection to the newly created slave object is performed by the second method,
How to develop software. 27. The method of claim 26,
The graphic object inserted into the first tie graphic object is removed from the unit design view, and information on the graphic object inserted into the first tie graphic object is stored in the first tie graphic object or of the first tie graphic object. The step of displaying in an adjacent position is,
receiving, by a user input, a tie target master object for a duplicate slave graphic object connected to two or more master objects among graphic objects inserted into the first tie graphic object;
removing from the unit design view remaining graphic objects excluding the duplicate slave graphic object among graphic objects inserted into the first tie graphic object; and
removing the connection graphic object between the duplicate slave graphic object and the tie target master object from the unit design view,
How to develop software. A method performed in a computing device to develop a program including a unit operating in a Finite State Machine (FSM) method, the method comprising:
displaying a first graphic object indicating a first state of the unit and a second graphic object indicating a second state of the unit on an FSM view among a plurality of views provided by program development software; and
automatically displaying a dialog for receiving a trigger message name and an action function name in response to a user input in the FSM view for creating a connection from the first graphic object to the second graphic object; and
and automatically adding the prototype of the action function to the source code of the unit by using the trigger message name and the action function name input through the dialog.
How to develop software. 32. The method of claim 31,
The prototype of the action function includes the name of the first state and the name of the trigger message as parameters, and the return is automatically described as the second state,
How to develop software. 32. The method of claim 31,
The step of automatically displaying a dialog for receiving the trigger message name and action function name as input,
In response to completion of input of the trigger message name and the action function name through the dialog, additionally displaying an action function graphic object connecting between the first graphic object and the second graphic object,
How to develop software. 34. The method of claim 33,
automatically displaying a dialog for receiving a trigger message name in response to a user input in the FSM view for creating a connection from the first graphic object to the action function graphic object; and
Further comprising the step of automatically updating the trigger message name included in the prototype of the action function in the source code of the unit to the trigger message name input through the dialog,
How to develop software. 34. The method of claim 33,
When a user input in the FSM view that creates a connection from the action function graphic object to a third graphic object indicating a third state of the unit is input, the return state included in the prototype of the action function is displayed as the second 3 further comprising the step of automatically updating to the status,
How to develop software. A method performed in a computing device that provides an integrated development environment (IDE) for developing a driving program of a machine including a plurality of actors as components,
When a user input indicating a connection from a first actor graphic object to a second actor graphic object is input, the source code of the first actor is automatically modified so that a reference to the second actor is added to the source of the first actor to do;
displaying an FSM edit view of the first actor when a user input indicating entry into a finite state machine (FSM) editor for the first actor is input; and
When a user input for creating a connection from a graphic object indicating a first state of the first actor to a graphic object indicating a second state of the first actor is input through the FSM edit view, the first state automatically adding to the source code of the first actor a prototype of an action function to be executed when transitioning from
How to develop software. A method performed on a computing device, comprising:
displaying the first graphic object pointing to the first source object and the second graphic object pointing to the second source object on a unit design view among a plurality of views provided by the program development software; and
When a user input in the unit design view connecting the first graphic object and the second graphic object is input, the source code of the first source object such that the first source object includes an instance of the second source object comprising the step of automatically correcting
How to develop software.

Images