Group items tagged

Technical documentation framework example

Architecture template example from HP

A pessimistic approach towards SOA seems to prevail in some blogs. But these opinions strike me by surprise. In the industries I am working for - public sector, healthcare and Defense/ public security - SOA is predominant and you will find only rare examples of tenders where SOA is not highlighted as the guiding principle for the whole architecture. SAP's CTO Vishal Sikka has already provided the community with some very helpful insights concerning these discussions. I just want to add some points from an architect's point of view: From my point of view it is not the SOA approach itself which should be questioned but the way how we architects sometimes work on SOA. Some of the mistakes that are listed below I have encountered during my SOA projects. Others are based on discussions with other architects and decision makers inside and outside SAP, from customers and from partners. My intention is simple: I want to help to avoid these mistakes in the future and to strengthen the SOA approach which is for me without an alternative.

How to represent data, information, concepts, strategy... A complete list of views with good examples.

"The first key characteristic of the emergent approach is best summarised as 'architect the lines, not the boxes', which means managing the connections between different parts of the business rather than the actual parts of the business themselves," said Bruce Robertson, research vice president at Gartner. "The second key characteristic is that it models all relationships as interactions via some set of interfaces, which can be completely informal and manual - for example, sending handwritten invitations to a party via postal letters - to highly formal and automated, such as credit-card transactions across the Visa network."