Rule-Based Detection of Process Conformance Violations in Application Lifecycle Management
Software engineering processes are the basis for the development of quality software products within time and within budget. In this paper we present an approach to detect process conformance violations that reveal deviations between planned and executed software engineering processes. The approach is based on process rules that complement the process documentation. A framework for defining, executing and evaluating these rules has been implemented as extension to an Application Lifecycle Management (ALM) solution. The framework has been applied in context of introducing new processes and practices in an industrial environment. Over the timespan of more than a year, process conformance has been continuously evaluated as part of the nightly build. We were able to demonstrate that the results can be used to identify hot spots in process conformance calling for immediate action, to reveal long-term issues that motivate process improvement measures and, furthermore, that the continuous feedback provided by the approach has a positive impact on process quality. Finally, the paper documents useful lessons we have learned during the application of our approach in a real-world setting.
KeywordsProcess Conformance Process Quality Application Lifecycle Management
Unable to display preview. Download preview PDF.
- 1.van der Aalst, W.: Process Mining: Discovery, Conformance and Enhancement of Business Processes. Springer (2011)Google Scholar
- 2.Huo, M., Zhang, H., Jeffery, R.: An Exploratory Study of Process Enactment as Input to Software Process Improvement. In: 4th International Workshop on Software Quality, WoSQ. ACM (2006)Google Scholar
- 4.Zazworka, N., Basili, V.R., Shull, F.: Tool Supported Detection and Judgment of Nonconformance in Process Execution. In: 3rd International Symposium on Empirical Software Engineering and Measurement, ESEM. ACM (2009)Google Scholar
- 5.Zazworka, N., Stapel, K., Knauss, E., Shull, F., Basili, V.R., Schneider, K.: Are Developers Complying with the Process: An XP Study. In: 4th International Symposium on Empirical Software Engineering and Measurement, ESEM. ACM (2010)Google Scholar
- 6.Kääriäinen, J., Välimäki, A.: Applying Application Lifecycle Management for the Development of Complex Systems: Experiences from the Automation Industry. In: O’Connor, R.V., Baddoo, N., Cuadrago Gallego, J., Rejas Muslera, R., Smolander, K., Messnarz, R. (eds.) EuroSPI 2009. CCIS, vol. 42, pp. 149–160. Springer, Heidelberg (2009)CrossRefGoogle Scholar
- 7.Schwaber, C.: The Changing Face Of Application Life-Cycle Management. Technical Report, Forrester Research Inc. (2006)Google Scholar
- 8.Saaksvuori, A., Immonen, A.: Product Lifecycle Management, 3rd edn. Springer (2008)Google Scholar
- 9.Pirklbauer, G., Zeilinger, R., Ramler, R.: An Integration-Oriented Model for Application Lifecycle Management. In: Filipe, J., Cordeiro, J. (eds.) 11th International Conference on Enterprise Information Systems. LNBIP, vol. 24, pp. 399–403. Springer, Heidelberg (2009)Google Scholar
- 10.Gousset, M., Krishnamoorthy, A., Keller, B., Timm, S.: Professional Application Lifecycle Management with Visual Studio 2010: with Team Foundation Server 2010. Wiley (2010)Google Scholar
- 11.Krishna, S., Fenstermaker, T.: IBM Rational Team Concert 2 Essentials. Packt Publishing (2011)Google Scholar
- 12.Lacheiner, H., Ramler, R.: Application Lifecycle Management as Infrastructure for Software Process Improvement and Evolution: Experience and Insights from Industry. In: 37th EUROMICRO Conference on Software Engineering and Advanced Applications, Euromicro SEAA. IEEE (2011)Google Scholar
- 13.Clark, M.: Pragmatic Project Automation: How to Build, Deploy, and Monitor Java Apps. The Pragmatic Programmers (2004)Google Scholar