KR20150133902A - System and method for developing of service based on software product line - Google Patents

Abstract

The present invention relates to a system and a method for developing a service based on a software product line. When developing the service based on the software product line, the method of the present invention comprises the following steps of: generating a service model having a sequence; setting one writing type between writing through the reuse of preregistered core assets and newly creating, for the generated service model; writing a business process model according to the set writing type and generating service specifications; setting one service type between a complex service and a single service for an activity which requests for an external web service call from the written service model; setting one writing type between writing through the reuse of the preregistered core assets and newly creating according to the set service type; writing a complex or single service model according to the set writing type; and packaging the written complex or single service model in a predetermined form, registering the same as a core asset, and outputting the same.

Description

TECHNICAL FIELD [0001] The present invention relates to a system and a method for developing a service based on a software product line,

The present invention relates to a service development technique based on a Software Product Line (SPL).

As the spread of software rapidly increases, a close relationship between human life and software has been established, and accordingly, a technology for rapidly producing quality software is required. However, in order to develop high-quality software, re-usability, stability, and performance must be considered. Therefore, it takes a lot of time and effort to develop the software.

In order to solve such a problem, conventionally, systems which provide similar services without developing systems separately have been considered together and developed. Specifically, a software product line (SPL) that assures sufficient core assets by analyzing common points and differences in consideration of functional aspects and quality of various systems belonging to the same domain, and develops desired systems by combining these core assets ) Was proposed.

However, in order to support systematic reuse in existing SPL, it is necessary to have an automated system that can only search and access passive service-oriented core assets. In the course of developing services that integrate business processes and service components Service reuse was not easy.

On the other hand, Korean Patent No. 819032 (entitled " business process automatic recovery apparatus and method composed of a web service ") of the related art discloses that an automatic recovery policy is set in advance in the process of designing a process according to execution characteristics of a business process A business process automatic restoration attribute setting unit, a storage unit for sequentially recording an execution progress status of the process, and a business process for retrieving the predetermined automatic restoration policy and restoring the execution of the process based on the execution progress status of the business process And an automatic restoration unit.

However, this conventional technique minimizes human intervention in the recovery of the web service based business process and prevents errors that may occur during manual recovery due to misjudgment of the process manager. In addition, And not an automated framework for reusing business processes and service components.

An embodiment of the present invention is to provide a service development system and method for developing services by reusing existing services as core assets in SPL.

It should be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to an aspect of the present invention, there is provided a service development system based on a software product line, in which artifacts of a service and a service created in advance are stored in a core asset ) Registered and stored service registry / repository; A service generation unit for generating a service description by reusing the registered core asset or defining a model of a service having a new arbitrary sequence; A core asset search unit searching at least one of service and service models among the registered core assets and providing the searched service and service model to the service generation unit as the core assets to be reused; And a service packaging / storage unit for packaging the service and service models generated by the service creation unit in a predetermined form and registering the packages in a service registry / repository.

According to another aspect of the present invention, there is provided a method of developing a service through a service development system based on a software product line, the method comprising: providing a business process model having a sequence using a business process execution language ; Setting a creation type of one of creation and new creation through reuse of a core asset previously registered in the business process model; Creating the business process model according to the created creation type and creating a service description; Setting a service type of any one of a composite service and a single service for an activity requesting an external web service call in the created business process model; Setting a creation type of one of creation and new creation through reuse of the previously registered core asset according to the set service type; Creating a model of the composite service or the single service according to the created creation type; And packaging the created business process model, the composite service model, or the single service model in a predetermined form, and registering the package as the core asset, and outputting the core asset as a core asset, Retrieves at least one of a registered service and a service model, and receives the retrieved service and service model as a core asset to be reused.

According to any one of the tasks of the present invention, the service and service model are used as core assets in the SPL to support the reuse of existing services and capabilities in the process of developing a new service meeting the target, Effective service can be developed.

According to any one of the tasks of the present invention, it is possible to import a business process model corresponding to a target among previously registered core assets to reuse or model a new business process, Can be set.

Further, according to any one of the tasks of the present invention, it is possible to establish an interface between an activity requiring an external web service call in a business process model and a single service or a complex service that is already registered and executed.

