WO2008025514A1

WO2008025514A1 - Systems and methods for rapid application configuration and deployment

Info

Publication number: WO2008025514A1
Application number: PCT/EP2007/007515
Authority: WO
Inventors: Miho Birimisa; Klaus-Peter Lang; Thomas Reiss; Andreas Schuh; Robert Viehmann; Werner Wolf; Jürgen Sattler; Joachim Gaffga; Frank Markert; Steffen Riemann; Peng Gao; Joachim Fitzer; Rainer Brendle
Original assignee: Sap Ag
Priority date: 2006-08-29
Filing date: 2007-08-28
Publication date: 2008-03-06

Abstract

Various embodiments described herein provide systems, methods, and software to reduce the complexity of in purchasing, configuring, modifying, and deploying software applications, such as large-scale enterprise resource planning ('ERP') applications. Some embodiments reduce the complexity of configuring such application by providing tools that place configuration setting decisions in a context where the decision-making is easier. Further, some embodiments may provide tools to input application configuration preferences that, when received, are utilized by one or more processes to make configuration decisions that are consistent across the application under configuration.

Description

SYSTEMS AND METHODS FOR RAPID APPLICATION CONFIGURATION AND DEPLOYMENT

Technical Field

[0001] The present subject matter relates to computer application solutions, and, more particularly, to systems and methods for rapid application configuration and deployment.

Background Information

[0002] Many large-scale computer applications are rather amorphous and can be configured in many different ways to provide many different types of functionality. Some such computer applications include enterprise resource planning ("ERP") applications.

[0003] Determining how to configure such large-scale computer applications is commonly a difficult task. Further, when a company selling such applications needs to make a proposal, the task is typically quite involved. Many application providers simplify the proposal process by providing application proposals that are very general and are not tailored to a specific customer. As a result, customers receiving the proposals may end up paying for application functionality that will not be used. Further, customers may not be fully apprised of the efforts and costs needed to implement the application beyond an initial installation.

[0004] Configuring and modifying configuration of such systems often involves the efforts of many highly trained individuals, any one of which may not know what the others are configuring. This may result in conflicting configuration settings that may not be discovered until after the system has gone live, or if already live, until system performance is adversely affected. Thus, the time and expense of configuring and maintaining large software systems can be significant. At the same time, an inconsistent configuration also can be costly to an enterprise using such a system if system performance is adversely affected.

Brief Description of the Drawin£s

[0005] FIG. IA and FIG. IB depict a system architecture and a process, respectively, in accordance with an example embodiment.

[0006] FIG. 1C and FIG. ID depict processes according to example embodiments.

[0007] FIG. IE is a block diagram of a system according to an example embodiment.

[0008] FIG. 2A is a block diagram of a system according to an example embodiment.

[0009] FIG. 2B is a block diagram of a system according to an example embodiment.

[0010] FIG. 3 is a block diagram of a system according to an example embodiment.

[0011] FIG. 4 is a block diagram of a system according to an example embodiment.

[0012] FIG. 5 is a flow diagram of a method according to an example embodiment.

[0013] FIG. 6 is a flow diagram of a method according to an example embodiment.

[0014] FIG. 7 is a flow diagram of a method according to an example embodiment.

[0015] FIG. 8 is a flow diagram of a method according to an example embodiment.

[0016] FIG. 9 is a flow diagram of a method according to an example embodiment. [0017] FIG. 10 is a block diagram of a computing system according to an example embodiment.

Detailed Description

[0018] Various embodiments described herein provide systems, methods, and software to reduce the complexity of in purchasing, configuring, modifying, and deploying software applications, such as large-scale enterprise resource planning ("ERP") applications. Some embodiments reduce the complexity of configuring such application by providing tools that place configuration setting decisions in a context where the decision-making is easier. Further, some embodiments may provide tools to input application configuration preferences that, when received, are utilized by one or more processes to make configuration decisions that are consistent across the application under configuration.

[0019] FIG. IA and FIG. IB depict a system architecture and a process, respectively, in accordance with an example embodiment. This architecture includes a user interface (10) and application configuration repository (20) within an application configuration environment (30), and an application execution repository (50) within an application execution environment (40). Based on a set of predefined application requirements (not shown), the application configuration environment (30) provides the user interface (10) to enable a user to assess one or more requirements for an application that the user wishes to configure (step 60). [0020] Via the user interface (10), the user is able to assess application requirements (112) from which the application configuration environment (30) can generate a configuration proposal (16) for presentation to the user (step 62). The user may then accept the proposal or revise it in accordance with the user's requirements. Based on rules and/or mappings associated with the pre-defined application requirements, the application configuration environment (30) may generate application configuration components (e.g., 122 and 26) to be utilized for implementing the application in accordance with the assessed requirements (step 64). The application may then be deployed by copying the application configuration components from the application configuration repository (20) to the application execution repository (50).

[0021] A pre-defined application requirement may include any stored application requirement (e.g., a listing of one or more business packages, business topics or business options) that the application configuration environment (30) makes available to the user for selecting or choosing via the user interface (10). An application configuration component may take any electronic form (e.g., content, metadata, scripts, executable code, schemas, etc.) that can be utilized by an application execution environment (40) to implement an application based on the user-provided requirements. The rules and/or mappings associated with the predefined application requirements allows the application configuration environment (30) to directly generate the appropriate application configuration component(s) based on a user's requirements.

[0022] Additionally, by storing the user's requirements (e.g., in a customer profile), the application configuration environment (30) is able to retrieve them later if a user wishes to revise the user's deployed application based on different requirements. As shown in FIG. 1C, the application configuration environment (30) allows a user to revise the user's requirements subsequent to generation and/or deployment of any application configuration components by providing the user interface (10) to enable the user to revise the user's requirements (step 70), generating a revised configuration proposal based on the revised requirements (step 72), and generating revised application configuration component(s) in accordance with the revised requirements (step 74) in a manner similar to that described above. [0023] In providing the user interface (10) to assist the user in assessing the requirements for an application, the application configuration environment (30) may present a three level scoping methodology to the user as shown in FIG. ID in accordance with an embodiment of the invention. The application configuration environment (30) may initially present the user with screens associated with high- level scoping (step 80), through which the user may select from a list of pre-defined business scenarios and/or job functions and answer specific key questions. Based on the user's response to the high-level scoping step (80), the application configuration environment (30) may generate a configuration proposal identifying pre-selected business packages and business topics in accordance with the user's requirements, and allow the user to revise the pre-selected packages and topics (step 82). Once the packages and topics are selected, the application configuration environment (30) may then allow the user to specify pre-defined business options associated with the selected packages and topics in accordance with the user's requirements (step 84).

[0024] FIG. IE is a block diagram of a system 100 according to an example embodiment. The system 100 includes an application configuration environment 102 and an application execution environment 104.

[0025] The application configuration environment 102 is a system 100 environment within which an application can be configured. However, the application will, or does, execute within the application execution environment 104. In some embodiments, this arrangement of the application configuration environment 102 and the application execution environment 104 separates the configuration of an application from the environment within which it executes. When an application configuration has been established, all or part of the configuration can then be deployed to the application execution environment 104. This deployment can occur to one or more separate instance of the application in the application execution environment 104. Although only a single application execution environment 104 is illustrated, multiple application execution environments 104 can exist, and the deployment can be made to one or more of the multiple application execution environments 104.

[0026] FIG. 2A is a block diagram of a system 200 according to an example embodiment. The system 200 includes a configuration scoping application 202, a data migration planner application 204, solution proposal and estimate engine 206, and the application configuration environment 102.

