Epf composer overviewpart1
Upcoming SlideShare
Loading in...5
×
 

Epf composer overviewpart1

on

  • 757 views

about eclipse platform

about eclipse platform

Statistics

Views

Total Views
757
Views on SlideShare
757
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Epf composer overviewpart1 Epf composer overviewpart1 Document Transcript

  • Eclipse Process Framework ComposerPart 1: Key ConceptsSecond Revision, April 2007by Peter Haumer, phaumer@us.ibm.comSolution architect, IBM Rational Software This two-part article offers an introduction to the process engineering approach and tool sup- port provided by the Eclipse Process Framework (EPF). It presents a process management tool platform and conceptual framework for authoring, tailoring, and deploying development processes. Part One, presented here, offers a high-level understanding of the key capabilities of the Eclipse Process Framework Composer tool and it provides an overview of key concepts and typical usage scenarios. Keywords: Eclipse Process Framework, process engineering, project management, software development proc- ess, requirements management, configuration management, agile development, software development best prac- tices, IBM Rational Method Composer, Rational Unified Process, SPEM. Author bio: Dr. Peter Haumer is an Eclipse Process Framework commit- ter. He is a solution architect for the IBM Rational Method Composer product platform and responsible for defining next generation process engineering tools. He represents IBM at the OMG in the SPEM 2.0 initia- tive. 1
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerFor companies and organization evolving into on-demand businesses 1 to compete in a world increasinglyenabled by multiple technologies and the disappearance of geopolitical boundaries -- “flatteners,” asThomas Friedman terms these enablers 2 -- the creation, integration, modernization, extension, and de-ployment of systems and software applications has become critical. Today, information technology notonly supports the business but, in many organizations, actually defines the business. 3 We are witnessingthe emergence of a new computing paradigm, often referred to as “business-driven development” 4 ; BDDorganizations fully integrate and align flexible development processes with business process developmentfor different lines of businesses as well as IT operations to improve business performance. Running business-driven development projects requires a very flexible development processes. Suchprocesses not only have to provide concrete support and guidance for modern development practices,such as agile, iterative, architecture-centric, risk- and quality-driven software development, but also haveto be flexible enough to support rapid tailoring and adoption of the process itself. These processes alsoneed to evolve across projects, and the projects being executed must themselves be able to evolve as busi-ness needs change mid-way to completion. 5 This paper introduces the Eclipse Process Framework Composer (EPF Composer), which addressesthe needs for BDD as well as modern agile development practices. The EPF Composer is a process man-agement tool platform and conceptual framework, which provides an easy to learn user-experience andsimple to use features for authoring, tailoring, and deploying of development process frameworks. Thepaper presents the EPF Composer version 1.0.2 that is available as a free download under the Eclipse1 See IBM, “On Demand Business,” http://www.ibm.com/ondemand, 2005. Also, Alfredo Gutierrez, “e-business on demand: Adevelopers roadmap,” http://www-128.ibm.com/developerworks/ibm/library/i-ebodov/index.html, IBM developerWorks, 2003.2 Thomas L. Friedman, The World is Flat: A Brief History of the 21st Century, Farrar, Straus and Giroux, 2005.3 Asiff Hirji, CIO Ameritrade, Gartner Financial Services Technology Summit,http://www.computerworld.com/careertopics/careers/story/0,10801,104482,00.html, Aug. 2005.4 Per Kroll and Walker Royce, “Key principles for business-driven development,” Rational Edge, http://www-128.ibm.com/developerworks/rational/library/oct05/kroll/index.html, October, 2005.5 Per Kroll and Walker Royce, “Key principles for business-driven development,” Rational Edge, http://www-128.ibm.com/developerworks/rational/library/oct05/kroll/index.html, October, 2005. 2
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerPublic license at the EPF homepage 6 . IBM also offers a commercial version of the EPF Composer toolnamed IBM Rational Method Composer 7 (RMC) that ships with the IBM Rational Unified Process (RUP)and provides additional enterprise capabilities not described in this article. This paper is presented in two parts. Part One offers a high-level understanding of the key capabilitiesof the EPF Composer environment, and it provides an overview of key concepts and typical usage scenar-ios. Part Two will provide more specific details and examples about authoring method content and proc-esses with EPF Composer.6 http://www.eclipse.org/epf/7 http://www-128.ibm.com/developerworks/rational/products/rup 3
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer1 Eclipse Process Framework Composer: What is it for?Eclipse Process Framework Composer (EPF Composer) is a tool platform for process engineers, projectleads, project and program managers who are responsible for maintaining and implementing processes fordevelopment organizations or individual projects. Typically, two key problems need to be addressed for such a process implementation. First, developers need to understand the methods and key practices of software development. Theyneed to be familiar with the basic development tasks, such as how to elicit and manage requirements, howto do analysis and design, how to implement for a design or for a test case, how to test implementationsagainst requirements, how to manage the project scope and change, and so on. Although popular agiledevelopment methods rely on self-organizing teams 8 – assuming that developers implicitly know how todo such work without documenting their methods – and learning through tutoring, many organizationsstill need to rely on explicitly documenting and educating such methods to establish common and regu-lated practices. In addition, many organizations are required to do so for compliance. (Note, that EPFComposer supports both of these audiences by making explicit method content optional as outlined inSection 2.) Second, development teams also need to define how to apply their development methods and bestpractices throughout a project lifecycle. That is, they need to define or select a development process. Forexample, requirements management methods have to be applied in one fashion during the early phases ofa project, where the focus is more on elicitation of stakeholder needs and requirements and scoping avision, and in a different fashion during later phases, where the focus is on managing requirements up-dates and changes and performing impact analysis of these requirements changes. Teams also need aclear understanding of how the different tasks within the methods relate to each other: for example, howthe change management method impacts the requirements management method as well as the regression 4
  • Eclipse Process Framework Composer: Key Concepts Peter Haumertesting method throughout the lifecycle. Even self-organizing teams need to define a process that gives,at minimum, some guidance on how the development will be scoped throughout the lifecycle, when mile-stones will be achieved and verified, and so on. The EPF Approach Standardize representation and Develop and manage Processes manage libraries of reusable for performing projects Method Content Process for Process assets Content on agile JUnit user Custom Application patterns development guidance Development with J2EE Standard or Content on Content reference processes Process for managing on J2EE Embedded System Enactable project iterative development Development plan templates Configuration Corporate Guidance on mgmt Process for guidelines serialized java beans guidelines SOA Governance on compliance Configure a cohesive process framework customized for my project needs Create project plan templates for Enactment of process in the context of my projectFigure 1: The EPF Approach of managing libraries of reusable method content that can be used toassemble processes. Reusable method content and processes can be configured by EPF Composerusers for specific project needs and then published for enactment as project plans or process docu-mentation. EPF Composer has two main purposes, which address the above needs:1. To provide for development practitioners a knowledge base of intellectual capital that allows them to browse, manage, and deploy content. This content can be licensed, acquired, and, more importantly, accommodates your own content consisting of, for example, method definitions, whitepapers, guide- lines, templates, principles, best practices, internal procedures and regulations, training material, and any other general descriptions of how to develop software. This knowledge base can be used for ref- erence and education and forms the basis for developing processes (the second purpose). EPF Com- poser is designed to be a content management system that provides a common management structure8 See Ken Schwaber and Mike Beedle, “Agile Software Development with SCRUM,” Prentice Hall, 2001. 5
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer and look and feel for all of your content, rather than being a document management system in which you would store and access hard to maintain legacy documents all in their own shapes and formats. All content managed in EPF Composer can be published to html and deployed to Web servers for dis- tributed usage.2. To provide process engineering capabilities by supporting process engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development projects. EPF Composer provides catalogs of pre-defined processes for typical project situations that can be adapted to individual needs. It also provides process building blocks called capability patterns that represent best development practices for specific disciplines, technologies, or development styles. These build- ing blocks form a toolkit for quickly assembling processes based on project specific needs. EPF Composer also allows you to set-up your own organization-specific capability pattern libraries. Fi- nally, the documented processes created with EPF Composer can be published and deployed as Web sites. 6
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerFigure 2: A Web site published by Eclipse Process Framework Composer containing and presentingall method and process content selected by the user for publication. The example shows the EPFOpenUP/Basic 9 framework.The Eclipse Process Framework project aims at providing solutions to common problems that develop-ment leads and teams face when acquiring and managing their methods and processes. For example:– Development teams need easy and centralized access to the information: many development organi- zations do not maintain central databases of their practices and processes. Typically, processes are ei- ther not documented at all, or they are physically distributed in various presentation formats. Proc- esses need to be deployed and accessible at the workplace providing process documentation while the work is being performed. 7
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer– It is difficult to integrate development processes that ship in their own propriety format: every book and publication presents method content and process use a different format. A lack of widely adopted standards and clearly defined concepts for representing method content and processes make it hard to integrate processes from different vendors and sources.– Teams lack an up-to-date knowledge base for educating themselves on methods and best practices: before effectively performing development processes, teams need to be trained. They require a knowledge base or encyclopedia on development methods which consistently reflects the same prac- tices on which processes are being defined projects are being performed.– Teams need support for right-sizing their processes: they need interactive guidance for answering the question of ‘how much process?’ do they need. Processes need to be tailored not only for each pro- ject, but also continuously throughout the project lifecycle. Hence, processes need to be scaled-up or scaled-down on demand with the ability to easily assemble new or tailor existing processes to address organization, project, or even project phase specific needs.– Ensure compliance to standardized practices: teams need the ability to standardize on practices and processes within the organization, manage and deploy these process definitions and provide the abil- ity for individual projects to still perform auditable tailoring and modification of these processes.– Effective execution of processes in project: Teams need to bridge the gap between process engineer- ing and process enactment by using similar representation and terminology. Managers need the abil- ity to import processes directly into their project execution environments that link back from the plan- ning elements, such as tasks to perform and their descriptions.9 See Ricardo Balduino, Brian Lyons, " OpenUP/Basic - A Process for Small and Agile Projects", athttp://www.eclipse.org/epf/general/OpenUP_Basic.pdf, eclipse.org/epf, 2006. 8
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer2 Overview of key terminology and conceptsTo effectively work with Eclipse Process Framework Composer, you need to understand a few conceptsthat are used to organize the content. This section provides a general overview of these concepts.2.1 Method content versus processThe most fundamental principle in the Eclipse Process Framework is the separation of reusable coremethod content from its application in processes. This directly relates to the two purposes of EPF Com-poser described in the Section 1. Almost all of EPF Composer’s other concepts are categorized along thisseparation, as shown in Figure 6 (see further below). Method content describes what is to be produced,the necessary skills required, and the step-by-step explanation describing how specific development goalsare achieved. These method content descriptions are independent of a development lifecycle. Processesdescribe the development lifecycle. They take the method content elements and relate them into semi-ordered sequences that are customized to specific types of projects.Figure 3: A two-dimensional representation of the Unified Process separation of method content andprocess. 9
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerThis separation of Method Content and Process is by no means a new idea. For example, it has been pre-sent in the Unified Process (UP) since its inception, also sometimes referred to as the static versus thedynamic structure 10 , and had already been described for OOSE 11 in 1992. Figure 3 shows a two-dimensional representation of how this separation is depicted in the UnifiedProcess (UP) 12 as well as the Rational Unified Process (RUP). Method content, describing how devel-opment work is being performed, is categorized by disciplines along the y-axis. This work is then refer-enced and sequenced in a process along the x-axis representing the timeline. This is the lifecycle of adevelopment project; it expresses when specific work will be performed. The graphs in the middle repre-sent an estimated workload for each discipline. As you can see, for example, one never stops working onrequirements in UP, but there are certainly peak times in which most of the requirements elicitation anddescription work is performed. There are also times at which a downward trend needs to be observedwhere fewer requirements changes have to be processed to bring the project to a close. This avoids “fea-ture creep,” in which requirements work remains constant or even increases. Hence, a process expressesfor such a lifecycle the variances of work being performed in the various disciplines, and the work itself isexplicitly defined and described by method content.2.2 Method ContentTo learn about development methods, people do research in libraries or they receive training. Many de-velopment methods are described in books, articles, training material, standards and regulations, and otherforms of documentation. These sources usually document methods in different ways, but mostly by pro-viding step-by-step explanations for a particular way of achieving a specific development goal under gen-eral circumstances. Examples include transforming a requirements document into an analysis model;defining an architectural mechanism based on functional and non-functional requirements; creating a10 Philippe Kruchten, “The Rational Unified Process: An Introduction,” Addison Wesley, 2003.11 I. Jacobson et al., “Object-Oriented Software Engineering: A Use Case Driven Approach,” Addison-Wesley, 1992.12 Ivar Jacobson et al, “The Unified Software Development Process”, Addison Wesley, 1998. 10
  • Eclipse Process Framework Composer: Key Concepts Peter Haumerproject plan for a development iteration; defining a quality assurance plan for functional requirements;redesigning a business organization based on a new strategic direction, and so on. EPF Composer allows you to take such content and to structure it in one specific way using a prede-fined schema. This schema is an evolution of the SPEM 1.1 OMG specification 13 referred to as the Uni-fied Method Architecture (UMA). Major parts of UMA went into the recently adopted revision of SPEM,SPEM 2.0 14 . EPF is aiming to fully support the final SPEM 2.0 in the near future. The UMA and SPEMschemata support the organization of large amounts of descriptions for development methods and proc-esses. Such method content and processes do not have to be limited to software engineering, but can alsocover other design and engineering disciplines, such as mechanical engineering, business transformation,sales cycles, and so on.Following the UMA and soon SPEM 2.0 schema, method content is represented in EPF Composer as aconstruct of roles defining development skills and responsibilities for work products. These work prod-ucts are produced by tasks that are performed by the roles and have work products as inputs and outputs.Figure 4 depicts typical sources for method content, as well as how the method content is represented inEPF Composer. The screen capture in Figure 4 shows how such method content elements are organizedin tree browsers on the left. Similar to a library, these tree browsers provide different indexes of theavailable elements for rapid access. The screen capture shows on the right an example of a task presenta-tion. This task presentation defines the task in terms of steps that need to be performed to achieve thetask’s purpose. You also see that the task has various relationships, such as relationships to roles that actas performers of the task and to work products that serve as inputs and outputs to the task. EPF Com-poser maintains and presents these relationships as hyperlinks connecting elements to each other. (Moredetails on tasks, roles, and work products will be provided in Part Two of this paper) In addition to roles,13 OMG, ”Software Process Engineering Metamodel,” version 1.1, formal/2005-01-06,http://www.omg.org/technology/documents/formal/spem.htm, 2005.14 OMG, ”Software Process Engineering Metamodel,” version 2.0, Final Adopted Specification, ptc/07-03-03,http://www.omg.org/cgi-bin/doc?ptc/07-03-03. 11
  • Eclipse Process Framework Composer: Key Concepts Peter Haumertasks, and work products, EPF supports the addition of guidance elements. Guidance is supplementaryfree-form documentation such as whitepapers, concept descriptions, guidelines, templates, examples, andso on. IC / Best Practices Books / Publications Standards / Regulations Homegrown MethodsFigure 4: Method content can be found in books and publications on software engineering methods.Eclipse Process Framework Composer expresses method content using concepts such as tasks, roles,work products, and guidance. This figure shows an example of how a task is presented in EPF.2.3 ProcessesA development process defines sequences of how work is being performed by roles and how work prod-ucts are being produced and evolved over time. Figure 5 shows that processes are typically expressed asworkflows or breakdown structures. 12
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer Workflow Workflow Breakdown / Iterations / Increments / Sprints / WaterfallFigure 5: Processes are expressed as workflows or breakdown structures in Eclipse Process Frame-work Composer. They utilize method content and define how methods are being applied throughoutthe project lifecycle they describe.Defining a strict sequence, as in a waterfall model, is just as much a process as defining a semi-orderedsequence of iterations in parallel work. These simply represent different development approaches. 15 Indefining a process, one can take method content and combine it into structures that specify how the workshall be organized over time to support different development approaches, as well as to meet the needs ofa particular type of development project, such as software for an online system versus software and hard-ware for an embedded system.15 For an in-depth comparison of these two approaches, see Walker Royce, “Software Project Management: A Unified Frame-work,” Addison Wesley Longman, 1998. 13
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer The Eclipse Process Framework aims at supporting processes based on many different developmentapproaches, development culture, and development process representation. EPF Composer can be used todefine different lifecycle models such as waterfall, incremental, or iterative lifecycles. EPF Composeralso supports different presentations for process such as work-breakdown structure or workflow presenta-tions. The EPF Composer screen capture on the right in Figure 5 shows an example of a process presented asa breakdown structure of nested activities. It also shows a workflow synchronized with this breakdownpresented by an activity diagram for one of the activities: the inception phase. The figure also illustrateshow method content such as tasks that define which role is performing work with inputs and outputs canbe utilized in processes. It indicates with the two blue arrows that the particular method content task “De-tail a Use Case,” from Figure 4, has been applied in the process twice: first, in the inception phase underthe activity “Define the System” and secondly, in the elaboration phase in the activity “Refine the systemdefinition”. Below each of these task applications you see lists of the performing roles as well as theinput and output work products. If you look closely, you see that these lists are different for each of thesetwo task applications, expressing differences in performing the detailing use cases method throughout thelifecycle. You see different roles involved and changes in the list of inputs to be considered and outputsto be produced or updated. In this example, these changes were defined by the author who created thisprocess to express the exact focus of the task performance for each occurrence at this particular point inthe lifecycle. In addition to updating the roles plus input and output work products for a task descriptor,you can also provide additional textual descriptions and select the exact steps of the task that should orshould not be performed in this particular occurrence of the task. As you will see in Part Two of thisarticle, the application of tasks into processes is a purely optional thing, which helps to make processesexpress explicitly how they shall be performed; or at least proving guidance on how it could be per-formed. However, processes in EPF Composer can also be kept free of this explicit information and bekept to expressing minimal or no prescriptive task. 14
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer2.4 Summary: EPF Concepts to Create Method FrameworksFigure 6 shows how the key Eclipse Process Framework concepts relate to method content versus processseparation and how you bring instances of these concepts together to build a Process Framework. Typi-cally the word framework is used in the context of an environment one can use to define partial or com-plete solutions for a particular problem domain using reusable structures as starting points as well asbuilding blocks for creating these new solutions. A Process Framework is a similar thing for the method-ology domain: It defines reusable method content, processes, building blocks, and tools that one can util-ize to define project or organization specific processes and methods. The EPF Website currently providesthree separate process frameworks for user to choose from (such as the OpenUP/Basic, Extreme Pro-gramming, and Scrum frameworks 16 ), but you can also use EPF Composer to create complete newframeworks from scratch.16 See http://www.eclipse.org/epf/downloads/downloads.php. 15
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer Method/Process FrameworkFigure 6: A summary of the proposed terminology overview for the Eclipse Process Framework.As you see in Figure 6, method content is primarily expressed using work products, roles, tasks, andguidance. Guidance, such as guidelines, concepts, templates, checklists, examples, or roadmaps, is posi-tioned right in the intersection of Method Content and Process. In other words, guidance can be related toand express information relevant to method content as well as processes. On the right-hand side of Figure6 you see the concepts used to represent processes in the Eclipse Process Framework. The main conceptis the activity that can be nested to define breakdown structures. Activities relate to each other to definethe flow of work. They contain references to method content, which we are going to introduce as descrip-tors in Part Two of this article. Activities are used to define processes of which the Eclipse ProcessFramework suggests two main kinds: delivery processes and capability patterns. Delivery processes rep-resent a complete and integrated process template for performing one specific type of project. They de-scribe a complete end-to-end project lifecycle and can be used as a reference for running projects withsimilar characteristics. Capability patterns are processes that express process knowledge for a key area ofinterest such as a discipline or a best practice. They can be directly used by process practitioners to guide 16
  • Eclipse Process Framework Composer: Key Concepts Peter Haumertheir work. They are also used as building blocks to assemble delivery processes or larger capability pat-terns, thus ensuring optimal reuse and application of the key practices they express. The concepts depicted in Figure 6 are defined in a way that they can be used quite independently fromeach other, which allows you to use EPF Composer to define process frameworks for different audienceswith relatively different process needs, process cultures, or even a different understanding of what processconstitutes. In other words, you could define your process framework by using all of the concepts or justthe subset that fits your needs. For example, if you work in a very agile environment you might just cre-ate descriptions of your guiding principles, practices, and values as guidance elements. If you want to adda bit more formability then you could add definitions for standard roles and work products. The nextlevel of formability would add explicit descriptions of task defining how standard development workshall be performed. All people would work with at that level would be this collection of tasks that can beused just for educating new team members, but also for creating concrete work items in a team support orscheduling system. All of these concepts could be used and managed in EPF Composer as describedabove without defining and using any processes, thus, by just providing a knowledge base of practices. Processes can be used in a similar independent way without using any method content at all. For ex-ample, teams that inherently know their practices and do not need any additional documentation couldjust use the process concepts to outline the lifecycle of their general development projects defining keymilestones and high-level activity on how to achieve these. As we will show with concrete examples inPart Two of this article, a light-weight process might contain only of a definition of phases or iterations,the milestone for each iteration as well as a list of key deliverables that shall be produced for each itera-tion, and perhaps lists of roles being responsible for these deliverables. Any combination of both of thesesides (the method content only approach or the process only approach) is also possible: You can defineprocesses in EPF Composer that either use a full set or just use a minimal set of method content. Finally,if you work in a very rigor, compliance focused environment you may choose to define rich processes that 17
  • Eclipse Process Framework Composer: Key Concepts Peter Haumerintegrate with explicit method content, provide detailed guidance as well as categorization schemes thatlet you clearly define practices and link compliance criteria and checklists for each of these.3 Typical Usage Scenarios for Working with EPF ComposerIf you are working with process framework comprising of method content and processes from the EPFproject such as the OpenUP/Basic framework, then you are mostly interested in using and tailoring thiscontent. Thus, this section provides an overview to the most typical usage scenarios for the Eclipse Proc-ess Framework Composer for using and tailoring an existing process framework. In Part Two of thisarticle we will extend on these scenarios with additional examples that you would consider when develop-ing new process frameworks with EPF Composer. Although EPF Composer is a powerful process au-thoring environment, there are various degrees of authoring and modes of utilizing EPF Composer’s ca-pabilities. As mentioned before, EPF provides content for various development approaches in its Ope-nUP/Basic, Scrum, and Extreme Programming frameworks comprising of a lot of method and processescontent for different needs. Therefore, in many cases not much authoring is actually required. All that isneeded is selecting, configuring, and tailoring the existing content to fit your needs. The simplest usage scenario for EPF Composer involves simply using the processes the way they ship.For the EPF Composer you are able to obtain rapidly growing libraries of content donated or sold by theproject’s committers. The commercial version of EPF Composer called IBM Rational Method Composerfor example, contains the complete sources of the Rational Unified Process framework (RUP v7.0), whichconsists of thousands of method and process elements for a broad variety of development situations. Italso includes various method plug-ins extending RUP with domain-specific additions such as develop-ment for concrete technologies such as J2EE or different development circumstances such as adopting acommercial of the shelves system (COTS). However, be aware that no organization or project requires all of this documentation all at once. In-stead, you should work with a specific subset called a method configuration, which tailors the process for 18
  • Eclipse Process Framework Composer: Key Concepts Peter Haumerspecific needs. During the selection and tailoring activities, you still might want to include your owncontent and link that into the existing available material. This is where EPF Composer’s authoring capa-bilities provide you with easy-to use but powerful editors to do this in a seamless way. The followingsubsections summarize the most common usage scenarios for EPF.3.1 Selecting and configuring existing method content and processesThis represents one of the simplest EPF Composer usage scenarios. You select the process and underly-ing method content that fits your needs by browsing the method library, which contains all of your pur-chased content as well as content that you downloaded from the Eclipse Process Framework Web site.Once you find a close fit, you start configuring this process (as depicted in Figure 7) by selecting or de-selecting what EPF calls “method packages.” Removing a method package removes all references to thecontent of this package from everywhere in the process. You can, for example, “strip down” a process tocontain a minimal subset of its content by removing packages that contain elements of work that you donot want to perform. Or, you could add method packages with very specific content for a particular do-main that this process supports as an option (for example, “plain” J2EE versus J2EE for SOA-specificcontent). 19
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerFigure 7: Configure processes and method content by selecting or de-selecting method packages thatshall be referenced or not referenced by the processes. You can create several method configurationsdefining filters on the overall method library in EPF Composer. Use the combo box in the toolbar toquickly switch between different method configurations. The Configuration view in the lower left cor-ner always displays the resulting contents of the selected method configuration.Method content and processes are organized in EPF method libraries according to the way they buildlogical units for useful configurations. For example, all content belonging to one specific discipline, suchas requirements or change management, can be found in one method package. Each of these packagesmight be further divided into sub-packages for specific practices in these disciplines. For example, Ope-nUP/Basic factors all of its content related to visual modeling into a separate package. Thus, you can addor remove visual modeling from the OpenUP/Basic with just one simple mouse-click by selecting or de-selecting the right package. The result is a configured process that you then publish and deploy to your team in HTML (see Figure2 for an example) and/or export into your project management tool. Note that you could create suchmethod configurations for processes that span the whole development lifecycle as well as just one or more 20
  • Eclipse Process Framework Composer: Key Concepts Peter Haumerphases, iterations, activities, and so on. Hence, you are not forced to define your entire lifecycle up front.Instead, you can configure your process iteratively, as needed.3.2 Tailor an existing processIn addition to simply configuring a process, you can actively modify processes to make them conformeven better to your specific needs by using one or more of the EPF Composer editors. You can createwhat we call a process contribution for an existing process that defines differential changes to that proc-ess. You can also directly add, remove, or replace elements in the process. Hence, in contrast to chang-ing the configuration -- which would make global changes on the process -- you can define individualchanges just in the places you require them. EPF Composer provides sophisticated dynamic linking ca-pabilities that separate your changes from the original process definition, so that when the underlyingprocess changes you can simply upgrade without loosing your changes. (In Part Two, I will provide de-tailed examples for process tailoring.)3.3 Create a new processAs an alternative to tailoring an existing process, you can also author a completely new process that re-uses activities from one or more existing processes. In cases where you cannot find any reusable materialat all, you can create a completely new process from scratch as well. In most cases, however, you willstart developing your own process by assembling reusable building blocks from method content as well aspredefined process patterns that we call capability patterns. A capability pattern is a mini process defin-ing reusable clusters of activities in a common process area that are performed typically over and overagain. Examples of capability patterns include "manage use case model” “develop a component,” “vali-date build,” or "ongoing management and support." In addition to replicating such patterns each time thework described by the pattern will be performed, EPF Composer allows you to dynamically link patternsinto your process. When the pattern changes, all applications of the pattern will then be automaticallyupdated. 21
  • Eclipse Process Framework Composer: Key Concepts Peter Haumer EPF Composer’s process authoring capabilities let you fully utilize the separation of method contentand process as outlined in Section 2. You can start creating your process by defining your own lifecyclemodel and then systematically populating it with method content and/or capability patterns that you eitherdefine yourself or reuse from the method library. Figure 8 depicts an example demonstrating how method content and capability patterns have been re-used in two processes with different lifecycle models.Figure 8: Two processes with two different lifecycle models applying the same capability patterns andmethod content.In Figure 8, the right hand side contains two breakdown structure process editors. The top one defines asimple variant of the Unified Process, which was the precursor to OpenUP/Basic. The bottom one defines 22
  • Eclipse Process Framework Composer: Key Concepts Peter Haumera Scrum-like process. Each of the two has its own distinct lifecycle model. The top one uses the four UPphases -- Inception, Elaboration, Construction, and Transition -- and defines iterations for them. Scrumprocesses are organized in iterations also referred to as sprints. If you carefully examine the two proc-esses in Figure 8, you see that there are commonalities as well as process-specific differences. Activitiessuch as Manage Iteration or Manage Sprint list different tasks because both processes have a differentmanagement approach. They have been authored specifically for each process. On the other hand, both processes share some activities such as Develop Solution or Validate Build.These activities represent capability patterns that have been defined as building blocks for the upper proc-ess; as you can see, they are listed in the tree browser on the left of Figure 8. These patterns have beenreused by the Scrum process author who applied them to the process by simple drag-and-drop operations.Devoted Scrum practitioners might say that this process violates the principles of Scrum by providingexplicit tasks for doing work instead of assuming self-organizing teams. However, we created this exam-ple to show you how processes like Scrum can easily be enriched with EPF Composer’s process author-ing capabilities by just reusing patterns and tasks that could serve as guidance for learning rather thanstrict work instructions for perhaps less experienced teams.3.4 Develop method content and create or extend processesThe last scenario presented here is the ability to not only create or tailor processes reusing EPF or a third-party method content, but also to develop your own method content and use that either to tailor existingprocesses or use in the creation of new processes. For method content authoring, you again have the choice of defining completely new content, or ex-tending existing method content. You develop new method content if you need to define your own roles,want to add additional work product types, want to add your development methods, or simply want toprovide additional guidance -- such as whitepapers, your organization’s specific regulations and guide-lines, or your own work product templates or checklists. If you simply want to modify existing methodcontent available in the method library by adding a work product responsibility to a role, adding steps to a 23
  • Eclipse Process Framework Composer: Key Concepts Peter Haumertask, or adding a few more check points to an existing checklist, you can do so with EPF Composer’sunique method plug-in and variability capabilities. Variability allows you change existing content with-out directly modifying the original. You have, for example, the ability to create a method plug-in forEPF’s OpenUP/Basic that contains a task contribution adding some new steps to an existing task. Or, youcould define a replacing work product for an OpenUP/Basic work product that defines your own variant.For example, it might have a different name, structure, and templates as well as customized descriptionsand guidance. All references other OpenUP/Basic elements had to the original work product will beautomatically replaced with references to your element. You can then optionally switch on and off yourextensions using method configurations as well as easily upgrade to newer versions of the original ele-ments and reapplying your changes. In EPF Composer, you define and document method content with intuitive form-based editors that areeasy to learn, but powerful enough to provide well-formatted rich text documentation. Figure 9 shows the editor for a work-product definition. To define a new work product type, you justcreate such an element in a method package. To document it you just need to use its editor for filling inform fields and creating relationships using selection dialogs and combo boxes. EPF Composer createsand manages the HTML behind the scenes that provides the well-formatted and hyperlinked documenta-tion that you saw in Figure 4 (showing a preview of page documenting a task). 24
  • Eclipse Process Framework Composer: Key Concepts Peter HaumerFigure 9: Form-based editor for a work product. Every form field can be expanded into a full-sizedrich text editor that allows you to format text, work with tables, include images, and so on. Once you have created your own method content elements, you can include them into your methodconfigurations and add them to your own or reused processes using the “Tailor Existing...” or “CreateNew...” scenarios described above. This concludes our overview of the most common EPF Composer usage scenarios. In Part Two of thisarticle, I will present a more in-depth look at method content and process. 25