Merely putting SOA into your proposal or as a stated capability is no longer going to be a “deal clincher” or a key “business differentiator”. The counterview I hear practitioners in SOA will say is that SOA is not just the standardized service practices but is also how the services can be identified that are differentiating. But that’s the rub. If SOA treats every requirement or design as a service problem, where is the difference?
A new technical report and a Quick Reference Guide exploring the synergies and identifying integration points between Frameworx and TOGAF® has been published by The Open Group and TM Forum.
If IT doesn’t believe in itself, how can we expect business to believe in us, to treat us like partners and not as order takers?
We are looking for more problem definitions and solutions to drive a collective global mindset forward to ensure that IT delivers benefits across the entire value chain. If we agree on what the problems are, prioritize and work on them in a wholly collegiate manner, the industry is in a better place as a consequence.
In the business architect profession, mistakes can have severe consequences. As such, it is only reasonable for customers to demand some kind of impartial proof of our professional skills.
Can the disciplines of architecture and information security do a better job of co-existence? What would that look like? Can we get to the point where security is truly “built in” versus “bolted on”?