[0027] The configuration scoping application 202 typically is a software tool that executes on a computing device, such as a portable computer, on a same computing device within which the application configuration environment 102 exists, or on another computing device that can be communicatively coupled to the application configuration environment 102.

[0028] The configuration scoping application 202, when executed, typically presents a set of scoping questions to a user. The scoping questions are linked to one of many adaptation catalog entries. The adaptation catalog entries may include a representation of all of the solution capabilities of an application to be configured, and eventually executed. In some embodiments, the solution capabilities are hierarchically divided into areas, packages, topics, and options. There may be multiple areas, and each area may have multiple packages. Each package may have multiple topics, and each topic may have multiple options.

[0029] In some embodiments, such as in an example embodiment where the application to be configured is an ERP application, the adaptation catalog may provide in the area Sales, a package Customer Order Management that contains the topics Sales Order Quote, Sales Order, Sales Order Analysis, and others. On that level, one or more options typically exist such as Approval Processing. [0030] In the configuration scoping application 202, as stated above, each scoping question may be linked to an adaptation catalog entry. An adaptation catalog entry further includes a rule. These rules typically model dependencies between the areas, packages, topics, and options and corresponding solution capabilities of the application. A rule may specify required inclusion or exclusion of other areas, packages, topics, or options, or may require specification of further areas, packages, topics, or options. A rule may also specify a recommendation or default area, package, topic, or option. [0031] For example, a first example scoping question, "What is the primary focus of your business?" may have three possible answers including "Sales," "Service," and "Logistics." Such a first scoping question typically is aimed at identifying an area of business in which the application is going to be used. Answering "Sales" typically tells the configuration scoping application 202 that the area is "Sales" and a rule tied to the adaptation catalog entry for "Sales" specifies dependencies with packages, topics, and options and the corresponding solution capabilities of the application necessary or optional in using the application in a sales business. Such a rule can also specify that other packages, topics, and options and the corresponding solution capabilities be excluded.

[0032] Thus, when a user answers scoping questions, the configuration of the application is being performed. Further, when a question is answered that is associated with an adaptation catalog entry having a rule that excludes another area, package, topic, or option, that rule may be applied to eliminate questions from consideration. Conversely, when a question is answered that is associated with an adaptation catalog entry having a rule that requires another area, package, topic, or option, that same rule may be applied to determine a next question, or group of questions, to ask a user. However, in the event that a question is not answered that is linked to a rule providing defaults, the question may be skipped without adversely affecting the application configuration.

[0033] In some embodiments, such as the embodiment of the system 200, the scoping questions further include a group of questions that request information regarding legacy systems to be replaced or augmented by an application. This group of questions requests and receives input through one or more user interfaces of the configuration scoping application 202. The answers to these questions identify systems, applications operating the systems, and data stores, such as databases, file storage, and other data storage mechanisms, that hold data on the systems that is accessed by the applications. In some embodiments, the questions further receive data necessary for connecting to the data stores. This information, once obtained, is made available to the data migration planner 204, which determines, and provides as output, a data migration plan to move, copy, or integrate data from legacy applications and data stores to the new application. The solution proposal and estimate engine 206 typically executes to provide output after answers to the scoping questions have been received. The output generated by the solution proposal and estimate engine 206 may include one or more of an application proposal, a project roadmap to implement and configure the proposed application, and a cost estimate.

[0034] In some embodiments, the application proposal may include one or more proposed applications selected as a function of the scoping question answers. An application of an application proposal is typically selected when the application meets at least some customer needs as identified from the scoping question answers. The application proposal may further include a listing of functionality that meets identified needs of a customer and other functionality that is available. In yet further embodiments, the application proppsal may further include a hardware requirement listing specifying minimum hardware requirements for implementing the application of an application proposal.

[0035] In some embodiments, the project roadmap includes a listing of tasks that are needed to implement and configure a proposed application. The tasks within a project roadmap may include a timeline for performing the tasks. In some such embodiments, the project roadmap may include a time estimate to implement the application and bring the application online in a test or production environment. [0036] In some embodiments, the cost estimate includes one or more cost estimates to implement the application of an application proposal. Some such cost may include a cost to procure or license the application, a cost to purchase or lease hardware on which the application will execute, costs to hire contractors to implement and configure the application, costs to train personnel on using the application, and other costs associated with implementing or configuring the application. [0037] In some embodiments, an application proposal is generated by the solution proposal and estimate engine 206 as a function of received scoping question answers and the adaptation catalog entries associated with those answers. As discussed above, the rules associated with adaptation catalog entries may specify which portions of an application must be included or excluded. In some such embodiments, the included and excluded portion of the application are utilized by the solution proposal and estimate engine 206 to generate the application proposal. If more than one application is available, the application meeting more of a customer's needs with preconfigured content is selected for the application proposal.

[0038] In some embodiments, the project roadmap is generated by the solution proposal and estimate engine 206 as a function of the adaptation catalog entries associated with the received scoping question answers. In some embodiments, the adaptation catalog entries, or another data structure associated with adaptation catalog entries, details tasks associated with implementing one or more portion of the application. For example, when an adaptation catalog entry rule requires inclusion of a portion of the application, one or more implementation tasks may be associated with that portion of the application. The details of a task may specify relationships between tasks that can be performed in parallel or that certain tasks must be completed before one or more other tasks. The solution proposal and estimate engine 206 may then stitch together identified tasks to build the project roadmap.

[0039] In some embodiments, the details of a task may further include an time estimate to complete the task. The time estimates of the various tasks included in the project roadmap may then be used to build a timeline that provides additional information to a customer, such as a time estimate of how long it will take to implement the application.

[0040] In some embodiments, the details of a task may further identify a role of a person to perform the task. The role, in some embodiments, identifies a contractor that will perform the task. The role information associated with the tasks of a project roadmap may then be used to build a list of required resources to execute the project roadmap.

[0041] In some embodiments, the application proposal and the project roadmap are further utilized by the solution proposal and estimate engine 206 to generate the cost estimate. The solution proposal and estimate engine 206, in some such embodiments, utilized information associated with adaptation catalog entries that identifies a cost of one or more portion of the application. The solution proposal and estimate engine 206 may further obtain cost information associated with one or more hardware requirements of the application. Further, in building the cost estimate, the solution proposal and estimate engine 206 may obtain role information from the project roadmap and a cost associated with the task and role information to determine a cost to obtain services of one or more contractors. These cost factors are then assembled to form the cost estimate. [0042] In some embodiments, one or more of the application proposal, project roadmap, a data migration plan, and cost estimate are generated upon receipt of the scoping question answers. One or more of the application proposal, project roadmap, and cost estimate may be provided for viewing on a computer screen, printed on paper, emailed, made available via a login on the Internet, or made available via another medium.

[0043] FIG. 2B is a block diagram of a system 210 according to an example embodiment. The system 210 includes a portable computing device 232 including a configuration application 236, an application configuration dataset 234 stored in a memory, an application transaction dataset 238 and the configuration scoping application 202. The system 210 further includes the application configuration environment 102. Although the application configuration environment 102 is not illustrated within the portable computing device 232, in some embodiments, the application configuration environment 102 may reside within the portable computing device 232. In other embodiments, the application configuration environment 102, the configuration scoping application 202, the application configuration dataset 234, the configuration application 236, and the application transaction dataset 238 may all reside on a computing device other than the portable computing device 232.

