Difference between revisions of "Software development process"
Karl Jones (Talk | contribs) (→See also) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 22: | Line 22: | ||
* [[Getting started with programming]] | * [[Getting started with programming]] | ||
* [[Software defect]] | * [[Software defect]] | ||
| + | * [[Software development]] | ||
* [[Software requirements]] | * [[Software requirements]] | ||
* [[Software testing]] | * [[Software testing]] | ||
Revision as of 09:00, 28 August 2015
In software engineering, a software development methodology (also known as a system development methodology, software development life cycle, software development process, software process, etc.) is a division of software development work into distinct phases (or stages) containing activities with the intent of better planning and management.
It is often considered a subset of the systems development life cycle.
The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.
Common methodologies include:
- Waterfall
- Agile
- Prototyping
- Iterative and incremental development
- Spiral development
- Rapid application development
- Extreme programming
Some people consider a life-cycle "model" a more general term for a category of methodologies and a software development "process" a more specific term to refer to a specific process chosen by a specific organization. For example, there are many specific software development processes that fit the spiral life-cycle model.
See also
- Computer program
- Getting started with programming
- Software defect
- Software development
- Software requirements
- Software testing
External links
- Software development process @ Wikipedia
