Eclipse process framework: Difference between revisions

Content deleted Content added
Common nouns are not capitalised in English
m Removing link(s) Wikipedia:Articles for deletion/OpenUP closed as soft delete (XFDcloser)
 
(One intermediate revision by one other user not shown)
Line 3:
 
*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]], an [[agile software development]] process optimized for small projects.
 
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.