Eclipse process framework: Difference between revisions

Content deleted Content added
BG19bot (talk | contribs)
m top: Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at Wikipedia talk:WikiProject Accessibility#LISTGAP
Rescuing 1 sources and tagging 0 as dead. #IABot (v1.5.2)
Line 4:
*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]], an [[agile software development]] process optimized for small projects.
 
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] {{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, sales cycles, and so on.
 
== See also ==