To give a consistent and more valuable property on models, model-driven processes should be able to reuse the expert knowledge generally expressed in terms of patterns. We focus our work on the design stage and on the systematically use of design patterns. Choose a good design pattern and ensure the correct integration of the chosen pattern are non trivial for a designer who wants to use them. To help designers, we propose design inspection in order to detect "bad smells in design" and models reworking through use of design patterns. The automatic detection and the explanation of the misconceptions are performed thanks to spoiled patterns. A "spoiled pattern" is a pattern which allows to instantiate inadequate solutions for a given problem: requirements are respected, but architecture is improvable. BAD SMELLS IN DESIGN AND DESING PATTERNS 44 J OURNAL OF OBJECT TECHNOLOGY V OL. 8, NO. 3 BAD SMELLS IN DESIGN AND DESING PATTERNS 46 J OURNAL OF OBJECT TECHNOLOGY V OL. 8, NO. 3

Abstract. To give a consistent and more valuable feature on models, we propose that model-driven processes should be able to reuse the expert knowledge generally expressed in terms of patterns. In order to formalize and use them, some design pattern ontologies have been developed. To share them on the Web they have been implemented using the OWL language. They can be easily interrogated with dedicated query languages. Our work has consisted in extending a design pattern intent ontology with "alternative model" and "strong points" concepts, which partially refers "anti-patterns". We validate this approach in tooling a step of a design review activity, we have proposed. This activity, directed by design patterns, is adapted to a model driven process, for the need to improve object-oriented architecture quality.

No abstract

In order to guarantee the use of good analysis and design practices and an easier maintenance of software, analysts and designers may use patterns. To help them, we propose models inspection in order to detect instantiations of "spoiled pattern" and models reworking through the use of the design patterns. As a design pattern allows the instantiation of the best known solution for a given problem, a "spoiled pattern" allows the instantiation of alternative solutions for the same problem: requirements are respected, but architecture is improvable. We have collected a set of alternative solutions and deduced the corresponding spoiled patterns. We have defined a first catalog of these improvable practices from several experiments with students. To overcome the limits imposed by this method (restricted public, limited problems and tiresome validation process), we would like open this problematic to the expert community. To achieve this, we propose a collaborative website sharing bad practices in object oriented design to improve the use of patterns.

No abstract