The PET framework provides support for the enactment of development processes for several project-supporting tools, e.g. TFS or Sharepoint.
Interpretation of input process models as well as the generation of templates for the target tools is encapsulated in plugins.
If you are new to PET, please read the following section, which explains its general concepts, as well as the dedicated
of this project.
A list of improvements over CollabXT regarding Team Foundation Server template generation is provided here:
Users, already familiar with the project might be interested in following pages:
Overview over the Process Enactment Tool Framework
The Process Enactment Tool Framework uses an intermediate architecture for process models. It consists of three parts:
- Process provider
- Tool provider
- Process-Tool interchange model
The interchange model
defines the data structures used by the generator system. During its processing PET uses
to read process models and tool providers
for result generation.
A process provider abstracts the concrete process. Its job is to filter and map the process' data into the interchange format. Tool providers contain the processing's intelligence, so to say. They are responsible for collecting all data, transforming them and
for providing the coupling to the particular tools.
All providers are realized as plug-ins. The generator tools load them automatically, e.g. for processes:
Having selected an available process, the next step is to select the target tool for the enactment:
Currently the platform supports following processes:
and following tools:
- Microsoft Sharepoint -->
- Microsoft Team Foundation Server -->
- Microsoft Office Word 2007/2008 -->
The following is an overview over further material regarding the Process Enactment Tool Framework.
How to build PET
Building the PET assemblies yourself is quite easy. Core, wizard, the V-Modell XT as well as the TFS provider should build right away : )
If you want to build the SharePoint and the DocX tool providers, please read the following notes. Do not need them? Simply disable the according projects within the Visual Studio solution.
- SharePoint provider: Before you can compile the provider assembly it is necessary to build the separate solution
Tum.CollabXT.SharePoint.Site which contains CollabXTStrings.dll and
CollabXTWebParts.dll. Furthermore these projects reference Microsoft.SharePoint.dll. You can most easily obtain it from a server running Windows SharePoint services (WSS).
- DocX provider: To build this assembly you need to get the DocumentFormat.OpenXML.dll from Microsoft (it is part of the Open XML SDK 2.0; there is no need to install the whole SDK, just extract the needed file from the installer via
msiexex). Put this library under Tum.CollabXT.DocxGen\Resources.
This project is an advancement over the previously published projects
and CollabXT TFS
. Both projects are now outdated and replaced by the integrated Process Enactment Tool Framework.
Quite a lot of research publications have been published around this project. A selection of relevant, English publications is: