Sunday, December 2, 2012

EA Tools and Cost



The availability of useful EA tools is critical to the approach to EA. It facilitates and enables the development, storage and presentation of the work. When selecting proper EA tools, there are many factors that need to be considered.(Factors listed in Enterprise Architecture Tool Selection Guide,Institute for Enterprise Architecture Developments)

  • Enterprise Architects
  • Solution Architects
  • Strategic Planners / Management
  • Enterprise Program Managers
  • Software Architects / engineers
  • External Partners


The modeling language differs in ability, flexibility to express the relations among different domains in the architect and to explain the processes of business and information usage.
orbussoftware.com

A wide variety of organization and process modeling languages are currently in use, among which the popular ones are: (According to Institute for Enterprise Architecture Developments)


  • The Business Process Modeling Notation (BPMN) is a standard for business process modeling, and provides a graphical notation for specifying business processes in a Business Process Diagram (BPD), based on a flowcharting technique very similar to activity diagrams from Unified Modeling Language (UML). The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics.
  • IDEF originating from the US Ministry of Defense is a collection of 16 (unrelated) diagramming techniques, three of which are widely used: IDEF0 (function modeling), IDEF1/IDEF1x (information and data modeling) and IDEF3 (process description).
  • ArchiMate as an Enterprise Architecture modeling language, originally developed as an initiative of a consortium of Dutch organizations and the Telematica Institute, today ArchiMate is part of the Open Group set of Standards.

Business/ IT Alignment



Some insiders at the ZDNet community, talked about their views on B/ I alignment:
John Bagdanov: "The bottom line is IT has to develop healthy working relationships with the business units and the executive office. You have to gain their respect and demonstrate you’re commitment to their success."
Vratislav Paulik: "Business/IT alignment has multiple dimensions, but I would like to focus on the most important one – strategic alignment. Balanced scorecard is a very good tool here. You include IT in the company strategic planning and ensure that the IT strategy is aligned with the business one in all the four balanced scorecard views – financial, customer, quality and employee. On the high level it means that the company objectives are cascaded down to IT in all the four areas, so that IT works in the company’s direction."
Besides EA activities, IT project management activities are frequently involved in B/ I alignment, such as risk management and project control activities.

Wikipedia:
In the Risk3[4] model, the objective of B/I Alignment is to manage three separate risks associated with IT projects: technical risk (will the system function as it should?), organizational risk (will individuals within the organization use the system as they should?), and business risk (will the implementation and adoption of the system translate into business value?). Business value is jeopardized unless all three risks are managed successfully.
topdeskmagazine.com




Info from www.isaca.org Business/ IT Alignment Overview

Establish processes of bi-directional education and reciprocal involvement in strategic planning to achieve business and IT alignment and integration. Mediate between business and IT imperatives so priorities can be mutually agreed.


Value Drivers
  • IT aligned with the organisation’s mission and goals
  • IT enabling the achievement of the strategic business objectives
  • Optimised return on IT investment
  • Opportunities for innovation identified and exploited

Risk Drivers
  • IT seen as a cost factor
  • The enterprise’s mission not being supported by its IT
  • IT management decisions not following the business direction
  • Lack of common understanding of business and IT priorities, leading to conflicts about allocation of resources and priorities
  • Missed opportunities to exploit new IT capabilities
  1. Ensure that IT informs enterprise management and key stakeholders on the current technology environment, possible future trends and value opportunities for the business.
  2. Ensure that enterprise management and key stakeholders discuss with IT management future business directions and enterprise goals to collaborate and develop a common understanding of the potential for IT to enable business goals.
  3. Ensure that IT management contributes to business strategy planning and identifies capabilities available to support enterprise goals and other opportunities to contribute to business value.
  4. Make the scope of the IT strategic and planning initiatives enterprisewide such that they address, document and consider all business and support activities.
  5. Ensure current and future business and IT alignment by:
    • Technology creating opportunities that the business can turn into enterprise benefits
    • Involving IT management in the development of enterprise goals to recognise opportunities and current capability limitations
  6. Align business imperatives and priorities with IT capabilities to establish enterprise priorities for inclusion in the IT strategic plan.
  7. In conjunction with business representatives, document a prioritised list of business products, services and processes that are critically dependent on IT.