JP2012108907A - User feedback-based dynamic economical system reconfiguration method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user feedback-based dynamic economical system reconfiguration method by which participants can positively modify software and a system so as to mutually share profit that the participants aim at by enhancing levels of development and maintenance repair of software and a system through intellect of group techniques of many users.SOLUTION: The user feedback-based dynamic economical system reconfiguration method includes a step (S2) of opening a basic economical system constructed on a server to the public through a network; a step (S3) of transmitting user's feedback including alterations of an UI structure of the basic economical system or alterations of an information structure through a user terminal connected to the network; steps (S11), (S15) of making UI structure alterations or information structure alterations of the basic economical system through the feedback; and a step (S2) of further opening the altered economical system reconstructed through the feedback to the public through the network.

Description

  The present invention relates to an ecosystem development technique that allows multiple anonymous users to secure and evolve voluntary traffic information for software and systems, and more particularly to improve flexibility and user efficiency in evolution. The present invention relates to a dynamic ecosystem reconfiguration method based on a user feedback that enables an ecosystem to be actively reconfigured by efficiently reflecting user feedback.

  In recent years, when software and systems have been developed and supplied unilaterally by large companies as in the past, it has become difficult information for developers and users to obtain sustainable life benefits. This trend is further clarified in the public software development method led by Linux (registered trademark) due to the development of Google and the success of the participating business model. In particular, users and applicable devices have been diversified due to the trend toward IT in the vicinity of living devices, and in response to this, most software and systems must provide differentiated services and changeable services by users. I must. The limited development environment by developers limited in this situation causes user dissatisfaction due to limitations of implementation and maintenance.

  Thus, a lot of software has shifted to a development method based on public software, which allows users to voluntarily work with other users of similar perspectives to acquire differentiated services according to their perspectives. Try to act as the next developer group. In this way, the natural transformation of the user as a developer allows the initial result to be continuously and spontaneously evolved with a high level of result by verifying various forms. In addition, users who participate as secondary developers can earn distinct benefits that can be earned from their own perspective: custom service or community composition, economic success, and so on.

  Ecosystem means a system that builds and evolves a naturally occurring organization that allows all developers to grow together through voluntary participation of various developers and users. Therefore, from the developer's standpoint, it is necessary to construct an ecosystem that can disseminate their own development results well in the early stages, and from the user's standpoint, not only can they receive the optimal service, It is necessary to configure the ecosystem so that it can participate more actively as a secondary developer. In particular, the ecosystem must have the flexibility to be reconfigured with minimal effort in order to be able to satisfy the diverse perspectives of multiple users.

  The ecosystem includes multiple variables, such as the type of product to be spread and the scope of the user, despite the voluntary management system of developers and users. Therefore, only essential functions that can be mutually agreed by the developer and the user can be determined in the early stage of system development, and the remaining functions are determined through an adjustment process in the ecosystem management process. However, most current ecosystems largely limit the usability of the initial users by providing only the ecosystem function services that are initially determined by the developers, as well as others by users who can occur in the future. There is a problem that the addition of functions and the linkage with external systems are severe.

  The present invention was devised to improve the above-mentioned problems, and the benefits aimed by participants by raising the level of software and system development and maintenance and repair through the collective intelligence of many users. It aims at user feedback based dynamic ecosystem reconfiguration method that can be actively modified to share each other.

  A user feedback-based dynamic ecosystem reconfiguration method according to the present invention includes a step of publishing a basic ecosystem built on a server via a network, and a user ecosystem connected to the network via the user terminal. Sending a user feedback including a UI structure change or an information structure change, performing a UI structure change or an information structure change of the basic ecosystem via the feedback, and a correction reconstructed by the feedback And further publicizing the ecosystem through the network.

  In the present invention, the step of changing the UI structure is adding or deleting a primary menu, a secondary menu or a menu for an independent function.

  The menu for the independent function of the present invention includes RSS, Twitter (social networking service), or tag cloud.

  The UI of the basic ecosystem according to the present invention is implemented by applying a UI abstraction hierarchy.

  In the present invention, the plurality of classes for performing the UI structure change are configured in different UIs, and the classes configured in the different UIs are primary menu correction, secondary menu correction or independent. It is a menu modification for the function.

  The UI of the basic ecosystem according to the present invention is characterized in that the addition and deletion are performed without limitation by applying an iterator pattern or an abstract factory pattern (abstract factory pattern).

  In the present invention, the classes configured in the different UIs include an upper function class and an aggregation lower detail class in the function class.

  In the present invention, the information structure changing step includes adjusting an information unit indicated in the ecosystem UI, and repackaging the adjusted information unit in a similar information category to form an information packaging unit. Adjusting the step.

  In the present invention, after the step of transmitting the feedback of the user, the step of reflecting the opinion of the user with respect to whether or not the feedback is reflected is included.

  The present invention enables the initial builder of the ecosystem to reduce development costs by ensuring a flexible ecosystem design pattern and model.

  In addition, the feedback from the participants can be structurally easily reflected and progressed quickly, and it is possible to induce the user's continuous, voluntary and positive participation for the reconfiguration of the ecosystem. Alternatively, user feedback can ensure constant changes and evolution of ecosystems while minimizing side-effects due to ecosystem modifications and changes.

