| |
Software Solutions
Adding usability improving solutions during late stage development is to some extent restricted by the software architecture. However, few software engineers and human-computer interaction engineers are aware of this important constraint and as a result avoidable rework is frequently necessary. In this paper we present a new type of pattern called a bridging pattern. Bridging patterns extend interaction design patterns by adding information on how to generally implement this pattern. Bridging patterns can be used for architectural analysis: when the generic implementation is known, software architects can assess what it means in their context and can decide whether they need to modify the software architecture to support these patterns. This may prevent part of the high costs incurred by adaptive maintenance activities once the system has been implemented and leads to architectures with better support for usability.
Reuse is such a powerful tool - so why isn't it more popular? Software development organizations live or die based on how effectively they generate, assimilate, reuse, and leverage their knowledge. While there is an abundance of knowledge artifacts like code modules, program charts, system designs, and requirement specifications in such organizations, this overabundance is precisely what keeps reuse an elusive silver bullet. This article offers insights from field research in 25 software development organizations to highlight the two missing parts of the reuse knowledge management (KM) puzzle - recoding and redesign. All organizations in our study had some sort of systematic reuse program in place.
Below are partner links recommended:
|
|
