For more information see the link below on VMWare site

http://www.vmware.com/files/pdf/VMware-View4-PCoIP-IG-EN.pdf

PC-over-IP is an innovative display protocol technology that enables the practical consolidation of all IT resources into a data center, eliminates the need for desktop workstations, PCs and thin clients, and delivers an uncompromised user experience to each desk, anywhere, without incurring the security risks associated with transmitting data across a network or having data reside in remote PCs.

Features

• Breakthrough innovation in display compression and propagation over LAN and WAN networks
• Fully transparent hardware bridging for peripherals and audio
• End-to-end security via wire-speed encryption on all data traffic sent between the centralized host and the user’s desktop
• Seamless integration into existing IT environments with no drivers required and no impact on the host operating system
• Unlimited desktop performance scalability as PC-over-IP technology is independent of host CPU or graphics processing
• Complete operating system and application independence

List of Cloud computing infrastructure tech and solution provider:

• 3Tera – Bought by CA – AppLogic grid OS used as cloud computing platform by service providers and enterprises
• IBM Smart Cloud- IBM is helping clients excel in cloud computing, providing secure and reliable Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) solutions.
• Appistry – Cloud computing middleware - Enables easily scalable cloud computing in the enterprise.
• Cassatt – Cassatt Active Response platform enables administrators to set policies to power physical and virtual servers safely on and off and pool their computing resources.
• Cloud Switch-  Migrate your existing enterprise applications to the cloud simply and securely, without re-architecting the application or changing your management tools
• Cordys - Cordys is a software company providing a unified cloud platform solution based on Service-oriented architecture,
• Capgemini G Cloud – Capgemini running a pilot for a Government Cloud
• Cloud City - CloudCityHosting.com specializes in solutions for small business that leverage today’s emerging Cloud hosted software technologies.
• CloudHan - Cloud tech and infrastructure consultant, in China.
• CloudScale Networks – Cloud enabler.  Currently in private ALPHA only
• Hexagrid Computing – IaaS software that easily allows service providers and enterprises to build private/public IaaS clouds
• HP ePrint Cloud -web-enabled printing solutions designed for the cloud that will, for the first time, allow people to: Print from any email device to any new ePrint-enabled printer from anywhere in the world through the new HP ePrint platform and store documents or files in the cloud and print direct when needed.

• Joyent – Cloud Infrastructure (Accelerators), and consulting for developers and enterprise.
• nScaled, Inc – Cloud related services such as Migrations, Deployment, Planning, Consulting
• OneLogin – Single sign-on and identity management for cloud-based apps
• Q-layer - provides software for data centres that enables cloud computing, support VSAN, VLAN, VPDC, currently support VMware ESX.
• Intalio – private cloud provider
• Skytap - IaaS service optimized for QA, Training, Demo, and Ops Testing. Supports VMware, Xen hypervisors & Windows, Linux & Solaris OS guests.
• Webscale Solutions – IT Strategy and Consulting on Cloud computing. Specialize in ROI investigations of CC. a CC provider evaluation framework and Enterprise Cloud Roadmap development.
• Windows Azzure – The Windows Azure platform offers a flexible, familiar environment for developers to create cloud applications and services.

List of Cloud computing infrastructure provider:

• Agathon Group – Cloud provider. Services include highly available VPS, virtual private datacenters and ready-to-use LAMP stacks. Self-service ordering. Custom development and managed services available.
• Amazon Web Services – Amazon EC2/S3 (Hardware-a-a-S & Cloud Storage)
• CohesiveFT – CohesiveFT Elastic Server Factory – Webservice for assembling full application stacks (contextualization, custom apps, middleware, on top of base configs) with deployment to many virtual and cloud environs.
• ElasticHosts – UK-based instant, on-demand servers in the cloud
• Flexiscale – Another instant provider of web servers with some advanced features like auto-scaling coming soon.
• GoGrid – instant, on-demand servers offering “control in the cloud”. Deploy Windows/Linux servers via web-interface in minutes
• GridLayer – Cloud Provider.  A service by Layered Technologies that delivers Virtual Private Datacenters and virtual private servers from grids of commodity servers
• LayeredTechnologies - Cloud Provider. provider of on-demand hosting and cloud and utility computing solutions through its brand GridLayer
• ReliaCloud – Deployed within a robust and resilient virtualization environment and architected to maximize uptime and performance. Free benefits include high availability, load balancing, robust APIs, and persistent servers.
• Mosso – Rackspace’s cloud hosting service
• Newservers – Instant provisioning of web servers either Windows or Linux
• Plura Processing – On-demand infrastructure for high-performance computing