FIG. 1 is a block diagram illustrating a structure of a service development system according to an embodiment of the present invention. Referring to FIG.
2 is a flowchart illustrating a service development method according to an embodiment of the present invention.
3 is an exemplary diagram illustrating a process of developing a composite service model from a business process model in a service development system according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

FIG. 1 is a block diagram illustrating a structure of a service development system according to an embodiment of the present invention. Referring to FIG.

1, a service development system 100 according to an embodiment of the present invention includes a service creation unit 110, a core asset search unit 120, a service description verification unit 130, a service packaging / (140) and a service registry / repository (150).

The service generation unit 110 generates a service generated in the SPL-based service development system 100. In detail, the service creation unit 110 includes a business process editor 111, a service assembly editor 112, and a web service editor 113.

Specifically, the business process editor 111 defines a model of a service having a sequence (hereinafter, referred to as a 'business process model') using a business process execution language (BPEL) Creates a service description of the model. For reference, the service description defines the functions provided by the service and the format of the message to be exchanged to use it.

Meanwhile, the service development system 100 according to an embodiment of the present invention provides input / output interface means (hereinafter, referred to as 'graphical user interface') for a service developer. At this time, the service generating unit 110 receives a selection of whether to generate a business process model or a new business process model by reusing the core asset previously registered from the service developer through the graphical user interface. Accordingly, the business process editor 111 defines a business process model by reusing or creating a core asset. At this time, when the reuse of the core asset is selected, the business process editor 111 searches for the reusable business process model among the core assets previously registered in the service registry / repository 150 Results are provided.

In addition, the business process editor 111 delivers to the service assembly editor 112 or the web service editor 113 an activity that requires an external web service invoke in the defined business process model. At this time, the business process editor 111 receives a service developer's choice as to whether to define an activity requesting an external web service call through a graphical user interface as a single or a composite service. Accordingly, the business process editor 111 determines the type of service to be created (i.e., either a single service or a composite service) according to the selection of the input service developer. The business process editor 111 then switches to the web service editor 113 if the determined service type is a single service and to the service assembly editor 112 if it is a composite service.

The service assembly editor 112 is a model of a composite service (hereinafter referred to as a " composite service model ") that can independently provide service by loosely combining and interacting with service components based on Java Business Integration (JBI) ), And generates the service description and Java code of the defined composite service model.

At this time, the service assembly editor 112 receives the selection of the service developer for the type of creation of the composite service model (i.e., creation or new creation through reuse of the core asset) through the graphical user interface. If the creation type of the composite service model is the reuse of the core asset, the service assembly editor 112 receives the result of searching for and recommending the composite service model to be reused among the core assets that have been previously registered by the core asset search unit 120 . At this time, the service assembly editor 112 receives a selection of a service developer for one of the multiple service models provided by the core asset search unit 120 through a graphical user interface, and defines a selected multiple service model. On the other hand, if the creation type for the selected composite service model is a new creation, the service assembly editor 112 generates a new composite service basic model including a web service interface for providing in / out parameters required by the selected activity.

As described above, the service assembly editor 112 creates a composite service model selected from the previously registered core assets or a newly created composite service basic model as a composite service model. At this time, if the created composite service model does not include a service model requesting an external web page call, the service assembly editor 112 directly transfers the service description of the composite service model to the service description verification unit 130. On the other hand, if the created composite service model includes a single service model requesting an external web page call, the service assembly editor 112 delivers the corresponding service model to the web service editor 113.

The web service editor 113 defines a single service model (hereinafter referred to as a 'single service model') composed of a web service interface and business logic, generates a service description and a Java code of a defined single service model do. For reference, the web service according to an embodiment of the present invention not only means an interface with a user through a web environment, but also means a system for processing complex business logic (for example, ERP and CRM) and a business process do.

At this time, the web service editor 113 receives a service developer's selection of a creation type (i.e., creation or new creation through reuse of core assets) of a single service model through a graphical user interface. If the creation type for the selected single service model is the reuse of the core asset, the web service editor 113 receives the appropriate service model that the core asset search unit 120 searches and recommends in the service registry / repository 150 . At this time, the web service editor 113 receives the selection of the service developer for one of the suitable single service models provided by the core asset search unit 120 through the graphic user interface. Then, the web service editor 113 sets an attribute of an activity (hereinafter, referred to as 'call activity') requesting an external web page call using a WSDL (Web Service Description Language) of the selected single service. On the other hand, when the creation type for the selected single service model is a new creation, the web service editor 113 generates a new web service basic model including a web service interface that provides in / out parameters required by the activity, Create a service.

 The core asset search unit 120 searches a service or a service model from the service registry / repository 150 so that the core asset registered in the service registry / repository 150 can be used in the service development system 100, Detection and provide. In detail, the core asset search unit 120 includes a service model searcher 121 and a service searcher 122.

