- I have no comments :) Ashraf Galal ... I have no comments :) Ashraf Galal On 2/20/2013 6:49 PM, Michael Poulin wrote: Ashraf, TOGAF is totally wrong aboutMessage 1 of 9 , Feb 20, 2013View SourceI have no comments :)
On 2/20/2013 6:49 PM, Michael Poulin wrote:
Ashraf,TOGAF is totally wrong about Business Architecture. I would not repeat their crap.
Re SOA and Business Architectue, I will not argue with your final conclusion - it is incorrect but it is because you do not know what Buisness Architecture is. I can only advise you to check the Site www.mpoulin.com in a couple of weeks for availability of the book that's dedicated to this exact topic.
From: Ashraf Galal <ashrafwg@...>
Sent: Wednesday, February 20, 2013 8:34 PM
Subject: Re: [service-orientated-architecture] Millar on Business Architecture & SOA
The business architecture definition (TOGAF v9):
The Business Architecture defines the business strategy, governance, organization, and key business processes.
From this definition, it addresses more than SOA and has nothing to do with SOA yet.
SOA as an Enterprise Architecture implementation method should be aligned with the business architecture.
To elaborate more:
For developing business goals-oriented enterprise architecture, system designers need to seriously focus on enterprise process perspective in such a task.
This stand will not only allow organizations to achieve their business goals, but also enable them to better reconcile business and IT that consumes millions of dollars invested into the enterprise IT infrastructure.
Infact, enterprise architecture provides a high-level description and view of the primary resources of any enterprise (Anaya & Ortiz 2005).
Theseprimary resources include users (users), processes (business processes), and technology (hardware and software).
However,the process or business process component of enterprise architecture represents the most central and fundamental, because it connects the other two resources (users and technology).
Poordefinition of business processes in an enterprise architecture leads to a number of problems such as "business and IT gap."
SOAcoming late in the life cycle, we don't use SOA for developing the business architecture.
Business architecture is input to SOA.
If we try to think SOA for business architecture it would be like we think in technology for gathering the requirements.
All the best
On 2/17/2013 8:34 AM, Gervas Douglas wrote:<<Is a business architecture reference model key to success with SOA projects?Designing an enterprise's SOA to work with business initiatives is a significant challenge facing SOA projects. In addition to Web services and SOA implementations, organizations must consider business intelligence from business processes. SOA solutions must deliver business flexibility for rapidly changing processes, businesses and data rules in a coordinated manner, for both people and machines. For that, business architects say that business architecture reference models are critical.Recently, I asked a group of business architects whether a business architecture reference model is key to SOA projects … [They] answered emphatically, "Yes."Ramsay Millar, practice lead, Integrate IT LLCManaging business and IT architecture models are strategic business capabilities -- and they need to be aligned to meet strategic outcomes. Communicating models and working together are key to realizing the dreams of SOA flexibility, cost savings and profits.A business model is made better when attention is paid to operational excellence. How does one achieve operational excellence? Through service quality. The service quality movement was led by EdwardDeming at Toyota, proven in the U.S. by JackWelch at GE in manufacturing and demonstrated in the services industry. But we must also explore frameworks for describing semantic business vocabulary models. The OMGBusiness Motivation Model (BMM) and TOGAFBusiness Architecture are a good beginning.The service quality movement in SOA projects needs to resonate with service quality practices. We need to describe the implied semantic business model using a holistic -- or systemsthinking -- approach when designing business solutions (collaborations between people and machines) to avoid continuing SOA project failures.Recently, I asked a group of business architects whether a business architecture reference model is key to SOA projects. I posted this question on a number of LinkedIn forums, including The BusinessArchitecture Community, TheOpen Group, TOGAFfor Architecture and Gartner EnterpriseArchitecture (Xchange). Business architects answered emphatically, "Yes." Here are summaries of their responses:
I would suggest recent researchby Birol Berkem on integrating business architecture frameworks as further reading on this topic.>>You can find this at: http://searchsoa.techtarget.com/answer/Is-a-business-architecture-reference-model-key-to-SOA-projects
- Business architecture reference models provide a holistic view first, to ensure that the value created through the SOA project fits into the big picture and aligns with the strategy of business operations and initiatives.
- A business reference architecture model is key for any type of project -- reference architecture can be used to support SOA projects as well. All SOA solution blueprints were created based on the reference architecture and used through the solution architecture review (governance) process and adjusted throughout the SDLC.
- Per the Open Group, the enterprise architecture (under which the business architecture is a key pillar) addresses the overall construction of the enterprise.
- The TOGAF business architecture meta-model needs to evolve and measure the impacts of strategic changes (driver, goal, objective). Business capabilities also need to be structured and related to service-levelagreements (SLAs). At the implementation level, we need to see direct linkage from business capabilities and SLAs that are orchestrated by business processes (people and machines).