[0044] The configuration application 236, in some embodiments, typically provides a set of tools via user interfaces to a user. The tools of the configuration application 236 may allow the user to modify answers to scoping question answers stored in an input cache 220 of the configuration scoping application 202, the application configuration dataset 234, and the application transaction dataset 238. The application configuration dataset 234 may be populated with data copied from a configuration repository 242 stored within a configuration workspace 228 of the application configuration environment 102. The application transaction dataset 238 may be populated with data copied either from a demonstration dataset stored in data repository 244 of the configuration workspace 228 or from the content repository 222.

[0045] Although the input cache 220 is illustrated within the configuration scoping application 202, the input cache 220 may exist separate from the configuration scoping application 202 within a memory of the portable computing device 232. In such embodiments, the input cache 220 may be populated with data copied from the scoping input database 226.

[0046] For the sake of understandability regarding several portions of the configuration scoping application 202 and the application configuration environment 102, these portions of the system 210 will be discussed followed by a more detailed discussion of the configuration application 236. [0047] The configuration scoping application 202, in some embodiments, may include a deduction engine 212, and an adaptation catalog 214'. In some embodiments, the configuration scoping application 202 may further include a solution proposal and estimate engine 216, a data migration planner 218, data migration tools 219, and an input cache 220. [0048] The application configuration environment 102, in some embodiments, may include an adaptation catalog 214, a content repository 222, and a configuration package repository 224. In some such embodiments, the application configuration environment 102 may further include a scoping input database 226, a configuration workspace 118, a deployment module 230, a configuration process 252, a fine tuning application 254, and a deployment datastore 240. [0049] The adaptation catalog 214 may include a representation of all of the solution capabilities of an application to be configured, and eventually executed. Each capability of an application to be configured is identified in an adaptation catalog 214 entry. The adaptation catalog 214 entries each may be identified as an area, package, topic, or option and may be organized in a hierarchy with a child identifying the parent. An example hierarchy is a "General Ledger" capability, which in some embodiments typically is a package having two topics, "cash based" and "accrual based" which are two application capabilities within the "General Ledger" capability. In some embodiments, the adaptation catalog 214' entries may be encoded in a markup language, such as extensible Markup Language ("XML"), or by another proprietary standard or open standards based encoding standard. [0050] The adaptation catalog 214 entries may further include scoping questions directed toward obtaining scoping information to determine what areas, packages, topics, and options are relevant to the user's needs. Additionally, the adaptation catalog entries typically include rules, the application of which can require inclusion or exclusion, or specify default inclusion or exclusion, of certain other areas, packages, topics, and options. Thus, because the areas, packages, topics, and options correlate to application capabilities, the inclusion, exclusion, and defaulting specifies what capabilities will be enabled and disabled in the application when deployed by the deployment module 230.

[0051] In some embodiments, rules and entries in the adaptation catalog can be linked to a configuration package that exists in the configuration package repository 224. A configuration package includes one or more configuration settings that enable or disable functionality of the application when deployed by the deployment module 230 or by a configuration process within the application configuration environment 102 when configuring the application within the configuration workspace 228. A configuration package can further be linked to one or more content items or content item definitions stored in the content repository 222. Some such content types include report layouts, forms, user interfaces, communication specifications, documentation, and other content that can be used in an application when deployed. A communication specification can include an XML schema, an EDI schema and connectivity information, mappings between file layouts and application data storage mechanisms, such as databases, and other similar communication specifications.

[0052] In one embodiment, the rules may be applied by the deduction engine

212 of the configuration scoping application 202. The configuration scoping application 202 typically presents a user interface to a user that requests answers to questions. The questions asked via the user interface are identified by the deduction engine 212 based on the adaptation catalog 214'. The adaptation catalog 214' is typically a copy of the adaptation catalog 214 of the application configuration environment 102. When an answer is received, the answer may be stored in the input cache 220 of the configuration scoping application 202. The deduction engine 212 then typically applies the rule associated with the adaptation catalog 214' entry of the question asked to the received answer. Through the application of the rule, in view of answers already received and rules already applied, the deduction engine 212 may be configured to identify a next question to ask. The identified question typically is then presented to the user through the user interface. This process may be configured to continue until either all of the questions have been asked or the user is out of time. If questions remain that have not been answered, the process can be continued at a later time or rules specifying default areas, packages, topics, and options in order to supply enough information to allow deployment of the application in a functional form. [0053] In some embodiments, the configuration scoping application 202 may further include a data migration planner 218. In such embodiments, one or more additional scoping questions typically can be asked. These additional scoping questions may be directed toward obtaining information from the user about legacy systems and how data is stored within them. In some embodiments, the questions simply ask what systems are currently in use. In other embodiments, the questions are more detailed to obtain information such as what type of database a system is utilizing and what type of customization has been made or custom systems developed. In some embodiments, the scoping questions request information to identify one or more of data source types, data source connectivity information, location of certain data items within a data source, data item types, and information describing one or more data items. The data migration planner 218 typically uses the answers to these additional questions to propose a data migration plan to the new application.

[0054] The data migration planner 218, in some embodiments, may evaluate the answers to the scoping questions to identify legacy systems utilized and how the data is stored. The data migration planner 218 may also evaluates the scoping question answers to identify what data is needed, and in what form, in an application to be deployed, or otherwise proposed. The data migration planner 218 then typically makes a data migration plan recommendation utilizing one or more data migration tools 219. A copy of the data migration plan may be stored in the configuration workspace 228 or other data storage location accessible within or to the application configuration environment 102.

[0055] The data migration tools 219, in some embodiments, typically include a representation of one or more tools that may be utilized to migrate data from a legacy application to the new application. Such tools may include legacy application plug-ins that execute within a legacy system to move or copy data. Some tools also include a data migration process recommendation for extraction of files from a legacy system and uploading to the files to the data stores of the new application. Some other tools include integration tools that operate between a legacy application and the new application to facilitate sharing of data between the two applications. Other tools and tool types are contemplated as well. Such other tools typically include tools developed by third parties that leverage an open architecture of the system 210 to facilitate data migration and integration between a legacy application and the new application.

[0056] In some embodiments, the configuration scoping application 202 includes a solution proposal and estimate engine 216. The solution proposal and estimate engine 216 may be used in a sales situation. For example, if a sales person is discussing with a sales lead what a certain application product can do for the sales lead, the sales person typically can utilize the configuration scoping application 202 to obtain information about the needs of the sales lead via the scoping questions. The scoping question answers may then be utilized by the solution proposal and estimate engine 216 to make an initial determination of what will be involved if the sales lead decides to purchase the application. The solution proposal and estimate engine 216 normally is configured to output information for the sales lead to make several determinations, such as the size of effort necessary to implement or transition to the application from legacy system, the cost involved, and cost. In some embodiments, the output of the solution proposal and estimate engine 216 outputs one or more of an implementation cost estimate, an application solution proposal, and a recommended project roadmap. In some embodiments, the solution proposal and estimate engine 216 outputs a proposal for one or more other options, application descriptions, sales literature, benefit statements of using the application, and addition documents, such as a proposal of key performance indicators the application can monitor to assist in managing the application or enterprise of the sales lead.

[0057] After the scoping question have been answered, the answers, and any other information obtained from a sales lead or other user of the configuration scoping application 202, the information typically is uploaded to the application configuration environment 102. However, in embodiments, where the configuration scoping application 202 executes on the same computing device as the application configuration environment 202, the scoping question answers and other information may be stored directly to the application configuration environment 102. [0058] When the configuration question answers and other information is uploaded, or otherwise stored to the application environment 102, the scoping question answers are stored to the scoping input database 226. The scoping question answers, in some instances, will be referred to interchangeably as the "scoping information."

