Mike Walker's Blog

Recap: Penn State Enterprise Architecture Education & Research Initiative

In this session at the Open Group Conference, Dr. Brian Cameron walked us through Penn State Enterprise Architecture Initiative at the College of ISTEA IST. I have blogged about this program before (Enterprise Architecture Goes To College, EA Becoming Academically Recognized and Offered) where I provide a listing of the other college institutions that offer EA in some form or another.

I learned a few additional interesting facts about the program. Specifically some of the key areas that Dr. Cameron is planning on expanding:

• Launch of online Professional Masters in EA
• Launch of undergraduate focus in EA
• Growth of the research portfolio
• Expansion of the Center for Enterprise Architecture

 

Below is the recap of the session.

 

Overview

The holistic nature of research endeavors aimed at understanding and improving the craft and practice of EA would mean that a number of disciplines will be implicated in defining the problem domain as well as contribute perspectives, approaches and techniques that will be valuable for addressing EA research concerns. Research on EA can benefit from these perspectives contributed by a number of allied disciplines.

• Enterprise Architecture Advisory Board, over seventy organizations from seven countries
• First Advisory Board Meeting conducted September 2009
• Creation of an undergraduate EA degree focus
• Creation of an online Professional Masters Program
• Creation of a professional development portfolio
• Creation of an EA Research Center

 

Dr. Cameron also established the Federation of Enterprise Architecture Professional Organizations (FEAPO) that is an association of professional organizations whose members have an active interest in the practice and professionalism of Enterprise Architecture.

FEAPO provides a forum to facilitate collaboration and coordination of activities of among Enterprise Architecture (EA) related professional organizations, to work toward a better integrated community and “one face”for the advancement of the profession of Enterprise Architecture. The advent of FEAPO has been welcomed the world over because there is a strong desire among practitioners and organizations in many countries to professionalize and advance the field of enterprise architecture.

This group consists of the following members:

• Data Management International
• International Association of Software Architects
• International Council on Systems Engineering
• International Standards Organization (ISO)
• The Association for Enterprise Information
• The Association for Enterprise Architects
• The Association of Business Process Management Professionals International
• The British Computer Society
• The Business Architecture Guild
• The Business Architects Association
• The Center for the Advancement of the EA Profession
• The EA Shared Interest Group from the Industry Advisory Council
• The Integration Consortium
• The Object Management Group
• The Open Group
• The National Association of State CIOs

 

Four Main Areas of the Program

• Undergraduate Education committee
• Defining the competencies that an undergraduate student graduating with a focus in Enterprise Architecture should possess.
• Masters Education committee
• Defining what competencies should be built into the new online Enterprise Architecture Professional Masters Program.
• Professional Development committee
• Defining what type of continuing education offering should be developed in the area of enterprise architecture. Offerings could include certificate programs, executive education, and customized programs for specific organizations.
• Research committee
• Defining what research streams should be developed and enhanced in relation to Enterprise Architecture.
• Helped develop a straw man participation model for the new EA Center.

 

Key Research Areas

1. EA career path development
2. EA framework development and usage
3. EA maturity assessments
4. EA Stakeholder analysis & engagement
5. Understanding EA styles
6. Value measurement frameworks for EA
7. Application of EA to areas outside of IT (e.g.: supply chain)

 

 

Organizations Involved

Alfabet, Germany Applied Research Lab/ Penn State Air Force Research Laboratory Armstrong Process Group Assoc. of Enterprise Architects (AEA) Association for Enterprise Information BAE Systems Inc Bllue Cross Blue Shield Association Boeing Booz Allen Hamilton Business Architecture Guild Center for the Advancement of the Enterprise Architecture Profession (CAEAP) CIGNA Computer Aid Inc. (CAI) Computer Sciences Corporation Cutter Consortium DAGH,LLC Department of Homeland Security Data Management International (DAMA International) Defense Intelligence Agency Deloitte Consulting EMC Corporation Ernst & Young FEMA Forrester Research Gartner GEICO IBM Innoveer Solutions Integration Consortium Iteraplan, Germany International Organization for Standardization (ISO) Johnson & Johnson Kaiser Permanente Kingdee Research Institute, China

