Managing Software As Data » History » Version 7
Steve Welburn, 2012-11-13 03:03 PM
| 1 | 1 | Steve Welburn | h1. Managing Software As Data |
|---|---|---|---|
| 2 | 1 | Steve Welburn | |
| 3 | 2 | Steve Welburn | The same issues as for data arise: |
| 4 | 6 | Steve Welburn | * [[Backing_up|Backing up]] |
| 5 | 2 | Steve Welburn | * Documentation |
| 6 | 2 | Steve Welburn | |
| 7 | 3 | Steve Welburn | However, whereas data changes slowly / infrequently, software is subject to ongoing changes during a project. Source code for software usually consists of text files and should therefore be stored in a suitable version control system (e.g. Mercurial, Subversion, git). Additionally, binary releases of software may be created as downloads for a project. |
| 8 | 2 | Steve Welburn | |
| 9 | 7 | Steve Welburn | Additionally, documentation has broader requirements - including both documentation to make the code maintainable (e.g. comments in the code, documenting APIs, Javadoc style documentation) and user documentation to explain how to install and use the software. |
| 10 | 7 | Steve Welburn | |
| 11 | 5 | Steve Welburn | The "Sound Software":http://www.soundsoftware.ac.uk project provides software project management facilities for digital music and audio research including Mercurial version control, downloads, documentation, issue lists and wikis through its "code repository":http://code.soundsoftware.ac.uk |