February 2004 - Posts

• Exposing the Core Functionality of an Enterprise Architecture

  The enterprise architecture team is responsible for exposing core functionality in ways that support the application teams. But how is that best done? I would like to propose a combination of 3 approaches: * Registration al la COM+ * Enterprise components Read More... Posted Sunday, February 29, 2004 10:57 PM by Stcohen | 0 Comments Filed under: Architecture

• Building enterprise worthy parts from Microsoft pieces

  I spent the last week working on a proof of concept for a very large customer. They wanted to build a service oriented software infrastructure to be used across many well known, and all possible future, applications. The principle goal is to provide safety Read More... Posted Saturday, February 28, 2004 4:13 PM by Stcohen | 8 Comments Filed under: Architecture

• The slippery slope of enterprise architecture definition

  Step with me if you will onto the slippery slope of enterprise architecture definition. I try to capture the boundaries of the enterprise in a single simple layered boxes-and-lines diagram. Relationships are conveyed through adjacency and separation helps Read More... Posted Tuesday, February 24, 2004 8:28 PM by Stcohen | 1 Comments Filed under: Architecture, MSF

• On safari for the ever elusive enterprise definition

  Two skills have served me well while gathering information about an enterprise. First, the lessons it has been my pleasure to have learned from my customers and the many, many, bright practioners I have been lucky enough to work with. Second, the ability Read More... Posted Saturday, February 21, 2004 1:15 PM by Stcohen | 2 Comments Filed under: Architecture, MSF

• It is the use of a product, not the content, which drives the selection of a specific model or artifact.

  Enterprise architecture products are decomposed into two primary categories; Inward facing products guiding or documenting the activities of the enterprise architecture program, or Outward facing products used to facilitate discovery and communicate the Read More... Posted Tuesday, February 17, 2004 8:15 PM by Stcohen | 0 Comments Filed under: Architecture

• How do we define the scope of an enterprise?

  How big is your enterprise? It turns out to be a very difficult question to answer. Consider this simple scenario; You have a newspaper delivery route. Your supplier pays you as a contractor. You receive the newspapers each morning from another independent Read More... Posted Sunday, February 15, 2004 10:38 PM by Stcohen | 1 Comments Filed under: Architecture, MSF

• As-is vs. To be

  Many discussions of how-to-do architecture talk about modeling the domain 'as-is' then defining the 'to-be' state. In general I agree, clearly defining the problem before identifying the solution is a risk mitigation technique. By focusing on the current Read More... Posted Saturday, February 14, 2004 12:51 PM by Stcohen | 0 Comments Filed under: Architecture, MSF

• Enterprise Architectural Guidance, policy, and law

  I believe that enterprise architecture more closely resembles social structures than physical structures and enterprise architects are more closely related to the authors of the declaration of independence than structural engineers. This is a key differentiator Read More... Posted Thursday, February 12, 2004 6:28 PM by Stcohen | 0 Comments Filed under: Architecture

• Enterprise Architecture must provide direct value

  Enterprise Architects face many directions at once and the deliverables are intended to help with the various lines of communication. * The models help aid the validation and discovery phase with the stakeholders and later provide a well known visualization Read More... Posted Wednesday, February 11, 2004 5:58 PM by Stcohen | 8 Comments Filed under: Architecture

• my definition of Enterprise Architecture

  When you speak to a traditional architect you are likely to hear about defining a space optimized by the structure for an intended use. Oddly, we in the software architecture world rarely discuss the space. Instead we focus on the activities of the product Read More... Posted Tuesday, February 10, 2004 8:48 PM by Stcohen | 0 Comments Filed under: Architecture

• Enterprise Architecture - top down and bottom up

  Generally the success of an individual project has been determined by how well its requirements were met. However the larger enterprise is better served if great care was taken to determine what will be "best" for the enterprise and how the individual Read More... Posted Tuesday, February 10, 2004 11:28 AM by Stcohen | 0 Comments Filed under: Architecture

• Enterpise Architecture and cross project intergration

  In an enterprise where architecture defines more than standards but creates governance so that many projects work together over time, cross project integration is much more a mandate than a target of opportunity. Consider the need for a cohesive identity Read More... Posted Tuesday, February 10, 2004 11:27 AM by Stcohen | 0 Comments Filed under: Architecture

• Shredding Requirements

  I spent most of yesterday going through 60+ verbose PowerPoint slides and 45 pages of detailed requirements. You see I have a customer who has run into several issues rooted in their initial design considerations. They are a CMM level 3 organization with Read More... Posted Tuesday, February 10, 2004 10:58 AM by Stcohen | 4 Comments Filed under: Architecture, MSF