KR20180060191A - Method for sharing objectless model defined declaratively without platform constraints and apparatus thereof - Google Patents

Abstract

Disclosed is a processing device of an integrated application framework, which supports a server application and a client application to interwork with each other by sharing a model, on the basis of a model-view-controller (MVC) pattern. The integrated application framework comprises: a model unit including at least one data interface; a server application providing unit for and converting and reconfiguring the at least data interface by sharing the model unit such that the model unit is compatible in a server application; and a client application providing unit for converting and reconfiguring the at least data interface by sharing the model unit, such that the model unit is compatible in at least one client application. Therefore, the amount of basic codes can be reduced.

Description

[0001] METHOD FOR SHARING OBJECTLESS MODEL [0002] DEFINED DECLARATIVELY WITHOUT PLATFORM CONSTRAINTS AND APPARATUS THEREOF [

Field of the Invention The present invention relates to a method and apparatus for sharing a declaratively defined non-purpose model without constraints of a platform, and more particularly, to an application framework sharing a declaratively defined non-purpose model based on a type- The present invention relates to a method and an apparatus that can share a single model without constraint of the method.

As information and communication technologies are developed and popular all over the world, various platforms are being developed that operate in the web environment and the mobile environment.

In order to provide services in both web and mobile environments, software developers are developing applications for both web and mobile environments. Repeating unnecessary efforts to develop the same or nearly similar applications in both web and mobile environments And it becomes a problem.

Further, even in a mobile environment, there is a problem that the mobile environment needs to be separately developed when the platform environment in which the mobile device is driven is different.

For example, mobile terminals typically run on Windows platforms, Android platforms, and IOS platforms, and each platform has a different development language to support it, so it is not easy to develop and share the same program source code.

On the other hand, one of the widely used development methodologies for developing applications is the Model-View-Controller (MVC) pattern.

The MVC pattern is an architectural pattern used in software engineering. Successful use of this pattern allows for separation of business logic from the user interface, making it easy to modify the visual elements of the application or business logic running behind it have.

Where the model represents the data of the application and the view represents user interface elements such as text, checkbox items, etc., and the controller can manage the interactions between the data and the business logic.

Conventionally, when an application according to each platform environment is developed by applying an MVC pattern, it is generally implemented to have an MVC pattern in each platform environment. In such a case, there is a problem in that it is difficult not only to interlink the platforms but also to repeat the same efforts.

Therefore, it is necessary to develop a development environment that can save development manpower and cost by independently implementing and sharing MVC pattern without depending on each platform or development language.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and it is an object of the present invention to provide an integrated application framework processing apparatus.

In order to achieve the above object, the present invention provides an integrated application framework processing apparatus.

According to an aspect of the present invention, there is provided an integrated application framework processing apparatus including: a server application and a client application that share a model based on a Model-View-Controller (MVC) You can handle an integrated application framework that supports interworking.

Here, the integrated application framework shares a model unit and a model unit including at least one data interface, and shares a server application providing unit and a model unit for converting and reconfiguring at least one data interface so that the model application is compatible with the server application And a client application providing unit for converting and reconfiguring the at least one data interface so that model attaching is compatible in at least one client application.

Here, the client application providing unit or the server application providing unit may be interworked with the model unit to support redefining data according to at least one data interface.

Here, the at least one client application may be implemented based on at least one of Ios, Android and web platform.

Here, the integrated application framework can be implemented based on a programming language that supports type inference and is interoperable with other programming languages.

Here, a commonly available programming language may include kotlin.

Here, the client application providing unit may confirm whether the model unit has been changed, and reconfigure at least one changed data interface into a data interface corresponding to a platform supported by at least one client application.

Here, the client application providing unit may check whether the data implemented according to the reconfigured data interface is changed, and reflect the change in the model unit.

Here, the change of the data may mean performing at least one of adding, deleting, and changing data according to at least one data face included in the model unit.

Here, the server application providing unit may support at least one of a JSON Request Parameter Handler and a JSON Response Handler.

Here, the client application providing unit may support at least one of a JSON Request Parameter Serializer, a JSON Response Deserializer, and a Reactive Response Communicator.

Here, the client application providing unit is separately configured according to at least one client application, and is separately configured according to at least one client application and a client view that provides a user interface composed of various templates, And may further include a client controller for controlling mutual messages.

Here, the integrated application framework may be provided by a program recorded on a recording medium.

When the integrated application framework processing apparatus according to the present invention as described above is used, it is possible to reduce the redundant investment of the development worker and to improve the development convenience by sharing the model when developing integrated applications supporting various platforms.

In addition, there may be an effect of reducing the basic code amount.

In addition, the coherence of the code can be increased, the degree of cohesion of the code can be increased, and the code jump can be reduced by 10% or more.

1 is a conceptual diagram of an MVC pattern.
2 is an exemplary diagram illustrating a development environment of an integrated development application to which an MVC pattern is applied.
3 is an exemplary diagram for explaining a development language generally used in each development environment.
4 is a first configuration diagram of an integrated application framework according to an embodiment of the present invention.
5 is a second configuration diagram for an integrated application framework according to an embodiment of the present invention.
6 is a configuration diagram of a system in which an application implemented according to an integrated application framework according to an embodiment of the present invention is mounted.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms first, second, A, B, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a conceptual diagram of an MVC pattern.

Referring to FIG. 1, the MVC pattern may include a model, a view, and a controller.

First, the model contains data about the application and can notify the controller and the view when there is a change in the state of the model. With this notification, the view can show the latest results, and the controller can add, remove, and modify the applicable commands as the model changes. In some MVC implementations, a view or controller can read the state of the model directly instead of a notification.

The controller can change the state of the model by sending commands to the model. Also, when the controller receives an event about a user action from a view, it can update the model accordingly, and can change the way the model is displayed by sending a command to the view selection associated with the response.

A view can obtain information from the model (state query) and produce results that the user will see. You can pass your events to the controller, and let the controller choose a view.

It should be understood, however, that each of the configurations herein may be modified according to the design, and is exemplarily described herein.

2 is an exemplary diagram illustrating a development environment of an integrated development application to which an MVC pattern is applied. 3 is an exemplary diagram for explaining a development language generally used in each development environment.

2, in order to develop an integrated application project supporting various platforms, at least one application running on a client or an application running on a server must be configured, databse management system (DBMS).

In this case, when an application running on at least one client is run on a mobile device, it may be configured according to a platform supported by the mobile device. For example, if the mobile device is an Android environment, Java and XML (Extensible Markup Language) And may be implemented using an Objective-C or Swift programming language if the mobile device is an IOS environment.

In addition, if the client is a device running in a web browser environment, it can be implemented in HTML (HyperText Markup Language), CSS (Cascading Style Sheets), and Javascript.

Examples of the devices on which the client application is mounted and operated include a desktop computer, a laptop computer, a notebook computer, a smart phone, a tablet PC, a mobile computer, A mobile phone, a smart watch, a smart glass, an e-book reader, a portable multimedia player (PMP), a portable game machine, a navigation device, a digital camera, a DMB digital multimedia broadcasting player, a digital audio recorder, a digital audio player, a digital video recorder, a digital video player, a PDA (Personal Digital Assistant) have.

On the other hand, an application running on a server can be implemented using Java Spring Framework, JSON (JavaScript Object Notation) format, or JSP (Javaserver pages).

As described above, since the programming language or format used differs depending on the platform or environment in which each application operates, the developer can implement the application by individually executing the project according to the respective platform, There may be a problem that the process of transplanting into the liver must be further performed.

Referring to FIG. 3, a process of applying an MVC pattern to an integrated application development project can be described.

Applying the MVC pattern described above to the development of an integrated application, a model, a view, and a controller can be independently implemented according to each server, mobile, and browser environment. It is common.

This can be attributed to the fact that the platform on which the application runs is different and the programming language it supports is also different, as in Fig.

As described above, when a model, a view, and a controller are individually implemented, a plurality of client applications and server applications are independent of each other. Therefore, when a project is divided for each developer, parameters and return types used in the mutual models are negotiated There is a problem that the basic code amount increases because the code having the same function is individually composed.

4 is a first configuration diagram of an integrated application framework according to an embodiment of the present invention.

Referring to FIG. 4, the integrated application framework 10 is a device that supports a server application and a client application to share models and cooperate with each other based on a Model-View-Controller (MVC) pattern Can be processed.

Here, the integrated application framework 10 includes a model unit 11 including at least one data interface, and a control unit (not shown) for sharing the model unit to convert the at least one data interface to reconfigure A client application providing unit (13) for sharing the server application providing unit (12) and the model unit (11) to convert the at least one data interface to reconfigure the at least one data interface so that the model unit ).

