bookmarks  13

  •  

    Enterprise architecture is a management practice that was initially developed within the IT discipline to manage the complexity of IT systems, as well as the ongoing change constantly triggered by business and technology developments. Today, one of the primary reasons EA is adopted in organizations worldwide is to promote alignment between business requirements and IT solutions. EA is expanding into other business disciplines, as well: to enable business strategy development, improve business efficiency, facilitate knowledge management and assist with organizational learning, to name a few. In order to effectively implement EA in organizations, architects are increasingly looking for best practices and frameworks to assist them. One of the few architecture frameworks publicly available to guide architects in their implementation is TOGAF. Put simply, TOGAF is a comprehensive toolset for assisting in the acceptance, production, use and maintenance of enterprise architectures. It is based on an iterative process model supported by best practices and a reusable set of existing architectural assets. Since it was developed by members of The Open Group Architecture Forum more than 10 years ago, TOGAF has emerged as arguably the de facto standard framework for delivering enterprise architecture.
    15 years ago by @cschie
    (0)
     
     
  •  

    One common problem I see in the IT industry is the qualification of IT decisions. I talk to architects from all around the world and hear a lot of creative and innovate ways of solving problems. More often than not, what I don’t hear is more concerning. When I have asked: Why did we approach the problem in this manner? How does this align to the business? Does this fulfill the business, functional and non-functional requirements Why is this the optimal architecture? Obviously there are a lot of other questions, but to keep this concise above are some sample questions. The last question is particularly interesting. I have heard  a broad range of fluffy answers such as: “trust me, I know what I am doing”, “I have been doing this for 20 years, I know how to do this”, “I am the expert of [X]”. All of these responses may be completely true but doesn’t quantify the solution. It doesn’t demonstrate that there was a process or a clear level of due diligence that was performed.
    15 years ago by @cschie
    (0)
     
     
  •  

    TOGAF defines "enterprise" as any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership. The term "enterprise" in the context of "enterprise architecture" can be used to denote both an entire enterprise - encompassing all of its information and technology services, processes, and infrastructure - and a specific domain within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise. Confusion often arises from the evolving nature of the term "enterprise". An extended enterprise nowadays frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units. The business operating model concept is useful to determine the nature and scope of the enterprise architecture within an organization. Large corporations and government agencies may comprise multiple enterprises, and may develop and maintain a number of independent enterprise architectures to address each one. However, there is often much in common about the information systems in each enterprise, and there is usually great potential for gain in the use of a common architecture framework. For example, a common framework can provide a basis for the development of an Architecture Repository for the integration and re-use of models, designs, and baseline data.
    15 years ago by @cschie
    (0)
     
     
  •  

    As the link between business and IT strategy, the enterprise architecture outlines the framework for IT solutions. The EA describes IT structures, standards, processes and shared corporate services. The task of an EA is to support the business areas and IT experts in shared planning processes and in the comprehensive further development of the IT architecture. Detecon decided to use TOGAF from Open Group as an open and widely accepted standard as basis for our architecture work. A comprehensive experience from successful projects at customers with different size and industry demonstrates the benefits of that strong methodology. Based on TOGAF basic structures, Detecon enhanced the methodology in different areas, e.g. the finance and controlling, business cases, governance or SOA migration strategy, and applies those successfully. Detecon trains architects in the TOGAF framework with the following goals: To accelerate architecture development at their companies To reduce complexity in planning heterogeneous best-of-breed systems To secure the implementation of all requirements To ensure security for the future To provide a tool for improved communication of goals and strategies for business units and managers.
    15 years ago by @cschie
    (0)
     
     
  •  

    TOGAF 9 encompasses the entire enterprise architecture life cycle, which is important as architecture is a never ending journey, always changing and evolving. The figure below depicts the TOGAF Architecture Development Method (ADM) which covers the entire architecture life cycle.
    15 years ago by @cschie
    (0)
     
     

publications  

    No matching posts.
  • ⟨⟨
  • ⟩⟩