Skip to main content

Eclipse Process Framework

Eclipse Process Framework (EPF) is an Eclipse Foundation project that provides tooling and metamodels for defining, publishing, and managing software and systems development processes based on the Eclipse Process Framework Composer and the underlying SPEM 2.0 specification (software process engineering).

  • Process authoring and management environment for software and systems development (process engineering).
  • Support for SPEM 2.0-based method content and process definition, including roles, tasks, work products, and guidance (software process modeling).
  • Tooling to configure, extend, and publish method libraries and custom development processes as web-ready process documentation (documentation generation).
  • Reference method libraries, including variants based on the Rational Unified Process (iterative development methodology).
  • Extensible framework for organizations to define and maintain their own process assets and practice libraries (process governance and reuse).

More About Eclipse Process Framework

Eclipse Process Framework (EPF) is a project under the Eclipse Foundation that focuses on tooling and method content for defining, configuring, and publishing software and systems development processes (process engineering). It targets organizations that want to formalize, document, and manage their development practices in a structured and repeatable way, while remaining able to tailor methods to specific projects, domains, or regulatory environments.

The central capability of EPF is the Eclipse Process Framework Composer, a process authoring tool that lets practitioners create and maintain method libraries (software process modeling). Within these libraries, users can define core elements such as roles, tasks, work products, and guidance artifacts, and group them into reusable practices, capability patterns, and delivery processes. EPF is based on the OMG Software & Systems Process Engineering Metamodel 2.0 (SPEM 2.0), which provides a standardized way of modeling processes and method content.

EPF also supplies reference method content, including libraries derived from or inspired by the Rational Unified Process (iterative development methodology). These libraries demonstrate how to structure iterative, use-case driven, and architecture-centric processes within the EPF environment. Organizations can adopt, tailor, or extend this reference content to align with internal standards, frameworks, or compliance requirements, or they can replace it with fully custom method libraries built from the ground up.

A key operational feature of EPF is its ability to publish process definitions into static web sites that present navigable process documentation (documentation generation). This allows enterprises to distribute a web-based process portal to development teams, with role-specific pages, task descriptions, templates, and guidelines. The published sites are suitable for integration with intranets or other documentation repositories and can be versioned and maintained as process baselines.

From an enterprise usage perspective, EPF is applied as a process governance and knowledge management tool (process governance and reuse). Process engineers and method specialists maintain central libraries in EPF Composer, while project teams consume the published guidance. The framework’s configuration and variability mechanisms enable organizations to maintain a core process while providing variants for particular technologies, business domains, or project sizes. Its grounding in SPEM 2.0 supports alignment with other tools or repositories that reference the same metamodel.

Within a technical taxonomy, Eclipse Process Framework fits into software process engineering tooling, method authoring environments, and process documentation generation platforms. It is relevant where organizations need a structured, model-based way to capture development practices, enforce consistent terminology, and provide a navigable process portal without building custom tooling.