Eclipse process framework: Difference between revisions

Revision as of 01:31, 22 March 2010

Latest revision as of 17:45, 5 July 2024

(25 intermediate revisions by 19 users not shown)

Line 1:

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

The '''Eclipse Processprocess Frameworkframework''' (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]]., Itand has two goals:

*To provide an extensible framework and exemplary tools for software process engineering - method and process authoring, library management, configuring and publishing a process.

*To provide exemplary and extensible process content for a range of software development and management processes supporting iterative, agile, and [[Iterative and incremental development|incremental development]], and applicable to a broad set of development platforms and applications. For instance, EPF provides the [[OpenUP/Basic]], an [[agile software development]] process optimized for small projects.

By using EPF Composer, youengineers can create yourtheir own [[Softwaresoftware development process]] by structuring it in one specific way 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 Unifiedunified Methodmethod Architecturearchitecture (UMA). Major parts of UMA went into the recently adopted revision of SPEM, SPEM 2.0140. EPF is aiming to fully support the final 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, and so on.

*To provide exemplary and extensible process content for a range of software development and management processes supporting iterative, agile, and [[Iterative and incremental development|incremental development]], and applicable to a broad set of development platforms and applications. For instance, EPF provides the [[OpenUP/Basic]], an agile software development process optimized for small projects.

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

By using EPF Composer you can create your own [[Software development process]] by structuring it in one specific way using a predefined schema. This schema is an evolution of the SPEM<ref>[http://www.omg.org/technology/documents/formal/spem.htm SPEM]</ref> 1.1 [[Object Management Group|OMG]] specification referred to as the Unified Method Architecture (UMA). Major parts of UMA went into the recently adopted revision of SPEM, SPEM 2.014. EPF is aiming to fully support the final 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, sales cycles, and so on.

== Limitations ==

The "content variability" [[Capability (systems engineering)|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.{{citation needed|date=May 2018}}

== See also ==

{{Portal|Computer programming}}

* [[IBM Rational Method Composer]] a commercial version supplied by IBM

* [[Meta-Processprocess Modelingmodeling]]

* [[OpenUP]]

* [[OpenUP/Basic]]

== References ==

{{reflistReflist}}

{{Refimprove|date=October 2008}}

== Limitations ==

The "Content Variability" capability severly 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.

==External links==

Line 25 ⟶ 23:

[[Category:Open content]]

[[Category:Eclipse (software)]]

[[Category:Software development process]]

[[pl:Eclipse Process Framework]]