Tuesday, June 30, 2009

Social networks definitely get their fair share of hype but are they actually providing any true business value?

Assessing the business value of Web 2.0 is similar to assessing the business value of an analytical (OLAP) database in that the real value of an OLAP is not in the database itself but rather in the "knowledge" gained by analyzing the "patterns" of data within the database. Web 2.0 is the philosophy and associated web-based tools (such as twitter, linkedin, facebook, myspace, orkut, etc.) of creating a more "personalized", "humanizing" web experience. Just as in the case of an OLAP database, the real business value of Web 2.0 is neither in the philosophy nor in the toolset but in the "relationships" and personal information captured about the users that was previously unavailable in Web 1.0. Companies across the world are burning midnight oil trying to decode all of this new data about online relationships hoping to strike gold with profitable insights. Companies such as Facebook have grandiose visions about changing the way people interact over the web and even displacing Google as the "search engine" of choice. Decoding these online relationships in the sea of data within the depths of Web 2.0 could be just the keys needed to unlock unheard of riches!

Friday, June 26, 2009

Given that SOA is an architectural style rather than a product, SOA-in-a-box might be an extreme but an SOA framework can come very close to a "box" if it meets the following criteria:

Provide a comprehensive methodology from inception to retirement. The methodology should describe the method for defining an SOA in terms of a set of building blocks andshow how the building blocks fit together.

Provide a common vocabulary

Include a list of recommended standards

Provide guidance on implementation patterns

Provide a comprehensive set of "starter" models, templates, samples, best practices, and project management related artifacts.

Contain a prescriptive recommendation of a set of tools and compliant products that can be used to implement the building blocks.

Sunday, June 21, 2009

My opinion: "SOA is not even a factor in the larger discussion of budgets."

Budget decisions are made based on strategic, operational, and tactical objectives - in that order of preference. SOA really should not play a role in that decision as it is the means to an end. That is, SOA is the means to achieving IT alignment with the business with the end goal being becoming more "agile" in meeting the business objectives. So, the budget decision might be to marginalize the priority of a certain set of business objectives, which in turn might nix an SOA initiative. Contrarily, as other business objectives gain priority, SOA should be a consideration in the implementation of those objectives. So, the nutshell is that whether or not SOA gets used as a tool to stream operations or gets the knife itself is really a "side effect" of business level decisions related to long-term goals and objectives.

Friday, June 5, 2009

My answer to this question is one that would apply equally to many other enterprise level initiatives such as SOA -- an obsessive focus on technology. Yes, technology is ultimately the vehicle through which the initiative such as SOA or BI is delivered and made available but it is certainly not the end goal. In fact, I would contend that BI and SOA are not end goals either! Rather, the end goal driving at the need for BI is the ability of an organization to be more responsive, proactive, and agile in an ever more competitive marketplace. Having said that, I have seen many an organization where BI and SOA initiatives are driven by technologists, who are much more focused on tools and technologies (and the related concerns of scalability, availabilty, etc.). The end goals are almost forgotten and the desired benefits never materialize. So, technology-based "tunnel vision" is what I think is the leading cause of death for BI projects in the Enterprise.

Monday, June 1, 2009

The answer to the question as posted, in my opinion, is "Why not?" It's like asking "Should Ford's Model T have been made available in colors other than black?" I think the real question here is "Can the SaaS Vendor Offer On-Premise Options?" The answer to this question is much more involved as it depends on the vendor's business model and long-term vision/strategy, what exactly the SaaS vendor is offering, the variability and configurability of the offering, and so forth. But even if the SaaS vendor could somehow package up an "on site" version of its offering, could the client "afford" it with the required initial capital investment, ongoing support expenses, and appropriately skilled resources?

About Tarak

Tarak is a highly experienced, results-oriented, business leader, skilled enterprise architect, and published thought leader. He has demonstrated the ability to lead diverse teams of professionals in achieving mission critical results in a variety of highly competitive industries, cutting-edge markets, and fast-paced environments. His broad professional background and excellent education provides a solid foundation to his ability in solving challenging business problems with innovative enterprise solutions that leverage and align IT capabilities with evolving business needs.
As a testament to his thought leadership, he has authored Living in the Innovation Age and co-authored Professional Java Web Services. He has also published over 80 articles on Innovation, IT Transformation, and Enterprise Architecture.