Specifically, the service model explorer 121 searches for a similar service model (hereinafter, referred to as a "service model") from the core asset registered in the service registry / repository 150 and recommends the selected service model And provides it to the service creation unit 110.

The service explorer 122 searches for a similar service in the core asset registered in the service registry / repository 150 and recommends the similar service, and provides a WSDL (Web Service Description Language) of the selected service to the service creation unit 110 .

For reference, the service model recommended by the service model explorer 121 and the service recommended by the service explorer 122 can be selected by a service developer through a graphical user interface. The WSDL can also be an XML document describing an overview of the services provided by the web service or an XML document describing that the endpoints in the network can invoke the web service through messages.

The service specification verification unit 130 performs a static check on the service description (i.e., BPEL and WSDL) generated from the service creation unit 110 and transmits the result to the service packaging / storage unit 140. Generally, a static check is an analysis of a program itself, without running the program to check that it is correct, and examines the logical errors inherent in the program. For example, a static test can create another test program, run the program up to an arbitrary state, and then check the contents of the storage device as a result.

The service packaging / storage unit 140 packages the artifacts of the service created by the service creation unit 110 into a predetermined packaging form suitable for registration in the service registry / repository 150, And requests registration to the service registry / repository 150. For reference, an artifact of a service includes at least one of a service model, a service description, and a binary file.

The service registry / repository 150 is a repository system for registering / storing artifacts of services and services created in the service development system 100. The service registry / repository 150 provides the service registry 110 with the core asset search unit 120 to reuse existing services and service models as core assets when developing services.

Hereinafter, a service development method according to an embodiment of the present invention will be described in detail with reference to FIG.

2 is a flowchart illustrating a service development method according to an embodiment of the present invention.

First, the creation type of the business process model is determined (S201).

That is, when developing a target new service, confirm the creation type that means whether the existing core asset is to be reused or newly created.

As a result of the determination in step S201, if the creation type is the reuse of the core asset, the business process model to be reused among the core assets previously registered in the service registry / repository is retrieved and the retrieved business process model is loaded into the business process editor (S202).

Then, a business process model through reuse of core assets is defined and created through a business process editor (S203).

On the other hand, if it is determined in step S201 that the creation type is new, a new business process model is created through the business process editor (S203).

Then, an activity that requires an external web service invoke is defined as a single service or a composite service in the created business process model (that is, reused or newly created business process model) (S204).

At this time, a selection of a service developer for a service type (that is, a single service or a composite service) in which the activity is to be created can be inputted through the graphical user interface. Also, the selection of the creation type for the single service or the composite service model defined above can be input from the service developer through the graphic user interface.

Then, the service type for the activity is determined (S205).

If it is determined in step S205 that the service type is a composite service, the service type is changed to a service assembly editor to determine a creation type of the composite service model in step S206.

As a result of the determination in step S206, if the creation type of the composite service model is the reuse of the core asset, the composite service model to be reused among the core assets previously registered in the service registry / repository is searched and recommended, The selected model is loaded into the service assembly editor (S207).

On the other hand, if it is determined in step S206 that the creation type of the composite service model is a new creation, a new composite service basic model including a web service interface that provides in / out parameters required through the service assembly editor is generated (S208).

Then, the loaded or generated model is created in the composite service model using the service assembly editor in step S207 or S208 (S209).

Then, it is determined whether the composite service model created in step S209 calls an external web service (S210).

If it is determined in step S210 that the created composite service model calls an external web service, the flow advances to step S211 to switch to the web service editor.

On the other hand, if it is determined in step S210 that the created composite service model does not call the external web service, the service description (e.g., BPEL and WSDL) generated from the composite service model is directly checked (S214).

If it is determined in step S205 that the service type of the activity calling the external web service in the business process model is a single service, the type of the single service model is determined by switching to the web service editor in step S211.

