Generalization Index: Defining a metric for the detection of smells in UML Class Diagrams in Eclipse Modeling Framework in Eclipse

In the field of Software Engineering, while designing the software design and maintaining the source code quality, a lot of good and bad practices come into being. With the continuous evolutions in the field of modeling in software development processes, Model Driven Software Development (MDSD), focuses towards the quality of software models. Unified Modeling Language (UML) is a graphical notation for expressing object-oriented designs. With its emergence as a modeling standard and being widely accepted by most software development organizations, in this research paper we focus on UML Class Diagrams. Metrics are mathematical models used for measuring. In software engineering, metrics are utilized for measuring quality aspects of software models. A manual model review is very time consuming and prone to errors, so it becomes essential to automate the tasks as effectively as possible. The Eclipse plug-in EMF Metrics supports specification and calculation of metrics wrt. specific EMF based models. A new definition technique for EMF quality assurance can be defined using Java, an OCL query or Henshin Pattern. In this paper we propose an algorithm for the calculation a new metric named Generalization Index Metric (GIX) for Java Code

Evaluasi dan Perbaikan Kualitas Desain Diagram Kelas

Dalam proses pengembangan dan pemeliharaan proyek perangkat lunak, kualitas merupakan salah satu hal penting yang menjadi penentu keberhasilan perangkat lunak.Kesalahan yang tidak ditemukan pada awal pengembangan akan membutuhkan sumber daya, biaya, dan waktu perbaikan yang lebih tinggi. Salah satu tahapan yang dilakukan saat proses pengembangan perangkat lunak adalah pemodelan data. Pada perangkat lunak yang berorientasi objek, data biasanya dimodelkan dalam bentuk diagram kelas. Kualitas pada diagram kelas sangat tergantung pada pengetahuan dari perancang. Oleh karena itu, berbagai metrik telah dikembangkan untuk menilai kualitas desain dari berbagai aspek. Pada paper ini, Penulis mengusulkan sebuah pendekatan dan model untuk mengevaluasi, mendeteksi, dan memperbaiki desain kelas diagram, sehingga sesuai dengan kriteria kualitas yang diharapkan

Testability Assessment Model for Object Oriented Software based on Internal and External Quality Factors

Software testability is coming out to be most frequent talked about subject then the underrated and unpopular quality factor it used to be in past few years. The correct and timely assessment of testability can lead to improvisation of software testing process. Though many researchers and quality controllers have proved its importance, but still the research has not gained much momentum in emphasizing the need of making testability analysis necessary during all software development phases. In this paper we review and analyse the factors affecting testability estimation of object oriented software systems during design and analysis phase of development life cycle. These factors are then linked together in the form of new assessment model for object oriented software testability. The proposed model will be evaluated using analytical hierarchical process (AHP)

Applying i* metrics for the integration of goal-oriented modeling into MDD processes

Nowadays, there exist modeling techniques that provide good support for the requirements elicitation and analysis of complex scenarios, such as the i* modeling framework. However, the application of these requirements models into Model-Driven Development (MDD) processes is still dependent on the experience of analysts and designers to manually transform the defined requirements models into an appropriate MDD model. Certain approaches have proposed guidelines to facilitate and partially automate this translation, but there is a lack of validation rules establishing how to build i* models for an improved generation of the corresponding MDD models. Thus, in this paper, we propose a set of metrics that are oriented to validating the adequacy of i* models as the starting point for MDD processes, as well as a process for the application of the proposed metrics in the i* framework.Preprin

Evaluasi dan Perbaikan Kualitas Desain Diagram Kelas

Dalam proses pengembangan dan pemeliharaan proyek perangkat lunak, kualitas merupakan salah satu hal penting yang menjadi penentu keberhasilan perangkat lunak.Kesalahan yang tidak ditemukan pada awal pengembangan akan membutuhkan sumber daya, biaya, dan waktu perbaikan yang lebih tinggi. Salah satu tahapan yang dilakukan saat proses pengembangan perangkat lunak adalah pemodelan data. Pada perangkat lunak yang berorientasi objek, data biasanya dimodelkan dalam bentuk diagram kelas. Kualitas pada diagram kelas sangat tergantung pada pengetahuan dari perancang. Oleh karena itu, berbagai metrik telah dikembangkan untuk menilai kualitas desain dari berbagai aspek. Pada paper ini, Penulis mengusulkan sebuah pendekatan dan model untuk mengevaluasi, mendeteksi, dan memperbaiki desain kelas diagram, sehingga sesuai dengan kriteria kualitas yang diharapkan