[0059] After the scoping information is within the scoping input database

226, the configuration process 252 within the application configuration environment 102 may execute to begin configuring an application in the configuration repository of the configuration workspace 228. The configuration repository 242 may include a set of configuration tables that mirrors, at least in part, the configuration tables the application. The configuration repository 242 may include a set of configuration tables for each of multiple instances of the application to allow use of the application configuration environment 102 to configure multiple application instances. Although the configuration process 252 is illustrated within the application configuration environment 102, the configuration process 252 may be a standalone application.

[0060] In some embodiments, the scoping input typically identifies a type of the application under configuration. In such instances, the application type identification informs the configuration process 252 of what configuration tables to instantiate, if needed, which configuration tables to populate with data, and determine one or more configuration packages to instantiate in the configuration repository. This allows the configuration process 252 to be independent of any particular application type. More simply stated, the configuration process 252, in some embodiments, may operate to configure virtually any application type in the configuration workspace. [0061] The configuration process 252 may further be configured to determine one or more configuration packages to instantiate in the configuration workspace 228. Configuration packages, in some embodiments, may include one or a set of configuration settings to enable or disable certain capabilities of the application. Configuration packages, as mentioned above, may be linked to adaptation catalog 214 entries and rules associated with adaptation catalog entries. Thus, the configuration process 252 queries the scoping information in the scoping input database 226 to identify configuration packages to instantiate. Thus, the configuration process 252 typically makes technical application configuration decisions while it executes without requiring further input from a user. [0062] In some embodiments, two or more of the configuration packages identified for deployment by the configuration process 252 may have conflicting configuration settings. Such conflicts can be handled in several ways. In one embodiment, the conflicts may be handled and corrected according to a rule associated with an adaptation catalog 214 entry. Such a rule may be defined to specify how the configuration process 252 will resolve the conflict while populating the configuration tables in the configuration workspace 228. In other embodiments, configuration packages may include an associated rule that is applied by the configuration process 252 to identify conflicting configuration settings and how to resolve an identified conflict. In yet further embodiments, the configuration process 252 may identify conflicting configuration settings when two configuration packages attempt to modify the same configuration setting in a conflicting manner. In such instances, a conflict notice may be provided to one or more individuals. Another embodiment includes two or more of these solutions for handling conflicting configuration settings. However, if conflicts still exist after the configuration process completes its execution, a user may utilize the fine tuning application 254, or directly modify the configuration tables in the configuration workspace 228, to resolve the conflicts. [0063] In some embodiments, the configuration package repository 224 may be stored within the content repository 222. The content repository 222 typically further stores definitions of report layouts, forms, user interfaces, communication specifications, documentation, and other content that can be used in an application when deployed. A communication specification may include an XML schema, an EDI schema and connectivity information, mappings between file layouts and application data storage mechanisms, such as databases, and other similar communication specifications.

[0064] Based on rules associated with adaptation catalog 214 entries and the scoping information, the configuration process 252, in some embodiments, may be configured to further identify content to be deployed. This identified content my either be copied to the configuration workspace 228 or, in some embodiments, a reference may be placed in the configuration workspace 228 that informs the deployment module 230 of content to be deployed.

[0065] As mentioned above, the fine tuning application 254 may be utilized to modify configuration settings where conflicts exist between two or more configuration settings. However, the fine tuning application 254 may further be used to modify configuration settings where conflicts do not exist. Fine tuning is commonly helpful to customize the configuration based on specific needs or desires of an enterprise that utilizes, or will utilize, the application under configuration. [0066] The fine tuning application, in some embodiments, provides one or more user interfaces for a user to view and modify the configuration settings. In some embodiments, the one or more user interfaces typically allow a user to drill down to the various configuration settings in a hierarchical manner. The hierarchy may be based on the areas, packages, topics, and options selected for deployment from the adaptation catalog by the deduction engine 212 and utilized by the configuration process 252 to select configuration packages to populate the configuration tables. Such embodiments typically allow a user to view the configuration settings in the context of the intended use of the application. In other embodiments, the user interface may further include a scripting screen, from which a script may be executed to modify configuration settings. In some embodiments, the scripting screen may be configured to operate on scripts encoded in a query language, such as Structured Query Language ("SQL").

(0067] In some embodiments, demonstration data may exist to facilitate the instantiation of a demonstration instance of the application for a sales lead, training session, or other purpose. The demonstration data, in some embodiments, may be linked to one or more configuration packages from the configuration package repository 224. The demonstration data typically exists in the content repository 222 so that it may be copied into a set of application tables in the configuration workspace 228. These tables typically hold such data as one or more of transactional data, operational data, master data, or other data that can exist in the application when the application is ready for execution or is executed. [0068] Once the demonstration data is copied to the configuration workspace 228, that data may be fine-tuned to more closely match the intended use of the demonstration data. For example, the system may be configured so that a sales person, or other individual, can fine-tune demonstration data values to more closely match a sales lead's expectations of the application. This fine-tuning may include modifying sales order documents in the demonstration data to include a name, address, and logo of the sales lead's enterprise, or other similar modifications to the demonstration data.

[0069] In some embodiments, before the deployment module 230 can deploy the application configuration, the configuration process 252 typically provides verification that the configuration is ready for deployment. In some embodiments, the verification may include a compile-like process that performs one or more checks on the configuration. In some embodiments, the checks typically include a semantic check to ensure all configuration settings conform to a configuration setting semantic specification and a syntax check to ensure all configuration settings conform to a configuration setting syntax specification. This typically includes ensuring all necessary configuration settings have been set. In these, and other embodiments, the checks may also include a foreign key check. A foreign key check typically is performed where a configuration setting of a configuration table refers to a value in another configuration table or other data store relevant to the configuration setting. This may include a check to ensure a user interface definition, or other content type that is referred to a configuration setting does in fact exist and is ready for deployment.

[0070] After the application has been configured in the configuration workspace and the demonstration data, if any, is ready, and the configuration process 252, if necessary, has performed its verification process, the configuration may be deployed by the deployment module 230. The deployment module 230 may be configured to deploy configuration settings to a baseline application that has already been instantiated in an application execution environment. In some embodiments, the deployment module may include a configuration setting deployment process, an activation process, and a data deployment process. The configuration setting deployment process typically copies configuration settings from the configuration tables in the configuration workspace 228. The data deployment process may be configured to execute if there is demonstration data in the configuration workspace 228. If there is demonstration data, the data typically is copied from the configuration workspace 228 to application tables in the application execution environment. Some embodiments further utilize the activation process.

[0071] The activation process, in some such embodiments, may be configured to execute to activate the application in the application execution environment after it has been successfully deployed. In some instances, the activation process may require an activation key, message, code, or other authorization from an activation authority to activate the application. The activation authority may include one or more of a number of individuals or entities. An example of an activation authority is an entity selling the application to be activated. This activation functionality requiring an activation key or other mechanism may be utilized for several purposes. Some such purposes include allowing the entity selling the application to ensure the application is properly configured, has passed certain testing necessary for the entity to ensure it will meet guaranteed service level agreements or objectives, for billing purposes, or other purposes that can benefit from such an activation process.

