2010 Fifth International Multi-Conference on Computing in the Global Information Technology 2010
DOI: 10.1109/iccgi.2010.16
|View full text |Cite
|
Sign up to set email alerts
|

Mapping Knowledge into Software Process

Abstract: 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 softw… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2017
2017
2017
2017

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 11 publications
(7 reference statements)
0
1
0
Order By: Relevance
“…Thus this section reviews the utilization of knowledge mapping by previous researchers in risk management and mitigation processes. Kerzazi and Robillard (2010) developed a new approach to software process modelling, which enables the mapping of knowledge required by the activity roles and stored into the activity input artifacts. In their approach the information is fed into a dashboard, which outlines any knowledge discrepancies within the software process model and enables process manager to manage risks associated to knowledge within a given task.…”
Section: Software Risk Mitigation and Knowledge Mappingmentioning
confidence: 99%
“…Thus this section reviews the utilization of knowledge mapping by previous researchers in risk management and mitigation processes. Kerzazi and Robillard (2010) developed a new approach to software process modelling, which enables the mapping of knowledge required by the activity roles and stored into the activity input artifacts. In their approach the information is fed into a dashboard, which outlines any knowledge discrepancies within the software process model and enables process manager to manage risks associated to knowledge within a given task.…”
Section: Software Risk Mitigation and Knowledge Mappingmentioning
confidence: 99%