Identifying class name inconsistency in hierarchy: a first simple heuristic

International audienceGiving good class names is an important task. Good programmers often report that they take several attempts to find an adequate one. Often programmers do not name consistently classes within a package, project or hierarchy. This is a problem because it hampers understanding the systems. In this article we present a simple heuristic (a distribution) to characterise class naming. We combine such a heuristic with structural information to identify inconsistent class names. In addition, we use this simple heuristic to give packages a shape. We applied such heuristic to 285 packages in Pharo to identify misnamed classes. Some of these misnamed classes are reported and discussed here

ACMiner: Extraction and Analysis of Authorization Checks in Android's Middleware

Billions of users rely on the security of the Android platform to protect phones, tablets, and many different types of consumer electronics. While Android's permission model is well studied, the enforcement of the protection policy has received relatively little attention. Much of this enforcement is spread across system services, taking the form of hard-coded checks within their implementations. In this paper, we propose Authorization Check Miner (ACMiner), a framework for evaluating the correctness of Android's access control enforcement through consistency analysis of authorization checks. ACMiner combines program and text analysis techniques to generate a rich set of authorization checks, mines the corresponding protection policy for each service entry point, and uses association rule mining at a service granularity to identify inconsistencies that may correspond to vulnerabilities. We used ACMiner to study the AOSP version of Android 7.1.1 to identify 28 vulnerabilities relating to missing authorization checks. In doing so, we demonstrate ACMiner's ability to help domain experts process thousands of authorization checks scattered across millions of lines of code

Enhance maintenance problem recognition techniques and its application to palm oil mills

This paper discusses the application of enhanced maintenance problem recognition techniques. The main contribution of this study is the proposed combined techniques, namely snapshot model, failure mode, effect and criticality analysis (FMECA), Pareto analysis, and decision analysis by using information technology (IT). The snapshot model is part of the maintenance modelling technique while FMECA, Pareto analysis, and decision analysis are part of maintenance reliability techniques. Each of the techniques and the proposed combined techniques is explained. The case study used for this enhanced technique was the palm oil mills maintenance problem. The result and possible further enhancement is also discussed

Enhanced maintenance problem recognition techniques and its application to palm oil mills

This paper discusses the application of enhanced maintenance problem recognition techniques. The main contribution of this study is the proposed combined techniques, namely snapshot model, failure mode, effect and criticality analysis (FMECA),Pareto analysis, and decision analysis by using information technology (IT). The snapshot model is part of the maintenance modelling technique while FMECA, Pareto analysis, and decision analysis are part of maintenance reliability techniques.Each of the techniques and the proposed combined techniques is explained. The case study used for this enhanced technique was the palm oil mills maintenance problem. The result and possible further enhancement is also discussed

Winnowing ontologies based on application use

The requirements of specific applications and services are often over estimated when ontologies are reused or built. This sometimes results in many ontologies being too large for their intended purposes. It is not uncommon that when applications and services are deployed over an ontology, only a few parts of the ontology are queried and used. Identifying which parts of an ontology are being used could be helpful to winnow the ontology, i.e., simplify or shrink the ontology to smaller, more fit for purpose size. Some approaches to handle this problem have already been suggested in the literature. However, none of that work showed how ontology-based applications can be used in the ontology-resizing process, or how they might be affected by it. This paper presents a study on the use of the AKT Reference Ontology by a number of applications and services,and investigates the possibility of relying on this usage information to winnow that ontology

The philosophy of logic

Postprin

Reconciliation of object interaction models

This paper presents Reconciliation+, a tool-supported method which identifies overlaps between models of different object interactions expressed as UML sequence and/or collaboration diagrams, checks whether the overlapping elements of these models satisfy specific consistency rules, and guides developers in handling these inconsistencies. The method also keeps track of the decisions made and the actions taken in the process of managing inconsistencies

Catalogue of Anti-Patterns for formal Ontology debugging

Debugging of inconsistent OWL ontologies is normally a tedious and time-consuming task where a combination of ontology engineers and domain expert is often required to understand whether the changes to be performed in order to make the OWL ontology consistent are actually changing the intended meaning of the original knowledge model. This task is aided by existing ontology debugging systems, incorporated in existing reasoners and ontology engineering tools, which ameliorate this problem but in complex cases are still far from providing adequate support to ontology engineers, due to lack of efficiency or lack of precision in determining the main causes for inconsistencies. In this paper we describe a set of anti-patterns commonly found in OWL ontologies, which can be useful in the task of ontology debugging in combination with those debugging tools

COMMUNITY PREFERENCES FOR TYPES OF BUSINESSES: A CASE STUDY OF THREE COUNTIES

Community/Rural/Urban Development,