[0072] In some embodiments, the deployment module 230 may further include a delta deployment process. The delta deployment process is generally relevant only after an application has already been deployed. When an application is deployed, or subsequently modified, the scoping information in the scoping input database 226 is updated to enable tracking of a current configuration of a deployed application. In embodiments including the delta deployment process, the scoping information typically may be tracked on a historical basis to at least allow a view of a current configuration and a modified configuration not yet deployed, if applicable. The delta deployment process may then utilize the historical tracking of the application configuration to identify changes between the current application configuration and the modified configuration not yet deployed. The delta deployment process then deploys only the changes to the application configuration. [0073] Some embodiments of the application configuration environment 102 may further include the deployment datastore 240. The deployment datastore 240 typically stores a representation of one or more application configurations of applications that have been deployed. The representations of the one or more application configuration may be stored or updated in the deployment datastore 240 by the deployment module 230 upon successful deployment of an application. [0074] A representation of an application configuration typically includes data representative of the application configuration settings. In some embodiments, the representation may further include data representative of content deployed to the application. [0075] The deployment datastore 240, in some embodiments, may be updated upon each configuration or content modification of a deployed system. In some embodiments, the deployment datastore may further include a versioning mechanism that maintains not only a current configuration representation, but also historical representations.

[0076] In some embodiments, the deployment datastore 240, or a current copy thereof, may be maintained by an entity that developed, or otherwise offers for sale, the application. The deployment datastore 240 may be used by the entity to monitor current application usage, perform billing processes as a function of a current application configuration, provide application upgrade information based on portions of the application or content utilized, and for other purposes. In some embodiments, the entity may provide application updates, bug fixes, or other upgrades directly to a deployed application instance. Such updates, bug fixes, or other upgrades may be identified as relevant to a particular application instance as a function of the configuration representation in view of adaptation catalog 214 entries.

[0077] As described above, the configuration application 236, in some embodiments, may provide a set of tools via user interfaces to a user. The tools of the configuration application 236 typically allow the user to modify answers to scoping question answers stored in an input cache 220, the application configuration dataset 234, and the application transaction dataset 238. The application configuration dataset 234 may be populated with data copied from the configuration repository 242. The application transaction dataset 238 may be populated with data copied from either a demonstration dataset stored in the data repository 244 or from the content repository 222. The input cache 220, if separate from the configuration scoping application 202 may be populated with scoping information copied from the scoping input database 226.

[0078] Through use of the configuration application 236 user interfaces, a user may modify data within the application transaction dataset 238 to customize the data used of a demonstration application to more closely reflect how a sales lead's enterprise will use the application. For example, through modifying the transaction data, data displayed within the demonstration may include orders with products, customers, addresses, countries, and other details that truly reflect those of the sales lead's enterprise.

[0079] Further, use of the configuration application 236 user interfaces may also allow a user to further refine an application configuration to more closely match the needs of a customer or sales lead. This can include a user taking a copy of an application configuration to work on while away from a connection to the application to be configured or application configuration environment 102, such as when traveling.

[0080] In some embodiments, the configuration application 236 may further include a warehouse-modeling module. The warehouse-modeling module may include a deduction engine 212 and a subset of an adaptation catalog 214 as discussed above, or may leverage the deduction engine 212 and adaptation catalog 214' of the configuration scoping application 202 if present on the portable computing device 232. In such embodiments, the adaptation catalog 214 (or 214') may further include one or more area, package, topic, option hierarchies of adaptation catalog 214 entries. The user may answer scoping questions to identify and define a warehouse layout and processes utilized within a warehouse to be modeled. Such warehouse modeling data, once defined, may be copied to the data repository. In some embodiments, such information is similar to configuration settings as a warehouse layout is not subject to frequent change. However, warehouse layouts are generally unique to each warehouse. Thus, warehouse data may be stored in the data repository and may be deployed to an application data table instead of a configuration table.

[0081] FIG. 3 is a block diagram of a system 300 according to an example embodiment. The system 300 includes the application configuration environment 102 as discussed above with regard to FIG. IE, FIG. 2A, and FIG. 2B. The system 300 further includes an application execution environment 104, a data migration process 302, legacy data 304, and application instance data 306. [0082] The application execution environment 104 is a data processing environment within which an application, or an application to be deployed, can execute. When deploying an application, the deployment module 230 needs to know what application execution environment 104 and what application instance within that environment to deploy to. In embodiments including only one application execution environment 104, the application execution environment 104 may already be known. Similarly, in an application execution environment including only a single application instance, the instance may already be known. [0083] Each instance of the application (i.e., application instances A, B, . . .

X) typically includes a set of identical configuration tables which can include distinct configuration settings from one another. In some embodiments, multiple instances of the application exist to provide a development instance, a test instance, and a production instance. In such embodiments where there are multiple application instances, the deployment module 230 may be configured to deploy the configuration settings from one of the application instances in the application execution environment 104 to another application in the same or another application execution environment 104. Although the deployment module 230 is illustrated as being a part of the application configuration environment 102, the deployment module 230, in other embodiments, can be a standalone application or a part of another application or process.

[0084] The data migration process 302, in some embodiments, in configured to migrate legacy data 304 to application instance data 306. In some such embodiments, the data migration process 302 may be a legacy application plug-in, or other process, that executes within the legacy application to migrate the data. In other embodiments, the data migration process 302 may be a plug-in, or other process, that executes within an application instance to migrate the data. In yet further embodiments, the data migration process 302 may be a data integration process that makes data from the legacy system available to an application instance and vice-versa.

[0085] The data migration process 302, in some embodiments, is configured to identify data to migrate based upon the data migration plan stored in the configuration workspace 228 of the application execution environment 102. In some such embodiments, the data migration plan may identify not only data items to move, but any data item type conversions that might be necessary, such as converting a string data item type to an integer or a string data item length. [0086] Some embodiments may include more than one data migration process 302. In such embodiments, the data migration processes may be of varying types. For example, one data migration process 302 may be an application plug-in, while another data migration process 302 may be a standalone application that executes to move or copy data between applications.

[0087] In some embodiments, the data migration process 302 may be leveraged for additional purposes. One such purpose may be to move data from application instance, such as application instance A, to another application instance, such as application instance B. Such a move may be useful when performing application instance upgrades or for copying data from a production instance to a test or development instance.

[0088] After the application has been configured in the configuration workspace 228, as illustrated and described with regard to FIG. 2B and FIG. 3, and the demonstration data, if any, is ready, the configuration may be deployed by the deployment module 230. Detail of the deployment module 230 is provided in FIG. 4. FIG. 4 is a block diagram of a system 420 according to an example embodiment. The system 420 typically includes the deployment module 420 and the application execution environment 104.

[0089] The deployment module 230 may include a configuration setting deployment process 404, an activation process 406, and a data deployment process 408. Some embodiments of the deployment module may further include a delta deployment process 410.

[0090] The application execution environment 104 may includes a baseline application 414. The baseline application 414 is an application that has been instantiated, but has not been configured. The baseline application may include a set of configuration tables 416 that will be populated by the deployment module 230. The baseline application 414 may further include other tables, data structures, and storage locations that may be populated by the deployment module 230 with one or more of demonstration data, application data, content, or other data. [0091] The deployment module 230, when executed, typically operates to deploy an application configured in the application configuration environment. Deployment is typically performed by one or more of the processes of the deployment module 410. These processes may include the configuration setting deployment process 404, the data deployment process 208, the activation process 406, and the delta deployment process 410. Some embodiments of the deployment module 230 may include one or more of these processes.

