A Comprehensive Code-Based Quality Model for Embedded Systems: Systematic Development and Validation by Industrial Projects

Mayr, Alois; Plösch, Reinhold; Kläs, Michael; Lampasona, Constanza; Saft, Matthias

doi:10.1109/issre.2012.4

Cited by 15 publications

(14 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Authors of this paper were part of the Quamoco development team and already developed Quamoco-based quality models for embedded systems [28], safety critical systems [29] and for software documentation quality [30]. Quamoco-based quality models rely on the basic idea of using product factors for expressing a quality property of an entity.…”

Section: Aspect and Factor Hierarchymentioning

confidence: 99%

Measuring, Assessing and Improving Software Quality based on Object-Oriented Design Principles

Plösch

Bräuer

Körner

et al. 2016

Open Computer Science

Self Cite

View full text Add to dashboard Cite

Good object-oriented design is crucial for a successful software product. Metric-based approaches and the identification of design smells are established concepts for identifying design flaws and deriving design improvements thereof. Nevertheless, metrics are difficult to use for improvements as they provide only weak guidance and are difficult to interpret. Thus, this paper proposes a novel design quality model (DQM) based on fundamental object-oriented design principles and best practices. In course of discussing DQM, the paper provides a contribution in three directions: (1) it shows how to measure design principles automatically, (2) then the measuring result is used to assess the degree of fulfilling object-oriented design principles, (3) and finally design improvements of identified design flaws in object-oriented software are derived. Additionally, the paper provides an overview of the research area by explaining terms used to describe designrelated aspects and by depicting the result of a survey on the importance of object-oriented design principles. The underlying concepts of the DQM are explained before it is applied on two open-source projects in the format of a case study. The qualitative discussion of its application shows the advantages of the automated design assessment that can be used for guiding design improvements.

show abstract

Section: Aspect and Factor Hierarchymentioning

confidence: 99%

Measuring, Assessing and Improving Software Quality based on Object-Oriented Design Principles

Plösch

Bräuer

Körner

et al. 2016

Open Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…An overview exemplified by an excerpt of the domain-specific model for embedded systems (Mayr et al 2012) can be seen in Fig. 6.9.…”

Section: The Quamoco Quality Metamodelmentioning

confidence: 99%

Model-Based Quality Management of Software Development Projects

Heidrich

Rombach

Kläs

2014

Software Project Management in a Changing World

View full text Add to dashboard Cite

Managing the quality of artifacts created during the development process is an integral part of software project management. Software quality models capture the knowledge and experience regarding the quality characteristics of interest, the measurement data that can help to reason about them, and the mechanisms to use for characterizing and assessing software quality. They are the foundation for managing software quality in projects in an evidence-based manner. Nowadays, coming up with suitable quality models for an organization is still a challenging endeavor. This chapter deals with the definition and usage of software quality models for managing software development projects and discusses different challenges and solutions in this area. The challenges are: (1) There is no universal model that can be applied in every environment because quality is heavily dependent on the application context. In practice and research, a variety of different quality models exists. Finding the "right" model requires a clear picture of the goals that should be obtained from using the model. (2) Quality models need to be tailored to company specifics and supported by corresponding tools. Existing standards (such as the ISO/IEC 25000 series) are often too generic and hard to fully implement in an organization. (3) Practitioners require a comprehensive set of techniques, methods, and tools for systematically specifying, adapting, and applying quality models in practice. (4) In order to create sustainable quality models, their contribution to the organizational goals must be clarified, and the models need to be integrated into the development and decision-making processes.

show abstract

“…In contrast, our preliminary work on the ESQM embedded systems software quality model [17] is focused on the quality of source code of embedded systems software. It covers a number of quality requirements for source code that were elicited from various (safety) standards and guidelines, such as IEC 61508, EN 50128, or the MISRA-C and C++ coding guidelines.…”

Section: Quality Model Based Approachesmentioning

confidence: 99%

“…Product factors are intended to express measurable properties of the product or its parts, for instance the reference validity prior to pointer access statements within source code (i.e., Reference validity @Pointer Access Statement) [17]. Basically, these factors are similar to what Dromey [28] calls quality carrying properties of product components.…”

Section: A Quality Meta Modelmentioning

confidence: 99%

See 1 more Smart Citation

Objective Measurement of Safety in the Context of IEC 61508-3

Mayr

Plösch

Saft

2013

2013 39th Euromicro Conference on Software Engineering and Advanced Applications

Self Cite

View full text Add to dashboard Cite

Safety standards like the IEC 61508 are an important source for developing safety-critical (software) systems as they provide a set of requirements and recommendations to assist engineers in system and software development. Applying this standard in practice leads to interpretation problems due to insufficient operationalization, i.e. unclear requirements and unclear or missing acceptance criteria. This makes it hard to measure the extent to which a product fulfills the requirements of the standard.For this, we systematically developed a quality model that covers the coding-related parts of the safety standard IEC 61508. It provides refinements to the recommendations and equips them with proper measurement support by means of static code analysis tools (236 measures for C/C++ systems).We found in an evaluation study that the used approach is suitable for covering the coding-related parts of the standard with proper and meaningful operationalization. Additionally, the results indicate an adequate completeness of the modeled contents. This encourages us to go a step further and to extend the model to support compliance assessments in future work.

show abstract

A Comprehensive Code-Based Quality Model for Embedded Systems: Systematic Development and Validation by Industrial Projects

Cited by 15 publications

References 18 publications

Measuring, Assessing and Improving Software Quality based on Object-Oriented Design Principles

Measuring, Assessing and Improving Software Quality based on Object-Oriented Design Principles

Model-Based Quality Management of Software Development Projects

Objective Measurement of Safety in the Context of IEC 61508-3

Contact Info

Product

Resources

About