Here, the server application providing unit 12 may be provided to the developer who develops the server application so that the model unit 11 can be compatible with different platform-based programming languages, It is provided to the developer who develops the application so that the model unit 11 can be compatible with different platform-based programming languages.

Here, an example of at least one data interface is as follows.

class TodoRemote: Remote () {
val add = post <AddTodo, Todo> ()
val edit = put <EditTodo, Todo> ()
val delete = delete <UUID, Unit> ()
val list = get <Unit, Array <Todo >> ()

data class AddTodo (val message: String)
data class EditTodo (val id: UUID, val message: String)
data class Todo (val id: UUID, val message: String)
}

The model unit 11 may have a data interface as shown in Table 1. Specifically, the model unit 11 sets the types and types of parameters (String, Array, etc.) for the variables add, edit, delete, list and classes AddTodo, EditTodo, Etc. can be defined.

Here, the client application providing unit 13 or the server application providing unit 12 may be associated with the model unit 11 to support redefining data according to at least one data interface.

Here, an example redefined in the server application is as follows.

val remote = TodoRemote (). apply {
add {TodoRemote.Todo (UUID.randomUUID (), it.message) .apply {todos + = this}}
list {todos}
edit {param ->
(id = it.id, message = param.message)} .toTypedArray () {if (it.id! = param.id)
todos.find {it.id == param.id} !!
}
delete {id ->
todos = todos.filter {it.id! = id} .toTypedArray ()
}
}