LMI Lockheed Martin Mathet Consulting, Inc. Meraka Institute, South Africa NetApp Northrop Grumman Object Management Group (OMG) Oracle PA. State System of Higher Education (PASSHE) Pfizer Pinnacle Business Group PNC Financial Services Group PricewaterhouseCoopers Progressive Insurance Raytheon Smartsphere PPM and EAM Solutions State Farm Insurance Company TATA Consultancy Services , India The Confiance Group The Enterprise Architecture Shared Interest Group from the Industry Advisory Council The National Defense University The MITRE Corporation The Open Group TONEX Trout Technologies Unisys Corporation U.S. Department of Defense U.S. Department of Interior U.S. General Services Administration (GSA) U.S. Office of Management and Budget (OMB) U.S. Air Force, Chief, Enterprise Architecture Division, Office of Warfighting Integration and CIO Verizon Telecom -Information Systems Virginia Information Technologies Agency Wipro Technologies

ArchiMate 2.0 Highlights

I am really excited about the new release of ArchiMate.  The reason I am so excited is that for the first time ArchiMate complements TOGAF with a compelling, versatile and unambiguous visual modeling language that covers the end to end enterprise architecture development method and not just solution architecture. Not only do we have the next evolution of the standard but it also comes backed with the training and certification aspects as well that makes this a very real and implementable standard.

This post is centered around some of the key highlights distilled from the my previous two posts (The Open Group Releases ArchiMate 2.0 , ArchiMate 2.0 Certification Released) and some additional analysis of the recent release of ArchiMate.

In general, the  ArchiMate 2.0 aids in the following ways:

• Helps model the enterprise architecture
• Works in a manner aligned with TOGAF
• Supports the preparation and management of:
• Business change
• Application rationalization
• Program and portfolio management
• Outsourcing scenarios
• Improves business and IT alignment
• Performs cost analysis and business case calculations

 

Additionally, there are six key aspect you should know about the new Archimate 2.0 specification.

 

#1 Improved and Expanded

• Based on many years of practical experience of modeling and analysis of Enterprise Architecture by a world-wide user base
• ArchiMate 2.0 now enables the creation of fully integrated models of the organization’s enterprise architecture, the motivation for it, and the programs, projects and migration paths to implement it

 

#2 Now fully aligned with TOGAF

With ArchiMate 2.0, it’s the first fully integrated version with TOGAF. With the updates of TOGAF 9.1 (clean up of the spec) and ArchiMate 2.0 we finally have a real modeling notation for EA. It promises to provide a vendor-independent set of concepts, that helps to create a consistent, integrated model “below the waterline”, which can be depicted in the form of TOGAF views.

• Integrated, consistent and coherent modeling in various phases
• Specifically designed for enterprise architecture
• Full support for viewpoints (predefined and user-defined) that supports generation of compelling views for various stakeholders from a central repository
• Not just the ‘boxes’, but also their interrelationships
• Explicit support for the service paradigm that defines business, application and infrastructure services with concrete, visible results for various stakeholders can be generated from a repository
• Impact-of-change, gap analysis, etc.
• Easy reuse of models, maintained in shared repository

 

#3 Improved TOGAF ADM alignment

• The language structure of the ArchiMate Core corresponds with the three main architectures as addressed in phases B, C & D in the TOGAF ADM
• The extensions to the Core closely correspond with the main aspects to be addressed in the Preliminary phase, Phase A and the Central Requirements management repository, as well as Phases E, F, G and H

The largest alignment area is the Architecture Metamodel as shown below:

 

However, there are great examples for each phase are shown below:

Preliminary Phase

Team Organization

 

Building Architecture Principles

 

A – Vision

Stakeholder Analysis

 

Business Goals

 

Architecture Vision

 

B – Business Architecture

Business Architecture

 

Realization of Requirements

 

C – Information Systems Architecture

Baseline / Current State Architecture

 

Target / Future State Architecture

 

Gap Analysis

 

Process Application Support

 

Information Structure View

 

Data Dissemination Diagram

 

D – Technology Architecture

Baseline Technology Architecture Model

 

Target Technology Architecture

 

Technology Architecture Gap Analysis

 

Platform Decomposition Diagram

 

Application / Technology Support Map

 

E – Opportunities and Solutions

Transition Architectures

 

F – Migration Planning

Projects for the Transitions between Plateaus

 

H & RM – Architecture Change Management & Requirements Management

Traceability Model

 

 

#4 ArchiMate 2.0 improves collaboration

By promoting a growth in shared understanding across multiple information roles including business executives, enterprise architects, systems analysts, software engineers, business process consultants and infrastructure engineers

 

#5 New Core extensions

• The Motivation extension to model stakeholders, drivers for change, business goals, principles and requirements
• The Implementation & Migration extension to support project portfolio management, gap analysis and transition and migration planning

 

#6 Inconsistencies have been removed

• Examples have been improved
• Additional text has been inserted
• Certain aspects clarified

 

 

Technorati Tags: ArchiMate,Open Group,Modeling,Enterprise Architecture

ArchiMate 2.0 Certification Released

Along side the release of the ArchiMate 2.0 specification, a new certification for the ArchiMate has been released this week.

ArchiMate, an Open Group Standard, is an open and independent modelling language for enterprise architecture that is supported by different tool vendors and consulting firms. ArchiMate provides instruments to enable enterprise architects to describe, analyze and visualize the relationships among business domains in an unambiguous way.

The ArchiMate Certification Program provides certification for people, training courses and for tools that meet The Open Group standards:

• The ArchiMate 2 Certification for People Program is a market-driven education and certification program to support ArchiMate 2, and ensures that individuals are knowledgeable about ArchiMate.
• The ArchiMate 2 Tool Certification Program ensures that a tool meets the mandatory requirements to support the ArchiMate modeling language.
• The ArchiMate 2 Accredited Training Course Program provides an assurance mark for training courses including an assessment both of the course and also the personnel and organization. In addition, all accredited training course include in their course fee the examination.

 

Resources

This section contains links to the key program documentation, including Datasheets, Policies and Conformance Requirements for each aspect of the certification program, together with the CSQ templates where applicable

 

Program Datasheets

The following datasheets are available describing the ArchiMate 2 for People Certification program.

• ArchiMate 2 Certification for People: Program Summary
• ArchiMate 2 Certification for People: ArchiMate 2 Certified

 

Certification for Individuals

• ArchiMate 2 Certification for People policy
• ArchiMate 2 Certification for People Conformance Requirements
• ArchMate 2 Certification for People Trademark License Agreement

 

Accreditation of ArchiMate 2 Training Courses

• ArchiMate 2 Training Course Accreditation Policy
• Archimate 2 Training Course Accreditation Agreement
• Archimate 2 Accreditation Trademark License Agreement
• ArchiMate 2 Training Course Accreditation Conformance Requirements
• Archimate 2 Training Course Accreditation Conformance Statement Questionnaire
• ArchiMate 2 Accreditation checklist
• ArchiMate 2 Training Course Accreditation Fees
• Requirements for IBT Examination Supervisors
• Examination Proctor Agreement
• IBT Technical Requirements
• IBT Candidate Delivery Help

 

Archimate Tool Support Certification

• Architecture Tools Certification Policy
• ArchiMate 2 Tools Conformance Requirements
• ArchiMate 2 Tools Conformance Statement Questionnaire
• ArchiMate 2 Certification and Trademark License Agreement

 

Source: http://www3.opengroup.org/certifications/archimate/

 

Technorati Tags: ArchiMate,Open Group,Enterprise Architecture,Modeling

Open Group Conference Presentation–Why EA’s Must Drive Cloud Strategy and Planning

First and foremost, a big thank you to the attendees of my session.  We filled the room! All the interaction and questions were top notch. I really enjoyed presenting to all of you.

 

In my session,  Why EA's Must Drive Cloud Strategy and Planning I drove the core message around why the EA should lead Cloud Strategy efforts but then quickly diving into how EA’s can drive this. I use a real world example and show a framework and method I created to provide a repeatable and predictable set of outcomes.

For those that would like to view my presentation you can find it below:

Why EA's must drive cloud strategy

View more presentations from Mike Walker.

 

I will continue to provide more detail in future posts.

 

 

Technorati Tags: Cloud,Enterprise Architecture,Open Group Conference,Open Group,TOGAF

The Open Group Releases ArchiMate 2.0

The Open Group released ArchiMate 2.0, the latest version of the organization’s open and independent modeling language for enterprise architecture. The updated version is now aligned with TOGAF, enabling enterprise architects using the language to improve the way key business and IT stakeholders collaborate and adapt to change. New certification programs for the standard will also be available for those interested in becoming certified in ArchiMate 2.0.

 

ArchiMate 2.0 will include the following features and benefits:

