MEASURING AND QUANTIFYING WEB APPLICATION DESIGN

The World Wide Web makes it easier for organizations and people to share information across great distances at a minimal cost. In addition, governments and businesses are beginning to offer services on the World Wide Web to their respective populations and customers. Unlike traditional desktop based applications where the programming language used are most likely Object Oriented (OO) based languages such as C++ or Java, most web applications are built upon more lightweight scripting languages. These languages typically don’t support all the OO features that more traditional languages support. In addition, some web applications are dependent on external web services or applications. These differences make it difficult to use traditional measuring techniques such as Quality Measurements in Object Oriented Design to quantify the complexity of a web application or its quality. This paper will propose a set of measurements derived from traditional Object Oriented metrics such as QMOOD, and attempt to use them on two Content Management Systems; Drupal and WordPress. These measurements will try to quantify the size and complexity of the two content management systems and make comparisons between them

Using Software Metrics in the Evaluation of a Conceptual Component Model

International audienceEvery interactive system has a functional part and an interactive part. However the software engineering and the human-computer-interaction communities work separately in terms of methods, models and tools, which induces a work overhead for integrating the results of these efforts, as well as increased inconsistency risks. We endeavour to treat this problem by proposing a design method, which couples the functional kernel and the interaction design. In particular, this method proposes a specific way of structuring the interaction and the business spaces. The structure is based on components called Symphony Objects. In this article, we attempt to evaluate the technical aspect of a Symphony Object model issued from the method by measuring its implementations with software metrics

Using Software Metrics in the Evaluation of a Conceptual Component Model

International audienceEvery interactive system has a functional part and an interactive part. However the software engineering and the human-computer-interaction communities work separately in terms of methods, models and tools, which induces a work overhead for integrating the results of these efforts, as well as increased inconsistency risks. We endeavour to treat this problem by proposing a design method, which couples the functional kernel and the interaction design. In particular, this method proposes a specific way of structuring the interaction and the business spaces. The structure is based on components called Symphony Objects. In this article, we attempt to evaluate the technical aspect of a Symphony Object model issued from the method by measuring its implementations with software metrics

Software metric for Java and C++ practices (Workpackage 1.1)

The objective of this deliverable is to define a catalog of software met- rics. In particular we analyze the metrics used in the Squale Model and tool. In addition it offers a coherent set of software metrics for object-oriented languages on top of which Squale practices will be based. There is a plethora of software metrics and a large amount of research articles. Still there is a lack for a serious and practically-oriented evaluation of metrics. Often metrics lacks the property that the software reengineer or quality expert can easily understand the situation summa- rized by the metrics. In particular since the exact notion of coupling and cohesion is complex, a particular focus on such point is important

Proceedings of 11th Symposium on Programming Languages and Software Tools and 7th Nordic Workshop on Model Driven Software Engineering

Robert C. Martin presented a software metric for a set of classes i.e. a package. The objective of the package level metric is to identify poorly designed packages. The Martin's metric actually consists of eight metrics which measure a few different characteristics of packages. The metric is widely known, but there is lack of theoretical and empirical evaluation of the Martin’s metric. This paper evaluates the theoretical background of the metric against an evaluation framework and presents an experimental evaluation of five open-source software applications. The theoretical validation reveals a weakness in Martin's definition for cohesion. We propose a modification which is valid according to the evaluation framework.  </div

Software Metrics for Package Remodularisation

There is a plethora of software metrics \cite{Lore94a, Fent96a, Hend96a, Han00a, Lanz06a} and a large amount of research articles. Still there is a lack for a serious and practically-oriented evaluation of metrics. Often metrics lack the property that the software reengineer or quality expert can easily understand the situation summarized by the metrics. In particular, since the exact notion of coupling and cohesion is complex, a particular focus on such point is important. In the first chapter of the present document, we present a list of software metrics, that are commonly used to measure object-oriented programs. In the second chapter we present our proposition for package metrics that capture package aspects such as information hiding and change impact limits

Practices in the Squale Quality Model (Squale Deliverable 1.3)

This document presents the Squale Software Quality Model as defined by Qualixo. It first reviews existing quality models and presents the Squale model with its particular- ity, namely a practice layer. Then it reviews in details an instance of this Squale Model with its Factors, Criteria and Practices, giving precise definitions and description1. Fi- nally, it discusses possible future enhancements of this model like new practices or its agreement with the program life-cycle and the change of needs during this life cycle