DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003

COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of invention:
SYSTEM AND METHOD FOR OBTAINING AND OPERATIONALIZING AN OPTIMAL ENTERPRISE ARCHITECTURE


APPLICANT:
Tata Consultancy Services Limited
A company Incorporated in India under the Companies Act, 1956
Having address:
Nirmal Building, 9th floor,
Nariman point, Mumbai 400021,
Maharashtra, India

The following specification particularly describes the invention and the manner in which it is to be performed.
CROSS REFERENCE TO RELATED APPLICATIONS
[001] The present application claims priority to an Indian Provisional Patent Application No.1268/MUM/2014, filed on May 11, 2014, the entirety of which is hereby incorporated by reference.

TECHNICAL FIELD
[002] The present disclosure in general relates to a field of modelling an enterprise architecture. More particularly, the present disclosure relates to a system and a method for obtaining and operationalizing an optimal enterprise architecture.

BACKGROUND
[003] Generally, enterprises have to respond to changes in business requirements due to multiple change drivers, such as evolving market conditions, technology obsolescence and advance, regulatory compliances, competitive pressures, and so on. Formulating strategies to face such imminent changes may be one of vital activities for the enterprises to carry out. Typically, the enterprises rely on human experts for deciding strategies to address the changes. For example, the strategies are decided based on documents with visual/textual notation. The strategies are neither machine-processable nor programmatically analyzable, and therefore lack capturing a holistic view of relevant aspects of the enterprises.
[004] With time, Enterprise architecture (EA) based modelling approach has been used for strategic decisions to overcome challenges associated with the changes in the enterprise. The EA based modelling approach tends to focus more on strategy making than the strategy operationalization. Other modelling approaches have also been used that focuses on the strategy operationalization from a perspective of either business or Information Technology (IT). The aforementioned approaches are cost intensive, time intensive, and are cumbersome.

SUMMARY
[005] This summary is provided to introduce concepts related to systems and methods for obtaining and operationalizing an optimal enterprise architecture and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[006] In one implementation, a method for obtaining and operationalizing an optimal enterprise architecture is disclosed. The method comprises receiving, by a processor, an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise. The EA model comprises units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates the at least one goal of the enterprise. The method further comprises integrating, by the processor, the EA model and the IM model to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise. The EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique. The method further comprises evaluating, by the processor, the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture. The method further comprises operationalizing, by the processor, the optimum enterprise architecture with the units of the EA model present in the enterprise.
[007] In one implementation, a system for obtaining and operationalizing an optimal enterprise architecture is disclosed. The system comprises a memory and a processor coupled to the memory. The processor executes program instructions stored in the memory to receive an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise. The EA model comprises units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates at least one goal of the enterprise. The processor further executes the program instructions stored in the memory to integrate the EA model and the IM model to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise. The EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique. The processor further executes the program instructions stored in the memory to evaluate the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture. The processor further executes the program instructions stored in the memory to operationalize the optimum enterprise architecture with the units of the EA model present in the enterprise.
[008] In one implementation, a non-transitory computer readable medium embodying a program executable in a computing device for obtaining and operationalizing an optimal enterprise architecture is disclosed. The program comprises a program code for receiving an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise. The EA model comprises units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates the at least one goal of the enterprise. The program further comprises a program code for integrating the EA model and the IM model to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise. The EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique. The program further comprises a program code for evaluating the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture. The program further comprises a program code for operationalizing the optimum enterprise architecture with the units of the EA model present in the enterprise.

