The Open Group’s new guide links all the moving parts (such as SOA principles, SOA governance, Reference Architectures, SOA maturity, SOA Meta-model, etc.) and I think it is a must-read for any enterprise architect using TOGAF® as their organization’s EA framework and SOA as an architectural style.
It’s time to review our EA practices and make amendments to the core frameworks and processes to face the challenges emerging from technology mega trends (Cloud/Mobile) and evolving business models (emerging markets).
As the IT environment has changed significantly over the past several years, members of the Security Forum saw a need to revisit the document, Enterprise Security Architecture, and to update the guidance contained in it to address changes including mobile device security, and new categories of security controls such as data loss prevention. Learn about the new download here.
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?