Relevance, benefits, and problems of software modelling and model driven techniques—A survey in the Italian industry

Context Claimed benefits of software modelling and model driven techniques are improvements in productivity, portability, maintainability and interoperability. However, little effort has been devoted at collecting evidence to evaluate their actual relevance, benefits and usage complications. Goal The main goals of this paper are: (1) assess the diffusion and relevance of software modelling and MD techniques in the Italian industry, (2) understand the expected and achieved benefits, and (3) identify which problems limit/prevent their diffusion. Method We conducted an exploratory personal opinion survey with a sample of 155 Italian software professionals by means of a Web-based questionnaire on-line from February to April 2011. Results Software modelling and MD techniques are very relevant in the Italian industry. The adoption of simple modelling brings common benefits (better design support, documentation improvement, better maintenance, and higher software quality), while MD techniques make it easier to achieve: improved standardization, higher productivity, and platform independence. We identified problems, some hindering adoption (too much effort required and limited usefulness) others preventing it (lack of competencies and supporting tools). Conclusions The relevance represents an important objective motivation for researchers in this area. The relationship between techniques and attainable benefits represents an instrument for practitioners planning the adoption of such techniques. In addition the findings may provide hints for companies and universitie

Overview on agent-based social modelling and the use of formal languages

Transdisciplinary Models and Applications investigates a variety of programming languages used in validating and verifying models in order to assist in their eventual implementation. This book will explore different methods of evaluating and formalizing simulation models, enabling computer and industrial engineers, mathematicians, and students working with computer simulations to thoroughly understand the progression from simulation to product, improving the overall effectiveness of modeling systems.Postprint (author's final draft

The effects of education on students' perception of modeling in software engineering

Models in software engineering bring significant potential in improvements of productivity of engineers, and improved quality of the artifacts they produce. Despite this significant potential, modeling adoption in practice remains rather low. Computer Science and software engineering curriculums may be one factor that causes this low adoption. In this study, we investigate the effects of education on students’ perception of modeling. We conducted a survey in three separate institutions, in Canada, Israel, and the U.S. The survey covers various aspects of modeling and addresses students ranging from a first year in undergraduate studies until final years in graduate studies. The survey’s findings suggest that the perception of undergraduate students towards modeling declines as they progress in their studies. While graduate students tend to be more favorable of modeling, their perception also declines over the years. The results also suggest that students prefer more modeling content to be integrated earlier in the curriculum

An Exploratory Study of Forces and Frictions affecting Large-Scale Model-Driven Development

In this paper, we investigate model-driven engineering, reporting on an exploratory case-study conducted at a large automotive company. The study consisted of interviews with 20 engineers and managers working in different roles. We found that, in the context of a large organization, contextual forces dominate the cognitive issues of using model-driven technology. The four forces we identified that are likely independent of the particular abstractions chosen as the basis of software development are the need for diffing in software product lines, the needs for problem-specific languages and types, the need for live modeling in exploratory activities, and the need for point-to-point traceability between artifacts. We also identified triggers of accidental complexity, which we refer to as points of friction introduced by languages and tools. Examples of the friction points identified are insufficient support for model diffing, point-to-point traceability, and model changes at runtime.Comment: To appear in proceedings of MODELS 2012, LNCS Springe

UML – a survey on technical university students in Lublin

Unified Modeling Language (UML) is a commonly known OMG (Object Management Group) standard for designing software systems. However, practice shows that the usage of UML varies depending on the specificity of a software system and company. The authors decided to explore the perspective of students with experience in using UML by conducting a survey with them. Analysis of the data gathered revealed that they use UML diagrams as an additional help when developing software. The main risk turned out to be different diagram interpretations

Integrating knowledge accross disciplines. Experiences from the NeWater project

The starting question for this deliverable was how to create a new adaptive management concept that can integrate insights from various disciplines and connect people from different institutional backgrounds. From literature research and empirical research on the NeWater project we identified challenges for cross-disciplinary knowledge integration, we evaluated interventions for connecting multiple knowledge frames, we analyzed the process of group model building with UML and formulated recommendations. Cross-disciplinary research has arisen from a growing number of complex problems for which knowledge of a single scientific discipline or societal field is insufficient, but presents important challenges: (1) collaboration and integration of knowledge requires in depth discussions that are timeconsuming; (2) the recursive process of problem structuring and restructuring is often at odds with the sequential planning of project activities; (3) participation and mutual learning are crucial but need to be carefully structured and sequenced; and (4) management and leadership faces the difficult challenge of balancing in depth exploration with timely delivery of tangible results. We conclude with the following general recommendations for large cross-disciplinary projects: (1) including a preparatory proposal phase for thorough exploration of opportunities of between researchers and stakeholders (2) flexible funding, planning and operational arrangements to allow for a recursive research process; (3) a project size that allows frequent interaction opportunities between researchers and between researchers and stakeholders to allow for mutual learning and in depth exploration; and (4) enhancing learning opportunities from one project to the next

Does UML modeling associate with lower defect proneness?:a preliminary empirical investigation

The benefits of modeling the design to improve the quality and maintainability of software systems have long been advocated and recognized. Yet, the empirical evidence on this remains scarce. In this paper, we fill this gap by reporting on an empirical study of the relationship between UML modeling and software defect proneness in a large sample of open-source GitHub projects. Using statistical modeling, and controlling for confounding variables, we show that projects containing traces of UML models in their repositories experience, on average, a statistically minorly different number of software defects (as mined from their issue trackers) than projects without traces of UML models.</p