SOA Best Practice, Governance, and Lifecycle Management

Just finalized the content for the training next week:

Day One: SOA Best Practice with Business and IT AlignmentBEST PRACTICE

Build a foundation for SOA practice understanding and provide a practical guidance with comprehensive content coverage and case studies to address the popular issues and confusions during SOA practice.

SOA Concept and Benefit Review: SOA CONCEPT AND BENEFIT REVIEW

·        SOA Conceptual Model

·        What SOA Means

·        SOA Major Benefits and ROI Estimate

·        ROI Estimate 2: SOA VISION AND ALIGNMENT WITH ENTERPRISE

ARCHITECTURE

Alignment of Business and IT

·        SOA Vision Reference

·        SOA Relationship with Enterprise Architecture

·        Service Oriented Enterprise (SOE)

·        Service Oriented Infrastructure

Case Study: "Why business model and cost model are important”

Session 3: SOA PRACTICE MODEL

SOA Practice Model

·        Service Structure: Layered Service Structure

·        Service Oriented Business Architecture: Business as a Service

·        Service Oriented Application Architecture: Composite Applications

·        Service Oriented Data Architecture: Data as a Service

·        Service Oriented Infrastructure: Framework, Cloud Computing, and ITIL

Case Study: "How to create SOA strategy and model for enterprise: Example Reviews and Lessons Learned"

SOA Practice Approach

·        Service Planning for Enterprise View

·        Segmentation and Federation Approaches

·        Service Componentization

·        Iterative and Incremental

Day Two: SOA Governance and Lifecycle Management

Provide a comprehensive coverage in governance concept, model, content, and SOA governance practice references. It’ll demonstrate how service lifecycle can be managed effectively with the help of SOA governance practice. Also, it’ll demonstrate how SOA practice can be evolved towards higher maturity with a roadmap. Finally, we’ll discuss where SOA is heading to.

§  Governance

§  Governance domains

§  Governance model

§  A governance structure

§  SOA Governance

§  SOA governance definition

§  SOA governance model

§  SOA governance structure

§  SOA governance process

§  SOA governance rule and regulations

§  SOA governance guidance

§  SOA governance technologies

§  SOA Lifecycle Management

§  SOA lifecycle components

§  SOA lifecycle management with governance

§  Two Case Studies:

§  Governance practice in two different organizations

§  SOA Maturity Model and Roadmap

§  Enterprise architecture maturity model

§  Service architecture maturity model

§  Service maturity model

§  SOA adoption roadmap

§  Where SOA Is Heading To

§  Curent state and trend

§  Business evolution associated with IT

§  Collaboration environment and cloud computing

§  Enterprise landscape evolution

§  The challenges enterprises are facing

§  How various efforts can work together cohesively

§  Content Summary and Discussion

Foundation-Based Approach for the Evolution of IT Enabled Business

Big change is ahead of us after the current economic downturn. Businesses and governments are adopting SOA and cloud computing, which implies a paradigm shift in how IT can impact business opportunities, performance, processes, and organization dynamics.  Businesses increasingly rely upon IT to achieve its goals and to implement its strategies. With technologies and products of many generations, and with stove-piped implementations, current IT complexity is growing faster than ever in replying to the required changes and integrations. IT costs are increasing exponentially.  Enterprise architecture, SOA, and Cloud Computing are aimed at meeting these challenges. Our service is to use a Foundation-Based Approach with an Enterprise Foundation Framework© to provide a cohesive practice of EA, SOA, and Cloud. This solution will be essential in providing a disciplined and systematical way to achieve the modernization and evolution objectives for IT enables businesses.

For instance, cloud computing will contribute to the content of Enterprise Architecture, but will not change the way how enterprise architecture should be approached and adopted.  Cloud computing is not a new technology, but suitable new technologies can help cloud computing to be more effective and efficient. While cloud computing may be over stated with its indirect influences during the hype, it is a practical implementation mechanism for Service Oriented Infrastructure, which is a subset for Service Oriented Architecture adoption.  Business advantages are gained mainly via Service Orientation, i.e. common service sharing in many different ways. Our service will clear the road, and enable our clients to move forward in a more effective and efficient manner.

Please contact us if you are interested: yan.zhao@architechllc.com

About Master Data Management

Got an email from a friend, talking about the Master Data Management (MDM) is a growing popular topic now. I believe there is no doubt about that, with the velocity of data we are producing and the tendency of increased data production. However, I think the key for the solution is beyond MDM domain. It is about how and what data should be collected.

I still remembered the raw data collection from web sites for data preservation. The amount of data growing makes me wonder even we can store them, how we can catch up in processing them to make them meaningful, e.g. to transform the data into information, let alone transform information into useful knowledge.  If data processing speeds continue leg behind data collection speeds, the data collected will not be useful, but add burden to the slow process. If more meaningless data involved, it’ll add more burden to the process. Therefore, we need to improve the data collection process, to collect the data with purpose, e.g. a Service Oriented Data Collection and Management Process, and collect the data cleanly.

Thoughts during OMG Business Ecology Initiative Day

I went to the OMG Business Ecology Initiative Day yesterday, and involved in very interesting discussions. Also, there are many other OMG meetings happening in the same venue.

Here I have some thoughts:

The term of Business Ecology sounds like to address business environment not limited to inside organizational boundaries. It indeed would be more meaningful in such extended business scope, due to the collaboration environment introduced by Internet, and even more by cloud computing, common service commoditization, social networking, etc.

Also, it would be good to address the challenges in business strategies, such as the pursue of process-driven, maturity, evidence-based management that lead to high productivity and cost reduction contradicts to the culture of innovation. We can see that innovation is increasingly moving to small businesses, and being acquired by the big ones after getting mature. At the meantime, common service providers are forming another separate line of business. This is becoming an ecosystem. Businesses are more correlated than before and with more mutual dependencies as well. The Inter-Enterprise Architecture I mentioned earlier was trying to describe this picture.

Enterprise Architects are Domain Dependent or Not

There is a discussion on: Can you apply sound EA practices across any domain or market?

One analogy I can think of is that a great landmark architect can accept architecture projects in different environment with different requirements, and do a good job in each case. The critical trait he/she has is the creativity combined with well-trained skills to come with a unique architecture solution that meets the requirements and fit the environment well. I believe this is the trait we need to have to accomplish any type of architectures successfully.

If we can handle an architecture assignment successfully or not, either in enterprise scope, a solution domain, or in architecture sub-domains, depends on if we can understand the requirements well for the required domain, scope, and environment. As we know, enterprise architecture has many components (or sub-domains), e.g. business, applications, information/data, infrastructure, technologies. How much each enterprise architect can handle depends on his/her background knowledge, experience, and skills let alone the creativity trait.

The easy acceptance of Big 5 is the repeatable processes (I don’t want to comment on if they are really the best practices or not) they tend to use with replaceable resources, which create similar results with less risk. This is a productivity-driven approach. The analogy is that the experienced architects produced “model home” architectures, while others go out to build many of those for their customers. However in reality, the production level “home building” approach does not fit everyone, which is one major reason for lacking of success stories. Each individual architect does make difference. In software industry, it tends to say, behind each successful product, there is a superstar architect. I believe this applies to architecture in any domain and any level.