( en | de | ru )

 

  2. user
  3. @cschie
  4. enterprise

bookmarks  33

  •  

    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.
    16 years ago by @cschie
     
      ITTOGAFalalignmentarchitecturecomplexityenterprise
      (0)
      copydelete
       
       
    •  

      In the book The Art of War for Executives, Donald G. Krause interprets the following: “Sun Tsu notes, superior commanders succeed in situations where ordinary people fail because they obtain more timely information and use it more quickly.” For metadata professionals, this observation is increasingly relevant as more and more of the business seeks integration and federation, alignment with business goals and strategies, and agility - the ability to respond both quickly and accurately to change. Industry analysts and IT professionals are less focused on solutions to problems where metadata management plays a role but rather look more to metadata management as an overall strategy for the benefits it provides to multiple aspects of the whole organization.
      16 years ago by @cschie
       
        architecturedataenterpriseinformationmodeling
        (0)
        copydelete
         
         
      •  

        sensitive
        16 years ago by @cschie
         
          EAenterprisearchitectureCIOmanagement
          (0)
          copydelete
           
           
        •  

          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.
          16 years ago by @cschie
           
            summaryenterprisearchitectureTOGAF
            (0)
            copydelete
             
             
          •  

            Open source is ready for EDW. Because open source is designed to be modular, an enterprise can start with one piece - say ETL or reporting - and can add on as needed. For comparable power and features an open source solution in this arena can cost 10 to 20 times less than a proprietary product. Whether large or small, companies today are being asked to do more with less. With open source, you can have an EDW without compromise.
            16 years ago by @cschie
             
              EDWETLdataenterpriseopenreportingsourcewarehousing
              (0)
              copydelete
               
               

            publications  14  

            • ⟨⟨
            • ⟨
            • 1
            • ⟩
            • ⟩⟩