beteo ALM Experts Blog

Category: Configuration Management

  • Can a Classic CMDB Cope With Business Service Management?

    Today´s IT in its role as service provider for the enterprise requires an immediate rethinking with regard to resources and configurations data management.

    If the datastore is not flexible enough, requirements resulting from service lifecycle management (SLM) might not be met to a satifactory degree and the provisioning of the CMDB services might not be as expected or as efficient as wanted.

    Configuration management databases (CMDB) used nowadays serve as rudimentary data pools and threaten to exist mainly for marketing reasons.

    A Sound Data Collection – Highly Exceeding Today´s Standard – is Necessary!
    A useful, efficient and active service lifecycle management (SLM) calls for a comprehensive enterprise service orientation and cross-company service management.

    To reach this goal, a homogenous and sound service database with an emphasis on „service“ is fundamental. Building up this database, the first step is to define a service catalog that allows all services including their relations to be identified. It is most important that all IT services are assigned to business services. This enables business service management (BSM) to execute impact analyses to an extent that would have been unthinkable ever before.

    From this perspective, a business service is an IT Service that creates direct value which becomes right away visible outside IT– due its obvious benefit to the business.

    At least one service access point per business service provides the point of entry to the targeted service and to the connection between business service and technical service.

    When collecting data for the service catalog, preferably by interviewing a number of steakholders, it is recommended to divide the service structure of the data collection into at least business, applications and infruastructure services from the beginning. The interviewer should always take the perspective of the interviewed person, as the service comsumer is the only one to tell if the provided service meets his/her requirements.

    There is more to a Service CMDB (S-CMDB)
    The data collected for the service catalog must be stored together with the usual data from other IT areas such as project portfolio management (PPM), IT development, and IT service management (ITSM).

    In order to do justice to a comprehensive service portfolio management approach, the data collection must contain all information, including their relations, needed for business as well as projects.

    Enabler of Comprehensive Service Portfolio Management
    The common data collection created for project portfolio management, IT development, and IT service management enables an efficient  holistic view of all IT and other projects and, in turn, serves as a basis for the targeted service portfolio management.

    Service Lifecycle

    The above figure illustrates that within the life cycle of a service, depending on the nature of the change, the currently prevailing requirement is considered either a project request or an operational issue. Through a holistic view, all service changes can be re-prioritized and grouped according to business requirements and users. This reduces risk within the implementation or problem solving cycle and ensures a seamless transition into business.

    Conventional CMDBs need to be extended if they want to meet the requirements of S-CMDBs and to achieve the high expected benefit to IT.

    About the author:
    Andreas Schegg, ITIL and Configuration Management Expert, is Senior Consultant at Ontrex AG, Winterthur, Switzerland.

  • HP BTO Software Centers – Overview

    HP offers a number of BTO Centers. These software packages support in the context of a BTO strategy specific phases of the application lifecycle. The following overview is meant to shed light on the HP BTO jungle.

    HP BTO Centers

    IT STRATEGY

    • Project and Portfolio Management Center (CIO Office)
      The IT management solution enables control and documentation of the enterprise processes, particularly with regard to an optimization of priorities, staff members and processes in IT organizations. For this purpose, modules for the management of portfolio, demand, time, changes, projects, resources, finances and programs are available. Upon coordination with business processes and enterprise requirements, the distribution and use of resources are optimized and processes are standardized (IT Governance).
    • SOA Center (CTO Office)
      The HP BTO solutions for governance, quality and management of service-oriented architectures (SOA) are designed to help customers to minimize economical risks in SOA project phases and to create a comprehensively controlled, business-oriented SOA basis. HP SOA Center enables registry/repository, policy management, consumer management, policy enforcement, performance monitoring und problem solving.

    APPLICATION DEVELOPMENT

    • Quality Center
      With HP Quality Center, a cross-enterprise exchange of information about test requirements, test planning, test execution and error reporting is possible, as well as checking for web security issues covering the entire testing and development team. Through functional test runs, GUI interfaces are automatically tested in applications and various release cycles.
    • Performance Center
      HP Performance Center features a real-time simulation of the maximum access demanded by customer requests using active virtual user input of the applications. This enables system optimization before „going live“ and ensures the desired steady availability. A required optimization can be controlled and accomplished under system load by help of an analysis program. Thus, new web or SAP applications are made secure before going into production.
    • Application Security Center
      By using the technologies of HP Applications Security Center, security gaps in web applications can be identified and judged all across the lifecycle: from development and quality control up to operation. Also applications that are already running in a productive system, can be checked for security gaps. In addition, audit and compliance requirements such as Sarbanes-Oxley, HIP AA or PCI can be met.

    (IT) OPERATIONS

    • HP Universal CMDB
      HP Universal CMDB is a configuration management database for IT organizations planning to implement business service management and ITIL-based initiatives. This software allows you to take up, document and store – in addition to physical configuration elements – logical elements. It also provides extended functionality such as an effects analysis and access control for building up and maintaining CMDB.

    Business Service Management

    • Business Availability Center
      This solution allows you to monitor the availability and performance of applications in operation for 24 hours a day and 7 days a week. Business processes, service levels, applications an the underlying infrastructure are coordinated to one another. The infrastructure is visualized by a graphical view with the traffic light set of colors red, orange and green showing the state of operation. A drill down is available for detailed view and error analysis. BAC is used to ensure the active operation of all business-relevant applications and to verify internal or external SLA agreements.
    • Operations Center
      This solution features a comprehensive, service-oriented access to IT management. Information is integrated and synchronized across management silos, IT and business are connected to one another. This distributed, scalable management solution which also includes security features allows you to monitor, control and record the status and performance of different IT environments, covering network, system, databases, applications, services and Internet.
    • Network Management Center
      This network management solution is considered a strategic and particularly important investment. In the last few years it has been established as an indispensible component of error and event management as well as visualization of network topologies. Network configuration, network events, application performance, and network analysis are the main areas involved.

    Service Automation

    • Data Center Automation Center
      Process automation in IT centers can be effectively supported by HP Data Center Automation Center allowing IT organizations to easily increase cost efficiency and to better meet quality and compliance requirements.
    • Client Automation Center
      More and more security risks, increasing availability requirements, and the rapidly growing number of mobile and remote staff members make it more difficult to effectively and efficiently manage client computers – a requirement, however, which every modern success-oriented enterprise should focus upon. HP Client Automation Center allows you to automate relevant IT processes across the lifecycle of the client computers, no matter where their physical locations are.

    IT Service Management

    • Service Management Center
      HP Service Manager is a comprehensive, fully integrated IT service desk solution targeted to reduce the time spent on problem solving. Thanks to ITIL-based best practice processes and a scalable, service-oriented architecture, consistent, integrated processes can be rolled out all across IT organizations. Event, problem, change, and release management processes can be automated. Service level management and catalog-based service requests are supported. All processes are coordinated by means of configuration management.

  • Software Archeology – how to Successfully Change SAP Releases

    16th century. The eyes of an archeologist are scanning a field. He is asking himself where he should start digging. In his life, he still has a few years left. Which area would, from his experience, hold a chance for him to make a discovery? Then he notices a tree. For growing, it would need nutrients, so underneath there might be something. This is what he knows from experience.

    When he starts digging, he hits on a small house of a rather poor family. Disappointed, he gives up.
    200 years later, a larger excavation project is started. The settlement is found to be the most important source of information about ancient times.

    SAP
    Those who know me are acquainted with my writing style exposing my affinity to exaggerate. Let´s take a typical SAP project, a release upgrade, for example. Doesn´t differ that much from the story of the unlucky archeologist, I think. In the beginning, you often know little about a system. Everything seems to be underground. You are asking yourself how to address the release change, and on the basis of which information you might dare a prognosis. What will happen during the project? If you are lucky, the consultant experts have a fair knowledge of the system and the processes implemented on them. If not, the project will almost typically go beyond its scope on the two axes expenditure of time and budget planning. As some of the most important project phases, such as testing and training of the end user, are neglected in favour of the implementation phase, you will be faced with a quality problem. This, in turn, will have an impact on the third axis, the user acceptance.

    The way out
    Typical SAP projects, such as upgrades, are planned according to the waterfall principle. But one important step of this method is massively neglected: The requirements analysis, also known as gap analysis – in other words, the question, „How did SAP influence OUR particular standard?” If you want to comprehensively answer this simple question with reference to a SAP landscape, the only solution to the “problem” of such massive analysis is its automation.

    How can you access best quality and complete information in the shortest possible time?
    There are quite a number of vendors who offer analysis tools, from SAP Consulting via RBE up to IntelliCorp. Each of these tools focuses on a particular aspect and therefore has its individual potency.

    IntelliCorp´s Assessor Template for SAP Upgrades addresses the problem on a rather broad basis. The tool offers a variety of fully automated analysis workflows. Within a few days, three on average, it provides a wide range of material for use in the context of a detailed planning of the upgrade project. As a side-effect, the result provides a basis for the implementation team to operate on. Its high degree of flexibility makes it a tool which is suitable for all SAP applications, including commercial solutions, integration of third-party software or own namespaces in workbench.

    About the author: Fritz Mosonyi is senior consultant and division manager for SAP tools at beteo partner SPP Wien.

  • Configuration Management for SAP Customizing?

    A comprehensive configuration management is the most important basis of SAP Change and Transport Management. For ABAP code, this is accepted as general practice and supported by suitable tools. But how about configuration management for SAP customizing?

    From our experience, the major part of changes transported across a SAP system landscape are customizing changes. Not surprisingly, the persons responsible for change and transport management often keep struggling with problems after roll-outs for lack of consistently applied configuration management for_these objects. A consistent change and distribution of customizing requires stringent configuration management.
    Crucial to a cross-enterprise use and protection of SAP templates is that central and local objects are well documented, comprising all versions of their lifecycle up to the newest version.

    Comprehensive SAP configuration management all across the SAP landscape is meant to ensure overall integrity of the objects involved in SAP development, including ABAP as well as non-ABAP objects:

    • The use of well-defined standardized naming conventions clearly reveals to which organizations, areas and projects the objects belong.
    • All changes to objects, including individual customizing settings, are documented. At any time, it is obvious who is – and at which times – the owner of settings, who is entitled to make and has made changes and for which reason. This allows the changes to be tracked afterwards, which is an equivalent to versioning.
    • The documentation also includes the information as to who and what and who depends from a defined customizing setting. This is an integral factor of reasonable impact management.

    In the context of each change to the SAP landscape systems, it must be made sure that the rules listed above for practicing a comprehensive SAP configuration management are observed. This, again, requires a strict organization of the change und transport management. Naming conventions for transport objects and transports must be established, transport packages must be grouped according to their content, organizational and technical processes must be clearly defined and adhered to.

    Some projects are highly dependent on a consistent comprehensive SAP configuration management. Without this, very often the challenges to enterprise SAP organizations can hardly be mastered, especially in the context of mergers and acquisitions, strategic outsourcing projects, insourcing, and regional or global consolidations of systems. This is also true for customizing changes. However, a solid foundation as outlined above allows such projects to planned and implemented with reasonable effort and fair success. Also customizing changes of several systems can be consolidated without a negative impact.

    In addition, a comprehensive SAP configuration management allows you to permanently record the data related to transports, to the transported objects and to the result of the transport, and to evaluate them. This is comparable to using suitable analyzing tools, such as the one offered by Prospero, which have been designed to disclose the causes of problems in SAP logistic processes, or even to give a prognosis concerning their results. The same is achieved by using SAP change management data for the transport of SAP changes. In any case, SAP change and transport management has still plenty of room for improvement in complex SAP landscapes.

    Summary
    Applying a wide-ranging SAP configuration management has turned out to be the most effective method to ensure a consistent and efficient SAP change and transport management and a consistent customizing across the SAP system landscape.

    Unfortunately, the opportunity for global enterprises using large SAP systems to improve the quality and to save costs by investing in SAP change and transport management is very often not seized, because it is thought to be technically complex. But if the challenge is taken up it soon shows that the problems are more political or company-related than of a technical nature.

  • Proactive Impact Management – the basis for BTO

    Business Technology Optimization as a Challenge
    Business Technology Optimization (BTO) targets at a closer collaboration of IT and business – nothing really new, just a daily challenge to the CIO. To support SAP IT organizations in reaching this target, beteo has designed the beteo Impact Hourglass.

    beteo Impact-Sanduhr

    With the beteo Impact Hourglass, principally all objects of the business domain (in the following BD) and the technical domain (in the following TD) which are involved in changes are seen integrally, comprising system and development, as well as in relation to each other. Thus, business and IT aspects of a system can be comprehensively understood, viewed and analyzed.  Relations between objects of both areas can selectively be established, according to the object type. Due to interdependencies, effects of changes can be mapped and understood across all levels.
    Persons from business and IT who are planning a change and are in charge of apecifying the change requirements can use the beteo Impact Hourglass to have all dependent objects from BD and TD displayed. This means that all objects which might have to be changed can be identified. This view including the technical objects as well as the descriptions of the business processes and all other describing objects of the development ensures that all objects affected by the change can be managed.

    The beteo Impact Hourglass is a suitable instrument to allow all persons involved in SAP system analysis processes – from planning to implementation of changes – to proactively carry out system impact analyses and simulations. Before there are any changes to the system, all possibly affected objects are identified. Special filters can be used to have particular object types and their relations displayed. So it is easy for users of the beteo Impact Hourglass to keep track of things. What is new about the beteo Impact Hourglass is that it not only allows viewing objects related to technical implementations (results from development and testing), but also organizational processes (business processes, activities, depending organizations) and describing objects (concepts, specifications, training, testing scenarios). Changes and their effects can be exactly planned, analyzed and controlled, and potential for optimization is revealed right away.

    beteo Impact analysis
    Basically, beteo Impact Hourglass enables three types of impact analysis.

    • Concurrent Impact Analysis
      The Concurrent Impact Analysis shows how many parallel changes are potentially made per object. This facilitates identifying risks on the one hand, and the grouping changes on objects on the other hand to address them at once. In most cases it is quite helpful to know in advance that there are upcoming concurrent changes to particular objects.
    • Dependency Impact Analysis
      The Dependency Impact Analysis shows which objects of the selected object type across the whole system and the development documentation might be directly affected by a particular change.
    • Interference Impact Analysis
      Starting from an object, which for example has been identified through Dependency Impact Analysis, the Interference Impact Analysis finds out which superordinate objects not directly connected to the same change are additionally affected. This might reveal processes using an object which has been indirectly affected by a change to another business process and therefore has to be tested after the change, because technically the same functions and settings are used in the system.

    Versioned documentation of Business Domain (BD), Technical Domain (TD) and related objects of system development

    The BD mainly includes organizational objects and objects resulting from describing system development measures. With the beteo Impact Hourglass, these objects and their relations can be documented and to each of them a lifecycle can be assigned. This ensures that the describing, organizational objects for each change request are identified and kept updated. Change requests not only refer to technical objects, but also to business objects and to all supporting objects which are created and customized in the context of the development process.

    The versioned documentation of the objects of business process management makes it easier to understand the evolution of all objects. Dependencies on real and describing business domain and technical objects and interdependencies between these objects are identified. Changes to programs and customizing activities can be presented and understood comprehensively and in relation to each other.

    Summary
     From the early stage of planning a change, before it is actually executed, the beteo Impact Hourglass provides a clear and complete conception of its effects and the possibility of evaluating them. This allows all types Impact Analyses to be proactively carried out and subsequently be tracked in the project phase.  Decisions in the context of practicability, planning of implementation – particularly of parallel upcoming changes – and project management and controlling can largely be improved and simplified.
    There are a number of useful tools available for the reactive Impact Analysis applied to objects of the technical domain (TD), such as IntelliCorp´s LiveCompare, Panaya Inc.´s Panaya, IBIS´ RBE Plus and Hewlett Packard´s Universal CMDB. However, they basically support the programmer and not as much the business analyst. The beteo Impact Hourglass integrates business processes into impact analysis and allows enterprises to benefit from Business Technology Optimization (BTO).

  • Lifecycle Management – no Pain, no Gain!

    Successful IT Planning & Control must include not only IT Service Management and Project & Portfolio Management, but also Application Lifecycle Management in order to be of lasting benefit. The following illustration by Gartner clearly demonstrates this.

    IT Planning- & Controlling

    Considering the support of the various areas and, above all, of the interfaces between them, it is obvious that helpful methods and high-quality tools for Service Development (Project & Portfolio Management, Design, Development and Testing) and Service Delivery (IT Service Management) are available and in use.

    On the other hand, tools and methods supporting the interfaces between the different areas and to Application Lifecycle Management in general seem to be rather scarce.

    At the same time, Application Lifecycle Management promises attractive benefits like:

    • a noticeable increase in developer productivity
    • “best practice” in development and service roll-out
    • a clear focus of developers on business instead of technical requirements
    • largely improved collaboration between development and business area
    • improved time-to-market by repeatable and partly automated processes and generally improved resource planning

    The software manufacturers priding oneself on their solutions that are supposed to reduce either project or operating costs are getting a bore. To them, the direct interdependencies between business and development are rarely of central concern. Statements as to the benefit of the solutions usually refer to either of the two aspects, and very often, improvement on one side is combined with a dramatic rise of costs on the other. This is why this topic is often referred to as the general “IT dilemma”.

    A relevant issue of “good” software engineering is a comprehensive requirements management, covering diverse influencing parameters. However, there are few cases where with each requirement all depending lifecycle objects are taken into account right from the start. But without this, recognizing competing requirements as what they are is impossible. What is more, hardly ever consideration is given to changes that are being implemented. Thorough IT Planning and Control across all fields of activities including their interfaces also comprises referencing and versioning of the describing, organizational and technical objects and their relation to one another. IT Service, and IT as a whole, is regarded and referred to as a complete system.

    The same is often true for business: IT Service Management (ITSM) includes Trouble Tickets without a clear reference to the concerned objects in Application Lifecycle. Information about the newest changes is not passed on to either the present development or the planned projects. This results in duplication, inconsistencies and considerable effort put in subsequent coordination. Any kind of re-use following the change or the newest project release is moving beyond reach.

    “Comprehensive” process frameworks and methods such as ITIL, PRINCE2, PMI and COBIT or SOX audit and compliance standards are just as unsuitable to overcome the “IT dilemma”, because they all disregard the interdependencies between the Service Lifecycle objects, meaning between processes, services and all technical objects. Although it is the intent and purpose of all these standards to diminish risks, I doubt if they can half-way reach this target without taking these dependencies into account.

    To me, the only solution in sight is introducing a professional method- and tool-supported Application Lifecycle Management.

  • The Cycle Above the Development Cycle

    Nowadays, software is used in virtually all enterprises. Software is continuously extended, changed or deactivated – as a result of changing business requirements, enhanced functionality of commercial software releases, or subsequent to bug-fixing. Over the years, typical phases, methods and techniques of the development cycle have established: project portfolio management techniques, software development methods and techniques, models for carrying out projects, IT service management and quality requirements.

    Software Development Cycle

    Software is code and all its descriptive objects
    In order to handle software applications, the user needs instructions, i.e. a user manual. Developers need a technical documentation, division managers need a process description, and the business or the outsourcing partner needs a business manual. For gach phase of a software development cycle, there are documents which are essential to particular user groups. Project plan and project documentation which influence the development of the software most directly, provide valuable information about the software. Some software components are dependent on system environments. Particular server and client components must be installed along with the software.

    As a result, even the most simple tool becomes part of a highly complex network of software and descriptive objects which are linked to many other objects.

    Managing the Software’s Lifecycle

    To the user, software is just a means to an end, a tool which temporarily facilitates the carrying out of particular tasks within the business process. In its lifecycle, the software passes through multiple development cycles (fig. 1) until it is replaced by a completely different tool (fig. 2). Every single software or software change is designed in line with defined requirements, or compared with other software, and then, if found suitable, developed and implemented.

    Software Development Cycle

    While being used, software is maintained, improved, and eventually deactivated. Some vendors offer tools to record all circumstances which determine the lifecycle of a software component as a complex system. The suitable instrument to this end is the Software Lifecycle Management. It offers a series of methods, techniques and supported by tools like advanced CMDB solutions and workflow engines.

    Multiple views in a holistic approach
    Software changes permanently. Its functionality is extended, the entry of data is facilitated, tasks are diversified. Existing software must be migrated, changes must be activated. Finally, a new version emerges from the amended former software version, or from part of it. For this new version, new instructions, new testing, and a new configuration are needed. Parts of the old software component continue to exist in the form of functions or modules which have been integrated in the new version.

    Software Development Cycle

    To reduce the complexity analyzing software systems during the change process tools allowing to take different perspectives have become a necessity. Depending on diverse requirements and tasks, for software environments we must be able to look at all software or descriptive objects and their relationships from a business, a development or a supplier view.

    Summary
    Development for sustainable systems requires a multidimensional look beyond the single development cycle. The overall software lifecycle, the cycle above the development cycle must be managed. Unidimensional, snapshot-like views as offered by many software techniques, do not allow an integrated Software Lifecycle Management. The tools for building up lifecycle management environments allowing to all interdependencies across the entire cycle are available, but still rarely used.

    Once in place lifecycle management systems keep even complex software systems manageable, customizable and flexibly adaptable.

  • Lifecycle Management – HP BTO Makes It Happen

    This article shows how Application Lifecycle Management can be implemented for large SAP installations. A description of the respective software components can be found on HP’s BTO website.

    Complex SAP systems landscape
    The subsequent chart illustrates how complex a comprehensive SAP Business Suite can be, with its various systems landscapes that can consist of development, quality assurance and production systems.

    Business processes proceed through various ABAP systems, i.e. SAP CRM, SAP ERP and SAP BW. Consequently, a sales activity will be registered in SAP CRM, while then through SAP ERP, the whole preparation, delivery and financial editing of data will be executed. Finally, corresponding ABC analysis will be run in SAP BW.

    If needed, the user will be offered further front-end functions by means of the role-based SAP Portal – created with SAP NDI (SAP Netweaver J2EE Development Infrastructure).

    In order to save investments, operations and development of such all-encompassing and technically complex systems must be ensured longterm. This calls for specific provisions. The required environment and its components are highlighted in blue in the chart below.

    SOA Lifecycle Management

    SAP Application Lifecycle Management with HP products
    For this reason, a Lifecycle Management Environment has been created for large SAP environments, based on HP’s software products. In the following lines, the roles taken over by the individual products and their integration are described.
    SOA Lifecycle Management

    1. Comprehensive support of all stages in the development cycle
    The actual development cycle is supported by the HP products shown in the chart. In addition, ARIS is used for modelling of the business processes and their visualisation.

    Quality Management (HP Quality Center)
    HP Quality Center, which is integrated into the Lifecycle Management environment by means of HP PPM, ensures proactive testing. Thus, the data relevant for the testing is collected, changed and validated at the adequate moment. At the same time, the respective test objects are managed by HP Quality Center.

    Business Service Management (HP BAC)
    HP BAC is integrated into the development process so that information regarding every single business-service can be obtained at every single stage of the development. On the level of business-service, multidimensional impact analysis can be undertaken in all phases of development and test. Furthermore, any related descriptive, organizational and technical objects can be elicited per Business Service.

    SAP Solution Manager
    Integrating SAP Solution Manager into the Lifecycle Management Environment ensures that the appropriate objects can be transported into the SAP systems landscapes. In so doing, the integrity of ABAP and non-ABAP objects of different SAP systems can be ascertained by means of the combinatorics of HP PPM.

    SOA Management
    By integrating Web Services Monitoring data of HP Systinet, access to the data about a Business-Services running in production is guaranteed at any time.

    2. Driving the development process
    HP PPM is utilised, employing all its functionality, to digitize, integrate and automate the processes. The strengths of HP PPM lie specifically in the execution of tasks for which the integration between process and tool are key: it drives all processes and is capable of communicating with every software used in the development cycle.

    Unfortunately, by changing the name of their Software Suite to HP Project and Portfolio Management Center (HP PPM), HP have removed the reference to the true strength of their product from its name. Therefore, the name situates the product only in reference to one Gartner IT quadrant: Project & Portfolio Management (PPM), while the former name Mercury IT Governance (Mercury ITG) reflected very well how strong the product is.

    • It can be used to effectively reduce, if not eliminate, manual or as well as technical interfaces and communication levels. Duplicate and manual data entry by the user may be removed, so that the risk for failures may be minimised and the efficiency maximised.
    • HP PPM combines organisational process stages with technical ones. By this means, it is possible to automate process stages and to include quality assurance measures directly into the process.
    • HP PPM allows to integrate SAP Solution Manager as a sub-process engine.
    • Thanks to HP PPM, all IT business processes can be formulated, digitalised and optimised in one and the same manner.

    3. Integration of the lifecycle data
    By means of integration across the various data stores of the tools, all used services and their dependencies can be monitored at any time. Comprehensive impact analysis is possible. For any change using HP BAC integration it is possible to determine all effected Business Services from the very beginning.

    Using HP PPM as an integration tool allows to reference and provide the necessary descriptive and organisational objects for every tool or user, while a defined process garantees the consistent integration all the results. This integration of the data of HP PPM into the Lifecycle Management Environment facilitates the complete reuse of the process information across the application lifecycle.

    Does HP promise too much?
    At least in the context of an SAP environment, the promise of HP BTO’s marketing messages holds true in a very realistic manner. HP BTO facilitates the pragmatic setup and successful operation of an Application Lifecycle Management.

Powered by