Patent Application
20100250316
This invention relates generally to lifecycle management and more specifically to the lifecycle management of SOA shared services.
In the past, software architectures have attempted to deal with increasing levels of software complexity. As the level of complexity continues to increase, traditional architectures are reaching the limit of their ability to deal with various problems. At the same time, traditional needs of information technology (IT) organizations persist. IT organizations need to respond quickly to new requirements of the business, while continuing to reduce the cost of IT to the business by absorbing and integrating new business partners, new business sets, etc.
Deconstructing and understanding business architectures to successfully deliver enterprise services is a complex undertaking for all businesses. Currently, no structured formal approach having a well-defined repeatable methodology based on the overall framework exists. There are no known standardized frameworks available in the industry that provide guidance and structure to such decomposition efforts to enable enterprises to undertake such initiatives with confidence.
In one embodiment, there is a method for developing a service oriented architecture (SOA) shared services portfolio. In this embodiment, the method comprises: decomposing a business architecture of an enterprise into a set of SOA shared services; and developing a SOA shared services portfolio that is populated with the set of SOA shared services.
In a second embodiment, there is a system for developing a service oriented architecture (SOA) shared services portfolio. In this embodiment, the system comprises at least one processing unit, and memory operably associated with the at least one processing unit. A portfolio tool is storable in memory and executable by the at least one processing unit. The portfolio tool comprises: a decomposition component configured to decompose a business architecture of an enterprise into a set of SOA shared services; and a development component configured to develop a SOA shared service portfolio that is populated with the set of SOA shared services.
In a third embodiment, there is a computer-readable medium storing computer instructions, which when executed, enables a computer system to develop a service oriented architecture (SOA) shared services portfolio, the computer instructions comprising: decomposing a business architecture of an enterprise into a set of SOA shared services; and developing a SOA shared services portfolio that is populated with the set of SOA shared services.
In a fourth embodiment, there is a method for deploying a portfolio tool for use in a computer system that provides development of a service oriented architecture (SOA) shared services portfolio. In this embodiment, a computer infrastructure is provided and is operable to: decompose a business architecture of an enterprise into a set of SOA shared services; and develop a SOA shared services portfolio that is populated with the set of SOA shared services.
The drawings are not necessarily to scale. The drawings are merely schematic representations, not intended to portray specific parameters of the invention. The drawings are intended to depict only typical embodiments of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements.
Embodiments of this invention are directed to developing a service oriented architecture (SOA) shared services portfolio. In these embodiments, a portfolio tool provides this capability. Specifically, the portfolio tool comprises a decomposition component configured to decompose a business architecture of an enterprise into a set of SOA shared services; and a development component configured to develop a SOA shared service portfolio that is populated with the set of SOA shared services.
Computer system 104 is intended to represent any type of computer system that may be implemented in deploying/realizing the teachings recited herein. In this particular example, computer system 104 represents an illustrative system for managing a SOA shared service. It should be understood that any other computers implemented under the present invention may have different components/software, but will perform similar functions. As shown, computer system 104 includes a processing unit 106, memory 108 for storing a portfolio tool 153, a bus 110, and device interfaces 112.
Processing unit 106 collects and routes signals representing outputs from external devices 115 (e.g., a keyboard, a pointing device, a display, a graphical user interface, etc.) to portfolio tool 153. The signals can be transmitted over a LAN and/or a WAN (e.g., T1, T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), wireless links (802.11, Bluetooth, etc.), and so on. In some embodiments, the signals may be encrypted using, for example, trusted key-pair encryption. Different external devices may transmit information using different communication pathways, such as Ethernet or wireless networks, direct serial or parallel connections, USB, Firewire®, Bluetooth®, or other proprietary interfaces. (Firewire is a registered trademark of Apple Computer, Inc. Bluetooth is a registered trademark of Bluetooth Special Interest Group (SIG)).
In general, processing unit 106 executes computer program code, such as program code for operating portfolio tool 153, which is stored in memory 108 and/or storage system 116. While executing computer program code, processing unit 106 can read and/or write data to/from memory 108, storage system 116, and a SOA shared services registry 117. SOA shared services registry 117 stores a plurality of SOA shared services and associated metadata, as well as rules against which the metadata is compared to locate, update, and store SOA shared services from decomposed business architectures, as will be further described below. Storage system 116 and services registry 117 can include VCRs, DVRs, RAID arrays, USB hard drives, optical disk recorders, flash storage devices, or any other similar storage device. Although not shown, computer system 104 could also include I/O interfaces that communicate with one or more external devices 115 that enable a user to interact with computer system 104.
Implementation 100 and portfolio tool 153 operate within a broader SOA shared services and lifecycle management process (SSLMP) 130, shown in
SOA SSLMP 130 of the present invention consists of the following distinct processes and associated methodologies:
Each of the above processes is a complete methodology that can be implemented independently since they define key stakeholders, affected processes, and touch-points throughout the organization. It will be appreciated that each of the above listed SOA processes are non-limiting examples of the functionality and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each process (I-VIII) may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s) of SOA SSLMP 130, as shown in
Referring now to
Next, once business architecture 132 is decomposed, a comprehensive portfolio of enterprise services is created. To accomplish this, a development component 160 is configured to develop SOA shared services portfolio 117 that is populated with set of SOA shared services 126. As mentioned above, SOA shared services portfolio 117 stores set of SOA shared services 126 and associated metadata, as well as rules against which the metadata is compared to locate, update, and store SOA shared services from decomposed business architecture 132.
In one embodiment, SOA shared services portfolio 117 is developed as described in phase 11 of SOA SSMLP 130 (
Next, each of set SOA shared services 126 is modeled, for example as described in the Service Modeling Design and Implementation phase shown in
After SOA shared services portfolio 117 is established and populated with set of SOA shared services 126, it is beneficial to manage/monitor SOA shared services portfolio 117 to maintain continuing service offerings and performance. In one embodiment, to accomplish this, portfolio tool 153 comprises a management component 165 configured to manage SOA shared services portfolio 117 and set of SOA shared services 126. Management component 165 manages aspects of service configuration, service re-factoring, service evolution, and service phase-out that are essential for the governance and lifecycle management of SOA shared services. The processes and methodologies identified for shared services portfolio re-factoring focus on establishing and maturing the services in terms of collaborations, program planning and funding. Service management helps enterprise 120 understand the entire lifecycle of a service and its impact on the enterprise.
Further, it can be appreciated that the methodologies disclosed herein can be used within a computer system to provide management of a SOA shared service, as shown in
The exemplary computer system 104 may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, people, components, logic, data structures, and so on that perform particular tasks or implements particular abstract data types. Exemplary computer system 104 may be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The program modules carry out the methodologies disclosed herein, as shown in
Furthermore, an implementation of exemplary computer system 104 may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer storage media” and “communications media.”
“Computer storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
“Communication media” typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism. Communication media also includes any information delivery media.
The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
It is apparent that there has been provided with this invention an approach for managing a SOA shared service. While the invention has been particularly shown and described in conjunction with a preferred embodiment thereof, it will be appreciated that variations and modifications will occur to those skilled in the art. Therefore, it is to be understood that the appended claims are intended to cover all such modifications and changes that fall within the true spirit of the invention.
