Group items tagged

strategy

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.

the six best practices are: Use a phased methodology. Develop a process documentation guide. Create a decision matrix. Simulate, model, and test. Communicate effectively. Monitor the processes.

whitepaper,comparison between the two choices that businesses have for building XML-based web services:J2EE , .NET2

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

"Central Authentication Service project, more commonly referred to as CAS. CAS is an authentication system originally created by Yale University"

Here is a quick list of 5 useful business tools to help outmaneuver your competition and avoid a headache in the process.

"Systems Engineering"