List of Cloud computing Paas provider:

• Aptana Cloud -  Elastic Elastic Application Cloud™ featuring fully stacked and integrated PHP app engines, Ajax/Jaxer app engines, and soon Ruby on Rails app engines — ready to use and ready to scale as you need it.
• Azati – Hosting platform for EC2 where popular applications are instantly deployed and application’s lifecycle is automatically managed.
• BIRT onDemand – BIRT onDemand is a Platform as a Service (PAAS) offering from Actuate, which enables users to host their BIRT-based data visualization apps on their hosted, cloud based platform.
• Bungee Connect - Provides end to end tools and systems required to develop, deploy and host web applications (Platform as a Service)
• cloudControl – (PaaS) Cloud development and hosting platform (Germany)
• Coherence – Oracle Coherence Data Grid for EC2 and other cloud platforms
• Force.com – Salesforce.com’s application development platform (PaaS)
• GigaSpaces – middleware for the cloud, “cloudware”
• Google AppEngine - (PaaS)Now support python
• Heroku – Ruby on Rails in their Cloud
• Morph Labs -  Fully managed, open, elastically-scalable, end-to-end deployment and delivery platform for Ruby on Rails and Java (Jetty, JRuby, Groovy and Grails) web applications. Leverages AWS, but completely abstracts details and complexities from developers.
• Intuit Partner Platform (IPP) – Platform as a Service (PaaS) from Intuit.
• Qrimp – An AJAX based PaaS
• RightScale – RightScale provides a platform and expertise that enable companies to create scalable web applications running on Amazon’s Web Services that are reliable, easy to manage, and cost less
• Stax – Java Platform as a Service

List of Cloud computing based service provider:

• CAM Solutions – Monitoring-as-a-Service(TM)
• CloudStatus- CloudEnabler. Real-time performance trending of cloud infrastructure (currently AWS).
• DATASiSAR – Cloud Computing technology based consulting & IT Services provider
• Kaavo‘s IMOD is an easy to use online application.  Cloud Computing Made Easy.
• Microsoft Mesh
• Nasstar -  SaaS provider.  Business grade Hosted Desktop service, UK market leaders.
• Nirvanix – Cloud Storage
• TrustSaaS – uptime monitoring and alerting service (‘SaaS Weather Report’) for Software as a Service (SaaS) run by an independent third party.
• UtilityStatus - Utility Computing Platform for SaaS charged in elapsed CPU time running on EC2.
• Novatium - A Managed utility computing service provider based in chennai, India.
• Quantix – A Cloud Managed Service Provider; Oracle Centric Cloud (Oracloud) & Business Continuity (RapidRecovery)

List of Semantic computing Cloud service provider:

• ThoughtExpress – Generic Enterprise Management Service based in semantics supported by semantic computing cloud to perform enterprise information processing to deliver: BPM, BI, enterprise modelling & semantic human interface without the need to program.

List of Cloud Security Consultants and Overlay Network Providers

CohesiveFT – CohesiveFT’s VPN-Cubed products are virtual firewallls, switches, hubs, and routers that are used to build overlay networks in clouds, across clouds, and to connect enterprise data centers to public clouds.

List of Cloud End-Points:

• XPack - a dedicated cloud end-point from Moderro Technologies.  A solid-state, power-saving, VESA mountable desktop appliance with custom desktop environment designed for web applications

TOGAF is an architecture framework – The Open Group Architecture Framework. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.

What is Architecture in the Context of TOGAF?

