Frames: How to Treat Software Components as Capital Assets -- and Why You Should

by Paul G. Bassett

The key technical barrier to capitalizing software components is our insistence on defining them as use-as-is, encapsulated executables. A proven technology -- known as "frames" -- breaks this barrier by shifting from use-as-is parts to "smart parts" that customize each other as needed. Independent auditors confirm that these capital assets deliver hard-to-believe ROIs. They also enable major improvements across software's entire lifecycle, from requirements gathering to so-called maintenance. As with any paradigm shift, it's fraught with nontechnical barriers. This Executive Report by Paul G. Bassett explains how to overcome the barriers and why you should.