IBM Tivoli Unified Process (ITUP) Composer v7.1 Tivoli Support Technical Exchange Web Seminar

1. IBM Tivoli Unified Process (ITUP)Composer v7.1Tivoli Support Technical Exchange Web Seminar

2. Objectives To introduce ITUP Composer concepts, processes, and method content: • ITUP content design and development • ITUP workspace and user interface • Rational Method Composer (RMC) concepts and native terminology • ITUP method library structure • Customizing ITUP content to meet the needs of your organization • Configuring existing content and publishing ITUP configurations to a published Web site or document NOTE:Thespeaker's notes (Notes Pages) provide further slide information.

3. Introduction to ITUP Composer v7.1

4. Introduction to ITUP Composer v7.1 (Continued)

5. Introduction to ITUP Composer v7.1 (Continued) • ITUP is read-only content • ITUP Composer is a tool used to customize ITUP content: • Built with Rational Method Composer (RMC) • RMC is the environment ITUP Composer runs in • ITUP Composer allows customers to tailor the IT processes in ITUP by modifying: • Workflows • Roles • Work products

6. Introduction to ITUP Composer v7.1 (Continued) Features: ITUP vs. ITUP Composer

7. Brief Demo of ITUP Composer

8. ITUP Composer Architecture Design

9. ITUP Composer Architecture ITUP Composer Components IT Staff ITUP Content Library IBM Rational Method Composer Customize Publish Create Repository of IT Service Management Processes Tool for Customizing, Creating and Publishing Customized Documentation & Online Ops Guide + =

10. Integration design – process management products (PMPs) Web client CTO Process owners Multi-sys admin - User IBM Tivoli Unified Process Composer Process consultants Rational Method Composer (RMC) • Roles • Work products • Scenarios • Tool mentors • Implementation services • Overview • Tool mentors • Future • Workflow • Roles • Expert advice Published Web site • Web server • IIS • Apache • SharePoint • WAS • Tomcat • iPlanet PMP plug-ins ITUP Composer plug-in Launch in context PMP User PMP UI CCMDB Capacity PM Release PM Storage PM Service Desk Service Catalog Maxmimo Tivoli PMPs

11. ITUP - PMP plug-in design to enable PMP integration

12. RMC Concepts and Terminology

13. The Rational Method Composer approach Standardize representation and manage libraries of reusable method content Develop and manage processesfor performing projects Configure a cohesive process framework customized for my project needs Create project plan templates for enactment of process in the context of my project

14. Separating method content from processes Method

15. Differences: method content and processes Processes Method content elements Roles Work products Tasks Guidance Tool mentors Assembled into a process

16. Method Composer’s Method Plug-in structureMethod plug-in comprises method content, capability patterns, and delivery processes

17. Method Content Tasks Tool mentor* Roles Work Products Method content – the basic elements • Roles – describe the skills necessary to perform a task or create a work product • Tasks – provides guidance on the work that needs to be done to transform inputs into outputs through a series of steps performed by one or more roles (independent of a specific lifecycle or process) • Work products – define the items needed as input or created as output of one or more tasks that are typically the responsibility of a single role Guidance

18. Add different kinds of guidance to content Checklist: provides a list of items that need to be § Reusable Asset: guidance linking method content § completed or verified, often used in reviews or for to intellectual capital that can be utilized to perform validation some task or leveraged as a starting point for the creation of a solution Concepts: outlines key ideas or underlying § principles that serve as foundation for more explicit Roadmap: is process specific guidance that § guidance represents a linear walkthrough of those items from a particular perspective Estimation Considerations: provides guidance on § the amount of effort to produce a work product or perform a task including any influencing factors Supporting Material: is a catchall used to represent § any other type of guidance that does not have a Examples: used to include typical samples of the § specific type items to be produced, may often only be a partial sample that is intended as further guidance rather Template: a form or empty instance of a work § than something to be reused product that can be used as starting point for the creation of a new one Guideline: general type of guidance used to provide § additional detail on to perform some set of actions or Term Definition: used to define items that make up § additional rules or recommendations related to work the glossary products and their properties Practice: represents a proven way or strategy of § Tool Mentor: specialize form of guidance on how to § doing something, they may also represent standards apply a specific tool to accomplish some piece of work or develop a particular work product Report: is a predefined template that represents the § output of an automated tool that may represent a Whitepaper: specialized version of concept that has § combination of information from other work products been externally reviewed or published

19. Define multiple category schemes forindexing, viewing, and navigating content Discipline (tasks) Domain (work products) – based on subject area Work Product Kind (work products) – based on usage/type Role Set (roles) Tool (tool mentors) Custom Category (any) – your own way of organizing content

20. Process Delivery processes Capability patterns Activities Process: delivery processes, capability patterns, and activities • Delivery Processes – are used to define a complete integrated approach to a specific type of project • Capability patterns – are a special type of process used to define a stereotypical way of performing work related to a particular subject, which might be used as a building block for assembling delivery processes or bigger patterns • Activities – are used to support the nesting and logical grouping of related breakdown elements

21. Browse instantly and preview the generated documentation Diagrams generated based on process model information: Role overview showing all the roles responsibilities. Text entered into forms rendered into html pages following style sheet-based common structure, look and feel.

22. Publishing: PDF and Microsoft Word Publishing PDF • The content of the ITUP library must be broken into two separate configurations Publishing Word • If you encounter problems when opening a published Word file, make sure Microsoft Word 2003 or later is used. • If you are opening large file, expect to take long time to open because Word needs enough time to paginate and spell check. Do not end the Word publishing too eary. Microsoft Word 2007 is better at opening large files.

