Cohesion and reuse in an object-oriented system
SSR '95 Proceedings of the 1995 Symposium on Software reusability
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
Refactoring use case models: the metamodel
ACSC '03 Proceedings of the 26th Australasian computer science conference - Volume 16
CSMR '01 Proceedings of the Fifth European Conference on Software Maintenance and Reengineering
Refactoring--Does It Improve Software Quality?
WoSQ '07 Proceedings of the 5th International Workshop on Software Quality
Dependency oriented complexity metrics to detect rippling related design defects
ACM SIGSOFT Software Engineering Notes
A cohesion metric proposal for object-oriented systems: COMIAS
ICCOMP'09 Proceedings of the WSEAES 13th international conference on Computers
Visual Indicator Component Software to Show Component Design Quality and Characteristic
ACT '10 Proceedings of the 2010 Second International Conference on Advances in Computing, Control, and Telecommunication Technologies
Improving object-oriented lack-of-cohesion metric by excluding special methods
SEPADS'11 Proceedings of the 10th WSEAS international conference on Software engineering, parallel and distributed systems
Hi-index | 0.00 |
Classes is the basic unit in object oriented software, therefore their quality has significant impact on the overall quality of the software. Class cohesion is one of the important factors that determine whether the design quality of a software is good or bad. In software development it is essential for software developers to gauge the degree of cohesion; yet in software development practice, it is rarely found software developers who are concerned with class cohesion and design quality. The lack of concerns resulted in their assembled software being difficult to maintain, understood and reused. Although these days there are many literatures discussing software metric as a tool to calculate the degree of cohesion, in reality the tool is rarely used. To seek an answer why these developers are reluctant to employ these metrics, a survey to several software developers was conducted. The result of the survey reveals that the developers prefer for an easier and more practical measurement. The use of a complicated and less practical measuring method makes the developers unwilling to gauge their design. Through this paper, the researcher is trying to formulate a more practical software metric and visual indicator that are easier to use. By applying visual indicator, the classes that have bad cohesion are able to be detected visually as well as able to map the risk of design outcome from metric gauging. It is hoped that visual indicator and software metric are able to be complementary tools for design software and refactoring; able to detect class cohesion problems fast and pinpoint area refactoring location.