Industrial strength software and quality: software and engineering at Siemens

Achatz, Reinhold; Paulisch, Frances

doi:10.1109/qsic.2003.1319117

Cited by 7 publications

(17 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Cost-Benefit Analysis [132], [151], [171], [227] Not stated [121], [123], [126], [131], [136], [137], [157], [159], [166], [167], [177], [184], [193], [194], [198], [205], [206], [208], [220], [249], [250] 21 of whether the assessed results are in causal relationship with the SPI initiative, is rarely discussed (see Section 3.4.7 for a more detailed discussion).…”

Section: Analysis and Discussionmentioning

confidence: 99%

“…Examples are: staff morale, employee satisfaction, quality awareness [121], [126], [133], [136], [137], [140], [149], [157], [177], [184], [186], [193], [202], [205], [209], [226], [227], [235], [238], [239], [248], [257], [263] 24…”

Section: Analysis and Discussionmentioning

confidence: 99%

“…Cost [121], [149], [157], [160], [161], [167], [170], [177], [178], [183], [185], [186], [189], [194], [204], [211], [226], [238] 18/0.32 Effort [119], [120], [136], [139]- [141], [143], [144], [152], [159], [176], [183], [206], [222], [229], [265], [266] 17/0.30…”

Section: Analysis and Discussionmentioning

confidence: 99%

“…There is little agreement on what should be measured, and the absence of a systematic and reliable measurement approach is regarded as a factor that contributes to the high failure rate of improvement initiatives [186]. Regardless of these problems in evaluating SPI initiatives, a plethora of evidence exists to show that improvement efforts provide the expected benefits [46], [71], [121], [137], [161], [184], [213], [224], [240], [248].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

BACKGROUND-Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE-This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD-The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS-Seven distinct evaluation strategies were identified, whereas the most common one, "Pre-Post Comparison", was applied in 49% of the inspected papers. Quality was the most measured attribute (62%), followed by Cost (41%) and Schedule (18%). Looking at measurement perspectives, "Project" represents the majority with 66%. CONCLUSION-The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that "Pre-Post Comparison" was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.

show abstract

Section: Analysis and Discussionmentioning

confidence: 99%

Section: Analysis and Discussionmentioning

confidence: 99%

Section: Analysis and Discussionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

show abstract

“…Consequently, also the ratio of software development in the costs of machinery has doubled over the last decade, reaching a level of 40% [33]. Today, we observe that major companies recognize software as a key enabler for their business [1], and in several industrial automation companies there are already more software engineers than personnel in the traditional mechanical or electronic engineering departments.…”

Section: Introductionmentioning

confidence: 99%

Automated testing of industrial automation software: practical receipts and lessons learned

Ramler

Putschogl

Winkler

2014

Proceedings of the 1st International Workshop on Modern Software Engineering Methods for Industrial Automation

View full text Add to dashboard Cite

The share of software in industrial automation systems is steadily increasing. Thus, software quality issues become a critical concern for many automation projects, which require effective software quality assurance measures. In this paper we describe an architecture for automated testing of software applications part of industrial automation systems. We focus on testing programmable logic controller (PLC) software for machineries, which can be achieved by using test automation frameworks derived from software development. The paper provides a collection of practical receipts describing how different approaches from software engineering best-practices can be applied in the context of industrial automation systems. A combination of these receipts has been used for automating software tests in an industrial automation project. In this project, more than 200 tests have been developed to assure the quality of critical PLC components. The tests are an integral part of the project's automated build and continuous integration system. Every software change triggers an automated build and test process to ensure that no defects or unintended side effects have been introduced. The feedback from the project confirmed the applicability and usefulness of the outlined testing approach in context of industry automation. The paper concludes with providing recommendations and sharing additional lessons we have learned from automated testing of PLC software.

show abstract

A conceptual framework for SPI evaluation

Unterkalmsteiner

Gorschek

Islam

et al. 2013

J Software Evolu Process

View full text Add to dashboard Cite

SUMMARYSoftware Process Improvement (SPI) encompasses the analysis and modification of the processes within software development, aimed at improving key areas that contribute to the organizations' goals. The task of evaluating whether the selected improvement path meets these goals is challenging. Based on the results of a systematic literature review on SPI measurement and evaluation practices, we developed a framework (SPI-MEF) that supports the planning and implementation of SPI evaluations. SPI-MEF guides the practitioner in scoping the evaluation, determining measures and performing the assessment. SPI-MEF does not assume a specific approach to process improvement and can be integrated in existing measurement programs, refocusing the assessment on evaluating the improvement initiative's outcome. Sixteen industry and academic experts evaluated the framework's usability and capability to support practitioners, providing additional insights that were integrated in the application guidelines of the framework.

show abstract

Industrial strength software and quality: software and engineering at Siemens

Cited by 7 publications

References 3 publications

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Automated testing of industrial automation software: practical receipts and lessons learned

A conceptual framework for SPI evaluation

Contact Info

Product

Resources

About