[0092] The configuration setting deployment process 404 typically deploys configuration settings to the configuration tables 416 of the baseline application 414 if the baseline application 414 has already been instantiated. However, in some embodiments, if the baseline system 414 has not been instantiated, the configuration setting deployment process 404, or other process of the deployment module may instantiate the baseline system 414 or call another process that will instantiate the baseline system 414. The deployment of the configuration settings may include a copying of configuration settings from the configuration tables of the configuration repository 242, as shown and described with reference to FIG. 2B, to the configuration tables 416 of the baseline application. In some embodiments, a configuration setting that is copied to the baseline application 414 may refer to an item of content or data stored in the data repository 244, of FIG. 2B, or the content repository 222, of FIG. 2B. In some such instances, the configuration setting deployment process 404 may call a method of the data deployment process 408 to cause that data or content to be copied to the baseline application 414. In other embodiments, that data or content may be copied when the data deployment process 408 is executed at either an earlier or a later time.

[0093] The data deployment process 408 may be executed if there is demonstration data in the configuration workspace 228 or if there is content to deploy from the data repository 244 of FIG. 2B or the content repository 222 of FIG. 2B. If there is demonstration data, the data may be copied from the configuration workspace 228 to application tables, data structures, storage locations, or other data stores in the application execution environment 104. If a proper table, data structure, storage location, or other data store does not exist in the application execution environment, the data deployment process, in some embodiments, is configured to execute, or call a method of another module, to cause that data location to be created or allocated.

