OIAm Offering: Difference between revisions

From OIAr Archive 2013
Jump to navigation Jump to search
(start)
 
(link)
 
Line 4: Line 4:
|homelink=OIAm_Introduction
|homelink=OIAm_Introduction
|homelinkname=up: table of contents
|homelinkname=up: table of contents
|fwdlink=Architecture_according_to_Blaauw
|fwdlink=Architecture workflow based on Blaauw
|fwdlinkname=next: Architecture according to Blaauw
|fwdlinkname=next: Architecture workflow based on Blaauw
|bgcolor=white
|bgcolor=white
}}
}}
Line 31: Line 31:
|homelink=OIAm_Introduction
|homelink=OIAm_Introduction
|homelinkname=up: table of contents
|homelinkname=up: table of contents
|fwdlink=Architecture_according_to_Blaauw
|fwdlink=Architecture workflow based on Blaauw
|fwdlinkname=next: Architecture according to Blaauw
|fwdlinkname=next: Architecture workflow based on Blaauw
|bgcolor=white
|bgcolor=white
}}
}}

Latest revision as of 18:50, 14 February 2013

previous : Preface up: table of contents next: Architecture workflow based on Blaauw




OIAm offering

OIAm brings business agility, architectural effectiveness and manageable and expandable infrastructure landscapes within grasp of any organization.

There are three mutually supportive key elements which OIAm provides:

  1. The definitive description of infrastructure architecture as an integral part of the architectural process, and how it can help to enforce architectural principles. There are two focal points: the need for a functional approach to infrastructure facilities, and how to select and work with the appropriate quality attributes.
  2. The Building Blocks Model (an architectural meta-model for infrastructure) which can be used to
    1. create and describe logical, modular infrastructure facilities,
    2. maintain a categorical and functional inventory of existing infrastructure landscapes, and
    3. structure and construct architectural products, like Reference Architectures, Impact Analyses and Project Start Architectures.
  3. A number of best practices to get infrastructure architecture off to a flying start within an organization, as well as guidelines for producing essential architectural artifacts which will make infrastructure architecture really work. Various implementation strategies are outlined, how to extend the Project Start Architecture is explained and the importance of a number of products such as Reference Architectures, Product Catalogs and Service Catalogs are also illustrated.

Apart from these three main ingredients, OIAm also provides guidance on how infrastructure architecture can improve security, project management, test management and production.



previous : Preface up: table of contents next: Architecture workflow based on Blaauw