The variables add, list, edit, and delete defined in the model unit 11 in Table 1 can be redefined as shown in Table 2 in the server application development environment provided with the server application providing unit 12, Can be redefined in the same way.

The at least one client application may be implemented based on at least one of Ios, Android and a web platform. In summary, one or more client applications may be implemented according to different programming languages that support it in different platform environments.

Here, the integrated application framework can be implemented based on a programming language that supports type inference and is interoperable with other programming languages.

Here, examples of programming languages that support type inference include swift, kotlin, modern C ++, Haskell, and the like.

Here, for example, a co-available programming language may include kotlin.

Here, the meaning of supporting type inference can be explained as follows.

var x = 5
var x: Int = 1

Referring to Table 3 described above with respect to coordinatein, var x = 5 can be deduced to be an integer even if the variable x is not described as int through 5, and var x: Int = 1 indicates that by specifying int It can also be declared fixed by an integer value.

Here, the meaning of common use with other languages may mean that they can be used in combination with each other in the source code unit or converted into another language. Specifically, cotlin is a language that can be mixed or transformed in a source code unit, and can be a main means of an integrated application framework sharing the model presented in the present invention.

Here, the client application providing unit 13 may confirm whether or not the model unit 11 has been changed, convert the changed at least one data interface into a data interface according to a platform supported by the at least one client application, have.

Here, the client application providing unit 13 may check whether the data implemented according to the reconfigured data interface has been changed, and reflect the change in the model unit 11.

