Monday, October 15, 2012

What is a Platform?

Hi Fellow Architects - Here are some common questions Architects often have to deal with when trying to build/ define a Platform. Of course, I would like to hear from the experienced among you to seed this discussion.

What is the purpose of the Platform?
Is it for others to build business capabilities or else is this for serving up some business capability that is your competitive advantage. The former may be called Infrastructure as a Service and the later Information as a Service. This informs your decision on how much of the interface to expose.

The first, Infrastructure as a Service, requires you tighten the integration and management interface and the integration pathways via strict SLAs and service contracts that drive both the infrastructure usage patterns, infrastructure management and billing.
The later, Information as a Service, drives you to define the service contract that is unique to your business needs with very tight service definition and service usage criteria while treating all of the business rules for aggregation and information interpretation as proprietary Intellectual Property which is kept under tight wraps. Here the interaction is via clean, crisp, stable interfaces that are defined and described in standard formats.
What are the common attributes of either Platform?
It has to be Extensible, Scalable and Flexible and it has to have the level of reliability that we have come to expect with services such as email, Google maps etc.
I would like to hear from you on what other key attributes should or could be part of any Platform.
  1. Are there any standards that govern these concepts?
  2. What if any principles and tenets apply to the building of a Platform?
  3. Do you treat this as just a technology choice or is this about using the technology to deliver the Platform capabilities?
  4. How do you insure that the constraints of the technology are not becoming the limiting factor to your Platform?
  5. How do you build the Platform so that you are in a forever beta mode without it becoming an onerous Platform management process?
  6. What are some of the key concepts you would want to establish as ground rules or concrete principles so that the basic premise of the Platform is not broken over the multiple iterations?
  
Thank you for tuning in. Your feedback is invaluable.
surekha -
surekha.durvasula@gmail.com

Sunday, July 22, 2012

Mastering Master Data??

Hi Fellow Architects,


Master Data has almost become a boring topic these days but I still find that many orgnaizations have not yet either harnessed the power of their master data or else have not really turned the corner on the "Master Data Project" which is now becoming an unwieldy expensive never ending project. 

I was wondering if any of you have had success stories in this space and have been able to come up with some simple best practices on tocpics related to master data such as the following -

a) how do you determine what is valuable information to be mastered and what not to?

b) how do you determine if the master data continues to be of relavance to the enterprise?

c) how the profile of master data has changed in the world of social networking etc.?


Your feedback is always welcome!!
--
Best Regards.

surekha -