November 25, 2015 © IBM Corporation Unified Method Framework (UMF) RMC Reference Architecture Overview Kelli Houston

© IBM Corporation 2 Purpose and Intended Audience  Purpose Provide an overview of a reference architecture for a Unified Method Framework (UMF)-compliant RMC method library Describe what is included in the reference architecture and how to use it to author a UMF-compliant method  Intended Audience Anyone interested in authoring UMF-compliant methods  Pre-Requisites Understanding of what the UMF is and its key concepts Understanding of the basics of method authoring

© IBM Corporation 3 Topics  Introduction  What is in the Reference Architecture  How To Use the Reference Architecture

© IBM Corporation 4 Why is a Reference Architecture Needed?  Structuring a method is critical and can get complex, especially for method frameworks  The UMF and its constraints and conventions adds to the complexity Guidance and examples of best practices is needed

© IBM Corporation 5 Reference Architecture Value Proposition  Provides a self-documenting example of how to structure a UMF- compliant RMC method library and its plug-ins  Provides a collection of UMF-compliant plug-in “templates” that can be used to jump-start UMF method structuring activities (structuring of the library and structuring of the individual plug-in types and their parts)  Benefits Reduces need for users to be RMC architecture experts Improves efficiency Eliminates the need to structure from scratch

© IBM Corporation 6 Prerequisite UMF Concepts  UMF plug-in types and their relationships  UMF configuration types and their relationships  UMF method library element naming conventions

© IBM Corporation 7 Topics  Introduction  What is in the Reference Architecture Plug-Ins Configurations  How To Use the Reference Architecture

© IBM Corporation 8 Reference Architecture is an RMC Method Library  Includes example of each UMF plug-in type (and their plug-in parts) and shows how they are related (what plug-ins are dependent on what plug-ins)  Includes example of each UMF configuration type and what they include

© IBM Corporation 9 Plug-In Overview: Plug-In Scope and Types  Plug-In Types (UMF plug-in types) Method Management Plug-ins Method Plug-Ins  Scope: General Context-Specific Cross-Context

© IBM Corporation 10 UMF Plug-In Types  Core Plug-Ins: Contain framework elements intended to be shared across elements in the framework Multiple core plug-ins Usually each context has a core  Practice Plug-Ins: Contain the practice elements One practice plug-in per practice Only depend on core plug-ins  Process Plug-Ins: Contain the elements that define a specific process Capability patterns and/or delivery processes Process-specific extensions to existing elements Processes that assemble tasks from specific practices One process plug-in per process/process family Depend on core and specific practice plug-ins  Publish Plug-ins: Contain the elements specific to publishing a specific configuration Welcome pages, configuration-specific navigation views One publish plug-in per publishable configuration Depend on process, practice and/or core plug-ins Core + Practices = Foundation for reuse across lifecycles (concrete elements) Core plug-ins Practice plug-ins Process plug-ins Publish plug-ins

© IBM Corporation 11 UMF Core Plug-In Types  Slot plug-ins: Contain slot definitions and associated guidance  Common plug-ins: Contain common reusable elements (e.g., common work products and common guidance)  Role Definition plug-Ins: Contain role and role set definitions  Category Definition plug-ins: Contain standard category definitions (e.g., discipline, domain and work product kind definitions) Role sets defined in Role Definition plug-ins Tools defined in Tool Definition plug-ins (tools are separately reusable)  Tool Definition plug-ins: Contain tool definitions Tool mentors are in practice plug-ins or common plug-ins  Navigation View plug-ins: Contain navigation view elements (e.g., navigation view building blocks, a generic navigation view and Do Not Publish category)  Copyright plug-ins: Contain the copyrights. One copyright plug-in per licensing level

© IBM Corporation 12 UMF Plug-In “Parts”  Each plug-In type may be implemented by one or more “physical” plug-in "parts"  Base plug-in: Contains the base method element definitions One base plug-in May depend on other Base plug-ins.  Extend plug-ins: Contain elements that extend elements in the Base plug-in. Zero or more Extend plug-ins (multiple extensions) Depend on the Base plug-in that contain the elements being extended “Booster” plug-ins  Assign plug-ins: Contain the delayed assignment of elements in the Base plug-in Zero or more Assign plug-ins (alternate assignments, assignment extensions) Depend on the Base plug-in and the plug-ins containing the elements being assigned to May depend on other Assign plug-ins if extending those assignments

