Eclipse process framework: Difference between revisions

Revision as of 03:41, 19 November 2018

Revision as of 04:19, 13 September 2019

Line 1:

{{RefimproveMore citations needed|date=October 2008}}

The '''Eclipse Process Framework''' (EPF) is an [[Open-source software|open source]] project that is managed by the [[Eclipse Foundation]]. It lies under the top-level [[Eclipse Technology Project]]. It has two goals:

Line 7:

By using EPF Composer, engineers can create your own [[Software development process]] by structuring it using a predefined schema. This schema is an evolution of the SPEM<ref>[http://www.omg.org/technology/documents/formal/spem.htm SPEM] {{webarchive|url=https://web.archive.org/web/20071030033843/http://www.omg.org/technology/documents/formal/spem.htm |date=2007-10-30 }}</ref> 1.1 [[Object Management Group|OMG]] specification referred to as the Unified Method Architecture (UMA). Major parts of UMA went into the adopted revision of SPEM, SPEM 2.0. EPF is aiming to fully support SPEM 2.0 in the near future. The UMA and SPEM schemata support the organization of large amounts of descriptions for development methods and processes. Such method content and processes do not have to be limited to software engineering, but can also cover other design and engineering disciplines, such as mechanical engineering, business transformation, and sales cycles.

IBM supplies a commercial version, [[IBM Rational Method Composer]].{{factcitation needed|date=May 2018}}

== Limitations ==

The "Content Variability" capability severely limits users to one-to-one mappings. Processes trying to integrate various aspects may require block-copy-paste style clones to get around this limitation. This may be a limitation of the SPEM model and might be based on presumption that agile methods are being described as these methods tend not to have deep dependencies.{{factcitation needed|date=May 2018}}

== See also ==

{{Portal|JavaComputer (programming language)}}

* [[Meta-Process Modeling]]