Paper Info
Title
Descriptive Software Process Modeling--How to Deal with Sensitive Process Information
Abstract
Descriptive software process models are important assets in software process improvement. The accuracy of the model, i.e., the degree to which it reflects the process as it is actually performed, is a key to the success of process improvement programs. To develop such a process model, a Process Engineer collects available process information, which is subsequently summarized in a process model. The information needed to develop an accurate description of the process is often sensitive, regarding, for instance, work practices that are not followed as described in the official process documentation. Revealing this sensitive information to other people within the software organization can be harmful for the information providers. Therefore, dealing with this type of information imposes ethical responsibilities to the Process Engineer and can put Process Engineers into an awkward situation. This paper lists experience from descriptive process modeling cases in industry where sensitive information was provided and provides guidelines on how to deal with such information.
Year
DOI
Venue
2001
https://doi.org/10.1023/A:1011986902298
Empirical Software Engineering
Keywords
Field
DocType
Descriptive software process modeling,process knowledge elicitation,process improvement,ethics
Software Engineering Process Group,Business process management,Personal software process,Systems engineering,Computer science,Empirical process (process control model),Business process modeling,Team software process,Goal-Driven Software Development Process,Process management,Process mining
Journal
Volume
Issue
ISSN
6
4
1382-3256
Citations 
PageRank 
References 
1
0.86
4
Authors
1
Name
Order
Citations
PageRank
Ulrike Becker-Kornstaedt113215.36