scholarly journals Design Principles for Integration of Model-Driven Quality Assurance Tools

2011 ◽  
Author(s):  
Othon Crelier ◽  
Roberto S. Silva Filho ◽  
William M. Hasling ◽  
Christof J. Budnik
Keyword(s):  
Quality Assurance ◽  
Design Principles ◽  
Model Driven

scholarly journals Measuring Models

2009 ◽  
pp. 147-169 ◽  
Author(s):  
Martin Monperrus ◽  
Jean-Marc Jézéquel ◽  
Joël Champeau ◽  
Brigitte Hoeltzener
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Point Of View ◽  
Specific Information ◽  
Model Driven Engineering ◽  
Text Documents ◽  
Model Driven ◽  
Domain Specific ◽  
Wide Range

Model-Driven Engineering (MDE) is an approach to software development that uses models as primary artifacts, from which code, documentation and tests are derived. One way of assessing quality assurance in a given domain is to define domain metrics. We show that some of these metrics are supported by models. As text documents, models can be considered from a syntactic point of view i.e., thought of as graphs. We can readily apply graph-based metrics to them, such as the number of nodes, the number of edges or the fan-in/fan-out distributions. However, these metrics cannot leverage the semantic structuring enforced by each specific metamodel to give domain specific information. Contrary to graph-based metrics, more specific metrics do exist for given domains (such as LOC for programs), but they lack genericity. Our contribution is to propose one metric, called s, that is generic over metamodels and allows the easy specification of an open-ended wide range of model metrics.

Applying Software Engineering Design Principles to Agile Architecture

2022 ◽  
pp. 330-355
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Software Engineering ◽  
Development Process ◽  
Design Principles ◽  
Design Concept ◽  
Agile Development ◽  
Model Driven ◽  
It Architecture ◽  
It Systems ◽  
Architectural Patterns ◽  
Java Programs

Most enterprise IT systems are very complex with a combination of COBOL and Java programs running on multiple platforms. What is needed is a solid IT architecture that supports the operation and growth of a cross-platform IT system. It must enable the iterative and incremental development of applications that are foreseen in an agile development process. The design concept of such an architecture with its infrastructure and development tool is presented in this chapter. This design concept is based on the design principles and architectural patterns of software engineering. The architecture is a combination of layered, component-based, and service-oriented architectural patterns. The agile development process is based on a model-driven approach. The architecture and development approaches were first introduced in 2004. Since then, many applications have been developed on time and within budget.

scholarly journals Model-driven Process Planning and Quality Assurance

Procedia CIRP ◽  
2015 ◽  
Vol 33 ◽  
pp. 209-214 ◽  
Author(s):  
Magnus Lundgren ◽  
Mikael Hedlind ◽  
Torsten Kjellberg
Keyword(s):  
Quality Assurance ◽  
Process Planning ◽  
Model Driven

Transitioning from Code-Centric to Model-Driven Industrial Projects

2009 ◽  
pp. 236-262 ◽  
Author(s):  
Miroslaw Staron
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Software Quality ◽  
Software Quality Assurance ◽  
Field Development ◽  
Model Driven ◽  
Domain Specific ◽  
Model Driven Software Development ◽  
Industrial Projects ◽  
New Challenges

Introducing Model Driven Software Development (MDSD) into industrial projects is rarely done as a “green field” development. The usual path is to make a transition from code-centric (CC) development in existing projects into MDSD in a step-wise manner. Similarly to all other software development activities; software quality assurance needs to be adjusted to meet the new challenges arising when using models instead of the code for the mainstream development. In this chapter we present a set of empirical data on the issues related to transitioning from CC to MDSD projects in industry. First; we present results from a set of experiments evaluating how a domain specific notation affects the effectiveness and efficiency of reading techniques used for inspecting models. Second; we present a comparison of productivity increase when changing to MDSD projects from one of the large Swedish companies. Finally we present a short survey on the prioritization of products; projects; and resource metrics in MDSD projects.

Applying Software Engineering Design Principles to Agile Architecture

2020 ◽  
pp. 82-108
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Software Engineering ◽  
Development Process ◽  
Design Principles ◽  
Design Concept ◽  
Agile Development ◽  
Model Driven ◽  
It Architecture ◽  
It Systems ◽  
Architectural Patterns ◽  
Java Programs

Most enterprise IT systems are very complex with a combination of COBOL and Java programs running on multiple platforms. What is needed is a solid IT architecture that supports the operation and growth of a cross-platform IT system. It must enable the iterative and incremental development of applications that are foreseen in an agile development process. The design concept of such an architecture with its infrastructure and development tool is presented in this chapter. This design concept is based on the design principles and architectural patterns of software engineering. The architecture is a combination of layered, component-based, and service-oriented architectural patterns. The agile development process is based on a model-driven approach. The architecture and development approaches were first introduced in 2004. Since then, many applications have been developed on time and within budget.

Assuring Maintainability in Model-Driven Development of Embedded Systems

2009 ◽  
pp. 352-373
Author(s):  
Stefan Wagner ◽  
Florian Deissenboeck ◽  
Stefan Teuchert ◽  
Jean-François Girard
Keyword(s):  
Quality Assurance ◽  
Commercial Vehicles ◽  
New Paradigm ◽  
Industrial Case Study ◽  
Matlab Simulink ◽  
Model Driven ◽  
Applied Model ◽  
Model Driven Software Development ◽  
Development Methods

In model-driven software development as much as in classical code-driven development maintenance costs make up the bulk of the total life cycle costs of a software system. However, as development methods in MDSD differ from classical methods, assuring the maintainability of systems built with MDSD requires companies to adjust their quality assurance to work with the new paradigm and the novel type of development artefacts. As the automotive industry has already applied model-driven approaches for some time (usually in the form of Matlab/Simulink) it proves to be a fertile ground to advance assurance methods for the maintainability of model-based systems. In this chapter we describe a two-dimensional quality metamodel and present an instance that defines maintainability for MDSD with Matlab/Simulink and TargetLink. We exemplify how such a model serves as the basis of all quality assurance activities and report on experiences made in an industrial case study with one of the leading international providers of commercial vehicles and transport solutions.

Quality in Model Driven Engineering

2009 ◽  
pp. 37-56 ◽  
Author(s):  
Teade Punter ◽  
Jeroen Voeten
Keyword(s):  
Quality Assurance ◽  
Embedded Systems ◽  
Conceptual Framework ◽  
Systems Design ◽  
Design Flow ◽  
Model Driven Engineering ◽  
New Approach ◽  
Model Driven ◽  
The Difference ◽  
Near Future

This chapter argues that embedded systems design faces several challenges of which late integration and the difference in development productivity between disciplines are major ones. Model driven engineering (MDE) looks a promising approach to address these challenges. However, MDE is a new approach which has to be defined and implemented in close interaction by academia and industry the near future. We therefore provide a conceptual framework to understand the possibilities and the flaws in quality assurance in the MDE design flow.

Sign in / Sign up

Export Citation Format

Share Document