Transitioning from Code-Centric to Model-Driven Industrial Projects

Author(s):  
Miroslaw Staron

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.

Author(s):  
Martin Monperrus ◽  
Jean-Marc Jézéquel ◽  
Joël Champeau ◽  
Brigitte Hoeltzener

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.


2021 ◽  
Vol 15 (24) ◽  
pp. 134-154
Author(s):  
Altti Lagstedt ◽  
Amir Dirin ◽  
Päivi Williams

Constant changes in a business context and software development make it important to understand how software quality assurance (SQA) should respond. Examining SQA from supplier and client perspectives, this study explores how different groups of SQA practitioners perceive future needs. A survey (n = 93) conducted in fall 2017 explored the views of SQA organizations on future trends. The results indicate that SQA organizations differ slightly in their attitudes to quality categories, as do different groups of SQA practitioners. It is argued that these differences should be taken into account when developing and implementing future SQA strategy. It is further argued that the found basic enables SQA management, evaluation of new practices, and allocation of resources to ensure that all quality categories remain balanced in the future.


2014 ◽  
Vol 1049-1050 ◽  
pp. 2032-2036
Author(s):  
Ai Ming Huang ◽  
Guang Shan Deng ◽  
Jun Hu ◽  
Yong Jun Huang

This paper mainly make a theoretical research and exploration on software quality assurance quality assurance improvement based on CMM process, with the educational software quality assurance model as an example. It elucidates the relationship between educational software process improvement and quality assurance, and explicits the importance of educational software development process improvement to the quality of educational software. Additionally, it discussed the establishment of educational software development model on the basis of the waterfall model of traditional software development, and construction of process quality management models and platforms based on CMM educational software process improvement.


Sign in / Sign up

Export Citation Format

Share Document