Articles by Brent Carlson

SOA Governance Best Practices – Architectural, Organizational, and SDLC Implications

Sun, 29 Jan 2006 10:00:00 EST

The fact that you're reading this article means that you are probably planning a service-oriented architecture (SOA) initiative and recognize that some level of governance is required in order to be successful. If you are like most people in this position, you are also somewhat confused as to the meaning of SOA governance. Governance is the current buzzword, and combining governance with SOA creates a phrase that every independent software vendor (ISV) wants a piece of. How do you sort out what is marketing hype from what is truly valuable and relevant to your organization's SOA efforts?

WS Track - Driving SOA Governance

Wed, 15 Dec 2004 00:00:00 EST

In the past year,Web services and service-oriented architectures (SOAs) have become mainstream because of their ability to provide business agility and flexibility through integration, productivity, and reuse. With SOA enablement on the rise, IT groups must address SOA governance as a means of controlling what and how services located within an SOA are deployed.

Whitehorse

Mon, 07 Jun 2004 00:00:00 EDT

With Whitehorse, Microsoft has placed a significant stake in the ground when it comes to modeling enterprise services. While Whitehorse is part of the not-yet-released Visual Studio 2005 (codenamed 'Whidbey'), Microsoft has publicly discussed and demonstrated significant elements of Whitehorse, and alpha code is currently in use by select Microsoft customers.

Software Reuse Is Dead, Long Live Software Reuse

Fri, 09 Jan 2004 00:00:00 EST

I know what you're probably thinking as you look at the title of this article: 'software reuse - been there, done that, and it doesn't work....' And it's true that many a software architect or project leader on a WebLogic project has broken his or her pick on the slag heap of reuse efforts and that the legacy of monolithic CASE tool suites has left a bad taste in many developers' mouths when it comes to developing reusable software.

Discovering and Documenting Business Application Patterns

Tue, 15 Apr 2003 00:00:00 EDT

Over the past two months, we've looked at the process of extracting a business application pattern from a series of business requirements. You've seen this pattern take shape, from its original form as a design meeting the specific needs of a particular business application (configurable product balance information) through an initial abstraction that was modified by other business requirements to reach its final form.

Discovering and Documenting Business Application Patterns

Fri, 21 Mar 2003 00:00:00 EST

This month we'll look at pattern discovery in more detail by continuing to examine a business application pattern we discovered and documented. Our focus isn't on creating formal patterns, but on capturing, refining, and sharing the knowledge gained during development. We'll discuss the steps we went through as we discovered and captured our pattern. As we progress through the steps, we'll show you not only what we learned as we captured this pattern, but also things we learned as we captured other patterns.

Discovering and Documenting Business Application Patterns

Mon, 03 Feb 2003 00:00:00 EST

You're probably saying to yourself, 'Oh, no! Not another patterns article!' Technically, that's what this is. However, instead of simply showing you a finished pattern, we're going to look at pattern discovery. And, while what we'll talk about can help you capture fundamental patterns (that is, if there are any fundamental patterns left to be defined) we're going to focus on the capture of more workaday patterns. These are patterns that may be useful to only you and your team and might never be made into formal patterns or even shared outside of your group. In fact a pattern purist might say they aren't even patterns.

Putting Web Services into (Business) Context

Mon, 16 Dec 2002 00:00:00 EST

Web services tool vendors frequently compete on how quickly their users can 'generate a Web service from scratch' or 'expose a Java/COM+/CORBA class as a Web service.' While speed of development is important, the broader business needs of an enterprise must be the main driver of new technology adoption.