This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Project Asset Portability
January/February 2006 (vol. 23 no. 1)
pp. 100-101
Diomidis Spinellis, Athens University of Economics and Business
Nowadays, a software system's program source code makes up only a small part of its assets stored as bits--taking up a larger percentage are specifications, design diagrams, application server deployment scripts, build rules, version history, documentation, and regression tests.

How is the situation in your organization? Can you easily move your design diagrams from one UML-based tool to another, change the repository where your specifications are stored, run your regression tests on a different platform, or switch to a different configuration management system? Unless your organization still uses paper records for these tasks (in which case your problems are in a totally different league), chances are you dread even the thought of changing the tools you use.

Index Terms:
software tools, project assets, portability
Citation:
Diomidis Spinellis, "Project Asset Portability," IEEE Software, vol. 23, no. 1, pp. 100-101, Jan.-Feb. 2006, doi:10.1109/MS.2006.28
Usage of this product signifies your acceptance of the Terms of Use.