Abstract
Service-oriented architecture is now the most popular software engineering concept. Software related antipatterns – commonly used seemingly good but in fact wrong solutions – can have adverse consequences of varying importance.
It implies that the use of an antipattern can and should be viewed as a risky event. It follows that some principles of risk management can be used.
We propose a method based on slightly simplified procedures of risk management and assessment. Using the procedures we give a short list of the most risky antipatterns, i.e., antipatterns occurring very often and having crucial consequences and present principles of antipattern refactoring.
The discussion of antipatterns is based on a long-term experience with service-oriented and service-oriented like (e.g., process control) systems and on the analysis of practice.