
Software process model rarely takes into account knowledge required to build software. This paper presents a new approach to software process modeling, which enables the mapping of knowledge required by the activity roles and stored into the activity input artifacts. Comparing knowledge concepts required for the various activities provides information on the knowledge gaps between the models elements involved. This information is fed into a dashboard, which outlines any knowledge discrepancies within the software process model and enables process manager to mitigate risks associated to knowledge within a given task.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
