Content deleted Content added
No edit summary |
m Removing link(s) Wikipedia:Articles for deletion/OpenUP closed as soft delete (XFDcloser) |
||
(66 intermediate revisions by 34 users not shown) | |||
Line 1:
{{More 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]], and has two goals:
*
*
By using EPF Composer, engineers can create their 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.
▲* To provide exemplary and extensible process content for a range of software development and management processes supporting iterative, agile, and incremental development, and applicable to a broad set of development platforms and applications. As an example, EPF provides the [[Open Unified Process]] (OpenUP) which is an agile software development process optimized for small projects.
IBM supplies a commercial version, [[IBM Rational Method Composer]].{{citation needed|date=May 2018}}
To learn more about EPF, visit the [http://www.eclipse.org/epf/ Eclipse Process Framework Web site].▼
== 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}}
* [[Meta-process modeling]]
==References==
{{Reflist}}
==External links==
▲
[[Category:Open content]]
[[Category:Eclipse (software)]]
[[Category:Software development process]]
|