You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Facets that describe Enterprise Architecture at a given institution:

 This is a start on a model for describing how Enterprise Architecture / I.T. Architecture is structured and engages with the enterprise.

Organizational Models of Enterprise Architecture

  •  Informal/ Ad hoc architecture - no formal architecture group.  Individuals acting as ad hoc architects in their areas
  • Isolated Architecture - a "more formal" architecture group but that group is buried in one department
  • Federated Architecture - Architecture deputies around campus working together to form a "enterprise architecture"
  • Head Architect with Domain Architects - like federated but with a central lead architect orchestrating the federation
  • Central Architecture - a core group of architects that review all projects in the enterprise

Other aspects that might affect positioning and organization models

  • Do you build or buy software - as a general rule is your institutions preference to build or buy
  • Do you outsource activities
  • Are you active in lots of open source projects
  • Do you have a Project Management Office
  • Do you have Portfolio Management Process

Facets that describe how you engage  (see Mark Poepping's Arch to Action document)

  • Where do you report:

    • Manager

      Director

      CIO

      Provost

  • Where is your range of effect:  Projects in

    • A group

      Department

      Multiple Deptartments

      Across Campus

      All Projects on campus

  • When do you engage with projects (based loosely on Enterprise Unified Process terminology)

    • At inception

      During Elaboration

      During Construction

      During Roll-out

      After Launch

  • Method of engagement

    • Pleading

      Recommending

      Requirements

      Project Review

      Project Gate

Organization's Operating Model

Which model most closely matches your organizations operating model (take fromEnterprise Architecture as Strategy by Ross, Weill and Robertson)

  • Distributed (few common business processes and little data integration)
  • Replicated (common business processes with little data integration)
  • Coordinated (few common business processes with high data integration)
  • Unified (common business process with high data integration)

Organizational Maturity Model

At which point in the maturity model would you say your organization is mostly at (also from EA as S)

  • Business Silos
  • Standardized Technology
  • Optimized Core
  • Business Modularity
  • No labels