© IBM Corporation 13 Topics  Introduction  What is in the Reference Architecture Plug-Ins General Plug-Ins Context-Specific Plug-Ins Cross-Context-Specific Plug-Ins Configurations  How To Use the Reference Architecture

© IBM Corporation 14 General Plug-Ins General plug-ins are “givens” (you don’t create them) – they are shared across contexts

© IBM Corporation 15 Topics  Introduction  What is in the Reference Architecture Plug-Ins General Plug-Ins Context-Specific Plug-Ins Cross-Context-Specific Plug-Ins Configurations  How To Use the Reference Architecture

© IBM Corporation 16 Context-Specific Plug-in Types Create one set per context Depend on general plug-ins

© IBM Corporation 17 Context-Specific Plug-ins and Dependencies

© IBM Corporation 18 Topics  Introduction  What is in the Reference Architecture Plug-Ins General Plug-Ins Context-Specific Plug-Ins Cross-Context-Specific Plug-Ins Configurations  How To Use the Reference Architecture

© IBM Corporation 19 Cross-Context Plug-in Types Dependent on context-specific and general plug-ins

© IBM Corporation 20 Cross-Context Plug-ins and Dependencies

© IBM Corporation 21 Topics  Introduction  What is in the Reference Architecture Plug-Ins Configurations Publish Configurations Process Construction Configurations  How To Use the Reference Architecture

© IBM Corporation 22 Publish Configurations: Plug-In and Package Selection

© IBM Corporation 23 Publish Configurations: Views

© IBM Corporation 24 Publish Configurations as Default Configurations

© IBM Corporation 25 Topics  Introduction  What is in the Reference Architecture Plug-Ins Configurations Publish Configurations Process Construction Configurations  How To Use the Reference Architecture

© IBM Corporation 26 Process Construction Configurations

© IBM Corporation 27 Process Construction Configurations as Default Configurations

© IBM Corporation 28 Topics  Introduction  What is in the Reference Architecture  How To Use the Reference Architecture

© IBM Corporation 29 When Would You Use the Reference Architecture  When structuring your method library (i.e., creating plug-ins and/or configurations) Reference architecture includes an example of each UMF plug-in type and shows how they are related (what plug-ins are dependent on what plug-ins) Reference architecture includes an example of each UMF configuration type and what they include  When structuring the internals of a plug-in Reference architecture includes an example of each plug-in type and each of their plug-in parts, as well as provides an example of a recommended internal structure Reference architecture provides a recommended relationship between processes in plug-ins and the UMF configuration types

© IBM Corporation 30 Realization of the Reference Architecture in RMC  Portions of the Reference Architecture have been included in RMC 7.5 as plug-in templates  This list of templates will grow over time

© IBM Corporation 31 Scenario: Creating a New Plug-In 1.Determine the scope (e.g., general, context-specific, cross- context), type (UMF plug-in type), and licensing level (UMF licensing level) of the plug-in to be created 2.Create/import any plug-ins that the new plug-in must be dependent on and any plug-ins they must be dependent on, etc. 3.Create the new plug-in Use the plug-in templates provided by RMC Create any necessary dependencies on other plug-ins based on the examples provided in the reference architecture

© IBM Corporation 32 Scenario: Creating a New Configuration 1.Determine the scope (e.g., general, context-specific, cross- context), type (UMF configuration type), and licensing level (UMF licensing level) of the configuration to be created. 2.Determine what plug-ins are to be included in the configuration. Make sure they are available for selection in the configuration. If not, import them (and any plug-ins they depend on) into the current library. 3.Create the new configuration Use the configuration templates described in the reference architecture Select the plug-ins to be included in the configuration, as well as the navigation views to be published (for publish configurations)

© IBM Corporation 33 Questions

© IBM Corporation 34 Thank You