• Improved business and IT alignment through  enterprise architecture modeling aligned with the TOGAF ADM
• Ability to better support the preparation and management of business change, application rationalization, program and portfolio management and outsourcing scenarios
• Ability to perform cost analysis and business case calculations
• A Motivation extension to model stakeholders, drivers for change, business goals, principles and requirements
• Implementation and Migration extensions to support project portfolio management, gap analysis and transition and migration planning
• Improved consistency and examples, as well as additional clarification updates from the previous version

 

Additional Resources and More Detail

• What’s New in ArchiMate 2.0?
• Visio Stencils

BP Business Architecture Session Recap

Shatender Singh and Madhav Madaboosi, BP Plc., US

Abstract: The Open Group has determined that Business Architecture is a critical input into the decision making for an Enterprise. This presentation will outline BP’s Business Architecture methodology and will also provide a case study. BP’s varied and global business processes required the convergence of siloed business architectures to meet a simplification agenda.

 

I sat in the BP Business Architecture Session Recap this afternoon. While there wasn’t a great level of detail on tangible business architecture concepts, approaches, models and tools I didn't find there was some useful nuggets for organizations to think about when trying to build a business driven EA organization. This session turned out to be more of a case study / reflection of the BP organization.

 

BP started this journey as a result of a business led change or mandate for IT to support a transformation strategy. BP architects made two smart decisions as a result:

• Leverage an existing standard – TOGAF
• Once a method was chosen BP chose to put a heavy emphasis on business architecture approaches with a flavor of portfolio management

Their Approach includes:

• TOGAF adoption
• Enterprise Activity Model
• Strategic directions of the business unit
• Architecture vision and principles
• Benchmarking
• Long tern business requirements
• All projects go through the same governance model to align to the business direction
• Harmonized the same data model across the company
• Segmented portfolio by flagging solutions as strategic
• Leverages principles from TOGAF heavily
• Design based on principles

 

As a result they produce:

• Non strategic requirements
• Process maps
• Rethink the inflight projects and align them to the short term and long term business roadmap
• This in turn influenced the overall architecture views such as information, application and technology aspects.

 

Steps for alignment

• EAM Alignment
• Common Processes
• Data
• Application / Technical

 

Lessons learned from BP

1. Balancing geographic and localized requirements – This was very difficult with the geographies alone but when you add legacy software with constraints and specialized information.
2. Make architecture community driven and introduce social
3. Process alignment is important for other dependencies to work
4. Design authority over deployed assets is a critical element of the overall strategy
5. TOGAF helps structure the evolution of the target architecture

Open Group Conference San Francisco Day 1 Keynotes

Day 1 of the Open Group Conference was kicked off with a bang. Jeanne Ross, whom I refer to as our EA Rock Star started the day with some fresh thinking about how we approach EA.

For al the presentations we had a set of key themes:

• Pragmatic and realistic approaches
• Business centric
• Value focused

 

What a great set of speakers!

 

The Enterprise Architect: Architecting Business Success

Jeanne W. Ross, Director & Principal Research Scientist, MIT Center for Information Systems Research

Session: Enterprise architecture has typically been the domain of IT groups, but the impact of enterprise architecture is felt enterprise-wide. Research at MIT Center for Information Systems Research has shown that adoption of enterprise architecture leads to greater efficiencies and business agility But how can enterprise architects work with senior leaders to envision and lead successful business transformations. This talk describes how enterprise architecture has contributed to the success of firms like Campbell Soup, Southwest Airlines, and USAA. We’ll also discuss how enterprise architects have helped lead the way.

Highlights

• The days of Enterprise Architects trying communicate it’s value is over. EA has been widely accepted
• However, now we need to pull it off the promise of EA
• We have to make sure we don’t blow it and deliver on our promise
• The traditional IT Architecture method of Plan, Build, Operate is broken because it doesn’t allow organization to capitalize on their own capabilities.
• A new model is needed, a business value cycle, NOT a value chain
• Architects must consider reality in their value

 

 A New Model is Needed

Below is the Exploit, Commit, Build, Run model that is adapted from Jeanne Ross’s presentation. 

 

This model is a change of thinking and how we operate as Enterprise Architects. The goal of this model is to facilitate the shift of focus to capability thinking. The challenges highlighted were:

• Company capabilities are under utilized
• Company capabilities are often overlooked
• EA is not always business value driven
• New capabilities developed

 