BRIEF DESCRIPTION OF DRAWINGS
[009] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like/similar features and components.
[010] FIG. 1 illustrates a network implementation of a system for obtaining and operationalizing an optimal enterprise architecture, in accordance with an embodiment of the present disclosure.
[011] FIG. 2 illustrates the system, in accordance with an embodiment of the present disclosure.
[012] FIG. 3 shows a flowchart for obtaining and operationalizing an optimal enterprise architecture, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION
[013] The present disclosure relates to a system and a method for obtaining and operationalizing an optimal enterprise architecture. At first, an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise are received. The EA model comprises units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates at least one goal of the enterprise. Further, the EA model and the IM model maybe integrated to obtain one or more expected enterprise architecture alternatives. Specifically, the EA model and the IM model may be integrated using ArchiMate®. Each expected enterprise architecture alternative may comprise a strategy to achieve the goals of the enterprise. The EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique.
[014] Upon obtaining, the one or more expected enterprise architecture alternatives may be evaluated to obtain an optimum enterprise architecture. In other words, the EA model is coupled with modifications and addition of elements and relations to obtain an optimum enterprise architecture. Subsequently, the optimum enterprise architecture may be operationalized with the units of the EA model present in the enterprise. In other words, the optimum enterprise architecture may be operationalized using relevant enterprise actors. In one example, the actors may include people in the enterprise. The actors may include a Manager, an Executive, a Chief Officer, or any person accountable in the enterprise. As presented above, the actors may have one or more tasks to perform within the enterprise.
[015] While aspects of described system and method for obtaining and operationalizing an optimal enterprise architecturemay be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system.
[016] Referring now to FIG. 1, a network implementation 100 of a system 102 for obtaining and operationalizing an optimal enterprise architecture is illustrated, in accordance with an embodiment of the present disclosure. The system 102 may receive an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise. The EA model comprises units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates at least one goal of the enterprise. The system 102 may integrate the EA model and the IM model to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise. The EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique. The system 102 may evaluate the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture. The system 102 may operationalize the optimum enterprise architecture with the units of the EA model present in the enterprise.
[017] Although the present disclosure is explained by considering that the system 102 is implemented on a server, it may be understood that the system 102 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, cloud, and the like. It will be understood that the system 102 may be accessed by multiple users through one or more user devices 104-1, 104-2…104-N, collectively referred to as user devices 104 hereinafter, or applications residing on the user devices 104. Examples of the user devices 104 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a workstation. The user devices 104 are communicatively coupled to the system 102 through a network 106.
[018] In one implementation, the network 106 may be a wireless network, a wired network or a combination thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 106 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
[019] Referring now to FIG. 2, the system 102 is illustrated in accordance with an embodiment of the present disclosure. In one embodiment, the system 102 may include at least one processor 202, an input/output (I/O) interface 204, and a memory 206. The at least one processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 206.
[020] The I/O interface 204 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 204 may allow the system 102 to interact with a user directly or through the user devices 104. Further, the I/O interface 204 may enable the system 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 204 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 204 may include one or more ports for connecting a number of devices to one another or to another server.
[021] The memory 206 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[022] In one implementation, at first, the user may use the client device 104 to access the system 102 via the I/O interface 204. The working of the system 102 may be explained in detail using FIG. 2. The system 102 may be used for obtaining and operationalizing an optimal enterprise architecture. In order to obtain an optimal enterprise architecture, the system 102 may receive Enterprise Architecture (EA) model of an enterprise. In one example, the enterprise may include, but not limited to, an educational institution, data centre, an Information Technology (IT) firm, and so on. The EA model may comprises a plurality of units performing at least one task to achieve at least one goal of the enterprise. In one example, the plurality of units may comprise one of an organizational unit, people, and an infrastructure unit. The people may indicate personnel available in the enterprise. The organizational unit may indicate essential business functions in the enterprise that are divided to maximize efficiency. In other words, the people in the enterprise may be divided to create separate departments, such as for marketing, sales, accounting, information technology, and so on. In one example, the people may be divided or classified in a hierarchy such as a Manager, an Assistant Manager, an executive, and so on. In another example, the people may be divided based on a project team, groups, and departments. The infrastructure unit may indicate resources that are available in the enterprise. The resources may include, but not limited to, computers, servers, data centres, and so on. The resources may be associated with policies and strategies pre-defined for the enterprise.
[023] The system 102 may receive data corresponding to each unit of the plurality of units based on a structure of the enterprise. In one example, the structure of the enterprise may include multiple departments with limited people in each department. In another example, the structure of the enterprise may include manufacturing unit, management, human resource department, and so on.
[024] As presented above, a unit in the plurality of units may perform at least one task to achieve at least one goal of the enterprise. In one example, the at least one task may comprise performing a function by the unit, e.g., an actor. In one example, the actor may include a Chief Financial Officer (CFO), a manager, an assistant, and so on.
[025] Further, the system 102 may receive Intention and Motivation (IM) model for the enterprise. The IM model may indicate factors to be considered to achieve the at least one goal of the enterprise. In other words, the IM model may be received for the enterprise or for each unit in the enterprise. In one example, the goal for the enterprise may include increase revenue of the enterprise by 20 percent. In another example, the goal for the enterprise may include maximize productivity of the actors or the units in the enterprise. In order to achieve the goals of the units or the enterprise, there may be internal drivers and/or external drivers. The internal drivers may include factors such as internal policies. The external drivers may include statutory policies. It is to be understood that the internal and external drivers may include other factors that are not disclosed and may be obvious to a person skilled in context of the enterprise.
[026] In order to explain goals of the units or the actors in the enterprise, few examples may be used. For example, a goal for the manager may include completing a project on time with available people. Similarly, a goal for the enterprise may include completing the project without additional cost within a specified time and with the people available. In order to explain the unit performing a task, an example may be used. Consider the hierarchy of the organizational unit as manager, assistant manager and executive. Consider, the manager allots a project to two assistant managers and each assistant manager has ten executives to work on the project. The manager may divide the people in the enterprise. For example, the manager may divide the people between project teams, groups, or departments based on a task. In one example, the executive may be assigned a task to write a software code for an application. Similarly, the assistant manager may be assigned a task to review the software code. Similarly, each unit in the plurality of units performs at least one task to achieve the goals themselves and that of the enterprise.
[027] The IM model may further comprise soft goals and dependency participants at every stage of the IM model. The contribution of various alternatives to the corresponding soft goals may be captured in terms of a scale from break (most negative) to make (most positive). The soft goals are qualitative aspects of desired solution i.e. the expected EA. The models with the activities that various actor are performing may be created in return.
[028] The IM model may comprise the Strategic Dependency (SD) and the Strategic Rationale (SR) models. The system 102 may use the SD model and SR model to capture the strategic dependencies between the actors or the units. Further, the SD model and SR model may be captured to model intentions of the actor in performing the appointed tasks respectively. In context of the enterprise, the SD model may describe the enterprise in terms of the strategic dependencies that the actors have on each other in accomplishing the actor’s tasks. The SR model may describe reasoning that the actors employ in determining the merit to organize the tasks.
[029] After receiving the intentions of the units in the IM model, the EA model may be integrated with the IM model. Specifically, the EA model and the IM model may be integrated to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative indicates a strategy to achieve the goals of the enterprise. The EA model and the IM model may be integrated by mapping elements of the EA model and the IM model using an ontology technique. Mapping of elements in the EA model and the IM model is explained using an example. In one example, the EA model may be mapped with IM model using ArchiMate®. As known, ArchiMate® is an open and independent modelling language for enterprise architecture. The EA model comprising the business, application, and infrastructure models may be mapped with the IM model. Mapping of the EA model and the IM model enables to specify that enterprise active structure entities use or create passive structure entities while performing behaviour (entities) as means to end that are goal(s) or soft goal(s).
[030] The ArchiMate® may define Active Structure Elements (ASEs) and Passive Structure Elements (PSEs) as entities that are capable of performing behaviour. The ASEs may be assigned to the behaviour element indicating units of activity. The PSEs may be objects upon which the behaviour is performed. The relationship may be represented using three layers, such as business, application, and technology layers. The service may bean externally visible behaviour of the model, which is made accessible through the interfaces, and constitutes the external view on the active structural element. The business layer may represent the products and the services being offered to external customers. The products and the services may be realized in the enterprise by the business processes performed by the actor. The resources may be used or created by the actor while performing the tasks. The actors may depend on each other to perform the task and/or to use or create the resource to achieve the goal or the soft goal.
[031] The ontology technique may be used to map the EA model and the IM model. The ontological representation of the IM model may lead the enterprise to consider the goal. To achieve the goal, the enterprise may have to come up with a course of action. The internal and external driver may influence the elements in the IM model. For example, a stakeholder may be interested in assessment of the internal driver and the assessment may lead to formulation of the goal.
[032] The ontological representation may be used to conduct change impact and landscape mapping analysis. In order to conduct the change impact, the EA ontology may be mapped with IM concepts. The ArchiMate® enables obtaining EA element type and name of both source and target nodes along with relation and documentation. After obtaining, the EA element type may be read into ontology model by constructing a dictionary, leveraging the type information of an instance and then constructing the data in terms of relations. In other words, the IM model concepts may be captured under Intentional Entity class. Specifically, the IM elements may be captured with the EA model, comprising elements internal to an actor (comprising strategic rationale model) and external to actors (strategic dependency model). Based on the ontological representation, the relations in the IM model are represented as means-end, task decomposition, contribution, and strategic dependency relations, benefit from being represented as reified relations. For example, a contribution link may indicate an element that contributes to a soft goal and also the contribution made. The contribution link in the IM model may be captured as an ontological class CTLink, instead of representing it as a relation. The source and target of contributions may be captured via has CTSource and has CTTarget object properties and the contribution may be captured via has CTValue. Similarly, the Means-ends links (MELink), task decomposition links (TDLink) and strategic dependency links (SDLink) may be represented.
[033] After integrating the EA model and the IM model, based on the context, one or more expected enterprise architecture alternatives may be obtained. After obtaining the one or more expected enterprise architecture alternatives, an optimum enterprise architecture may be obtained from the one or more expected enterprise architecture alternatives. Further, the optimum enterprise architecture may be operationalized. In order to explain evaluating the one or more expected enterprise architecture alternatives, an example may be used.
[034] Consider two large wealth management banks, WM1 and WM2, with multi-billion dollars involved in a Merger and Acquisition (M&A) activity. Consider both WM1 and WM2 are in a retail brokerage with 10000 Financial Advisors across 700 locations in a Country X. The objective of the M&A is to form a WM3 with the expressed strategic goal of triplingWM1’s revenue and gross margin in 5 years with a strategic growth viewpoint. Consider the context or the problems identified for forming WM3 are products and services rationalization, branch consolidation, workforce integration, application rationalization, data migration, and capacity enhancement. In order to explain obtaining and operationalizing an optimal enterprise architecture, consider the context of products and services rationalization of over a 1500 entities and more than 2500relations.
[035] At first, the EA model for the products and services rationalization context may be received. The context of the product and services problem may be traced back to the key external driver which may lead WM1 to engage into M&A with WM2. For the purpose of the context, market condition may be interpreted by WM1 as ripe for M&A for extending WM1’s product portfolio toWM2’s and vice-a-versa. The market conditions may be captured for the product and services. Specifically, the external and internal drivers of the market conditions may be captured. Furthermore, product portfolios of WM1 and WM2, which are similar, may be considered.
[036] After capturing the factors based on the context, an assessment of the Internal MDriver instance for the similar products may be carried out such that products and services of the merged entity may be rationalized. The strategic goal of revenue increment (IHardGoal instance Revenue to be increased with Doubled Product Mix) should be satisfied when rationalizing the product mix that shares many products of WM1 and WM2 with common features. The Chief Financial Officer (CFO) may be the stakeholder with responsibility of overseeing the activities that will be constructed via means-end analysis of this goal. The CFO may have two options, prefer the product mix of WM1 which is the majority stakeholder of the M&A or rationalize the product mix. For the first choice, IntentionalITask instance Prefer the Majority Stake, task decomposition suggests that when preferring the majority stake, margin should be improved still, captured in ISoftGoal instance Margin be improved. Means-ends decomposition of IHardGoal instance Majority Stake be Preferred may suggest that either all of WM1 products are retained while WM2’s are decommissioned or WM1 products are retained and enhanced with additional features from similar products of WM2.
[037] For IntentionalITask instance Product Mix to be rationalized, similar task and means ends decomposition may be carried out. When product mix rationalization choices are coined, dependencies of the CFO on others such as, Research Head (RH), and Chief Information Officer (CIO), and Business Unit Heads (BU Heads) may become apparent. Either specialized product mix models may be used for product rationalization for which the CFO may depend on the RH, or the rationalization ranking could be based purely on projected IT and sales costs of integration and operationalization of the new product mix, for which the CFO could get the cost inputs from the CIO and the BU Heads respectively. A third alternative may include cost inputs of the CIO and the CFO that may be integrated into product mix models by considering both customer and product profitability. The third alternative may not include general parameters such as customer segments and market share.
[038] The contribution of various alternatives to corresponding soft goals may be captured in terms of a scale from Break (most negative) to Make (most positive). The models with activities that the CIO, the BU Heads and the RH may be responsible for, and may be created in return.
[039] Upon completion of the IM model for a given problem, Integration ITask instances may be assigned until all the levels are reached to satisfaction. Assigning satisfaction values to IntegrationITask instances may be similar to making selection in means to all the ends in all the actors that are part of the IM model.
[040] As evident from above that the CFO and the BU Head are certainly key actors, along with the CIO who oversees an application layer at the highest level in the present example. While modelling the EA model, the process of client acquisition and fulfilment may be easy. Specifically, the EA model of the WM1 via questions like- the CFO, the BU Heads, and the CIO are involved in products and services, then what are the existing processes where these three actors come together to interact with products and services?, how are the products and services sold to customers?, and so on.
[041] After capturing the problem specific to the EA model, EA elements may be created for operationalization. In order to create the EA elements, each IntegrationITask instance may be realized by one or more behaviour elements. Further, behaviour elements and Integration Tasks mapped in extended enterprise meta-model may be represented using ArchiMate’s realizes relation. The mapping may result in capturing operationalization of instances of IntegrationITask using any behaviour elements such as instances of Business Process, Business Service, Business Function, Application Function, and Application Service. The List of selected products indicates an Application Data Object instance which itself realizes a Business Object. The Business Object instance may be accessed by the EA Behaviour instances like Business Process instance which realizes one of three rationalization alternatives of preparing rationalized product list based on a product mix model. The IntegrationITask instances may be combined in various ways based on whether the IntegrationITask satisfy the root goal. In order to preserve the elements that was added for specific Integration ITask instances, the elements may be tagged with the IntegrationITask instance name. At the time of tagging all the EA elements that were necessary in operationalizing the IntegrationITask instance, the rationalized product list may be prepared based on inputs from the CIO and the BU to be used by others. Subsequently, the expected operationalization model may be extracted.
[042] A set of elements comprising an operationalization model may be computed in various ways. The expected EA model that captures all possible expected alternatives would consist of the IM model, the operationalization model of all the alternatives and the existing EA model. Ontologically subtracting the existing EA model and the IM model from expected model may give the operationalization model of all the alternatives. The set of the operationalization elements of the IntegrationITask instances in a specific strategy may be separated using a SPARQL query as per the tagging performed earlier. The IntegrationITask instances in a strategy defined may be matched with the result set returned by execution of the SPARQL query, and the corresponding operational EA elements may be retrieved.
[043] Referring now to FIG. 3, a method 300 for obtaining and operationalizing an optimal enterprise architecture is shown, in accordance with an embodiment of the present disclosure. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[044] The order in which the method 300 is described and is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the disclosure described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 300 may be implemented in the above-described system 102.
[045] At step/block 302, an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise may be received. The EA model may comprise units performing at least one task to achieve at least one goal of the enterprise. The IM model indicates at least one goal of the enterprise.
[046] At step/block 304, the EA model and the IM model may be integrated to obtain one or more expected enterprise architecture alternatives. Each expected enterprise architecture alternative may comprise a strategy to achieve the goals of the enterprise. The EA model and the IM model may be integrated by mapping elements of the EA model and the IM model using an ontology technique.
[047] At step/block 306, the expected enterprise architecture alternatives with the IM model may be evaluated to obtain an optimum enterprise architecture.
[048] At step/block 308, the optimum enterprise architecture may be operationalized with the units of the EA model present in the enterprise.
[049] Although implementations of system and method for obtaining and operationalizing an optimal enterprise architecture have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for obtaining and operationalizing an optimal enterprise architecture. ,CLAIMS:WE CLAIM:

