Definitive Software Library Whitepaper

September 3, 2009

These days, everyone is talking about the need to do more with less. Challenging economic conditions have led to smaller development teams and intense pressure to shorten time to market and reduce costs. Pressure to meet legal, regulatory, internal and technical compliance requirements continues to grow and it’s difficult to keep up using only manual reviews. However, these challenges can drive companies to take shortcuts that may ultimately increase costs and result in the creation of software that’s difficult and costly to maintain, enhance or change to meet changing business needs. Companies often have trouble finding or even defining the high-value core competency assets that are driving business value in the organization. In situations like these, it’s essential to get control of and understand your assets to reduce your solution delivery costs.

Development teams sometimes turn to open source or third-party components to expedite development, but these components may not be supported in the long run or support contracts for maintenance may not be available, which means that troubleshooting problems in the future becomes next to impossible. Or, teams attempt to reduce development costs by outsourcing to a lower-cost provider. However, if the team has failed to properly store and document its assets, it can take providers weeks of initial work to search through thousands of work products scattered throughout a variety of domain-specific repositories before they find the assets they need, increasing the cost of the engagement.

In this White paper I explain how a definitive software library can be used to address these challenges and reduce costs associated with managing and using your software assets.


4 Responses to “Definitive Software Library Whitepaper”

  1. Jason Stanis Says:

    I am interested in leveraging some of the features of RAM to help manage enterprise architecture assets that we are creating in Rational/Telelogic System Architec.

    I posted a thread out on developer works a while back but it has been quiet…

  2. Carlos Says:

    Hi Jason. Thanks for commenting. We have gotten many requests from customers. And we are working things into our plans. Just like with all the other IBM product acquisitions.. the first release after acquisition is called “bluewash” This type of release ensures you have the right branding, support the right languages, accessibility, have removed any questionable components etc… The more customers who ask for the the integration the higher prioritization it gets.

  3. Gili Says:

    Example movie of using a DSL with a development build process is published here:

  4. Tahir Rashid Says:

    Hi All,

    I am doing my final year project with regards to implemnting a DSL and the information i have come accross is its importance and implmentation. I was wondering if you point me into the right direction with regards to History of DSL and how this has changed over time .

    You can email me directly on with any links or information you may have .

    Many Thanks,


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: