background preloader

TOGAF® 9.1

TOGAF® 9.1

Related:  Architecture Générale

HATEOAS The HATEOAS constraint decouples client and server in a way that allows the server functionality to evolve independently. Details[edit] A REST client enters a REST application through a simple fixed URL. All future actions the client may take are discovered within resource representations returned from the server. The media types used for these representations, and the link relations they may contain, are standardized. The Open Group Architecture Framework Structure of the TOGAF Architecture Development Method (ADM).[1] The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture.[2] TOGAF has been a registered trademark of The Open Group in the United States and other countries since 2011.[3] TOGAF is a high level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology.

A Comparison of the Top Four Enterprise-Architecture Methodologies Roger Sessions ObjectWatch, Inc. May 2007 Applies to: Enterprise Architecture TOGAF or not TOGAF: Extending Enterprise Architecture beyond RUP Develop and deploy your nextapp on the IBM Bluemixcloud platform. Start your free trial When provided with a problem statement or pointed to a specific user need, a project team equipped with the IBM Rational Unified Process® (RUP®) approaches a solution by creating a Business Case, a Vision statement, and a Software Requirements Specification among other artifacts. These work products and the activities that produce them are well understood within both the technical and business communities. However, the ways in which we conceptualize, prioritize, and select which business problems and user needs to implement in software remains a highly variable process throughout our industry. This article explores the maturing and increasingly important role of enterprise architecture (EA) frameworks for today's software development organizations.

Zachman Framework The Zachman Framework of enterprise architecture The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes.;[2] rather, it is an Ontology whereby a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) is used to take into account both whom the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed.[3] The framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since.[4]

Enterprise Architecture Links, Institute For Enterprise Architecture Developments (IFEAD) Via Nova Architectura website The field of architecture is alive and kicking. New regulations, globalization and the extended enterprise make the need for architectural thinking and acting even more evident than it already was. With this increasing need for architecture the need for the exchange of ideas, best practices, research and methods among architects is growing too.

The Open Group's Architect Certification Programs by Leonard Fehskens Contents IntroductionThe Open Group Architecture FrameworkA New IT Architect CertificationAccredited Certification ProgramsBoard Review Certification ProcessRequirementsRecertificationBenefits of CertificationMore Information Introduction How do you know if someone is really an architect? This has become an increasingly important question as the context and nature of information systems have evolved into their present forms. UML, RUP, and the Zachman Framework: Better together Over the past decade, the advantages of using the Unified Modeling Language (UML) for modeling software applications have become clear. During this same timeframe, the Rational Unified Process, or RUP, has proved itself as a software development process, and the Zachman Framework1 has proved itself as a framework for organizing and communicating architectural artifacts. Amid the swarm of overlapping methodologies, these stand apart as three pillars of modern information systems architecture. This article considers the combined usages of these technologies by examining their meta-characteristics and proposing some ways to apply them in combination within organizations. UML, RUP, and Zachman in brief

The role of the Solution Architect during the implementation In my previous article I describe the role of the Solution Architect within the TOGAF ADM, mostly acting between phases E to G, with a specific focus on E (Opportunities and Solutions) and F (Migration Planning). This article will cover the role in phase G: Implementation governance. The objective of that phase is to formulate recommendations for each implementation project, and govern and manage an architecture contract covering the overall system implementation and deployment. In companies where the maturity is high, it would be perfectly acceptable to have the Solution Architect acting in the name of the Enterprise Architecture team and coordinate activities during the phase G. TOGAF defines objectives during that phase and each of them may be detailed as follows. ► To formulate recommendations for each implementation project (Source: TOGAF 9)

Information Technology Infrastructure Library ITIL (formerly known as the Information Technology Infrastructure Library) is a set of practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business. In its current form (known as ITIL 2011 edition), ITIL is published as a series of five core volumes, each of which covers a different ITSM lifecycle stage. Although ITIL underpins ISO/IEC 20000 (previously BS15000), the International Service Management Standard for IT service management, the two frameworks do have some differences. ITIL describes processes, procedures, tasks, and checklists which are not organization-specific, but can be applied by an organization for establishing integration with the organization's strategy, delivering value, and maintaining a minimum level of competency. It allows the organization to establish a baseline from which it can plan, implement, and measure.

I passed the TOGAF cert, and all I got was this lousy piece of paper… Fog a mirror? Check. Study and pass the TOGAF certification? Check. Congratulations, you are now an architect. Wait, what? Generating Value Through Strategic Architecture Old News. Long Shorts. Jumbo Shrimp. Agile EA. What’s the common thread?? BPM - Closing the Loop I wanted to lay down the components of a typical BPM system and how they all work together to provide the concept of process management to the organization. Business Process Management is both a business and a technology concept depending upon the perspective and roles we perform in an organization. In this post, I want to target the operational and technical aspects of what constitutes within the realm of BPM. Operationally speaking Business Process Management is all about achieving efficiency and efficacy for the organization.

Related:  LEARNEnterprise Architecture