Abstract: A method for integrating a plurality of existing software applications is disclosed. The method comprises executing the plurality of existing software applications. A composite graphical user interface (GUI) is created containing selected objects. A user's interactions with each of the plurality of existing software applications are recorded to record at least one function from each of the plurality of existing software applications. The at least one recorded function from each of the plurality of existing software applications is assigned to at least one of the selected objects in the composite GUI.

Abstract: A system comprises a processor and storage containing software. When executed, the software causes the processor to receive a set of metrics to be monitored, cause to be monitored the set of metrics, and filter the monitored metrics per a sharing policy to produce a subset of the set of metrics.

Abstract: An information repository contains information regarding engagements, where the information regarding engagements specifies outcomes of the engagements and roles of individuals involved in the engagements. In response to a query seeking to locate personnel with particular experience, at least one of the individuals is identified based on the information regarding engagements, where the identifying considers the roles of the individuals in the outcomes of the engagements.

Abstract: A method for integrating a plurality of existing software applications is disclosed. The method comprises executing the plurality of existing software applications. A composite graphical user interface (GUI) is created containing selected objects. A user's interactions with each of the plurality of existing software applications are recorded to record at least one function from each of the plurality of existing software applications. The at least one recorded function from each of the plurality of existing software applications is assigned to at least one of the selected objects in the composite GUI.

Abstract: A services registry and method for enabling determination of the quality of a service provided therein are presented. The registry includes a service-oriented architecture (SOA) repository that takes as input information from a plurality of data sources that map to a plurality of rating dimensions. The registry further includes a rating calculation engine that receives service characteristics for a service and calculates, based on category weightings and rating rules that are customizable by an organization, a service quality rating for provision to service consumers that takes into account the plurality of rating dimensions. The rating calculation engine recalculates the service quality rating over time as the service is being used and goes through lifecycle stages.

Abstract: In an embodiment, the invention provides a method of prioritizing problems in IT services. The method comprises determining a plurality of N problems. An incident cost, a workaround cost, an expected resolution cost, and a total cost for each of the N problems is determined. A priority is assigned to each of the N problems such that each priority has an expected resolution time. The priorities are assigned such that the total cost for fixing all N problems is lower than any other selection of priorities.

Abstract: Methods, systems, and computer program products are provided for information technology (IT) services lifecycle management. A services architecture provides a plurality of services that are capable of being ordered. A design service captures declarative specifications of services as service models. A catalog service receives the service model and combines the service models into a plurality of service offerings to provide a catalog of orderable services. An order configuration service receives an order for at least one orderable service selectable from the catalog of orderable services. An order processing service instantiates the at least one orderable service in two phases, thereby generating an instantiated ordered service. An order fulfillment service fulfills the order in accordance with the instantiated ordered service.

Abstract: A taxonomy is disclosed for describing mobile electronic services (MES) comprising a tree structure for organizing descriptive characteristics of the MES, wherein the tree structure includes: a root level for identifying an environment to which the MES is directed; a service model level for identifying a plurality of service categories; an entity level for identifying a plurality of accessing entity categories; a platform level for identifying a plurality of available component platforms; a class level for identifying a plurality of application characteristics; and an application level for identifying a plurality of specific MES applications; and metadata for identifying additional information relevant to selection of the MES.

Abstract: Systems, methodologies, media, and other embodiments associated with pre-sales technical consulting are described. One exemplary system embodiment includes a tracking data store configured to store data concerning an ATC team pre-sales technical consulting engagement, a decision guiding logic configured to facilitate making decisions during the pre-sales technical consulting engagement and a user interface logic configured to facilitate displaying data stored in the tracking data store and decision guiding data provided by the decision guiding logic.

Abstract: Systems, methodologies, media, and other embodiments associated with producing a metaplan for a Web services development project are described. One exemplary method includes establishing sets of criteria for planning a Web services project and selectively organizing selected members of the sets of criteria into a metaplan.

Abstract: A system and method is disclosed for creating a mobile electronic service (MES).

Abstract: A system and method is disclosed for invoking a mobile electronic service (MES).

Abstract: A taxonomy is disclosed for describing mobile electronic services (MES) comprising a tree structure for organizing descriptive characteristics of the MES, wherein the tree structure includes: a root level for identifying an environment to which the MES is directed; a service model level for identifying a plurality of service categories; an entity level for identifying a plurality of accessing entity categories; a platform level for identifying a plurality of available component platforms; a class level for identifying a plurality of application characteristics; and an application level for identifying a plurality of specific MES applications; and metadata for identifying additional information relevant to selection of the MES.