It shows the network environment for realizing the ecosystem. 1 shows the configuration of a server for implementing an ecosystem according to the present invention. Step by step the procedure for user feedback on the ecosystem. 2 shows an example of a model to which a UI abstraction hierarchy is applied. Shows the process by which a user participates in the ecosystem to change opinions.

  Hereinafter, a user feedback-based dynamic ecosystem reconfiguration method according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the process, the thickness of the line and the size of the component shown in the drawings may be exaggerated for the sake of clarity and convenience. Moreover, the term mentioned later is a term defined considering the function in this invention, and this may change with a user, an operator's intention, or a custom. Therefore, the definitions for such terms must be made based on the contents throughout this specification.

  The initial objective of building the ecosystem is to disseminate and spread the results of development by content developers and suppliers, but the development results have evolved to a high level from various perspectives through voluntary user participation. It must be possible to form a mutual cooperative relationship between the users participating in this process.

  Therefore, in the present invention, in order to induce effective dissemination of products and voluntary participation of users, a basic structure of the initial ecosystem and a procedure by which user feedback can be efficiently and efficiently reflected in the ecosystem. Presented.

  Alternatively, present a system development model that applies design patterns to develop a flexible ecosystem where user feedback can minimize side-effects due to ecosystem modifications and changes, It also presents a process for multiple users to participate in the maintenance and repair of the ecosystem efficiently.

  FIG. 1 shows a network environment for realizing an ecosystem. Referring to FIG. 1, a network environment for realizing an ecosystem includes a server 110 and a plurality of user terminals 130 capable of bidirectional communication via the server 110 and the network 120.

  The user terminal 130 is a computer such as a desktop PC or a laptop PC, or communicates data with the server 110 via an appropriate user interface (UI) such as a wireless communication device such as a mobile phone or a smartphone. Any device that can do this is possible.

  A user can connect to the server 110 via the user terminal 130 and use a service provided by the server 110, but is not limited thereto, and is actively implemented by the server 110 via the ecosystem. It can also act as a developer or information provider that modifies or alters the resulting product to evolve it.

  The server 110 can implement an appropriate UI that can be used by the user on the user terminal 130, and the user can connect to the server 110 through such a UI, and information that is built by the developer or the server 110. Or provide feedback for corrections or changes to the product that was initially built by the developer.

  FIG. 2 shows a configuration of the server 110 for realizing the ecosystem according to the present invention. Referring to FIG. 2, the server 110 includes an information posting module 111, a material providing module 112, a user participation module 113, an operation / management module 114, and a storage module 115. The user can communicate with the ecosystem embodied by the server 110 via the UI 116.

  The information posting module 111 is information that is considered to be useful to the user from the viewpoint of a developer, and is a module for providing notification information that is not frequently fed back by the user. For this, the information bulletin module 111 can generate an information bulletin menu such as a bulletin board or a notice board for posting information on the UI of the user terminal 130. In such an information posting menu, “ecosystem purpose and mission”, “News”, “release information”, “notification items”, and the like can be posted. Alternatively, the information bulletin module 111 is a “tag cloud” function that allows the developer to conveniently inform the user of the updated contents, or “tag cloud” that makes it easy for the user to configure important tags. Etc. can be embodied.

  The document providing module 112 is a module for providing a result to be shared with the user from the developer's viewpoint or a result of frequent feedback by the user, such as “downloading”, “FAQ”, “technology An information providing part such as “articles” can be implemented.

  The user participation module 113 is a module that implements a function that allows the user feedback to be confirmed and whether or not the reflected result is reflected. The lower module includes, for example, an orphan A module capable of generating a menu for performing the project module 113a, thematic forum 113b, and the question / answer 113c function may be provided.

  The orphan project module 113a is for supporting the user participation project so that the shared result can be evolved into various shapes by the user. It is for sharing information by user groups who are impressed with the subject. Alternatively, the question / response 113c is for the purpose of knowledge transfer with respect to shared information, and may be embodied as “Q & A”, “reply”, or the like.

  The operation / management module 114 is a module that operates and manages the server 110, and performs an operation and management function related to user information, content, security, and the like.

  The storage module 115 is a module that performs a function of physically storing and managing content managed by the ecosystem embodied in the server 110, that is, content provided by the developer and changed content by the secondary developer (user).

  The user can actively reconfigure the ecosystem by improving the ecosystem while performing feedback via the user participation module 113 of the server 110 at the user terminal 130 connected to the server 110.

  FIG. 3 shows a procedure for performing user feedback on the ecosystem as shown in FIG.

  Step S1 is performed in which a developer develops a basic ecosystem constructed mainly for distributing initial contents, and step S2 is performed in which the developer is built in the server 110 and published via the network 120. Accordingly, the user connected to the server 110 via the user terminal 130 connected to the network 120 goes through step S3 in which feedback is sent to such a basic ecosystem. At this time, the UI structure or the information concept is changed according to the range in which the feedback is reflected.

  As shown in FIG. 3, when the UI structure is changed according to feedback from the user, S4 can be performed, or the primary menu (main menu) addition step S5 or the deletion step S6.

  At this time, if the primary menu change is not generated, a step S7 for adding or deleting a secondary or lower menu simply occurs to expand the content.

  On the other hand, if there is no change in the UI structure, step S8 in which a menu for an independent function such as RSS, Twitter, tag cloud, or the like is added or changed is performed. After the UI changed in this way secures an appropriate space through the step S9 for rearranging the menu position on the UI, the step S10 for correcting the main frame (that is, the UI layout) and the overall UI are performed. Finishing is done through step S11 to reconstruct.

  If the feedback from the user is a feedback requesting a change in the information structure, after step S13, adjusting the information unit displayed on the ecosystem UI, re-packaging the adjusted information unit into a similar information category In step S14, the information packaging unit is adjusted. Then, it finishes by performing step S15 which adjusts a physical information storage structure. The modified ecosystem thus changed by the user feedback is further published via the network 120, and a continuous feedback reflection cycle is performed through step S16 in which the modified ecosystem by other users is considered.

  Such ecosystem feedback is frequently generated by multiple users, so it is important to reflect such frequent user feedback in the UI hierarchy without side effects. For this reason, in the ecosystem of the present invention, a model defined so that the maintenance and repair of the ecosystem can be easily performed regardless of the change subject (class) by implementing the UI by applying the UI abstraction hierarchy is applied. Can do. FIG. 4 shows an example of a model in which such a UI abstraction hierarchy is proposed.

  This model is broadly divided into an abstract UI management part, a function management part, and a repository management part. Among these, the UI management part that is most closely changed by user feedback is the UI management part. By defining the abstraction hierarchy, it is defined to minimize the ease of change due to the independence of implementation and the dependency on the association module.

  For this reason, when the user needs to change UI structure by applying the abstract factory pattern (Abstract Factory Pattern), which is a design pattern, the primary menu is modified so that different processing is possible depending on conditions. Three classes of menu correction and correction (FirstMenuModifying, SecondMenuModifying, IndependentUIModifying) are implemented to form different UIs. In addition, it has been possible to maximize the independence of the menu instance (MenuInstance) class by applying an iterator pattern so that menus can be added or deleted without limitation.

  The abstract factory pattern is useful when you have to create and throw "object sets" for various components. This pattern can be used to generate objects that match the situation. A typical example is the look and feel change function of the AWT / Swing library, which is a GUI component of the Java programming language. The appearance of Metal, Microsoft Wind, Mac OS, etc. can be changed. As a result, the basic factory object in the abstract factory can be changed. Then, all GUI objects generated thereafter can be based on the corresponding look and feel.

  In addition, by defining classes in an aggregation relationship as a whole, it is possible to select functional implementation by user feedback, and it is possible to design a customized ecosystem through operation correction within the same class. I did it. In other words, the upper function class includes a lower detail class that adds a sense of detail, and a module that is in a collective relationship with one class embodies another ecosystem depending on the presence or absence of a set of modules that are aggregated as a selection target. be able to.

  FIG. 5 illustrates the process by which a user such as that described above participates in the ecosystem and promotes opinions.

  When an opinion on the user feedback is received S11 via the user terminal 130, the process goes through step S13 which is considered by one or more management members (Administration Members) who voluntarily operate the ecosystem in the initial stage. In this process, the consent of the user who proposed the feedback can be secured S12 and S15, and the management committee is examined by the self-reconsideration S14.

  If it is determined that the feedback reflection is not preferable, the user feedback is finished in the issue process end S16 process. When the user feedback is completed by a simple correction operation, this is reflected as it is, and correction S17 is performed.

  If a significant change such as a change in the DB or UI frame is requested, the opinion of the management committee is communicated to the user terminal 130 to the user (suggestor) who has proposed feedback, and the discussion with the user is subsequently proceeded. The In this way, step S18 for reconverging opinions through the process of discussion and correction can be performed.

  If such a significant change needs to be made, after the feedback reflection method is set S19, the opinions of the users who have proposed feedback are converged S20. If there is an agreement of the user who proposed the feedback, such feedback is reflected S21, and the user who proposed the feedback further evaluates the evaluation by the user by transmitting the evaluated opinion with respect to the reflected result. Through step S22.

  Through this series of steps, user feedback can be processed on an official and formal process, allowing users to review their opinion processing process and contribute to sustainable ecosystem management. It can develop as a core user.

  The present invention has been described with reference to the embodiment shown in the drawings. However, this is merely an example, and various modifications and equivalent other embodiments will be possible if the person has ordinary knowledge in the technical field to which the technology belongs. Can be understood. Therefore, the technical scope of the present invention should be defined by the following claims.

