next up previous
Next: Initial goals of Up: WISR Working Group Previous: WISR Working Group

Introduction

Many software organizations adopt object technology (OT), hoping for substantial reuse, yet do little to develop specific reuse-enhancing plans or use known and emerging methods of systematic reuse (such as CFRP-based process, Creator/Utilizer organizations, Domain Engineering methods, system and component generators). While acknowledging that reuse is a balanced People, Process and Technology issue, most OO researchers and many practioners focus on purely technical issue. Languages and methods seem most popular with research, while frameworks, patterns and business objects seem more popular with industry. OO companies seem to focus only on selling training on the latest methodology, and tools to support it, or low level libraries. Each group does what excites them most, or sells best.

The hypothesis is that this problem is in part fueled by two communities that rarely meet each other or read each others literature, in part because of historically different foci (software engineering in the large vs. rapid development in the small). There is too little general software engineering education in most CS programs, and too little reuse engineering in these, even though many do (try) to teach OO methods. We believe it is time for these two cultures to work much more closely together. Some work (eg., REBOOT, Gomaa's EDLC, RPM product, ...) have made some progress, but this not known outside the reuse community.



Larry Latour
Wed Sep 20 16:13:18 EDT 1995