# Patent

## Title
Visualization framework for customizable types in a development environment

## Abstract

A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.

## Background
CROSS-REFERENCE TO RELATED APPLICATION
The present application is based on and claims the benefit of U.S. provisional patent application Ser. No. 62/133,875, filed Mar. 16, 2015, the content of which is hereby incorporated by reference in its entirety.


BACKGROUND
Computing systems are currently in wide use. Some computing systems are relatively large, and may include, for instance, thousands of different user interface and data entities, like tables and other artifacts. Such computing systems are often customized (some heavily customized) before they are deployed in a given implementation. For example, computer programs can be developed on various development tools. Many software developers use interactive (or integrated) development environments (IDEs) in order to develop software. The developers use an IDE in order to develop models of types within a computing system, and in order to customize those models.
By way of example, some computing systems include enterprise resource planning (ERP) systems, customer relations management (CRM) systems, line-of-business (LOB) systems, among others. These types of computing systems often include many thousands of different types that are modeled and customized. By way of example, some such systems often have thousands of different forms, alone, not to mention many other types. Such systems also commonly include a great deal of logic, as well as workflows, and data entities (such as tables) that allow users to access the system and perform a set of activities, or tasks, in order to carry out their duties within a particular organization for which they are working.
These systems are not the only types of computing systems that have a large number of types. For instance, gaming systems, or a wide variety of other types of systems, often also have many thousands of different types that are modeled in the computing system.
The various types that are modeled in the computing system are compiled (or assembled) into assemblies that are run during runtime. The modeled types can represent data or workflow. For instance, the computing system may store information as a collection of entities, where each entity represents an item associated with an organization. A customer entity, for example, may represent a customer. A sales order entity, for instance, may represent a sales order. A sales quote entity may represent a sales quote. These are illustrative examples only.
When such a computing system is deployed in a specific organization, it is common for the computing system to be highly customized in order to meet the functional requirements of the particular organization in which it is deployed. By way of example, different organizations may wish to have different fields on a given form that represents a customer entity. In addition, for example, different organizations may wish to have different logic for computing a currency conversion on an expense report form. Thus, it can be seen that a given computing system may be heavily customized so that it meets the requirements of a given organization that is using it.
A computing system may also have multiple different layers of customization. For instance, a software company that has created and developed the basic system may simply sell the system as a base product. An independent software vendor (ISV) may then generate a set of customizations to the base product, so that the base product can be resold with those customizations. A value added reseller (VAR) may add another layer of customizations, and the ultimate end user of the product may be in a partnership with a development partner, where the development partner adds their own customizations.
Currently, when a developer or other programmer generates customizations to a base product, the customizations are used to overwrite the base application models in the base product. Such overwriting is achieved by compiling the application model with the changes (to reflect the customizations) already made.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
SUMMARY
A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. 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. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of one example of a development channel.
FIG. 2 is a block diagram of one example of a development architecture having development functionality for developing a base system.
FIG. 3-1 is a flow diagram of one example of a method for generating a customized system.
FIG. 3-2 illustrates one example of an XML file representations of a base type.
FIG. 4 is a block diagram of one example of a differencing/combining engine.
FIG. 5 is a flow diagram of one example of a method for constructing a customized system using stored deltas.
FIG. 6 illustrates one example of a visualization system.
FIGS. 7-1 and 7-2 are screenshots of examples of integrated views.
FIG. 8 is a flow diagram of one example of a method for visualizing customizations and conflicts to a developer.
FIGS. 8-1, 8-2 and 8-3 illustrate example elements that have been customized.
FIG. 8-4 is a screenshot of one example of a conflict resolution window.
FIGS. 8-5 and 8-6 are screenshots of an example of a view showing hierarchy customization conflicts.
FIGS. 9-1, 9-2, and 9-3 are screenshots of examples of user interfaces provided by a lifecycle management system.
FIG. 10 is a flow diagram of one example of a method for upgrading a base system.
FIG. 11A is a block diagram of one example of a DSL modeling system.
FIG. 11B is one example of a portion of the architecture shown in FIG. 2, illustrating a type store, in more detail.
FIG. 11C is a block diagram of a portion of the architecture shown in FIG. 2, illustrating an application type store and runtime environment in more detail.
FIG. 11D is a flow diagram illustrating one example of the operation of the DSL modeling system shown in FIG. 11A.
FIGS. 12A-12C show examples of user interface displays.
FIG. 12D-1 to FIG. 12D-5 (collectively referred to as FIG. 12D) shows one example of XML for DSL and one example of DSL for DSL extensions.
FIG. 13 is a block diagram showing one example of the architecture illustrated in FIG. 2, deployed in a cloud computing architecture.
FIGS. 14-16 show various examples of mobile devices that can be used in the architectures discussed in the previous figures.
FIG. 17 is a block diagram of one example of a computing environment that can be used in various parts of the architectures set out in the previous figures.



