A quantitative framework for software restructuring

Kang, Byung-Kyoo; Bieman, James M.

doi:10.1002/(sici)1096-908x(199907/08)11:4<245::aid-smr193>3.3.co;2-#

Cited by 10 publications

(7 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A number of studies demonstrate the significant correlation of software quality metrics with errors in the software design (e.g. [3,5,16,33,34]). In the tradition of this work, there are some works in the 1990s that are mainly rooted in software quality measurement.…”

Section: Related Workmentioning

confidence: 99%

On a Quest for Good Process Models: The Cross-Connectivity Metric

Vanderfeesten

Reijers

Mendling

et al. 2008

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

101

View full text Add to dashboard Cite

Abstract. Business process modeling is an important corporate activity, but the understanding of what constitutes good process models is still rather limited. In this paper, we turn to the cognitive dimensions framework and identify the understanding of the structural relationship between any pair of model elements as a hard mental operation. Based on the weakest-link metaphor, we introduce the cross-connectivity metric that measures the strength of the links between process model elements. The definition of this new metric builds on the hypothesis that process models are easier understood and contain less errors if they have a high cross-connectivity. We undertake a thorough empirical evaluation to test this hypothesis and present the findings. The good performance of this novel metric underlines the importance of cognitive research for advancing the field of process model measurement.

show abstract

Section: Related Workmentioning

confidence: 99%

On a Quest for Good Process Models: The Cross-Connectivity Metric

Vanderfeesten

Reijers

Mendling

et al. 2008

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

101

View full text Add to dashboard Cite

show abstract

“…The module detection literature is plentiful. Tools to improve legacy code use clustering to partition graphs (Mitchell, Mancoridis, 2006), metrics to increase cohesion (Kang, Bieman, 1999) and slicing of FDGs -Functional Dependence Graphs (Rodrigues, Barbosa, 2006), tools to detect modularity violations (Wong, et al, 2011). Even with a quantitative flavor, they clearly differ from the Linear Software Models' approach.…”

Section: Related Workmentioning

confidence: 99%

Linear Software Models for Well-composed Systems

Exman¹

2012

Proceedings of the 7th International Conference on Software Paradigm Trends

View full text Add to dashboard Cite

Modularity is essential for automatic composition of real software systems from ready-made components. But given ready-made components do not necessarily correspond exactly to the units and functionality of designed software system architecture modules. One needs a neat composition procedure that guarantees the necessary and sufficient components to provide required units. Linear Software Models are rigorous theoretical standards subsuming modularity. The Linear-Reducible model is proposed as a model of wellcomposed software systems, above and beyond software variability. Indeed, case studies of representative systems recognized as well-composed, be they small, intermediate building blocks or large scale, are shown to be Linear-Reducible. The paper lays down theoretical foundationsupon exact linear independence and reducible matrix conceptsproviding new precise meanings to familiar modularity ideas, such as the single responsibility theorem. The theory uses a Modularity Matrixlinking independent software structors to composable software functionals in a Linear Model. 92 Exman I..

show abstract

“…The metric lack of cohesion of method (LCOM) measures the degree of similarity of methods that access one or more of the same attributes [11]. Higher value of LCOM indicates that the methods may be coupled to one another via attributes, increasing the complexity of class design and the likelihood of errors during the development process.…”

Section: Testabilitymentioning

confidence: 99%

“…The metric, weighted method per class (WMC), is a count methods implemented within a class, or the sum of the complexities of the method [11]. As the value of WMC increases, testing become difficult and testability would decrease.…”

Section: Testabilitymentioning

confidence: 99%

Metrics for Test Case Design in Test Driven Development

Shrivastava¹,

Jain²

2010

IJCTE

View full text Add to dashboard Cite

The demand for quality in software applications has grown, and awareness of software testing-related issues plays an important role. In research, we formulate the Automated Test Case of Unit Testing design metrics from a collection of internal testing design metrics that are correlated. In this paper the test case design metrics estimation is based on object oriented software design metrics determine the testability of test case in Test Driven Development approach. The estimation of the Automated Test Case for Unit Testing (ATCUT) design metrics, measures that quantify attributes of a test case design, that can be measured by the size, complexity and reusability of test case and testability of its product.

show abstract

A quantitative framework for software restructuring

Cited by 10 publications

References 44 publications

On a Quest for Good Process Models: The Cross-Connectivity Metric

On a Quest for Good Process Models: The Cross-Connectivity Metric

Linear Software Models for Well-composed Systems

Metrics for Test Case Design in Test Driven Development

Contact Info

Product

Resources

About