Marco Torchiano, Federico Tomassetti, F. Ricca, Alessandro Tiso, G. Reggio
The adoption of Model Driven Development (MDD) promises, in the view of pundits, several benefits. This work, based on the data collected through an opinion survey with 155 Italian IT professionals, aims at performing a reality check and answering three questions: (i) Which benefits are really expected by users of modeling and MDD? (ii) How expectations and achievements differ? (iii) Which is the role of modeling experience on the ability of correctly forecasting the obtainable benefits? Results include the identification of clusters of benefits commonly expected to be achieved together, the calculation of the rate of actual achievement of each expected benefit (varying dramatically depending on the benefit) and the "proof" that experience plays a very marginal role on the ability of predicting the actual benefits of these approaches.
{"title":"Benefits from modelling and MDD adoption: expectations and achievements","authors":"Marco Torchiano, Federico Tomassetti, F. Ricca, Alessandro Tiso, G. Reggio","doi":"10.1145/2424563.2424565","DOIUrl":"https://doi.org/10.1145/2424563.2424565","url":null,"abstract":"The adoption of Model Driven Development (MDD) promises, in the view of pundits, several benefits. This work, based on the data collected through an opinion survey with 155 Italian IT professionals, aims at performing a reality check and answering three questions: (i) Which benefits are really expected by users of modeling and MDD? (ii) How expectations and achievements differ? (iii) Which is the role of modeling experience on the ability of correctly forecasting the obtainable benefits?\u0000 Results include the identification of clusters of benefits commonly expected to be achieved together, the calculation of the rate of actual achievement of each expected benefit (varying dramatically depending on the benefit) and the \"proof\" that experience plays a very marginal role on the ability of predicting the actual benefits of these approaches.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115660025","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Rut Torres Vargas, Ariadi Nugroho, M. Chaudron, Joost Visser
The goal of this study is to investigate the use of UML and its impact on the change proneness of the implementation code. We look at whether the use of UML class diagrams, as opposed to using no modeling notation, influences code change proneness. Furthermore, using five design metrics we measure the quality of UML class diagrams and explore its correlation with code change proneness. Based on a UML model of an industrial system and multiple snapshots of the implementation code, we have found that at the system level the change proneness of code modeled using class diagrams is lower than that of code that is not modeled at all. However, we observe different results when performing the analysis at different system levels (e.g., subsystem and sub subsystem). Additionally, we have found significant correlations between class diagram size, complexity, and level of detail and the change proneness of the implementation code.
{"title":"The use of UML class diagrams and its effect on code change-proneness","authors":"Rut Torres Vargas, Ariadi Nugroho, M. Chaudron, Joost Visser","doi":"10.1145/2424563.2424566","DOIUrl":"https://doi.org/10.1145/2424563.2424566","url":null,"abstract":"The goal of this study is to investigate the use of UML and its impact on the change proneness of the implementation code. We look at whether the use of UML class diagrams, as opposed to using no modeling notation, influences code change proneness. Furthermore, using five design metrics we measure the quality of UML class diagrams and explore its correlation with code change proneness. Based on a UML model of an industrial system and multiple snapshots of the implementation code, we have found that at the system level the change proneness of code modeled using class diagrams is lower than that of code that is not modeled at all. However, we observe different results when performing the analysis at different system levels (e.g., subsystem and sub subsystem). Additionally, we have found significant correlations between class diagram size, complexity, and level of detail and the change proneness of the implementation code.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126496473","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
G. Reggio, Maurizio Leotta, F. Ricca, E. Astesiano
A software developer facing a modelling task may follow different styles at different levels of abstraction and precision, to better cope with the aims and the potential users of the model. We address the problem of modelling the business processes by means of UML activity diagrams, and present five styles differing in the precision level, from the Ultra-Light style, where the nodes and the edges of the activity diagram are decorated by freely-formed text, to precise styles where instead OCL and UML actions are used. Then, we propose a practical empirical method for choosing the most suitable style depending on the context in which the models will be used (why, when, where, how long, by whom).
{"title":"Business process modelling: five styles and a method to choose the most suitable one","authors":"G. Reggio, Maurizio Leotta, F. Ricca, E. Astesiano","doi":"10.1145/2424563.2424574","DOIUrl":"https://doi.org/10.1145/2424563.2424574","url":null,"abstract":"A software developer facing a modelling task may follow different styles at different levels of abstraction and precision, to better cope with the aims and the potential users of the model. We address the problem of modelling the business processes by means of UML activity diagrams, and present five styles differing in the precision level, from the Ultra-Light style, where the nodes and the edges of the activity diagram are decorated by freely-formed text, to precise styles where instead OCL and UML actions are used. Then, we propose a practical empirical method for choosing the most suitable style depending on the context in which the models will be used (why, when, where, how long, by whom).","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131993987","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Hafeez Osman, Arjan van Zadelhoff, Dave R. Stikkolorum, M. Chaudron
Class diagrams play an important role in software development. However, in some cases, these diagrams contain a lot of information. This makes it hard for software maintainers to use them to understand a system. In this paper, we aim to discover how to simplify class diagrams in a such way that they make systems easier to understand. To this end, we performed a survey to analyze what type of information software developers find important to include or exclude in order to simplify a class diagram. This survey involved 32 software developers with 75% of the participants having more than 5 years of experience with class diagrams. As the result, we found that the important elements in a class diagram are class relationship, meaningful class names and class properties. We also found that information that should be excluded in a simplified class diagram is GUI related information, private and protected operations, helper classes and library classes. In this survey we also tried to discover what types of features are needed for class diagram simplification tools.
{"title":"UML class diagram simplification: what is in the developer's mind?","authors":"Hafeez Osman, Arjan van Zadelhoff, Dave R. Stikkolorum, M. Chaudron","doi":"10.1145/2424563.2424570","DOIUrl":"https://doi.org/10.1145/2424563.2424570","url":null,"abstract":"Class diagrams play an important role in software development. However, in some cases, these diagrams contain a lot of information. This makes it hard for software maintainers to use them to understand a system. In this paper, we aim to discover how to simplify class diagrams in a such way that they make systems easier to understand. To this end, we performed a survey to analyze what type of information software developers find important to include or exclude in order to simplify a class diagram. This survey involved 32 software developers with 75% of the participants having more than 5 years of experience with class diagrams. As the result, we found that the important elements in a class diagram are class relationship, meaningful class names and class properties. We also found that information that should be excluded in a simplified class diagram is GUI related information, private and protected operations, helper classes and library classes. In this survey we also tried to discover what types of features are needed for class diagram simplification tools.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133483586","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
We present the results of a controlled experiment aimed to investigate whether the source code comprehension increases when participants are provided with UML class and sequence diagrams produced in the software design phase. The experiment has been conducted with Master students in Computer Science at the University of Salerno. The data analysis shows that the participants significantly better comprehend source code when it is added with class and sequence diagrams together.
{"title":"Does the combined use of class and sequence diagrams improve the source code comprehension?: results from a controlled experiment","authors":"G. Scanniello, C. Gravino, G. Tortora","doi":"10.1145/2424563.2424569","DOIUrl":"https://doi.org/10.1145/2424563.2424569","url":null,"abstract":"We present the results of a controlled experiment aimed to investigate whether the source code comprehension increases when participants are provided with UML class and sequence diagrams produced in the software design phase. The experiment has been conducted with Master students in Computer Science at the University of Salerno. The data analysis shows that the participants significantly better comprehend source code when it is added with class and sequence diagrams together.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126715095","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
S. Zugal, J. Pinggera, H. Reijers, M. Reichert, B. Weber
To empirically investigate conceptual modeling languages, subjects are typically confronted with experimental tasks, such as the creation, modification or understanding of conceptual models. Thereby, accuracy, i.e., the amount of correctly performed tasks divided by the number of total tasks, is usually used to assess performance. Even though accuracy is widely adopted, it is connected to two often overlooked problems. First, accuracy is a rather insensitive measure. Second, for tasks of low complexity, the measurement of accuracy may be distorted by peculiarities of the human mind. In order to tackle these problems, we propose to additionally assess the subject's mental effort, i.e., the mental resources required to perform a task. In particular, we show how aforementioned problems connected to accuracy can be resolved, that mental effort is a valid measure of performance and how mental effort can easily be assessed in empirical research.
{"title":"Making the case for measuring mental effort","authors":"S. Zugal, J. Pinggera, H. Reijers, M. Reichert, B. Weber","doi":"10.1145/2424563.2424571","DOIUrl":"https://doi.org/10.1145/2424563.2424571","url":null,"abstract":"To empirically investigate conceptual modeling languages, subjects are typically confronted with experimental tasks, such as the creation, modification or understanding of conceptual models. Thereby, accuracy, i.e., the amount of correctly performed tasks divided by the number of total tasks, is usually used to assess performance. Even though accuracy is widely adopted, it is connected to two often overlooked problems. First, accuracy is a rather insensitive measure. Second, for tasks of low complexity, the measurement of accuracy may be distorted by peculiarities of the human mind. In order to tackle these problems, we propose to additionally assess the subject's mental effort, i.e., the mental resources required to perform a task. In particular, we show how aforementioned problems connected to accuracy can be resolved, that mental effort is a valid measure of performance and how mental effort can easily be assessed in empirical research.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123436299","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
R. Macasaet, Manuel Noguera, María Luisa Rodríguez, J. L. Garrido, Sam Supakkul, L. Chung
Micro-businesses are the smallest enterprises and since they come in large numbers and are greatly diversified, they become difficult to define and classify. Micro-businesses also have several resource restrictions. These ambiguities and constraints make software research and development difficult in the micro-business domain. Component-based development offers advantages for the software of micro-businesses. The reuse of components for common requirements minimizes resource consumption in their software projects. This paper provides a working definition for micro-businesses, observations of their behavior, working micro-business behavior patterns, and examples of real world applications on how the patterns help in software development through requirements. The micro-business behavior patterns are associated with components that will be used later on in the development of micro-business software systems.
{"title":"Micro-business behavior patterns associated with components in a requirements approach","authors":"R. Macasaet, Manuel Noguera, María Luisa Rodríguez, J. L. Garrido, Sam Supakkul, L. Chung","doi":"10.1145/2424563.2424573","DOIUrl":"https://doi.org/10.1145/2424563.2424573","url":null,"abstract":"Micro-businesses are the smallest enterprises and since they come in large numbers and are greatly diversified, they become difficult to define and classify. Micro-businesses also have several resource restrictions. These ambiguities and constraints make software research and development difficult in the micro-business domain. Component-based development offers advantages for the software of micro-businesses. The reuse of components for common requirements minimizes resource consumption in their software projects. This paper provides a working definition for micro-businesses, observations of their behavior, working micro-business behavior patterns, and examples of real world applications on how the patterns help in software development through requirements. The micro-business behavior patterns are associated with components that will be used later on in the development of micro-business software systems.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128945435","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Feature models have been commonly used to model the variability and commonality in software product lines. We have defined the Feature Assembly Modelling, a feature modelling technique that allows to model variability in software adopting a multi perspective approach. Furthermore, the approach allows modelling software by combining both variability and reusability, i.e. we have developed an approach to take reusability into account while defining new software. To support the approach, we have also developed an information retrieval framework that provides an interactive visualization of the feature models. The visualization allows users to explore and query the existing models. In this paper, we report on our experience in introducing this variability modelling approach into a small-scale software company. This experience was very useful for both parties. The company was able to uncover the structure of their software and the modelling exercise provided them better insight in their products. For us, it has helped to better understand the needs of companies, to evaluate the usability of our Feature Assembly approach and the associated learning curve, as well as revealing its current limitations. Moreover, as we are aware of the fact that classical feature modelling is not yet a practice adopted by companies, it was interesting to see that our approach was well accepted and appreciated by the company.
{"title":"Modelling and managing variability with feature assembly: an experience report","authors":"Lamia Abo Zaid, Olga De Troyer","doi":"10.1145/2424563.2424575","DOIUrl":"https://doi.org/10.1145/2424563.2424575","url":null,"abstract":"Feature models have been commonly used to model the variability and commonality in software product lines. We have defined the Feature Assembly Modelling, a feature modelling technique that allows to model variability in software adopting a multi perspective approach. Furthermore, the approach allows modelling software by combining both variability and reusability, i.e. we have developed an approach to take reusability into account while defining new software. To support the approach, we have also developed an information retrieval framework that provides an interactive visualization of the feature models. The visualization allows users to explore and query the existing models. In this paper, we report on our experience in introducing this variability modelling approach into a small-scale software company. This experience was very useful for both parties. The company was able to uncover the structure of their software and the modelling exercise provided them better insight in their products. For us, it has helped to better understand the needs of companies, to evaluate the usability of our Feature Assembly approach and the associated learning curve, as well as revealing its current limitations. Moreover, as we are aware of the fact that classical feature modelling is not yet a practice adopted by companies, it was interesting to see that our approach was well accepted and appreciated by the company.","PeriodicalId":123055,"journal":{"name":"EESSMod '12","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116569682","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：