DETAILED DESCRIPTION
FIG. 1 is a block diagram of one example of a development channel 100. Development channel 100 may illustratively include system developer 102, independent software vendor (ISV) 104, value added reseller (VAR) 106, partner or customer 108, a runtime environment 110, and end user 112. FIG. 1 shows that system developer 102 may illustratively be an original software manufacturer that designs and develops a base system 114, such as a base business software system. For instance, base system 114 may be a gaming system, an ERP system, a CRM system, an LOB system, etc.
Depending on the type of system, it may be that base system 114 is heavily customized or extended before it is deployed in runtime environment 110, for use by one or more end users 112. By way of example, ISVs 104 often customize base system 114 and make it available to value added resellers 106 which, themselves, customize the base system 114 (after it has already been customized by independent software vendor 104). It may also be that a customer 108, such as an organization of end user 112, desires to even further customize the base system 114 to meet the functional requirements of the organization, so that it can be successfully deployed in runtime environment 110. Alternatively, or in addition, customer 108 may partner with a partner in further customizing the base system 114.
This type of customization can be problematic. For example, when system developer 102 attempts to publish an update to the base system 114, the update may, in some ways, be incompatible with the end user's customizations. Therefore, if the end user attempts to install the update, this can create problems. Further, even where system developer 102 is simply attempting to maintain the code base of the base system 114, this can also create problems where the maintenance conflicts with customizations that have made by ISV 104, VAR 106, and/or customer 108.
FIG. 2 is a block diagram of one example of a development (customization) architecture 200 having development functionality for developing a base system 202 having application elements (or objects) that are run in a computing system. By way of example, development architecture 200 can be used by any of ISV 104, VAR 106, and/or customer 108 to customize base system 202 to meet the functional requirements of an organization, so that the customized system 204 can be successfully deployed in a runtime environment 206 used by an end user 208 of the organization. In this example, architecture 200 can represent any portion of the development channel 100 shown in FIG. 1.
FIG. 2 shows that, in one example, base system 202 includes models 210. Models 210 comprise containers that hold corresponding metadata 212 and can have code 214 as well. In the illustrated example, models 210 include metadata and code corresponding to various different types of application elements (i.e., types) within base system 202. Depending on the particular base system, models 210 can comprise thousands of different elements types that are stored in a type store 216. The types can be defined based on a type system framework employed by a development environment 220 (e.g., an interactive or integrated development environment (IDE)).
A “type” represents an abstraction, representing concepts modeled in a system. In one example, architecture 200 employs a rich hierarchical type system where base types can be extended to create more complex subtypes. A base type comprises a basic or primitive component within the models. Examples of base types include, but are not limited to, an integer type, a string type, a floating point number type, an enumeration value type, a Boolean type, etc. These base types can be extended to create subtypes such as, but not limited to, a quantity type, a currency code type, a sales price type, an hour type, etc. These subtypes can be further extended to create more complex types.
For instance, types can be used to represent various abstractions or concepts in an organization (such as, but not limited to, a customer, a sales order, an employee, etc. in an ERP or CRM system) or in the way the organization information is processed for the specific needs of the organization (such as hiring an employee, creating an order, process an approval, etc.). Some examples of such types include, but are not limited to, tables (which each represent a persisted, object such as a sales order), classes (that contain logic), forms (that represent the presentation of information for the consumers of the information), security roles (represents the access control for information to the consumers), workflows (that represents the flow of processes), menu items, entities, permissions, and other supporting concepts to define the application. These types are defined by a structure of elements each described using a set of attributes or properties (e.g., key/value pairs) and an associated set of operations that are used to interact with the construct. The particular structure of properties, methods, and/or computations define runtime behavior for elements of the given element type. For instance, table objects contain metadata and code for persisting application data in a database, and form objects contain metadata and code to describe information content to be displayed in various devices for application users to consume information and interact with the application.
In this manner, each element type has a particular structure of properties, methods, and/or computations that define runtime behavior for elements of that element type. For example, a table element type can include a name (e.g., “customer table”) and a set of properties that identify attributes for a customer (e.g., customer ID, address, etc.). Also, in this example, the table element type can include a method for computing a value for the customer and/or a method for displaying the value.
The instances of the types are designed by a developer 218 (e.g., developer 218 designs what the customer table or sales order form should look like) and a runtime environment 206, at the time of running the customized system 204, creates, manages and persists specific instances of these types (e.g., customer table type and sales order type, etc.) and provides a framework and an environment for these instances to interact with each other.
The types of system 202 are persisted or stored in type store 216 as documents or files with a defined schema (e.g., extensible markup language (XML), javascript object notation (JSON), a proprietary schema, etc.) in a storage medium, such as a computer file system, database, or cloud storage. For sake of the present discussion, but not by limitation, type store 216 will described as storing the types in type store as XML files. Of course, this by way of example only. Other formats can be utilized.
In this example, metadata 212 and code 214 for each type are serialized into one XML file. That is, snippets of code (i.e., unstructured strings) and metadata (i.e., structured sets of properties and values) are interspersed in the XML file. As such, the metadata and code XML files comprise serialized element structures, each with its own type.
Development environment 220 includes a type accessing component 222 that stores the types in type store 216 and that accesses the stored types from type store 216. In one example, type accessing component 222 is configured to serialize the types into their storage (e.g., XML file) representations as they are stored into type store 216, and to deserialize the storage representations into their physical, source code representations as they are retrieved from type store 216 for development within development environment 220. The source code representations can comprise objects in an object-oriented programming environment. Any suitable programming language(s) can be utilized in development environment 220.
In order to customize base system 202, developer 218 requires that some or all of the types need to be customized, to various degrees, depending on the organizational needs and the unique requirements the organization faces to differentiate them in the market place.
To facilitate customization of base system 202, developer 218 uses customization tools 224 of development environment 220 to make customizations to the base system 202. In the example shown in FIG. 2, the development environment 220 illustratively corresponds to the environment in which customer 108 makes customizations to base system 114. It will be noted, however, that development environment 220 can be an environment in which any developer in development channel 100 (shown in FIG. 1), or any other developer in any other channel, makes customizations to a base system.
By way of example, an IDE (or other development environment) may include a source code editor, one or more build automation tools and a debugger. Some IDEs illustratively include a compiler, an interpreter, or both. They may include a version control system and various tools to simplify the construction of graphical user interfaces. They can also include a class browser, an object browser, and a class hierarchy diagram for use with object oriented software development. Thus, developers can use IDEs to generate the code and metadata, along with customizations to code and metadata, which may be utilized in developing a system for use in a given organization.
Developer 218 can interact with development environment 220 either through a separate developer device (such as a personal computer, a tablet, another mobile device, etc.), or directly. Developer 218 can also interact with development environment 220 over a network (e.g., remotely). Developer 218 is shown interacting directly (e.g., locally) with development environment 220 in FIG. 1 for the sake of example only.
Development environment 220, in one example, includes processor(s) and/or server(s) 226, a display system 223 (which, itself, includes a user interface component 225 and one or more sensors 227, and it can include other items 229 as well), a difference generation system 236, an upgrade system 242, a visualization system 246, a customization analyzer and conflict detection system 248, and a conflict resolution system 250. Development environment 220 can include other items 259 as well.
FIG. 2 shows a variety of different blocks. It will be noted that the blocks can be consolidated so that more functionality is performed by each block, or they can be divided so that the functionality is further distributed. It should also be noted that type store 216 can comprise, in one example, any of a wide variety of different types of data stores. Further, the data in the data store can be stored in multiple additional data stores as well. Also, the data stores can be local to the environments, agents, modules, and/or components that access them, or they can be remote therefrom and accessible by those environments, agents, modules, and/or components. Similarly, some can be local while others are remote.
User interface component 225 generates user interface displays 230 with user input mechanisms 232, for interaction by developer 218. Developer 218 interacts with user input mechanisms 218 in order to control and manipulate development environment 220. In one example, developer 218 can do this to implement customization tools 224 or any other component(s) of development environment 220.
Sensor(s) 227 are configured to detect inputs to display system 223. In one example, one or more of systems 236, 242, 246, 248, and 250 also include sensors configured to detect inputs to those systems.
In one example, processor(s) and/or server(s) 226 comprises a computer processor with associated memory and timing circuitry (not shown). The computer processor is a functional part of environment 220 and is activated by, and facilitates the functionality of, other systems, components and items in environment 220. In one example, one or more of systems 236, 242, 246, 248, and 250 can also include processor(s).
User input mechanisms 232 sense physical activities, for example by generating user interface displays 230 that are used to sense user interaction with environment 220. The user interface displays can include user input mechanisms that sense user input in a wide variety of different ways, such as point and click devices (e.g., a computer mouse or track ball), a keyboard (either virtual or hardware), and/or a keypad. Where the display device used to display the user interface displays is a touch sensitive display, the inputs can be provided as touch gestures. Similarly, the user inputs can illustratively be provided by voice inputs or other natural user interface input mechanisms as well.
Development environment 220, in one example, includes a methodology engine 233 for defining and performing various methods and processes within development environment 220. Methodology engine 233 facilitates an automated framework that uses code generation to drive the implementation of generating the deltas representing changes to the base system, storing the deltas, and applying the deltas to the base system to construct the customized system.
As illustrated in FIG. 2, customization tools 224 include a type customization component 234 that enables developer 218 to customize the types in models 210 of base system 202. For purposes of the present discussion, customizations will be used to mean additive changes to the metadata 212 or code 214 or functionality of base system 114, as well as non-additive changes.
One type of customization comprises adding metadata or code to a given element type. In one example, objects of a form type can be customized by adding a new property, such as a new field, on the form or adding a new method to perform a calculation on data entered on the form or display data via a presentation element in the form. In another example, objects of an employee type can be customized by adding a “hire date” property or adding a new method for determining a raise for employee's salary. In another example, objects of a customer type can be customized by adding a new field to the customer indicating required service levels (e.g., gold customer/silver customer/brass customer, etc.).
Another type of customization comprises deleting or changing properties to a given element type. In one example, objects of a form type can be customized by changing a width of a field. In another example, objects of a customer type can be customized by changing a property value (e.g., changing a customer ID field representing a customer from 10 to 15, changing a label “customers” to “clients”, etc.). For instance, to account for a geographical location in which the system is deployed, a customer address within customer objects can be customized to have more detailed information.
Another type of customization comprises changing a hierarchical arrangement of the metadata elements for a given element type. To illustrate, in one particular example, objects of a form element type comprise a control (e.g., a reset button) that is a child node under a parent node. The parent node comprises a tab labeled “General.” Developer 218 may desire to move the control under a different tab labeled “Details.” To accomplish this, the developer 218 moves or re-parents the child node, corresponding to the control, to a different parent node corresponding to the “Details” tab.
Of course, these are only examples of how customizations can be made to metadata or code, and a wide variety of other customizations can be made as well.
When developer 218 develops customized system 204 by customizing types within base system 202, the customizations are stored as deltas which represent the type differences between the customized system 204 and the base system 202. In one example, difference generation system 236 computes, for each type that is customized by developer 218, a delta or difference between the customized type in customized system 204 and the base form of the type in base system 202.
In one embodiment, difference generation system 236 uses an object model to capture how an instance of a given type can change (such as between versions of base system 202 or different customization layers). In one example, this object model is inferred from a meta model that defines the type system framework within development environment 220, which specifics the structure of individual types in models 210. The meta model allows a given object to be inspected at any time to determine what customizations have been made to the object. This meta model can be obtained using a domain specific language modeling system 235, in one example.
Once the delta for the customized type is computed by difference generation system 236, it is then serialized into an XML file (or other format) by type accessing component 222. Each element in the XML file represents a particular change to the base type in base system 202. In one example, type accessing component 222 serializes the delta into the XML file using the meta model. The meta model defines the schema of the XML file. The XML file is stored in type delta store 238. In this manner, the delta is represented by a separately stored XML file, that is separate from the corresponding XML file stored for the base type of base system 202. While the delta file is separate from the XML files for base system 202, it can be stored in the same physical data store (i.e., type store 216). In another example, the delta file can be stored remote from the base system 202.
A given type in base system 202 can have multiple different layers of customization. For example, multiple entities can each provide different customization to the type. The multiple layers of customization of the type can apply to a same portion of metadata or code, or to different portions of metadata. With respect to development channel 100 shown in FIG. 1, base system 114 can be customized by ISV 104, and then further customized by VAR 106 and/or customer 108. Thus, the type can have multiple delta files in type delta store 238. Each delta file comprises a layer of customization.
In a particular example, for an employee form type, ISV 104 customizes the objects to include an additional field. This customization is represented by a first delta file stored in type store 216. Then, customer 108 customizes the employee form type to modify a label of the field. This customization is represented by a second delta file stored in type store 216. Both of the first and second delta files are stored, separately, in type delta store 238. Type store 216 stores information that associates or maps both of the first and second delta files with the corresponding employee form type, to which they apply, as well as information that defines an order in which the deltas were written. This information allows the deltas to be applied to the base employee type in base system 202 in the correct order.
By way of illustration, but not by limitation, storing a delta file for a given type separate from the underlying base XML file allows the corresponding customization of the type to be easily isolated from the base system as well as other layers of customization for the type. This can facilitate versioning of the deltas as well as physical separation of a customization from the base system (e.g., publishing the customization from a third party provider, such as a marketplace). For instance, ISV 104 can customize a type and provide the corresponding XML file for download from their own website, for example. Further, a developer may desire to remove a portion of proprietary information from the customized system 204 before it is provided to another party. To do so, the developer removes the corresponding XML file without having to further customize the system through customization tools 224 of environment 220.
To construct customized system 204, type accessing component 222 accesses the types and their corresponding deltas, which are stored as XML files in one example, from type store 216. Type accessing component 222 deserializes the base XML files and the delta XML files into corresponding object representations. Then, for each type that has at least one delta, a differencing/combining engine 240 of system 236 is utilized to put the base object and the delta object(s) for that type together to construct the corresponding customized type. Differencing/combining engine 240 understands the structure of the base object and the delta object to facilitate their combination.
After all customized types are constructed, the customized system 204 can be further developed within development environment or passed to runtime environment 206 (or other endpoint) for consumption. Examples of other endpoints include, but are not limited to, upgrade system 242 which facilitates upgrading the underlying base system 202 and lifecycle management system 244 which facilitates managing the customized system 204 once it is deployed. In one example, the runtime environment or other endpoint is unaware of the deltas. The endpoint simply consumes the application types within customized system 204.
FIG. 3-1 is a flow diagram of one example of a method 260 for generating a customized system. For sake of illustration, but not by limitation, method 260 will be described in the context of developer 218 using development environment 220 to develop customized system 204.
At step 262, developer inputs are detected to customized base system 202. For example, developer 218 can access customization tools 224 through user interface displays 230 to select base system 202 for customization. At step 264, type accessing component 222 accesses base system 202 from type store 216. For example, this can include deserializing the XML files for the various types modeled in base system 202. FIG. 3-2 illustrates one example of an XML file representation 261 of a base type (a table in the present example) that is retrieved from type store 216.
At step 266, a DSL modeling display can be displayed with user input mechanisms to receive user inputs that perform DSL modeling at step 268. An example of performing DSL modeling is described in further detail below.
At step 270, a type customization display is displayed with user input mechanisms. For example, customization tools 224 can be provided to developer 218 to customize the types modeled in base system 202. At step 272, user inputs are detected that perform customizations to one or more of the modeled types. For example, as mentioned above, a customization can comprise adding metadata or code to a given element type, deleting or changing properties to a given element type, or changing a hierarchical arrangement of the metadata elements for a given element type. Referring again to FIG. 3-2, one example change (i.e., changing an “original value” to a “changed value”) is represented at reference number 263. These of course, are examples only.
At step 274, development environment 220 identifies the customizations as deltas or differences from the base system 202. In one example, difference generation system 236 is utilized to identify the deltas from the developer customizations.
FIG. 4 illustrates one example of differencing/combining engine (DCE) 240 of difference generation system 236 that can be used at step 274. DCE 240 is configured to compute and construct the deltas between the original object and the customized object that is customized by the user inputs detected at step 272. DCE 240 includes a difference representation component 280 which comprises a mechanism for extracting the differences to compute the deltas and to apply the differences to the base system to construct the customized system 204.
Difference representation component 280 uses a difference computing engine 282. Difference computing engine 282, in one example, uses the object model that is inferred from the meta model to compute differences in the containment hierarchy. Difference computing engine 282 disassembles the type being customized into more basic or primitive components. By way of example, a primitive component comprises a constituent part (e.g., a string, an integer, an enumeration value) that makes up the base type. Each change to a type can be derived from a basic set of changes to the primitive components of the type.
A primitive difference computing component 284 identifies the individual primitive components and inspects each component individually to determine whether it has been changed, added, deleted, or otherwise customized. In one example, primitive difference computing component 284 compares the customized type against the base types in base system 202 to identify the differences.
Referring again to method 260, the delta that represents the differences between the customized type and the base type is generated as a separate file that is tied or otherwise associated with the base system at step 276. In one example, the meta model, which can be defined through DSL modeling system 235, defines the schema format for storing the base system types in type store 216, and the delta types are inferred from the base system types. In this manner, a framework is provided for defining the format of the XML files.
At step 278, the separate delta file is saved in type store 216 separate from base system 202. With respect to the example of FIG. 3-2, a delta file 265 is generated.
FIG. 5 is a flow diagram of one example of a method 300 for constructing a customized system using stored deltas. For example, method 300 can be performed at runtime to apply type deltas in type delta store 238 to base system 202 to construct customized system 204 that is run within runtime environment 206. In another example, method 300 can be performed to test the customized system 204 within a test environment or when customized system 204 is to be further customized within development environment 220 by developer 218. For the sake of illustration, but not by limitation, method 300 will be described in the context of development environment 220.
At step 302, an input is detected to generate types with the deltas applied. As mentioned above, this can include an indication that the customized system 204 is to be run within runtime environment 206. The types are retrieved from base system 202 at step 304. In one example, this includes type accessing component 222 serializing the XML file representations of the types from base system 202 into their physical representations within development environment 220.
At step 306, development environment 220 retrieves all of the deltas corresponding to the types retrieved at step 304. As mentioned above, there can be multiple different layers of customizations to the types. For example, the deltas retrieved at step 306 can include ISV deltas 308 (e.g., representing customizations made by ISV 104 in FIG. 1), VAR deltas 310 (e.g., representing customizations made by VAR 106 in FIG. 1), and customer deltas 312 (e.g., representing customizations made by customer 108 in FIG. 1).
At step 314, the base system types are broken down into their primitive components. For example, DCE 240 receives and disassembles the base system types. A difference application engine 286 (shown in FIG. 4) of DCE 240 applies the deltas to the primitive components at step 316. In one example, this includes difference application engine 286 breaking down the deltas into their primitive components at step 318 and then merging the primitive values of the base system and the deltas.
In one example, a primitive difference application component 288 (shown in FIG. 4) applies the deltas at the correct locations in the base type at the primitive component level. For example, but not by limitation, in one example a primitive component comprises a string as a property within the type. The delta can specify a new or customized value for this string. The primitive difference application component 288 applies the new value to this primitive component within the base type.
In one example, where there are multiple deltas applying to a given type, method 300 identifies an order for applying the deltas at step 320. The order of the deltas can be determined, in one example, from their corresponding XML representations that indicate when the corresponding customizations were made.
At step 322, customization analyzer and conflict detection system 248 of development environment 220 identifies and resolves conflicts that arise in a given type due to the application of the deltas to the base system types.
At step 324, development environment 220 reassembles the types with the deltas applied and outputs the types at step 326, for example for consumption at an end point such as runtime environment 206.
Development environment 220 provides a framework to apply customizations comprehensibly across an entire system for all types in a manner that is efficient, flexible, and requires less developer time. Conversely, in other types of systems the developer had to manually hand-code a given customization across many different types within the base system. Development environment 220 uses code generation to drive the framework implementation in a way that improves the customization architecture.
Referring again to FIG. 2, visualization system 246 is configured to generate visualizations to developer 218 to facilitate the development process. The visualization can identify, among other things, customizations made to various elements as well as conflicts that arise due to conflicting customizations.
For example, an ISV and a VAR may each customize a type in two different ways. The ISV may customize a label in a base type to one value and the VAR may customize the same label to a different value. Customization analyzer and conflict detection system 248 is configured to analyze the customizations made to base system 202 and to detect conflicts between the customizations. These conflicts can be resolved using conflict resolution system 250 that includes, in one example, an auto-resolution component 252 that is configured to automatically resolve some conflicts (e.g., using conflict resolution rules) and a conflict surfacing component 254 that is configured to surface conflicts for developer 218. Conflict resolution is discussed in further detail below.
FIG. 6 illustrates one example of visualization system 246. In the illustrated example, visualization system 246 includes a display system controller 330 that is configured to control display system 223 to generate user interface displays 332 using user interface component 225. In one example, user interface displays 332 are presented to developer 218 during customization of base system 202. For instance, user interface display 332 can be displayed at step 270 in method 260.
As shown in FIG. 6, one example user interface display 332 comprises an integrated visualization (or view) 334 which shows customizations as they have been applied over lower layers of customization. In other words, integrated view 334 shows developer 218 the entire system including the base objects and the customized objects. Through integrated view 334, developer 218 can visualize all of the elements that are customized as well as elements that are not customized. Further, the integrated view 334 can also visualize which elements have conflicts and which elements do not have conflicts.
One example of an integrated view 334 is shown in FIG. 7-1. Integrated view 334 is illustratively a hierarchical tree structure having parent nodes and child nodes. Each child node depends from a corresponding parent node and is shown as being indented to the right relative to the corresponding parent node.
FIG. 7-1 provides a screen shot of a user interface 336 that displays an indication of the type being customized and a list of elements 340 for that type. The user interface 336 includes visual cues for developer 218 to understand what elements have been customized. In the illustrated example, the elements that have been customized are visually distinguished from the elements that have not been customized, for example by bolding the customized element (represented by reference numerals 342). The customizations can comprise changes made by the developer 218 in a current layer of customization, as well as changes made in lower layers of the customizations (e.g., previous customizations made by ISV 104 and/or VAR 106). Further, any of a variety of different types of customizations can be indicated. Some include, but are not limited to, property changes, addition of new elements, re-parenting of elements, and the changing of order of elements. Further, a code and/or metadata editor (not shown in FIG. 7-1) can also be provided with user interface 336. This can enable the developer 218 to make further customizations and to resolve conflicts in the customizations. In another example, user interface 336 can include a preview window 343 of the object. For example, where type 338 is a form, the preview window 343 can display a preview of the form.
Referring again to FIG. 6, visualization system 246 includes a filtering component 344 that filters the view based on a filtering input received from developer 218, for example in a search box 346 shown in FIG. 7-1. The filtering input can include keywords that are used to search the elements. The filtering input can also be used to switch from integrated view 334 to a non-integrated view 348 to view only elements that have been customized or only elements that have conflicts. This is discussed in further detail below. Visualization system 246 can include other items 345 as well.
FIG. 7-2 illustrates another example of an integrated view 334. FIG. 7-2 provides a screen shot of a user interface 350 indicating elements that have been customized and elements that have conflicts. As shown in user interface 350, elements that have been customized are provided with a visual indicator 351-1 (“[c]” in the present example) and elements that have conflicts are provided with a visual indicator 351-2 (“[!]” in the present example). Using these visual indicators, developer 218 can easily see which elements have been customized at a lower level of the customizations and/or have conflicts arising from the customizations.
FIG. 8 illustrates one example of a method 360 for visualizing customizations and conflicts to a developer. For the sake of illustration, but not by limitation, method 360 will be described in the context of visualization system 246 of development environment 220.
At step 362, customized system 204 is constructed by applying type deltas in store 238 to base system 202. At step 364, an integrated view 334 is generated to visualize the customized system to developer 218. Integrated view 334 visually indicates customizations at block 366 and conflicts at 368.
In one example, FIGS. 8-1, 8-2 and 8-3 illustrate elements that have been customized in different ways. FIG. 8-1 illustrates a property change customization. Specifically, one or more properties of element 373 have been changed to new values. Element 373 is visualized by bolding the element's name. Further, the change properties can be displayed in a popup window 375, for example when the user hovers a cursor over and/or selects element 373. Window 375 visualizes the changed properties.
FIG. 8-2 illustrates a customization in which a new element 377 is added. This customization can be visualized by bolding element 377 and/or using a visual indicator 379 (a “+” sign in the present example). Use of visual indicator 379 visually differentiates the new element customization in FIG. 8-2 from the property change customization in FIG. 8-1.
FIG. 8-3 illustrates a re-parented element customization in which an element 381 has been moved to a new parent element. This customization can be indicated by bolding element 381 and/or providing a visual indicator 383 (an arrow in the present example) indicating that the customization is a re-parenting of the element. In this manner, indicator 383 visually differentiates the type customization in FIG. 8-3 from the customizations in FIGS. 8-1 and 8-2.
In the example illustrated in FIG. 6, in order to identify and visualize the various types of customizations and conflicts at step 368, visualization system 246 includes a property change visualization system 352, a hierarchy change visualization system 354, and a code change visualization system 356. Property change visualization system 352 includes a property customization visualization component 353 that visualizes property customizations and a property customization conflict visualization component 385 that visualizes property customization conflicts. Hierarchy change visualization system 354 includes a hierarchy customization visualization component 355 that visualizes hierarchy customizations and a hierarchy customization conflict visualization component 387 configured to visualize hierarchy customization conflicts. Code change visualization system 356 includes a code customization visualization component 357 that visualizes code customizations and a code customization conflict visualization component 389 configured to visualize code customization conflicts. Each of systems 352, 354 and 356 can include other components 358 as well.
Referring again to FIG. 8, in one example, developer 218 can further develop on the system through the integrated view. At step 369, development inputs are detected to customize an element displayed in the integrated view. For instance, developer 218, from the integrated view, selects a given model element to customize or extend, and then provides development inputs to customize or extend metadata and/or code associated with the selected model element.
In one example, the customizations that can be made by developer 218 are restricted or limited based on the customization layers. As mentioned above, in example step 362 the customized system is constructed for developer 218 to view and develop the system at a current customization layer, with the view showing changes made at lower layers of customizations (e.g., elements added or changed at a lower customization layer, etc.). At step 369, the development by developer 218 is restricted so as to not allow developer 218 to delete or rename an element added at a lower customization layer. This, of course, is one example only.
In one example of step 369 in which a code editor is present to developer 218 to edit code, developer 218 provides inputs to change an order of methods within the code editor. Although the order of the methods in the code editor may not impact the runtime environment, it may play a significant role in how developer 218 organizes and visualizes their code. As such, in one example, development environment 220 stores the reordered methods for subsequent presentation to developer 218. For example, a delta can be generated and stored to reflect the new method order.
At block 370, a filtering input is received from the developer to filter integrated view 334 to a desired non-integrated view 348. Examples include a customization filtering input (such as “[c]”) to view customizations only at block 372 or a conflict filtering input (such as “[!]”) to view conflicts only at block 374. The filtered non-integrated view 348 is displayed at step 376.
In the case of filtering the view to show customizations, visualization system 246 employs property customization visualization component 353, hierarchy customization visualization component 355, and code customization visualization component 357. In the case of filtering the view to show conflicts, visualization system 246 employs property customization conflict visualization component 385, hierarchy customization conflict visualization component 387, and code customization conflict visualization component 389.
At step 378, a user input is received to remove a customization from the object. For example, through the integrated view displayed at step 364 or the filtered view displayed at step 376, developer 218 can right click or otherwise select one of the customized elements, and then indicate that the customization should be removed (e.g., select a remove customization menu item).
At step 380, a user input is received to resolve a conflict. For example, through the integrated view displayed at step 364 or the filtered view displayed at step 376, developer 218 can right click or otherwise select one of the customized elements. Then, at step 382, a conflict resolution window is displayed to the user. At step 384, a conflict resolution input is detected and the customization conflict is resolved based on the input.
One example of a conflict resolution window 400 is illustrated in FIG. 8-4. As illustrated in FIG. 8-4, conflict resolution window 400 displays a list 402 of properties that have conflicts for the selected element (i.e., element “LastName” in the present example), and lists 404, 406, 408, and 410 of conflicting values for the properties in list 402. For example, for each conflicted property in list 402, window 400 displays a “current value” in list 410 for the property along with one or more other values that give rise to the conflict. By way of example, these other values include a value in list 404 that is assigned to the property by developer 218 (i.e., “your value”, which could be the same as or different than the current value), an “original value” in list 408 from the base system 202, and a value in list 406 from another layer of customization (i.e., “their value”). For example, where developer 218 is part of customer 108, “their value” in list 406 can be a customization that was made by ISV 104 or VAR 106 shown in FIG. 1.
Conflict resolution window 400 also includes a plurality of user input mechanisms that allows developer 218 to select the value they desire for each property in list 402, to resolve the conflict. In the example of FIG. 8-4, each value in lists 404, 406, 408, 410 has a corresponding option button 401, 403, 405, 407 (or other user input mechanisms) that allows the user to select the value for the property in list 402. Also, in one example, a set of user input mechanisms 409, 411, 413, 415 are provided for developer 218 to select all of the values in the corresponding list 406, 410, 408, 404. Once the conflict has been resolved, the conflict icon within the integrated view is removed as there is no longer a conflict for that element.
Referring again to FIG. 8, in another example, step 382 is utilized to resolve hierarchy change conflicts visualized by component 387. To illustrate, FIG. 8-5 shows a user interface 420 that visualizes hierarchy customization conflicts where nodes 422 do not have a parent node. By way of example, this can occur due to an update to the base system that removes a particular node that previously had one or more dependent child nodes. In one example, the un-parented nodes 422 are not editable until they are properly parented to a valid parent node. FIG. 8-6 illustrates user interface 420 in which node 422 has been re-parented to a proper parent node (for example by the developer 218 dragging node 422 within user interface 420). This removes node 422 from the list of hierarchy conflicts. Node 422 is now editable from user interface 420.
In the context of a code customization conflict visualized by component 389, step 382 displays the conflicting code in a conflict resolution window. Each portion of code is provided with a control that allows developer 218 to select that portion of code to resolve the conflict. This can be done in a manner similar to conflict resolution window 400 shown in FIG. 8-4.
Visualization system 246 provides an integrated visual and design experience for modeling customizations along with multiple visual cues to distinguish the actual customizations. The developer can easily switch between different user interfaces, such as an integrated view and a non-integrated view, that provides views of the customized system. This enhances the user experience and provides for a more efficient development environment.
Referring again to FIG. 2, in one embodiment lifecycle management system 244 is accessible by development environment 220 and includes services that can be used by developer 218 to identify, track, and resolve issues that arise during various lifecycles of a project. For instance, lifecycle management system 244 allows developer 218 to track issues which arise during customization of base system 202. The services of lifecycle management system allow a user to identify the needs of an organization and functionality that is provided with a system and generate or identify functionality or customizations that need to be made to the system in order to meet the needs of the customer that is deploying the system.
The services can include, for example, a diagnostic service that allows lifecycle management system 244 to identify particular environmental information that defines the environment of the deployed system. For instance, lifecycle management system 244 can receive information regarding runtime environment 206 from reporting and management system 258.
Lifecycle management system 244 provides integrated tools for reporting, project management (e.g., gathering estimates), costs of upgrades and conflict resolutions, and producing a timeline accounting for dependencies. These integrated tools help the developer understand the transformations being made, and plan for and execute the remaining tasks of the upgrade. Further, this provides a predictable experience on the part of the developer.
For instance, lifecycle management system 244 include tools that a developer 218 uses in performing various tasks within a project. For example, lifecycle management system 244 can walk the developer 218 through a work breakdown structure of a particular set of tasks pertaining to development of the customized system 204.
In one example, lifecycle management system 244 includes an upgrade service 256 that facilitates upgrades to the system. Upgrade service 256 can provide, in one example, cloud-based metrics pertaining to upgrading the base system 202. For example, developer 218 can upload their metadata and code to lifecycle management system 244 which analyzes the metadata in code and provide various metrics pertaining to whether to upgrade the system and how long it is expected to take. Further, lifecycle management system 244 can provide a series of user interface displays that walk the developer 218 through the upgrade process. Lifecycle management system 244 identifies what resources for the upgrade task are required. The use of lifecycle management system improves the user experience and reduces processing time and bandwidth for the upgrade process.
By way of example, FIGS. 9-1, 9-2, and 9-3 illustrate example user interfaces provided by lifecycle management system 244 during a solution migration process. One example is an update of a current base system 202. The interface 430 is displayed for an upgrade analysis performed on the current base system. For example, developer 218 has uploaded the current system to lifecycle management system 244 which analyzes the system to identify various tasks that need to be completed during the update process. This can be provided in the form of viewable records or files 432.
User interface 434 illustrated in FIG. 9-2 provides a report summary of the upgrade in terms of manual effort required by the developer or other persons involved in the upgrade process. For example, the report summary is broken down in terms of the different models 210 within base system 202 with a corresponding time estimate for how long various tasks will take. FIG. 9-3 provides a user interface 436 that breaks down the specific steps and tasks and provides a work breakdown structure at a more granular level.
FIG. 10 illustrates one example of a method 500 for upgrading a base system. For the sake of illustration, but not by limitation, method 500 will be described in the context of architecture 200 illustrated in FIG. 2.
At step 502, the method starts with a current, customized version of base system 202. For example, base system 202 is stored in type store 216 along with type deltas in store 238 that define customizations to the base system.
At step 504, a maintenance input indicating that the base system is to be upgraded is detected. For example, the maintenance input can comprise an input from developer 218 initiating an upgrade process. In another example, the maintenance input can be received from another system, such as lifecycle management system 244.
For sake of the present discussion, the base system 202 will be referred to as “version A” upon which customizations have been defined for a customized system 204 (referred to as “version A′”). The base system is to be upgraded to a new version (i.e., “version B”. Developer 218 desires that the customizations be carried over to the upgraded version to form a customized version of the upgraded system (referred to as “version B′”).
At step 506, the current version A′ is retrieved. At step 508. The method automatically detects that version A′ is customized. For example, difference generation system 236 applies the meta model, that defines the type system framework within development environment 220, to inspect objects of the current version to determine what customizations have been made to the objects.
At step 510, the delta of the current version (referred to as “delta 1”) is found or otherwise accessed. For example, the deltas can be retrieved from type store 216 or can be computed by difference generation system 236.
At step 512, the delta of the base system upgrade (referred to as “delta 2”) is found or otherwise accessed. For example, lifecycle management system 244 can provide an indication of the differences between version A and version B. In another example, lifecycle management system 244 can provide the entire upgraded base system (version B) to development environment 220, which uses difference generation system 236 to compute delta 2 between version A and version B.
At step 514, the method combines delta 1 (the changes from version A to version A′) and delta 2 (the differences between version A and version B).
At step 516, the method compares delta 1 and delta 2 and identifies any conflicts at step 518. At step 518, the method determines any conflicts between delta 1 and delta 2, for example using customization analyzer and conflict detection system 248.
At step 520, the method automatically makes changes to the system where there are no conflicts. In one example, this can include making transformations needed to accommodate changes between version A and version B including, but not limited to, changing names and calling conventions for application programming interfaces, applying refactoring of the customizations through standard patterns and deriving new types based on the customizations.
At step 522, method 500 performs automatic conflict resolution for conflicts that do not require user input. For example, auto-resolution component 252 of conflict resolution system 250 is utilized to apply conflict resolution rules 524. For example, step 522 can use conflict resolution rules 524 that include algorithms for conflict resolution. One example of a conflict resolution rule comprises a change to an underlying system API. The conflict resolution rule finds the old references to the API and replaces them with new references. In another example of a conflict resolution rule, a customization to version A added text to a user interface but, in version B, some of the UI concepts no longer apply. In this example, the conflict resolution rule can dissemble the previous UI customization and reassemble into a new UI definition in version B.
At step 526, conflicts that are not resolved at step 522 are surfaced for user resolution. For example, the conflicts can be surfaced using conflict surfacing component 254 of conflict resolution system 250. Step 526 provides any suitable user interface that allows the user to resolve the conflict. In one example, a user interface similar to FIG. 8-4 is provided. In any case, conflict resolution inputs are detected at step 528 and used to resolve the conflicts at step 530.
At step 532, a delta is computed for the new, customized version B′ (i.e., delta 3). In one example, this is performed by difference generation system 236. The computed delta 3 is saved to type store 216 at step 534.
In the illustrated example of method 500, many if not all of the steps are performed by development environment 220. In another example, some or all of the steps can be performed by a cloud-based lifecycle management system (i.e., system 244). For example, lifecycle management system 244 can find the deltas at step 510 and 512, combine and compare the deltas at steps 514 and 516, and identify and resolve conflicts at 518 and 522. This of course, is one example of how method 500 can be implemented within architecture 200.
FIG. 11A is a more detailed block diagram of one example of DSL modeling system 235 in more detail. FIG. 11B illustrates DSL-modeled types that can be used by development environment 220, in more detail, and FIG. 11C illustrates one example of runtime environment 206 and application types in an application type store 550 that can form a part of type store 216, or can be separate. FIG. 11D shows one example of the operation of DSL modeling system 235 in more detail. FIGS. 11A-11D will now be described in conjunction with one another.
In the example shown in FIG. 11A, DSL modeling system 235 illustratively includes application type modeling component 552, difference generation type modeling component 554, development tool type modeling component 556 (which, itself, can include behavior authoring type modeler 558 and property authoring type modeler 560), cross reference generation type modeling component 562, application validation type modeling component 564, search type modeling component 566, other productivity type modeling components 568, and it can include other items 570. DSL modeling system 235 illustratively allows the developer 218 to use domain-specific languages (DSLs) to describe the concepts (types) and their relationships to one another. It provides a framework for generating a comprehensive suite of types that, themselves, provide frameworks for development tools, applications, tools for applications, and other developer productivity tools that integrate into those tools.
In general, DSLs describe concepts (or abstractions) and the relations between them in a formal way. Relationships can be described using object-oriented design concepts, such as inheritance, association and composition. The base system 202 may have a number of concepts for developing applications, for instance, such as a class concept (that may contain X++ or other code), a table concept (that is a persistable set of values with code), a form concept (that surfaces information for a user in a user interface), a query concept, etc. Instances of these concepts (such as a customer table, an order processing class, a sales order form, etc.) in base system 202 may be referred to as metadata, and these can be used as building blocks of the final application that comprises base system 202 or customized system 204. DSL modeling system 235 is illustratively used to describe these concepts themselves, such as what constitutes a table, what makes a class, etc. These descriptions are data about metadata or meta-metadata. DSL modeling system 235 can be used to formally describe the notion of these concepts and use code generation techniques to generate several related sets of specific types that form the basis for building an application. Some sets of generated types can include types that represent serializable metadata, such as a table, a class, a form, etc. Instances of these types are designed by the application developer. For instance, the application developer may design what the customer table should look like and what the sales order form should look like, based upon the requirements of the organization deploying the application. The application runtime, at the time of running the application, creates, manages and persists specific instances of these types (such as the customer table type, the sales order type, etc.) and provides a framework and an environment for these instances to interact with one another. These interactions are what makes up the application that comprises customized system 204. The sets of generated types can also include types that are used to support the ability to create the above-described serializable types. These types are consumed by the design time developer tools (such as those in development environment 220). They provide the developer 218 with the capabilities to design the serializable types described above.
Yet another set of generated types include a set of types that are used to generate and navigate the references among the metadata instances (such as the references among the customer table and sales order form, etc.). These references are cross references and serve as a productivity tool for the developer 218.
In operation, DSL modeling system 235 first detects a user input indicating that the user wishes to engage DSL modeling system 235. This is indicated by block 572 in FIG. 11D.
The various components in DSL modeling system 235 then display DSL modeling user input mechanisms that can be actuated to generate various DSL type models. Displaying these user input mechanisms is indicated by block 574.
The corresponding component of DSL modeling system 235 then detects actuation of the user input mechanism in order to generate DSL type models. This is indicated by block 576. For example, application type modeling component 552 illustratively generates user interface displays that can be actuated to generate DSL-modeled application types 578 (shown in FIG. 11B). Difference generation type modeling component 554 illustratively generates user input mechanisms that can be actuated to generate difference generation types 580. Development tool type modeling component 556 illustratively displays user interface displays with user input mechanisms that can be actuated to generate development tool types 582. Behavior authoring type modeler 558 illustratively generates user interface displays that allow developer 218 to generate behavior authoring types 584. Similarly, property authoring type modeler 560 illustratively allows the developer to generate property authoring types 586. Other development tool types 588 can be authored as well.
Cross reference generation type modeling component 562 illustratively generates user interface displays, with user input mechanisms, that can be actuated to generate cross reference generation types 590. Application validation type modeling component 564 generates user interface displays, with user input mechanisms, that can be actuated to generate application validation types 592. Search type modeling component 566 generates user interface displays with user input mechanisms that can be actuated to generate search types 594, and other productivity type modeling components 568 can generate user interface displays, with user input mechanisms that can be actuated to generate other productivity types 596. The DSL-modeled types 597 in type store 595 can include other items 598 as well. It can thus be seen that the various DSL-modeled types 597 can be accessed within development environment 220. They can be used to actually generate application types 578, and a host of different types for the application development framework and tooling deployed within development environment 220. They can be used to generate types for generating cross references between the various application types 578 or other DSL-modeled types. They can be used to generate the difference types 580 that are used to generate differences between the various application types 578. They can also be used to generate a host of different application validation types 592, various development tool types 582 and other productivity types 596 that can be used within development environment 220.
When the user inputs are received to generate the various types in type store 595, then the corresponding components in DSL modeling system 235 generate the DSL type models. This is indicated by block 600 in FIG. 11D. It then saves the DSL type models to type store 595, where they can be used by development environment 220. This is indicated by block 602. In one example, they are stored as XML files. This is indicated by block 604. They can of course be stored in other ways as well, as indicated by block 606.
FIG. 11C shows is a block diagram of portions of the architecture shown in FIG. 2, with runtime environment 206 and application types store 550 shown in more detail. It can be seen in FIG. 11C that runtime environment 206 illustratively includes runtime engine 608, user interface component 610, processors or servers 612, and it can include other items 614. Environment 206 illustratively generates user interface displays 616, with user input mechanisms 618, for interaction by end users 208. End users 208 illustratively interact with user input mechanism 618 in order to control and manipulate the various applications or customized system 204 that is being run in runtime environment 206.
Runtime engine 608 illustratively accesses the various application types 578 stored in application types store 550, in order to run the applications comprising customized system 204. FIG. 11C shows that application types 578 can include a wide variety of different types. They can include entities 620, processes 622, security roles 624, workflows 626, tables 628, classes 630, forms 632, or a wide variety of other application types 634. Applications type store 550 can store other records or other information 636 as well.
Thus, runtime engine 608 illustratively accesses types 578 to perform processes 622 or workflows 626, referencing security roles 624, classes 630, forms 632, etc. It can also operate on entities 620 or a variety of other records.
FIGS. 12A-12C show a set of example user interface displays that can be generated by DSL modeling system 235 in generating DSL-modeled types. FIG. 12A, for instance, shows a user interface display which includes user actuatable input mechanisms that can be actuates in order to generate a DSL-modeled form type. It can be seen that the form has a form design, and the form design has a set of form controls. The various controls can have methods, etc. By actuating the display elements in FIG. 12A, the developer can illustratively modify the DSL definition of a form.
FIG. 12B shows a user interface display that displays classes and relationships on the right, and a set of properties for a specific class (the interactions class) on the left. Again, the developer can interact with the display elements to generate or modify the DSL-modeled type.
FIG. 12C shows one example of editing a DSL model in more detail. It can be seen in FIG. 12C that a user has selected the “Custom Attributes” property. If the user actuates that display element (such as by right clicking n it or otherwise) this causes DSL modeling system 235 to display a popup menu that allows the user to edit the attributes. By selecting any of the various fields in the popup display, the user can modify or otherwise change the DSL model.
In one example, when the DSL models are generated by the various components of DSL modeling system 235, they are stored as XML documents. FIG. 12D-1 to FIG. 12D-5 (collectively referred to as FIG. 12D) shows two different XML documents. The first is an XML document for DSL models of various types. It then shows an example XML document for a set of DSL extensions. Of course, the two DSL documents shown in FIG. 12D are shown for the sake of example only.
It can thus be seen that the present description provides significant technical advantages. By way of illustration, in some types of systems a developer typically has to manually hand-code a given customization across many different types within the base system. Conversely, the present framework, in one example, can apply customizations comprehensibly across an entire system for all types in a manner that is efficient, flexible, and requires less developer time and improves developer efficiency. The present development environment uses code generation to drive the framework implementation in a way that improves the customization system itself.
In one example, the framework uses deltas to store different layers of customization and to construct the customized system in a manner in which a runtime environment does not need to be aware of the deltas. The framework is able to apply the customization deltas in the correct order, and to store the deltas separately such that they can be easily removed from the system, for example in the case where an organization desires to remove proprietary information from the customized system. This can reduce the storage overhead required to store and implement the customized system.
Further, the present description provides a model framework that uses a meta model which allows a given object to be inspected at any time to determine what customizations have been made to the object. This is advantageous in an upgrade situation, for example, in which an organization desires to migrate customizations to a new system version. The model framework inspects the customized system to identify the customizations which are then applied to the new system version. This reduces the development time need to develop the upgrade system and can reduce the likelihood of development errors.
Further, the present description provides a visualization framework that generates visualizations to a developer to facilitate the development process. The visualizations can identify, among other things, customizations made to various elements as well as conflicts that arise due to conflicting customizations. For example, an integrated view improves the developer experience by allowing the developer to better understand what elements have been customized over various customization layers, how those elements have been customized, and what conflicts result from those customizations. This provides an integrated visual and design experience for modeling customizations along with multiple visual cues to distinguish the actual customizations. The developer can easily switch between different user interfaces, such as the integrated visualization and a non-integrated or filtered visualization, that provide different views of the customized system. Further, the developer can easily address and resolve the customization conflicts. This can enhance the user experience and provide for a more efficient and less error-prone development environment.
Further, the present description provides a DSL modeling system that advantageously allows a developer to use a domain-specific language to describe the concepts (or types) and the relationships. It allows the developer to have a framework for generating a comprehensive suite of types that themselves provide frameworks for development tools, applications, tools for applications and other developer productivity tools that integrate into those tools. By using DSL-modeled types, the types, themselves, can easily be modified by modifying the corresponding models. This model-driven approach greatly enhances the efficiency of the development environment. In prior systems, this information was often hard coded into a computing kernel thus, in order to change the structure or definition of a type, a great deal of manual, time consuming and error prone activity was needed. By modeling this information in DSL model, the developer need only modify the model, and the change is propagated all the way through the system, to the runtime environment.
The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.
Also, a number of user interface displays have been discussed. They can take a wide variety of different forms and can have a wide variety of different user actuatable input mechanisms disposed thereon. For instance, the user actuatable input mechanisms can be text boxes, check boxes, icons, links, drop-down menus, search boxes, etc. They can also be actuated in a wide variety of different ways. For instance, they can be actuated using a point and click device (such as a track ball or mouse). They can be actuated using hardware buttons, switches, a joystick or keyboard, thumb switches or thumb pads, etc. They can also be actuated using a virtual keyboard or other virtual actuators. In addition, where the screen on which they are displayed is a touch sensitive screen, they can be actuated using touch gestures. Also, where the device that displays them has speech recognition components, they can be actuated using speech commands.
A number of data stores have also been discussed. It will be noted they can each be broken into multiple data stores. All can be local to the systems accessing them, all can be remote, or some can be local while others are remote. All of these configurations are contemplated herein.
Also, the figures show a number of blocks with functionality ascribed to each block. It will be noted that fewer blocks can be used so the functionality is performed by fewer components. Also, more blocks can be used with the functionality distributed among more components.
FIG. 13 is a block diagram of architecture 200, shown in FIG. 2, except that its elements are disposed in a cloud computing architecture 800. Cloud computing provides computation, software, data access, and storage services that do not require end-user knowledge of the physical location or configuration of the system that delivers the services. In various embodiments, cloud computing delivers the services over a wide area network, such as the internet, using appropriate protocols. For instance, cloud computing providers deliver applications over a wide area network and they can be accessed through a web browser or any other computing component. Software or components of architecture 200 as well as the corresponding data, can be stored on servers at a remote location. The computing resources in a cloud computing environment can be consolidated at a remote data center location or they can be dispersed. Cloud computing infrastructures can deliver services through shared data centers, even though they appear as a single point of access for the user. Thus, the components and functions described herein can be provided from a service provider at a remote location using a cloud computing architecture. Alternatively, they can be provided from a conventional server, or they can be installed on client devices directly, or in other ways.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
In the example shown in FIG. 13, some items are similar to those shown in FIG. 2 and they are similarly numbered. FIG. 13 specifically shows that runtime environment 206, development environment 220, type store 216, and lifecycle management system 244 can be located in cloud 802 (which can be public, private, or a combination where portions are public while others are private). Therefore, user 112 and developer 218 use a user device 804 and developer device 806, respectively, to access those systems through cloud 802. User device 804 renders user interfaces 808 to user 208 and developer device 806 renders user interfaces 810 to developer 218.
FIG. 13 also depicts another example of a cloud architecture. FIG. 13 shows that it is also contemplated that some elements of architecture 200 can be disposed in cloud 802 while others are not. By way of example, type store 216 can be disposed outside of cloud 802, and accessed through cloud 802. In another example, lifecycle management system 244 can also be outside of cloud 802, and accessed through cloud 802. In another example, runtime environment 206 and/or development environment 220 can also be outside of cloud 802, and accessed through cloud 802. Regardless of where they are located, they can be accessed directly by devices 804 and 806, through a network (either a wide area network or a local area network), they can be hosted at a remote site by a service, or they can be provided as a service through a cloud or accessed by a connection service that resides in the cloud. All of these architectures are contemplated herein.
It will also be noted that architecture 200, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
FIG. 14 is a simplified block diagram of one illustrative embodiment of a handheld or mobile computing device that can be used as a user's or client's hand held device 16, in which the present system (or parts of it) can be deployed. FIGS. 15-16 are examples of handheld or mobile devices.
FIG. 14 provides a general block diagram of the components of a client device 16 that can interact with architecture 200. In one example, client device 16 can run components of runtime environment 206 or development environment 220, or both. In the device 16, a communications link 13 is provided that allows the handheld device to communicate with other computing devices and under some embodiments provides a channel for receiving information automatically, such as by scanning Examples of communications link 13 include an infrared port, a serial/USB port, a cable network port such as an Ethernet port, and a wireless network port allowing communication though one or more communication protocols including General Packet Radio Service (GPRS), LTE, HSPA, HSPA+ and other 3G and 4G radio protocols, 1×rtt, and Short Message Service, which are wireless services used to provide cellular access to a network, as well as Wi-Fi protocols, and Bluetooth protocol, which provide local wireless connections to networks.
Under other examples, applications or systems are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 (which can also embody processor 226 from FIG. 2) along a bus 19 that is also connected to memory 21 and input/output (I/O) components 23, as well as clock 25 and location system 27.
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Similarly, device 16 can have a client system 24 which can run various applications. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
FIG. 15 shows one embodiment in which device 16 is a tablet computer 820. In FIG. 15, computer 820 is shown with user interface display screen 822. Screen 822 can be a touch screen (so touch gestures from a user's finger can be used to interact with the application) or a pen-enabled interface that receives inputs from a pen or stylus. It can also use an on-screen virtual keyboard. Of course, it might also be attached to a keyboard or other user input device through a suitable attachment mechanism, such as a wireless link or USB port, for instance. Computer 820 can also illustratively receive voice inputs as well.
Additional examples of devices 16 can also be used. Device 16 can be a feature phone, smart phone or mobile phone. The phone can include a set of keypads for dialing phone numbers, a display capable of displaying images including application images, icons, web pages, photographs, and video, and control buttons for selecting items shown on the display. The phone includes an antenna for receiving cellular phone signals such as General Packet Radio Service (GPRS) and 1×rtt, and Short Message Service (SMS) signals. In some examples, the phone also includes a Secure Digital (SD) card slot that accepts a SD card.
The mobile device can also be a personal digital assistant or a multimedia player or a tablet computing device, etc. (hereinafter referred to as a PDA). The PDA can include an inductive screen that senses the position of a stylus (or other pointers, such as a user's finger) when the stylus is positioned over the screen. This allows the user to select, highlight, and move items on the screen as well as draw and write. The PDA can also include a number of user input keys or buttons which allow the user to scroll through menu options or other display options which are displayed on the display, and allow the user to change applications or select user input functions, without contacting the display. The PDA can include an internal antenna and an infrared transmitter/receiver that allow for wireless communication with other computers as well as connection ports that allow for hardware connections to other computing devices. Such hardware connections are typically made through a cradle that connects to the other computer through a serial or USB port. As such, these connections are non-network connections.
FIG. 16 shows that the phone can be a smart phone 840. Smart phone 840 has a touch sensitive display 842 that displays icons or tiles or other user input mechanisms 844. Mechanisms 844 can be used by a user to run applications, make calls, perform data transfer operations, etc. In general, smart phone 840 is built on a mobile operating system and offers more advanced computing capability and connectivity than a feature phone.
Note that other forms of the devices 16 are possible.
FIG. 17 is one embodiment of a computing environment in which architecture 200, or parts of it, (for example) can be deployed. With reference to FIG. 17, an exemplary system for implementing some embodiments includes a general-purpose computing device in the form of a computer 910. Components of computer 910 may include, but are not limited to, a processing unit 920 (which can comprise any of the processors discussed above), a system memory 930, and a system bus 921 that couples various system components including the system memory to the processing unit 920. The system bus 921 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. Memory and programs described with respect to FIG. 2 can be deployed in corresponding portions of FIG. 17.
Computer 910 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 910 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including 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. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 910. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 930 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 931 and random access memory (RAM) 932. A basic input/output system 933 (BIOS), containing the basic routines that help to transfer information between elements within computer 910, such as during start-up, is typically stored in ROM 931. RAM 932 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 920. By way of example, and not limitation, FIG. 17 illustrates operating system 934, application programs 935, other program modules 936, and program data 937.
The computer 910 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only, FIG. 17 illustrates a hard disk drive 941 that reads from or writes to non-removable, nonvolatile magnetic media, and an optical disk drive 955 that reads from or writes to a removable, nonvolatile optical disk 956 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 941 is typically connected to the system bus 921 through a non-removable memory interface such as interface 940, and optical disk drive 955 are typically connected to the system bus 921 by a removable memory interface, such as interface 950.
Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
The drives and their associated computer storage media discussed above and illustrated in FIG. 17, provide storage of computer readable instructions, data structures, program modules and other data for the computer 910. In FIG. 17, for example, hard disk drive 941 is illustrated as storing operating system 944, application programs 945, other program modules 946, and program data 947. Note that these components can either be the same as or different from operating system 934, application programs 935, other program modules 936, and program data 937. Operating system 944, application programs 945, other program modules 946, and program data 947 are given different numbers here to illustrate that, at a minimum, they are different copies.
A user may enter commands and information into the computer 910 through input devices such as a keyboard 962, a microphone 963, and a pointing device 961, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 920 through a user input interface 960 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 991 or other type of display device is also connected to the system bus 921 via an interface, such as a video interface 990. In addition to the monitor, computers may also include other peripheral output devices such as speakers 997 and printer 996, which may be connected through an output peripheral interface 995.
The computer 910 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 980. The remote computer 980 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 910. The logical connections depicted in FIG. 17 include a local area network (LAN) 971 and a wide area network (WAN) 973, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
When used in a LAN networking environment, the computer 910 is connected to the LAN 971 through a network interface or adapter 970. When used in a WAN networking environment, the computer 910 typically includes a modem 972 or other means for establishing communications over the WAN 973, such as the Internet. The modem 972, which may be internal or external, may be connected to the system bus 921 via the user input interface 960, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 910, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 17 illustrates remote application programs 985 as residing on remote computer 980. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
Example 1 is a development system comprising a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.
Example 2 is the development system of any or all previous examples, wherein the set of customized elements comprise model elements that are customized over a plurality of customization layers, and the integrated view user interface display visually distinguishes a first model element from a second model element based on a type of customization made to each of the first and second model elements.
Example 3 is the development system of any or all previous examples, wherein the user development inputs further develop the first model element, and the customization component is configured to restrict the development of the first model element based on the customization layer at which the first model element was added.
Example 4 is the development system of any or all previous examples, wherein a customization removal user input is detected through the integrated view user interface display with respect to the first model element and, in response to the customization removal user input, the customization component removes one or more customizations from the first model element.
Example 5 is the development system of any or all previous examples, wherein the set of customized elements comprise metadata elements, and the integrated view comprises different visual indicia for each of a metadata element having a property customized in one of the customization layers, a metadata element added in one of the customization layers, and a metadata element that has been re-parented in one of the customization layers.
Example 6 is the development system of any or all previous examples, wherein the set of customized elements comprise code elements, and the integrated view comprises different visual indicia for each of a code element having a method added in one of the customization layers, and a code element having a method customized in one of the customization layers.
Example 7 is the development system of any or all previous examples, wherein the user development inputs are received through the integrated view.
Example 8 is the development system of any or all previous examples, wherein the user development inputs change a method order for a given element in a code editor, and the customization component is configured to store the changed method order for subsequent presentation in the code editor.
Example 9 is the development system of any or all previous examples, wherein the visualization system is configured to detect a view change user input and, in response to the view change user input, switch from the integrated view user interface display to a non-integrated view user interface display.
Example 10 is the development system of any or all previous examples, wherein the user development inputs are received through the non-integrated view user interface display.
Example 11 is the development system of any or all previous examples, wherein the view change user input defines filter criteria, and further comprising a filtering component configured to filter elements for display in the non-integrated view user interface display based on the filter criteria.
Example 12 is the development system of any or all previous examples, wherein the non-integrated view user interface display displays the set of customized elements without one or more of the non-customized elements.
Example 13 is the development system of any or all previous examples, wherein the non-integrated view user interface display displays only customized elements that have customization conflicts.
Example 14 is the development system of any or all previous examples, and further comprising a conflict detection system configured to detect a given one of the customized elements that has a customization conflict, wherein the integrated view user interface display visually indicates the customization conflict, and a conflict resolution system configured to resolve the customization conflict based on a detected conflict resolution user input.
Example 15 is a development system comprising a customization component configured to detect user development inputs to develop elements of a computing system, a display system, a customization conflict detection system configured to identify a given customized element having a plurality of different customization layers and to detect a customization conflict between the customization layers, and a visualization system having a display system controller configured to control the display system to generate a user interface display that visually represents the given customized element and the detected customization conflict.
Example 16 is the development system of any or all previous examples, wherein the display system controller is configured to control the display system to generate a customization conflict visualization user interface display that represents the customizations to the first customized element at each of the different customization layers.
Example 17 is the development system of any or all previous examples, and further comprising a conflict resolution system configured to resolve the customization conflict based on a detected conflict resolution user input.
Example 18 is a computer-implemented method comprising identifying a set of base elements of a computing system and a set of customized elements, that have been customized from base elements of the computing system, generating an integrated view user interface display, with user input mechanisms, that displays representations of the customized elements and the non-customized base elements, detecting a user interaction with the user input mechanisms that defines a filtering criteria, and generating a filtered view user interface display that displays representations of the customized elements based on the filtering criteria.
Example 19 is the computer-implemented method of any or all previous examples, wherein generating the filtered view user interface display comprises switching from the integrated view user interface display to the filtered view user interface display by filtering one or more of the non-customized base elements.
Example 20 is the computer-implemented method of any or all previous examples, wherein generating the filtered view user interface display comprises at least one of displaying only elements that have been customized, or displaying only elements that have customization conflicts.
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 above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

## Claims

1. A computer-implemented method comprising:
identifying a set of non-customized elements of a computing system;
identifying a set of customized elements of the computing system, that have been customized from base elements of the computing system;
identifying a customization type for each customized element of the set of customized elements, the customization type indicating a type of customization that has been applied to the customized element;
generating a representation of an integrated view user interface display that includes a filter criterion user input mechanism, wherein the integrated view user interface display visually distinguishes the set of customized elements from the set of non-customized elements, and the integrated view user interface display includes a set of visual indicators corresponding to the set of customized elements, each visual indicator in the set of visual indicators being visually associated with one of the customized elements and visually identifying the customization type for the associated customized element,
wherein the set of customized elements comprise metadata elements, and the integrated view of the user interface display comprises visual indicia for at least one of:
a metadata element having a property customized in a customization layer;
a metadata element added in a customization layer; and
a metadata element that has been re-parented in a customization layer;
receiving an indication of user actuation of the filter criterion user input mechanism;
based on the indication of user actuation of the filter criterion user input mechanism, identifying a filtering criterion that is based on at least one of:
the customizations applied to the set of customized elements; or
conflicts between the customizations applied to the set of customized elements;
based on the filtering criterion, identifying a filtered set of elements; and
generating a representation of a filtered view user interface display that comprises representations of the filtered set of elements.

2. The computer-implemented method of claim 1, wherein generating the filtered view user interface display comprises switching from the integrated view user interface display to the filtered view user interface display by filtering one or more of the non-customized elements.

3. The computer-implemented method of claim 1, wherein generating the filtered view user interface display comprises at least one of:
displaying only elements that have been customized; or
displaying only elements that have customization conflicts.

4. An electronic development system comprising:
a processor; and
memory storing instructions executable by the processor, wherein the instructions configure the electronic development system to provide:
a customization component configured to:

receive an indication of a user input; and
based on the indication of the user input, customize a computing system; and
a visualization component configured to:
identify a set of customized elements of the computing system;

identify a set of non-customized elements of the computing system;
identify a customization type for each customized element of the set of customized elements, the customization type indicating a type of customization that has been applied to the customized element; and
generate a representation of an integrated view user interface display that visually distinguishes the set customized elements from the set of non-customized elements, wherein the integrated view user interface display includes a set of visual indicators corresponding to the set of customized elements, each visual indicator in the set of visual indicators being visually associated with one of the customized elements and visually identifying the customization type for the associated customized element; and
wherein the set of customized elements comprise metadata elements, and the visual indicators comprises visual indicia for at least one of:
a metadata element having a property customized in a customization layer;
a metadata element added in a customization layer; and
a metadata element that has been re-parented in a customization layer.

5. The electronic development system of claim 4, wherein each customized element is customized, according to the customization type, from a base element in the computing system.

6. The electronic development system of claim 4, wherein the set of customized elements comprises model elements that are customized over a plurality of different customization layers, the model elements comprising a first model element having a first customization type and a second model element having a second customization type that is different than the first customization type, and wherein the visual indicators associated with the first and second model elements visually indicate that the first and second model elements have different customization types.

7. The electronic development system of claim 6, wherein the customization component is configured to restrict development of a particular model element based on a determination of the customization layer at which the particular model element was added.

8. The electronic development system of claim 4, wherein the integrated view user interface display comprises a customization removal user input mechanism associated with a particular one of the customized elements, and wherein the customization component is configured to:
receive an indication of user actuation of the customization removal user input mechanism; and based on the indication of user actuation of the customization removal user input mechanism, remove a customization from the particular customized element.

9. The electronic development system of claim 4, wherein the set of customized elements comprise code elements, and the integrated view user interface display comprises different visual indicia for each of:
a code element having a method added in one of the customization layers; and

a code element having a method customized in one of the customization layers.

10. The electronic development system of claim 4, wherein the integrated view user interface display comprises a development user input mechanism, and the indication of the user input comprises an indication of user actuation of the development user input mechanism.

11. The electronic development system of claim 10, wherein the customization component is configured to:
based on the indication of user actuation of the development user input mechanism, change a method order for a particular one of the customized elements in a code editor;

store an indication of the changed method order;
receive an indication of a user request to access the particular customized element; and
based on the indication of the user request, access the stored indication and generate a representation of a user interface display that presents the customized element with the changed method order in the code editor.

12. The electronic development system of claim 4, wherein the visualization component is configured to receive an indication of a view change user input and, based on the indication of the view change user input, switch from the integrated view user interface display to a non-integrated view user interface display.

13. The electronic development system of claim 12, wherein the visualization component is configured to:
based on the indication of the view change user input, define a filter criterion, and wherein the instructions configure the electronic development system to provide:
a filtering component configured to filter the set of customized elements and the set of non-customized elements for display in the non-integrated view user interface display based on the filter criterion.

14. The electronic development system of claim 13, wherein the non-integrated view user interface display displays the set of customized elements without one or more of the non-customized elements in the set of non-customized elements.

15. The electronic development system of claim 14, wherein the non-integrated view user interface display displays only customized elements that have customization conflicts.

16. The electronic development system of claim 4, and further comprising:
a conflict detection system configured to detect a given one of the customized elements that has a customization conflict, wherein the integrated view user interface display visually indicates the customization conflict; and
a conflict resolution system configured to resolve the customization conflict based on a detected conflict resolution user input.