  |
|
|
|
The basic framework for comparing software and hypertext is mainly comprised of system size. This can further be divided into features such as structural properties, development processes, software reuse, unit testing, black-box testing, version control and configuration management, that characterize the task of maintaining software. These features are essentially independent of one another and so are not ranked in any particular way.
Small-scale programming includes structures that might be adopted for a relatively modest program, such as one produced by a single programmer over a few days or weeks. The parallels between Web documents and computer programs should not be taken too far. Within Web documents, there is nothing equivalent to a thread of execution, although Java applets come close. Also, unlike software, each load operation in Web documents is user-initiated. Large-scale programming and hypertext Large-scale programming involves the levels of effort that a team of programmers would put into a system over a number of months or years. Design practices, design tools, and maintenance tools are fairly well developed for largescale programming problems. The same cannot be said for hypertext documents. In this respect, the problems associated with the development of hypertext documents resemble those encountered in the development of software 30 to 40 years ago. This is therefore the area where most lessons can probably be learned. Go To Page: 1
The copyright of the article Hypertext and Software in Software Re-engineering is owned by Faisal Bin Bashir. Permission to republish Hypertext and Software in print or online must be granted by the author in writing.
|
|
|
|