1. A method for obtaining and operationalizing an optimal enterprise architecture, the method comprising:
receiving, by a processor, an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise, wherein the EA model comprises units performing at least one task to achieve at least one goal of the enterprise, and wherein the IM model indicates at least one goal of the enterprise;
integrating, by the processor, the EA model and the IM model to obtain one or more expected enterprise architecture alternatives, wherein each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise, and wherein the EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique;
evaluating, by the processor, the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture; and
operationalizing, by the processor, the optimum enterprise architecture with the units of the EA model present in the enterprise.

2. The method of claim 1, wherein the units comprise at least one of: an application, an infrastructure layer, and people.

3. The method of claim 1, wherein the optimum enterprise architecture is obtained by altering the units of the EA model with respect to the IM model.

4. The method of claim 1, further comprising capturing Strategic Dependencies (SD) among the units to model intentions of the units performing at least one task.

5. A system for obtaining and operationalizing an optimal enterprise architecture, the system comprising:
a memory; and
a processor coupled to the memory, wherein the processor executes program instructions stored in the memory, to:
receive an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise, wherein the EA model comprises units performing at least one task to achieve at least one goal of the enterprise, and wherein the IM model indicates at least one goal of the enterprise;
integrate the EA model and the IM model to obtain one or more expected enterprise architecture alternatives, wherein each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise, and wherein the EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique;
evaluate the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture; and
operationalize the optimum enterprise architecture with the units of the EA model present in the enterprise.

6. The system of claim 5, wherein the units comprises at least one of: an application, an infrastructure layer, and people.

7. The system of claim 5, wherein the optimum enterprise architecture is obtained by altering the units of the EA model with respect to the IM model.

8. The system of claim 5, wherein the processor further executes the program instructions to capture Strategic Dependencies (SD) among the units to model intentions of the units performing the at least one task.

9. A non-transitory computer readable medium embodying a program executable in a computing device for obtaining and operationalizing an optimal enterprise architecture, the program comprising:
a program code for receiving an Enterprise Architecture (EA) model and an Intention and Motivation (IM) model of an enterprise, wherein the EA model comprises units performing at least one task to achieve at least one goal of the enterprise, and wherein the IM model indicates the at least one goal of the enterprise;
a program code for integrating the EA model and the IM model to obtain one or more expected enterprise architecture alternatives, wherein each expected enterprise architecture alternative comprises a strategy to achieve the goals of the enterprise, and wherein the EA model and the IM model are integrated by mapping elements of the EA model and the IM model using an ontology technique;
a program code for evaluating the expected enterprise architecture alternatives with the IM model to obtain an optimum enterprise architecture; and
a program code for operationalizing the optimum enterprise architecture with the units of the EA model present in the enterprise.