Does SaaS diminish the need for enterprise architecture? This is a good question, but we have to understand what is meant by Enterprise Architecture (EA).

It is generally accepted to be a discipline and sometimes that strategically aligns an organization to its technology and business goals.

Activities such as Enterprise Architecture Planning (EAP) serve this need and are essential to IT Governance. Other activities relate to the application of Enterprise Architecture to specific domains, such as Line of Business (LOB) portfolios, Technical Architecture (which may include networking, security, etc.) and Application Architecture.

So, given this definition–YES, EA is essential because even (or perhaps especially) if the applications and business processes leave the enterprise four walls (ala SaaS), planning and governance are needed to ensure alignment to strategic goals.

The role of EA is to periodically adjust those long term goals and the trajectory to attain them in response to changing technologies, business drivers, etc.

So as new paradigms like SaaS and other types of Cloud Computing emerge, EA must evaluate them and establish standards, guidelines, policies, etc.

For example, EA may incorporate SaaS based on cost benefit and an assessment that recognizes SaaS applications as being aligned to enterprise needs for security, privacy, compliance, service level, business function, etc.

And in addressing whether there is a need to architect solutions when adopting SaaS (presumably in support of EA as a discipline), then YES, there is still a critical need to define how SaaS integrates with the enterprise technology landscape.

Questions such as what is the master of my data? How do I manage Identities and Accounts? How do I produce Compliance Reporting? How do I migrate to/from adopted and sunset SaaS Apps? How do I establish Trust Relationships? How do I provide Quality and Service to my constituencies? etc.

These issues require solutions in the domains of Information Architecture, Security Architecture, Network Architecture, Application Architecture, Technical Architecture and so on–presumably envisioned and vetted by architects of various types (including Portfolio Architects, Solutions Architects, etc.)

So while the GAME may have changed, the need for the PLAYERS has not. Architecture–in all senses of the word–remains essential.

In closing I will say that SaaS pushes the emergence of Business Architecture to a new height because of the direct empowerment of LOB owners.

Acquisition and deployment of real solutions is now within grasp of business owners (seemingly) without the need for conventional IT delivery and support.

But many of the above questions may go unanswered without engagement of EA, and latent risks (such as compliance and security) may turn into real issues.

Coby Royer has over 20 years technology experience in software and security start-ups, consulting, and large enterprises. He has served roles in software development, enterprise architecture, and management, in lines of business that include Internet security, commercial software, financial services, consumer goods, e-commerce, and expert systems.