Architect Consultant blog

Service Oriented Architecture Issues todays IT: Heterogeneity: no interoperable interfaces, now we have web services Business Focus Agility, reuse and cost reduction Benefits of SOA Reuse of Services (at the business unit level) Agility: respond quickly to changing business requirements Simpler integration (by using standards) Architectural Principles Formal contracts (Thomas: Contract Standardization) Loose Coupling Abstraction Reusability Autonomy Statelessness Discoverability Composability (Durability) (Interoperability) (Standards compliance) (First all from Thomas Erl's books, last three added by Oracle) Service Definition principles Service encapsulation - A Service must perform a complete unit of work Service loose coupling - Services maintain a relationship that minimizes dependencies between them Service contract - Services adhere to a contractual agreement, as defined collectively by one or more Service description documents Service abstraction -

Introduction I work as a Enterprise Application Integration / Service Oriented / Business Process Management consultant at a company. I started using Blogger , LinkedIn , Facebook and Twitter  almost 2 years ago. I started with LinkedIn and almost a year later with my blog, recently i started using Twitter and Facebook. I also tried Plaxo and Hyves but I dropped them. My first reaction to Twitter and Blogger was the same as the one I get today: I have no time to Blog I do not know what to Blog Why should I Blog? And with Twitter: I do not know what to Tweet I am not interested in what a person does in the bathroom Too may Tweets to read Stupid stuff Within this blog item i will try to explain why I think it is a necessity (or can be) for every consultant. Blogging I started blogging with knowledge storage in mind. When I found a solution for a particular problem or when I did not want to forget how I did some things, i started to make a Blog item for it. This way I could always look up

Overview Licencing Modeling tools and Users Business/Enterprise Architect Business Strategy Implement Business Architecture Process Analysis/documentation Business User Understands the business High level business processes Process Analyst BPMN 2.0 expert (business view) Understands the details of the business Make implementation decisions Process Developer BPMN 2.0 expert (technical view) WebServices, XML Enterprise Apps Implement processes and UIs Collaborative Design BPM Studio Process Analytics Social BPM SOA Platform End-to-End instance and Flow checking due to integrated platform. BPMN 2.0 support Change with BPMN 1.1 : Model execution Models are interchangeable XPDL and BPEL were used to interchange and execute Interactive task and workflow BPM Studio supports Simulation . BPM Studio Business Indicators Snapshots of business indicators must be added to the workflow and this is a little awkward because it blurs the process model. Good integrati