Start with Exploit to direct us. Exploit doesn’t eliminate planning but makes it more effective.

 

Companies are doing similar things today and referenced in the presentation:

• Aetna
• Protection 1
• USAA
• Pepsi
• Commonwealth of Australia

 

How does this change?

• Information is key.
• Get it in the hands of the everyone.

 

USAA was used as an example of a company that has embraced this:

• Shifted their products around life events for their customers
• Enterprise strategy was put outside IT
• EA’s shift to advisors to the business

 

The role of EA’s in business value is to:

• Help senior execs clarify their business goals. EA’s should provide strategy to CIO’s as an advisory services.
• Identify architectural capability that can be readily exploited
• Present options and their implications for business goals
• Build capabilities incrementally

 

How Enterprise Architecture is Helping NISSAN IT Transformation

Celso Guiotoko, Corporate Vice President and CIO, Nissan Motor Co., Ltd.

In 2005, Nissan Global IS Dev developed "BEST" as an IT mid-term plan which significantly improved the efficiency of its information systems. This was followed in 2009 with the development of the "Change" program, which provided the basis for further advances by changing "people", "technology" and "process". And, in 2011, the next IT mid-term plan "VITESSE" was launched, designed to bring direct profit in the company by IT Dev.

Nissan focused on a core set or principles. They have some really good ones.

Nissan Principles

1. Business Value
2. Information is an asset
3. Reduce complexity
4. Independent from physical
5. Business driven
6. Change
7. Reuse
8. Competitive advantage
9. Best Practice

 

A program they established to make the transformation is called the BEST program. 

 

BEST Program Elements

• Business Alignment
• Enterprise Architecture
• Selective sourcing
• Technology Simplification

 

Some of the tools used by Nissan to deliver on BEST are:

• Business Process Reference Model
• Business Process is defined use
• Information Architecture – Entity modeling and
• Linking business architecture to information architecture
• Information data map
• Platform rationalization model

 

Business Process Reference Model

 

As a result of these EA efforts Nissan has a :

• Reduced cost per user from 1.09 to .63
• 230k return with 404 applications reduced
• The solution deployment time has been improved
• Significantly reduced hardware costs

 

 

The Transformed Enterprise

Andy Mulholland, Global Chief Technology Officer, Capgemini

If it is different to the well understood enterprise of today with its enterprise IT model what is different and why is it an advantage? These are basic questions which need to be addressed, and understood, before attempting to consider how business processes and resulting technology architectures will need to change.

Andy Mulholland author of three books since 2005 defining using the Web for business, changing to a collaborative working model and using clouds for enterprise business uses his experience to bring a cohesive answer to the questions

 

Highlights

• Inside Out vs. Outside In
• IT is Inside Out, focusing on the activities and problems within the 4 walls of the company wheras the business looks at problems Outside In.
• Two very different models
• The assertion is that we need to understand both of these forces
• The Outside In focus must be given a great deal more thought
• Conway's Law - Enterprises cannot change beyond the constraints of their communications
• Recommendation by Andy- "Seizing the Whitespace" by Johnson - for business model innovation
• Andy highlights the Gartner Nexus model of Cloud, Social, Information and Mobile as the transformation catalyst
• Social networks work better in fast environs to share knowledge efficiently than email
• Cloud forces down a transformation path
• TOGAF has to accept a new way of exposing value from the traditional inside out to a  TOGAF focused on a Outside In model

 

The Transformed Enterprise

 

 

Making Business Drive IT Transformation Through Enterprise Architecture

Lauren C. States, Vice President & Chief Technology Officer, Cloud Computing and Growth Initiatives, IBM Corp

Todays business demands and pressures have accelerated the pace of change. This focus on growing the business, entering new markets, enabling new, faster, better and less expensive services to customers creates challenges. While enterprise systems that may address these challenges are emerging:

• How is an enterprise to choose which IT systems to utilize?
• What strategies should they employ for short-term realization and longer term value of IT investments?
• How does the CIO ensure that business and IT infrastructures cohesively evolve while keeping pace with economic challenges and associated uncertain business implications

 

The Reality of the Forces on IT

1. Customer – Unlimited real-time access to ever changing information and expertise
2. Partners – Acting as an extension of the enterprise
3. Employees– Engaging externally in ways that are outside the traditional scope of work
4. Competitors – Entering new spaces quickly

 

