Keynote

Titel:
From informal process sketches to enactable process:
How to represent your development process with SPEM 2.0,
Rational Method Composer, and Team Concert

Datum und Uhrzeit:
29. April 2008 von 14:30 bis 15:15 Uhr

Beschreibung:
The term “Development Process” means many different things to many different people depending on their development culture and historical background, development domain, compliance requirements and many, many other factors. For some people the development process is represented as a well-defined workflow and breakdown of activities that needs to be performed by development teams throughout a well-defined lifecycle defining when to deliver what result. For others, it just a body of knowledge represented as a team’s collection of useful textual reference material such as guidelines, white papers, reference examples, and artifact templates managed on a Wiki. For other teams it would be a declaration (perhaps even a manifesto) of values and principles that guides them in the right selection of specific development practices and lifecycles, which again could be represented in any of the forms listed here. For some it is important that the process defines a lifecycle of iterative achievements in the form of milestones represented as specific artifacts and deliverables. For others, process is just a set of rules that are used to govern the development work, which need to be fulfilled at all times or at specific points in the lifecycle or which are dependent on the state of the work products (e.g. do not allow any source code files without a copyright statement in late development phases; or do not allow significant architectural changes without going through a specific approval process once the architecture is in the state baselined).

The OMG Software and Systems Process Engineering Metamodel (SPEM 2.0) provides sets of concepts, notations, and an extensibility framework that aims at allowing development teams to represent their processes in any of these ways and many more. This presentation introduces the SPEM 2.0 specification as well as its implementations. We will introduce the basic concepts of SPEM 2.0 in the form of examples and case studies of using SPEM to represent many different development methods and processes used in the industry such as Eclipse Way, EssUP, ITUP, MSF Agile, OpenUP, Rational Unified Process, Scrum. We will show how SPEM 2.0 concepts and notations can be used in different ways ranging from informal whiteboard drawings and ‘napkin sketches’ over using the SPEM 2.0 UML 2 Profile in a UML model tool to using the formal XMI and CMOF schemas for dedicated CASE tool support. As an example for such a dedicated authoring tool we will then introduce and demonstrate the IBM Rational Method Composer (RMC 7.2), which represents an implementation of a large set of SPEM 2.0 concepts. We review the capabilities of this environment as well as look at examples for different methods and processes. Finally we show in an end-to-end tool scenario how organizations and teams can instantiate, enact, and measure their RMC processes directly in the developer’s IDE utilizing the IBM Rational Team Concert and Rational Jazz team collaboration platform.

Referent:

Dr. Peter Haumer is a solution architect for the IBM Rational Method Composer product platform and a committer in the Eclipse Process Framework project. He is responsible for defining next-generation process engineering tools, and he represents IBM at the OMG in the SPEM 2.0 initiative serving as the lead of the finalization task force. Before joining Rational's Commercial Methods team, he worked as a senior professional services consultant for the IBM Rational brand. He performed on-site consulting and training, and he assisted and coached customers to be successful with the RUP and other Rational tools. Peter received his doctorate in computer science from the Technical University Aachen, Germany.