ISO/IEC 42010:2007 defines “architecture” as:

“The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.”

TOGAF embraces but does not strictly adhere to ISO/IEC 42010:2007 terminology. In TOGAF, “architecture” has two meanings depending upon the context:

1. A formal description of a system, or a detailed plan of the system at component level to guide its implementation
2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time

In TOGAF we endeavor to strike a balance between promoting the concepts and terminology of ISO/IEC 42010:2007 – ensuring that our usage of terms defined by ISO/IEC 42010:2007 is consistent with the standard – and retaining other commonly accepted terminology that is familiar to the majority of the TOGAF readership.

What Kind of Architecture Does TOGAF Deal With?

There are four architecture domains that are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support:

• The Business Architecture defines the business strategy, governance, organization, and key business processes.
• The Data Architecture describes the structure of an organization’s logical and physical data assets and data management resources.
• The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
• The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.

Architecture Development Method

The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures.

All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities.

Phases within the ADM are as follows:

• The Preliminary Phase describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles.
• Phase A: Architecture Vision describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
• Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.
• Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
• Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.
• Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.
• Phase F: Migration Planning addresses the formulation of a set of detailed sequence of transition architectures with a supporting Implementation and Migration Plan.
• Phase G: Implementation Governance provides an architectural oversight of the implementation.
• Phase H: Architecture Change Management establishes procedures for managing change to the new architecture.
• Requirements Management examines the process of managing architecture requirements throughout the ADM.

Deliverables, Artifacts, and Building Blocks

Architects executing the ADM will produce a number of outputs as a result of their efforts, such as process flows, architectural requirements, project plans, project compliance assessments, etc. The TOGAF Architecture Content Framework provides a structural model for architectural content that allows major work products to be consistently defined, structured, and presented.

The Architecture Content Framework uses the following three categories to describe the type of architectural work product within the context of use:

• A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders. Deliverables represent the output of projects and those deliverables that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape at a point in time.
• An artifact is a more granular architectural work product that describes an architecture from a specific viewpoint. Examples include a network diagram, a server specification, a use-case specification, a list of architectural requirements, and a business interaction matrix. Artifacts are generally classified as catalogs (lists of things), matrices (showing relationships between things), and diagrams (pictures of things). An architectural deliverable may contain many artifacts and artifacts will form the content of the Architecture Repository.
• A building block represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.Building blocks can be defined at various levels of detail, depending on what stage of architecture development has been reached. For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to “architectures” or “solutions”.
  • Architecture Building Blocks (ABBs) typically describe required capability and shape the specification of Solution Building Blocks (SBBs). For example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software.
  • Solution Building Blocks (SBBs) represent components that will be used to implement the required capability. For example, a network is a building block that can be described through complementary artifacts and then put to use to realize solutions for the enterprise.

The relationships between deliverables, artifacts, and building blocks are shown below

Figure: Relationships between Deliverables, Artifacts, and Building Blocks

For example, an Architecture Definition Document is a deliverable that documents an architecture description. This document will contain a number of complementary artifacts that are views of the building blocks relevant to the architecture. For example, a process flow diagram (an artifact) may be created to describe the target call handling process (a building block). This artifact may also describe other building blocks, such as the actors involved in the process (e.g., a Customer Services Representative). An example of the relationships between deliverables, artifacts, and building blocks is illustrated in Example – Architecture Definition Document .

Figure: Example – Architecture Definition Document

Enterprise Continuum

TOGAF includes the concept of the Enterprise Continuum, which sets the broader context for an architect and explains how generic solutions can be leveraged and specialized in order to support the requirements of an individual organization. The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.

An overview of the structure and context for the Enterprise Continuum is shown in Enterprise Continuum .

Figure: Enterprise Continuum

Architecture Repository

Supporting the Enterprise Continuum is the concept of an Architecture Repository which can be used to store different classes of architectural output at different levels of abstraction, created by the ADM. In this way, TOGAF facilitates understanding and co-operation between stakeholders and practitioners at different levels.