Highlights

• We are the beginning of the next major shift
• IBM has reduced their application portfolio by 2/3 with cloud transformation
• Technology is changing the way the CMO is doing there job. Most are not ready because they go through a noisy set of data and a lose of control over brand
• Highlights the CIO survey http://www-935.ibm.com/services/c-suite/cio/study.html

 

IBM’s Cloud Transformation Model

 

Macro method used by IBM

 

Technorati Tags: Enterprise Architecture,Open Group Conference,Open Group

Come see me present Why EA’s Must Drive Cloud Strategy and Planning at the Open Group Conference

For those that are attending the Open Group conference in San Francisco here in the next few weeks from now I wanted to let you know that I will be presenting. My presentation is within the Cloud Strategy and SOA Governance track entitled “Why EA’s Must Drive Cloud Strategy and Planning” .

If this is a topic of interest to you or your organization, please stop by. It would  be great to see you there and answer any questions you may have.

Additionally, if you are at the conference or in the San Francisco area and would like to get together please let me know.

 

More

• My Session and Others: http://www3.opengroup.org/events/timetable/628
• Conference Home Page: http://www3.opengroup.org/sanfrancisco2012 

 

Technorati Tags: Cloud,Strategy,Enterprise Architecture,EA,TOGAF,Open Group Conference,Open Group

Open Group Publishes its First Cloud and International SOA Standards

Today, The Open Group announced three new industry standards to enable businesses to effectively integrate elements of SOA and Cloud Computing into a solution or enterprise architecture. The new standards are:

• SOA Reference Architecture
• Service-Oriented Cloud Computing Infrastructure Framework
• Open Group Service Integration Maturity Model

 

SOA Reference Architecture

Provides a blueprint for creating and evaluating SOA solutions. With the release of the SOA RA Standard, enterprise architects now have a common language and approach for creating SOA solutions that meet different organizational needs, and bridge the gap between business and IT.

 

This specification presents an SOA RA, which provides guidelines and options for making architectural, design, and implementation decisions in the implementation of solutions. The goal of this SOA RA is to provide a blueprint for creating or evaluating architecture.

Additionally, it provides insights, patterns, and the building blocks for integrating fundamental elements of an SOA into a solution or enterprise architecture.

Informally, the aim of the SOA RA is to answer some of the key questions and issues encountered by architects, including but not restricted to common questions such as:

• What are the aspects, building blocks, and layers of an SOA that I need to consider in designing solutions, establishing enterprise architecture guidelines, or assessing an architecture based on service-oriented principles?
• What are the building blocks I need to include in each layer of my solution or standardize as part of a enterprise architecture?
• What are some of the key architectural decisions I need to make when designing a solution, or assessing an architecture that is based on service-oriented principles?
• How do I increase my chances of gaining benefit from using SOA by taking into account key layers and building blocks with which I may initially be unfamiliar as our company makes it journey through higher levels of maturity? One of the ways in which we can establish a baseline and move to higher levels of maturity is to use The Open Group Service Integration Maturity Model (OSIMM) [21].
• Which roles in a project would benefit from using these principles and guidelines?

The SOA RA is used as a blueprint and includes templates and guidelines for enterprise and solution architects as well as software engineering roles within the software development life-cycle. These facilitate and ultimately enable automation and streamlining the process of modeling and documenting the architectural layers, the capabilities and the Architecture Building Blocks (ABB) within them, options for layers and ABBs, mapping of products to the ABBs, and architectural and design decisions that contribute to the creation of an SOA. It is intended to support organizations adopting SOA, product vendors building SOA infrastructure components, integrators engaged in the building of SOA solutions, and standards bodies engaged in the specifications for SOA.

More: http://www.opengroup.org/soa/source-book/soa_refarch/intro.htm

 

Service-Oriented Cloud Computing Infrastructure (SOCCI) Framework

Is the first Cloud standard from The Open Group, which outlines the concepts and architectural building blocks necessary for infrastructures to support SOA and Cloud initiatives.

Service-Oriented Cloud Computing Infrastructure (SOCCI) is the realization of this framework for the cloud. This document details the SOCCI elements, the synergies realized through the cohesive application of SOA and cloud-based principles, and the SOCCI Management Building Blocks. It expands upon the relationships between service-orientation and its application to various infrastructure components. Finally, the concepts outlined are explained in the context of a business scenario – Motor Cars in the Cloud.

