On the Efficiency of Design Patterns Implemented in C# 3.0

Bishop, Judith; Horspool, R. Nigel

doi:10.1007/978-3-540-69824-1_20

Cited by 3 publications

(4 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The seminal text of Gamma, Helm et al (1995) documented twenty-three design patterns and these have been added to, modified and studied by others since (Antoniol, Fiutem, & Cristoforetti, 1998;Bishop, 2008;Buschmann, Meunier, Rohnert, Sommerlad, & Stal, 1996;Di Penta, Cerulo, Guéhéneuc, & Antoniol, 2008;Fowler, 1997;Schmidt, Stal, Rohnert, & Buschmann, 2000). Bieman et al (2003) selected thirteen of the twenty-three design patterns and explored whether their intended benefits and, in particular, whether their relative stability compared to other classes were being empirically realized.…”

Section: Motivation and Related Workmentioning

confidence: 99%

“…Object-oriented design patterns are reusable descriptions or templates showing the relationships and interactions between classes and objects (Bishop, 2008;Buschmann, Meunier, Rohnert, Sommerlad, & Stal, 1996Grand, 2002. Many design patterns including some of those described by Gamma, Helm, Johnson, and Vlissides (1995) promote adaptability by supporting specialization of the pattern-based classes.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Faults and Their Relationship to Implemented Patterns, Coupling and Cohesion in Commercial C# Software

Counsell

Gatrell

2012

International Journal of Information System Modeling and Design

View full text Add to dashboard Cite

This paper documents a study of fault proneness in commercial, proprietary software and attempts to determine whether a relationship exists between class faults and the design context of a class, namely the coupling and cohesion of a class, and whether the class is a participant of common design patterns. The authors studied a commercial software system for a 24 month period and identified design pattern participants by inspecting the design documentation and source code; coupling and cohesion metrics were measured by inspecting the source code with a tool; we also extracted fault data for the same period to determine whether a relationship existed between the design context and the fault propensity of a class. Results showed that design pattern participant classes were marginally more fault-prone than non-participant classes, The Adaptor, Method and Singleton patterns were found to be the most fault-prone of thirteen patterns explored. Coupling was found to have a significant relationship with the fault proneness of classes in the system; efferent coupling was a stronger indicator of fault propensity than afferent coupling. Cohesion, when measured using the LCOM(HS) metric, was not found to have a strong relationship with fault proneness.

show abstract

Section: Motivation and Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Faults and Their Relationship to Implemented Patterns, Coupling and Cohesion in Commercial C# Software

Counsell

Gatrell

2012

International Journal of Information System Modeling and Design

View full text Add to dashboard Cite

show abstract

“…However, our aim was to model these capabilities as linguistic constructs (with a type system and a semantics, proved sound) and to integrate them in the static type system of mainstream languages. With incomplete objects, we tried to shorten the distance between the language features and the design patterns, so that their implementation can be smoother [8] and possibly more efficient [9].…”

Section: Programming Examplesmentioning

confidence: 99%

Object reuse and behavior adaptation in Java-like languages

Bettini

Venneri

2011

Proceedings of the 9th International Conference on Principles and Practice of Programming in Java

View full text Add to dashboard Cite

Inheritance, which is a basic mechanism in mainstream objectoriented languages, introduces a strong coupling which limits modularity and code reuse. Furthermore, static class hierarchies cannot easily deal with unpredictable dynamic adaptations of the object behavior. In order to overcome these limitations, we propose new linguistic constructs for composing objects in a Java-like language. Objects are intended as featherweight components which can be used in multiple compositions, and object types specify not only the implemented functionalities, but also the required methods, which will be provided by other components during composition. Thus the language supports flexible object reuse and adaptation of the object behavior at run time. The static type discipline guarantees that method calls on well-typed object compositions are safe.

show abstract

“…We do not aim at replacing design patterns completely: design patterns will keep on providing "a high-level language of discourse for programmers to describe their systems and to discuss common problems and solutions" [11]. Language features should make the application of a pattern easier and possibly more efficient [11]. For instance, implementations of patterns were proposed using aspect-oriented programming [19] and collaboration-based design [25].…”

Section: Incomplete Objects and Design Patternsmentioning

confidence: 99%

I-Java: An Extension of Java with Incomplete Objects and Object Composition

Bettini

Bono

Turin

2009

Software Composition

View full text Add to dashboard Cite

Abstract. Object composition is often advocated as a more flexible alternative to standard class inheritance since it takes place at run-time, thus permitting the behavior of objects to be specialized dynamically. In this paper we present I-Java, an extension of the Java language with a form of incomplete objects, i.e., objects with some missing methods which can be provided at run-time by composition with another (complete) object. Therefore, we can exploit object composition as a linguistic construct, instead of resorting to a manual implementation. This work builds on our theoretical model of incomplete objects, which was proved typesafe.

show abstract

On the Efficiency of Design Patterns Implemented in C# 3.0

Cited by 3 publications

References 10 publications

Faults and Their Relationship to Implemented Patterns, Coupling and Cohesion in Commercial C# Software

Faults and Their Relationship to Implemented Patterns, Coupling and Cohesion in Commercial C# Software

Object reuse and behavior adaptation in Java-like languages

I-Java: An Extension of Java with Incomplete Objects and Object Composition

Contact Info

Product

Resources

About