Top 10 SOA Pitfalls: #3 - Missing skills
Join the DZone community and get the full member experience.Join For Free
just like any other paradigm, a level of new knowledge and
experience is required. unfortunately, soa requires lots of new
knowledge and experience. it requires a different way of thinking of
more or less everyone involved. people are used to closed environments
on both organisational and technical level; largely well protected from
influences and unwanted dependencies with the outside world. it's all
in their area of influence which makes achieving short term results
relatively easy. i'm referring to silo applications where the world is
complicated enough. from their view, soa makes things even more
complex. there should be awareness that there is lack of knowledge,
experience and attitude and something should be done about this first.
there is no real solution, except for the obvious one: educate everyone
involved. also, agile methodologies have proven to be effective in
building up knowledge and experience.
companies we come across introduce soa in different ways:
- external consultant / architect advises the company to follow this new paradigm. if she is wise enough, she will first focus on the business case for soa and make people understand why the company needs this architecture style. at the end, this makes things less confusing for people who don't understand soa. at the same time, making an understandable business case for soa is a daunting task. but very much worth the effort. at the same time, companies tend to approach soa in their business cases as a thing which directly delivers value. they don't realize that soa is just an architectural style and not a thing. creating business case for soa means making the match between the real business values and advantages of this architectural style.
- product vendor has an esb (enterprise service bus), which seems to match with wanted features, which seems to be backed by real business needs. in the end, everybody is playing with the toy. playing becomes difficult over time, because knowledge development is often driven by the tool. non-it people tends to feel left out and see soa as something technical. strangely enough, even they seem to be happy with the big toy without the understanding how the toy solves their problems. another proof we all have something childish in ourselves.
- a group of people from within the company read the books, attend courses, conferences and so on and somehow realise soa will solve many of their problems. they get together, start brainstorming and soon realize that this thing called soa is huge and that there are many area's "where no man has gone before". according to them, if you want to do it well, you should spend a lot of time and effort in thinking and defining it. they act like researchers but without real plan covering the outline of this research, principles, results, criteria when the research is finished and so on. another proof of childish behaviour. children love to create something big, are satisfied if they learn something a long the way and be completely equanimous if the whole thing is not used or replaced with something else.
let me be clear that there are many ways to introduce soa and that it very much depends on the concrete situation. even the toy-based approach is in some situations the best possible approach. but, each of them suffers from a lack of knowledge and skills in many area's:
the term itself is quite new for many organisations and becomes important in soa world. creating business architecture in soa means crossing the departmental boundaries, integrated business process modelling, creation of canonical data models, definition of business services (which are later translated into concrete services), defining different kind of security architecture, gathering business requirements and concerns of many stakeholders, and thinking in soa design patterns.
software requirements engineering
the toolbox of an requirements engineer is often limited to use cases. this methodology is not very suitable in soa environment because it covers a very limited area. quality (deprecated term: non-functional) requirements become more important because the complexity of a soa architecture has larger impact on performance, availability, application management.
as a project manager, your project has budget and scope. it gets really fuzzy when people start requesting to build generic services and take care of their concerns. your budget holder could also be reluctant to pay extra for something like this. especially when you tell her what this means when the system is in production mode. a project manager should aim for two goals: usual delivery of the business product and "readiness" for soa. these goals could conflict and project manager should be able to manage these conflicts. we see in practice that project managers simply ignore the soa goals if the conflicts occur.
software architects and developers
they require skills on eai/soa patterns, webservices, messaging, esb's, bpm engines. and particularly difficult to find are specialists with experience in xslt, xquery, ebxml and ws-* stack.
testers will also need to understand soa and the exact implications of it on testing. testing services independently of each other is relatively easy. but what about a complete business process, supply chain testing, transaction handling over multiple services when a transaction must be rolled back, asynchronous messaging, automated testing and so on.
an it manager who does not really understand soa sees it as introduction of some large and expensive infrastructure components which magically solves the integration problems . in large organisations there are several it managers, one for each department. it proves almost impossible to introduce collective middleware. the problem is the assigned responsibility and ownership . one of the solutions is creation of a the separate middleware competence center or shared service center. this often is a complete new department. if you're lucky, the it manager and her staff have soa skills.
separate departments can have a protective attitude. although everybody in the company will tell you that collaboration is good for everyone, they will first protect interests of the department before they address overall company interests. the root cause is the unclear advantages of collaboration. people tend to see disadvantages, e.g. additional dependencies.
if a company lacks knowledge in only one these areas, the whole soa
undertaking is in danger. the symptoms are long discussions, sometimes
for a year or longer and the only results are large documents and/or
some unused middleware infrastructure. the discussions focus on who
should do what and how are responsibilities divided. the root problem
is that these people have many years of experience, but don't realize
they are lacking the skills needed for soa and they should be doing
something about this first.
hiring experienced consultants to the job only solves the problem if everybody actively participates in the learning process and consultants have coaching role.
lack of skills can be partially compensated by focusing on short term results and learning from mistakes, which is an agile way of thinking.
next week viktor grgic will take us to #2...
Opinions expressed by DZone contributors are their own.