Organizations continue to struggle when identifying the role of business architects and persist in misaligning them to IT departments. Tom Graves, an Enterprise Architect at Tetradian Consulting, pointed out the problems this causes and challenges architects to not accept the status quo but rather, try and improve the situation.
The CompArch Conference is a federated conference that brings together researchers and practitioners interested in Component-Based Software Development and Software Architecture. This year the event is held at the University of Colorado in the United States from June 20th to June 24th. As general chairs Ivica Cnrkovic and Judith Stafford were appointed.
In a recent report, Gartner revealed that only 9% of Enterprise Architecture (EA) endeavors are done in partnership with the business side of an organization. While the percentage of collaborative projects is expected to increase to 30% by 2016, to some this is still an alarmingly low level of involvement by EA teams who run the risk of being bypassed when business groups make technical decisions.
In the wake of recent articles arguing that too much details in EA are futile, Ian, a Cloud Architect at Fujitsu, is wondering if better business architecture abstractions wouldn't be the key to successful Enterprise Architecture.
A new developerWorks article by Jens Andexer and Willem Bekker describes business implications of SOA, stressing both its advantages and drawbacks.
Justin Cormack sparks a discussion about the adoption of RESTful architectures in the enterprise or the lack thereof with his post.
Industry analyst Neil Ward-Dutton, writes that the combination of Business Process Management (BPM) and Service-Oriented Architecture (SOA) is seen as technically complementary. There are different views on how the two concepts play together, however, the author maintains that there is enough synergy between them to increase business value.
In a series of posts, following his participation in EAC 2009, Richard Veryard discusses the role and value of Enterprise Architecture.
One of the prerequisites for successful SOA implementation is an understanding of the business problem that will be solved and building a business case for the implementation.
The results of SOA case study competition, conducted by SOA Consortium and CIO magazine are showing common themes in SOA implementations. The include strengthening of business IT alliances as the main factor for implementation success and definitions of specific, confirmed by real numbers, business benefits, , as a measure of this success.
IT has consistently failed to deliver expected value time and time again. According to Ian Thomas, Industrialization (componentization, specialization) may be a solution for supporting software agility and reliability in the new business environment.
According to Clay Shirky, the success key for social software is “a brutally simple mental model [...] shared by all users”. Referring to it as Shirky’s law, Michael Nielsen analyzes why programmers often fail to obey it. His arguments as well as the discussion that has followed provide interesting insights into pitfalls that need to be avoided for building successful social applications.
AMQP came from inside of JPMorgan, thanks to John O'Hara. But his vision was bigger than just a new way to do things internally. The standard and open source technologies around it have been gaining momentum. Jeff Gould and others shed some light on where AMQP came from, who is driving it, and where it might be going.
Large centrally designed BI systems often don't meet the expectations of their end users. In this article at Cutter IT journal Scott Ambler has written about using Agile methods to help meet the user's expectations and deliver business value quickly.
While SOA was the big name in the buzzword tag cloud, BPM is quickly getting bigger and bigger. As organizations are becoming more aware of the need to tame their processes in order to get the benefits of IT investments, BPM is gaining importance and mindshare inside and outside of IT. Is one more important for your architecture?