Patching and Deployment

Vol. 3 No. 2 – March 2005

Patching and Deployment

Articles

Understanding Software Patching

Developing and deploying patches is an increasingly important part of the software development process.

by Joseph Dadzie

Patching the Enterprise

Organizations of all sizes are spending considerable efforts on getting patch management right - their businesses depend on it.

by George Brandman

On Plug-ins and Extensible Architectures

Extensible application architectures such as Eclipse offer many advantages, but one must be careful to avoid "plug-in hell."

by Dorian Birsan

UML Fever: Diagnosis and Recovery

Acknowledgment is only the first step toward recovery from this potentially devastating affliction.
The Institute of Infectious Diseases has recently published research confirming that the many and varied strains of UML Fever continue to spread worldwide, indiscriminately infecting software analysts, engineers, and managers alike. One of the fevers most serious side effects has been observed to be a significant increase in both the cost and duration of developing software products. This increase is largely attributable to a decrease in productivity resulting from fever-stricken individuals investing time and effort in activities that are of little or no value to producing deliverable products. For example, afflictees of Open Loop Fever continue to create UML (Unified Modeling Language) diagrams for unknown stakeholders. Victims of Comfort Zone Fever remain glued in the modeling space, postponing the development of software. And those suffering from Gnats Eyebrow Fever continue creating models that glorify each and every Boolean value of prospective software implementations.

by Alex E. Bell

Curmudgeon

Comments are More Important than Code

The thorough use of internal documentation is one of the most-overlooked ways of improving software quality and speeding implementation.

by Jef Raskin

Kode Vicious

Kode Vicious Reloaded

The program should be a small project, but every time I start specifying the objects and methods it seems to grow to a huge size, both in the number of lines and the size of the final program.

by George Neville-Neil