Software Process Capability
by
Stephen Lane
—
last modified
Apr 25, 2012 13:38
—
filed under:
KnowledgeModel
Definitions
| Term: Software Process Capability |
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) |
The term software process capability describes the range of expected results which are achievable from the implementation of a software process. It is important to understand capability is not the same as performance. Software process performance is the actual results achieved from following a software process. This is in contrast to the results which are anticipated by implementing such an approach [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/
