is part of Professional services group of IBM/Kenexa, based out of IBM Visakha Hills Lab in Visakhapatnam. He was earlier part of WebSphere development at IBM India Software Labs in Bangalore. Prior to this, he was a consultant at WebSphere BPM Practice. He is a Certified SOA Solution Designer(2007), Certified SOA Associate, co-author of WebSphere InterChange Server Migration Scenarios redbook. He is Member, Board of Studies, Dept of CSE, College of Engineering, Andhra University. He blogs here and tweets, sharing his Social Experience, as the scroll of Life unrolls in the Eternal Enterprise!
Continuing further on my earlier posting on Software Assets
, I was mentioning if there exists any standard in software assets space. Reusable Asset Specification
(RAS) provides a standard way to describe and package assets. So when was RAS defined? Some RAS timelines.
- RAS was initially developed by the RAS consortium 2001-2003
- RAS was adopted at the St. Louis OMG meetings, April 2004
- The RAS FTF submitted its Final report to the OMG in March 2005
- RAS FTF Final report accepted and final voting completed by OMG in June 2005
So, next thing to ponder on is the need for RAS. RAS is needed for a common representation of assets to enable the transfer, sharing, and management of software assets. RAS provides the organization and structure of information and artifacts for an asset. Lets see in a later posting, on asset management/governance provided in the form of asset repositories, which is critical in SOA implementations.
Technorati Tags: standard, ras, asset
Post to del.icio.us