Participants have specific requirements from the cloud computing infrastructure. We will be elaborating on these requirements. The relationship of the base roles (Consumer, Provider, and Developer) and composite role (Integrator) are described above.

More: http://www.opengroup.org/soa/source-book/socci/intro.htm

 

Open Group Service Integration Maturity Model

Delivers a common maturity model, which has now been ratified as an ISO and IEC International standard, for advancing the continuing adoption of SOA and Cloud Computing within and across businesses.

The Open Group SOA Integration Maturity Model (OSIMM) provides consultants and IT practitioners with a means to assess an organization’s Service Oriented Architecture (SOA) maturity level. It defines a process to create a roadmap for incremental adoption which maximizes business benefits at each stage along the way. The model consists of seven levels of maturity and seven dimensions of consideration that represent significant views of business and IT capabilities where the application of SOA principles is essential for the deployment of services. The OSIMM acts as a quantitative model to aid in assessment of current state and desired future state of SOA maturity.

 

More: http://www.opengroup.org/soa/source-book/osimmv2/intro.htm

 

More information

• Press Release - www3.opengroup.org/news/press/open-group-publishes-new-standards-soa-and-cloud
• SOA Reference Architecture PDF - https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?publicationid=12490
• Service-Oriented Cloud Computing Infrastructure (SOCCI) Framework (SOCCI) PDF - https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?publicationid=12510
• OSIMM V2 PDF - https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?publicationid=12450

 

Technorati Tags: Enterprise Architecture,Solution Architecture,SOA,Cloud,Reference Architecture,Patterns,Open Group

Open Group Complements TOGAF with SABSA Integration

The Open Group announced last month the release of the TOGAF & SABSA Integration Whitepaper, a new guide developed in collaboration with The SABSA Institute to enable enterprise and security architects to integrate security and risk management approaches into enterprise-level architectures. Endorsed and developed by The Open Group Security and Architecture Forums and The SABSA Institute, the whitepaper aims to help architects align IT security decisions with critical business goals while reducing costs and improving interoperability across the enterprise.

 

"For too long, security and risk management have been considered a discipline separate from enterprise architecture, which has led to increased costs, reduced interoperability and less productive organizations. This guide empowers enterprise architects to apply a holistic, business-driven approach to IT security decisions," said Jim Hietala, VP of Security for The Open Group. "Like TOGAF, the SABSA methodology provides guidance for aligning architecture with business value, in addition to addressing a critical need for greater integration between security and enterprise architectures within organizations."

Intended as a practical guide, the whitepaper views security architecture as an integral part of how enterprise architecture should be approached, a critical shift that is often overlooked in enterprise architecture frameworks but that encourages enterprise architects to focus attention on business processes rather than just technology solutions. To address security and risk management more effectively within enterprise architecture frameworks, the whitepaper also describes ways that TOGAF and SABSA can be seamlessly integrated for optimum security and business productivity. This includes detailed guidance on how to produce business and risk management-based security architectures, along with practical approaches to improve the integration of information security across the enterprise. Within this context, a main objective of the paper is to spark debate in the enterprise architecture community about the evolving role of enterprise architects in enabling the business to manage operational risk.

"In the past, security and enterprise architectures have been designed and acquired in silos, without common architecture languages that help tie both to broader business objectives," said John Sherwood, Head of the SABSA Academy, a division of The SABSA Institute. "We're proud to integrate SABSA with TOGAF finally to provide structure for the relationship between enterprise and security architectures, and help create more efficient, cost effective and productive enterprises. Our hope is that the paper will fundamentally change the way enterprise architects think about enterprise architecture."

The SABSA methodology was chosen for integration with TOGAF based on its objective of developing security architectures that facilitate the business, much like TOGAF's business driven approach and open methodology. Utilizing the SABSA Business Attributes Profiling method, the integrated methodology enables the creation of better architectures that drive tighter alignment between business and IT within enterprises. The whitepaper is the culmination of the TOGAF-SABSA Integration Project that began in May 2010 as a joint initiative of The Open Group Architecture Forum, Security Forum and The SABSA Institute.

The TOGAF SABSA Integration Whitepaper is available here: https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?publicationid=12449

 

Technorati Tags: Enterprise Architecture,TOGAF,SABSA,Risk Management,Security,ADM,Open Group