Figure 2 - uploaded by Wael Mohsen
Content may be subject to copyright.
Contexts in source publication
Context 1
... [49]- [52] is a sample software package for circular graphs. It is creating publication-quality infographics and illustrations with a high data-to-ink ratio, richly layered data, and pleasant symmetries. Figure 19 and Figure 20 shows samples for Circos output ...
Context 2
... is creating publication-quality infographics and illustrations with a high data-to-ink ratio, richly layered data, and pleasant symmetries. Figure 19 and Figure 20 shows samples for Circos output DSM. ...
Similar publications
The literature proposes many software metrics for evaluating the source code non-functional properties, such as its complexity and maintainability. The literature also proposes several tools to compute those properties on source codes developed with many different software languages. However, the Rust language emergence has not been paired by the c...
Sustainable software development practices are essential for ensuring code quality, maintainability, and security. However, traditional approaches often overlook the presence of code smells and vulnerabilities, leading to technical debt and security risks. This paper presents a comprehensive analysis of code smells and vulnerabilities in Java appli...
The object of software defect prediction (SDP) is to identify defect-prone modules. This is achieved through constructing prediction models using datasets obtained by mining software historical depositories. However, data mined from these depositories are often associated with high dimensionality, class imbalance, and mislabels which deteriorate cl...
Software fault prediction is the significant process of identifying the errors or defects or faults in a software product. But, accurate and timely detection is the major challenging issue in different existing approaches to predicting software defects. A novel Gaussian linear feature embedding-based statistical test piecewise multilayer perceptive...
Citations
... In the midst of technological progress and competition to offer products and services to meet the demands of the consumer, the need arises to measure as a vital activity required to survive. Mohsen et al. [2] asserts that software metrics are a standard for determining process maturity and required effort. ...
... Kaner and Bond [8] argue that "measurement is the empirical and objective assignment of numbers, according to a rule derived from a model or theory, to attributes of objects or events with the intention of describing them". Referring to software, a metric is "a standard for measuring the degree to which a software system and process possess some property" [2]. Metrics help track the development of teams and their progress. ...
It is very important to understand the metrics that are applied within IT processes in today’s industry, why they are important, and in what types of companies they are used. This article presents the results of a systematic literature review of some of the most widely used metrics exposed in the literature, referring to Scrum, ITIL and CMMi practices. The objective is to determine the scientific progress in this field and to identify the candidate metrics that can be used later in a metrics integration model, designed to help monitor IT services to improving the performance of organisations that use Scrum, CMMi and ITIL. The exploratory search found 1,196 articles, of which 198 were reviewed, from which 31 were finally chosen. From these, a total of 297 metrics were identified, of which 112 (38%) are for Scrum, 98 metrics (33%) are for ITIL, and 87 (29%) are for CMMi. Most of these metrics are used in European companies.
... Following Figure 8 explains the daily teamwork and reflects each member state and each team state. As Wa'el [42] explained in the agile matrices, one of the most important KPIs is the burndown chart that reflects if the team on the planned track and will finish all of the tasks it committed to finishing it in the sprint planning meeting or not. Explain a sample burndown chart for Sprint of MoJ Team: ...
... To evaluate the quality of reduced ontologies, we used our previous researched tool called OntoHealthMonitor [33] along with a set of standard tools like (OntoClean [34], OntoQA [35]and OntoMetric [36], [37] [33], [37] on original and reduced ontology to compare each ontology quality before and after reduction operation. ...
... To evaluate the quality of reduced ontologies, we used our previous researched tool called OntoHealthMonitor [33] along with a set of standard tools like (OntoClean [34], OntoQA [35]and OntoMetric [36], [37] [33], [37] on original and reduced ontology to compare each ontology quality before and after reduction operation. ...
... To evaluate the quality of reduced ontologies, we used our previous researched tool called OntoHealthMonitor [40] along with a set of standard tools like (OntoClean [41], OntoQA [42]and OntoMetric [43], [44]) to generate a set of visualizations and metrics results about reduced ontologies. We applied all standard Metrics like (No. of classes, No. of properties, Size of vocabulary, Depth of inheritance, Entropy of graph, Class in degree, Class out-degree, Number of Fanout, Fanout of root class, No. of root classes, No. of leaf classes, Average depth of inheritance tree, No. of ontology partitions, No. of minimal inconsistent subsets, Average value of axiom inconsistencies, No. of separate connected components in the instances, No. of relationships between instances, No. of external classes, Reference to external classes, Reference includes) [40], [44] on original and reduced ontology to compare each ontology quality before and after reduction operation. ...
... To evaluate the quality of reduced ontologies, we used our previous researched tool called OntoHealthMonitor [40] along with a set of standard tools like (OntoClean [41], OntoQA [42]and OntoMetric [43], [44]) to generate a set of visualizations and metrics results about reduced ontologies. We applied all standard Metrics like (No. of classes, No. of properties, Size of vocabulary, Depth of inheritance, Entropy of graph, Class in degree, Class out-degree, Number of Fanout, Fanout of root class, No. of root classes, No. of leaf classes, Average depth of inheritance tree, No. of ontology partitions, No. of minimal inconsistent subsets, Average value of axiom inconsistencies, No. of separate connected components in the instances, No. of relationships between instances, No. of external classes, Reference to external classes, Reference includes) [40], [44] on original and reduced ontology to compare each ontology quality before and after reduction operation. The following table explains a simple comparison between primary and reduced ontologies metrics. ...
Ontology is widely used in the areas of knowledge engineering, web-based data mining, and others. The process of developing and evolving inter-organizational domain ontologies is easy to get much redundant information. Rough set theory can be used to reduce the attributes of ontologies. This type of reduction eliminates the harsh requirements of the reduct and overcomes the drawback of the possible reduct that the derived decision rules may be incompatible with the ones derived from the original system. In this paper, we formulate the preliminaries of using Rough Set Theory to solve this problem while building or evolving process of the inter-organizational domain ontology. This technique can be used to enhance automatic and semi-automatic operations to develop and evolve ontologies.