23. Publishing can cause memory issues • RMC can fail by an out of memory error. • Exit RMC and use the provided methods to resolve the issue (see Notes page)

24. Publishing a single process Selecting a particular process in RMC publishes only the process in the process tab, and any other views in the configuration. • Reason – RMC, by design, publishes to HTML and assumes that a whole site is comprised of the other tabs, but only includes the selected process. Resolution is to copy the configuration to create a new one. • Delete all the tabs you do not want • Create a new custom category, and only assign the desired process into the custom category • Set that custom category as the only view in the configuration for publishing

25. Reporting Process engineer and project manager needs • Adhere to the organization documentation requirements • Publish entire process as well as selected pieces • Publish content for review and process implementation • Define and run analysis reports on a method library or process RMC 7.2 Reporting (powered by Eclipse BIRT technology) • Create any kind of report on all the information in an RMC method library • Powerful BIRT visual report designer(well documented, tutorials and books available) • Alternative output formats: MS Word, HTML • Easy to use for with predefined report building blocks for RMC

26. Processes • Formulate Workflows • Make use of method content Activity detail diagram Activity diagram

27. Libraries, plug-ins, and configurations The ITUP plug-in contains both method content and processes.You can build your plug-in using ITUP and base_concepts plug-ins as the base. • The ITUP library contains: • Aset of method plug-ins • A set of configurations that are defined by selecting method plug-ins or their components • ITUPconfigurations are published to become the process Web site

28. Perspectives and views Authoring perspective Browsing perspective Library view Scope: The library. Elements: Plug-ins with their method and process contents. Also configurations. Operations: Create and modify. Configuration view Scope:The selected configuration with its selected content packages. Elements: Method elements and process elements organized in folders. Operations: Modify. Configuration view Scope: The selected configuration with its selected content packages and variability resolved. Elements: Method elements and process elements organized in folders. Operations: View.

29. Authoring perspective Library view Double-click an element in the Library view to access the contents for editing in the Editor window. Descriptions and other information can be modified. The Authoring perspective is used to create and edit all plug-ins, their contents, and all configurations. Configuration view

30. Browsing perspective Diagrams generated based on process model information: Role overview showing all the roles responsibilities. The Configuration view is accessible from both the Authoring and Browsing perspectives. The Browsing perspective is used to see how a page will look when it is published. Double-click an item in the Configuration view to display the contents in the window. Contents cannot be modified in the Browsing perspective.

31. Process content Plug-in Process content is in content packages • Package contents • Roles • Tasks • Work products • Supporting materials (called Guidance) • Other process contents in Standard Categories • Disciplines • Domains • Role Sets • Tools

32. Workflows are separate from content Process workflows are represented as Capability Patterns Customized workflows are called Delivery processes

33. RMC Customization Overview

34. Content variability • Maintains existing content unchanged during customization • Is applicable to: • Roles • Work products • Tasks • Custom categories • Is not applicable to: • Processes (Capability patterns)

35. Content variability types • Contributes • The element adds to the base element • Extends • The element inherits characteristics of the base element • Replaces • The element replaces parts of the base element • Extend and Replace • The element inherits characteristics of the base element and establishes redefined values NOTE: An element with variability options is identified in the Description view.

36. Example: Effects of variability on role elements Example: Effects of variability on role elements Role1 Role1 Role1 Task 1 Work product 1 Task 1 «itupReplaces» «itupExtends» «itupContributes» «itupContributes» Role2 Role3 Role2 Role2 Task 2 Work product 2 Task 2 Task 3 Results withContributes Results withReplaces Results withExtends Role 1 Task 1 Task 2 Task 3 Role 2 Task 2 Role 1 Work product 1 Role 2 Work product 1 Work product 2

37. Main effects with different variability types

38. Demo Rational Method Composer

39. Customizing ITUP Composer

40. Four main customizing scenarios Use the existing processes. Individual users can create personal views. Evaluate the ITUP processes. I do not need adifferent process. I need a different process. Make your configuration selections in the tool. Select custom categories (views) and publish. Evaluate the existing library containing ITUP plug-ins and configurations. A Create a plug-in. Work in the Processes folder and create a delivery process. Populate your delivery process from ITUP capability patterns. Tailor at the process level. Select or create a configuration and custom categories. Publish. I can use existing ITUP plug-in components to build my process. B I can tailor existing capability patterns and delivery processes to build my process. Create a plug-in. Work in the Method Content folder and create new content elements. Create relationships between new elements. Select or create a configuration and custom categories. Publish. C I need to add tasks, work products, roles, or guidances in the ITUP plug-in. Create a plug-in. Work in the Method Content folder and create new content elements. Create relationships between new elements. Create variability relationships to existing elements. Select or Create a configuration and custom categories. Publish. D I need to change tasks, work products, roles, or guidances in the ITUP plug-in.

41. Customizing ITUP Composer Publish a customized “ACME” method web site with changes to the Out-Of-The-Box (OOTB) ITUP content. Steps to define new elements and publish: • Create a plug-in. • Create a method content package in a new plug-in. • Create tasks, roles, work products, and guidances in the new plug-in. • Create relationships between the new elements. • Create a content variability relationship from the ACME plug-in to the ITUP content. • Create your own processes (delivery processes) by reusing parts of the ITUP processes (Capability Patterns). • Create and specify a new configuration containing ITUP content and the new plug-in. • Create a new view (custom category) and attach it to your configuration. • Publish (method content and delivery processes) as a Web site.

42. Creating a new method plug-in

43. Creating a content package

44. Customizing roles 2 1 3

45. Customizing work products 2 1 3

46. Customizing tools and tool mentors

47. Customizing tasks

48. Customizing processes

49. Customizing processes (continued)

50. Creating a new custom category (view)