A goal-oriented approach for the generation and evaluation of alternative architectures

There is a recognized gap between requirements and architectures. There is also evidence that architecture evaluation, when done at the early phases of the development lifecycle, is an effective way to ensure the quality attributes of the final system. As quality attributes may be satisfied at a different extent by different alternative architectural solutions, an exploration and evaluation of alternatives is often needed. In order to address this issue at the requirements level, we propose to model architectures using the i* framework, a goal-oriented modelling language that allows to represent the functional and non-functional requirements of an architecture using actors and dependencies instead of components and connectors. Once the architectures are modelled, we propose guidelines for the generation of alternative architectures based upon existing architectural patterns, and for the definition of structural metrics for the evaluation of the resulting alternative models. The applicability of the approach is shown with the Home Service Robot case study.Peer ReviewedPostprint (author's final draft

On the Quality of Relational Database Schemas in Open-source Software

International audienceThe relational schemas of 512 open-source projects storing their data in MySQL or PostgreSQL databases are investigated by querying the standard information schema, looking for overall design issues. The set of SQL queries used in our research is released as the Salix free software. As it is fully relational and relies on standards, it may be installed in any compliant database to help improve schemas. Our research shows that the overall quality of the surveyed schemas is poor: a majority of projects have at least one table without any primary key or unique constraint to identify a tuple; data security features such as referential integrity or transactional back-ends are hardly used; projects that advertise supporting both databases often have missing tables or attributes. PostgreSQL projects appear to be of higher quality than MySQL projects, and have been updated more recently, suggesting a more active maintenance. This is even better for projects with PostgreSQL-only support. However, the quality difference between both databases management systems is mostly due to MySQL-specific issues. An overall predictor of bad database quality is that a project chooses MySQL or PHP, while good design is found with PostgreSQL and Java. The few declared constraints allow to detect latent bugs, that are worth fixing: more declarations would certainly help unveil more bugs. Our survey also suggests that some features of MySQL and PostgreSQL are particularly error-prone. This first survey on the quality of relational schemas in open-source software provides a unique insight in the data engineering practice of these projects

A unifying framework for the definition of syntactic measures over conceptual schema diagrams (extended version)

There are many approaches that propose the use of measures for assessing the quality of conceptual schemas. Many of these measures focus purely on the syntactic aspects of the conceptual schema diagrams, e.g. their size, their shape, etc. Similarities among different measures may be found both at the intra-model level (i.e., several measures over the same type of diagram are defined following the same layout) and at the inter-model level (i.e., measures over different types of diagrams are similar considering an appropriate metaschema correspondence). In this paper we analyse these similarities for a particular family of diagrams used in conceptual modelling, those that can be ultimately seen as a combination of nodes and edges of different types. We propose a unifying measuring framework for this family and illustrate its application on a particular type, namely business process diagrams.Preprin

GUMCARS: General User Model for Context-Aware Recommender Systems

Context-Aware Recommender Systems (CARS) are extensions of traditional recommender systems that use information about the context of the user to improve the recommendation accuracy. Whatever the specific algorithm exploited by the CARS, it can provide high-quality recommendations only after having modeled the user and context aspects. Despite the importance of the data models in CARS, nowadays there is a lack of models and tools to support the modeling and management of the data when developing a new CARS, leaving designers, developers and researchers the work of creating their own models, which can be a hard and time-consuming labor, and often resulting in overspecialized or incomplete models. In this paper, we describe GUMCARS - a General User Model for Context-Aware Recommender Systems, where the main goal is to help designers and researchers when creating a CARS by providing an extensive set of User, Context and Item aspects that covers the information needed by different recommendation domains. To validate GUMCARS, two experiments are performed; first, the completeness and generality of the model are evaluated showing encouraging results as the proposal was able to support most of the information loaded from real-world datasets. Then the structural correctness of the model is assessed, the obtained results strongly suggest that the model is correctly constructed according to Object-Oriented design paradigm