Exploring implicit parallelism in class diagrams

Tolga Ovatman*, Thomas Weigert, Feza Buzluca

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

5 Citations (Scopus)

Abstract

Abstract: As multicore processors are becoming more wide-spread, leveraging of parallelism is once again becoming an important concern during the software development process. Substantial refactoring is required to parallelize legacy sequential software in order to exploit the advantages offered by parallel processing. In this study, guidelines are offered to aid in parallelizing object-oriented programs by analyzing their designs as represented in UML class diagrams. We define often occurring patterns of class-dependencies and demonstrate their characteristics in class diagrams by investigating their properties. We present example instances exhibiting the usage of these patterns in class diagrams. Through analyzing the runtime aspects of these instances, we have identified how they impact the parallelization of object oriented software. Taking these lessons into account when refactoring existing object-oriented software can significantly reduce time and effort required. We have evaluated our method by applying it to three popular design patterns and a real-world case study.

Original languageEnglish
Pages (from-to)821-834
Number of pages14
JournalJournal of Systems and Software
Volume84
Issue number5
DOIs
Publication statusPublished - 1 May 2011

Funding

This study was performed when Tolga Ovatman was at Missouri University of Science and Technology as a scholar of the Scientific and Technological Research Council of Turkey (TUBITAK) under scholarship number 2214 .

FundersFunder number
TUBITAK2214
Türkiye Bilimsel ve Teknolojik Araştirma Kurumu

    Keywords

    • Class diagram analysis
    • Object oriented software refactoring
    • Parallel software design

    Fingerprint

    Dive into the research topics of 'Exploring implicit parallelism in class diagrams'. Together they form a unique fingerprint.

    Cite this