By means of the Enterprise Continuum and Architecture Repository, architects are encouraged to leverage all other relevant architectural resources and assets in developing an Organization-Specific Architecture.

In this context, the TOGAF ADM can be regarded as describing a process lifecycle that operates at multiple levels within the organization, operating within a holistic governance framework and producing aligned outputs that reside in an Architecture Repository. The Enterprise Continuum provides a valuable context for understanding architectural models: it shows building blocks and their relationships to each other, and the constraints and requirements on a cycle of architecture development.

The structure of the TOGAF Architecture Repository is shown in the diagram below

Figure: TOGAF Architecture Repository Structure

The major components within an Architecture Repository are as follows:

• The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content.
• The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository.
• The Architecture Landscape shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives.
• The Standards Information Base (SIB) captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.
• The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise.
• The Governance Log provides a record of governance activity across the enterprise.

Establishing and Maintaining an Enterprise Architecture Capability

In order to carry out architectural activity effectively within an enterprise, it is necessary to put in place an appropriate business capability for architecture, through organization structures, roles, responsibilities, skills, and processes. An overview of the TOGAF architecture capability is shown in diagram below

Figure: TOGAF Architecture Capability Overview

Establishing the Architecture Capability as an Operational Entity

Barring architecture capabilities set up to purely support change delivery programs, it is increasingly recognized that a successful enterprise architecture practice must sit on a firm operational footing. In effect, an enterprise architecture practice must be run like any other operational unit within a business; i.e., it should be treated like a business. To this end, and over and above the core processes defined within the ADM, an enterprise architecture practice should establish capabilities in the following areas:

• Financial Management
• Performance Management
• Service Management
• Risk Management
• Resource Management
• Communications and Stakeholder Management
• Quality Management
• Supplier Management
• Configuration Management
• Environment Management

Central to the notion of operating an ongoing architecture is the execution of well-defined and effective governance, whereby all architecturally significant activity is controlled and aligned within a single framework.

As governance has become an increasingly visible requirement for organizational management, the inclusion of governance within TOGAF aligns the framework with current business best practice and also ensures a level of visibility, guidance, and control that will support all architecture stakeholder requirements and obligations.

The benefits of architecture governance include:

• Increased transparency of accountability, and informed delegation of authority
• Controlled risk management
• Protection of the existing asset base through maximizing re-use of existing architectural components
• Proactive control, monitoring, and management mechanisms
• Process, concept, and component re-use across all organizational business units
• Value creation through monitoring, measuring, evaluation, and feedback
• Increased visibility supporting internal processes and external parties’ requirements; in particular, increased visibility of decision-making at lower levels ensures oversight at an appropriate level within the enterprise of decisions that may have far-reaching strategic consequences for the organization
• Greater shareholder value; in particular, enterprise architecture increasingly represents the core intellectual property of the enterprise – studies have demonstrated a correlation between increased shareholder value and well-governed enterprises
• Integrates with existing processes and methodologies and complements functionality by adding control capabilities

Using TOGAF with Other Frameworks

Two of the key elements of any enterprise architecture framework are:

• A definition of the deliverables that the architecting activity should produce
• A description of the method by which this should be done

With some exceptions, the majority of enterprise architecture frameworks focus on the first of these – the specific set of deliverables – and are relatively silent about the methods to be used to generate them (intentionally so, in some cases).

Because TOGAF is a generic framework and intended to be used in a wide variety of environments, it provides a flexible and extensible content framework that underpins a set of generic architecture deliverables.

As a result, TOGAF may be used either in its own right, with the generic deliverables that it describes; or else these deliverables may be replaced or extended by a more specific set, defined in any other framework that the architect considers relevant.

In all cases, it is expected that the architect will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise. This architecture tailoring may include adopting elements from other architecture frameworks, or integrating TOGAF methods with other standard frameworks, such as ITIL, CMMI, COBIT, PRINCE2, PMBOK, and MSP.

As a generic framework and method for enterprise architecture, TOGAF also complements other frameworks that are aimed at specific vertical business domains, specific horizontal technology areas (such as security or manageability), or specific application areas (such as e-Commerce).