Here, whether the data is changed may mean performing at least one of adding, deleting, and changing data according to at least one data face included in the model unit 11. [

5 is a second configuration diagram for an integrated application framework according to an embodiment of the present invention.

Referring to FIG. 5, the model unit 11 may include various data interfaces (data interface 1, data interface 2, data interface 3).

Here, the server application providing unit 12 may support at least one of a JSON Request Parameter Handler and a JSON Response Handler.

Here, the JSon Request Parameter Handler may mean a function or a subroutine for analyzing or processing a parameter when a request is received from the client in JSON format.

Here, the JSon Response Handler may refer to a function or a subroutine that processes a response of a server according to a request.

Here, the client application providing unit 13 may support at least one of a JSON Request Parameter Serializer, a JSON Response Deserializer, and a Reactive Response Communicator.

Here, the JSon Request Parameter Serializer may be a function or a subroutine that performs a process of arranging parameters when a request is sent to the server.

Here, the JSon Response Deserializer may be a function or a subroutine for processing a parameter received in a response received from the server.

Here, the Reactive Response Communicator may be a function or a subroutine that supports functions that can be directly handled by the client.

We have used the JSON format as an example, but this is an example, and the message format can use XML.

In addition, the client application provider 13 or the server application provider 12 may be configured to support a Representational State Transfer (REST) architecture.

Here, REST is a software architecture and may refer to an interface for transmitting data on the web over HTTP without a separate transport layer such as Simple Object Access Protocol (SOAP) or session tracking through cookies. For example, it may contain a Restful Resource Dispatcher, which may refer to a function or subroutine that expresses a URI in a REST fashion.

Here, a program providing an integrated application framework can be recorded and provided on a recording medium.

Here, the client application providing unit 13 may be separately configured according to the at least one client application and may include a client view providing a user interface composed of various templates and a client view separately configured according to the at least one client application, and a client controller for controlling messages between the model view and the client view.

Here, the integrated application framework may include an exception processing unit for detecting and processing various exceptions generated in the process of interpreting the programming language, and may include a log management module for recording the exception It is possible.

6 is a configuration diagram of a system in which an application implemented according to an integrated application framework according to an embodiment of the present invention is mounted.

Referring to FIG. 6, a system implemented by an integrated application framework according to the present invention may include a server connected to a client through a network, and a database may additionally be included in the server.

In addition, the client may have a mobile client running in an IOS environment or an Android environment depending on each supported platform, and there may be a client running in a Windows environment.

Here, each client sends and receives a request and a response to the server and runs the mounted application, where the mounted application is implemented according to the integrated application framework, so that the model can be shared with each other have.

Therefore, data interoperability can be easily achieved because they interact with each other through the shared model.

The CRUD (Create, Read, Update, Delete) codes implemented in accordance with the integrated application framework processing apparatus according to the present invention are stored in a commonly used spring framework Compared with the implemented code, it can be effective to reduce the basic code amount by more than 10%.

Here, the basic code amount can mean an absolute amount of code that is basically necessary when one module unit is created.

Here, the Spring Framework is an open source application framework for the Java platform, which may be referred to as Spring, supports Aspect Oriented Programming (AOP) for dynamic website development, And can be a framework for supporting the development of components based on XML.

In addition, when an integrated framework processing apparatus according to an embodiment of the present invention is used, since a single model is shared, the fragile point of code integrity can be reduced by 10% or more when an integrated application is constructed.

In addition, when the integrated framework processing apparatus according to an embodiment of the present invention is used, it is implemented as a logical division that shares a model according to an MVC pattern, not a physical division to divide into an explicit file form. The code jump can be reduced by 10% or more.

The methods according to the present invention can be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the computer readable medium may be those specially designed and constructed for the present invention or may be available to those skilled in the computer software.

Examples of computer-readable media include hardware devices that are specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions may include machine language code such as those produced by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate with at least one software module to perform the operations of the present invention, and vice versa.

Also, the above-described method or apparatus may be implemented by combining all or a part of the configuration or function, or may be implemented separately.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the present invention as defined by the following claims It can be understood that

Claims (12)

1. A processing device of an integrated application framework that supports server and client applications to share models and interact with each other based on a Model-View-Controller (MVC) pattern,
The integrated application framework includes:
A model unit including at least one data interface;
A server application providing unit for sharing the model unit and converting and reconfiguring the at least one data interface so that the model unit is compatible with the server application; And
And a client application providing unit that shares the model unit and converts and reconfigures the at least one data interface so that the model unit is compatible in at least one client application. The method according to claim 1,
The client application providing unit or the server application providing unit,
And in association with the model unit, to redefine data according to the at least one data interface. The method according to claim 1,
Wherein the at least one client application comprises:
Ios, Android, and web platform. The method according to claim 1,
The integrated application framework includes:
And is implemented based on a programming language that supports type inference and is interoperable with other programming languages. The method of claim 4,
The co-usable programming language comprising:
An integrated application framework processing device, including kotlin. The method according to claim 1,
The client application providing unit,
Confirms whether or not the model unit is changed, and converts the changed at least one data interface into a data interface according to a platform supported by the at least one client application, and reconfigures the data interface. The method according to claim 1,
The client application providing unit,
Confirms whether data implemented according to the reconfigured data interface has been changed, and reflects the change to the model unit. The method of claim 7,
Whether or not the data is changed,
Means to perform at least one of adding, deleting, and changing data according to at least one data face included in the model unit. The method according to claim 1,
The server application providing unit,
A JSON Request Parameter Handler, and a JSON Response Handler. &Lt; Desc / Clms Page number 12 &gt; The method according to claim 1,
The client application providing unit,
An integrated application framework processor supporting at least one of a JSON Request Parameter Serializer, a JSON Response Deserializer, and a Reactive Response Communicator. The method according to claim 1,
The client application providing unit,
A client view separately configured according to the at least one client application and providing a user interface composed of various templates; And
Further comprising a client controller separately configured according to the at least one client application to control a message between the client view and the model unit. The method according to claim 1,
And a program for providing the integrated application framework.

Images