As a result of the determination in step S211, if the creation type of the single service model is the reuse of the core asset, an appropriate service among the core assets previously registered in the service registry / repository is searched and recommended, The calling activity attribute is set using the WSDL (S212).

On the other hand, if the creation type of the single service model is newly created as a result of the determination in step S211, the web service basic model that provides the in / out parameters required through the web service editor is automatically generated and the web service is created S213).

Then, the service specification generated from the service model set or created in the step S212 or S213 is statically inspected through the service specification verification unit (S214).

Then, in step S214, the composite service model or the single service model in which the static inspection is completed is service-packaged in a predetermined packaging form and the core asset registration is set for future reuse of the service in step S215.

Then, the service generated through the above steps is outputted and the corresponding service is registered in the service registry / repository (S216).

Hereinafter, a process of developing a business process model through the service development system 100 according to an embodiment of the present invention will be described with reference to FIG.

3 is an exemplary diagram illustrating a process of developing a composite service model from a business process model in a service development system according to an embodiment of the present invention.

As shown in FIG. 3, the service development system 100 according to an embodiment of the present invention generates a 'business process model 1' through a business process editor. At this time, the business process model 1 is composed of a plurality of business process steps.

One of these business process steps can be automatically generated as a composite service model using a service model explorer as a service model to reuse previously registered core assets. At this time, the service assembly editor defines the composite service 1 for the service model. If the composite service 1 includes a service model that calls an external web service, the composite service 1 switches to the web service editor.

And, another one of the business process steps can be a new composite service basic model without reusing pre-registered core assets. At this time, the service assembly editor defines the compound service 2 for the compound service basic model.

 In addition, another one of the business process steps may be a service model for reusing previously registered core assets, and a single suitable service may be mapped using a service explorer. At this time, a single mapped service is defined as a single service 2 through the web service editor.

Meanwhile, another one of the business process steps may automatically generate a new web service basic model without reusing the previously registered coloring assets. At this time, the generated web service basic model is defined as a single service 3 through the web service editor.

 An embodiment of the present invention described above may be embodied in the form of a recording medium including instructions executable by a computer such as a program module executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

100: service development system
110:
120: Core asset search section
130: Service Specification Verification Unit
140: Service packaging / storage unit
150: Service Registry / Repository

Claims (5)

In a service development system based on a software product line,
A service registry / repository registered and stored as artifacts of pre-created services and services as core assets;
A service generation unit for generating a service description by reusing the registered core asset or defining a model of a service having a new arbitrary sequence;
A core asset search unit searching at least one of service and service models among the registered core assets and providing the searched service and service model to the service generation unit as the core assets to be reused; And
And a service packaging / storing unit for packaging the service and service model generated by the service creating unit in a predetermined form and registering the same in a service registry / repository. The method according to claim 1,
Further comprising: a service specification verifying unit for statically inspecting the service description of the service and the service model generated by the service generator and providing the service description to the service packaging /
The service creation unit,
A service development system that defines a business process model using a business process execution language as a model of the service. The method according to claim 1,
The core asset search unit may include:
Searching for a predetermined similar service or similar service model among the core assets previously registered in the service registry / repository,
Recommending at least one of the searched service or service model to the service creation unit,
The service creation unit,
A service requesting an external web service call among the models of the defined service is generated as either a composite service or a single service,
And creating a service model by creating either the creation of the newly registered core asset or the creation of the new service for each of the composite service and the single service. A method for developing a service through a service development system based on a software product line,
Generating a business process model having a sequence using a business process execution language;
Setting a creation type of one of creation and new creation through reuse of a core asset previously registered in the business process model;
Creating the business process model according to the created creation type and creating a service description;
Setting a service type of any one of a composite service and a single service for an activity requesting an external web service call in the created business process model;
Setting a creation type of one of creation and new creation through reuse of the previously registered core asset according to the set service type;
Creating a model of the composite service or the single service according to the created creation type; And
Packaging the created composite service model or single service model into a predetermined form and registering the model as the core asset,
The re-use of the pre-registered core assets,
And searching for at least one of the previously registered service and service model and providing the retrieved service and service model as the core asset to be reused. 5. The method of claim 4,
Packaging the created composite service model or single service model in a predetermined form and registering the model as a core asset and outputting the model,
Further comprising the step of statically inspecting the service specification of the model of the composite service or the model of the single service.

Images