Abstract:
Data-driven configuration of various views on data models. A framework may be provided that offers one or more parameterized view generation components, each aimed at generating a particular view type in response to configuration data that populates the parameters of the associated component. A user or other computing entity merely provides configuration data to an appropriate view generation component to generate a custom view. That custom view may then optionally perhaps be applied to any number of data models, or perhaps not applied to any data model at all and just saved for perhaps some future use. This view generation may generate composite views on a data model, or even hierarchical views on a data model.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    Data models define a collection of components and potentially also the interrelationships between those components. The components may be any definable entity, and the relationship between the components may be any definable relationship. Data models are not limited to defining software components such as objects in an object-oriented program. Components in the data model may also be representation of people (in the case of, for example, an organizational hierarchy data model), steps or flows (in the case of a process data model), cash credits or debits (in the case of a balance sheet data model), and so forth for a potentially unlimited variety of data models. The nature of the components will often depend on the nature of the data model itself. 
         [0002]    The various components of a data model may have various associated attributes. Furthermore, each component might have various relationship types with other components of the data model. In order to gain a reasonable intuition on a particular data model, it is helpful to have a particular visual representation (or view) of the data model. However, some views may emphasize particular attributes, and perhaps particular relationship types, but even if unintentionally deemphasize other attributes and relationship types. 
         [0003]    When a developer designs a computer-implemented view of a data model, the developer may program software that illustrates that is applied to a particular data model to show a particular view of the particular data model. However, to do that, the developer might go through detailed coding processes and labor associated with developing that computer-implemented view. Alternatively or in addition, the view may be limited to only one particular view of the data, and have limited configurability. 
       BRIEF SUMMARY OF THE INVENTION 
       [0004]    Although not required, some embodiments described herein relate to the configurability of various views on data models. A framework may be provided that offers one or more parameterized view generation components, each aimed at generating a particular view type in response to configuration data that populates the parameters of the associated component. Accordingly, a user or other computing entity merely provides configuration data to an appropriate view generation component to generate a custom view. That custom view may then optionally perhaps be applied to any number of data models, or perhaps not applied to any data model at all and just saved for perhaps some future use. 
         [0005]    In one embodiment, a composite viewer may be generated that includes various different views on a data model, allowing the user to simultaneously view the data model from different perspectives thereby potentially gaining further insight and understanding as compared to just viewing the data model through one view. 
         [0006]    Alternatively, or in addition, a composite view of a data model may be embedded in yet another composite view to generate a hierarchical structure of views. In one embodiment, the highest layer of that hierarchy might even be an entire application, or even perhaps an operating system. 
         [0007]    This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. 
         [0008]    These and other objects and features of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0009]    To further clarify the above and other advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. It is appreciated that these drawings depict only illustrated embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which: 
           [0010]      FIG. 1  illustrates a computing system in which embodiments described herein may operate; 
           [0011]      FIG. 2  illustrates a message processing environment that represents just one of many environments in which the principles described herein may operate; 
           [0012]      FIG. 3  schematically illustrates a view construction module of  FIG. 2 ; 
           [0013]      FIG. 4  illustrates a rendering environment in which a custom view is to be used by a rendering module to render views of one or more selected data models. 
           [0014]      FIG. 5  illustrates a flowchart of a method for formulating a custom view that may be applied to data models. 
           [0015]      FIG. 6  illustrates a user interface that may result from this generation of a composite view. 
           [0016]      FIG. 7  illustrates a user interface that may be used to augment the composite view of the data model. 
       
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
       [0017]    Embodiments described herein relate to a data-driven configuration of various views on data models. First, some introductory discussion regarding a computing system in which the principles described herein may be employed will be described with respect to  FIG. 1 . Then, various embodiments of the configuration of various views on data models will be described with respect to  FIGS. 2 through 7 . 
         [0018]      FIG. 1  illustrates a computing system  100 . Computing systems are now increasingly taking a wide variety of forms. Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, or even devices that have not conventionally considered a computing system. In this description and in the claims, the term “computing system” is defined broadly as including any device or system (or combination thereof) that includes at least one processor, and a memory capable of having thereon computer-executable instructions that may be executed by the processor. The memory may take any form and may depend on the nature and form of the computing system. A computing system may be distributed over a network environment and may include multiple constituent computing systems. 
         [0019]    As illustrated in  FIG. 1 , in its most basic configuration, a computing system  100  typically includes at least one processing unit  102  and memory  104 . The memory  104  may be physical system memory, which may be volatile, non-volatile, or some combination of the two. The term “memory” may also be used herein to refer to non-volatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well. As used herein, the term “module” or “component” can refer to software objects or routines that execute on the computing system. The different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads). 
         [0020]    In the description that follows, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors of the associated computing system that performs the act direct the operation of the computing system in response to having executed computer-executable instructions. An example of such an operation involves the manipulation of data. The computer-executable instructions (and the manipulated data) may be stored in the memory  104  of the computing system  100 . 
         [0021]    Computing system  100  may also contain communication channels  108  that allow the computing system  100  to communicate with other message processors over, for example, network  110 . Communication channels  108  are examples of communications media. Communications media typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information-delivery media. By way of example, and not limitation, communications media include wired media, such as wired networks and direct-wired connections, and wireless media such as acoustic, radio, infrared, and other wireless media. The term “computer-readable media” as used herein includes both storage media and communications media. 
         [0022]    Embodiments within the scope of the present invention also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise physical storage and/or memory media such as RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media. 
         [0023]    Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described herein. Rather, the specific features and acts described herein are disclosed as example forms of implementing the claims. 
         [0024]      FIG. 2  illustrates a configurable view generation environment  200  in which the principles described herein may be employed. The environment  200  may be incorporated within the computing system  100  of  FIG. 1 . The configurable view generation environment may generate a custom view that may then be applied to any number of data models. There are a limitless variety of data models, each having particular component type(s). For instance, a data model might be a process in which the components are steps in that process, an organizational chart in which the components are resources or employees, a computer program in which the components are modules, an inventory in which the components are individual items or classes of items in that inventory, a representation of the solar system in which each of the components is a representation of a sun, a planet, a moon, or the like. 
         [0025]    The possibilities are limitless for what a data model might be. The principles described herein may be applied wherever different users might want different views of a data model. For instance, in a process data model in which the components are steps, some individuals (such as general contractors) might want a view that emphasizes which steps are dependent on completion of other steps, and that emphasizes a representation of a time required for each step to complete. The contractor or another user might want a view that emphasizes which steps have been completed, which are in process, and which are not started. If the data model where the solar system, a scientist might want a realistic scaled view of the solar system, perhaps one that outlines the orbit of the various planets. Another view on the solar system might artificially enlargen the representation of the various planets so that they might be more easily viewed by schoolchildren who are being taught about the solar system. For any given data model, a user might want to easily switch their view of the data model from one custom view to another, or even perhaps view multiple custom views of the data model simultaneously. Haven given this example, the principles described herein may apply to any data model, and to any configurable view on that data model. 
         [0026]    The process of formulating a custom view is data driven. The user or some other human or computing entity may set configuration data  201  that defines how the custom view will be constructed. The configuration data  201  is one of the inputs to the custom view generator  210 . The configuration data  201  may be all provided at once, or may be provided at different times during the custom view construction process. In one embodiment, the configuration data  201  is declarative. 
         [0027]    The type of configuration data  201  might not be standardized, but may differ according to the type of custom view to be generated. There are a variety of view construction modules  202  that might each correspond to a particular custom view type. There might be numerous view construction modules  202  available to the custom view generator  210 . However, in  FIG. 2 , there are only four view construction modules  202 A,  202 B,  202 C and  202 D illustrated. The ellipses  202 E represents, however, that there may be fewer than this number, or more that this number—perhaps many more. 
         [0028]    Referring to  FIG. 3 , a view construction module  300  is schematically illustrated. The view construction module  300  includes various parameters that might depend on the type of custom view that the view construction module  300  may correspond to. In this specific example, the view construction module  300  is illustrated as including five parameters  301 ,  302 ,  303 ,  304  and  305 . However, the number of parameters may differ according to the custom view, and according to the degree to which that custom view has been parameterized. Accordingly, the ellipses  306  represents that there may be other types of views as well. 
         [0029]    The parameters of the view construction module  300  may be populated by the configuration data  201  if the view construction module  300  is to be used to generate a custom view. The logic  310  of the view construction module  300  may then be used with the various populated parameters as inputs to define underlying behavior of the view. For instance, if the custom view was to be a flowchart of the process data model in which the components were steps, a parameter might be a whether dependencies are to be shown, a designation of the symbol types that are to be used to represents the various step times (e.g., conditional branching, start and stop steps, and others), whether there are certain conditions to be applied such as minimizing certain steps if the number of steps exceeds a certain number, and the like. Accordingly, the configuration may be a property of a view (e.g., background color), but may also include a condition that affects the behavior of a view, and that may potentially require further information before the structure of the custom view may be known. For instance, if there are more than 20 components in a data model, a different view entirely may be used to represent that view as compared to there being 20 or less components in the data model. 
         [0030]    Referring back to  FIG. 2 , the custom view generator  210  receives the configuration data  201 , selects an instance of an appropriate view construction module  202  (e.g., view construction module  202 C), and populates the various parameters of the view construction module  202 C with information from the configuration data. This results in a custom view  211 C. being generated, which may then be provided to a library of custom views  211 . In  FIG. 2 , three custom views  211 A,  211 B and  211 C are illustrated as being included in the custom view library  211 . However, there may be other numbers as represented by the ellipses  211 D. The custom views may later be applied to one or more data models to thereby create an actual view of a data model. The custom views  211  may each contain the logic of the corresponding view construction module from which the custom view was constructed, with one or more or all of the corresponding parameters being now populated by the configuration data. 
         [0031]      FIG. 4  illustrates a rendering environment  400  in which a custom view is to used by a rendering module  410  to render views  411  of one or more selected data models  402 . A single custom view may be used to render multiple data models. For instance, the custom view  401  may be used to render any one or all of the data models  402 . The data models are illustrated as including five data models  402 A,  402 B,  402 C,  402 D and  402 E. However, the ellipses  402 F represents that there may be library of more or less than this number of data models. Accordingly, not only might a user configure multiple views, but those custom views may each be applied to any one or more data models. 
         [0032]      FIG. 5  illustrates a flowchart of a method  500  for formulating a custom view that may be applied to data models. In the first stage of the method  500 , the custom view is constructed as represented by the acts  501 ,  502 ,  503  and  504 . Such acts may be performed for each custom view to be generated. In the second stage of the method  500 , which might occur at any point after the first stage, the custom view as applied to a data model to render a view of the data model. This second stage is represented by acts  505  and  506 , and may be repeated whenever a custom view is to be applied to a data model to render a view of the data model. 
         [0033]    The configuration data is accessed (act  501 ). For instance, in  FIG. 2 , the configuration data  201  is accessed by the custom view generator  210 . User input might then designate that the configuration data is to be applied to generate a custom view (act  502 . Alternatively, there might be some other triggering mechanism for determining that the configuration data is to be used to generate a custom view. 
         [0034]    The configuration data is then applied as one or more parameter to a corresponding view construction module (act  503 ). In  FIG. 2 , for example, the configuration data  201  may be applied to the parameters of the view construction module  202 C. This results in the generation of a custom view (act  504 ) that may be applied to any one or more of the available data models. For instance, in  FIG. 2 , the custom views  211  were generated by the custom view generator  210  by applying the configuration data  201  to one or more of the view construction modules  202 . 
         [0035]    Thereafter, user input may be detected designating that the custom view is to be applied to a data model to generate a custom view of the data model (act  505 ). Alternatively, some other triggering mechanism might be used to determine that a custom view is to be applied to a data model. This results in the generation of a custom view of the data model (act  506 ). 
         [0036]    Some of the custom views may represent composite views formulated as a collection of one or more other custom views. For instance,  FIG. 6  illustrates a user interface  600  that may result from this generation of a composite view. The user interface  600  includes three custom view renderings  602 ,  603  and  604 , or the same data model. The custom view rendering  602  in the upper right corner lists the various properties of the data model. In this case, the data model is named “5”, is of type “sub-process”, and has certain information and roles also illustrated in the properties view  602 . A flow view  603  is illustrated in the lower left corner and illustrates the process as a flow chart. A tree view  604  is illustrated in the lower right corner and illustrates the process data model as a tree structure. 
         [0037]    The upper left corner represents a master view  601  that illustrates a representation of all of the data models that the composite custom view may be applied to. In this case, the fifth data model is selected. If another data model is selected in the master view  601 , the detail views  602  through  604  would show views of a different data model. The physical relationship of the various views of the composite view may also be configurable. 
         [0038]    The views may be applied hierarchically. For instance, in  FIG. 6 , there is a two level hierarchy of custom views illustrated. The detail views  602  through  604  each represent a first level in the hierarchy. Accordingly, each of the detail views  602  through  604  may have been generated by applying a different custom view to the same data model. Accordingly, the composite view  600  represents a composite view on a data model. This composite model may be augmented. 
         [0039]      FIG. 7  illustrates a user interface  700  that may be used to augment the composite view of the data model. In this example, some type of user interaction (e.g., a drag and drop from the custom view selection banner  710 ) causes the selected custom view to be applied to the data model, and relatively positioned with the prior composite custom view of the data model. In  FIG. 7 , an augmented tree view  701  of the same data model is now illustrated. In this case, the selection of the augment tree custom view from the selection banner  710  was the indication to the system that that custom view is to be applied to the data model. Accordingly, the composite custom view of the data model now includes four detail views  602 ,  603 ,  604  and  701 . In a similar way, a custom view of a data model may be deleted by perhaps dragging and dropping a custom view off of the display. 
         [0040]    In  FIG. 7 , the composite view (represented by the aggregation of views  600  and  701 ) might itself be a component of a data model, with perhaps the entire display  700  being yet another custom view of a data model. The entire display  700 , however, is applied to a different model. Specifically, the data model is a list of the various custom views and a corresponding edit area. The banner  710  and its positioning at the top of the display may be the result of a particular custom view applied to the custom view data model. That custom view might also provide an edit area where the composite view  600  and  701  may be operated upon. An entire application may be defined using a higher-level custom view. Thus, when one purchases an application, a user might be able to configure the high-level custom view on the data model representing that application so that the application is rendered as the user wishes. 
         [0041]    Accordingly, embodiments have been described in which various views of data models may be generated in a configurable way. An intermediary programmer or even a user may thus be able to quickly define and change various views on a data model. This flexibility allows for the generation of views in a manner that is more tailored for a particular application or user. 
         [0042]    The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.