TOGAF Document Categorization Model

A TOGAF document categorization model exists to structure the release management of the TOGAF specification. It is not intended to serve as an implementation guide for practitioners.

Within the model, the content of the TOGAF document is categorized according to the following four categories:

• TOGAF Core consists of the fundamental concepts that form the essence of TOGAF.
• TOGAF Mandated consists of the normative parts of the TOGAF specification. These elements of TOGAF are central to its usage and without them the framework would not be recognizably TOGAF. Strong consideration must be given to these elements when applying TOGAF.
• TOGAF Recommended consists of a pool of resources that are specifically referenced in TOGAF as ways in which the TOGAF Core and Mandated processes can be accomplished (e.g., the SEI Architecture Trade-Off Analysis Method or business scenarios).
• TOGAF Supporting consists of additional resources that are not referenced in the other three TOGAF categories itself but provide valuable assistance.

Is the cost of SANs for your virtual servers holding you back? Want higher availability storage for your virtual servers but lack the budget and room for an external SAN system?

The HP LeftHand P4000 Virtual SAN Appliance Software creates a virtual storage node using resources that already exist inside your virtual servers. These nodes can be clustered together to transform your existing server storage into a clustered storage system that is managed as a single SAN. This allows you to use all VMware ESX advanced features that need shared storage such as VMware HA, VMotion, DRS, and SRM. You can use the P4000 VSA to cluster disks from multiple servers without disruption and add more as needed. The P4000 VSA is a VMware certified compatible SAN/Storage device customers can count on. Installed easily on any VMware ESX server, the P4000 VSA combines server virtualization and SAN on the same server platform and is fully integrated with HP LeftHand P4000 SAN Solutions.

Features & Benefits

HP LeftHand P4000 Virtual SAN Appliance Software

1. Gain the benefits of a SAN without requiring a physical SAN infrastructure
a. Provides shared storage for VMware ESX environments leveraging your server’s current disk storage
b. Enables VMware advanced features: HA, VMotion, DRS, SRM
c. Scalable without disruption
d. VMware certified compatible SAN/storage device
2. Easy to deploy and use
a. Installs easily on any VMware ESX server with few system requirements
b. Effective for test and development environment
3. P4000 VSA is fully integrated with the HP LeftHand P4000 SANs
a. Offers cost effective disaster recovery and virtual SAN to physical SAN replication that is fully compatible/certified with VMware SRM
b. Use VSA environments as cost-effective tiered storage

1. The Business Architecture defines the business strategy, governance, organization, and key business processes.
2. The Data Architecture describes the structure of an organization’s logical and physical data assets and data management resources.
3. The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
4. The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.

What is differences between TOGAF 8 and TOGAF 9

Features that are common to TOGAF 8 and TOGAF 9

• The business rationale for Enterprise Architecture and TOGAF
• The TOGAF Architecture Development Method and its deliverables, including Business, Data, Applications and Technology Architecture
• The Enterprise Continuum
• Enterprise Architecture Governance
• Architecture Principles and their development
• Architecture Views and Viewpoints
• Requirements Engineering using Business Scenarios
• Architecture Maturity Assessments
• Architecture Skills Framework
• An Introduction to Building Blocks

Features added in TOGAF 9

• Architecture Partitioning
• Content Framework and Meta Model
• Capability Based Planning
• Business Transformation Readiness
• Using TOGAF to develop Security Architectures
• Architecture Repository
• Using TOGAF to develop SOAs

I am a certified TOGAF Practitioner and has reviewed many Enterprise Architecture Frameworks.  TOGAF 9 is revision of TOGAF 8 with new concepts such as

Modular Structure

One focus of TOGAF 9 development has been to ensure that the specification content is structured in a modular way. The modular seven-part structure of TOGAF allows for the concepts in each part to be developed with limited impacts on other parts. Content that was contained within the TOGAF 8.1.1 Resource Base has been classified and moved into parts that have a defined purpose (as opposed to generic “resources”).