[0094J Some embodiments of the deployment module 230 may further include the activation process 406. The activation process, in some embodiments, is configured to execute to activate the baseline application 414 after it has been successfully deployed. In some instances, the activation process 414 may require an activation key, message, code, or other authorization from an activation authority to activate the configured baseline application 414. The activation authority may include one or more of a number of individuals or entities. An example of an activation authority may include an entity selling the baseline application 414 to be activated.

[0095] This activation process 406 and associated functionality may be utilized for several purposes. Some such purposes may include allowing the entity selling the application to ensure the application is properly configured, has passed certain testing necessary for the entity to ensure it will meet guaranteed service level agreements or objectives, for billing purposes, or other purposes that may benefit from such an activation process. [0096] In some embodiments, the activation key, or other activation signal may be received over a network, such as the Internet. In other embodiments, the activation key, or other activation signal, may be manually input into an administration user interface or configuration table of the configured baseline application 414.

[0097] In some embodiments, the deployment module 230 may further include the delta deployment process 410. The delta deployment process is typically only relevant after an application has already been deployed. When an application is deployed, or subsequently modified, a representation of the application configuration may be stored or updated in the deployment datastore 240 as described and illustrated with reference to FIG. 2B. This may enable tracking of a current configuration of a deployed application. In embodiments including the delta deployment process 410, the scoping information may further be tracked on a historical basis to at least allow a view of a current configuration and a modified configuration not yet deployed, if applicable. The delta deployment process 410 may then use that historical tracking of the application configuration to identify changes between the current application configuration and the modified configuration not yet deployed. The delta deployment process 410 may then only deploy the changes to the application configuration and any additional content needed or otherwise referenced by the new application configuration. [0098] FIG. 5 is a flow diagram of a method 500 according to an example embodiment. The example method 500 includes determining a scoping question to ask as a function of a response to one or more other scoping questions. In some embodiments, possible responses to one or more scoping questions are associated with one or more application configuration packages 502. The method 500 may further include selecting one or more application configuration packages for deployment as a function of one or more received scoping question responses 504. In some embodiments, an application configuration package includes predefined content, such as demonstration data. [0099] In some embodiments, a configuration package is selected for deployment as a function of another configuration package previously selected as a function of one or more received scoping question responses a configuration package selection constraint, or rule, of the first configuration package. In some embodiments, a configuration package selection constraint can require or exclude selection of an application configuration package. Where a first application configuration package selection constraint requires selection of a second application configuration package, the first application configuration package, in some embodiments, leverages functionality of the second application configuration package.

[00100] FIG. 6 is a flow diagram of a method 600 according to an example embodiment. The example method 600 includes receiving and storing customer information including information detailing customer data from legacy applications 602. The method 600 further includes determining a plan to migrate the customer data from the legacy applications to a target application as a function of the received customer information and the target application 604. Some embodiments further include asking data migration planning questions and receiving answers through a user interface, wherein the received answers identify one or more customer data migration preferences or requirements.

[00101] The data migration planning question answers identify customer data source information. The customer data source information can include one or more of data source type, data source connectivity information, locations of data items within the data source, data item types, data item descriptive information, and other data source information. In some embodiments, the data migration planning question answers provide information to identify data sources within one or more customer legacy applications and target application data destinations for the customer data.

[00102] The method 600, in yet further embodiments, includes providing a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application, wherein recommended data migration tools are identified as a function of the data migration planning question answers and scoping information. The plan to migrate the customer data from the legacy application to a target application can include a file format for at least a portion of the customer data and identify a data loading process to load data from a file in the file format to the target application.

[00103] FIG. 7 is a flow diagram of a method 700 according to an example embodiment. In some embodiments, the example method 700 includes receiving customer information including information detailing customer data processing preferences 702 and processing the customer information to identify portions of an application related to the customer data processing preferences 704. The method 700 also typically includes generating one or more application proposals as a function of the identified portions of the application 706. [00104] In some such embodiments of the method 700, the customer data processing preferences include one or more data processing requirements. [00105] The one or more application proposals may include an application solution proposal that meets at least some of the customer data processing preferences. The one or more application solution proposals may include not only a proposed application, but also a proposed configuration of the proposed application. [00106] An application solution proposal may further include a project plan for implementing and configuring the proposed application. Some embodiments include preconfigured application content in the application solution proposal selected as a function of the received customer information. [00107] FIG. 8 is a flow diagram of a method 800 according to an example embodiment. The example method 800 includes storing, in a memory device, a scoping input database, wherein the scoping input database holds one or more customer profiles 802 and storing, in the memory device, a content data store 804. The method 800 may further include storing, in the memory device, an adaptation catalog, wherein the adaptation catalog links content stored in the content data store to possible customer profiles stored in the scoping input database 806. The method 800 may also include executing one or more configuration processes, wherein the one or more configuration processes execute to instantiate an application configuration in a workspace area of the memory device, wherein the application configuration includes content selected as a function of a customer profile from the scoping input database and the adaptation catalog 808. [00108] The customer profile data may be received via a configuration application that receives answers to a dynamic set of questions selected from a universe of questions as a function of question answers and the adaptation catalog. Some embodiments of the method 800 may further include receiving application configuration fine-tuning settings. Additional embodiments may also include storing received application configuration fine-tuning settings in a customer profile. Yet another embodiment of the method 800 may include storing a customer profile in a customer profile database.

[00109] FIG. 9 is a flow diagram of a method 900 according to an example embodiment. In some embodiments, the example method 900 includes configuring an application in an application configuration environment 902 and executing a deployment module to deploy the application to an application execution environment, which includes a baseline application 910. In some embodiments, the deployment module executes by deploying configuration settings from the configuration repository to the application execution environment 912, and executing an activation process, wherein the activation process activates functionality of the baseline application as a function of the configuration settings stored in the configuration repository 914. The deployment module further executes by deploying data from the data repository to one or more data stores in the application execution environment 916.

[00110] In some embodiments, the baseline application in the application execution environment includes a plurality of objects. In some such embodiments, the activation process activates functionality of the baseline application by calling an activation method of one or more objects selected by the activation process as a function of the configuration settings stored in the configuration repository. [00111] Some embodiments of the method 900 further include storing, in the application configuration environment, at least a current configuration model of the baseline application. The current configuration model can be used in some embodiments to determine differences between a current state of the baseline application configuration as a function of the current configuration model and a current state of the application configuration environment. Then the configuration setting deployment process, the activation process, and the data deployment process can be executed to deploy only the differences between the current state of the baseline application and the current state of the application configuration environment.

[00112] In some embodiments, the deployment module further includes a process to receive deployment commands within the application configuration environment. The deployment commands can include commands identifying portions of an application to deploy and a target application execution environment. The target application execution environment can include a test environment, development environment, production environment, reporting environment, or other environment.

[00113] FIG. 10 is a block diagram of a computing system according to an example embodiment. In one embodiment, multiple such computer systems are utilized in a distributed network to implement multiple components in a transaction- based environment. An object-oriented architecture may be used to implement such functions and communicate between the multiple systems and components. One example computing device in the form of a computer 1010, may include a processing unit 1002, memory 1004, removable storage 1012, and non-removable storage 1014. Memory 1004 may include volatile memory 1006 and non-volatile memory 1008. Computer 1010 may include - or have access to a computing environment that includes - a variety of computer-readable media, such as volatile memory 1006 and non-volatile memory 1008, removable storage 1012 and nonremovable storage 1014. Computer storage includes random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM) & electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (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 capable of storing computer-readable instructions. Computer 1010 may include or have access to a computing environment that includes input 1016, output 1018, and a communication connection 1020. The computer may operate in a networked environment using a communication connection to connect to one or more remote computers, such as database servers. The remote computer may include a personal computer (PC), server, router, network PC, a peer device or other common network node, or the like. The communication connection may include a Local Area Network (LAN), a Wide Area Network (WAN) or other networks.

[00114] Computer-readable instructions stored on a computer-readable medium are executable by the processing unit 1002 of the computer 1010. A hard drive, CD-ROM, and RAM are some examples of articles including a computer- readable medium. The term "computer readable medium" is also used to represent carrier waves on which the software is transmitted. For example, a computer program 1025 capable of providing a generic technique to perform access control check for data access and/or for doing an operation on one of the servers in a component object model (COM) based system according to the teachings of the present invention may be included on a CD-ROM and loaded from the CD-ROM to a hard drive. The computer-readable instructions allow computer 1010 to provide generic access controls in a COM based computer network system having multiple users and servers. [00115] In the foregoing Detailed Description, various features are grouped together in a single embodiment to streamline the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

[00116] It will be readily understood to those skilled in the art that various other changes in the details, material, and arrangements of the parts and method stages which have been described and illustrated in order to explain the nature of this invention may be made without departing from the principles and scope of the invention as expressed in the subjoined claims.

Claims

ClaimsWhat is claimed is:

1. A system for configuring an application, comprising: a configuration server; and a data store communicatively linked to the configuration server, wherein the configuration server provides a user interface to assess one or more requirements for an application based on a set of pre-defined application requirements, wherein the configuration server generates a configuration proposal based on the one or more assessed requirements, the configuration proposal specifying a subset of the set of pre-defined application requirements correlating with the one or more assessed requirements, wherein the configuration server stores the one or more assessed requirements in the data store, and wherein the configuration server generates one or more application configuration components correlating with the specified subset of pre-defined application requirements to implement the application in accordance with the one or more assessed requirements.

2. The system of claim 1, wherein the configuration server retrieves, after the generating of the one or more application configuration components, the stored requirements from the data store, wherein the configuration server provides the user interface to revise the stored requirements for the application based on the set of pre-defined application requirements, wherein the configuration server generates a revised configuration proposal based on the revised requirements, the revised configuration proposal specifying a revised subset of the set of pre-defined application requirements correlating with the revised requirements, and wherein the configuration server generates a revised one or more application configuration components correlating with the revised subset of pre-defined application requirements to implement the application in accordance with the revised requirements.

3. The system of claim 1 or 2, wherein the one or more assessed requirements are stored in association with a customer profile.

4. The system of any one of claims 1 to 3, wherein pre-defined business scenarios are provided to a user for selection via the user interface to assist the user in assessing the one or more requirements for the application.

5. The system of any one of claims 1 to 4, wherein pre-defined job functions are provided to a user for selection via the user interface to assist the user in assessing the one or more requirements for the application.

6. The system of any one of claims 1 to 5, wherein the one or more application configuration components are deployed by being copied from an application configuration repository to an application execution repository.

7. The system of any one of claims 1 to 6, wherein a plurality of business packages, business topics or business options are provided pre-selected to a user via the user interface to assist the user in assessing the one or more requirements for the application.

8. The system of claim 7, wherein the configuration server determines, upon the user deselecting one or more of the plurality of pre-selected business packages, business topics or business options, whether to deselect any other of the pre-selected business packages, business topics or business options as a result of the user's deselection.

9. A system for configuring an application, comprising: means for providing a user interface to assess one or more requirements for an application based on a set of pre-defined application requirements; means for generating a configuration proposal based on the one or more assessed requirements, the configuration proposal specifying a subset of the set of pre-defined application requirements correlating with the one or more assessed requirements; and means for generating one or more application configuration components correlating with the specified subset of pre-defined application requirements to implement the application in accordance with the one or more assessed requirements.

10. A method comprising: determining a scoping question to ask as a function of a response to one or more other scoping questions, wherein possible scoping question responses are associated with one or more application configuration packages; and selecting one or more application configuration packages for deployment as a function of one or more received scoping question responses.

11. The method of claim 10, wherein an application configuration package includes predefined content.

12. The method of claim 10 or 11, wherein a second configuration package is further selected as a function of: a first configuration package selected as a function of the one or more received scoping question responses; and a configuration package selection constraint of the first configuration package.

13. The method of claim 12, wherein the configuration package selection constraint of the first configuration package requires selection of the second application package.

14. The method of any one of claims 10 to 13, wherein a second application configuration package is not selected for deployment as a function of one or more exclusion constraints associated with a first selected application configuration package.

15. A system comprising: a processor; a memory operatively coupled to the processor; a configuration package repository stored in the memory, wherein the configuration package repository includes one or more configuration packages; an adaptation catalog stored in the memory, wherein the adaptation catalog includes scoping questions associated with one or more of the configuration packages; a configuration scoping application that executes on the processor to: determine a scoping question to ask as a function of a response to one or more other scoping questions, wherein possible scoping question responses are associated with one or more of the application configuration packages; and select one or more of the application configuration packages for deployment as a function of one or more received scoping question responses.

16. The system of claim 15, wherein an application configuration package includes an association to content in a content repository.

17. The system of claim 16, wherein content includes application demonstration data.

18. The system of any one of claims 15 to 17, wherein a second configuration package is further selected as a function of: a first configuration package selected as a function of the one or more received scoping question responses; and a configuration package selection constraint of the first configuration package.

19. The system of claim 18, wherein the configuration package selection constraint of the first configuration package requires selection of the second application package.

20. The system of claim 18 or 19, wherein application functionality associated with the first application configuration package leverages functionality of the second application configuration package.

21. A system comprising: a customer profiling application, wherein the customer profiling application receives and stores customer information including information detailing customer data from legacy applications; and a data migration planning process, wherein the data migration planning process determines a plan to migrate the customer data from the legacy applications to a target application.

22. The system of claim 21, wherein: the customer profiling application asks questions and receives answers through a user interface; and the received answers identify one or more customer data migration preferences.

23. The system of claim 21 or 22, wherein the data migration planning process identifies customer data source information including one or more of: data source type; data source connectivity information; locations of data items within the data source; data item types; and data item descriptive information.

24. The system of any one of claims 21 to 23, wherein the data migration process identifies data sources within one or more customer legacy applications and target application data destinations for the customer data.

25. The system of any one of claims 21 to 24, wherein the data migration process provides a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application.

26. A method comprising: receiving and storing customer information including information detailing customer data from legacy applications; and determining a plan to migrate the customer data from the legacy applications to a target application as a function of the received customer information and the target application.

27. The method of claim 26, further comprising: asking data migration planning questions and receiving answers through a user interface, wherein the received answers identify one or more customer data migration preferences.

28. The method of claim 26 or 27, wherein the data migration planning question answers identify customer data source information including one or more of: data source type; data source connectivity information; locations of data items within the data source; data item types; and data item descriptive information.

29. The method of any one of claims 26 to 28, wherein the data migration planning question answers provide information to identify data sources within one or more customer legacy applications and target application data destinations for the customer data.

30. The method of any one of claims 26 to 29, further comprising: providing a recommendation of one or more data migration tools to migrate data from the customer legacy applications to the target application, wherein recommended data migration tools are identified as a function of the data migration planning question answers.

31. A system comprising: a customer profiling application, wherein the customer profiling application receives and stores customer information including information detailing customer data processing preferences; and a solution proposal and estimate engine, wherein the solution proposal and estimate engine processes the customer information to produce output including one or more application proposals.

32. The system of claim 31 , wherein the customer data processing preferences include one or more data processing requirements.

33. The system of claim 31 or 32, wherein the one or more application proposals include an application solution proposal that meets at least some of the customer data processing preferences.

34. The system of claim 33, wherein the application solution proposal includes a proposed application and a configuration for the proposed application.

35. The system of claim 34, wherein the one or more application solution proposals further include a project plan for implementing and configuring the proposed application.

36. The system of claim 34 or 35, wherein the application solution proposal further includes preconfigured application content selected as a function of the received customer information.

37. The system of claim 33, wherein the one or more solution proposals further include a cost estimate for the application solution proposal.

38. A method comprising: receiving customer information including information detailing customer data processing preferences; processing the customer information to identify portions of an application related to the customer data processing preferences; and generating one or more application proposals as a function of the identified portions of the application.

39. The method of claim 38, wherein the customer data processing preferences include one or more data processing requirements.

40. The method of claim 38 or 39, wherein the one or more application proposals include an application solution proposal that meets at least some of the customer data processing preferences.

41. The method of claim 40, wherein the application solution proposal includes a proposed application and a configuration for the proposed application.

42. The method of claim 41 , wherein the one or more application solution proposals further include a project plan for implementing and configuring the proposed application.

43. The method of claim 41 or 42, wherein the application solution proposal further includes preconfϊgured application content selected as a function of the received customer information.

44. The method of claim 40, wherein the one or more solution proposals further include a cost estimate for the application solution proposal.

45. A system comprising: one or more memory devices; a scoping input database in the one or more memory devices, wherein the scoping input database holds one or more customer profiles; a content data store in the one or more memory devices; an adaptation catalog stored in the one or more memory devices, wherein the adaptation catalog links content stored in the content data store to possible customer profiles stored in the scoping input database; a workspace area in a memory device; and one or more configuration processes, wherein the one or more configuration processes execute to instantiate an application configuration in the workspace area including content selected as a function of a customer profile from the scoping input database and the adaptation catalog.

46. The system of claim 45, further comprising: a fine-tuning application, wherein the fine-tuning application allows modification of one or more application configuration settings.

47. The system of claim 45 or 46, wherein the application configuration instantiated in the workspace environment can be deployed to a runtime environment from which the application can execute.

48. A method comprising: storing, in a memory device, a scoping input database, wherein the scoping input database holds one or more customer profiles; storing, in the memory device, a content data store; storing ,in the memory device, an adaptation catalog, wherein the adaptation catalog links content stored in the content data store to possible customer profiles stored in the scoping input database; and executing one or more configuration processes, wherein the one or more configuration processes execute to instantiate an application configuration in a workspace area of the memory device, wherein the application configuration includes content selected as a function of a customer profile from the scoping input database and the adaptation catalog.

49. The method of claim 48, wherein customer profile data is received via a configuration application that receives answers to a dynamic set of questions selected from a universe of questions as a function of question answers and the adaptation catalog.

50. The method of claim 48 or 49, wherein the application configuration instantiated in the workspace environment is deployable to a runtime environment from which the application can execute.

51. A system comprising: an application configuration environment, wherein the application configuration environment includes: a configuration repository stored in a memory, wherein the configuration repository includes configuration settings of an application to deploy; and a data repository stored in the memory, wherein the data repository includes data to be included with the application to deploy; an application execution environment, wherein the application execution environment includes a baseline application; and a deployment module, wherein the deployment module includes: a configuration setting deployment process to deploy configuration settings from the configuration repository to the application execution environment; an activation process, wherein the activation process activates functionality of the baseline application as a function of the configuration settings stored in the configuration repository; and a data deployment process to deploy data from the data repository to one or more data stores in the application execution environment.

52. The system of claim 51 , wherein the baseline application in the application execution environment includes a plurality of objects.

53. The system of claim 52, wherein the activation process activates functionality of the baseline application by calling an activation method of one or more objects selected by the activation process as a function of the configuration settings stored in the configuration repository.

54. The system of any one of claims 51 to 53, wherein: the application configuration environment further comprising: an application execution environment deployment data store, wherein at least a current configuration model of the baseline application is stored therein; and the deployment module further comprising: a delta deployment process, wherein the delta deployment process: determines differences between a current state of the baseline application configuration as a function of the current configuration model and a current state of the application configuration environment; and calls the configuration setting deployment process, activation process, and data deployment process to deploy only the differences between the current state of the baseline application and the current state of the application configuration environment.

55. The system of any one of claims 51 to 54, wherein the configuration setting deployment process publishes configuration settings directly to one or more configuration tables.

56. The system of any one of claims 51 to 55, wherein the deployment module further includes a process to receive deployment commands within the application configuration environment, wherein the deployment commands include commands identifying portions of an application to deploy and a target application execution environment.

57. A method comprising: configuring an application in an application configuration environment, wherein the application configuration environment includes: a configuration repository stored in a memory, wherein the configuration repository includes configuration settings of the application; and a data repository stored in the memory, wherein the data repository includes data to be included with the application; and executing a deployment module to deploy the application to an application execution environment which includes a baseline application, wherein the deployment module executes by: deploying configuration settings from the configuration repository to the application execution environment; executing an activation process, wherein the activation process activates functionality of the baseline application as a function of the configuration settings stored in the configuration repository; and deploying data from the data repository to one or more data stores in the application execution environment.

58. The method of claim 57, wherein the baseline application in the application execution environment includes a plurality of objects.

59. The method of claim 58, wherein the activation process activates functionality of the baseline application by calling an activation method of one or more objects selected by the activation process as a function of the configuration settings stored in the configuration repository.

60. The method of claim 58 or 59, further comprising: storing, in the application configuration environment, at least a current configuration model of the baseline application; and determining differences between a current state of the baseline application configuration as a function of the current configuration model and a current state of the application configuration environment; and executing the configuration setting deployment process, activation process, and data deployment process to deploy only the differences between the current state of the baseline application and the current state of the application configuration environment.

61. The method of any one of claims 58 to 60, wherein the deployment module further includes a process to receive deployment commands within the application configuration environment, wherein the deployment commands include commands identifying portions of an application to deploy and a target application execution environment.

62. The method of claim 61, wherein target application execution environment identifier includes a test application execution environment.