|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Diomidis Spinellis, "Project Asset Portability," IEEE Software, vol. 23, no. 1, pp. 100-101, January/February, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2006.28, author = {Diomidis Spinellis}, title = {Project Asset Portability}, journal ={IEEE Software}, volume = {23}, number = {1}, issn = {0740-7459}, year = {2006}, pages = {100-101}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.28}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Project Asset Portability IS - 1 SN - 0740-7459 SP100 EP101 EPD - 100-101 A1 - Diomidis Spinellis, PY - 2006 KW - software tools KW - project assets KW - portability VL - 23 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2006.28
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.