The modular structure in TOGAF is intended to support greater usability, as each part has a defined purpose and can be read in isolation as a stand-alone set of guidelines. The modular structure is also expected to support incremental adoption of the TOGAF specification. Finally, the modular structure supports more sophisticated release management of the TOGAF specification. In future, individual parts may evolve at different speeds and the current specification structure is intended to allow changes in one area to take place with limited impacts across the specification.

Content Framework

A significant addition of new content to the TOGAF specification is the content framework. The TOGAF content framework provides a detailed model of architectural work products, including deliverables, artifacts within deliverables, and the architectural building blocks that artifacts represent. The intention of including a content framework within TOGAF is to drive greater consistency in the outputs that are created when following an Architecture Development Method (ADM).

The benefit of including a content framework applies at a number of levels. Firstly, within a single architecture development initiative the content framework provides a comprehensive checklist of architecture outputs that could be created and consequently reduce the risk of gaps within the final architecture deliverable set.

The second major benefit of inclusion of a content framework applies when attempting to integrate architectural work products across an enterprise. The content framework is intended to be adapted and then adopted by an enterprise in order to mandate standard architectural concepts, terms, and deliverables. If all architecture initiatives use the same models for content, their outputs can be combined much more easily than in situations where each architect uses a completely different approach.

Finally, a substantial benefit of the inclusion of a content framework within TOGAF is that it provides (for the first time) a detailed open standard for how architectures should be described. The existence of this standard allows tools vendors, product vendors, and service vendors to adopt consistent ways of working, which in turn will result in greater consistency between architecture tools, better tool interoperability, more consistent reference architectures, and better comparability between related reference architectures.

Extended Guidance on Adopting TOGAF within an Enterprise

Within larger organizations, the practice of enterprise architecture requires a number of individuals and teams that work together on many architectures. Although each architecture will address a specific problem, in an ideal situation architectures can be considered as a group in order to develop an overall integrated view of how the enterprise is changing.

This version of TOGAF features an extended set of concepts and guidelines to support the establishment of an integrated hierarchy of architectures being developed by teams that operate within an overarching architectural governance model. In particular, the following concepts are introduced:

• Partitioning: In order to develop architectures that have manageable levels of cost and complexity, it is necessary to partition the enterprise into specific architectures. TOGAF discusses the concept of partitioning and provides a variety of techniques and considerations on how to partition the various architectures within an enterprise.
• Architecture Repository: TOGAF provides a logical information model for an Architecture Repository, which can be used as an integrated store for all outputs created by executing the ADM.
• Capability Framework: This version of TOGAF provides a more structured definition of the organization, skills, roles, and responsibilities required to operate an effective enterprise architecture capability. The new TOGAF materials also provide guidance on a process that can be followed to identify and establish an appropriate architecture capability.

Explicit Consideration of Architectural Styles, Including SOA and Security Architecture

The new “ADM Guidelines and Techniques” brings together a set of supporting materials that show in more detail how the ADM can be applied to specific situations. The new guidelines discuss:

• The varying uses of iteration that are possible within the ADM and when each technique should be applied
• The linkages between the TOGAF ADM and Service Oriented Architecture (SOA)
• The specific considerations required to address security architecture within the ADM
• The various types of architecture development required within an enterprise and how these relate to one another

Additional ADM Detail

This version of the TOGAF specification includes more detailed information supporting the execution of the ADM. Particular areas of enhancement are:

• The Preliminary phase, which features extended guidance on establishing an enterprise architecture framework and planning for architecture development. The extended Preliminary phase also provides pointers to the definition of a governance model for architecture benefit realization and also discusses the linkage between TOGAF and other management frameworks.
• The Opportunities & Solutions phase and Migration Planning phase, which feature a more detailed and robust method for defining and planning enterprise transformation, based on the principles of capability-based planning.

The Benefits of TOGAF 9

TOGAF 9 provides a wide-ranging set of revisions to the TOGAF specification. When combined, these edits seek to achieve a set of objectives to improve the value of the TOGAF framework.

Greater Usability