111: Information posting module 112: Document providing module 113: User participation module 114: Operation / management module 115: Storage module 116: User interface

Claims (9)

Publishing the basic ecosystem built on the server via the network;
Sending user feedback including a UI structure change or information structure change of the basic ecosystem via a user terminal connected to the network;
Changing the UI structure or information structure of the basic ecosystem via the feedback; and
Publishing the modified ecosystem reconfigured by the feedback via the network, and reconfiguring the user feedback based dynamic ecosystem.   The user feedback based dynamic ecosystem reconfiguration according to claim 1, wherein the step of changing the UI structure is a primary menu, a secondary menu, or a menu addition or deletion for an independent function. Method.   The method of claim 2, wherein the menu for the independent function includes RSS, Twitter, or tag cloud.   The method of claim 2, wherein the UI of the basic ecosystem is implemented by applying a UI abstraction hierarchy.   A plurality of classes for performing the UI structure change are configured in different UIs, and the classes configured in the different UIs are for primary menu correction, secondary menu correction or independent functions. The user feedback-based dynamic ecosystem reconfiguration method according to claim 4, wherein the menu is modified.   The user according to claim 5, wherein the UI of the basic ecosystem is an addition or deletion performed without limitation by applying an iterator pattern or an abstract factory pattern (abstract factory pattern). A feedback-based dynamic ecosystem reconfiguration method.   6. The user feedback-based dynamic ecosystem re-established according to claim 5, wherein the classes configured in the different UIs are composed of an upper function class and a lower detail class aggregated in the function class. Configuration method. The step of changing the information structure includes:
Adjusting an information unit displayed on the UI of the ecosystem;
2. The user feedback based dynamic ecosystem reconfiguration method according to claim 1, comprising repackaging the adjusted information unit into a similar information category to adjust the information packaging unit. .   The user feedback based dynamic ecosystem reconfiguration method according to claim 1, further comprising a step of reflecting the user's opinion on whether or not the feedback is reflected after the step of transmitting the user feedback. .

Images