Software Process
by
Stephen Lane
—
last modified
Apr 25, 2012 13:37
—
filed under:
KnowledgeModel
Definitions
| Term: Software Process |
Domain: Cross-cutting issues | ||||
|---|---|---|---|---|---|
| Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
| D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
A software process is defined as a set of activities
that begin with the identification of a requirement and results in the development
and maintenance of a software product that satisfies that need.
In practice it is a set of activities, methods, practices, and
transformations that people undertake to develop and maintain software
and its associated artefacts [SEI]. |
||||
Competencies
- Lero@UL: http://www.lero.ie/;Stephen Lane,
Ita Richardson; Sarah Beecham; Marty Sanders
- Tilburg: Software Processes; http://www.tilburguniversity.nl/eriss/research/;
Oktay Turetken
References
- [SEI] The Software Engineering Institute: http://www.sei.cmu.edu/cmmi/