A number of enhancements within TOGAF 9 support greater usability of the overall specification. Firstly, the modular structure of the specification makes it easier for an architect to consider a specific aspect of the architecture capability. In all areas, the specification seeks to add detail and clarity above and beyond previous TOGAF versions.

More Focus on Holistic Enterprise Change

TOGAF has a solid history in IT architecture, considering the ways in which IT can support enterprise change. However, as TOGAF has grown in depth and maturity it has become a framework for managing the entire spectrum of change required to transform an enterprise towards a target operating model. TOGAF 9 continues this evolution and incorporates a broader perspective of change that allows enterprise architecture to be used to specify transformation across the business, data, application, and technology domains.

More Consistency of Output

Previous versions of TOGAF focused on providing a consistent process for developing architectures. TOGAF 9 includes a greatly enhanced consideration of architectural work products to ensure that a consistent process is used to produce consistent outputs. The Architecture Content Framework provides a detailed model of the outputs to be created by the ADM. Additionally, the Enterprise Continuum, Architecture Partitioning, and Architecture Repository sections provide detailed guidance on how architectural deliverables can be scoped, governed, and integrated.

GEAS is a combination of our patented Agile RightStep® EA methodology and a well defined tool methodology that together encompasses seven key capabilities that are deployed based on the particular client environment and the client’s level of organizational EA maturity. Each of the seven key capabilities comprising GEAS are described below:

• Capture – Gathers information about the enterprise including mission, vision, goals, applications and supporting IT
• Compilation – Extracts, transforms and populates the repository with information
• Presentation – Depicts the architecture in a manner that is appropriate to the audience, providing EA data for management decision making
• Repository – Places the EA model and related artifacts under configuration management in a secure repository
• Analyse – Provides the ability to search and evaluate the EA information stored in the repository using the analysis engine to support business decisions (for example, the prioritization of IT initiatives/spend relevant to impact on the business mission of the organization)
• Hosting – A secure, managed environment containing the repository with the models comprising the EA; can be performed by the client or outsourced to us as part of the EA services
• Sustaining – The processes necessary for ongoing support, updating and integration of the EA into the day-to-day business operations of the enterprise

GEAS leverages two EDS’ offerings/capabilities including:

• Agile RightStep® – Our patented, time-tested EA methodology with a 10+ year record of success is used in the capture, compilation, analysis and presentation module.
• Organizational Change Management – Provides a government agency with the support necessary to successfully implement the desired “to be” business processes and corresponding IT systems/applications

Benefits

• Cornerstone of GEAS is RightStep®
• Sustainable Architecture
• OMB 300 Forms Integration
• OMB Guideline Conformance

I have worked for a number of blue chip clients and IT Outsourcing companies such as Capgemini, Fujitsu Services, EDS, and now HP. I gained experience in industries such as Manufacturing, Banking, Telco, Utilities,  and Government departments.

I am a Chartered IT Professional recognised and awarded by BCS (British Computer Society) with certifications such as SNIA Certified Architect (Storage Networking Industry Association) , and TOGAF certified Practitioner.

I am an IT Architect who has breadth of experience in Security, Virtualisation, Infrastructure Architecture, Service Architecture, Enterprise Architecture,ITIL Processes, TOGAF, Zachman, EDS RightStep, CEnterprise Frameworks.  Enterprise Architecture to include requirements gathering, application / mapping of the Business requirements, functional and non functional requirements to the overall Architecture, ITIL Mapping to Managed Services and SLA, Conceptual designs, Sales support, Contract Mapping to Service Delivery

I am an outstanding communicator and networker, whose personal focus is to deliver projects to a very high quality on time and to budget. I am equally effective working independently or as part of a team. I am comfortable interfacing at all levels including technical staff, customers and senior management. I have excellent oral and written communication skills, and passionate in Infrastructure Technology and Architecture; and how it fits within the “big Picture” to add most business value.

I love public speaking and take an active interest in mentoring people in IT. I am also a Safe Neighbourhood Watch Coordinator of my area and do regular meetings with the residents on crime, neighbourhood issues, and dealing with the local Police and local Council. I enjoy meeting people, playing football, and socialising.